-
Notifications
You must be signed in to change notification settings - Fork 0
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
Solution DB #10
Comments
Please, make sure that it is possible to trace for any given solution which solver it came from, because, I think, it will not be uncommon to have a multitude of slightly tweaked versions of the same solver and it is good to know which ones of them are better. |
Yes, I have ideas for that. |
To view them, start the dashboard locally. There is even "integration" with their model viewer, so you don't have to click "Choose file"! Now working on |
Solution DB done. Now working on solver runner. |
Integrating new solvers
Local development
This command will run your solver on all problems. Results are printed to the screen but not uploaded to the DB. This is convenient to weed out initial bugs without polluting the DB with too much failed attempts. Once the solver is more or less ready, move on to Running solver worker
It will take all your cores to run specified solver on all available tasks. Solutions and failed attempts will be saved in the DB. Troubleshooting solver_workerStart the dashboard, find your last invocation in the Gathering the solutions
It will grab the best solution for every problem from the DB, create zip archive and print it's SHA256. |
problems
andsolutions
.submission.zip
I will do this because I have experience setting up the Car&Fuels prototype.
The text was updated successfully, but these errors were encountered: