I assume there is something in place to stop them patenting our part?

Science would go so much faster if everybody knew everything instead of every company hiding things. Knowledge should never ever be owned.

They can't patent "our part". That is part of the "prior art" to them. They can only patent their advances beyond that, which may of course depend on "our part"; otherwise, there would be no point in doing what we are doing.

Otherwise, your "much faster" theory can be put to the test as I have indicated. Good luck.

Are you suggesting that private companies somehow help science? Sure, they have money, but if nobody else can benefit from the findings I call that a backwards step, especially if the patent then ends up blocking anyone else doing similar research. Just look at the nonsense with patenting genes! And those other countries aren't exactly rich enough to try my "idea", which I would prefer to be referred to as "common sense".

Companies help science if they think they can make money doing so, with a few exceptions for those with owners that want to help the public.

It'd be nice to keep this thread for Problems and Technical Issues, maybe if you start a thread in the café to discuss this particular subject?

---

Grant
Darwin NT

Companies help science if they think they can make money doing so,

I guess that could work both ways. More money input, but the possibility of preventing others from using the results.

with a few exceptions for those with owners that want to help the public.

Elon Musk springs to mind.

---

It'd be nice to keep this thread for Problems and Technical Issues, maybe if you start a thread in the café to discuss this particular subject?

Yawn.... move it then.

---

Yawn.... move it then.

Please heed the advice to carry on the conversation where more appropriate. All of it is off topic, and it is easier to delete than to move. Far better for all to simply do more than yawn in the first place.

---

Rosetta Moderator: Mod.Sense

Yawn.... move it then.

Please heed the advice to carry on the conversation where more appropriate. All of it is off topic, and it is easier to delete than to move. Far better for all to simply do more than yawn in the first place.

Feel free to delete it. Conversations drift, we've all read it, it can go if you wish. But starting a new conversation would have snapped it in two.

---

12345678910

12345678910

You've been warned, counting is off topic.

---

After resetting the project to the new https address, I keep getting the below error:
6/17/2020 2:32:34 PM | https://boinc.bakerlab.org/rosetta/ | Resetting project
6/17/2020 2:32:37 PM | https://boinc.bakerlab.org/rosetta/ | Fetching scheduler list
6/17/2020 2:32:39 PM | | Project communication failed: attempting access to reference site
6/17/2020 2:32:41 PM | | Internet access OK - project servers may be temporarily down.

According to the server stat page, everything appears to be running.

Any clues?

---

After resetting the project to the new https address, I keep getting the below error:
6/17/2020 2:32:34 PM | https://boinc.bakerlab.org/rosetta/ | Resetting project
6/17/2020 2:32:37 PM | https://boinc.bakerlab.org/rosetta/ | Fetching scheduler list
6/17/2020 2:32:39 PM | | Project communication failed: attempting access to reference site
6/17/2020 2:32:41 PM | | Internet access OK - project servers may be temporarily down.

According to the server stat page, everything appears to be running.

Any clues?

If thigs are still not working, might as well start with the basics- re-boot your modem & the computer and see if that clears the networking issue.

---

Grant
Darwin NT

After resetting the project to the new https address, I keep getting the below error:
6/17/2020 2:32:34 PM | https://boinc.bakerlab.org/rosetta/ | Resetting project
6/17/2020 2:32:37 PM | https://boinc.bakerlab.org/rosetta/ | Fetching scheduler list
6/17/2020 2:32:39 PM | | Project communication failed: attempting access to reference site
6/17/2020 2:32:41 PM | | Internet access OK - project servers may be temporarily down.

According to the server stat page, everything appears to be running.

Any clues?

Which version of BOINC are you using? Under which version of which operating system? (For example, I am using 64-bit BOINC 7.16.7 under Windows 10, version 1903.)

Your problem looks typical for most users using a recent version of Windows who are still using BOINC 7.16.6 or earlier.

https://www.nvidia.com/Download/index.aspx?lang=en-us

It appears that you are still using BOINC 7.6.22, although under Windows 10, and therefore need to upgrade to BOINC 7.16.7, preferably with no tasks under BOINC that have started running but have not finished.

Excuse me - I gave the wrong link for updating your BOINC version.

https://boinc.berkeley.edu/download_all.php

I'm running Rosetta on a MacBook Air version 10.15.5 with 8 Gb of RAM. BOINC version is 7.16.6 and when I check for a new version it says there are no newer versions.
I'm running Rosetta 19 hours/day using at most 32% of CPU time. (so to not let the CPU run too hot) I have been running it for a little over a month and I have 1,786 credits.

My question is why am I getting the following message so frequently in the task status report:

"Timed out - no response"

Sometimes I get also the following:

"Not started by deadline - canceled"

Thanks in advance for any response(s).

"Timed out - no response"

This one I don’t know about.

"Not started by deadline - canceled"

Deadlines for Rosetta@home tasks are 3 days from the time they are issued. It can take BOINC several days to learn how much wall time it takes a new computer to complete the CPU time required for each task (8 hours by default), so it is important to configure your settings to ensure that BOINC doesn’t download more tasks than you will be able to complete before their deadline.

In your settings (configured either online or locally [Advanced view > Options > Computing preferences]), set Store at least to no more than 0.3 days (≈ task duration, if your CPU is doing nothing besides Rosetta), and Store up to an additional to 0.02 days. These low values should help to ensure you don’t get a backlog of tasks you can’t complete before the deadline; as long as your computer is frequently online you will not run out of tasks as BOINC will still contact the server whenever it needs more work.

If you have a large backlog of Ready to start tasks that you suspect you have no chance of completing, you can Abort them to return them to the server to be allocated to another computer.

I'm running Rosetta 19 hours/day using at most 32% of CPU time.
"Not started by deadline - canceled"

The problem is in that first line. "using at most 32% of CPU time" means it will take at least 24hours to process one 8 hour Task.
You would be much better off limiting the number of cores/threads you use, but let them run at 100%

I'd suggest

Computing
   Usage limits	
                                   Use at most 50% of the CPUs
                                   Use at most 100% of CPU time

and use the caching values as suggested by Brian Nixon (or even smaller ones).

---

Grant
Darwin NT

Error after pc reboot:

22/06/2020 08:32:06 | Rosetta@home | [error] garbage_collect(); still have active task for acked result rb_06_18_29700_29099__t000__0_C1_SAVE_ALL_OUT_IGNORE_THE_REST_949298_51_1; state 1

---

It's been an excellent run for the last few months, but no tasks available for download

As of 22 Jun 2020, 11:02:34 UTC [ Scheduler running ]
Total queued jobs: 0
In progress: 599,832
Successes last 24h: 512,637

---

It's been an excellent run for the last few months, but no tasks available for download

Thanks. I wish they would tell us whether it is an operational glitch with the servers, or a longer-term issue with supply.
We need to manage our machines too, if we are to do the work effectively.

---

It's been an excellent run for the last few months, but no tasks available for download

Thanks. I wish they would tell us whether it is an operational glitch with the servers, or a longer-term issue with supply.
We need to manage our machines too, if we are to do the work effectively.

On the main page, https://boinc.bakerlab.org/rosetta/ , is "total queued jobs". This varies from 0 to 12 million. Just keep an eye on that. A server glitch wouldn't show that going down to 0. I'm assuming at the moment we're coming to the end of a set of work and awaiting the scientists analysing that before creating more.

Do what I do, use more than one project so the computer is always busy. If you class Rosetta as much more important than the other project, simply set the resource share at https://boinc.bakerlab.org/rosetta/prefs.php?subset=project and the equivalent at your other project to either a much higher number for Rosetta, or 0 for the other project (which means it only runs when Rosetta has no tasks).

Or of course just let the machines have a rest? Not sure why some people get upset when there's no work to do.

---

Error after pc reboot:

22/06/2020 08:32:06 | Rosetta@home | [error] garbage_collect(); still have active task for acked result rb_06_18_29700_29099__t000__0_C1_SAVE_ALL_OUT_IGNORE_THE_REST_949298_51_1; state 1

I'm guessing, but could that mean your PC sent a task back but didn't finish getting the response before you rebooted? So the server has the result, but your PC thinks it doesn't. Do you have a completed task in the list?

---