Bug_Fix: Property Recursion - Develop #361
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update cost property that was causing a recursion loop when accessed
This PR is based on PR #350 but cherry-picked to be able to be merged into
develop
instead ofdev/refactor
. PR #350 was an update to #345 based on reviewer feedback.om_total_expense
toom_total_expenses
following naming convention inHybridSimulation
.om_total_expense
in theOutputs
class and theom_total_expenses
property to a Sequence.cf_operating_expenses
from a Numpy Array type to a Tuple to avoid additional errors when accessing the property.Related issue
Impacted areas of the software
Additional supporting information
PR #350 was approved by @dguittet.
Test results, if applicable