spawnScan icon indicating copy to clipboard operation
spawnScan copied to clipboard

Not quite finding all spawns in big areas

Open Wouter93 opened this issue 8 years ago • 5 comments

There are clear patterns where no pokemon spawns are found. This only happens in large areas

(See the following picture) http://i.imgur.com/teU9V0O.jpg There are some horizontal lines where no pokemons are found, even though there are definitely pokemons there.

I'm not sure what causes it, but I suspect that workers are jumping too far (from the far right to the far left) when a 'row' is completed- resulting in no pokemons found for a long duration.

Wouter93 avatar Aug 10 '16 13:08 Wouter93

that looks to me like one or more of the threads crashed, what version was this done on, how many workers, and how many steps?

TBTerra avatar Aug 10 '16 13:08 TBTerra

Going back to the log and yeah, it seems like a lot of threads crashed trying to sleep a negative time.

The version was one from ~10 hours ago. Using 100 workers doing 40182 steps covering 391.788141632 km^2

Will try a rescan with your update ^^

Wouter93 avatar Aug 10 '16 13:08 Wouter93

if many threads crashed, i would also change stepsPerPassPerWorker in the config down to 45

TBTerra avatar Aug 10 '16 13:08 TBTerra

I'll try that.

On a side note, the time for doing a 'pass' seems to increase a lot sometimes. Some workers take 400 seconds to do a pass, while others take a whopping 1700 seconds

Wouter93 avatar Aug 10 '16 15:08 Wouter93

hmm, passes should take 500-600 seconds, lower numbers tend to mean its the tread that got all the oddments not done by the others, but numbers that high are concerning (anything over 900 is definitely not getting all the spawns)

TBTerra avatar Aug 10 '16 15:08 TBTerra