Latest version for Houdini users
2 views
Skip to first unread message
Patrick
May 18, 2011, 9:25:29 AM5/18/11
to dexen_users
For those of you using Dexen with Houdini (i.e. my students), I have
created an updated version that fixes various things. In particular we
have been having trouble with getting Dexen to install and run
correctly on Windows without having admin rights.
For the latest version, I have created a zip file source distribution.
Just unzip it anywhere on your hard disk and follow the instructions
in the README_HOUDINI.txt file. Also, have a look at the Houdini EA
generator page here: http://code.google.com/p/dexen/wiki/houdini_ea_generator
You can try out the Houdini examples in the 'examples\xml' folder. Let
us know if you have problems.
created an updated version that fixes various things. In particular we
have been having trouble with getting Dexen to install and run
correctly on Windows without having admin rights.
For the latest version, I have created a zip file source distribution.
Just unzip it anywhere on your hard disk and follow the instructions
in the README_HOUDINI.txt file. Also, have a look at the Houdini EA
generator page here: http://code.google.com/p/dexen/wiki/houdini_ea_generator
You can try out the Houdini examples in the 'examples\xml' folder. Let
us know if you have problems.
Patrick
May 18, 2011, 9:27:52 AM5/18/11
to dexen_users
ps You can download the zip file (dexen-hou-0.3.3.3.zip) on the
downloads page: http://code.google.com/p/dexen/downloads/list
downloads page: http://code.google.com/p/dexen/downloads/list
Patrick
May 18, 2011, 9:22:46 PM5/18/11
to dexen_users
An updated version has been uploaded (dexen-hou-0.3.3.4.zip)
See http://code.google.com/p/dexen/downloads/list
Just a bunch of bug fixes...
See http://code.google.com/p/dexen/downloads/list
Just a bunch of bug fixes...
Patrick
May 19, 2011, 11:02:24 PM5/19/11
to dexen_users
Another updated version has been uploaded (dexen-hou-0.3.3.5.zip)
See http://code.google.com/p/dexen/downloads/list
Fixed a bug related to creating snapshot files.
CLI command get_job_snapshot_file JOB_ID FILE_PATH STEP
While we are on the subject of snapshot files, the STEP parameter is a
bit hard to understand. It is actually the time step - at each time
step, a snapshot of the live population will be taken. However, since
Dexen is a pparallel system, time is a bit odd. If we use time on the
clock, e.g. every 5 minutes, then it would be quite unpredictable -
since if you use 10 slaves it will run much faster than if you use 1
slave.
So in the end we decided to use a counter (Action ID), which counts
every time Dexen does something - e.g. executes a task. So if you
specify STEP as 50, then a snapshot will be taken every 50 actions.
The problem with this is that for users, it is a bit hard to
understand what the STEP really represents in terms of time. For the
moment, the best is just to use trial and error - maybe about 50
actions is OK. (You can see the actions in the log file.) In future we
will have to revisit this issue - maybe we need to give the user
different ways of specifying the time step - time on the clock, Action
ID, or Transaction ID.
See http://code.google.com/p/dexen/downloads/list
Fixed a bug related to creating snapshot files.
CLI command get_job_snapshot_file JOB_ID FILE_PATH STEP
While we are on the subject of snapshot files, the STEP parameter is a
bit hard to understand. It is actually the time step - at each time
step, a snapshot of the live population will be taken. However, since
Dexen is a pparallel system, time is a bit odd. If we use time on the
clock, e.g. every 5 minutes, then it would be quite unpredictable -
since if you use 10 slaves it will run much faster than if you use 1
slave.
So in the end we decided to use a counter (Action ID), which counts
every time Dexen does something - e.g. executes a task. So if you
specify STEP as 50, then a snapshot will be taken every 50 actions.
The problem with this is that for users, it is a bit hard to
understand what the STEP really represents in terms of time. For the
moment, the best is just to use trial and error - maybe about 50
actions is OK. (You can see the actions in the log file.) In future we
will have to revisit this issue - maybe we need to give the user
different ways of specifying the time step - time on the clock, Action
ID, or Transaction ID.
Reply all
Reply to author
Forward
0 new messages