[PIPE2D-469] fiber traces issues when working with 300 fiber data Created: 30/Oct/19  Updated: 17/Jun/20  Resolved: 17/Jun/20

Status: Won't Fix
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: ncaplar Assignee: price
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks PIPE2D-441 Attempt to reduce 300 fiber data Won't Fix
Story Points: 4
Sprint: 2DDRP-2019 I, 2DDRP-2019 J, 2DDRP-2019 K
Reviewers: hassan

 Description   

The constructFiberTrace.py fails when working on 300 fiber data. 

This is after we have decided to skip the flat fielding which was also failing. This is most likely  due to low flux levels available for this data. 

constructFiberTrace.py should have a bit easier time because there are 15 images avaliable, while for flat fielding only 1 image is available at each dither position. 

The full traceback is available at https://gist.github.com/nevencaplar/3da094c5c784f752ffe4ae22c67f24dc

The version of the pipeline is 5.1.4. (as available on Tiger October 28, 2019).

The command I run is sh pfs_preparation_Oct28.sh, which is available on Tiger in /home/ncaplar/ReductionScripts/Oct24. It calls modified pfs_build_calibs script (modified to skip flat fielding). 

 Comments   
Comment by price [ 17/Jun/20 ]

I think this is solved in PIPE2D-472.

Generated at Sat Feb 10 15:53:47 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.