search

PokemonGoers / PredictPokemon-2

In this project we will apply machine learning to establish the TLN (Time, Location and Name - that is where pokemons will appear, at what date and time, and which Pokemon will it be) prediction in Pokemon Go.
Apache License 2.0
9 stars 3 forks source link

URGENT: Integration with PokeData #67

Closed gyachdav closed 7 years ago

gyachdav commented 7 years ago

This issue is a status update request and an urgent call to complete the integration with project A so we can move ahead with the launch.

Please make here a task list and tick completed steps so we will know what is needed in order to complete this integration.

@semioniy @bensLine @MatthiasBaur @Aurel-Roci

Aurel-Roci commented 7 years ago

Since we are going to provide a npm package for the predictions, what is needed from team A is adding java in the docker container, since we are using java to run the weka file for the predictions.

jonas-he commented 7 years ago

Java is done. Apart from that only adding a dependency is not gonna cut it right? we'll need to add a new API route, which then listens on prediction requests and calls something like a predict(lat, lng, timestamp) function from your package. However i didnt find such in the description here https://www.npmjs.com/package/predict-pokemon

Aurel-Roci commented 7 years ago

Thanks for letting me know, I will add that to the description. You can find it here the way it works. https://github.com/PokemonGoers/PokeData/issues/183

bensLine commented 7 years ago

@jonas-he fyi, we have to adapt the URL when the 6GB database is available. Besides, you need to unzip the json/pokestop_groups.7z file in the prediction npm package in order to use it. And it takes a while to initialize the module.

gyachdav commented 7 years ago

It has been 13 days since this issue was open with the label URGENT and the last response here is 10 days old... We need an answer here about status ASAP! aka As Soon As Possible! 😡

@PokemonGoers/pokedata

Aurel-Roci commented 7 years ago

@gyachdav The only reason this issue is kept open, is so that if team A has any further questions on the predictions the can ask here. The integration is done.

gyachdav commented 7 years ago

This is not how it should be handled. If this is done then the issue is closed. If project A has some questions they are welcome to open a new issue label it "questions" and reference this issue if needed.

Now, if this is done - is there a demo where we can see the integration actually working?