The CAMEL framework is an integrated and flexible framework allowing users to seamlessly compare space weather and space science model outputs with observational data sets.
The backend of the CAMEL framework takes advantage of Community Coordinated Modeling Center (CCMC) existing services.
The front-end interactive visualization tool (i.e. CAMEL Web App) powered by the backend infrastructure allows users to plot model outputs and observation data sets together while providing options to calculate various skill scores from our library of skill scores.
In addition to using the CAMEL interactive visualization tool, the CAMEL framework provides a webservice interface or an Application Programming Interface (API) allowing users to download "approved data sets/output" available on the CAMEL backend database into their own environment. **Note: approved data sets/output = the original owner/curator of the data sets/output gives full permission to the CCMC to share and redistribute the data sets/output.
Public Code/Data Repository
As of August 2023, the CAMEL Validation Skill Scores Library code is approved to be an official NASA Open-Source project.
To download and/or contribute to the code, please visit the NASA official code repository for the project: https://github.com/nasa/camel.
In addition, "approved data and output files" ingested into CAMEL are publicly accessible via this public GitLab repo.
List of Validation Campaigns on CAMEL
Instructions to Provide Data to CAMEL
Before providing your data files to us, please review the following information:
In order to ingest data for your validation study into the CAMEL framework, metadata about your study as well as your data sets are needed.
Currently, CAMEL can only ingest 1-D time-series data. The expected format for data files are ASCII/TEXT files with date/time and parameters in separate columns (see example file [TEXT File]).
Note: It will be helpful to go to the CAMEL Web App to see other validation studies that are available on our system now. Let us know if your data sets should go under an existing validation study or a new one should be created for you.
Required Metadata Information
Please send an email request to the CAMEL team with the following information:
- Which Domain does your validation study fit in? (e.g. Solar, Heliosphere, Magnetosphere, Ionosphere, Thermosphere, Space Radiation and Plasma Effects, etc.)
- What Topic does your validation study fit in? (Surfacing Charging in near-earth region, Solar Wind Parameters, Total Electron Content, etc.)
- What is the location for your study? (e.g. L1) Note: your validation study name would be the combination of topic and location (ex: TEC at Boulder)
- Is this a specific event study? If so, please provide your event name, start date in UTC, end date in UTC, and Description.
- What are the parameters for your validation study? For each parameter, please provide the parameter name, description, and units.
Data Files Upload Instructions
Please contact the CAMEL team if you are interested in providing/uploading data files to be ingested into CAMEL for a validation study.
All "approved data and output files" ingested into CAMEL are publicly accessible via this public GitLab repo.
Expected/Recommended File Format: ASCII/text file with date, time, parameters, and location/instrument in separate columns (see example file [TEXT File]).
- L. Rastaetter, C. Wiegand, R. Mullinix (2019), Comprehensive Assessment of Models and Events using Library Tools (CAMEL) framework: Time series comparisons, Space Weather, DOI: 10.1029/2018SW002043.
For tracking purposes for our government sponsors, we ask that you notify the CCMC whenever you use any CCMC tools/software systems in any scientific publications and/or presentations. Follow the steps on the publication submission page
See our full publication policy for a sample 'acknowledgement statement' to be included in your publication.
Please also follow and acknowledge the owner/generator/curator of the original data sets/output by adhering to their rules of the road, licenses, and/or data policy whenever applicable.