Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not quite finding all spawns in big areas #26

Open
Wouter93 opened this issue Aug 10, 2016 · 5 comments
Open

Not quite finding all spawns in big areas #26

Wouter93 opened this issue Aug 10, 2016 · 5 comments

Comments

@Wouter93
Copy link

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.

@TBTerra
Copy link
Owner

TBTerra commented Aug 10, 2016

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?

@Wouter93
Copy link
Author

Wouter93 commented Aug 10, 2016

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 ^^

@TBTerra
Copy link
Owner

TBTerra commented Aug 10, 2016

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

@Wouter93
Copy link
Author

Wouter93 commented Aug 10, 2016

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

@TBTerra
Copy link
Owner

TBTerra commented Aug 10, 2016

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants