[PIPE2D-1187] Plan for data acquisition April 2023 run Created: 18/Mar/23 Updated: 01/Jul/23 Resolved: 19/May/23 |
|
| Status: | Done |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | arnaud.lefur | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | EngRun | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Sprint: | PreEng11Apr1 | ||||||||
| Description |
|
With the upcoming run in April 2023, we'll have opportunities to take calibration data. spectrograph : 1,3
data taken is listed here . |
| Comments |
| Comment by yuki.moritani [ 28/Apr/23 ] |
|
As of 2023.04.30, the following dataset was taken (see also https://sumire.pbworks.com/w/page/152988447/Calibration%20Data%20from%20Run%2011 where we can track the processing history of these data):
|
| Comment by price [ 28/Apr/23 ] |
|
The fiberProfile sets do not include the requested slit dither. The slit dither is important to measure the sub-pixel profile for the central fibers. The ditheredFlat set does not include repeats for the dithers, which leaves them vulnerable to CRs. The set needs to be repeated from the start; it is not sufficient to attempt to take new data at the previous slit positions. |
| Comment by price [ 03/May/23 ] |
|
Can I request for the future that when a set of arcs is taken, that a quartz also be taken as part of the same set? The quartz contains a lot of information in the spatial dimension that helps with getting a good detectorMap solution. |
| Comment by price [ 03/May/23 ] |
|
Thanks for the new fiberProfiles data! I believe it’s allowed us to make the best fiberProfile measurements yet (see attached files). In particular, the problems we used to have with fibers at the center of r1 don’t appear to be present. We had previously attributed those problems to imprecise detectorMaps, but I now believe that it was caused by a lack of sampling, and the inclusion of the slit dithers has solved it. There are some fibers that have weird profiles, which mainly appears due to malfunctioning cobras (84,85,86,114), and some lower-level issues, but I’m very happy with this. I hope that we’ll be able to repeat it with m1, m3 and n1 when the data for those becomes available. For the record, I used the following datasets: set5_allHidden, set5_1vs4_set0_dithered, set4_1vs4_set2_dithered, set3_1vs4_set3_dithered, set2_vs14_set1, set3_1vs2_dithered, set4_1vs2_dithered |