-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add Pretty Cost Printing #1125
Add Pretty Cost Printing #1125
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "(a type of InputOutputCurve)" necessary? We haven't focused on InputOutputCurve elsewhere in documentation, so I think it could be extraneous and confusing
Also, could shorten "composed of" to "with" or something, but otherwise, looks good
My thinking was we want to make it super clear when things are input-output curves versus incremental/marginal curves, etc., but I agree that using type names that aren't otherwise very exposed is confusing. Thoughts on another way to do this, or do you think it's already sufficiently clear that this is an input-output curve? |
Fixes #1048. Depends on NREL-Sienna/InfrastructureSystems.jl#377.
Here's how the new cost struct printouts look at their most complicated (printing some operational costs):
Next is to figure out a way of abbreviating this to stick it into the components printout.