Handle incomplete EPW design conditions header #5134
+9,752
−509
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.
Pull request overview
EpwDesignCondition
has many API-breaking changes related to its getters. The previous behavior was to misleadingly return a value of 0 for any empty design condition header field. The types for the getters are now eitherboost::optional<double>
orboost::optional<int>
.Notes:
stringToDouble
return 0.0 if an empty string is passed in? Yes.heatingDryBulb99
is empty string insetHeatingDryBulb99
? Yes.boost::optional<double>
; e..g,double EpwDesignCondition::heatingDryBulb99() const {
toboost::optional<double> EpwDesignCondition::heatingDryBulb99() const {
? Yes.double m_heatingDryBulb99
toboost::optional<double> m_heatingDryBulb99
in EpwDesignCondition class? Yes.Pull Request Author
src/model/test
)src/energyplus/Test
)src/osversion/VersionTranslator.cpp
)Labels:
IDDChange
APIChange
Pull Request - Ready for CI
so that CI builds your PRReview Checklist
This will not be exhaustively relevant to every PR.