The expiration time for new job artifacts in CI/CD pipelines is now 30 days (GitLab default). Previously generated artifacts in already completed jobs will not be affected by the change. The latest artifacts for all jobs in the latest successful pipelines will be kept. More information: https://gitlab.lrz.de/help/user/admin_area/settings/continuous_integration.html#default-artifacts-expiration

Commit f5868499 authored by Dominic Etienne Charrier's avatar Dominic Etienne Charrier
Browse files

Remove paragraph duplicate.

parent 863d31d8
......@@ -114,28 +114,6 @@ Furthermore, if you have run the same experiment multiple times, it will compute
the measured minimum, maximum, and mean times. It will also include the standard
deviation of the measured times into the generated CSV table.
\paragraph{Parsing runtimes}
After completion of all jobs (or of some jobs if you want to have a peek),
you can run
\begin{code}
<path_to_sweep>/sweep.py <path_to_configuration_file> parseAdapters
\end{code}
which tells you which jobs have been processed successfully and which
ones have not. However, the main purpose of this subprogram is to parse
the measured CPU and real time spent in the different phases (\textit{adapters})
of the algorithm from the output files written by your jobs.
The parsed data is put into a CSV table which can be easily edited
with any spreadsheet software.
Depending on the solver implementation (fused algorithmic phases vs. straightforward implementation using separate
predictor, Riemann, and corrector loops), the algorithmic phases constituting a time step differ.
\texttt{sweep.py} comes with another subprogram \texttt{parseTimeStepTimes} for post-processing the
output of the \texttt{parseAdapters} subprogram. This subprogram is aware of the two different solver implementations
when computing the CPU and real time spent in the time stepping adapters.
Furthermore, if you have run the same experiment multiple times, it will compute
the measured minimum, maximum, and mean times. It will also include the standard
deviation of the measured times into the generated CSV table.
\paragraph{Parsing LIKWID metrics}
It is possible to instruct \texttt{sweep.py} to use LIKWID's \texttt{perfctr} wrapper.
In this case, you specify the LIKWID metric groups you want to measure
......
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