-
Notifications
You must be signed in to change notification settings - Fork 393
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
Finish removing Objexx gio #8248
Conversation
Pulled develop in one more time to get fresh CI results. I'm building locally then I'll push that up. |
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 like lots of great cleanup here. I'll be leaning on CI pretty heavily for verifying the outputs, but I'll definitely do some testing locally as well.
…agedTerminalHeatPump integration test
@lefticus @Myoldmopar running integration tests locally on my Mac showed that
The clear_state on that got left in an experimental state from #8318, so once that was cleaned up the above problems went away. However, after that E+ errored out due to not being able to parse the
Once those |
@mitchute thanks for pushing that up. The |
@Myoldmopar are these inputs that are failing on Mac new, or were they overlooked when I first created this PR? If you need me to look at this I'm going to be completely busy through Friday, but able to first thing next week. |
I did not verify when they were introduced, though I could run an automated bisection to find the exact commit. And this is not urgent. We are past 9.4.0 release, and just getting some of these relatively easy-to-review PRs merged in for the next release. |
Sounds good, let me know if there's anything you'd like me to look at. |
I haven't been able to diagnose exactly what caused it, but with this branch, if I add a |
e0 is going to be parsed as "10^0" I have no idea what d0 is supposed to mean. So the |
OK, I understand this a bit more now. In raw numeric input fields it is not allowed, even in the develop branch. The problem shows up in EMS commands. In EMS, as you likely know, the user writes their own functions in a built-in language, the EnergyPlus Runtime Language. The interpreter for this is built inside EnergyPlus and the user-defined functions are executed at runtime. In this custom language, the user can assign numeric literals. Multiple suffixes are allowed, including both If you look in commit ddaa942, you will see that @mitchute removed the So when EMS is interpreting a user-defined function, there could be a command line like: Let me know if you want some more clarification. |
This actually makes perfect sense. Since all of the GIO has been removed through the system (including EMS) and replaced with more standard things. I can fix this. |
* convert `d` or `D` to `e` when appropriate and pass to normal normal parsing code * try to make failure cases between libc++ (used on MacOS and some Clang installs) and MSVC/libstdc++ the same in the case of failed parses.
… finish_removing_gio
I believe this last commit 19d9855 addresses the parsing problems with |
Deleted one set of results above to confirm security issue is still there. If it is, I'll try merging my Decent PR tomorrow and re-running. Either way, this branch should be all ready to go in. |
A rerun showed this was still fine, but I need to verify it builds with latest develop. After that passes I'll get this merged in. |
Still all really good. I'm going to build locally to make sure that last develop movement didn't cause the build to break then merge. |
@Myoldmopar should we revert out these changes I made, or are they covered elsewhere? |
I say leave them. They are still present in the other test file so we are still covered there. |
Pull request overview
Finishes removing Objexx gio and support libraries from Energy+
No expected change in tests.