-
Notifications
You must be signed in to change notification settings - Fork 1
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
removed checkBoundary for #1 #3
Conversation
@dhblum this PR adds IbpsaMpc/Resources/Scripts/merge.py , which merges the files from this PR. I made no manual adjustments. This PR now merges IBPSA.Media.Air and a subset of IBPSA.Fluid.Sources. Can you review this? |
Thanks @Mathadon Yes I will review. |
@dhblum when this is merged I'll look at further PRs! |
@Mathadon Should Examples be added for these models in this PR? If so, should appropriate ones be added with the merge script (e.g. |
Missing dependencies are a bit of an issue here. Also for plot scripts/unit tests. So I would not add examples by default. Their main function is to test the models, which is already done in IBPSA. We can add new examples later. Ok? |
My 2 cents is to add examples as we go along. Although models are tested in IBPSA, some are being modified for IbpsaMpc, and it is not clear a priori if such modifications break code. |
@Mathadon I'm ok developing a formal set of Example models along with #5 and getting this PR merged to be able to build off of. But trying to compile a simple model with just Also, I think 728d2de overwrites what is done in 38b4798, correct? |
@dhblum I have added |
Merged the library IBPSA
@dhblum this is ready to be merged! |
@Mathadon Thanks so much. This is on my list this week to review! |
👍 |
I can compile and optimize a model that includes all source models in this PR. The implementation looks good to me. One further question is what to do about documentation. All documentation, including revisions, are directly copied from IBPSA. Some of the documentation may not apply to the MPC library at the current moment, or possibly ever. For instance, the Fluid package UserGuide references heat exchangers and chiller models which are not yet implemented. Also, there may be restrictions on the use of models or parameters that are not reflected in the documentation from IBPSA. |
We can either remove the documentation altogether, or keep it and use merge option 3 to modify the documentation if needed? |
I think it will be important to have some documentation, so perhaps merge option 3 will be the way to go as needed. |
Does the current PR require changes or can we continue with this? |
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.
This PR is ready to merge.
this closes #1