From 4bbfb68a6ee35a585663921e397877df6e2258aa Mon Sep 17 00:00:00 2001 From: Danny Marc Rotscher <danny.rotscher@tu-dresden.de> Date: Fri, 29 Jul 2022 13:00:48 +0200 Subject: [PATCH] Update doc.zih.tu-dresden.de/docs/software/energy_measurement.md --- .../docs/software/energy_measurement.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc.zih.tu-dresden.de/docs/software/energy_measurement.md b/doc.zih.tu-dresden.de/docs/software/energy_measurement.md index 3c0e5b2f6..2f47043ec 100644 --- a/doc.zih.tu-dresden.de/docs/software/energy_measurement.md +++ b/doc.zih.tu-dresden.de/docs/software/energy_measurement.md @@ -39,9 +39,8 @@ regulator (CPU, DDR) measurements. ## Command Line Interface -The HDEEM infrastructure can be controlled through command line tools that are made available by -loading the `hdeem` module. They are commonly used on the node under test to start, stop, and -query the measurement device. +The HDEEM infrastructure can be controlled through command line tools. They are commonly used on +the node under test to start, stop, and query the measurement device. - `startHdeem`: Start a measurement. After the command succeeds, the measurement data with the 1000 / 100 samples/s described above will be @@ -57,6 +56,10 @@ query the measurement device. data can be read from the device after this command is executed before a new measurement is started. +!!! note + + Please always execute `clearHdeem` before `startHdeem`. + ## Integration in Application Performance Traces The per-node power consumption data can be included as metrics in application traces by using the -- GitLab