Skip to content
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

SKYTHRURMS on 20240821, tiles 27156, 27117, expid 249649-249651 #207

Open
schlafly opened this issue Aug 27, 2024 · 5 comments
Open

SKYTHRURMS on 20240821, tiles 27156, 27117, expid 249649-249651 #207

schlafly opened this issue Aug 27, 2024 · 5 comments

Comments

@schlafly
Copy link
Contributor

QA reports large SKYTHRURMS on 20240821, tiles 27156, 27117, expid 249649 - 249651. I don't actually see anything wrong with the data and can't think of a case where SKYTHRURMS has told us something useful before, so I don't really know what to do with this. 249650 & 249651 are particularly interesting because almost all R cameras have high SKYTHRURMS but the BZ cameras do not, and we expect TPCORR to be fairly achromatic. These are bright tiles with pretty fine looking redshifts, so I'm inclined to ignore them, but @julienguy expressed some interest in these tiles.

@daqiii
Copy link

daqiii commented Aug 27, 2024 via email

@araichoor
Copy link
Contributor

it s formally computed here (it s a per-exposure, per {petal,camera} measurement):
https://github.com/desihub/desispec/blob/019d6fa7d7707d4d3af6a444c927d5c1bf234866/py/desispec/exposure_qa.py#L355-L357

            sky_throughput_corr=fitsio.read(sky_filename,"THRPUTCORR")
            petalqa_table[band.upper()+'SKYTHRURMS'][petal]=1.48*np.median(np.abs(sky_throughput_corr-1))
            log.info("petal #{} {} sky throughput rms={:4.3f}".format(petal,band,petalqa_table[band.upper()+"SKYTHRURMS"][petal]))

@schlafly
Copy link
Contributor Author

Yeah, that was our question when we saw those alerts too---we don't see them very often. It's the spread in "TPCORR", which is intended to be a measure of how consistent the sky amplitudes are among the different fibers. i.e., our expectation is that the sky fibers can be used to subtract the sky from the science fibers, but there is some code that tries to compute a per-fiber sky amplitude (TPCORR) based on the sky lines; this is reporting that the variance in those TPCORR measurements is larger than nominal.

I don't understand it yet.

@araichoor
Copy link
Contributor

about those three exposures:

@geordie666
Copy link
Collaborator

For the record, we marked these tiles as good in QA. This issue remains open in case anyone wants to dig deeper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants