Skip to content

Commit cd12e8b

Browse files
reformat question answers
1 parent 758d6d8 commit cd12e8b

File tree

1 file changed

+13
-17
lines changed

1 file changed

+13
-17
lines changed

_episodes/01-introduction.md

Lines changed: 13 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -43,22 +43,18 @@ EMSValTool is first and foremost a tool to analyse climate data. But you probabl
4343
> - Perfect
4444
> - Suitable for (Jupyter) notebooks
4545
>
46-
> Check our answers by unfolding the boxes below.
46+
> Check our answers by unfolding the box below.
4747
>
4848
>> ## ESMValTool is ...
4949
>>
50-
>> - A tool to analyse climate data. It takes care of finding, opening, checking, fixing, concatenating, and preprocessing CMIP data and several other supported datasets.
51-
>> - A way to make climate science more [FAIR](https://fair-software.eu/about). ESMValTool collects provenance information about the data and code that are used to obtain a result. It comes with a readible recipe format that makes climate analysis consistent, reproducbile, and easy to share.
52-
>> - A community effort. EMSValTool is developed and maintained by a large team of climate scientists and software engineers. It is an open source project to which anyone can contribute. It's longevity depends on these contributions.
53-
>> - A command line tool. ESMValTool was originally designed for the command line. But, we are working on a user-friendly python interface as well.
54-
>> - Free. ESMValTool is licenced under Apache 2.0, which means everyone can use, modify, or share it free of charge. We *do* encourage all users to contribute to the community once they get more comfortable with the tool, though.
55-
>{: .solution}
56-
>
57-
>> ## ESMValTool is not ...
58-
>>
59-
>> - The easy way out. If you just want to do an exploratory analysis or quickly hack something together, ESMValTool is probably not the way to go. The tool is intended for robust, repeatable and shareable climate analysis. That *does* require a bit more effort.
60-
>> - Perfect. Although we are continuously working to improve the tool, you may encounter some bugs or missing features. In this lesson, you'll learn how to troubleshoot, find help, and maybe even contribute to the solution yourself.
61-
>> - Suitable for (Jupyter) notebooks. ESMValTool was designed as a command line tool. But, we are working on a user-friendly Python interface as well.
50+
>> ✓ **A tool to analyse climate data.** It takes care of finding, opening, checking, fixing, concatenating, and preprocessing CMIP data and several other supported datasets.
51+
>> ✕ **The easy way out.** If you just want to do an exploratory analysis or quickly hack something together, ESMValTool is probably not the way to go. The tool is intended for robust, repeatable and shareable climate analysis. That *does* require a bit more effort.
52+
>> ✓ **A community effort.** EMSValTool is developed and maintained by a large team of climate scientists and software engineers. It is an open source project to which anyone can contribute. Its longevity depends on these contributions.
53+
>> ✓ **Free.** ESMValTool is licenced under Apache 2.0, which means everyone can use, modify, or share it free of charge. However, we *do* encourage all users to contribute to the community once they get more comfortable with the tool.
54+
>> ✓ **A command line tool.** ESMValTool was originally designed for the command line. But, we are working on a user-friendly python interface as well.
55+
>> ✓ **A way to make climate science more [FAIR](https://fair-software.eu/about).** ESMValTool collects provenance information about the data and code that are used to obtain a result. It comes with a readible recipe format that makes climate analysis consistent, reproducible, and easy to share.
56+
>> ✕ **Perfect.** Although we are continuously working to improve the tool, you may encounter some bugs or missing features. In this lesson, you will learn how to troubleshoot, find help, and maybe even contribute to the solution yourself.
57+
>> ✕ **Suitable for (Jupyter) notebooks.** ESMValTool was designed as a command line tool. But, we are working on a user-friendly Python interface as well.
6258
>{: .solution}
6359
{: .challenge}
6460

@@ -70,18 +66,18 @@ The figure below shows the different components of ESMValTool. Most of the work
7066
![figure showing ESMValTool architecture]({{ page.root }}/fig/esmvaltool_architecture.png)
7167

7268
>## Discussion: (dis)advantages of this approach?
73-
> Discuss or think about the pro's and cons of this architecture for a moment. Then unfold the box below to see our answers.
69+
> Discuss or think about the pros and cons of this architecture for a moment. Then unfold the box below to see our answers.
7470
>
7571
>
7672
>>## See our thoughts
7773
>>
78-
>> - Streamlining common preprocessing steps ensures consistency in the algorithms being used and the way they are executed. This facilitates comparison and reproducibility.
74+
>> - Streamlining common preprocessing steps ensures consistency in the algorithms being used and the way they are executed. This facilitates comparison and reproducibility.
7975
>> - Provenance and citation information can be tracked through the entire workflow.
80-
>> - The core builds upon the [iris](https://scitools.org.uk/iris/docs/latest/) package, which is quite strict in order to minimize unexpected results.
76+
>> - The core builds upon the [iris](https://scitools.org.uk/iris/docs/latest/) package, which is quite strict in order to comply with CF conventions and minimize unexpected results.
8177
>> - Recipes are easy to read and share.
8278
>> - A collection of recipes and diagnostic scripts is shipped with ESMValTool, ready for re-use. Everyone can add to this collection.
8379
>> - The recipe format takes some getting used to and may be a bit less flexible then working on the datasets directly.
84-
>> - Missing features can be more of a limiting factor.
80+
>> - Features or dataset support that are missing from ESMValCore can be a limiting factor.
8581
>{: .solution}
8682
{: .discussion}
8783

0 commit comments

Comments
 (0)