-
Notifications
You must be signed in to change notification settings - Fork 2
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
Need to be able to specify batch size for number of files loaded #75
Comments
Can you clarify what you mean by "step through many sets"? |
It's possible zip files are being redundantly unpacked: |
There are say 10,000 images in a class and my set size is 500 ROIs. I guess step through was not the right term, since they all stay loaded. Just say I've loaded 8,000 (or even all 10,000). Then it gets hung up. I can't say exactly how many are too many. |
I've often wondered why it isn't more of a "step through" with the set size. Would it be easier for the computing if I saw first the first 500, then the next 500 etc, rather than having all 10,000 loaded at once? |
This issue is part of the cause for a problem with #74. If I get to a very large class (mix, or other, if starting wihout classifications), and I step through many sets, then the system is frozen and the only way I can get going again is by clicking the "IFCB Annotate" in the upper left and starting over. Then it is tedious to click through 30 views to get past "other" and see the rest of the views. This was happening even with only 2 bins of data. Maybe the view should be a drop down menu in addition to next and previous? I'm not sure there is an immediate solution to being able to get through a large class. So, a solution for just getting past it would be good in the interim.
More details on the hang up after a large class: It mostly just gets stuck. If it does appear to move to the next view, then the images for the next class are not shown - only the lingering horizontal red lines. And then it is also stuck. If I look at the large class and do not load past the first set, I can get by it.
If I can specify the batch size, this would help. If 10 bins are loaded, the tool can be trying to work with tens of thousands of images at one time.
The text was updated successfully, but these errors were encountered: