12.07.2015 Views

interface control document (icd) - the Planetary Data System

interface control document (icd) - the Planetary Data System

interface control document (icd) - the Planetary Data System

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MRO CRISM – PDS Geosciences Node ICD Version 1.1 January 25, 2005Oversight of <strong>the</strong> archiving process will be provided by <strong>the</strong> MRO <strong>Data</strong> and ArchivesWorking Group (DARWG). A subgroup of <strong>the</strong> MRO Project Science Group, <strong>the</strong>DARWG coordinates <strong>the</strong> planning, generation, validation, and delivery of all MROarchives. The DARWG meets regularly by teleconference during <strong>the</strong> archive planningperiod and as needed during mission operations. Representatives of <strong>the</strong> CRISM Teamand Geosciences Node will attend <strong>Data</strong> and Archives Working Group meetings andreport progress.3. RESPONSIBILITIES OF CRISM SCIENCE TEAM3.1 CRISM Science <strong>Data</strong> ArchivesThe CRISM Team is responsible for writing <strong>the</strong> CRISM Standard <strong>Data</strong> Product SIS, withhelp from <strong>the</strong> Geosciences Node as needed.The CRISM Team is responsible for writing instrument and data set descriptions for <strong>the</strong>PDS catalog in <strong>the</strong> format specified in <strong>the</strong> PDS Standards Reference, with help from <strong>the</strong>Geosciences Node as needed.The CRISM Team is responsible for performing science validation on CRISM dataproducts.The CRISM Team will deliver science data products to <strong>the</strong> Geosciences Node accordingto <strong>the</strong> schedule in <strong>the</strong> MRO Archive Plan. <strong>Data</strong> will be transferred on hard media such asexternal hard disks, provided by <strong>the</strong> CRISM team.The CRISM Team will deliver relevant calibration reports and files needed for datacalibration to <strong>the</strong> Geosciences Node.The CRISM Team will deliver to <strong>the</strong> Geosciences Node IDL software to ingest targetedRDR products and produce map-projected spectral reflectance products. Software shouldinclude source code and <strong>document</strong>ation and should be delivered as one or more Zipcompressedfiles.The CRISM Team is responsible for delivering to <strong>the</strong> Geosciences Node any additional<strong>document</strong>ation <strong>the</strong>y want to include in <strong>the</strong> archive. Documentation files should be inei<strong>the</strong>r plain text or HTML format to be PDS-compliant. O<strong>the</strong>r versions such as AdobePDF may also be included at <strong>the</strong> Team's discretion.The CRISM Team is responsible for providing samples of all data products and productlabels as described in <strong>the</strong> Standard <strong>Data</strong> Product SIS for <strong>the</strong> PDS-required peer review.The Team is also responsible for resolving any liens that may be placed against CRISMscience data sets as a result of <strong>the</strong> peer review, with help from <strong>the</strong> Geosciences Node asneeded.3.2 CRISM Spectral LibraryThe CRISM Team is responsible for providing data sets for <strong>the</strong> Spectral Library alongwith <strong>the</strong> supporting information required by PDS, specifically PDS data labels and dataset and instrument <strong>document</strong>ation files for <strong>the</strong> PDS catalog.2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!