SDSP_0001
=========

- Version 1.0 of this data set, covering the cruise and AnneFrank phases 
  of the mission, was submitted to SBN and reviewed in 2003.  This 
  enhanced data set is also identified as Version 1.0 but should be
  Version 2.0.  Change all occurrences of DATA_SET_ID to
  "SDU-C-SPICE-6-V2.0".  Change all occurrences of VOLUME_VERSION_ID
  to "VERSION 2".

- The are many NAVCAM frames.  Which frame was used to generate 
  pointing/geometry information in the Navcam Wild 2 data set?  

  Also, which other SPICE kernels were used to calculate pointing/
  geometry information?  This note is applicable to nearly all
  of the Stardust data sets.

  Similarly, what versions of SPICE kernels were used for the
  archived Stardust NAVCAM data from the AnneFrank encounter?


catalog
-------

spiceds.cat

- In the 'Loading Kernel Files...' section, the '(note that the
  logical path...)' clause is garbled.

- In the 'SPK Files' section, the last 2 sentences appear to
  be a caution.  Consider putting these 2 sentences in a new
  'Caution on Using SPK Files' section. 

- In the 'CK Files: Spacecraft Bus CK Files' section, change
  'and send down...' to 'and sent down...'.

- In the 'CK Files' section, make it clear that the NAVCAM
  CKs contain discrete data and one should use the spacecraft clock
  time, not the UTC, found in the PDS labels when calling SPICE
  routines.  

  Per Boris, NAVCAM CKs were "generated by taking SCLK-tagged mirror 
  angles from image headers, turning them into appropriate rotations, 
  and packaging these rotations into a type 1 (discrete) CK, which stores 
  these SCLK tags 'as is'.  So if you start with the same SCLK as originally 
  went into production,  you get the data even if time correlation has 
  changed.  If you start with UTC which may have been done with other 
  correlation (not the case for NAVCAM index) or was round off a bit 
  (is the case for NAVCAM tags), you may miss CK data by just a bit ...
  which is enough for SPICE to complain."


data/fk and /ck 
---------------

- There are no body-fixed frames for AnneFrane or Wild 2 targets
  with accompanying /pck files.  Per Boris, now that we have some 
  papers on the target orientation and possibly some target body-fixed 
  frames (for Wild 2?), it may be time to add body-fixed frames and
  pck files to the Stardust SPICE data set.  However, NAIF will
  need guidance from the science community.

sdu_v17.tf 

 - The 'Usage Notes' section states that one can compute the 
   transformation matrix from the Navcam image frame to the 
   J2000 frame by loading the "ideal/opnav correction" CK files 
   and calling sxform:
       sxform('SDU_NC_IMAGE_OPNAV', 'J2000', ET, XFORM) 
   or by loading the Navcam mirror "real alignment"
       sxform('SDU_NC_IMAGE', 'J2000', ET, XFORM)

   1) Add a note that one must calculate the ephemeris time (ET)
      from the spacecraft clock time at the start of an image
      exposure (found in the data labels) for this transformation 
      to work.  Do not use use the UTC (also found in the data
      labels).  

   2) It is not clear which CK files contain "ideal/opnav correction"
      or "real alignment" information
 
 - Per Boris, consider adding the following mapping keywords:

     NAIF_BODY_NAME  += ( 'WILD2'                    )
     NAIF_BODY_CODE  += ( 1000107                    )
     NAIF_BODY_NAME  += ( '81P/WILD 2 (1978 A2)'     )
     NAIF_BODY_CODE  += ( 1000107                    )
     NAIF_BODY_NAME  += ( 'ANNEFRANK'                )
     NAIF_BODY_CODE  += ( 2005535                    )
     NAIF_BODY_NAME  += ( '5535 ANNEFRANK'           )
     NAIF_BODY_CODE  += ( 2005535                    )


data/ik
-------

sdu_navcam_v21.ti

 - In the 'CCD Characteristics' section, replace question marks 
   in units strings for 'Full well', 'Dark current' with the 
   appropriate units.

To do: Check remaining instrument kernels; may have similar
  units problem


data/sclk
---------

sdu_sclkscet_00105.tsc

 - In the 'SCLKvSCET file SDFU Header' section, is the value 
   for SPACECRAFT-ID, 29, correct?  The NAIF s/c ID is -29.

 - What is the correct format for a s/c clock time string?  In the
   index.tab file for the NAVCAM Wild 2 data set, the format is
   '0757539099:037' but the NAIF Tutorial 'Leapseconds and Spacecraft
   Clock Kernels' says the format is '0757539099.037' for Stardust.  
   Using different delimiters is confusing.

