사용자 도구

사이트 도구


traccar-test-01

차이

문서의 선택한 두 판 사이의 차이를 보여줍니다.

차이 보기로 링크

traccar-test-01 [2019/01/29 09:13]
chajh
traccar-test-01 [2021/04/13 06:54]
줄 1: 줄 1:
-===== Traccar Client on Old Smartphones ===== 
-Code (Finding ghosts): [[https://github.com/jaehyukcha/jaunt/blob/master/Finding%20Ghosts.ipynb|GitHub]] 
- 
-==== Intro ==== 
-We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people's move day by day. We needed a GPS tracker that is stable enough to get 10-100 people's location at once, and easy to install for participants. We've been through a few things, that is another story. \\ 
-Anyway, we adopted Traccar as our GPS tracking platform base, and we'd already tried several experiments. It worked well, but we got a bad news recently. \\ 
-==== What's the problem? ==== 
-GPS is only available outdoors. Today, GPS tracking system are usually built in vehicles such as airplane, ships, trucks, and taxis. They move most of the time except for a few minutes on a shaded path such as a tunnel. So, it's easy to get the location data from these objects. There are not too many tracking devices that also fit perfectly by types of vehicle. Well then. How about the location of people? Can we still get data from individual person through GPS Tracker like Traccar?\\ 
- 
-Today's people mostly spend their time inside: home, office, subway, shopping mall and so on. GPS cannot get indoor position so that we can just see where people move from a place to another place. What's more, if people send their location data through small devices like smartphone, we will face numerous smartphones. Unlike the devices for vehicles, there are a lot of things varied such as its OS, the version of OS, manufacturer, hardware conditions, etc. \\ 
-So, we got some potential issues: 
-  * Most of data are not real value. It is an estimated value of its place. 
-  * The tracker device are so varied. It is so hard to comprehend.  
- 
-Besides, it is sufficient so that we can get the places our participant visits, although we don't catch actual location where they are in each place.  
-==== Bad news? ==== 
-While we believe we know the testers' stay points, Dr. Jun, our fellow researcher, reported some clients didn't send data for several hours. It could be problem.  
-  - If any movement was existed in the gap, the data for many hours have been lost. 
-  - If not, it is fine. Nothing to do. 
- 
-We must look into which is right. 
-==== Test ==== 
-Unfortunately, we don't have the specific information of previous participant's devices. So, we should imagine the device which might cause some problems and should be sifted out before experiment begin. First, we picked old phones with some troubles. We want to know whether these legacy devices can run Traccar client properly. Because no small number of our study targets is the disabled and the aged. Some of them use a quite old phone that might have hardware or software issues.((The disabled and the aged are normally not rich, rather than others, at least in Korea. (I think it is global phenomenon) Anyhow, we'd better ready for a participant who has a phone that we're not familiar with. )) \\ 
- 
-Test starts: 20190121 
-^Name^Phone^OS Ver.^Traccar Ver.^Network^Major problem^ 
-|DBLAB0102|iPhone 6|12.1.2|5.5 (latest in iOS)|Only Wi-Fi (tethered to other phone's network)|Battery Drain| 
-|DBLAB0103|Samsung Galaxy S5|6.0.1|5.17 (latest in Android)|Only Wi-Fi (tethered to other phone's network)|A little Lag to catch GPS signal| 
- 
-Both devices have sent location data for a week. 
-To get more information, go to the GitHub link above.\\ 
- 
-==== Result and Analysis ==== 
-We configured the client to send its location every 60 seconds. Theoretically, it should've transmit data within 1-2 minutes even if there is some include calculation delays. Here is count of the gaps in minute. 
-^  ^ < 2 min ^ 5 ^ 30 ^ 60 ^ 120 ^ 180 ^ 360 ^ > 360 ^ total ^ % of < 2 min ^ 
-^DBLAB0102| 5045 | 44  |3|0 |2|0|4|4|5102| 98.8827 | 
-^DBLAB0103| 8192 | 121 |6|14|5|1|3|0|8342| 98.2018 | 
-Overall 
-The result in detail is written in GitHub above. 
- 
-=== Case 1: Low battery and shutting down === 
-=== Case 2: Low battery and energy saving mode === 
-=== Case 3: Sleep mode/idle === 
-=== Case 4: Process killed by OS === 
  
traccar-test-01.txt · 마지막으로 수정됨: 2021/04/13 06:54 (바깥 편집)