Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_auxiliary_telescope
-
Labels:
-
Story Points:4
-
Epic Link:
-
Sprint:TSSW Sprint - Sep 2 - Sep 14, TSSW Sprint - Sep 16 - Sep 28, TSSW Sprint - Sep 29 - Oct 13, TSSW Sprint - Oct 14 - Oct 27
-
Team:Telescope and Site
Description
The output of the spectrograph is currently going to be stored in the Large File Annex (LFA) as FITS files. The CSC needs to be able to push data to the LFA after it is read out and packaged: this ticket is for the work to manage that communication.
My goal here is to make this flexible enough that it is easy to swap it out if we decide we want to use some other storage method (e.g. direct to database).
Where do I find documentation about how to communicate with the (an?) LFA? How should we handle testing of that communication? I can obviously stand up a mock as I'm doing for the spectrograph itself, but it would be good to have a "real" system I can talk to for validation.
Attachments
Issue Links
Activity
I am happy with the implementation and I will do the updated WCS storage in DM-21797
John Parejko Is the data array (HDU 0 in your example above) one-dimensional, or is it two-dimensional with the list of wavelengths applying to one of the two axes (i.e., the dispersion direction in a chip image)?
I see that https://github.com/spacetelescope/jwst/issues/2235 discusses the implementation of astropy support for WAVE-TAB via GWCS.
John Parejko I believe that the way to just get the two arrays from a file in WAVE-TAB format would look something like this:
hdulist = astropy.io.fits.open(filename) |
instFlux = hdulist[0].data |
wavelength = hdulist[1].data.field('WaveCoord')[0] |
(You are extracting the array-valued data in the 'WaveCoord' column in the 1st and only row of a one-row binary table.)
This is what you would do if you were in control of how the file was written and you knew for sure that the binary table was in the first extension and that the column name for the wavelength list was 'WaveCoord'. If you wanted to write more bulletproof FITS-standard-compliant code, you could look up the extension name and column name; it might look like this:
hdulist = astropy.io.fits.open(filename) |
instFlux = hdulist[0].data |
assert hdulist[0].header['NAXIS']==1 |
assert hdulist[0].header['CTYPE1']=='WAVE-TAB' |
waveext = hdulist[0].header['PS1_0'] |
wavecol = hdulist[0].header['PS1_1'] |
wavelength = hdulist[waveext].data.field(wavecol)[0] |
Given the above discussion, are you willing to mark this ticket and the PR `Reviewed`, Tim Jenness?