- Fixed writing score
- Better time estimation

v0.08

- Removed the input file "experiments"
- One input file sticky (compressed)
- One single input for the application (compressed)
- Change the score computation

v0.07

- Removed the score file

v0.06

- Fixed the stderr output

v0.05

- Windows executables statically compiled
- Linux glibc problem solved
- Re-introduced the "score.txt" output file (not used for validation, we will use it for statistics)
- The application can handle a variable number of input files (this should reduce the network usage)
- The application now compute part of the post-processing analysis

v0.04

- Standard error more compact
- Removed the "score.txt" output file and the related MD5 library

v0.03

- Compact standard error
- Results file problem with carriage return/new line solved

v0.02

- BOINC suspend working. Critical sections problem solved

v0.01

- First release

Now the project is beta but, in the future, may be stable and public
So, these are usually requests from volunteers for all boinc projects:
1) A GPU client (better OpenCL, for all gpu cards)

2) Screensaver

3) Android client (for smartphone)

4) Extension for better performance (like AVX)

You have been warned!! :-)

1) "Sprites" is a mistake it should be "Spirtes";
2) PC means Peter-Clark, Spirtes is the second name of Peter.

<message>
Uno o pi� argomenti non validi. (0x80000003) - exit code -2147483645 (0x80000003)
</message>

ERROR: Invalid parameter detected in function (null). File: (null) Line: 0
ERROR: Expression: (null)

Please try to make the stderr output more compact. From

#132 Tue Dec 24 02:05:01 2013
Graph created File: complete_gene_net read Standard deviations computed Correlations computed l: 0 1 2 3 4 5 6 7 8 9 # of arcs: 2223
Writing checkpoint's file

to something like

132|13-12-24 02:05:01|G F S|C(9:2223)
CHK

I mean, all the needed info squeezed in few bytes.

I did not work on that, but I think that the new version we already sent has a more compact stderr.

Also, do you need to read the complete_gene_net at every iteration? Shouldn't be more efficient to just read it at start or returning from checkpoint and keep it (or a copy of it) in memory?

When we developed the first versions of the application, we had no bounds on the complete_gene size, so the best strategy was to read on-the-fly the lines needed.
I think that we should discuss this with professor Blanzieri, reading it once should be faster, but I suspect that working with different species could lead to far bigger input files, compared to the Arabidopsis. Splitting those files may be a solution, though..

int boinc_time_to_checkpoint();