* TODO.html, README.html: Remove these old files.
* AUTHORS, COPYING, ForRelease, NEWS, ToDo: Update for release. * eo.cfg (PROJECT_NUMBER): Bump version to 1.0
This commit is contained in:
kuepper
parent
51d6ddc239
commit
0afa0b9fa4
11 changed files with 51 additions and 165 deletions
|
|
@ -5,4 +5,4 @@ Gustavo Romero Lopez
|
|||
Maarten Keijzer
|
||||
Marc Schoenauer
|
||||
Jeroen Eggermont
|
||||
|
||||
Jochen Küpper
|
||||
|
|
|
|||
|
|
@ -500,5 +500,3 @@ necessary. Here is a sample; alter the names:
|
|||
Ty Coon, President of Vice
|
||||
|
||||
That's all there is to it!
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,9 @@
|
|||
2006-12-18 Jochen Küpper <jochen@fhi-berlin.mpg.de>
|
||||
|
||||
* TODO.html, README.html: Remove these old files.
|
||||
|
||||
* AUTHORS, COPYING, ForRelease, NEWS, ToDo: Update for release.
|
||||
|
||||
2006-12-17 Jochen Küpper <jochen@fhi-berlin.mpg.de>
|
||||
|
||||
* README: Better links to Templates/
|
||||
|
|
|
|||
|
|
@ -1,14 +1,16 @@
|
|||
In oder to create a new release from the current cvs sources perform
|
||||
the following steps:
|
||||
In order to create a new release from the current cvs sources perform the
|
||||
following steps:
|
||||
|
||||
- Set version number in configure.in and doc/eo.cfg.
|
||||
- Set version number in configure.in and doc/eo.cfg
|
||||
- Check/update NEWS file, set release date and version in NEWS.
|
||||
- Run `make check && make dist`.
|
||||
- Test distribution (unpack, configure, make check).
|
||||
- Put distributions at SourceForge.
|
||||
- Post news on SourceForge project-page.
|
||||
- Send announcement to mailing lists.
|
||||
- Bump version number to next x.y.z-cvs in configure.in and doc/eo.cfg.
|
||||
- Run `make check && make dist`
|
||||
- Test distribution (unpack, configure, make check)
|
||||
- Tag released code in cvs, in order to allow a branch to be created at that
|
||||
version if the necessity will arise later
|
||||
- Put distribution files at SourceForge
|
||||
- Post news on SourceForge project-page
|
||||
- Send announcement to mailing lists
|
||||
- Bump version number to next x.y.z-cvs in configure.in and doc/eo.cfg
|
||||
|
||||
# Local Variables:
|
||||
# coding: iso-8859-1
|
||||
|
|
|
|||
|
|
@ -8,23 +8,23 @@ if USE_TUTORIAL
|
|||
SUBDIRS_TUT = tutorial
|
||||
endif
|
||||
|
||||
SUBDIRS = src doc contrib win $(SUBDIRS_APP) $(SUBDIRS_TUT) test
|
||||
SUBDIRS = src doc contrib win $(SUBDIRS_APP) $(SUBDIRS_TUT) test
|
||||
|
||||
|
||||
# Directory for documents
|
||||
DOCDIR = ~/public_html/eodocs
|
||||
DOCDIR = ~/public_html/eodocs
|
||||
|
||||
# Directory for indices -- not useful for the user
|
||||
IDXDIR = ~/index
|
||||
IDXDIR = ~/index
|
||||
|
||||
|
||||
# Add documentation to distribution
|
||||
dist-hook:
|
||||
$(MAKE) documentation
|
||||
$(INSTALL_DATA) -d $(srcdir)/doc/html $(srcdir)/doc/latex $(srcdir)/doc/man $(distdir)/doc/
|
||||
$(MAKE) documentation
|
||||
$(INSTALL_DATA) -d $(srcdir)/doc/html $(srcdir)/doc/latex $(srcdir)/doc/man $(distdir)/doc/
|
||||
|
||||
# Prepare documentation
|
||||
documentation:
|
||||
cd doc && $(MAKE) doc && cd ..
|
||||
cd doc && $(MAKE) doc && cd ..
|
||||
# convinience-target
|
||||
doc: documentation
|
||||
doc: documentation
|
||||
|
|
|
|||
6
eo/NEWS
6
eo/NEWS
|
|
@ -1,9 +1,11 @@
|
|||
* release 1.0 (not yet released)
|
||||
- Implement CMA-ES.
|
||||
- Update introductory pages of documentation and webpage.
|
||||
- Add Microsoft Visual C++ project support files (for Visual Studio 2003 and 2005)
|
||||
- Upgrade Teamplates/ script to create a complete standalon EO project (using autotools)
|
||||
- Remove support for pre-standard C++ compiler (i.e. gcc-2.x), which allows to
|
||||
clean up the code considerably. Assume availability of sstream and limits.
|
||||
- Add Microsoft Visual C++ project support files
|
||||
clean up the code considerably.
|
||||
Assume availability of sstream and limits.
|
||||
|
||||
* release 0.9.3z.1 (1. Oct. 2005)
|
||||
- Support gcc-3.4 and gcc.4.x.
|
||||
|
|
|
|||
115
eo/README.html
115
eo/README.html
|
|
@ -1,115 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.05 [en] (X11; I; Linux 2.0.30 i586) [Netscape]">
|
||||
<META NAME="Author" CONTENT="J.J. Merelo">
|
||||
<TITLE>EO evolutionary computation framework</TITLE>
|
||||
<STYLE TYPE="text/css">
|
||||
<!-- /* Style Sheet definitions need to be commented to hide them from incompatible Browsers.*/
|
||||
/*hotdog style name="NUEVOH2"*/
|
||||
H2 {
|
||||
font-family: Arial,Helvetica;
|
||||
color: #FFFFCC;
|
||||
background: #000077;
|
||||
}
|
||||
/* End Style Sheet commenting. */ -->
|
||||
</STYLE>
|
||||
|
||||
</HEAD>
|
||||
<BODY TEXT="#000077" BGCOLOR="#FFFFCC" LINK="#0000EE" VLINK="#551A8B" ALINK="#FF0000">
|
||||
|
||||
<CENTER>
|
||||
<H1>EO Evolutionary Computation Framework and Library</H1></CENTER>
|
||||
|
||||
EO (Evolvable|Evolutionary objects) is a C++ toolbox for evolutionary computation which defines interfaces for
|
||||
many classes of algorithms used in evolutionary computation, and, at the
|
||||
same time, provides some examples that use those interfaces. The client/user
|
||||
can include those objects in his or her programs, or create their own. If new objects are created, the GeNeura team commit themselves to test them, and make them available
|
||||
to the Evolutionary Computation community. In this way, no changes have
|
||||
to be made to the library design or to a program that implements an EC algorithm: just new classes added. Our intention would be that, in the future, somebody implementing an EC algorithm would say "I am using EO, plus a class that hs been made publicly available", improving repeatability of EC results and easing its availability.
|
||||
<BR>EO uses STL, and ANSI C++. So far, it has been tested and works
|
||||
with gcc 2.8.1 and egcs 1.0.2 in Linux, Irix, Win95/NT (with Cygwin) and
|
||||
Solaris Machines, and with Visual C++ 5.0 in WinNT machines. Makefiles for Unix and project
|
||||
files and makefiles for NT are provided.
|
||||
|
||||
|
||||
<h2>Installing EO and compiling examples in UNIX</h2>
|
||||
To start and use it, first you can untar or unzip it (depending on the distribution you got), by doing,
|
||||
<BR><TT>bash$ zcat eo-0.6.tgz | tar xvf -</TT><BR>
|
||||
or
|
||||
<BR><TT>bash$ unzip eo-0.6.zip</TT></P>
|
||||
<P>
|
||||
Once everything is decompressed to the eo-0.6 directory (or whatever), <TT>cd</TT> to it and type
|
||||
<BR><TT>bash$ configure</TT><br>
|
||||
or
|
||||
<BR><TT>bash$ configure --prefix=/my/fav/directory</TT><br>
|
||||
if you intend to use it from another directory. If you do so, you´ll have then to copy manually all the <TT>.h</TT> and <TT>.a</TT> files to it. Right now, EO is mostly templates-based, so it has mainly got header files, plus a small and independent utility library.</P>
|
||||
<P> After that, type
|
||||
<BR><TT>bash$ make</TT>
|
||||
<BR>This makes the object and library files needed, makes the examples
|
||||
in the <TT>apps/examples</TT> directory, and builds the genetic mastermind
|
||||
application in the <TT>apps/master</TT> directory. If anything goes wrong at this stage, e-mail us. It should work properly with the compilers mentioned so far.
|
||||
</P>
|
||||
<p>Then, to unzip the documentation
|
||||
<BR><TT>bash$ make docunzip</TT>
|
||||
<BR>which unzips the HTML documentation into the <TT>doc</TT> directory.</p>
|
||||
<P>If there is any problem, write to any of the addresses below, or
|
||||
just do
|
||||
<BR><TT>bash$ make bug-report</TT>
|
||||
<BR>and tell us your problem, indicating EO release, the C++ compiler you
|
||||
are using, and the platform.
|
||||
</P>
|
||||
|
||||
<h2>Installing EO and compiling examples in Win95/NT</h2>
|
||||
|
||||
Unzip the library to your favorite directory by double-clicking on the eo-0.6 icon, and then load <tt> apps/examples/examples.dsw </tt> or <tt>
|
||||
apps/examples/master.dsw </tt> workspaces; then define the main
|
||||
directory you installed it to as default include directory (in
|
||||
tools->directories or somesuch) and press F7 for compiling. Alternatively, if you favor makefiles, change into the apps/examples directory and run<br>
|
||||
<TT>C:\my\dir\eo-0.6\apps\examples> nmake /f examples.mak</TT><BR>
|
||||
which will create debug executables for all the examples. </P>
|
||||
|
||||
<P> In the CygWin environment, everything should work in the same way as in UNIX, but for a couple of things. To run configure, type<br>
|
||||
<tt>bash$ sh ./configure</tt>, or, much better, create a <TT>\bin</TT> directory and copy sh.exe to it; that way, shell scripts will work properly.</P>
|
||||
|
||||
<h2>Availability</h2>
|
||||
The latest versions of EO are always available from <A HREF="http://geneura.ugr.es/~jmerelo/eo ">http://geneura.ugr.es/~jmerelo/eo</A>
|
||||
and <A HREF="ftp://geneura.ugr.es/pub/eo">ftp://geneura.ugr.es/pub/eo. </A>
|
||||
|
||||
|
||||
<H2>Working with EO</H2>
|
||||
For a quick dive into the eo library, check the <A HREF="http://geneura.ugr.es/~jmerelo/eo/ASimpleGeneticAlgorithm.html">SGA</A>
|
||||
<BR>Then go ahead to the <A HREF="http://geneura.ugr.es/~jmerelo/eo/DefiningGAstheeasyway.html">EasyGA,</A>
|
||||
which is a more flexible implementation of a Genetic Algorithm.
|
||||
<BR>Then, why not, see how EO implements Simulated Annealing in <A HREF="http://geneura.ugr.es/~jmerelo/eo/EOSimAnnAlg.html">EOSimAnnAlg</A>. If you have unzipped the documentation, there should be also <A HREF="doc/index.html">local copies</A> of these files.
|
||||
|
||||
|
||||
<H2>Tell us something!</H2>
|
||||
If you have any problem, have created a new class, or just want to
|
||||
tell us something, write to <A HREF="mailto:eo@kal-el.ugr.es">eo@kal-el.ugr.es</A>.
|
||||
The eo mailing list is hosted by OneList,
|
||||
<a href="http://www.onelist.com/subscribe.cgi/eodev">
|
||||
<img src="http://www.onelist.com/join.gif" height=36 width=72>
|
||||
[Click to subscribe to eodev@onelist.com].
|
||||
</a>
|
||||
|
||||
<HR WIDTH="100%">
|
||||
|
||||
<H2>Legal Stuff</H2>
|
||||
EO is free and free distribution; however, if you include parts of EO in
|
||||
a commercial product, you have to request authorization from us.
|
||||
<BR>The usual things apply too. If it does not work, if your wife or dogs
|
||||
abandons you, or your room humector stops working, it's not our fault.
|
||||
<BR>
|
||||
|
||||
<HR WIDTH="100%">
|
||||
<CENTER><Form method="POST" ACTION="http://geneura.ugr.es/cgi-bin/jj/mysearch.pl">
|
||||
Search EO documentation <inPUT NAME="busca"><Input TYPE="submit" VALUE="Search">
|
||||
<input type=hidden name=indexPath value="/home/jmerelo/index/eo.idx">
|
||||
<input type=hidden name=origPath value="/home/jmerelo/public_html/eo">
|
||||
<input type=hidden name=mappedPath value="http://geneura.ugr.es/~jmerelo/eo">
|
||||
<input type=hidden name=pageTemplate value="/home/jmerelo/public_html/search_eo.html">
|
||||
</Form></CENTER>
|
||||
<HR WIDTH="100%">
|
||||
</BODY>
|
||||
</HTML>
|
||||
28
eo/TODO.html
28
eo/TODO.html
|
|
@ -1,28 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>TODO list for EO</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>TODO list for EO</h1>
|
||||
<ul>
|
||||
<LI>Provide a way to easily manipulate the algorithm in runtime, be it
|
||||
from grafically or text; expand command-line capabities?
|
||||
<LI>Provide a graphical interface for Windows, in VC++ or BBuilder.
|
||||
<LI>Creare more examples of the objects of which there is only one instance:
|
||||
algorithms, evaluators. Try to adapt most well-know algorithms to EO
|
||||
<LI>Integrate the gTK interface seamlessly in the library.
|
||||
<LI>Complete documentation.
|
||||
<LI>Try to implemente as algorithms the best known paradigms: Evolution Strategies, Evolutionary programming.
|
||||
</ul>
|
||||
|
||||
|
||||
<hr>
|
||||
<address><a href="mailto:jmerelo@kal-el.ugr.es">Juan Julian Merelo Guervos</a></address>
|
||||
<!-- Created: Wed May 13 11:06:58 CEST 1998 -->
|
||||
<!-- hhmts start -->
|
||||
Last modified: Wed May 13 11:12:34 CEST 1998
|
||||
<!-- hhmts end -->
|
||||
</body>
|
||||
</html>
|
||||
17
eo/ToDo
Normal file
17
eo/ToDo
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
An old TODO list for EO (from 1998):
|
||||
|
||||
Provide a way to easily manipulate the algorithm in runtime, be it
|
||||
from grafically or text; expand command-line capabities?
|
||||
|
||||
Provide a graphical interface for Windows, in VC++ or BBuilder.
|
||||
|
||||
Creare more examples of the objects of which there is only one
|
||||
instance: algorithms, evaluators. Try to adapt most well-know
|
||||
algorithms to EO
|
||||
|
||||
Integrate the gTK interface seamlessly in the library.
|
||||
|
||||
Complete documentation.
|
||||
|
||||
Try to implemente as algorithms the best known paradigms: Evolution
|
||||
Strategies, Evolutionary programming.
|
||||
|
|
@ -1,3 +1,7 @@
|
|||
2006-12-18 Jochen Küpper <jochen@fhi-berlin.mpg.de>
|
||||
|
||||
* eo.cfg (PROJECT_NUMBER): Bump version to 1.0
|
||||
|
||||
2006-12-03 Jochen Küpper <jochen@fhi-berlin.mpg.de>
|
||||
|
||||
* mainpage.html: update, add link to Niko Hansen's comparison
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ PROJECT_NAME = EO
|
|||
# This could be handy for archiving the generated documentation or
|
||||
# if some version control system is used.
|
||||
|
||||
PROJECT_NUMBER = 0.9.4-cvs
|
||||
PROJECT_NUMBER = 1.0
|
||||
|
||||
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
||||
# base path where the generated documentation will be put.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue