Skip to content

Commit 001e549

Browse files
committed
add some text for log file in the diagnostic
1 parent 21e8770 commit 001e549

File tree

1 file changed

+17
-2
lines changed

1 file changed

+17
-2
lines changed

_episodes/06-debugging.md

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ questions:
77
objectives:
88
- "Fix a broken recipe"
99
keypoints:
10-
- "There are two different kinds of log files: ``main_log.txt``, and ``main_log_debug.txt``."
10+
- "There are three different kinds of log files: ``main_log.txt``, and ``main_log_debug.txt`` and ``log.txt``."
1111
---
1212

1313
Every user encounters errors. Once you know why you get certain types of errors,
@@ -60,7 +60,7 @@ Let's change the working directory to the folder ``run`` and list its files:
6060
~~~
6161

6262
~~~
63-
main_log_debug.txt main_log.txt recipe_example.yml resource_usage.txt
63+
diag_timeseries_temperature main_log_debug.txt main_log.txt recipe_example.yml resource_usage.txt
6464
~~~
6565
{: .output}
6666

@@ -72,6 +72,21 @@ To inspect them, we can look inside the files. For example:
7272
cat main_log.txt
7373
~~~
7474

75+
Now, let's have a look inside the folder ``diag_timeseries_temperature``:
76+
77+
~~~bash
78+
cd path_to_output_directory/run/diag_timeseries_temperature
79+
ls
80+
~~~
81+
82+
~~~
83+
diag_provenance.yml log.txt resource_usage.txt settings.yml
84+
~~~
85+
{: .output}
86+
87+
In the ``log.txt``, ESMValTool writes the output messages,
88+
warnings and possible errors that are related to the diagnostic script.
89+
7590
If you encounter an error and don’t know what it means, it is important to read the log information.
7691
Sometimes knowing where the error occurred is enough to fix it, even if you don’t entirely understand the message.
7792
However, note that you may not always be able to find the error or fix it.

0 commit comments

Comments
 (0)