Commit 1c67e238 authored by Carina Lansing's avatar Carina Lansing
Browse files

Tweaked the note box styles one more time so they are more noticeable.

parent ff0cbe6e
......@@ -36,10 +36,13 @@ Until then, LASSO-O will take a while to run depending upon the number of simula
you are processing. In addition, the first time you run the lasso-o_shcu container,
the container runtime will download the container image, which will also take a few minutes.
> ---
>
> **NOTE:**
> If you do not use a scheduler to invoke the script, it will run on the login node,
> which may be killed per host policy if it runs for too long.
>
> ---
When your job has completed, you may view the outputs created in the
`run-lasso-o_shcu/data/outputs` folder using the notebooks provided.
......
......@@ -39,9 +39,13 @@ Until then, LASSO-O will take a while to run depending upon the number of simula
you are processing. In addition, the first time you run the lasso-o_shcu container,
the container runtime will download the container image, which will also take a few minutes.
> ---
>
> **NOTE:**
> If you do not use a scheduler to invoke the script, it will run on the login node,
> which may be killed per host policy if it runs for too long.
>
> ---
When your job has completed, you may view the outputs created in the
......
......@@ -26,11 +26,14 @@ environment:
* [README-DOCKER.md](./README-DOCKER.md). Use these instructions if you are running from your local desktop. **NOTE: this should be used for small test runs only**
* [README-SINGULARITY.md](./README-SINGULARITY.md). Use these instructions if you have Singularity installed on your HPC cluster.
> ---
>
> **NOTE:**
> Some HPC clusters may require review/approval of container images before you
> are allowed to use them. If that is the case, admins can find more information
> about the lasso-o_shcu container image and how it was built from the [GitLab repository](thttps://code.arm.gov/lasso/containers/lasso-o_shcu).
>
> ---
#### 3) Prepare Simulation Data
Place or symbolically link your WRF LES simulation wrfstat and wrfout files into the `data/inputs` directory.
......@@ -71,9 +74,13 @@ wrfstat_d01_2018-07-10_12:00:00.nc
You can order WRF Simulation data to test with from the [ARM Data Discovery Tool](https://adc.arm.gov/discovery/#/results/datastream::sgplassodiagraw3C1.m1/start_date::2018-07-10)
> ---
>
> **NOTE:**
> You do not have to copy any observational data (e.g., sgpcldfracset15mC1.c1, sgplassodiagobsC1.c1),
> as this data is embedded in the container image.
>
> ---
### 4) Edit config.yml file
Edit the config.yml file to provide parameters about your run. The config.yml file contains
......@@ -116,9 +123,13 @@ environment:
* [README-DOCKER.md](./README-DOCKER.md). Use these instructions if you are running from your local desktop. **NOTE: this should be used for small test runs only**
* [README-SINGULARITY.md](./README-SINGULARITY.md). Use these instructions if you have Singularity installed on your HPC cluster.
> ---
>
> **NOTE:**
> The specific run command will vary depending upon the container runtime and scheduler
> used at your HPC cluster.
>
> ---
### 6) Plotting output and skill scores via Jupyter Notebook
See the [notebooks/README.md](notebooks/README.md) file for instructions on how to start
......
......@@ -50,13 +50,16 @@ Start up a headless juptyer notebook kernel with the following command:
$ conda activate lasso
$ jupyter-notebook --ip=0.0.0.0 --no-browser --port=56269
```
> ---
>
> **NOTE:**
> You MUST be in the notebooks folder when you run the juptyer-notebook
> command or else the notebook links will not behave correctly.
>
> Also, we are binding to the arbitrary port 56269. If this port
> is in use on your server, feel free to change the port number as needed.
>
> ---
When you start your juptyer notebook kernel, the console should output
the http url from which you can access your notebook. For example:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment