Source code can always be found in the code release directory.

When compiling be sure to use the:

APP_VERSION = 0.18
APP_NAME = your_app_name

-DBOINC_APP_VERSION=$(APP_VERSION)
and
-DBOINC_APP_NAME='"$(APP_NAME)"'

flags to make sure your binary gets credit. I've also updated the_parameters.sh script so to test a WU you just need to run:
./set_parameters

The results should look like the following:

20:
nm_s20_l01
parameters [14]: 0.571713000000000 12.312118999999999 -3.305187000000000 148.010256999999996 22.453901999999999 0.420350000000000 -0.468858000000000 0.760579000000000 -1.361644000000000 177.884238000000011 23.882891999999998 1.210639000000000 -1.611974000000000 8.534378000000000
metadata: it: 5, ev: 588
fitness: -2.985312797571472
your_app_name: 0.18

21:
nm_s20_l01
parameters [14]: 0.571713000000000 12.312118999999999 -3.305187000000000 148.010256999999996 22.453901999999999 0.420350000000000 -0.468858000000000 0.760579000000000 -1.361644000000000 177.884238000000011 23.882891999999998 1.210639000000000 -1.611974000000000 8.534378000000000
metadata: it: 5, ev: 588
fitness: -2.889342881503315
your_app_name: 0.18

79:
searchname
parameters [8]: 0.342173733203920 25.951791084662300 -2.170941473882660 38.272511356953906 30.225190442596112 2.214906001337289 0.323161690642917 2.774024471628528
metadata: this is the metadata
fitness: -2.946683357256020
your_app_name: 0.18

82:
searchname
parameters [8]: 0.405879611547422 17.529961843393409 -1.857514527214484 29.360893891378243 31.228263575178566 -1.551741065334000 0.064096152599308 2.554282099127810
metadata: this is the metadata
fitness: -2.985569777902147
your_app_name: 0.18

86:
searchname
parameters [8]: 0.733171635575244 14.657212876628332 -1.705465347395041 16.911711745343634 28.077212666463502 -1.203290851581461 3.527360643924728 2.224821450587501
metadata: this is the metadata
fitness: -3.027909854710189
your_app_name: 0.18

---

I'll be adding some sample checkpoint files for each of these stripes as well (sometime later tonight or tomorrow), so it'll be easy to test that they're checkpointing correctly as well.

---

I'll be adding some sample checkpoint files for each of these stripes as well (sometime later tonight or tomorrow), so it'll be easy to test that they're checkpointing correctly as well.

But you can't compare the values in the checkpoints, because they are of course dependent on the stage of the computation. They will be most likely different even on the same computer when one runs the same application twice and compares the checkpoints written after let's say two minutes.

I'll be adding some sample checkpoint files for each of these stripes as well (sometime later tonight or tomorrow), so it'll be easy to test that they're checkpointing correctly as well.

But you can't compare the values in the checkpoints, because they are of course dependent on the stage of the computation. They will be most likely different even on the same computer when one runs the same application twice and compares the checkpoints written after let's say two minutes.

Well, if the application is started using the checkpoint file, it should return the same result as if it had been run without one.

The checkpoint files (given the same point in the computation) should be the same across different computers.

So what I was planning on doing was having a set of checkpoint files from different stages in the workunits computation, so a user could test them by having the application using a checkpoint file and seeing if the result it gave was the same as if it had ran without a checkpoint.

---