This is a (somewhat) minimal implementation of a HillClimber/IVMC experiment from M4M. It runs exactly the same experiments (given the same parameters), but the trajectory are not bit-for-bit idential (due to some weirdness in M4M to do with supporting population models).
This is a (somewhat) minimal implementation of a HillClimber/IVMC experiment from M4M. It runs exactly the same experiments (given the same parameters), producing the same output (which requires a couple of weird implementations details, but nothing too painful).
## Dependencies
...
...
@@ -32,7 +32,7 @@ This will run each of the experiments called in the `Program.Main` method. Each
## Notes
The idea behind IVMCTrim is that it is possible to understand/mess with the model quickly, instead of having to trawl through M4M looking for the right place to plug in an `IComposer` or whatever, only to find that your code doesn't serialise properly. If you want to understand the model: this is the place to look. If you want to perform serious analysis, then you will want M4M.
The idea behind IVMCTrim is that it is possible to understand/mess with the model quickly, instead of having to trawl through M4M looking for the right place to plug in an `IComposer` or whatever, only to find that your code doesn't serialise properly. If you want to understand the model or just want to reproduce existing results, IVMCTrim is the place to look. If you want to perform serious analysis, then you will want M4M.
In order to ensure the simulations are exactly the same as those run under M4M, the order and method by which random numbers are generated must be exactly the same. This ordering is fairly easy to see in IVMCTrim.
...
...
@@ -40,7 +40,7 @@ In order to ensure the simulations are exactly the same as those run under M4M,
## Help / More / Contact
If you run into trouble or want access to M4M (the nightmare inducing program that ran the actual experiments in the paper) then contact fjn1g13@soton.ac.uk. It is not made available 'by default' due to the complexity of the implementation, and the many unfinished and broken components it contains: we believe it is better to supply an understandable implementation, but if you want to reproduce the figures from the paper or otherwise mess with the model/analysis, then I'll be happy to help.
If you run into trouble or want access to M4M (the nightmare inducing program that ran the original experiments in the paper) then contact fjn1g13@soton.ac.uk. It is not made available 'by default' due to the complexity of the implementation, the many unfinished and broken components it contains, and the complexity involved in using it: we believe it is better to supply an understandable implementation, but if you want to reproduce the figures from the paper exactly or otherwise mess with the model/analysis, then I'll be happy to help.