| Discovery Data Analysis Program (DDAP) | |
| The ROSES 2014 Discovery Data Analysis Program (DDAP) Appendix C.11, notes: | |
| Amended on February 25, 2014. This amendment changes the name of C.11 from Planetary Mission Data Analysis Program (PMDAP) to the Discovery Data Analysis Program (DDAP) | |
 | |
| 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.
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 a vailable 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. 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 PDS 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. The DDAP is not intended to overlap other active data analysis or core research and analysis programs. Therefore, the DDAP does not support the analysis of: Mars data obtained by missions to Mars (see the Mars Data Analysis Program (MDAP)), Data from Cassini (see the Cassini Data Analysis Program (CDAPS)), or Lunar data (see the Lunar Data Analysis Program (LDAP)). | |
| A Step-1 proposal is required and must be submitted electronically by the Authorized Organizational Representative (AOR). No budget is required. Only proposers who submit a Step-1 proposal are eligible to submit a Step-2 proposal. Full (Step-2) proposals must broadly contain the same scientific goals proposed in the Step-1 proposal. The Step-1 proposal title and Principal Investigator cannot be adjusted.To add funded investigators between the Step-1 and Step-2 proposals proposers should write to the point(s) of contact below and cc sara@nasa.gov at least two weeks in advance of the Step-2 due date. NASA intends to respond within two working days. Submission of the Step-1 proposal does not obligate the proposer to submit a Step-2 (full) proposal later. |
| Critical Dates | ||
| Step 1 Proposal Due Date | Data Included in PDS by | Step 2 Proposal Due Date |
| 07-21-14 | 08-20-14 | 09-19-14 |
| ||
| Mission data are available from the Planetary Data System (PDS). | |||
| |||
| Data Available at PPI | |||
| Mission | |||
|---|---|---|---|
| MESSENGER | NEAR | ||
| Lunar Prospector | |||
| |||
| Other Data Within PDS | |
| The following Discipline Nodes have additional information (may be in lien resolution): | |
|
Atmospheres Node Imaging Node Geosciences Node Small Bodies Node | |
| |
| Ancillary data (SPICE files) can be obtained from the NAIF Node | |
 |
Privacy / Copyright Freedom of Information Act |
 |
Web Master: PDS-PPI Operator Nasa Official: William Knopf Last Updated: Febuary 2009 |