gijsverdoeskleijn
commented
3 years ago Thanks @nadsabha. Please check and correct my summary of what we decided this morning to get wavecal/micado.npz incorporating specifics from what you write above:
- @wkausch provides here a hyperlink to the line list of the MICADO wavelength calibration lamp ("linelist_MICADO"). Two essential columns are (1) wavelength of the line ("lambda_line_i") and (2) its relative strength (f_line_i").
- @nadsabha extracts for one detector and one slit the spectral layout (x_m,y_m,lambda_m) in specorders-180626.fits. Then does a linear interpolation to find x_line_i,y_line_i using the two tuples of (x_m,y_m,lambda_m) for the two lambda_m around lambda_line_i.
- Then populate the micado.npz as follows:
((“wlc”, “WLC”), “>f8”), = lambda_line_i ((“wll”, “WLL”), “>f8”), = lambda_line_i ((“posc”, “POSC”), “>f8”), = y_line_i ((“posm”, “POSM”), “>f8”), = y_line_i ((“xfirst”, “XFIRST”), “>i2”), = x_line_i ((“xlast”, “XLAST”), “>i2”), = x_line_i ((“approx”, “APPROX”), “O”), = we do not know what this is? @nadsabha : can you understand from existing npz files what this needs to be? If not, ask Ansgar for help. ((“width”, “WIDTH”), “>f8”), = if not in linelist_MICADO, @nadsabha : is it an idea to fix it to a single value for all lines as initial guess? And determine this typical value by eye from the simulated arclamp image FITS file? ((“height”, “HEIGHT”), “>f8”), = f_line_i ((“order”, “ORDER”), “>i2”), = @nadsabha : populate this manually using the simulated arclamp image FITS file? (“flag”, “?”), = set all to being used as initial guess?
@nadsabha few additional requests from me: please add hyperlinks to specorders-180626.fits. And to the uves npz file with the initial wavelength solution estimate. And to make sure I am not misunderstanding a critical thing: what does the "3-" mean in "3-Wavelength"?
nadsabha
One of the files to be created to make PyReduce run on MICADO simulated data: 3-Wavelength calibration file: wavecal/micado.npz (numbering scheme following the https://github.com/astronomyk/PyReduce/issues/1#issue-913337583)
It is a table (numpy recarray) with initial guess for wavelength calibration as an npz file (pickled numpy recarray). From https://pyreduce-astro.readthedocs.io/en/latest/instruments.html it should be as follows: (e.g. https://github.com/astronomyk/PyReduce/blob/master/pyreduce/wavecal/uves_red_860nm_2D.npz)
"get_wavecal_filename, should return the filename to the wavelength calibration first guess. That is a npz file containing a numpy recarray called cs_lines. The recarray should have the fields:
((“wlc”, “WLC”), “>f8”), # Wavelength (before fit) ((“wll”, “WLL”), “>f8”), # Wavelength (after fit) ((“posc”, “POSC”), “>f8”), # Pixel Position (before fit) ((“posm”, “POSM”), “>f8”), # Pixel Position (after fit) ((“xfirst”, “XFIRST”), “>i2”), # first pixel of the line ((“xlast”, “XLAST”), “>i2”), # last pixel of the line ((“approx”, “APPROX”), “O”), # ??? ((“width”, “WIDTH”), “>f8”), # width of the line in pixels ((“height”, “HEIGHT”), “>f8”), # relative strength of the line ((“order”, “ORDER”), “>i2”), # echelle order the line is found in (“flag”, “?”), # flag that tells us if we should use the line or not "
The files we/I have are: (sent by Wolfgang)
i- Spectral layout folder (https://drive.google.com/drive/folders/1zBQzAZmonYXxeaQxfzc5bNrxosRMabi6?usp=sharing) with the files:
ii- Line lists folder (https://drive.google.com/drive/folders/1l9kKF2w-6gHgOdihVu7fB3mjxmUvSEut?usp=sharing) with the files: