green-metrics-tool icon indicating copy to clipboard operation
green-metrics-tool copied to clipboard

Calibration script

Open ArneTR opened this issue 1 year ago • 0 comments

At the moment the GMT has no means of detecting:

  • What the base load on the system is
  • What the base temperature of the system is
  • What the base energy of the system is
  • What the overhead of the GMT is when running it's reporters with the requested resolution

I propose a calibration script that runs for 5 mins min. and polls all these values on a 1-second interval. If the values do not change anymore after these 5 mins the script will create an average and put these values out as the "baseline".

We need this baseline then further to make claims about:

  • When is a system "cool" again and another run can start
  • What is the expected resolution of the system? This is directly derived from the noise / STDDEV in the baseline
  1. Once we have done the calibration we then start all the reporters from the config.yml and let it run for min 5 min. Again, once the values do not change anymore we create the average and estimate the overhead of the tool on the system.

This value can then optionally be deducted from any measurement if reporting is needed.

  1. The calibration script should be able to update the config.yml with the baseline values

  2. The pauses in the GMT should be dynamic and actively responding to the temperature. If no temperature reporter is defined then default to the phase-transition-time. Maybe rename it to default-phase-transition-time

ArneTR avatar Jul 01 '23 11:07 ArneTR