RoboJogger is a user interface for RoboRunner. RoboJogger together with RoboRunner provide functionality similar to that of RoboResearch -- the ability to run robots in challenges for the purpose of testing, diagnostics, and comparison -- but with a few distinct differences. The primary advantage of Robojogger/RoboRunner is that RoboRunner uses the Robocode API to run battles rather than running Robocode through a runtime execution for each battle, reducing the amount of time it takes to run a challenge.
RoboJogger is currently being developed by Skotty.
- 1 Downloads
- 2 Version Compatibility
- 3 Development Progress
- 4 RoboJogger Version Notes
- 5 Screenshots
Versions prior to 1.0 may still have issues but are available for review to anyone who is interested. If you do try it, feedback is welcomed. Should interest in this exist and grow, I'll look into hosting it from someplace more official; for now, it's just a ZIP of jars and files hosted off my personal website.
- RoboRunner -- Packaged with a custom version of RoboRunner 1.2.3 that is currently dubbed as RoboRunner 184.108.40.206.
- Robocode -- Known to work with Robocode 1.7.3.x. Not yet tested on other versions, but likely works with many versions up to current.
- Java -- Requires version 1.6+ for most platforms. On Mac, with the current build, RoboJogger may not work with any Java version other than a recent copy of 1.6. With 1.7, my understanding is that Apple turned Java over to Oracle, and I am unsure whether or not the Apple Java Extensions used in RoboJogger will function properly, or if they will need to be removed for 1.7+.
The RoboJogger UI is being built using Skotty's existing Swing codebase as a starting point. This means some of the background code may not be entirely clean or relevant, but it will speed development considerably.
At present, there is no licensing restrictions on any of the code, as it is all written entirely by Skotty and Skotty generally doesn't bother with licenses for his own code. However, some kind of open source license may be applied to RoboJogger before it is released, provided there is any desire for such.
RoboJogger is initially set up for using Robocode 220.127.116.11. If you switch Robocode versions when running Setup, you will have to manually copy the correct robocode.jar file into the robocode_jars folder that RoboJogger uses (you will be prompted about this in the program when you run Setup). Part of the issue is that the setup function is part of the application rather than a separate script as in RoboRunner, and I therefore cannot specify a classpath via the command line like RoboRunner itself does. Instead, RoboJogger uses robocode jars from a folder named robocode_jars. When setting up with a new version, most of the jars are automatically copied into this folder, but the robocode.jar file cannot be. When RoboJogger is running, robocode.jar is in use and cannot be automatically replaced. Thus the required manual copy.
As of 0.9.7, there are still no on-the-fly results. To see the latest results, you have to close any open results summary windows and reopen them, such that they pull the latest data from the RoboRunner score log files. Also, RoboJogger calculates confidence values itself. Confidence values for individual robots will match what RoboRunner calculates, but confidence values for challenge groups and overall total will not be the same. The method RoboJogger uses is not the same as what RoboRunner uses. This will likely change in a later version. A more detailed look at computing confidence is shown in a later section.
A quick explanation of what some of the jars in RoboJogger are:
- robojogger.jar -- the main RoboJogger classes
- core.jar -- generic set of Swing classes RoboJogger relies on; this could be trimmed down to only what is needed when 1.0 comes out
- zenput.jar -- input validation classes that RoboJogger uses
- applestub.jar -- stub classes that match the signature of the Apple Java Extensions classes used on Macs; this jar is included on the non-Mac version to prevent class not found exceptions.
- roborunner-18.104.22.168.jar -- slightly modified version of RoboRunner 1.2.3 used by RoboJogger
- guava-12.0.1.jar -- used by RoboRunner 1.2.3
- log4j-1.2.11.jar -- logging engine used by RoboJogger
Confidence interval calculations are based on the assumption that data points will match a certain type of distribution. Whether it is the best match or not, both RoboRunner and RoboJogger currently assume scores against a robot will follow a normal distribution. Furthermore, both RoboRunner and RoboJogger use a 95% confidence interval, meaning with a large number of repeated samples, 95% of the calculated confidence intervals would include the true value of the parameter.
For battles against a single robot, the confidence interval calculation is reasonably simple, and both RoboRunner and RoboJogger calculate this value in the same way: X +/- 1.96 * d / sqrt(n), where X is the average of all scores, d is the standard deviation, and n is the number of battles.
However, how to calculate the confidence for a group or for the total is a more complicated question. RoboJogger and RoboRunner take differing approaches for this.
For RoboJogger, group and total confidence intervals are determined by using a single data point for each season. For example, if you had a completed challenge with 10 seasons, an average for each season would be computed, giving 10 averages that then serve as data points for the computed confidence interval.
This becomes further complicated when using smart battles, as then there will be a differing number of battles for each robot in the challenge. In this case, RoboJogger pads the number of battles for robots with fewer battles by creating fake random scores for those robots where the random scores are obtained by randomly choosing a score that falls within the confidence interval for that specific robot.
RoboJogger Version Notes
Version 1.0 (Planned)
First real non-beta release! This will be released once 0.9.8 has been thoroughly tested and any remaining bugs ironed out.
- Fix any remaining outstanding issues.
Version 0.9.8 (Planned)
- Improved melee support.
- Add on-the-fly battle results (requires RoboRunner update).
- Fixed major bug where first start of RoboRunner after executing Setup would fail to launch properly.
- RoboJogger now ensures RoboRunner has been cleanly shut down before starting a new RoboRunner or exiting.
- Added preference "Additional Bots Directory". Any challenge robots not in the RoboJogger bots directory will be pulled from this directory if possible. A typical usage of this would be to set the directory to your RoboRumble robots directory.
- RoboRunner output dialog is no longer always on top of the main window.
- RoboRunner progress bar now spans the width of the window instead of being a fixed size, and has a slightly changed appearance when RoboRunner is not running.
Prior to 0.9.7, there was a somewhat rare bug where a score log would lose some (usually most) of it's battle scores. This may have been fixed with the changes to ensure RoboRunner is shut down cleanly. However, I can't be certain, so please let me know if you encounter this bug with 0.9.7. I will be holding off on researching this further under the assumption that it is fixed until such time that someone loses data again.
- Challenge runs table now allows multiple interval selection to make moving and deleting groups of challenge runs less tedious.
- Challenge run table now includes columns for seasons completed, battles completed, and battles total. As previously, right-click heading row to toggle columns on and off.
- Subtotal columns in the result summary and detail windows are now highlighted with a light green background.
- Added new preference "Use Subtotal Group Names". When selected, column headings for subtotals in the result summary and detail tables will use the group names (if available) from the challenge file instead of generic names Sub1, Sub2, etc.
- Total battles completed for each challenge run is now stored in the RoboJogger settings file so that Score Logs for every challenge run do not have to read on startup.
- Replaced RoboJogger image with an improved version provided by Chase.
- Subtotals and overall total on a season by season basis is now shown on the result details window.
- Completion percentages are now shown using floor function everywhere instead of round.
- Removed "BATTLE COMPLETED" message from appearing in RoboRunner output window.
- Changed from using jdesktop Java 5 backported SwingWorker class to launching Java SwingWorkers in a cached thread pool. The backport is not required and the cached thread pool takes care of Java bug 6880336.
- Added new splash screen.
- In RoboRunner, the XMLEventReader and GZIPInputStream are now closed after a ScoreLog is loaded.
- Added a basic output parser for RoboRunner. Challenge run progress information in the main window is now updated on the fly; however, result windows must still be closed and reopened to pick up updated data.
- When challenge run completion information is updated for a challenger, challenge completion information is now updated for all challenge runs with the same challenger.
- Fixed nasty bug where clicking the close button instead of either the OK or Cancel button on the New Challenge window could cause an exception that would corrupt the list of Challenge Runs.
- Added ability to run with the "-clean" parameter that will attempt to remove any invalid challenge runs from the challenge runs list. Use this if a prior version corrupted your data and RoboJogger won't start properly.
- Challenge table challenge completion information is now updated when RoboRunner is manually stopped.
- Challenge table challenge completion information is now updated when the number of seasons for a challenge run is changed.
- Added reentrant lock synchronization to the RoboRunner ScoreLog load and save methods to help prevent score log corruption.
- Added some additional exception handling so that RoboJogger can still run when there are corrupt score logs.
- Fixed bug where having score results for challenges with different numbers of rounds would result in unmodifiable exception.
- Fixed typo on enum where "PERCENT_SCORE" was accidentally typed as "PRECENT_SCORE". This resulted in being unable to create new PERCENT_SCORE challenges unless the challenge name was typed to match the misspelling.
- Delete challenge confirmation prompt now shows the standard challenge run title.
- Fixed bug where battle scores were not filtered to ensure only battle scores with the same number of rounds as the challenge were used.
- Fixed bug where challenge run completion percentage did not change to 100% after challenge run was completed.
- Score type values AVERAGE_BULLET_DAMAGE and AVERAGE_ENERGY_CONSERVED are now recognized.
- Scores for all scoring types should now be correct (hopefully).
- Added option to create Wiki formatted text to the result summary window popup menu.
- Added preference for Author name used with Wiki formatted text.
- Reduced distribution size further by eliminating duplicate jars.
- Added ability to show custom Descriptions for Challenge Runs.
- Added ability to edit Challenge Runs (though Robot and Challenge cannot be changed)
- Columns in the Challenge Run table on the main window can now be toggled on and off using a popup menu on the table header.
- Column sizes, order, and visibility in the Challenge Run table is now saved on exit and restored on startup.
- Fixed bug where Robot would fail to load if the Robot jar file contained multiple .properties files.
- Added new window for setting preferred Look and Feel. If no preference is set, the system Look and Feel is used.
- Fixed bug where some functions were not properly re-enabled after RoboRunner finished processing all challenges.
- Fixed bug where RoboRunner threads would remain active and continue to consume CPU after stopping RoboRunner.
- Only prompt user about replacing robocode.jar on setup if robocode.jar changes (rather than prompting for every version change).
- Reduced the packaged copy of Robocode to the bare minimum to reduce distribution size.
Some generic notes on RoboJogger:
- All errors and a few information messages are logged to the file robojogger.log.
- On first run (or any time the robocodes folder is empty), the RoboRunner setup window will appear automatically on launch. However, you can run setup anytime by lauching it through the Tools menu.
- Robocode version 22.214.171.124 is currently packaged with RoboJogger, and that version serves as the default when you run RoboRunner setup.
- If you change the version of Robocode when running RoboRunner Setup, you will have to manually copy the robocode.jar file from the new version of Robocode into the robocode_jars folder. You will be prompted about this by the program.
- All robots must be in the bots directory. When adding a new challenge, robots listed as part of the challenge must be in the bots directory, but the robot selected to participate in the challenge will be automatically copied into the bots directory if it is not already there.
- Development robots are not currently supported.
- Popup menus exist for the challenge run table on the main window and for the challenge result windows that show the score summary. This is particularly important to know for the challenge result windows, as at the moment the popup menu is the only way to access the challenge result detail window that shows results for every season.
- When RoboRunner is running, incomplete challenges will be processed from the top of the challenge run table to the bottom, until RoboRunner is stopped or no incomplete challenges remain.
- Currently distributed as a simple ZIP archive, but later can provide installer for Windows and .app for Mac if desired.
Main RoboJogger window (version 0.9.5). When RoboRunner is started, it will begin running any incomplete challenges in the table of challenges one at a time, starting from the top of the table, until all challenges have been completed.
(side note: the total seasons in this screenshot for each challenge is quite low because at the time I was running challenges that had over 250 robots each, and my older PC can only run about 7500 battles per day; the challenges in this screenshot represent about 2 solid days of execution on my PC; there is an advantage to this approach in that you can see the results of a lot of different challenges more quickly and you can always go back and edit the challenge runs to add more seasons)
Dialog for running RoboRunner setup. Currently accessed via menu: Tools -> Run Setup.
Dialog for adding a new challenge (version 0.9.7). Currently accessed via button on main window, menu item in popup menu over table, or in the main menu under: File -> New Challenge.
Window showing summary of battle results. At present, it uses the top row to show scores, and the second row to show confidence in the scores. Center data area is separate and scrollable to better handle huge challenges (suggested by Voidious).