I cant be on the net all the time and the workunits deadlines are too short for me. Nothing like getting 0 credit for all the workunits I crunched and watts I wasted. I'm done.

Man, I long for the old Seti@home days. I dont care if people cheated or whatnot. I could easily move my WUs around via flash drive to whatever PC needed them without having to physically connect to the net with taht particular PC before these deadlines.

Can anybody direct me to any un-boinc-like distributed processing project that's not so regimented?

---

As you are no doubt aware bob, the Rosetta deadlines were extended. They used to be 7 days, now they are 10 days. But if that doesn't fit with your internet availability, or the number of times you wish to run around with a flash stick, you might try a project with a really really long deadline, like Climate Prediction. Last I knew their deadline was 1 year, and it takes 3 months of dedicated crunching to complete a single WU. It is a BOINC project, but the extreme difference in deadlines may be a better fit to what you are looking for.

I hope you will stay with Rosetta for the machines that you have that do have ready internet access.

---

Rosetta Moderator: Mod.Sense

Quick note, although you get the 'credit', the project still uses the result. I wish they went back to their original deadline times of 2weeks to a couple of months when we first started.

But I guess there is a need for the 1 week deadline (extended to 10 days to aid the weekend syndrome).


F@H is none boinc, FaD was really good for what you want to do but is no longer running, I wouldn't touch United Devices.
But you should have a look at this site that lists and has a brief on most projects around http://www.distributedcomputing.info/ There are plenty of none boinc projects.

---

Team mauisun.org

Thanks for the pointers. I just want a stress free crunchiong environment -- no to have to worry about things like moving my laptops around. The 1-2 week deadline thing just doesnt work for me.

I have been a longtime member of the UD project but that just seems like a stale thing. No upgrades or changes for eons. Could be crunching teh ssame handfuls of WUs forever for all I know. The 3rd party caching never worked very well for me.

I will look into the references you have mentioned.

-B

---

F@H is none boinc

While F@H is not (yet?) using Boinc and has similar objectives as Rosetta, for bob's purposes it is even worse. Like Rosetta the F@H project requires a quick turnaround of their workunits since subsequent workunits depend on the previous results. While Rosetta/Boinc allows some caching of workunits to mitigate the not-always-online network issue, the F@H client permits only one workunit at a time.

Outside of Climate Prediction I don't know of any project that works well with systems that are mostly offline.

---

Team Helix

F@H is only similar in that it is folding, but they are teo different things.

F@H last time I knew had no-deadline units you could specify.

P.S. At UD if you have been doing cancer then yes you've been repeating the same old, same old cancer units for the past year or so :(
They decided not to stop that as people might move away from them.

If you have been doing the HPF then nope you have been doing new work, though really you shoudl have moved to World Community Grid.

---

Team mauisun.org

You know bob, you might consider uninstalling boinc on the computers that might not be able to run boinc all of the time, and just keep it with one one or two that have limited access, like dial-up or something. That way, you can still participate with only one or two of your computers with a limited cache on hand to keep you busy. Would this help? Also, are you able to keep any of your hosts running all of the time to crunch? Hope you can find a way to keep crunching!

---

(Click for detailed stats)

F@H last time I knew had no-deadline units you could specify.

Those have been discontinued for some time now. They wouldn't really have helped either since the client would only download one of those. When that one workunit is complete the computer would sit idle until bob transfers another workunit. The only benefit the timeless workunits would have given is that you would still get credit if the workunit is being returned after a long (not indefinite) time.

---

Team Helix