-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Numerical Syntax #104
Comments
Yes this can be easily fixed. We just to round to 2 decimal points when rendering the table. I'll add this to the next release. |
Thanks @JoshC1994 , I have been having this issue as well. @davidusb-geek while you are fixing the rounding could I suggest some additional improvements: Could I suggest that all the power values be rounded to 0 decimal places. P_PV and P_Load are already displayed as int, but the other P_ variables are displayed with a lot of unnecessary precision and it would be good if they could also be displayed as int, cost_profit & cost_fun could also potentially be rounded to 2 decimal places: |
Yes sure, no problem with these improvements. |
Solved here: #105 |
+1 thank you! @davidusb-geek Appreciate everything you do for this project! |
Great! Closing this as completed. |
This is solved in the (just-to-be-released) new release. |
Describe the bug
The Syntax of numbers shown in the "Last Run Optimisation Results Table" sometimes displaying as scientific numbers.
Why
The fact may be simply due to the input data EMHASS is being fed and the maths being calculated so that the resulting number is too great for the plotly table to display.
Fix
Would it cause too many issues with resolution if EMHASS only considered data and calculated the resultant to say 2 decimal points. I would think that any more resolution is only adding complexity and would require unnecessary compute resources.
Maybe the decimal count could be set via config?
I might be missing something but in most use cases I think that 2 decimal places would be enough resolution.
The text was updated successfully, but these errors were encountered: