Right now they are 32 core with 16gb of RAM. Which should be enough for crunching.

Some Rosetta 4.20 Tasks require over 2GB of RAM.
32*2= way more than 16GB.
Although the larger RAM Tasks have been very few and far between, 500MB to 1GB has been the usual range for Rosetta 4.20 Tasks lately. And 32*.5= all your RAM.

16GB RAM on a system with 64 cores/threads is way, way, way too little.

---

Grant
Darwin NT

A flock of work units arrived recently that are behaving oddly, well, all but one of them...

I have one machine, a workstation Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz / Arch Linux, which crunches Rosetta and WCG packets fine. A few months ago, added a really old dual Intel(R) Xeon(TM) CPU 2.80GHz machine (old Dell server, latest Ubuntu server LTS.) The old machine was getting Rosetta Beta workunits and choking on them; error, error, error... it was able to crunch through several non-beta workunits though. Thought it was the old CPUs, like an unsupported instruction or something. Reading this, now thinking it was bad workunits.

And we're back...

Looks like the whole website went down for about 10hours today.
Couldn't even get to the Rosetta home page let alone upload results.
Everything going through fine now

---

All my units are getting validate errors now.

GDB: you are not alone in all returned results getting valitated errors. The top 10 CPUs I checked plus my own got the same verdict.

Yep, The Validator is borked,

For me, anything returned from 3 Apr 2024, 22:02:46 UTC fails, and a quick look at th top computers shows the same thing- everything going back at present fails Validation.

If someone could get the Projects attention?

---

Grant
Darwin NT

If someone could get the Projects attention?

+1
After the over 60 wus failed some hrs ago, i'm ready to upload about ten wus.
Have i to stop the upload?

---

Let's see if these work units are still credited. But I have the feeling that after calculating they will go straight into the trash can. Unfortunately, one computer will be running until this afternoon and will probably only produce garbage before I can separate it from Rosetta.

---

Let's see if these work units are still credited.

If it's not Valid, there is no Credit.

---

Grant
Darwin NT

Have i to stop the upload?

It will stop you from getting new work, but it is the only way to stop returned work from not Validating until the project fixes the issue.
They could also re-run the validation of the presently failed Tasks, but i don't like the odds of that actually happening.

---

Grant
Darwin NT

it will stop you from getting new work, but it is the only way to stop returned work from not Validating until the project fixes the issue.

The problem is that some of these wus are near the deadline.
It's a pity to throw away the work done.... (i don't care a lot about points, i care about science)

---

The problem is that some of these wus are near the deadline.
It's a pity to throw away the work done.... (i don't care a lot about points, i care about science)

And it will stop you from being able to get new work from other projects as well.
So return them & get more work & hope the project fixes up all the failed Validation Tasks when they fix the Validation issue.

As it is, if they don't Validate then they won't (or they shouldn't) go into the science database. If it's not Valid, then it's not going to be of use to science. That's the whole point of Validation, otherwise it's just garbage in, and then garbage out.

---

Grant
Darwin NT

As it is, if they don't Validate then they won't (or they shouldn't) go into the science database. If it's not Valid, then it's not going to be of use to science. That's the whole point of Validation, otherwise it's just garbage in, and then garbage out.

That's the point!!
Thousands of wu wasted...

---

I don't want to recieve more posts about this unless it is a post from staff member that fixed it.

Let's see if these work units are still credited.

If it's not Valid, there is no Credit.

Rosetta does (or did) have an overnight scheduled job that sought out tasks that completed successfully but didn't validate in order to credit them anyway, but that clearly hasn't happened yet (overnight on the West Coast presumably).

Let me see if I can revive my contact to the project team, seeing as I haven't contacted them for a year.
Maybe they'e less fed up of me by now.

Edit: Email sent. We wait

---

unless it is a post from staff member that fixed it.

Staff member??

---

28 tasks with validate error...great....but i suppose thats just the way it goes with a beta.

28 tasks with validate error...great....but i suppose thats just the way it goes with a beta.

NO. That is the way Rosetta has chosen.

There should be a preference option that allows you to OPT OUT of the BETA work units. This is ESPECIALLY true if the project gives ZERO credit for the computing. About 25% of the BETA work units I am receiving run for several hours, finish without errors, and are marked INVALID as wasted work.

These INVALID results are a problem with the Rosetta BETA binary. Rosetta has chosen to run all the BETA units for hours instead of minutes. They could run the BETA binaries for minutes instead of hours until the BETA binaries have some successes.

28 tasks with validate error...great....but i suppose thats just the way it goes with a beta.

They might have beta in the name but these have been the production WUs for some time now.

Let's see if these work units are still credited.

If it's not Valid, there is no Credit.

Rosetta does (or did) have an overnight scheduled job that sought out tasks that completed successfully but didn't validate in order to credit them anyway, but that clearly hasn't happened yet (overnight on the West Coast presumably).

Let me see if I can revive my contact to the project team, seeing as I haven't contacted them for a year.
Maybe they'e less fed up of me by now.

Edit: Email sent. We wait

Looking like they're still fed up with me... no response & no change I can notice

---