The Google App Engine (GAE) service in this repository is the Botleague Problem Endpoint for all problems that use the Deepdrive simulator.
This app works in conjunction with the problem-coordinator and problem-worker.
Communication between these apps happens via Firestore.
This endpoint's responsibility is to implement the Botleague problem API for Deepdrive. Jobs are managed by the problem-coordinator on GCE which is an event loop that starts instances and assigns eval jobs to them.
The problem-worker processes run on the large instances alongside the sim or bot container and deal with those containers' local lifecycles.
The endpoint, coordinator, and worker have all been designed so that you could easily re-use them for another problem on GCP, say vehicle detection, by changing constants.py and instance config JSON files.
As Botleague is problem agnostic, all communication with the problem endpoint, coordinator, etc... happens through the endpoint. Obviously this means Botleague should not access the Problem endpoint database and visa versa, even though this is technically possible within the Deepdrive problem endpoint implementation.
pip install -r requirements.txt
See Makefile
If you want GAE to use a different BOTLEAGUE_LIAISON_HOST that the default,
i.e. liaison.botleague.io, just set BOTLEAGUE_LIAISON_HOST in the eval
config db, e.g. <problem-endpoint-name>_eval_config.
Copyright © 2019, Deepdrive. Licensed under the MIT License, see the file LICENSE for details.