-
Notifications
You must be signed in to change notification settings - Fork 36
Home
This space is for managing the development of the server for the Power TAC competitive simulation. Please feel free to add material to existing pages or to create new pages.
This space is for discussing and communicating design and implementation details of the server. At the powertac.org site you will find an overview and public wiki that is primarily focused on the needs of potential participants.
-
Issues: We use the powertac-server issue-tracker for tracking issues across all elements of the project. All other modules should have their issue-trackers disabled; if some do not, it's a mistake.
-
Discussions: Please subscribe to the developers mailing list at http://power-tac-developers.975333.n3.nabble.com/.
-
Papers: Can be found at http://www.powertac.org.
-
Data: Ryan and Erik have written up info on accessing public weather data and wholesale price data.
-
Javadoc: We are now using Doxygen to generate documentation on the Minnesota Jenkins CI server. Since the common module is built separately (so brokers can depend on it without sucking in server code), it's in two pieces, although the server also contains common to ease navigation.
-
Continuous integration We use the Jenkins CI platform at Minnesota to run a continuous integration process. Each time the master branch of a module is updated, it will be pulled into jenkins and rebuilt, and all tests run. This system also generates up-to-date javadocs using doxygen.
Find out how to set up a development environment and hook up to the various tools that we use to share and coordinate our work.
Coding/Documentation guidelines, issue tracking, testing and committing code.
Discussion of game design on the participant's wiki. Mostly older material.
Details on the structure of the Power TAC software system.
Information about the various models that are part of the Power TAC simulation
Who is working on what?
Older content, mostly obsolete