Difference: HPDPDefinitionPage (16 vs. 17)

Revision 172015-09-16 - KatrinaExter

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

Herschel Highly Processed Data Product Page

Line: 40 to 40
 

PACS-S

Changed:
<
<
In order of priority: these first are HPDPs
>
>
In order of priority/doability:
 
HPDP name Description Data Catalogue (tables) Images (PNGs, etc) Documentation (Readme, QSummary, etc) Notes Prototype delivery
Changed:
<
<
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  
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  
Point-source calibrated data - case 2 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   straightforward to do once the pipeline script has been fully validated and sources identified; validation is on-going but not guaranteed  
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  
>
>
Pipeline processing bright sources 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 at a minimum, or entire obsContext if done via SPG No Yes To be proposed for 14.1 SPG rather than provide as an HPDP Some level of manual reduction may be necessary, but are probably not many such observations  
Point-source calibrated data For off-centred 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 (http://herschel.esac.esa.int/twiki/bin/view/Pacs/QualityCommentsSpec) on off-centred observations and identification of likely centred point sources has been done  
Long range spectrometer flat-fielding - potential Correcting the few cases of bad flatfielding Yes - level2/2.5 equivalent FITS files No Yes   may be unnecessary if the new range scan flatfielding works well  
Unchopped observations: pipeline processing with new response drifts correction Improved transient correction and background subtraction as provided by the new NHSC pipeline scripts Yes - level2/2.5 equivalent FITS files, or entire obsContext if done via SPG No Yes To be proposed for 14.1 SPG rather than provide as HPSP Highly desirable, but requires a fuller validation of this script first (if the script does not provide improved results, neither SPG nor HPDP can be created here)  
Unchopped observations: subtracting the baseline If the continuum in these AOTs cannot be improved (wrt absolute level and shape, less wrt SNR) then instead subtract the baseline Yes - level2/2.5 equivalent FITS files: baseline subtracted cubes/spectra and cubes of the baseline that was subtracted No Yes   Desirable, necessary if the new transients correction pipeline does not becomes SPG in 14.1  
Unchopped observations: manual processing to correct very bad transients Improved transient correction and background subtraction provided by processing the data manually Yes - level2/2.5 equivalent FITS files No Yes   Highly desirable, but depends on how many such observations there are and on progress on PACS-6462  
Point-source calibrated data using the "POC" script products processed through the dedicated pointing offset correction script for bright point sources Yes - level2/2.5 equivalent FITS files No Yes   straightforward to do once the pipeline script has been fully validated and sources identified; validation is on-going (but not guaranteed to finish)  
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 do, exploratory studies are being done with help of MSc students at ESAC and Leuven and we should know better early in 2016  
Identifying background contamination; removing it? For ChopNod and Unchopped AOTs, looking at line (and continuum?) contamination in the off positions: primarily to make a quality comment, but if the number is manageable then also to correct for the contamination Yes - level2/2.5 equivalent FITS files No Yes   HPDP, for the quality comment part the ICC have agreed to do this, but for the subtraction part it would have to be done at HSC (note: unlikely to ever actually be completed, however, due to it being a difficult job)  
 
Changed:
<
<
These should be SPG:
>
>
These should actually be SPG (14 or 14.1):
 
HPDP name Description Data Catalogue (tables) Images (PNGs, etc) Documentation (Readme, QSummary, etc) Notes Prototype delivery
Changed:
<
<
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  
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  
>
>
Point-source calibrated data (pointed AOTs only) SPG products processed through the standard pipeline script and then creating point source spectra from them Yes, part of SPG obsContext No Yes   Note: is done on all pointed AOTs, regardless of whether the source is know to be a point or not  
Long range spectrometer flat-fielding - main Including flatfielding for range scans in the SPG Yes, entire obsContext No Yes   depends on validation in AAT 14 but is looking good  
Red leak spectral range Run the specific pipeline that deals with red leak region (CalBlock+RSRF) and provide data stand-alone Yes, part of entire obsContext No Yes   Hoping for 14, but more likely to be 14.1  
Repair of failed observations Re-run pipeline on observations set to failed Yes, entire obsContext No Yes   Observations that are classed as failed or delivered for reprocessing will be processed in 14; of those that fail, for those that can none-the-less be processed manually and are worth so-doing  
 

SPIRE-P

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