SJS checked through EFOSC2 and SOFI spectra for basic checks of validity of important header keywords. SOFI spectra all look fine (apart from the integer shoft problem which also affects all EFOSC2 data), EFOSC2 data have some issues
Bugs for Dave/Morgan to check/correct in purple. Bugs for Stefano to correct in next version of pipeline in red
Working on the *si.fits files in /data/psdb2data1/pessto_eso_phaseIII/validated_pessto_files/efsoc/spectra
There are 860 science spectra (*si.fits). ALL of the problem files below are from files from April 2012
List of files in : SPEC_BIN_problemfiles.txt
Stefano to check in pipeline and correct for next release.
A large number of files have a garbage value set for
SPEC_RES= 432.0955936041426 / Spectral resolving power
For example, it should be 357 or 225 for Gr13 (for 1 or 1.5" slits), but it is recorded as values between 3-30, which is obviously wrong. Similar problem for Gr11 and Gr16 exists.
There are 70 problem files - in SPEC_RES_problemfiles.txt
Stefano - how is this value calculated ? Is it measured on the arc frames ? Can pipeline be revised to reduce these failures for SSDR2 ?
The pipeline shifts the spectra in wavelength with respect to the sky lines. But the value for SHIFT in the header is always an integer. Why ? It should not be ? Is it recorded wrongly, or is it calculated wrongly ?
Also, the value for SHIFT is missing in two files
SOLUTION: set SPEC_ERR = 1
The SOFI spectra also have integer shifts.