When testing scripts in languages, account for both the binary executable and the energy used in compilation (black box)

Experiment with the various (software) energy measurement tools that exist, based off the prior academic papers and their ideas

• intel tooling
• powerTOP
• etc

On a Debian-based GNU Linux Distribution, rework the energy tool used in measurer.py to use something that functions with linux and AMD hardware. Ideally, output data in the same normalized way so that data analysis scripts do not need to be changed.

Given dummy data that will eventually become real data, present a visualization form to view how a breakdown of utilization metrics

Test if the energy logger and profiler need to both be running at the exact same time, or if we can run them in sequence, repeating the desired test program.

improve analyzer.ipynb to draw labeled intervals of the where each function is

Explore existing profilers for a few different languages:

• Python
• C++

Goal to implement someday:

• Rust
• Go
• C
• Java
• Kotlin
• JavaScript 💀

Note any differences between the existing profiling APIs. How extendable are they? Try some simple tracking and tagging of different code injections