Could we add an "energy_unit" attribute to the estimators?
See original GitHub issueI was thinking, it could be interesting to have the energy_unit
attribute that we now have attached to every parsed DataFrame also attached to the estimators? In this way for example, when one uses the plot_ti_dhdl
function, the function itself can get the original units of the data from the input data, without relying on the input of the user.
Issue Analytics
- State:
- Created a year ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Estimation of energy consumption in machine learning
Two use cases to estimate energy consumption for deep learning and data mining. ... Thus, we believe that efforts towards estimating energy consumption...
Read more >Machine learning for estimation of building energy ...
The statistical methods use building historical data and frequently apply regression to model the energy consumption/performance of buildings.
Read more >Estimating the Performance and Economic Value of Multiple ...
We use the presented methodology to implement both technologies in a production cost model to compare the dispatch and system value of the...
Read more >Cost Estimating Guide - DOE Directives
Activity-based, detailed or unit cost estimates are typically the most definitive of the estimating techniques and use information down to the ...
Read more >Generation Attribute Tracking System (GATS) Operating Rules
System Energy, Multi-fuel Generating Unit, Non-Unit Specific Imports, ... specify the state(s) for which the Retail LSE will use the GATS.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Make sense, I will make it that one could only
get
delta_f_ and d_delta_f_ but cannot beset
them. We don’t want the user to modify the estimator object, as this could give raise to the inconsistency issue that you have suggested.This does make sense. I do the unit conversion at the end and you do it at the beginning.
Correct me if I’m wrong. So I think currently only the visualization part of the code will ask the user to specify the unit. I will try to think of a way that all the visualization function would have a uniformed logic.
I am going to mark the issue itself as “won’t fix” because we’re keeping the energy associated with the data, as @xiki-tempula explained.
Please raise a separate issue for any documentation problems or just fix the docs with a PR.