Volume 1 (written by SDC)
- Purpose of this Document: This MMS-SMART Science Data Products Guide is intended to provide the general science community an explanation of the essential details for working with MMS-SMART data. It includes descriptions of the MMS-SMART instrumentation, science algorithms, data products, and data access.
- Applicable documents
- Contributing authors
2. Mission Background
This should be pretty easy to put together from available documents. Section 2 of the PDMP has a short summary that I pulled together. That was intended for an internal audience that’s already familiar with MMS though so for the Data Products Guide, the Background section should probably cover more depth. The report, “Resolving Fundamental Processes in Space Plasmas” has too much info but it should serve as a good resource. Someone in the evolving Data Products Guide group will probably have a good idea of an existing resource that may be a better fit.
- Science objectives
- Mission phases
3. Science Data Overview
- Data collection strategy – this has evolved over the past few years and will need some explanation. The Burst Algorithms Definition and Concept of Operations document (BADCO) provides an overly thorough description but Section 2, in particular, provides relevant background for this section.
- Survey data
- Burst data
- Description of distributed processing system – See Sections 3 and 5 of the PDMP
- c. Conventions (e.g. file names, file organization, status bytes, time, etc) – Will eventually be described in the MMS CDF File Format Guide. I’m working on that document and I’m hopeful that conventions will be pretty well fleshed out at some point in the Spring. Currently, the only real conventions are the file naming convention (Sec. 3.1) and the variable naming convention (Sec. 5.1.1).
- Data products
- Description of data product levels – See Section 4 of the PDMP
- Science parameters
- Tables organized by instrument: - These are summaries of what the instrument teams provide in their volumes. It would probably be worth requiring the instrument teams to provide summaries for you.
- Parameter names
- Description of each parameter
- Units for each parameter
- Size in bytes for each parameter – I’m not sure if the instrument teams will be able to provide this level of detail before April. Maybe but it’s possible they won’t have this kind of detail for another year. They should be able to provide everything else for this section now.
- Description of versioning system (e.g. what constitutes new versions, new revisions and how are new releases coordinated) – This is being worked now and I should be able to provide info in February.
- Change notification (e.g. email, RSS, website, etc) – This info exists in SOC requirements but isn’t described in prose anywhere. At some point, we can have a discussion on this topic and you should be able to write the section from there.
- Rules of use – The Heliophysics Data Policy has a “Rules of the Road” in Appendix A. I don’t think we want to cite that directly but I’m not sure of that. It’s probably worth looking at what related programs have done for their “Rules of use.” Take a look at data download sites for THEMIS, RBSP, and JUNO.
- Analysis tools
- What to look for in the data – this will need to come from the instrument teams. Let’s make sure they have a section like this and then you can summarize and/or refer the reader to each investigation’s suggestions.
- Descriptions of tools that will be available – A tool called Autoplot (http://autoplot.org/) is our baseline tool for data access and visualization. Some of the instrument will also be providing their own analysis tools, which should be summarized here.
4. Ancillary Data
- Coordinate systems – we’re planning to begin discussions with the instrument teams about various coordinate systems needed for science analysis in January. It might be useful for you to sit in on a few of those.
- Parameters (e.g. position, velocity, attitude, constellation geometry, status bytes, etc)
5. Data Access
- Where to get data (e.g. SOC, VxO, SPDF?)
- Data product release schedule
- MMS related websites (e.g. SOC, EPO, ITFs, MMS main, etc)
- Summary plot keys?
Volumes 2+ (one volume per investigation as described below)
Overview of investigation, instruments, retrieved parameters, etc.
- Science background
- Level-2 science requirements
- Instrument characteristics (high level "how it works" including design and operations)
3. Data Products
- Descriptions of Quicklook products
- Descriptions of Level-2 products
- Error analysis
- Constraints, limitations, assumptions
- Science parameters (including parameter names, description of each, units, size in bytes) – ITFs should be able to do a pretty good job here with the caveat that it will almost certainly need to be updated next Fall
- Status bytes – it's not likely this will be known until next Fall
- Confidence in measurements
- Comparison of other measurements
- Validation of data against models
- Quality control and diagnostics
- Data analysis and visualization - suggested techniques
- What to look for in the data
- Description of needs for each data product
- Description of what will be provided
- Documentation (e.g. release notes, user guides)