This post will be updated as we complete things, and serves as a list on what needs to be done by the server group.
I will update this post as we go. Please subscribe to this topic to receive updates!

A checklist specifically for the server group:
- {DONE} [Daniele] Provide more redundancy
- - With the new workunits that are generated the redundancy factor will be 2.
- {DONE} [Daniele] Delete old WU, restart work generator, generate new ones with replication factor of 2.
- {DONE} [Daniele] Improve the reliability of the task generator.
- {DONE} [Daniele] Make a script that takes the files, and registers it with the workunit.
- {DONE} [Daniele] Embed more information on the WU names.
- {DONE} [Daniele] Create a script that automatically run the script of the preprocessing group and register all the generation directives in the task generator.
- {DONE} [Daniele] Give a proportional time estimation to client for the workunit. Note: currently the flops estimation is incorrect, but at least is somehow proprtional to the amount of work in a workunit.
- [Trung] Rename the project
- - URL: gene.disi.unitn.it/boinc/
- - Name of the project: Gene
- [Trung] Rename the application, and delete the old ones
- [Chau][Trung] Test the validator with live data (the work generator will distribute data with replication factor of 2 in a few hours)
- [Chau] Test the differences between the results obtained on Intel and AMD
- {DONE} [Daniele] Rename the work generator executable
- [Chau] Rename the validator executable
- [Claudio] Check with the post-processing group what they want as input (do a new topic on that and send email)
- [Claudio][Chau] Check how boinc handles exporting data, and what needs to be modified in order to export data in their format (assimilator?)
- [??] Limit the numbers of assigned workunits.

The names near the task are who (I think) wants to do the task.

>> IF YOU WANT TO DO SOMETHING ELSE WRITE ME AN EMAIL. <<

These thing are done and tested to work:

Application:
- provide more platforms (both x64 and x32)
- - we have mac, linux x86 x64 and win x32 (runs also on win64)
- test checkpoints and progress bar
- - they work
- - time estimation is all messed up, but at least it is proportional to the work in the workunit. boinc will auto-adapt (hopefully) to the wrong estimation.

Server side:
- embed info into wu name (something like gene_datasource_npi_otherinfo_index)
- - ok: contains the name of an xml file containing all the info.
- do redundancy (now it seems that the result is self-validated)
- - Redundancy of 2 is enabled.
- NOTE: now I inserted in the queue the analysis of all the network that the preprocessing gave us.

Names:
- give meaningful names to specialized daemons, i.e. sample_work_generator should be gene_work_generator
- - Renamed to gene_work_generator. Also the validators, assimilators etc have names in the form gene_xx

[About Rename the Project]

I find a way to change a project's name and project's URL while maintaining the forum content and user's credit. Users need to remove old project from boinc-client and add the new one. Tested on Boinc Virtual Machine.

For example, we want to change the name from 'test' to 'gene'. The URL becomes 'http://gene.disi.unitn.it/gene/'

Stop the project and take the website down

About:

limit somehow the number of distributed wu (no too big client caches now) say max 2 per host per core (just an idea)

I want to ask about the way we provide credits for "Anonymous platform". http://boinc.berkeley.edu/wiki/Anonymous_platform. Because they will not use our application.