Opened 20 years ago
Closed 20 years ago
#814 closed defect (fixed)
ppStats's output is different depending on the format of the input FITS files
| Reported by: | jhoblitt | Owned by: | Paul Price |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | ppStats | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Which is problem for things like the pXtools helper scripts which need to
processes this output. This isn't nessicarily a ppStats issue but it is
something that we need to work out. As a temporary solution I've hacked
together a PS:IPP::Metadata::StatsFilter module that simple renames header
values output by ppStats but this isn't a very sophositcated solution. It
really needs to have some more intelligence/configuration to it. I'm wondering
if it doesn't make sense to put some 'mapping function' functionality into ppStats?
Change History (2)
comment:1 by , 20 years ago
| Status: | new → assigned |
|---|
comment:2 by , 20 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
The use of the concepts in the previous comment have resolved this bug --- I can
run ISP and MegaCam data through the same script.
Note:
See TracTickets
for help on using tickets.
Added concepts:
FPA.OBSTYPE
FPA.ALT
FPA.AZ
CHIP.TEMP
into psModules as standard, fully-supported concepts. This is a step towards
resolution of this bug.