-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tile 11 stuck positioners assigned different ra,dec on different exposures (both are wrong) #2359
Comments
I had a look at that. my understanding is:
I don t see an obvious way to fix that at the exposure level, as I guess the thing to do would be to use for the relevant part of the fibermap code should be: desispec/py/desispec/io/fibermap.py Lines 891 to 897 in abfec75
and desispec/py/desispec/io/fibermap.py Lines 991 to 999 in abfec75
if useful, illustrating what s in the coordinates files:
|
and a side-comment: if useful, here s a check of the number of rows with
|
@sbailey: for info, I m running separate few sanity checks on kibo, and I stumbled on those again, I believe. I m parsing the healpix redrock files (EXT_FIBERMAP) extension: |
for completeness / book-keeping, here s a list of those healpix files (identified with np.nan for PLATE_RA or PLATE_DEC):
|
Tile 11 observed on 20210505 exposures 87353 and 87354 had a set of stuck positioners that got assigned different TARGET_RA, TARGET_DEC for the two exposures.
From kibo/preproc/20210505/00087353/fibermap-00087353.fits
From kibo/preproc/20210505/00087354/fibermap-00087354.fits
It looks like in one case the code is assigning default values to something way off the tile, and in another case assigning them to 0.0 (which I thought we had previously fixed...).
These are all bad targets and thus aren't particularly high priority, but we should understand the bookkeeping of this and get it standardized. It lead to the healpix bookeeping issue in #2354 due to different fibermaps of the same tile covering different healpix.
The text was updated successfully, but these errors were encountered: