Comments (6)
We tried with @swiezew to reproduce the issue on his Mac, but the classification finished without issues. I need to investigate the issue on my laptop further.
from mbaza.
@swiezew how long does it take on your machine? if we extrapolate to numbers of images that we expect in real usage, how long would the inference take? is it using GPU on your machine?
from mbaza.
@marekrogala I've worked with the 628 images sample. I used my 2013 Mac's CPU (2,7GHz, 16GB RAM). Inference was divided into 10 batches, each took approximately 100 seconds (15 minutes in total). That means each image took around 0.7sec. The typical size of the data to be analysed has been said be 30000 images, which would take around 6hours on my laptop.
from mbaza.
It seems the crash is indeed due to the classifier running out of memory. I noticed that I am consistently able to process the full data set if I close all Chrome instances; with a few tabs open the classifier would crash on the 10th batch and with many tabs open it would crash on the 3rd.
Our users probably won't have more than 16 GB RAM on their machines (?), so solving this issue is a priority. Scaling the images down might suffice; I'll create a separate issue for it.
from mbaza.
from mbaza.
Closing - we didn't have any reports of this issue recently.
from mbaza.
Related Issues (20)
- The species tooltip in the observation inspector can get detached
- Remove flashing animations from map markers
- Make cards with prediction overrides more prominent
- Configurable photos size in observation inspector
- Protect users from mistakes when overriding predictions
- Assets don't work on Windows
- Selection mode collides with filtering
- Sprint 5
- Sprint 6
- Test Mbaza on Windows HOT 3
- Separate component for ExplorePage when data is not loaded
- Save relative paths to images when running inference
- Sprint 7
- Station is not extracted from file path on Windows
- ONNX runtime error on Windows HOT 1
- Fix and enable automatic build / publish
- Fail the build if the models are missing
- [Bug]: Mbaza Installation Issue on MacOS Monterey V 12.6 - "A JavaScript error occurred in the main process" HOT 1
- Enable developer tools for all builds
- Classification fails without clear feedback if output is not a file
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mbaza.