[PIPE2D-73] Several PfsMapper.paf glitches Created: 07/Sep/16  Updated: 23/Jul/19  Resolved: 23/Jul/19

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

Type: Bug Priority: Major
Reporter: cloomis Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

1. The output of a detrend.py was postISRCCD/2016-09-01/v0000057/PFSAr1.fits. Shouldn't that be ..../PFSA-000057-1r.fits?

I.e. can I change

postISRCCD: {
template: "postISRCCD/%(dateObs)s/v%(visit)07d/PF%(site)s%(category)s%(arm)s%(spectrograph)1d.fits"

to:

postISRCCD: {
template: "postISRCCD/%(dateObs)s/v%(visit)07d/PF%(site)s%(category)s%(visit)07d%(arm)s%(spectrograph)1d.fits"

2. Likewise for calexp.

3. While at it, can we swap arm and spectrograph for spArm?

4. And should the spArm key be pfsArm?



 Comments   
Comment by hassan [ 03/Nov/18 ]

Confirm with cloomis whether this can be resolved.

Comment by hassan [ 21/Jul/19 ]

To quickly review with cloomis and price against current DRP code.

Comment by price [ 23/Jul/19 ]

I've confirmed that 1 and 2 have been done (we have postIsrCcd-%(site)s%(category)s%(visit)06d%(arm)s%(spectrograph)1d.fits and calExp-%(site)s%(category)s%(visit)06d%(arm)s%(spectrograph)1d.fits).

Regarding 3 and 4, I don't know what spArm was, but it doesn't exist any more.

I recommend closing this.

Comment by cloomis [ 23/Jul/19 ]

I concur.

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