The Events File
The events file controls events that need to occur throughout the course of
a run. This includes the output of data files as well as active events that
effect the population (such as extinction events or changes to the mutation
rate). This is not a complete list, but should include all of the most
used and useful events.
File Formats
This file consists of a list of events that will be triggered either singly
or periodically. The format for each line is:
type timing event arguments
The type determines what kind of timings the event will be based off
of. This can be immediate [i], based on update [u], or based
on generation [g].
The timing should only be included for non-immediate events. If a
single number is given for timing, the event occurs at that update/generation.
A second number can be included (seperated by a colon ':') to indicate how
often the event should be repeated. And if a third number is listed (again,
colon seperated) this will be the last time the event can occur on. For
example, the type and timing "u 100:100:5000" would indicate that the
event that follows first occurs at update 100, and repeats every 100 updates
thereafter until update 5000. A type timing of "g 10:10" would cause the
event to be triggered every 10 generations for the entire run.
The event is simply the name of the event that we want to trigger,
and the arguments detail exactly how it should work when it is
triggered. Each event has its own arguments.
Some examples:
i pause
Pause avida as soon as the run first starts.
|
u 100:100 print_average_data
Print out all average measurements collected every one hundred updates,
starting at update 100.
|
g 10000:10:20000 print_data dom_info.dat
update,dom_fitness,dom_depth,dom_sequence
Between generations 10,000 and 20,000, append the specified information to
the file "dom_info.dat" every ten generations. Specifically, the first
column in the file would be update number, second is the fitness of
the dominant genotype, followed by the depth in the phylogentic
tree of the dominant genotype, and finally its genome sequence.
|
Output Events
Output events are the primary way of saving data from an avida experiments.
The main two types are continuous output, which append to a single file
every time the event is trigged, and singular output, which produce
a single, complete file for each trigger.
Analysis Events
Analysis events use data from the current state of avida, process it
(sometimes quite heavily) and then output the results. These are slowly
migrating over to the analysis mode of avida (see the analysis documentation
for more information).
Population Events
Population events modify the state of the population, and will actually
change the course of the run. There are a wide variety of these.
Resource Events
Events that allow user to change amounts of resources in the system.
Misc. Events
These are other events that didn't seem to fit better anywhere else...
Project hosted by:
