Opened 17 years ago
Closed 17 years ago
#11 closed enhancement (fixed)
Use a statsec to define the statistics
| Reported by: | Matthew Whiting | Owned by: | Matthew Whiting |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Searching | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Currently, the statistics for the cube are either calculated on the full cube, or the user specifies a fixed threshold. It would be useful to have the option of specifying a subsection of the cube in which to calculate the statistics, and then apply those values to the full cube (for instance, if you know a large chunk of your cube is going to be contaminated by bright emission).
This would work by having a parameter "statsec" that needs to be given as a subsection string. We would then need to parse that to get offsets and so on -- change the parseSubsection() function to a generic function and then use it for both the data subsection and the stats subsection.
Note: See
TracTickets for help on using
tickets.
Done: [254] and subsequent. Can now specify a statsec parameter, and the section is read in the same way as the pixel subsection.
Ticket closed.