Power and battery usage monitor for Windows 10 on ARM64

Run powerusagerunner.bat from the repo directory with an output directory as the first argument (defaults to the current directory). Prompts will give you instructions on how to proceed. Once complete, pass the output directory to the powerusageanalyzer.py with --data.

IMPORTANT: Polling interval should be no less than 1 minute, otherwise you risk duplicating data which is difficult to find and filter.

Steps to Run

IMPORTANT: This tool does not differentiate between AC and Battery testing, it is up to the user to configure this before starting the experiment. Furthermore, the tool cannot tell what applications should/shouldn't be running, it is up to you to ensure that have what you need running during baseline. There is a pause between the testing and baseline phases with the Batch script that allows you to setup the testing phase before continuing. With WinPowerUsage, after calling stop(), you can pause for as long as you need before starting the testing phase. stop() ends the baseline phase, and kill() ends the testing phase (or everything but that is not recommended).

1. Clone this repository.

2. There are a couple ways that the data can be recorded:

   1. Run from powerusagerunner.bat <BASELINETIME> <TESTINGTIME>, where BASELINETIME, and TESTINGTIME must be given in seconds.
   2. Integrate power usage gathering tool into another process with WinPowerUsage from the file windows_powerusage.py.
      1. An example implementation in Raptor can be found in this bug

3. Simple experiments should be conducted using the batch file though it can still be easily done with the python version if needed.

   1. If this is the case, be sure to use a Windows Command Prompt with Administrator Privileges.

4. After running the experiments, an output directory titled usagerunfrom* is created and contains the results from the baseline and testing gathering stages.

   1. If running Raptor with this tool, you'll find the data in the powerusage folder in the artifact directory.
   2. It's important to call WinPowerUsage.kill() when finished to store the config for a more precise analysis.

5. I suggest moving the data off the reference hardware as soon as it's finished to free up the hardware for more tests.

6. Be sure to have matplotlib and numpy installed - you can try obtaining them with pip install -r requrements.txt but it's highly likely that this will break. I suggest using the Anaconda environment to get around any errors you may have.

7. Pass the folder to the analyzer like so (the --data directory must contain the baseline and testing folders along with a config.json file:

   		python powerusageanalyzer.py --data usagerunfrom1241987128 --compare --application "firefox" --baseline-application "firefox" --plot-power --smooth-battery --baseline-time 21600 --testing-time 600 --outputtype csv
   

   Testing time and baseline time can (most of the time) be found with the values stored in config.json and is automatically calculated. If there are issues, it can be changed with the flags in the command above. There are also --exclude-apps and --exclude-baseline-apps to ignore some applications if needed. See powerusageanalyzer.py for more information.

   Multiple applications can be observed at the same time if a list of applications is given to --application, or --baseline-application

   The --outputtype can either be JSON or CSV - CSV has a nicer results printout in the console. The results created in this file type are stored in a results folder in the given --data directory.

NOTE: For the Batch script, a conhost.exe process exists for it in the powercfg /SRUMUTIL reports - it can be ignored with the exclusion flags, but it is good to know it's there.

NOTE: See this bug for research that has already been performed along with a spreadsheet containing all the results.