I set up a couple of machines to run Rosetta while the Einstein project is down and one machine seems to work perfectly, but the other will upload finished jobs but will not report them. Any ideas what wher the problem might be? The settings aee the saem for both machines.

F. Prefect

I set up a couple of machines to run Rosetta while the Einstein project is down and one machine seems to work perfectly, but the other will upload finished jobs but will not report them. Any ideas what wher the problem might be? The settings aee the saem for both machines.

F. Prefect

It the way boinc works, it batch reports jobs after a liitle while, just leave it it should do it automatically.

You may also want to change the runtime length of a job.

Goto your preferences https://boinc.bakerlab.org/rosetta/prefs.php?subset=project and find Target CPU run time set it to 24hrs (that is if you are still using dial-up.
Each jobs now runs for longer (it doesn't effect the results at all, can explain more if needed) but it saves you bandwidth a lot.

---

Team mauisun.org

I'm not having any problems with R@H, but I was wondering what others are doing with their cache since it is tangential to the post below. I know all 3 of my boxes are set at 1 days worth in the cache. I've found it to be quite helpful; it's enough to keep me running R@H even if there is a short break. What do some of you others have your cache set at?

for the continous crunchers I tend to set them to a long run and a 4 day cache.
for the partime it'll be a 1/2 to 1 day cache and 2 or 3 hr tasks.
for irregulars it's default and 2hr tasks

Task length is usually set to the time I expect them to be on in one sitting unless they are in mine... Guess what 3 preference settings just are not enough, since we cannot do project setting locally that's not an option and once you set the default from default to say home you loose a setting :-( as there is no way back afaik)

Not tested out BAM's setting but I think it has the same project specific preferences problem or at least last time I checked.

---

Team mauisun.org

I set up a couple of machines to run Rosetta while the Einstein project is down and one machine seems to work perfectly, but the other will upload finished jobs but will not report them. Any ideas what wher the problem might be? The settings aee the saem for both machines.

F. Prefect

It the way boinc works, it batch reports jobs after a liitle while, just leave it it should do it automatically.

You may also want to change the runtime length of a job.

Goto your preferences https://boinc.bakerlab.org/rosetta/prefs.php?subset=project and find Target CPU run time set it to 24hrs (that is if you are still using dial-up.
Each jobs now runs for longer (it doesn't effect the results at all, can explain more if needed) but it saves you bandwidth a lot.

Thanks FC. It appears it defaults to 8 days when installed and although I only have it installed on 2 machines, it seems like every time send in a couple of results, I get hit with more and more downloads. I've read the FAQs and understand what you mean by not effecting the results. I'll make the change and thanks for the help.

F. Prefect

About a year a go I was running Rosetta along with another project and to make a long story short, I detached Rosetta. I would now like to run Rosetta again but when I attempt to attach to the project I get the message that I am attached but no files will download. Any help appreciated. Sorry about all the posts, but I would like to get it up and running again.

F. Prefect

About a year a go I was running Rosetta along with another project and to make a long story short, I detached Rosetta. I would now like to run Rosetta again but when I attempt to attach to the project I get the message that I am attached but no files will download. Any help appreciated. Sorry about all the posts, but I would like to get it up and running again.

F. Prefect

F. Prefect--

Have you tried doing a Rosetta project reset through the BOINC manager. I've read your other posts and I do not believe you should have to delete any files manually. A reset of the project should delete the files not needed and reload the files that are.

You can do this by left clicking on Rosetta under the projects tab and then "reset project" under commands. Hope this works.

Tim

Edit: There are certainly other issues that can be looked at later regarding resource shares and project debts etc. However, I do offer one caution, BOINC is designed to work through all of this on its own. If Rosetta is fine before or after the reset, BOINC will allow work eventually on its own terms. Often its best to just leave BOINC manage the projects as this is what it is designed to do.

---

yo estoy teniendo el mismo problema !!
i have the same problem :(

---

I moved the tech support discussion in the "no communication" thread in the Science forum into this thread. Let's help get these 2 win98 machines back to running Rosetta.

How many spots can you stop Rosetta in the Boinc client? I remember having troubles switching from 100% Rosetta to 100% Ralph and back.

---

Rosetta Moderator: Mod.Tymbrimi
ROSETTA@home FAQ
Moderator Contact