[PIPE1D-28] Dummy output Created: 02/Oct/20 Updated: 26/Nov/20 Resolved: 26/Nov/20 |
|
| Status: | Done |
| Project: | DRP 1D pipeline |
| Component/s: | drp_1dpipe |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | Ali Allaoui | Assignee: | Ali Allaoui |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
When the input spectrum is not valid, an output must nevertheless be provided. What is the structure and the content of such an output (same number of hdu ? redshift value set to -99 ? same number of candidates ?) |
| Comments |
| Comment by Masayuki Tanaka [ 09/Oct/20 ] |
|
I ran the current pipeline and saw that it generates only the primary header with no HDUs. I think this is one way to write a dummy output; it does not have the full structure specified in the data model, but it is very clear that the pipeline did not successfully process the spectrum (and also we do not waste the disk space with nonsense numbers). But, let me check with the database people and ask what would be a good format for their work. I will get back to you next week. |
| Comment by Masayuki Tanaka [ 13/Oct/20 ] |
|
It seems the database people do not have a strong opinion. So, let's go ahead with the primary header only with no following HDUs. The current pipeline behaves this way and there is no need to update the pipeline. Please close this ticket if you agree.
|
| Comment by Pierre-Yves CHABAUD [ 13/Oct/20 ] |
|
Thank you Masayuki Tanaka for your prompt answer. |