[PIPE1D-25] Output pfsZcandidate*.fits files for the stellar solver Created: 30/Sep/20  Updated: 17/Dec/21

Status: In Review
Project: DRP 1D pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Normal
Reporter: ishigaki Assignee: Ali Allaoui
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to DAMD-92 Update 1D pipeline DM with multi-type... Done
Reviewers: ishigaki

 Description   

I’m running the drp_1dpipe for a stellar input spectrum and using a set of templates from X-shooter library (R~10000). A resulting velocity looks very good with 15km/s for an input spectrum of 18km/s.
The resulting pfsZcandidate*.fits file, however, contains only 2 HDUs instead of 5 and therefore does not contain uncertainty and posterior probabilities for the redshift. The contents of the output files look like:

No.  Name   Ver  Type   Cards  Dimensions  Format
 0 PRIMARY    1 PrimaryHDU   10  ()    
 1 ZCANDIDATES  1 BinTableHDU   21  1R x 6C  [D, D, J, D, 15A, 15A] 

 

When I set “enablestellarsolve = no”, an output pfsZcandidate*.file properly contains 5 HDUs, but when I set “enablestellarsolve = yes”, an output file contains only 2 HDUs. It would be great if the drp_1dpipe contains additional HDUs also for stellar analyses. 

 

 Comments   
Comment by vlebrun [ 02/Oct/20 ]

Dear Miho

actually we did not include the other HDUs, which contain the PDF, the model and the line measurements in the stellar solver output, because it did not seem relevant. Indeed the PDF is only computed on the very short redshift range  [-0.001;0.001], the model is only the template, and we do not perform line measurements on stars. 

For consistency, we will include those HDUs within this branch

Vincent

Comment by ishigaki [ 05/Oct/20 ]

Dear Vincent, 

Thank you for your comments! Yes, that would be very helpful. For the stellar solver, I set

"redshiftrange" [-0.001; 0.001],  "redshiftstep" 1.0e-6. Is this very small step compatible with the pipeline algorithm?

Comment by vlebrun [ 05/Oct/20 ]

Well, all steps values are theoretically OK, but the computation time will increase. It should remain OK as the resdshit range is small

Vincent

Comment by ishigaki [ 05/Oct/20 ]

Thanks for the confirmation. Then, we will, at the moment, continue using  "redshiftrange" [-0.001; 0.001],  "redshiftstep" 1.0e-6 for stellar analyses. 

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