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

monitor evolution of new charge trap in z1 #259

Open
sybenzvi opened this issue Dec 17, 2024 · 2 comments
Open

monitor evolution of new charge trap in z1 #259

sybenzvi opened this issue Dec 17, 2024 · 2 comments
Labels
dailyops For listing individual dailyops problems

Comments

@sybenzvi
Copy link
Collaborator

@julienguy has noted the development of a new charge trap in z1b during the past two weeks. The trap's effect is visible in differences in QA plots from 2024-12-01 and 2024-12-12. See also the relevant discussion in #instops.

Note that z1, which is a replacement CCD, is currently read out in 4-amp mode. This ticket is a reminder to watch for effects on redshifts from this device as part of daily QA.

@sybenzvi sybenzvi added the dailyops For listing individual dailyops problems label Dec 17, 2024
@araichoor
Copy link
Contributor

reminding this ticket, as it looks like the effect is getting stronger, and now maybe starts to impact redshift quality.

here are the plots for 20241229:

  • ctedetrow:
Screenshot 2024-12-30 at 10 16 39 AM (here s a compilation for all Dec. 2024 nights: https://data.desi.lbl.gov/desi/users/raichoor/tmpdir/ctedetrowbyrow-202412-z1.pdf)
  • skyzfiber:
Screenshot 2024-12-30 at 10 16 50 AM
  • per-petal success rate:
Screenshot 2024-12-30 at 10 16 57 AM

@sybenzvi
Copy link
Collaborator Author

sybenzvi commented Jan 6, 2025

Comment: Julien has modeled the trap in software and the success rates in P1 seem to be pretty good since the start of last weekend (2025-01-03).

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

No branches or pull requests

2 participants