fixing the messing columns for pipe properties #3664
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes Issue #3562
How to test?
Use a smaller scenario and run network part 2 (detailed)
Compare results
DH__velocity_edges_mpersandDH__massflow_edges_kgs.csvThe results (v) in the former .csv and results (m˙) in the latter .csv:
v=ρ⋅Am˙
Here, v (velocity) depends on m˙ (mass flow rate, check DH__massflow_edges_kgs.csv
) and A (cross-sectional area of the pipe, which depends on the pipe diameter, checkDistribution.xlsx` in the Scenario Input database) and ρ equals 998kg/m3.Can you be the reviewer of this PR? @KFSchlager
Thanks, Zhongming