Greetings,

Well, I just discovered something new about that task that is not showing any progress:

It is showing a minute increase in progress. It's gone from 0.455% to 0.457%. And that remaining estimate has taken off. It is going UP. It is currently at 38 days 3 hours and counting.

This is weird! It should be running in PANIC mode since the deadline is this Friday May 1st. Should I abort or hope it settles down?

Have a great day! :)

Siran

Greetings,

I'm so glad I didn't do anything with that task. I just logged back into Linux from doing some stuff in WoW and the tasks is working normally.

All is back to status quo... lol :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Holy moley! What is up with this task? That is a BOAT load of errors!

It crashed out after 7 seconds, so no big deal.

But you are running an old version of Boinc Manager, so always best to upgrade it. Bugfixes involved

---

Holy moley! What is up with this task? That is a BOAT load of errors!

It crashed out after 7 seconds, so no big deal.

But you are running an old version of Boinc Manager, so always best to upgrade it. Bugfixes involved

Hi Sid,

I'm running BOINC on Linux Mint v19.3. The latest version on the BOINC website is 7.4.22. I'm running 7.14.2. They have a development version 7.16.6, but I don't do development versions.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Holy moley! What is up with this task? That is a BOAT load of errors!

It crashed out after 7 seconds, so no big deal.

But you are running an old version of Boinc Manager, so always best to upgrade it. Bugfixes involved

Hi Sid,

I'm running BOINC on Linux Mint v19.3. The latest version on the BOINC website is 7.4.22. I'm running 7.14.2. They have a development version 7.16.6, but I don't do development versions.

Have a great day! :)

Siran

Understood - I'd be the same. Hopefully a stable version becomes available for you soon.

---

Greetings,

I gotta new badge today! :) Things are looking up. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I have a weird question:

A couple, 3 days ago I decided to get Rosetta started on my old Pentium dual core laptop. It does not have the ram to run 2 tasks so it only runs 1. This laptop is OLD! I got it back in 2006 and it still runs just fine, at least in 32 bit. It won't take Windows 10 and the newest Linux so I paid Micro$oft for Win 7 Pro 32 bit.

Here's the thing. My 8th generation main (i7 8086k w/32GB Ram) has errors almost daily while the laptop has yet to have any. Is slower better than almost top of the line (turtle vs hare)? I know, weird question. ;)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I have a weird question:

A couple, 3 days ago I decided to get Rosetta started on my old Pentium dual core laptop. It does not have the ram to run 2 tasks so it only runs 1. This laptop is OLD! I got it back in 2006 and it still runs just fine, at least in 32 bit. It won't take Windows 10 and the newest Linux so I paid Micro$oft for Win 7 Pro 32 bit.

Here's the thing. My 8th generation main (i7 8086k w/32GB Ram) has errors almost daily while the laptop has yet to have any. Is slower better than almost top of the line (turtle vs hare)? I know, weird question. ;)

Have a great day! :)

Siran

No, faster is always better for Rosetta (at least science-results-wise). The reason for your errors on your faster computer appears to just be bad luck. You may very well have gotten a bad batch of WUs, such things happen. If you are paranoid, select no new tasks on your main computer, wait for the current tasks to complete and readd the project (they updated the URL anyways, so remember to change the URL to https://boinc.bakerlab.org/rosetta/ when adding the project, this will not cause errors, readd the project when it's convenient)

Wait.. just realized the most of the tasks that errored out for you succeeded on other machines...

I don't know what's up. I'm not technical enough to understand the error messages, but I do know it can't possibly be an issue of your CPU being too fast. The 8086K isn't nearly the fastest CPU on this project, faster CPUs run just fine.

-[ snip ]-

Have a great day! :)

Siran

No, faster is always better for Rosetta (at least science-results-wise). The reason for your errors on your faster computer appears to just be bad luck. You may very well have gotten a bad batch of WUs, such things happen. If you are paranoid, select no new tasks on your main computer, wait for the current tasks to complete and readd the project (they updated the URL anyways, so remember to change the URL to https://boinc.bakerlab.org/rosetta/ when adding the project, this will not cause errors, readd the project when it's convenient)

Hi Tom,

If there are CPUs running faster than mine, than they are overclocked and running >4.0GHz. ;)

Nah, I'm not paranoid about it. I would get errors when I was doing SETI. It just seemed weird that my laptop hasn't had any errors, yet, but my main gets them almost every day.

I always set NNT after I have filled my cache on my main. That way I don't get any tasks running in panic mode. ;) The laptop cache is much smaller so I just let it go. Both are set to NNT right now because of the URL notice.

I was about to ask about the notice I keep getting on both machines:

Rosetta@home: Notice from BOINC
This project is using an old URL. When convenient, remove the project, then add https://boinc.bakerlab.org/rosetta/
5/2/2020 8:01:29 AM Minty-Winders, Rick-LT

But you answered it for me. :) Thanks!

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I have a weird question:

A couple, 3 days ago I decided to get Rosetta started on my old Pentium dual core laptop. It does not have the ram to run 2 tasks so it only runs 1. This laptop is OLD! I got it back in 2006 and it still runs just fine, at least in 32 bit. It won't take Windows 10 and the newest Linux so I paid Micro$oft for Win 7 Pro 32 bit.

Here's the thing. My 8th generation main (i7 8086k w/32GB Ram) has errors almost daily while the laptop has yet to have any. Is slower better than almost top of the line (turtle vs hare)? I know, weird question. ;)

Have a great day! :)

Siran

I’d put it down to volume of throughput. The slow machine using a single core does not process anything like as many WUs as your main rig and is therefore is far less likely to see an error. If your main rig sees one a day then it will be more than 2 or 3 days before you laptop is likely to see one.

Greetings,

Oops! Something has happened since the url change me thinks. I go to my tasks page and click any link such as the Error or Next or Validation pending and I get a page that says:

Already logged in
You are logged in as Siran d'Vel'nahr . Log out

:(

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Oops! Something has happened since the url change me thinks. I go to my tasks page and click any link such as the Error or Next or Validation pending and I get a page that says:

Already logged in
You are logged in as Siran d'Vel'nahr . Log out

:(

Have a great day! :)

Siran

Greetings,

I just discovered that the above only happens if you select the Task link on the account page. If you select the computers link and then click the Tasks link for each computer, you can see the error, valids, invalids, etc. When I get a chance I'll look at the urls displayed at the bottom for each "different" link. ;)

[edit]The only difference in the urls is that the tasks link looks for tasks for all computers while the task link per computer only looks for tasks for that computer. Confused? ;)[/edit]

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Admin is fixing the links, you may have caught things before changes were completed, please try again later today. See post here

---

Rosetta Moderator: Mod.Sense

Admin is fixing the links, you may have caught things before changes were completed, please try again later today. See post here

Hi Mod,

It's fixed. Thanks! :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

On the Leader board...
Until you get to #76 (8 threads) and #131 (32 threads) you don't see ANY systems that are running less than 48-64 threads.

It is amazing the number of server class/HEDT systems with huge core counts that are running here.

Tom M

---

Help, my tagline is missing..... Help, my tagline is......... Help, m........ Hel.....

Holy moley! What is up with this task? That is a BOAT load of errors!

It crashed out after 7 seconds, so no big deal.

But you are running an old version of Boinc Manager, so always best to upgrade it. Bugfixes involved

Hi Sid,

I'm running BOINC on Linux Mint v19.3. The latest version on the BOINC website is 7.4.22. I'm running 7.14.2. They have a development version 7.16.6, but I don't do development versions.

Have a great day! :)

Siran

There are a couple of options available to you.
1. Us LoctusOfBorg’s ppa to get 7.16.6
2. Us the Ubuntu 7.16.6 from the BOINC web site

Despite what the BOINC web site says DA released 7.16.5 for Windows and 7.16.6 for Mac and Linux. There is however an issue with it, in that the default log flags are turned off. That can be worked around with a cc_config file turning them on. Linux comes with a default cc_config file with them explicitly set anyway.

---

BOINC blog

On the Leader board...
It is amazing the number of server class/HEDT systems with huge core counts that are running here.

Tom M

I’ve only got a measly 88 threads running between 8 machines :-)

I really need to get myself one of those 128 thread machines.

---

BOINC blog

So one downside of running longer WU times on 24/7 machines while keeping a minimal queue is the occasional double work. What happens to the jobs in these cases?

Take for example this: https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1049461192
One was a 8 hour job that was returned after the deadline and produced this: https://boinc.bakerlab.org/rosetta/result.php?resultid=1167217453
After the deadline passed my machine was issued the task quickly and started crunching the same unit but for a 24 hour period and produced this: https://boinc.bakerlab.org/rosetta/result.php?resultid=1170418333

In this scenario, what happens? Does my 24 hour crunch just get tossed or are both results valid?

I've seen this happen on several of my machines multiple times. I really don't want to go track down each double work unit and manually abort them. Does it matter?

but for a 24 hour period and produced this: https://boinc.bakerlab.org/rosetta/result.php?resultid=1170418333

In this scenario, what happens? Does my 24 hour crunch just get tossed or are both results valid?

Check the Work Unit- both the Tasks have been completed, Validated & granted Credit.



It's good that the project does cancel unstarted Tasks if they aren't needed, but it would be even better if they would configure the system so that it's doesn't resend a Task until there is no chance of it being returned, that way they won't have to cancel so many Tasks.

The deadline is 3 days, there is a 10 hour extension on the actual CPU Target time before the watchdog kicks in.
If they are using a Grace period, then they need to configure the servers so that a Task isn't resent until the deadline, grace period & the 10 hour Watchdog timer cut off period, and maybe an extra 2 hours just in case, have all passed. Once that period of time has passed, then the existing Task should be declared "Not returned by deadline" & an Error & no Credit granted. And then the next Task should then be sent out.
Don't send it until it is needed- if it's being cancelled, then it wasn't needed.

---

Grant
Darwin NT

Check the Work Unit- both the Tasks have been completed, Validated & granted Credit.

Yes this part is obvious from a reporting standpoint, but from the research standpoint what happens? Do both completed units go to the researchers for analysis? The same task on two machines, run for 2 different amounts of time produced different numbers of decoys. I produced 18 decoys, but TardyMcLatekin's kicked out 5. Were the first 5 of mine the same as the other computer who was fashionably late?