-
Notifications
You must be signed in to change notification settings - Fork 57
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
Automatically load MW and charge in MCAS #1246
Conversation
…func that returns mw with units
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1246 +/- ##
==========================================
- Coverage 94.28% 94.27% -0.01%
==========================================
Files 357 357
Lines 35894 35918 +24
==========================================
+ Hits 33841 33863 +22
- Misses 2053 2055 +2 ☔ View full report in Codecov by Sentry. |
): | ||
m[0].fs.properties = MCASParameterBlock( | ||
solute_list=["Na_+", "Cl_-", "N"], | ||
mw_data={"H2O": 0.018, "Na_+": 0.023, "Cl_-": 0.0355, "N": 0.01}, |
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.
minor observation - mw for N is 0.014
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.
True - although I wasn't too careful when doing this since the tests are really intended to test functionality rather than true values (in these particular instances).
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.
looks good to me
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.
LGTM
Fixes/Resolves:
Summary/Motivation:
This PR allows the user to now skip the step of entering MW and charge data for solutes---assuming they follow proper naming convention. If a name doesn't line up with what is expected, the user could manually enter data for those solutes but skip for more typical solute names (e,g,,
"Na_+"
and similar ions can be handled without a problem, but"target_ion"
wouldn't turn up search results).Changes proposed in this PR:
Legal Acknowledgement
By contributing to this software project, I agree to the following terms and conditions for my contribution: