There\'s tens of crashed results (still) in my profile. Since only one of them ever created a trickle, I would like to get rid of all the other crashed ones. They clog up space unnecessary anyway. How is the deletion of crashed models handled?

---

Because of the long times involved in this project, where there is a possibility that they may be still waiting on a computer to be processed, they stay there for a few years, as do unused computers.
One person was slowly prcessing a model for over a year, before finally finishing it.

Because of the long times involved in this project, where there is a possibility that they may be still waiting on a computer to be processed, they stay there for a few years, as do unused computers.

That is reasonable for how the __server__ behaves.

However, if the __participant__ knows that there is ZERO chance that any results will ever be submitted for an assigned but wiped_out/crashed workunit, there ought to be a way to either:

(1) RETURN the workunit to the server, for it to dispose of as it will, or
(2) REFETCH the workunit starting data, so that the original assignee can try working on it again, from the beginning.
.

Data sets are flagged by the server for possible re-issue about 6 weeks after no trickles are received.
Refetching may not be possible for various reasons.
As for what users are or aren\'t allowed to do on a projects servers is up to each project\'s designers.
The science is the thing, not how tidy a users account page looks to a user.

Life isn\'t neat and simple. There are always \'weeds\'.