[Feature]: Give the user the possibility to break the program when using default values #188
Labels
🛟 catches
Handling of wrong / unexpected behaviour
💎 enhancement
New feature or request
good first issue
Good for newcomers
Describe the feature
Create a possibility for the user to catch non matching CPU names or locations early on.
Use case(s):
This avoids running long processes and discovering in hindsight that the default TDP was used, potientially yielding inexact results.
Suggested implementation:
Implement a
useFallback=true
parameter in the config to have the calculation break if it does not find the CPU model / location for the CI. Thefallback
option has to be implemented into the matching of CI and TDP.The text was updated successfully, but these errors were encountered: