Giter Club home page Giter Club logo

Comments (2)

schollz avatar schollz commented on May 18, 2024

I think 5 minutes - but yeah the accuracy should go up a little bit if you do spend more time. There are WiFi fluctuations that can be pretty rampant.

from find3.

Thomas499 avatar Thomas499 commented on May 18, 2024

I am reopening this issue rather than creating a new issues for basically the same title. If you would prefer new issue instead let me know.

I read https://www.internalpositioning.com/doc/tracking_your_phone.md under the Learn some Locations section that it is recommended to train location for 5 minutes per room.

Then I read on https://github.com/schollz/find3/blob/master/doc/tracking_your_computer.md For your tracking scans to work, you must go to each room and run the learning command for about 10 minutes.

Then I read on https://github.com/schollz/find3/blob/master/doc/passive_tracking.md Leave the device in the location for about 30 minutes to collect a good amount of fingerprints. This will allow you to collect about 15 pieces of sensor data per location.

So different documentation recommends 5 minutes, 10 minutes, and 30 minutes per room. Granted, the 30 minute recommendation appears to be for passive scanning rather than learning by phone. Perhaps it would be beneficial to change the documentation to match each other or at very least have the information regarding time to train for various methods in one spot.

Is it possible to bypass the rate that android scans naturally, to decrease the time it takes to learn each room? - Like what would happen if we scan every second for the wifi signals?

I will hint that training over longer periods of time rather than all in a quick setting seems to produce significantly better results. I.e. if you scan in 5 minutes, chances are someone hasn't opened or closed different doors. It seems to help to take readings in different environments.

Perhaps the most significant environment change is humidity. Train on a dry day, then train while its raining, then train again the day after it rains.

Perhaps on the app, instead of training for 5,10,30 minutes at a time, just have a button that takes one reading per press. Tell the user to train each room twice a day, once in morning, once at night, over the course a week. That's 14 well difference readings that take into account doors opening and closing, and different humidity levels. All of which would not be accounted for if you just train in one setting.

from find3.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.