schollz / find3

High-precision indoor positioning framework, version 3.
https://www.internalpositioning.com/doc
MIT License
4.63k stars 364 forks source link

analysis.to Analyze SensorData:222 unable to analyze: could not find '*********.find3.ai' #169

Open igurvich opened 5 years ago

igurvich commented 5 years ago

Installed the FIND3 server from source on a raspberry pi 3 running raspbian buster, following the instructions on the official document here: https://www.internalpositioning.com/doc/server_setup.md When running the test suite the analysis fails. Output from AI server is:

rm -rf __pycache__*
rm -rf src/__pycache__*
rm -rf venv/*
export FLASK_APP=server.py && \
export FLASK_DEBUG=1 && \
cd src && \
flask run --debugger --port 8002
 * Serving Flask app "server.py" (lazy loading)
 * Environment: production
   WARNING: Do not use the development server in a production environment.
   Use a production WSGI server instead.
 * Debug mode: on
 * Running on http://127.0.0.1:8002/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 263-968-070
/usr/local/lib/python3.7/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
  from numpy.core.umath_tests import inner1d
/usr/local/lib/python3.7/dist-packages/sklearn/ensemble/weight_boosting.py:29: DeprecationWarning: numpy.core.umath_tests is an internal NumPy module and should not be imported. It will be removed in a future NumPy release.
  from numpy.core.umath_tests import inner1d
2019-07-17 13:36:26,719 - [server/classify] - DEBUG - loading /root/go/src/github.com/schollz/find3/server/main/data/zxo1qZZb.find3.ai
127.0.0.1 - - [17/Jul/2019 13:36:26] "POST /classify HTTP/1.1" 200 -
2019-07-17 13:36:26,846 - [server/classify] - DEBUG - loading /root/go/src/github.com/schollz/find3/server/main/data/zxo1qZZb.find3.ai

Output from main data storage server is:

2019-07-17 13:35:27 [INFO] [PID-2818] server.go Run:579 Running on 0.0.0.0:8005
2019-07-17 13:36:26 [INFO] [PID-2818] server.go func1:1360 [::1]:34236 POST /data?justsave=0 91.845814ms
2019-07-17 13:36:26 [ERROR] [PID-2818] analysis.go AnalyzeSensorData:222 unable to analyze: could not find '/root/go/src/github.com/schollz/find3/server/main/data/zxo1qZZb.find3.ai'
2019-07-17 13:36:26 [INFO] [PID-2818] server.go func1:1360 [::1]:34238 POST /data?justsave=0 128.379374ms
2019-07-17 13:36:26 [ERROR] [PID-2818] analysis.go AnalyzeSensorData:222 unable to analyze: could not find '/root/go/src/github.com/schollz/find3/server/main/data/zxo1qZZb.find3.ai'

I have check at the path given and there is no ***find3.ai file present, there is only an sqlite3.db file. This is the second time I have tried to reinstall the thing from scratch and I encounter the same issue. (Docker installation hanged for a couple of hours, so decided to install it from source)

Sammy1Am commented 4 years ago

Running into the same issue. It looks like previously in #89 someone said it just "resolved on its own", so I guess I'll wait a bit. I suspect something's not quite right though...

Sammy1Am commented 4 years ago

An update (on the off-chance @igurvich still cares or anyone comes across this): I installed the find3 app on my phone and did some active learning and it seems to have created the .ai file and now it's happy. Switched back to passive scanning / learning and things are okay.

Seems like probably some sort of issue with passive scanning / learning not initializing the .ai file the same way active does.

kamilyucedal commented 4 years ago

Please check your db path permission. We changed our directory permissions to write for our user and then issue solved

Sammy1Am commented 4 years ago

For me, find3 had no issues creating the .ai file when in "active" mode, so the permissions didn't seem to be an issue. It actually looks like passive tracking in general is broken (see #181), and one of the pieces missing is the code to create the .ai file on startup. (Not sure if this is the same situation for OP though)