... | ... | @@ -76,7 +76,8 @@ Nemo modelfactors generates a Output folder during execution.The location of thi |
|
|
It contains:
|
|
|
|
|
|
- **logs:** Contains all the error and output files of the jobs submitted during the script execution. If any job fails the script is stopped, this way you can troubleshoot the error by easily locating and reading the logs.
|
|
|
- **Gprof:** Is where the functions of the Nemo configuration are listed.
|
|
|
- **gprof:** Is where the functions of the Nemo configuration are listed. Only this list remains if the script is executed entirely.
|
|
|
- **Run_NEMO:** If the script is executed correctly this folder is deleted, is where NEMO is ran in order to obtain the different traces.
|
|
|
- **Metrics:** Folder where the performance metrics data produced is stored, more information in the next section.
|
|
|
|
|
|
## Data generated
|
... | ... | @@ -103,7 +104,7 @@ All the data generated can be found inside the Metrics folder. |
|
|
|
|
|
# Workflow
|
|
|
|
|
|
In this section the general workflow of the script is quickly explained in order to get an overview of what the script is doing.
|
|
|
In this section the general workflow of the script is quickly explained in order to get an overview of what the script is doing.
|
|
|
|
|
|
Steps 1 and 2 are performed simultaneously with step 3, the same applies to each sub-step of step 4.
|
|
|
1. Nemo is compiled with the -gprof flag (only if not done already).
|
... | ... | |