Difference: HPDPDefinitionPage (12 vs. 13)

Revision 132015-09-15 - ElenaPuga

Line: 1 to 1
 
META TOPICPARENT name="HSC.WebHome"

Herschel Highly Processed Data Product Page

Line: 43 to 43
 In order of priority: these first are HPDPs

HPDP name Description Data Catalogue (tables) Images (PNGs, etc) Documentation (Readme, QSummary, etc) Notes Prototype delivery
Deleted:
<
<
High flux source data Very bright sources ought to be reduced with a difference pipeline script (to account for non-linearity/self-curing) Yes - level2/2.5 equivalent FITS files No Yes   Some level of manual reduction may be necessary, but are probably not many such observations  
Unchopped observations: response drifts - case 1 Unchopped range scans severely affected by response drift (e.g. after high glitch rate or after high-flux source observation) Yes - level2/2.5 equivalent FITS files No Yes   Highly desirable  
Unchopped observations: transients - case 1 Baseline-subtracted unchopped spectra Yes - level2/2.5 equivalent FITS files No Yes   Desirable, if case 2 is not possible this becomes Highly desirable  
Unchopped observations: transients - case 2 Improved transient correction and background subtraction Yes - level2/2.5 equivalent FITS files No Yes   Highly desirable, if it is possible to do this is preferred over case 1  
 
Point-source calibrated data - case 1 For off-centred sources that are likely to be point sources: SPG products processed through the standard pipeline script with non-standard extraction of final PS spectrum Yes - level2/2.5 equivalent FITS files No Yes   A useful possibility, feasibility will be more clear once QC work on off-centred observations and identification of likely centred point sources has been done  
Added:
>
>
High flux source data Very bright sources ought to be reduced with a difference pipeline script (to account for non-linearity/self-curing) Yes - level2/2.5 equivalent FITS files No Yes To be proposed for 14.1 SPG Some level of manual reduction may be necessary, but are probably not many such observations  
Unchopped observations: response drifts - case 1 Unchopped range scans severely affected by response drift (e.g. after high glitch rate or after high-flux source observation) Yes - level2/2.5 equivalent FITS files No Yes To be proposed for 14.1 SPG Highly desirable  
Unchopped observations: transients - case 1 Baseline-subtracted unchopped spectra Yes - level2/2.5 equivalent FITS files No Yes   Desirable, if case 2 is not possible this becomes Highly desirable  
Unchopped observations: transients - case 2 Improved transient correction and background subtraction Yes - level2/2.5 equivalent FITS files No Yes To be proposed for 14.1 SPG Highly desirable, if it is possible to do this is preferred over case 1  
Identifying background contamination ChopNod and Unchopped, Line (and continuum?) Yes - level2/2.5 equivalent FITS files No Yes   HPDP, but depends on how possible it will be to identify these and how many we find  
Line list catalogue Spectral Feature catalogue No Yes - one file per obsid, and one concatenated file No   HPDP: dependent on available human resources, would be completely HSC to decide we want to do this as is not on ICC plans  
 
Changed:
<
<
In order of priority: these should be SPG or are of lower priority HPDPs
>
>
These should be SPG:
 
HPDP name Description Data Catalogue (tables) Images (PNGs, etc) Documentation (Readme, QSummary, etc) Notes Prototype delivery
Changed:
<
<
Point-source calibrated data - case 2 SPG products processed through the dedicated point-source correction script for sources consistent with being centred point source Yes - level2/2.5 equivalent FITS files No Yes   SPG: straightforward to do once the pipeline script has been fully validated and sources identified; validation is on-going  
>
>
Point-source calibrated data - case 2 SPG products processed through the dedicated pointing offset correction script for sources consistent with being centred point source Yes - level2/2.5 equivalent FITS files No Yes   SPG: straightforward to do once the pipeline script has been fully validated and sources identified; validation is on-going  
 
Point-source calibrated data - case 3 SPG products processed through the standard pipeline script for sources consistent with being centred point sources Yes - level2/2.5 equivalent FITS files No Yes   SPG  
Long range spectro flat-fielding - main Including flatfielding for range scans in the SPG Yes - level2/2.5 equivalent FITS files No Yes   SPG  
Changed:
<
<
Long range spectro flat-fielding - potential Correcting the few cases of bad flatfielding Yes - level2/2.5 equivalent FITS files No Yes   HPDP or SPG, depends on whether/how many of these will be present after the final SPG  
>
>
Long range spectro flat-fielding - potential Correcting the few cases of bad flatfielding (probably unnecessary) Yes - level2/2.5 equivalent FITS files No Yes   HPDP or SPG, depends on whether/how many of these will be present after the final SPG  
 
Red leak spectral range Run the specific pipeline that deals with red leak region (CalBlock+RSRF) and provide data stand-alone Yes - level2 equivalent FITS files No Yes   SPG  
Repair of failed observations Re-run pipeline on observations set to failed Yes - level2/2.5 equivalent FITS files No Yes   Observations that are classed as failed but which will now run in SPG are easy to do and could become standard SPG, for others that require manual reduction they could also become the standard SPG, probably not difficult  
Deleted:
<
<
Removing background contamination Line (and continuum?) Yes - level2/2.5 equivalent FITS files No Yes   HPDP, but depends on how possible it will be to identify these and how many we find, would be manual reduction and differently for chopNod and unchopped  
Line list catalogue Spectral Feature catalogue No Yes - one file per obsid, and one concatenated file No   HPDP: dependent on available human resources, would be completely HSC to decide we want to do this as is not on ICC plans  
 

SPIRE-P

 
This site is powered by the TWiki collaboration platform Powered by Perl