Added optional performance timing framework to AnalysisBaseAdd optional performance timing to AnalysisBase#5216
Conversation
…lationships, and result accuracy
There was a problem hiding this comment.
Hello there first time contributor! Welcome to the MDAnalysis community! We ask that all contributors abide by our Code of Conduct and that first time contributors introduce themselves on GitHub Discussions so we can get to know you. You can learn more about participating here. Please also add yourself to package/AUTHORS as part of this PR.
|
@Chinmayykashyap-git you deleted the AI disclosure part of the template - can you please detail if you used any AI assistance as part of this PR? |
|
@IAlibay |
Summary
This PR introduces a minimal, opt-in performance timing framework for
AnalysisBase.run()usingtime.perf_counter.Timing is disabled by default and can be enabled via
run(enable_timing=True). Collected timing data is exposed via a dedicatedanalysis.performanceattribute.Changes
enable_timingflag toAnalysisBase.run()preparetotalThis implementation is intentionally lightweight and designed to be extensible to parallel-aware timing in future work.
📚 Documentation preview 📚: https://mdanalysis--5216.org.readthedocs.build/en/5216/