Code Monkey home page Code Monkey logo

Comments (2)

Bytekeeper avatar Bytekeeper commented on June 26, 2024

Essentially the whole database.
I might reconsider this in the future, but for now I won't do it. For one, there's the problem with huge data packages which will require some special method of distribution (unless I want to clogg my vserver).
Then, I'd like to know what is done with the data and if results will be shared with the community again. I'd rather add more graphs and aggregations for everyone than provide data that is only used by small portion of the community.
That doesn't mean I won't hand out a snapshot of all the data, but not often and especially not on regular intervals.

from basil.

chriscoxe avatar chriscoxe commented on June 26, 2024

Ok, thanks for considering it. FYI, the main use cases for me when I am developing my bot would be to:

  • Know who won for games that lasted 60 minutes (i.e. based on in-game scores), because in this scenario, the bot itself has no way of knowing this (it's adjudicated based on in-game score after each bot's onEnd() method finished).
  • To get the detailed data for the number of the various timeouts (e.g. number of 1 second timeouts, number of 85 milliseconds timeouts, etc). The Tournament Manager software doesn't provide this to bots.
  • Find out the context of games where my bot crashed/timed out. Especially to be able to identify and get a copy of the replay file produced by the opponent's bot (to see which map, which opponent, and what happened in the game), or at least know the map and opponent then attempt to reproduce the problem locally. If my bot crashed or timed out while starting up, it might have been before it wrote information about the map & opponent etc to the write folder, and also my bot wouldn't have written a replay file.
  • To look for patterns in the history of the data where my bot performed badly, e.g. periods when losing a lot for particular maps or opponents (or combination of opponent and map), or after a particular update of my bot or an opponent bot. My bot writes info to the write folder that I could analyze instead I suppose, but I expect this would be useful to other bot authors that don't record this info or not at this level of detail.
  • Similarly, to look for turning point in the history when my bot learned a way to consistently beat a particular opponent, or vice versa, then see what each bot started doing (e.g. started using a particular build order/strategy, or an update that added new functionality that helped a lot).

from basil.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.