Hopefully it means something to someone somewhere.

Ah: divided by a common language… :-⁠)
Perfectly comprehensible this side of the pond.

tin o[f] fizzy stuff = can of soda
duff = defective
guff = nonsense

Also “septic tank” is occasionally used as rhyming slang for “Yank”, but I don’t think that’s what’s meant here.

Lol! Too much information.

Wrt whether that's what was meant, I didn't think it was wrt the slang. I thought it was wrt to the CGCCGGG stuff in the task names

Isn't that genetic code? I've assumed it was. Whether it is or not, it's only important it means something to them, not to us.

Unless they're too dumb to understand what they're naming means - far be it for me to exclude all possibilities...

I was going to say that, but what about the Y B and X?

same here, 10x C4s waiting for work due to the 6GB requirement.
Hopefully soon there will be a lot of tasks for the small computers available.
In the meanwhile i let them crunch WCG.

I have never seen such easy Rosettas. They all under 500 MB on 50 Ryzen 3000 cores (Ubuntu 20.04.2).
But there is always WCG.

PS - Even less on Win10. Under 200 MB on 10 Ryzen3600 cores.

---

I have never seen such easy Rosettas. They all under 500 MB on 50 Ryzen 3000 cores (Ubuntu 20.04.2).
But there is always WCG.

PS - Even less on Win10. Under 200 MB on 10 Ryzen3600 cores.

Those may be taking advantage of a way that compilers often organize the compiled code. The read-write sections cannot be shared between tasks, but all the tasks running can share a read-only section.

I allocate 28Gb from 32Gb total
They don't need the RAM. If they run, they generally use 300Mb, not 5 or 6Gb each. It's more than a bit crackers.

Once you've started them, I wonder if Boinc adjusts to what they're actually using, or leaves the requested 6.5GB there just in case? You could see what happens if you try to run only Rosettas.

I've speculated that's the case too. Demand a maximum amount to start, then let the task decide once it's running.
I cleared all the problem tasks on my laptop before by setting NNT to Rosetta & WCG and only when all other tasks had completed did my problem task start.

That was a while ago.

Now I've got another one problem Rosetta task. I've suspended all unstarted Rosetta tasks, set NNT again, kept my last few WCG tasks so that as each of the 3 running Rosetta tasks finish, it switches to less-demanding WCG tasks to see if enough RAM is freed up.
If it isn't, let the WCG tasks complete as well until there's only the one problem Rosetta task.
If it runs, fine. If it doesn't, abort it.
What a performance...

---

Hopefully it means something to someone somewhere.

Ah: divided by a common language… :-⁠)
Perfectly comprehensible this side of the pond.

tin o[f] fizzy stuff = can of soda
duff = defective
guff = nonsense

Also “septic tank” is occasionally used as rhyming slang for “Yank”, but I don’t think that’s what’s meant here.

Lol! Too much information.

Wrt whether that's what was meant, I didn't think it was wrt the slang. I thought it was wrt to the CGCCGGG stuff in the task names

Isn't that genetic code? I've assumed it was. Whether it is or not, it's only important it means something to them, not to us.

Unless they're too dumb to understand what they're naming means - far be it for me to exclude all possibilities...

I was going to say that, but what about the Y B and X?

1) I don't know
2) It's none of my business and doesn't impinge on me or anyone else in any way

---

They have to be taught at some time. Which activity do you think they are allowed to do first? Or do you think that they can start both at the same time, with no tests of what the are doing works properly?

Christ...

What? It's a valid point. Why would you think a biologist knows about the code?

When you're in a hole, stop digging

---

What? It's a valid point. Why would you think a biologist knows about the code?

All the cool kids who work on projects like this one, using proprietary software, know how to code, grandpa. Like just about everything else in life, some are better at it than others. Some are experienced and others are not.

SiDock@home is chugging along merrily on most of my boxes. I'm getting the memory appetite notice on the boxes with less than 8gb of RAM. One box scooped up some projects for Rosetta@home, so the comment that they are squeezing out a few every so often seems to be correct.

Over the course of this afternoon I’ve had 6 segv errors, all on files starting miniprotien.

Anyone else? Or do I start checking my hardware?

Over the course of this afternoon I’ve had 6 segv errors, all on files starting miniprotien.

Anyone else? Or do I start checking my hardware?

I got a signal 11, but nothing about a segv.
https://boinc.bakerlab.org/rosetta/result.php?resultid=1365882560

---

I have never seen such easy Rosettas. They all under 500 MB on 50 Ryzen 3000 cores (Ubuntu 20.04.2).
But there is always WCG.

WCG are not getting any tasks from me. Their admins are too arrogant.

I allocate 28Gb from 32Gb total
They don't need the RAM. If they run, they generally use 300Mb, not 5 or 6Gb each. It's more than a bit crackers.

Once you've started them, I wonder if Boinc adjusts to what they're actually using, or leaves the requested 6.5GB there just in case? You could see what happens if you try to run only Rosettas.

I've speculated that's the case too. Demand a maximum amount to start, then let the task decide once it's running.
I cleared all the problem tasks on my laptop before by setting NNT to Rosetta & WCG and only when all other tasks had completed did my problem task start.

That was a while ago.

Now I've got another one problem Rosetta task. I've suspended all unstarted Rosetta tasks, set NNT again, kept my last few WCG tasks so that as each of the 3 running Rosetta tasks finish, it switches to less-demanding WCG tasks to see if enough RAM is freed up.
If it isn't, let the WCG tasks complete as well until there's only the one problem Rosetta task.
If it runs, fine. If it doesn't, abort it.
What a performance...

If it's too big, I run it on a bigger machine. My PCs have 8, 8, 8, 16, 36, 36, and 64GB.

Hopefully it means something to someone somewhere.

Ah: divided by a common language… :-⁠)
Perfectly comprehensible this side of the pond.

tin o[f] fizzy stuff = can of soda
duff = defective
guff = nonsense

Also “septic tank” is occasionally used as rhyming slang for “Yank”, but I don’t think that’s what’s meant here.

Lol! Too much information.

Wrt whether that's what was meant, I didn't think it was wrt the slang. I thought it was wrt to the CGCCGGG stuff in the task names

Isn't that genetic code? I've assumed it was. Whether it is or not, it's only important it means something to them, not to us.

Unless they're too dumb to understand what they're naming means - far be it for me to exclude all possibilities...

I was going to say that, but what about the Y B and X?

1) I don't know
2) It's none of my business and doesn't impinge on me or anyone else in any way

Sometimes they're interesting. There's the drhicks ones. Some Universe tasks said "on_error" which is rather pessimistic. I wonder what Rosetta's "save all out" means?

They have to be taught at some time. Which activity do you think they are allowed to do first? Or do you think that they can start both at the same time, with no tests of what the are doing works properly?

Christ...

What? It's a valid point. Why would you think a biologist knows about the code?

When you're in a hole, stop digging

I'm not in a hole and I think you're confusing the two people you're replying to.

What? It's a valid point. Why would you think a biologist knows about the code?

All the cool kids who work on projects like this one, using proprietary software, know how to code, grandpa.

I disagree. I'm sure you can become a brilliant biologist without knowing the first thing about coding.

Over the course of this afternoon I’ve had 6 segv errors, all on files starting miniprotien.

Anyone else? Or do I start checking my hardware?

I got a signal 11, but nothing about a segv.
https://boinc.bakerlab.org/rosetta/result.php?resultid=1365882560

Yes, signal 11 is a segv fault.

All the cool kids who work on projects like this one, using proprietary software, know how to code, grandpa.

I disagree. I'm sure you can become a brilliant biologist without knowing the first thing about coding.

+1
They are not pure coders, they are biologists that use code.
They want results, not to create "beautiful" (and optimized) code.
And, in the past, Rsj5, analizing the rosetta sw said that is "fluffy code".

---

I just suspended a task that has been running for 16:19:35 (stuck at 00:10:15 remaining). Any ideas how to get this one to finish and get credit for it?

I just suspended a task that has been running for 16:19:35 (stuck at 00:10:15 remaining). Any ideas how to get this one to finish and get credit for it?

It sometimes helps to shut down BOINC, then restart BOINC and then the task.

Progress seeming to freeze near the end of a task is often a sign that the task was created with a severe underestimate of how long the task would run.

It sometimes helps to shut down BOINC, then restart BOINC and then the task.

Progress seeming to freeze near the end of a task is often a sign that the task was created with a severe underestimate of how long the task would run.

OK, thank you. I just tried that (rebooted in between as well), and it reset to ~16% complete... Maybe I just kill it if it's going to run forever?