-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BBPBGLIB-1057] Replace Report.hoc by report.py #145
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
The less HOC the better 🥳
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ea1e422
to
2296f55
Compare
This comment has been minimized.
This comment has been minimized.
2296f55
to
f11bdc4
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Great change! My only slight concern is regarding performance since reports can demanding as they go through all sections and hoc can use optimized 'for' loops, like |
Actually we have the times of the report setup time. It is true that is slower, but do we care that much? it is usually insignificant compared to the run time. I checked the blueconfigs sonataconf-quick-v5-plasticity that has 5 reports, and run a simulation for 10ms and changed the target to Mosaic (~220k cells and 110 gids per rank), so this is almost worst case scenario (short simulation with a lot of reports and big number of gids per rank). The hoc version:
And the python version:
What do you think? |
Thanks for the measurements. I think that's acceptable given the benefit. 👍 |
f0a5936
to
79b6682
Compare
This comment has been minimized.
This comment has been minimized.
a5b4db1
to
26b62e6
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
a9f23d5
to
45bbbbe
Compare
This comment has been minimized.
This comment has been minimized.
- Move exception handling outside report_setup and avoid returning a boolean BLUECONFIGS_BRANCH=jblanco/summation_intrinsic_currents_precision
BLUECONFIGS_BRANCH=jblanco/summation_intrinsic_currents_precision
45bbbbe
to
7bbf3cc
Compare
Logfiles from GitLab pipeline #205492 (:white_check_mark:) have been uploaded here! Status and direct links: |
## Context Create a python report.py and replace the old Report.hoc ## Review * [x] PR description is complete * [x] Coding style (imports, function length, New functions, classes or files) are good * [x] Unit/Scientific test added * [ ] Updated Readme, in-code, developer documentation
## Context Create a python report.py and replace the old Report.hoc ## Review * [x] PR description is complete * [x] Coding style (imports, function length, New functions, classes or files) are good * [x] Unit/Scientific test added * [ ] Updated Readme, in-code, developer documentation
Context
Create a python report.py and replace the old Report.hoc
Review