[PIPE2D-1210] Reduce data obtained in Nov 2022, Apr, July 2023 for the internal data release (EDR2) Created: 01/May/23  Updated: 01/Feb/24  Resolved: 01/Feb/24

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Kiyoto Yabe Assignee: Kiyoto Yabe
Resolution: Done Votes: 0
Labels: EDR, EngRun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PIPE2D-1241 Reduce data obtained in Apr 2023 run ... Done
relates to PIPE2D-1140 Reduce data obtained in Nov run for t... Done
Story Points: 3
Sprint: EDR+AIT

 Description   

Similar to PIPE2D-1140, reduce the data obtained in 2023 Apr commissioning run. 
The list of calibration data taken may be found in PIPE2D-1187
 

A complete set of visits to be reduced are:

run12 (Jul 2023): https://sumire.pbworks.com/w/page/153934425/Science%20Data%20from%20Run%2012

run11 (Apr 2023): https://sumire.pbworks.com/w/page/153263325/Science%20Data%20from%20Run%2011

run08 (Nov 2022): https://docs.google.com/document/d/1qfZV55DYlx9t7ru6dKntg3CiJj2HF3McBwJ2DZUrCWk/edit

 



 Comments   
Comment by Wilfred Gee [ 03/May/23 ]

Just a note that the Twilight Sky dates should be 4/22 (UTC) and visit 91183-91187.

Comment by yuki.moritani [ 03/May/23 ]

Thank you for pointing it out. I corrected visit and date. I'm sorry I was not clear, but the dates are the night of observation. (It should be confusing though..)

Comment by rhl [ 13/May/23 ]

I'm confused by those names. E.g. visit 91178 is '0x7efb873c7b26a935', 'fluxcal_test_da_4419865155422033280_pa+00_sm1 V001' but this list calls it "da_4419865155422033280". Maybe we could standardise on the pfsDesignId (with or without the designName)?

Comment by yuki.moritani [ 13/May/23 ]

I'm sorry for confusion. I agree to add pfsDesignId on the list, I was lazy to put them, hoping someone would like to put one later as long as visit is listed.. (If I do next time, I'll be more careful.) design.Name was sometimes too long and a little confusing as the same name was used for different design, so designId should be listed, I feel.

Comment by Kiyoto Yabe [ 01/Feb/24 ]

The processing is done for the release as `edr2-20231203`, so I close this ticket.

Generated at Sat Feb 10 16:04:18 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.