Below are the liens for the following STEREO data set:
    STEREO-C-SECCHI-3-COMETIMAGES-V1.0

o The image names listed in the photometry dataset for four comets (c2007y5, 
  c2008k4, c2008l14, c2009d4) don't match those in the image dataset.
  These need to be investigated and corrected as needed.

o SBN (Raugh) offered programming help to generate a per-object summary of
  coverage (total number of images, #/instrument, #/filter, etc.).  Jian Yang
  can provide a list of fields from the labels that should be summarized.

o Helpful to have a table listing the number of available images for each comet.

file: 'catalog/dataset.cat'
--> Suggest adding SECCHI COR1 & HI2 to the abstract, in addition to or instead of the processing steps.
--> TIME inconsistencies:
--> --> START_TIME = 2007-01-30T08:08:12.467
--> --> STOP_TIME = 2010-01-03T10:54:16.009
--> --> But in abstract line 27: '... from 2006-2009.', also in line 215 it says 2007-2009, and line 252 says 2006-2009 again.
--> The ABSTARCT_DESC and DATA_SET_DESC mentions that there is data from 2006 thru 2009, but the START_TIME is 2007 and the STOP_TIME is 2010-01.  Likewise there are only data directories for 2007 thru 2009.
--> --> Note that the one data file with a date of 2010 is the end date for a file that begins in 2009.
--> line 49: '...following families...', but then only one family is listed
--> lines 68-73: Formatting issue with first table in Data Set Overview: column 1 is in column 2 for some rows.
--> Line 77: White light here, but secchiinst.cat states both instruments have filters?
--> Line 95: "HI2 has observed a number of non-sungrazing comets due to its extremely large field of view, but thus far has only observed two sungrazing comets (C/2011 W3 Lovejoy and C/2012 S1 ISON) due to its large solar elongation." -> "HI2 has observed a number of non-sungrazing comets due to its large field of view and large solar elongation, but thus far has only observed two sungrazing comets (C/2011 W3 Lovejoy and C/2012 S1 ISON)."
--> Line 125: First instance of HI1A, HI1B but the A/B designations have not been introduced.  Add above a quick note that explains there are two spacecraft and their naming conventions.
--> Line 135: Define MSB acronym.
--> Line 136: typo somet
--> Line 137: "(or [some] other less variable image)"
--> Line 137: "less variable" is not immediately clear.  Revise, or consider removing as this parenthetical does not appear critical. "rather than creating, e.g., a daily median because ..."
--> Line 144: Quantify the success of this background subtraction method?
--> Line 160: Possible to provide reference, SIS, etc about imaging mode? Or point out it is irrelevant to this dataset.
--> Line 169: For completeness, which R-band does NOMAD use?
--> Line 177: Cite the instrument catalog file for details on the pixel angular scales?  Aperture radii are listed as "~350 arcsec" and "~103 arcsec".  File states COR2 is 14.7"/pix, 7 * 14.7 = 103".  File states HI1 is 35"/pix, 5 * 35 * 2 = 350".  Please remove the "~" characters if these are correct.
--> Line 177-178: "The aperture radius was 5 pixels (~350 arcsec) for HI1 and 7 pixels (~103 arcsec) for COR2." Is photometric aperture size relevant here?
--> Line 205: Restate the sentence as an absolute uncertainty on the calibration constants, e.g., "The absolute calibration uncertainty is estimated to be XXX mag, 1-sigma confidence level."  Moreover, these calibration factors assume star-like spectra.  Is this OK and is there a reference for more discussion?
--> Line 218: final DD should be SS?
--> Lines 220+ says, regarding the file naming convention:
--> --> ... TEL is an abbreviation for the telescope used (h1A = HI1A, h1B = HI1B, c2A = COR2A, and c2B = COR2B)... The actual files have h1a, h1b, c2a, c2b (i.e. entirely lower case)
--> Line 229: "Each processed *.FIT file has a detached PDS label (*.LBL) file which contains information about the image in standard FITS keywords."  This is a strange sentence for this document since the PDS label should contain information about the image in standard PDS3 keywords.  I suggest ending the sentence at "file" or "(*.LBL)".
--> Line 248: "such as some HI1 documentation available in copyrighted publications."  Instead, please cite relevant references (be specific rather than obscure).
--> Line 250: Move this paragraph to the top of the Data section.
--> Line 256: "Future updates" I don't think there is a need to discuss future data.  Just state what is in this data set.  Alternatively, you can state what is not in the data set, but there is no need to make statements about what might be because it may never occur.
--> Line 260: "A parallel dataset containing photometric measurements for all the comets in this archived is being submitted concurrently."  When the data set(s) is certified/accepted, this sentence will immediately become obsolete.  Remove it or cite the actual data set (use "in preparation", if necessary).
--> The CONFIDENCE_LEVEL_NOTE is effectively empty.  This should contain information about error estimates, completeness, and such as appropriate.
--> In the CONFIDENCE_LEVEL_NOTE, indicate that some Kreutz comets could not be included, and why.

file: 'catalog/secchiinst.cat'
--> The INSTRUMENT_TYPE = "IMAGING TELESCOPES" should be changed to "IMAGER".
--> line 174: Change "[WRAIGHETAL2011]" to "[WRAIGHTETAL2011]".  The first "T" in "WRAIGHT" is missing.

file: 'data/*/*.fit'
--> Why XMAX-XMIN = 11 not 40? Also for YMAX-YMIN.
--> --> example: data/2008/2008c6/2008c6_h1a_20080207_084901.fit

files: 'data/2008/2008c6/*.fit'
--> 2008c6 images: blank strip in two images, why?

directory: 'data/calib/'
--> Should this directory be at the root of the data set?

directory: 'document/'
--> All of the calib files should be moved to a calib directory at the root of the data set.

files: 'document/*/*.lbl'
--> The ^DOCUMENT link should be changed from "[DIRECTORY]/[FILENAME]" to "[FILENAME]".  This is due to the fact that the label and data file exist in the same directory.  
--> --> Example for 'document/filt_trans/filttrans.lbl' line 5: The ^DOCUMENT link should be changed from "filt_trans/cor_trans.png" to "cor_trans.png".

file: 'document/comet_elements.lbl'
--> line 3: The DATA_SET_ID should be "V1.0" not "V2.0".

file: 'document/docinfo.txt'
--> Revise entry for comet_elements.asc: This table also includes instruments observed each comet.
--> Some files are not listed with their directories, but their labels do include the directory.  Please add complete paths to all listed files.

file: 'NOTES/introdoc.pdf'
--> Some of this text (especially the first paragraph) would have been great in the dataset.cat!
--> Please more briefly summarize what is essential.  Details should be left to the archive.  For example, at this point, we don't need to know that the 'secchi_prep' routine was used.  Data processing could probably be stated in two sentences, but is it even relevant for the photometry data set?  I think the data format and processing of the other data set should be taken for granted in this latter case.
--> Is the background removal technique relevant in an intro document?
--> 'Reading the Data' contains details on data production.  File naming conventions is definitely appropriate, though.
--> References to FITS files, but no FITS files.

file: 'voldesc.cat'
--> Remove all ^TARGET_CATALOG files that do not exist in 'catalog/targets/'.

   
 Last updated: 2015-01-13, SBN:T.Barnes