Report posterior bootstrap progress on completion rather than dispatch - #23
devonjkohler with Copilot wants to merge 1 commit into
Conversation
Co-authored-by: devonjkohler <35807256+devonjkohler@users.noreply.github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #23 +/- ##
==========================================
+ Coverage 69.69% 69.81% +0.12%
==========================================
Files 36 36
Lines 3550 3565 +15
==========================================
+ Hits 2474 2489 +15
Misses 1076 1076
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Posterior graph estimation currently advances the bootstrap progress bar when runs are queued, so progress reaches 100% before computation actually finishes. This change makes progress reflect completed bootstrap work.
Progress accounting moved to job completion
joblibcallback context manager that incrementstqdmwhen each parallel batch completes.joblibcallback after execution to avoid cross-call side effects.run_bootstrapprogress flow updatedtqdm(range(n_bootstrap))) with a completion-driventqdm(total=n_bootstrap)wrapped aroundParallel(...).