Last updated: 3/15/2016, through Amendment 1.
Step-1 Proposal due date: 4/6/2016
Step-2 Proposal due date: 6/16/2016
Data Availability date: 5/17/2016
The Cassini Data Analysis Program (CDAP) is described in Appendix C.10 of the ROSES 2016 NRA.
The full document, including amendments, can be accessed under Solicitations at the NSPIRES web site.
The scope of this Program has been clarified and slightly modified in ROSES-2016. Proposers are expected to carefully read the solicitation and should E-mail the program point of contact with any questions sufficiently ahead of the Step-1 proposal deadline.
Spacecraft mission data to be used in proposed work must be available in the Planetary Data System (PDS) or an equivalent, publicly accessible archive, at least 30 days prior to the full proposal submission deadline.
For volumes at the Ring-Moon Systems Node which meet the CDAP basic eligibility requirements for publicly available timing (based on the Step 2 Proposal due date), see the Data Status tab.
OPUS, our Outer Planets Unified Search tool, allows users to search for and obtain subsets of data based on a wide range of constraints. OPUS supports Saturn system data obtained by Cassini CIRS prior to July 2010, and all Saturn system observations currently available in PDS obtained by Cassini ISS, UVIS and VIMS, as well as data sets obtained by other missions including Voyager. Search results include preview images for all observations.
For Cassini ISS, UVIS, and VIMS, the OPUS search parameters are based on enhanced geometric metadata generated at the Ring-Moon Systems Node, and include constraints relating to the surfaces of the planet and satellites as well as to the rings.
Our Cassini information pages provide:
SPICE data and software may be obtained from the NAIF web site.SPICE data files contain spacecraft and solar system geometry data necessary to interpret scientific observations from space-based instruments. The SPICE system also includes a large suite of software, mostly in the form of subroutines, that users incorporate in their own application programs to read SPICE files and to compute derived observation geometry, such as altitude, latitude/longitude, and lighting angles.
Proposed data products for delivery to the PDS should be clearly described, and the proposer should consult with the manager of the appropriate PDS data node to insure that they will be PDS compliant and constructed as efficiently as possible.
Requirements for depositing derived data products in the Planetary Data System have been revised to require that all products be PDS4 conformant. Guidelines for planning data in this format are available at Archiving under PDS4.