-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add Conversion Progress Bars #778
Conversation
for more information, see https://pre-commit.ci
@CodyCBakerPhD Actually I see now in #774 that you don't think we need these options. I'm getting this error with the above code enabled:
|
# "iterator_opts": dict( display_progress=True, progress_bar_class=TQDMProgressSubscriber, progress_bar_options=progress_bar_options ) | ||
} | ||
if available_options.get("properties").get(interface).get("properties", {}).get("stub_test") |
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.
I would not bother displaying the per file progress when running in stub mode - just the total bar should be fine (since individual files should be instantaneous)
This feature is just for non-stub full conversions with many files
This only applies to recording and imaging interfaces; sorting, such as Phy, do not currently support it at all since they don't buffer at all (source data is small enough to load entirely to RAM) |
…outBorders/nwb-guide into hdmf-progress-bars
for more information, see https://pre-commit.ci
This behavior may be related to the fact that the raw TQDM updates indicate |
…he NWB GUIDE root folder
for more information, see https://pre-commit.ci
That might just come down to an edge case on the size of this (small) data I can try with some larger files |
@garrettmflynn it might be a while until the entire stack comes into sync with this; can you splinter out the logging improvement to a separate PR? Also would it be possible to limit the number of error messages displayed at a time so the screen doesn't plan? |
for more information, see https://pre-commit.ci
@garrettmflynn Any idea what's up with the ubuntu pipelines here? I reran them 3 times |
Looks like we saw this same error in #676 (comment). Last time, we were able to track this down by looking at the artifacts. I'll do this now. |
At least for the lastest run, it looks like the progression though one of the pipelines (previously an earlier pipeline, this time CellExplorer) freezes and the Puppeteer instance decides it's been too long after 5min. Looking at the screenshots, everything looks good. Only weird part is that there aren't any after CellExplorer File Metadata since the stall. |
And it's happening on all of the CI now? |
My bad, looks like I didn't wait for the final screenshot to finish before closing Puppeteer. Had to significantly refactor the iteration through all the pipeline pages so a screenshot could be injected after each—and it looks like this slipped through. |
for more information, see https://pre-commit.ci
…outBorders/nwb-guide into hdmf-progress-bars
for more information, see https://pre-commit.ci
Just tried this out locally on Windows using the multi-session tutorial dataset that was modified (by changing line https://github.com/NeurodataWithoutBorders/nwb-guide/blob/main/src/pyflask/manageNeuroconv/manage_neuroconv.py#L1347 from Since the number of jobs is not yet exposed to the frontend (so no parallel writing of multiple files) I would have expected only one extra bar below the main one (counting how many files remain), with the second bar tracking progress on writing the 'long' recording for each file However, I did not see any extra bar displayed |
Was this a full or stub conversion? Just tested on my M2 and I'm able to observe sub-bars for each file—though this is disabled for stubs. |
While the option isn't exposed on the UI, we are telling the backend to write use 2 jobs at the moment—so you should see four sub-bars populate in groups of two. Though to clarify, you're expecting to see one sub-bar if the n_jobs is 1? |
It was a full conversion; I don't expect sub bars for stub mode (though I would expect parallelization) Odd, I just tried with my M1 mac and they show up fine; I'll try again on Windows later and raise an issue
Yeah, I'd always expect sub-bars per file to show how long each individual file is taking to write |
This PR implements the basic skeleton for parallel conversion progress bars, specifically a parallelized global bar for conversions.
Pretty sure this still requires updates to NeuroConv to allow for within-file updates. Specifically, we need to ingest the following conversion options: