-
Type:
Task
-
Status: Open (View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:3
-
Sprint:2DDRP-2021 A3, 2DDRP-2021 A 4, 2DDRP-2021 A5, 2DDRP-2021 A 6, 2DDRP-2021 A 7, 2DDRP-2021 A 8, 2DDRP-2021 A 10
As discussed during the internal Princeton Group telecon 2021-03-22, please go through the recent stability data acquired at Subaru this year, identifying those visits which are 'good' and those which are problematic, due to hardware configuration changes, significant SCR temperature variations, etc. This requires sifting through the relevant logs etc.
The 'good' visits will be passed on to the automatic pipeline for subsequent processing and analysis.
- blocks
-
PIPE2D-711 Coordinate regeneration of CALIB registry on summit
-
- Open
-
-
-
- Open
-
- relates to
-
-
- Won't Fix
-
The labelling of the 'good' stability data into calibration data and science data is the subject of PIPE2D-791 (linked). I'm fine to close that ticket and combine both tasks into this single ticket if in practice they cannot be separated easily, and there's less confusion.
Good point, Hassan. I think we may want to merge the two tickets as exactly how to do PIPE2D-791 will become clearer as part of this work, but let's leave them as-is for now.
I think we need a bit more than that. I'd like to label a subset of the data as calibration data and a subset as science data (and this may mean a new way to do the book-keeping). Then generate calibrations using the calibs (and Mineo-kun's scripts), and look at the results and sort out what's going on.
For example, using the calibs in /scratch/pprice/pipe2d-706/CALIB I see fiberId 464 as consistently offset; why?
Ultimately, we want a set of calibrations produced using the automated tools that are as good as we can produce.