-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #128 from TeaganKing/documentation
Config file documentation
- Loading branch information
Showing
9 changed files
with
38 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,3 +18,4 @@ externals/ | |
/docs/_build/ | ||
/docs/README.md | ||
/docs/NCAR_tips.md | ||
/docs/contributors.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# CUPiD Configuration File | ||
|
||
This page describes the fields in the configuration file that might commonly be edited. | ||
|
||
<img src="../../../images/config_1.png" alt="CUPiD Config 1" width=1000 /> | ||
The data sources section of the configuration file describes general data sources and expected directory structure for running CUPiD. | ||
|
||
`sname`: nickname for this configuration as a string. This will be used as the name of the folder your computed notebooks are put in | ||
|
||
<img src="../../../images/config_2.png" alt="CUPiD Config 2" width=1000 /> | ||
The computation config section of the configuration file supplies the default kernel for running CUPiD. This should usually be `cupid-analysis`. If a contributor wants to include additional packages, please create an issue describing the packages you'd like to add to this conda environment. | ||
|
||
|
||
<img src="../../../images/config_3.png" alt="CUPiD Config 3" width=1000 /> | ||
The above section of the configuration file describes 1) global parameters that are applicable to all notebooks and 2) timeseries-related parameters specific to each component. | ||
|
||
`case_name`: name of CESM case; this should also be a subdirectory of `CESM_output_dir`. | ||
|
||
`base_case_name`: name of CESM case to compare the specified case to. | ||
|
||
`CESM_output_dir`: directory where output from CESM is located. | ||
|
||
`start_date` and `end_date`: describe the time period over which we want to analyze output. | ||
|
||
`vars` for various components: variables which CUPiD will expect to find for various components and then make timeseries for. | ||
|
||
<img src="../../../images/config_4.png" alt="CUPiD Config 4" width=1000 /> | ||
The compute notebooks section of the configuration file describes the notebooks that will be computed as well as any parameters specific to those notebooks. | ||
|
||
`nmse_PSL`: This is the name of a notebook which is added to the atmospheric component diagnostics. | ||
|
||
`regridded_output`, `base_regridded_output`, `validation_path`, etc: These are parameters specific to the `nmse_PSL` notebook. If a contributor wants to include additional parameters specific to a notebook, we recommend following a similar format and changing variables names to represent the relevant quantities. | ||
|
||
<img src="../../../images/config_5.png" alt="CUPiD Config 5" width=1000 /> | ||
The Jupyter Book Table of Contents section of the configuration file describes the Juptyter Book configuration to display the output of the CUPiD diagnostics. Please include your notebook name within the files under `chapters`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.