-
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
Avoid duplicate code in downchunking #180
Conversation
Pull Request Test Coverage Report for Build 8522125034Details
💛 - Coveralls |
I don't understand why the 3.9 test passes while the 3.10 test timeout... I think the tests failed because of the slow database download. I tried reverting to the main branch and still got a timeout. We should try again later. |
Thanks for opening this @mhliu0001, It make a lot of sense to clean up the code in these plugins! I will try to find time next week to check it! |
Now the tests have passed. |
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.
Looking good! I ran the code and the results did not change (as expected). The code in the compute method is also cleaner now. I will bump the plugin versions as we changed the compute method and then merge this PR.
In the previous code, the
compute
function for downchunking plugins (S2PhotonPropagationBase, PMTResponseAndDAQ) has some duplicate code. While I understand this is because the chunking start/end times are different, it can be avoided by defining a functioncompute_chunk
, and calling it to calculate the data in each chunk.This PR should not alter the behavior of fuse and should be purely cosmetic. If the simulation results change, please let me know.