Opened 16 years ago
Last modified 16 years ago
#1351 assigned enhancement
Make EXTDATA values all upper-case
| Reported by: | Michael Wood-Vasey | Owned by: | eugene |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ippconfig | Version: | current |
| Severity: | normal | Keywords: | |
| Cc: |
Description
CFITSIO funpack rewrites EXTDATA as all caps. I'm not sure that this follows any particular standard, but CFITSIO has some implicit power. As a practical issue, it would be a great convenience is the EXTDATA values could be written, or, more importantly, recognized, by IPP software in all-caps.
This is a ticket file subsequent to discussions with Joel Welling and Gene Magnier.
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Component: | config → ippconfig |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
to make this fix for future data, we only need to change the entries in ippconfig/*/camera.config EXTNAME.RULES.
I believe that list (EXTNAME.RULES) is only used to generate output
Double check that read functions do not rely on the names listed in EXTNAME.RULES (only on the header info)
comment:3 by , 16 years ago
looks like this is used by pmSourceIO.c and pmPSF_IO.c. The read functions do use the table do decide where to find PSF and source tables.
To make the backwards compatible, we need to make the code and the rules know how to look for the older names.

This should apply to EXTNAME as well. What's the difference between EXTDATA and EXTNAME anyway?