The 1 year deadline for completing a model is arbitrary - the BOINC server software requires that a completion date be inserted, as this is used by the other, shorter projects. (See list here.)

Provided that a computer returns at least one trickle a month, then the data will continue to be accepted well past the one year \"deadline\".
Delaying trickles for longer than about 6 weeks will cause the server software to regard the model as \'lost\', and it will mark that data set for possible re-issue to another computer.

The only exception to this \'no deadline\', is if the project finishes, and models haven\'t been returned.
Examples of this are the THC (Thermohaline Circulation Experiment), and the SAP (Seasonal Atttribution Project).

---

Backups: Here

The 1 year deadline for completing a model is arbitrary - the BOINC server software requires that a completion date be inserted, as this is used by the other, shorter projects. (See list here.)

Provided that a computer returns at least one trickle a month, then the data will continue to be accepted well past the one year \"deadline\".
Delaying trickles for longer than about 6 weeks will cause the server software to regard the model as \'lost\', and it will mark that data set for possible re-issue to another computer.

The only exception to this \'no deadline\', is if the project finishes, and models haven\'t been returned.
Examples of this are the THC (Thermohaline Circulation Experiment), and the SAP (Seasonal Atttribution Project).

So if I have computer that hasn\'t reported in more than 6 weeks should I still fire it back up or should I just abort the unit?

If you\'re talking about this model, then it hasn\'t been re-issued yet. (Click on the number alongside \"Workunit\".) So you can continue with it.

---

Backups: Here