When looking at specific WUs on the website, it just shows the application as "Rosetta" with no indication of the application version. I should think adding the version would be very helpful to those with multiple machines as a central place to check and see if there are any problem WUs you need to kill (such as the v4.97 problems over the weekend).

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

The Wus are not that specific to the application version. Usually the WUs can run under any recent version of the application. However the application version is shown in the result file for returned results. You can reach that info from your stats page.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

So, what triggers the download of a new application version? It just checks for a new one every time it requests work?

If the WU doesn't determine app version... then this idea may have some merit:

It occurs to me that dial-up users probably get in to a pattern, come home, dial up, download EMails, allow BOINC network access, BOINC uses the internet for 10 minutes while you read your EMails, then you disconnect and go watch TV. ... and when a new application comes out, with a 7-10MB download, that puts them in a bind, because they're usually low on WUs, and now they must complete the download of the new app version before they can get anymore.

So, the idea would basically be to give the user some means of control over WHEN they go to a new version. This would allow them to do that long download on Saturday, or on off-peak time, or when they aren't already pressing their usage limits, or whenever it suits them.

I guess knowing what triggers the new version now would determine how such a control might be implemented. Maybe add a URL button on the Projects tab, "Version update"? And have that allow some "manual download" (via the browser and save) of the new version? Drop the file in the BOINC directory, the project checks if a new version is available the next time BOINC starts... something like that. That way the button would only appear when a new version is available. Then I suppose a R@H preference is also needed to allow you to say "just do it for me, whenever" for the non-dial up users.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/