Examples
--------
Several data type examples and their corresponding parmfiles are available here.
To test whether migrate works on your machine run simply:

migrate-n parmfile.testml
migrate-n parmfile.testbayes

Timing on my Macbook Pro (Intel Core 2 Duo 2.5 GHz with 2 cores,  6 MB L2 Cache, 
4 GB memory, 800 MH bus speed) running parmfile.testml and parmfile.testbayes
using: time migrate-n parmfile.x -nomenu, reporting real time
--------------------------------------------------------------------------------
compilation using:                     ML                      Bayes
make                                2m41.964s                  4m33.969s
make thread                         3m53.349s                  4m1.313s
make mpis                           2m02.678s                  3m3.744s
--------------------------------------------------------------------------------
Timing using the FSU HPC cluster:
make (1 node)                       2m54.069s                  4m50.497s 
make mpis (11 nodes)                0m31.185s                  0m39.507s

On Mac: compiler gcc 4.1; the threaded version uses 5 threads (suboptimal on a 2-core 
machine, the MPI version uses 3 nodes [1 master + 2 worker])

Compare your runs with the runs labeled:
outfile-ml-saved
outfile-bayes-saved

They should look similar, although there might be differences because 
of optimization (compiler dependent) and hardware differences.
Differences in these (too) short run are due to different 
optimization on different machines, I doubt that it is
possible to compare between different computer architectures
but if the program finish it is likely that the program will work on
your data, too.


Peter Beerli
(beerli@fsu.edu)
May 2009
