Skip to content

Change "resiliency" variable labels for clariity#739

Merged
cpaulgilman merged 2 commits into
patchfrom
SAM_891-resiliency-labels
Feb 2, 2022
Merged

Change "resiliency" variable labels for clariity#739
cpaulgilman merged 2 commits into
patchfrom
SAM_891-resiliency-labels

Conversation

@cpaulgilman

Copy link
Copy Markdown
Collaborator

The term "resiliency" means different things in different contexts, so avoid using in labels. In this case use "Battery hours of autonomy during grid outage" instead.

Accompanies NatLabRockies/SAM#902

Replacing "resiliency" in variable labels with "hours of battery autonomy during grid outage".

I did not change the "resiliency" group name to avoid problems with PySAM.

Alternate suggestions for variable labels welcome!

The term "resiliency" means different things in different contexts, so avoid using in labels. In this case use "Battery hours of autonomy during grid outage" instead.

@brtietz brtietz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall I like the naming and the grouping - just one nitpick regarding min and max in the variable names (which might trigger some additional renaming)

Comment thread ssc/common.cpp Outdated

@sjanzou sjanzou left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good... I agree we should, at some point, have a consistent max and min naming scheme

@cpaulgilman cpaulgilman requested a review from brtietz February 2, 2022 00:06
@cpaulgilman cpaulgilman merged commit 2bbe91e into patch Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants