Open rosteen opened 1 year ago
It's unclear to me what the suggestion is. Is it that non-JWST files get loaded with the (1d) JWST loader if they have TELESCOP=="JWST"
(which seems fine to me, though your description seems to be of an XY problem), or something more general?
I recently encountered a use case where a science team was creating their own data products and attempting to match the JWST file format, so that the files could automatically be identified and read in by the
specutils
IO machinery. The last sticking point was that the _identify_jwst_fits function requires that there be anASDF
extension in the file as well as havingTELESCOP=="JWST"
in the header. As far as I can tell, only 2D and 3D files actually use theASDF
extension, so I'm thinking that removing that requirement for identifyingx1d
files might be useful to make it easier for users to create JWST-style files and have them identified. I'm opening this issue in case there are any objections (I'm not convinced yet that this is a good idea myself) - to me, a potential downside is the case where a user creates a file withTELESCOPE=JWST
in the header but in a different format that otherwise could be read by one of the generic readers.