| ... | ... | @@ -52,8 +52,8 @@ The Acceleration sub-component calculates a number of Acceleration Specific indi |
|
|
|
`make`
|
|
|
|
|
|
|
|
- **Step 3:** Run the dataset in the new device:
|
|
|
|
- *Step 3a:* The developer has to update the script `get-power.py` providing the files (/dev) that monitor the power sensors of the new device. For example, we provide also the `get-power-nano.sh` which is used for the Nvidia Jetson Nano, that also includes a Tegra X1 SoC with less GPU-cores. If needed (if the new device follows a completely different strategy on monitoring power the user can also make any additional changes needed on `measure_time_energy.sh`)
|
|
|
|
- *Step 3b:* Generate the dataset
|
|
|
|
- **Step 3a:** The developer has to update the script `get-power.py` providing the files (/dev) that monitor the power sensors of the new device. For example, we provide also the `get-power-nano.sh` which is used for the Nvidia Jetson Nano, that also includes a Tegra X1 SoC with less GPU-cores. If needed (if the new device follows a completely different strategy on monitoring power the user can also make any additional changes needed on `measure_time_energy.sh`)
|
|
|
|
- **Step 3b:** Generate the dataset
|
|
|
|
`cd real-life-dataset && python generate_dataset_script.py energy`
|
|
|
|
Notes: The script `generate_dataset_script.py` runs all the benchmarks automatically. If the user wants to run a specific benchmark the `run_rataset.py` can be used `python run_dataset.py <app_hotspot_name> <energy|time>` The app_hotspot_name is retrieved from the config.txt, while the second argument is energy for measuring energy and time for measuring time.
|
|
|
|
|
| ... | ... | |
