|
RunFiles
for Simulator005
release
6
Current
hot message:
You
will have to upgrade to release 6 (or later) to work with
the following run-files.
From now on you
can find the currently hottest run-files here.
Project 3 theme:
Simulator005 looks at what happens, if two different Muller's
ratchet processes with constant mutational effects operate
in the same population at the same time.
Project
3 ( TwoSDMRatchets ) scheduling session 2 continues to
schedule the latest big project of evolution@home. After more
than 3.5 years of CPU time on fairly fast machines, enough
small tasks have been computed for the moment. Now comes the
largest part of the project: looking at what happens in the
more complex tasks. Since some of the run-files are quite
long, some of you might want to consider editing them manually
to speed up computation of some parameter combinations that
are at the back of the file.
CPU-time predictions
may be very inaccurate, as this project explores the unknown.
Project
3 ( TwoSDMRatchets ) scheduling session 1 schedules the
latest big project of evolution@home. Now Simulator005 looks
at what happens, if two different ratchet processes operate
in the same population at the same time. This collection of
run-files contains 21680 simulations of an estimated CPU-time
of less than 1 month with a total of 98.7 years most probable
CPU-time and 714 simulations of an estimated CPU-time of more
than 1 month with a total of 97.1 years most probable CPU-time.
Since some of the run-files are quite long, some of you might
want to consider editing them manually to speed up computation
of some parameter combinations that are at the back of the
file.
Project 1-2
theme: Simulator005 looks at what happens, if one single
Muller's ratchet process operates in a population. Mutational
effects are constant. Otherwise a wide range of parameter
combinations is used.
Project
2 ( SimpleSDMRatchet ) scheduling session 1 schedules
a small special set of simulations that require very much
RAM. Its for those of you who want to test the limits of what
can be simulated on 32 bit CPUs. Unfortunately, Simulator005
is not yet ready for 64 bit CPUs and it may take some time
until it is.
Project
1 ( SimpleSDMRatchet ) scheduling session 7 is the same
as session 6, without tasks that have been computed often
enough already.
Project
1 ( SimpleSDMRatchet ) scheduling session 6 has 1166 computable
simulations with 26.7 years most probable combined CPU-time.
Project
1 ( SimpleSDMRatchet ) scheduling session 5 has 555 computable
simulations with 6.34 years most probable combined CPU-time.
Older
less well organized run-file collection have been removed.
Please note that here is no overlap between scheduling session
5 and earlier run file collections.
Follow one of the links and select a run-file from the collection
you find there.
Make sure that
- the run-file
needs less Megabytes RAM than your computer can provide
while you work with it.
If you feel insecure about what to choose, use 2 MB for
a computer hat is older than 1995, and 10 MB for computers
that are younger. However, if you know what you do, please
choose the largest RAM-sizes your computer supports without
using virtual memory.
- at least the
smallest simulations in the run-file need less computing
time than the limit you specified in your preferences.
- the total estimated
computing time is longer than the time until you plan to
visit this site again to get the next run-file (e.g. your
holidays).
- you have the
current release of Simulator005
How
do I start a simulation with these run-files?
Just
get the run-file you want in your browsers window, then save
it under the name "run"as a text-file in your simulators
folder. Then start the simulator. (If you did not enter the
preferences yet, then do it now.)
What
if several people use the same run-file?
That is perfectly OK. The simulations computed by the
simulator depend very much on chance. Therefore each simulation
is started with a unique random seed and starting the same
set of parameters thus leads to different results. While the
first run of a new parameter combination allows one only to
get a very rough feeling for the results, all other repeats
are neccessary to compute mean and variance of the output-parameters.
The larger the variance the more simulations are needed to
get accurate estimates. The more repeats are available, the
higher is the accuracy of the statistics computed.
If you currently get no Internet connection, but your run-file
has been completed, you may also rename it back to "run"
and start it again. However, if possible, get fresh run-files
from this site, because simulations that have been computed
often enough are being removed from the runfiles to prevent
excessive repetition.
What
about multiprocessor machines?
As the current simulator computes the random seed
of a stochastic simulation from the second of the time when
the latter is started, different starts lead to different
valid results. Thus, on multiprocessor machines, start
different run-files on different CPUs. This avoids identical
start seconds on different CPUs. Identical tasks with identical
seeds keep the additional simulation(s) from contributing
to statistical quality.
What
run-file should I choose?
Generally, choose those run-files that need little less RAM
than the maximum you can afford. Furthermore, chose those
files with the longest computing times you can imagine your
computer to handle. And, please do not chose the first
three run-files (as probably a lot of people are going
to).
Are results lost if my computer crashes?
Yes, but only minimally. Each simulate-command from the run-file
stands for a single run whose results are stored to harddisk
after it has been completed. So, such results are not lost
by a crash. If you start a run that needs very long time,
then each hour an intermediate results-file is generated.
For very long runs these intermediate can be very valuable,
as it can be hard to complete the whole simulation. However,
final results are always better. If evolution is interrupted
very often (due to a crash or other reasons), please choose
run-files with simulations that need less time than the interrupts
intervall.
How
often do I submit results?
That
is up to you. However, we suggest the following:
- whenever a run
file has been completed
- after 2-4 weeks,
if the run-file does not finish earier
- If a single
simulation needs more than that, then submit results, whenever
you see that this simulation has generated a real results
file (= results.S005.txt, please do not submit IntermediateResults).
To submit results,
see here.
|
