Bright tile 26226 observed with high read noise about desisurveyops

[schlafly]

We discussed this on the 20220321 survey-ops call and decided that we would call these exposures bad (126715, 126716, 126717, 126718). This is the three exposures on the BRIGHT tile (026226) and the one exposure on the following BACKUP tile (41779). I'm not convinced that the read noise is actually an issue on this BRIGHT tile in very bright sky conditions, and I'm confident that it's not an issue on the following BACKUP tile, but for homogeneity's sake we'll take the very marginal loss of effective time.

@akremin, can you mark these as bad and reprocess?

[schlafly]

@akremin , this one has somewhat high priority because it's one of the few tiles remaining in the early, southern part of the NGC, which is now setting. It would be good to mark this exposure bad so that we can get more observations to complete this section of the footprint in Y1.

[akremin]

Apologies -- I missed this the first time around and am just getting to it after the ping yesterday.

The four exposures (126715, 126716, 126717, 126718) have been marked bad, and the spectra+redshift files associated with those exposures have been removed from daily. There were no other exposures for those tiles, so nothing needed to be rerun. I also don't see any later observations of the tiles, so no downstream cumulatives need to be redone either.

I just reran the tsnr script and the nigthly_qa script to reflect the removal of these exposures.

Back to you, Eddie.

[schlafly]

Thanks, I cleared the QA here.