Update det setup and relock blocks #261
Conversation
|
Should we remove scheduler/src/schedlib/policies/satp3.py Line 93 in 443fa02 |
That's in the relock block not detector setup for SATp3 so isn't that still used or was that what Katie meant in #260, to remove it from both relock and det setup? Just remembered, I'll need to update the estimated durations too. |
|
I thought this is what Kaite meant in #260. |
|
I believe this is what Katie meant @mmccrackan. I'm okay with removing it from the relock block because relock automatically takes noise for 30 seconds, so we'll have a super conducting noise to reference and track over time. I don't think there is a take_noise in the regular det setup. @kmharrington @msilvafe I think it would be good to add functionality to track the white noise levels from the relock-- do we think we could get someone to add this functionality without much difficulty? |
|
On the R&D call we discussed that we should now have both fixed tones in the data streams and bare resonator channels on the wafers. So we should still have plenty of in-situ tracking capabilities for readout noise levels. We do need trackers built for these sorts of things. We need trackers for a lot of things.... |
|
And yes @mmccrackan this is what I was meaning |
Oh I see, so there are bare resonators already on each wafer? And the idea is to have those taking data concurrently with the TESes as well? |
|
The bare resonators and fixed tones don't actually track the flux ramp so they're not a very good tracer of the readout noise. The dark squid is a better tracer of the readout noise, its a channel with a squid that's flux ramped but doesn't have any TES attached. That gets tracked through the metadata as SQID I believe perhaps we just need to figure out how to tag that properly in the data quality metrics stuff so that we can monitor that in grafana. |
Updates detector setup and relock blocks according to #260.