| Discovery Data Analysis Program (DDAP) | ||
| The ROSES 2016 Discovery Data Analysis Program (DDAP) Appendix C.11 | ||
| NOTICE: The research solicitation was amended on March 10, 2016. This program element has been modified to permit proposals for work on Kepler/K2 observations of solar system targets. | ||
 | ||
| The research solicitation states: | ||
| The objective of the Discovery Data Analysis Program (DDAP) is to enhance the scientific return of Discovery Program missions by broadening the scientific participation in the analysis of data, both recent and archived, collected by Discovery missions. | ||
| The following is a list of Discovery Missions or Discovery Missions of Opportunity for which archived data is available: NEAR, Stardust, Genesis, Deep Impact, MESSENGER, Dawn, Kepler/K2, EPOXI and Stardust-NExT. | ||
| Note that DDAP investigations using Kepler/K2 data are limited to those using observations of Solar System objects. | ||
| ||
| Critical Dates | ||
| Step 1 Proposal Due Date | Data Included in PDS by | Step 2 Proposal Due Date |
| 09/08/16 | 10/18/16 | 11/17/16 |
| ||
| Mission data are available from the Planetary Data System (PDS). | |||
| |||
| Data Available at PPI | |||
| Mission | |||
|---|---|---|---|
| MESSENGER | NEAR | ||
| |||
| Other Data Within PDS | |
| The following Discipline Nodes have additional information (may be in lien resolution): | |
|
Atmospheres Node Cartography and Imaging Sciences Node Geosciences Node Small Bodies Node | |
| |
| Ancillary data (SPICE files) can be obtained from the NAIF Node | |
| |
| The DDAP supports investigations that use only data available in the Planetary Data System (PDS) or equivalent publicly accessible archive(s). The data must be archived and publicly available 30 days prior to the submission deadline for DDAP proposals. Spacecraft data that have not been placed in such archives are not eligible for use in DDAP investigations. In all cases, it is the responsibility of the DDAP investigator to acquire any necessary data. Investigators are encouraged to contact the archive for assistance in identifying specifics of available datasets. Datasets to be used in the proposed work must be clearly and specifically identified in the proposal. Regardless of the archive(s) used, if the data to be analyzed have known issues that might represent an obstacle to analysis, the proposers must demonstrate clearly and satisfactorily how such potential difficulties will be overcome. | |
| This Program Element uses a two-step proposal submission process described in Appendix C.1, section 2. | |
| Data products produced by funded DDAP investigations must be archived in the Planetary Data System. When proposing the archiving of products into the PDS, an archive plan must be included, identifying schedule and budget to go through the PDS ingestion process. Data products should be submitted to the PDS by the end of the funded research period, unless the investigator explicitly makes a case in the proposal for a later date. For more information, please contact the Planetary Data System(http://pds.nasa.gov/). This requirement supersedes the general requirement found in Appendix C.1. | |
| It is the responsibility of the proposers to DDAP to specifically identify any needed mission data and to ascertain that those data are publically available. Proposals dealing with mission data should provide convincing evidence that the data have sufficient quality and are available in sufficient quantity to achieve the goals set forth in the proposal. The proposer should demonstrate a familiarity with the data and an understanding of the work required to refine the data for the purposes of the analysis. | |
 |
Privacy / Copyright Freedom of Information Act |
 |
Web Master: PDS-PPI Operator Nasa Official: William Knopf Last Updated: Febuary 2009 |