interns
we'd like to congratulate the wigle^tm lab interns who have spent the last six months updating our data filtering/ranking/triangulating algorithms as their "summer" project.
this should result in some minor signal increases in the very noisy data set that is wigle. seti@home eat your heart out.
this should result in some minor signal increases in the very noisy data set that is wigle. seti@home eat your heart out.
Uh guys, the interns appear to have eaten a few hundred thousand data points on the way.....<<burp>>...we're back to less than 7 million ?
6,977,155 to be exact at 5:27 PM CDT.
6,977,155 to be exact at 5:27 PM CDT.
Aye, the number goes down from time to time as better methods of fingerprinting garbage are developed. This time it pushed under a milestone.
Normally the stats page seems pretty accurate, but I was wondering if something is not correct with these #s?
New unique networks today: 293
New networks today with location: 225
Files parsed today: 434
Queued files waiting to process: 346
And a "Last Post" sorted showing only 2 people have posted new files on 8/23 which will become 8/24 in approx. 20 minutes (EST)?
According to the stats, hratch and mungewell have combined to post 434 files and found 293 new networks? right? Also, I could have sworn Mark571 had something like 58+k new APs found this month a couple of days ago (I'm pretty sure I was third again, something like 3 months in a row). But I guess I could have been dreaming about that last part... scary. I just have this weird feeling something isn't right with the #s is all.
New unique networks today: 293
New networks today with location: 225
Files parsed today: 434
Queued files waiting to process: 346
And a "Last Post" sorted showing only 2 people have posted new files on 8/23 which will become 8/24 in approx. 20 minutes (EST)?
According to the stats, hratch and mungewell have combined to post 434 files and found 293 new networks? right? Also, I could have sworn Mark571 had something like 58+k new APs found this month a couple of days ago (I'm pretty sure I was third again, something like 3 months in a row). But I guess I could have been dreaming about that last part... scary. I just have this weird feeling something isn't right with the #s is all.
My jaw dropped and I'm quite shocked to see the stats whitedice mentions
Guess I'll have to wait some time to see if I'll make it into the first stat page todayFiles parsed today: 434
Queued files waiting to process: 384
Due to batching, the numbers seen there might not be what you would expect during a large processing run.
Damn, I guess driving around with Fake AP running in the backseat is frowned upon here huh?Aye, the number goes down from time to time as better methods of fingerprinting garbage are developed. This time it pushed under a milestone.
I noticed waaay too many APs stacked on top of each other here
http://www.wigle.net/gps/gps/Map/online ... 8533782958
It is a city centre, APs are dense in reality, but not that dense. More likely it was that someone entered location of the city instead actual GPS readout or used some position rounding.
I guess the algorithm could be further improved to detect those
http://www.wigle.net/gps/gps/Map/online ... 8533782958
It is a city centre, APs are dense in reality, but not that dense. More likely it was that someone entered location of the city instead actual GPS readout or used some position rounding.
I guess the algorithm could be further improved to detect those
what you're seeing in that webmap snippet is a rendering artifact, and not actually eleventy points stacked on one another. a query (or use of a real client) shows only one of each offending network.
and yes, the algorithms are pretty much in continuous improvment, even when it makes things worse :-)
and yes, the algorithms are pretty much in continuous improvment, even when it makes things worse :-)
I noticed waaay too many APs stacked on top of each other here
http://www.wigle.net/gps/gps/Map/online ... 8533782958
It is a city centre, APs are dense in reality, but not that dense. More likely it was that someone entered location of the city instead actual GPS readout or used some position rounding.
I guess the algorithm could be further improved to detect those
Actually since my home scanning station never moves, it alsways has the same location. about 20 peers drive by on the highway every day!
Who is online
Users browsing this forum: Bing [Bot] and 4 guests