News: JGAP 3.2 released - Genetic Algorithms and Programming in Java

  1. JGAP is a Genetic Algorithms and Genetic Programming package written in Java. JGAP version 3.2 represents major feature enhancements, including: + Port to Java version 5 (previously also ran on version 4) + Providing a job-based evolution facility, allowing to run your own computing grid + Improvements in the grid logic (especially concerning the architecture) + Better evolution architecture thanks to the new Breeder class + Caching of fitness computation via introduction of business keys + Speedup + Genetic Programming enhancements + A complex Robocode GP example for evolving pure Java code + A lot of new unit tests (currently we count over 1350 unit tests) + Bug fixes with new unit tests exposing the former bugs + A lot more, see the change log This version includes a lot of input from the growing user base of JGAP. We are very happy of that because the heart of JGAP is the community! Feedback from you is always welcome and necessary to still raise the quality of JGAP in the future! This release can be downloaded here: http://sourceforge.net/project/showfiles.php?group_id=11618&package_id=48940 For more information visit the JGAP homepage at http://jgap.sourceforge.net If you are not convinced yet, don't hesitate contacting us in case of any questions, feedback or other suggestions regarding JGAP. You may also take a look at the extensive Javadoc provided with JGAP as well as the examples and the over 1300 unit tests you won't easily find in other open-source projects!
  2. I've been using this in a prototype project and it has prooved to be very good in a stand alone client, but not so good in a multi-threaded environment (e.g. J2EE) as there are thread safety issues in the Configuration object (a static method needs to be called before a instance can be created using the new operator) as well as far too much use of System properties (imho). Definately worth a look and much kudos to the development team, but make sure you perform adequate due diligence if you intend to use this in a production environment. I wouldn't have normally commented, but since this is ServerSide.com I felt I should have pointed out the issue I was having while trying to integrate this in to a J2EE project. I should also mention that I raised these to Klaus who was very responsive in helping me to identify a solution to my personal problems with regards to the issues mentioned, so thanks Klaus!