Even clicking reply, typing +1, then clicking send takes more time, let alone the time taken checking if I had any
I can't bring myself to care, let alone mention it

Is there a remote hope that someone of the team reads, before or later, the forum and take a solution for an old bug??
A hope, remote hope...

---

Even clicking reply, typing +1, then clicking send takes more time, let alone the time taken checking if I had any
I can't bring myself to care, let alone mention it

And when you have over 30 wus bugged in the last 5 hrs, what do yo do?

---

Even clicking reply, typing +1, then clicking send takes more time, let alone the time taken checking if I had any
I can't bring myself to care, let alone mention it

Is there a remote hope that someone of the team reads, before or later, the forum and take a solution for an old bug??
A hope, remote hope...

After a few years now, I think we can be certain the answer is a firm no.

I was taken by a reply I had (in the days when I was being replied to - also years ago) when a lot higher proportion of tasks were getting rejected and, rather than delete the offending tasks, because they only ran for 15-20secs of CPU time, was to let them run and error out because even 30 tasks would only be 5-600secs of CPU time (actually core time, so divide by the number of cores for actual seconds of CPU time) and that was several orders of magnitude less work than coding some way of deleting them before they went out. During which exercise, a lot of good tasks would be taken out at the same time, so it was counterproductive in a multitude of ways.

And that's what happened.

The same applies here. No-one in their right mind would do any different.

The only real problem is the amount of time wasted complaining about it.

Tbh, I think it's exactly the same reason why <I> stopped getting replies. A complete waste of time and effort.
So, if you feel bad about my reply here, take a moment to think about my situation...

Meanwhile, boinc-process server is down again - no validation going on right now - 200k waiting in the queue

---

Meanwhile, boinc-process server is down again - no validation going on right now - 200k waiting in the queue

Almost 300k now.

---

Grant
Darwin NT

Almost 300k now.

Almost 400k now.

---

Grant
Darwin NT

So, if you feel bad about my reply here, take a moment to think about my situation...

I'm not bad about your reply, I'm sorry for your pessimism.
I continue to think that if a software is bugged, it's good thing to advice developers.

Don't they read it? Too bed for them.

---

Almost 300k now.

Almost 400k now.

I think it went to almost 500k, but I took a look at 20:35 UK time just as parts of boinc-process came back online and after a refresh it was all back
A glance now (01:38 UK time) and it shows 266k, so it's coming down slowly

---

So, if you feel bad about my reply here, take a moment to think about my situation...

I'm not bad about your reply, I'm sorry for your pessimism.
I continue to think that if a software is bugged, it's good thing to advice developers.

Don't they read it? Too bad for them.

I'm not a coder of any kind, but the impression I get is that it's an error-trapping issue rather than a bug (you could say that's the same thing, I accept).
The impression I get (but may be very wrong) is that tasks are seeded randomly, but don't double-check if the random seed is out of bounds so it can be re-seeded, and errors out as a result.
It's a <perfect>, even if ugly, solution.
It happens so rarely and with such little consequence (wasted CPU time is approx zero) that it's not worth the effort to correct among a batch somewhere around a million tasks.
The rest give them the results they need.

It may offend from a user pov, but I think from a researcher pov it's neither here nor there.
It's very likely they <do> know. It just doesn't matter.
And, as always, we're here for the project's needs. They don't exist for ours.

The tail has never wagged the dog at this project - unlike many other projects.
That's been made very clear to me. It's not pessimism on my part, but realism.
I don't need to be told twice, even if others need to be told ten or twenty times and still not take the hint.
I know that sounds harsh, but I don't know how else to say it.

---

Almost 300k now.

Almost 400k now.

I think it went to almost 500k, but I took a look at 20:35 UK time just as parts of boinc-process came back online and after a refresh it was all back
A glance now (01:38 UK time) and it shows 266k, so it's coming down slowly

I'm just in the final stages of clearing down all the excess WCG tasks Boinc brought down from the previous Rosetta outage and we're out of Rosetta tasks again.
So frustrating...

---

I'm just in the final stages of clearing down all the excess WCG tasks Boinc brought down from the previous Rosetta outage and we're out of Rosetta tasks again.
So frustrating...

A relatively small number of tasks available - showing 230k on the front page 3hrs ago. Hopefully part of more, but may not be.
It's something

---

A relatively small number of tasks available - showing 230k on the front page 3hrs ago. Hopefully part of more, but may not be.
It's something

Snd seems a new kind of simulations: "testmpnn_hallucinated" and "testmpnn_diffusion"

---

A relatively small number of tasks available - showing 230k on the front page 3hrs ago. Hopefully part of more, but may not be.
It's something

Snd seems a new kind of simulations: "testmpnn_hallucinated" and "testmpnn_diffusion"

Yup - wonder what that's all about.
A few more tasks becoming available too - still not a great amount. Showing 475k an hour ago on the front page.
Every little bit helps

---

Snd seems a new kind of simulations: "testmpnn_hallucinated" and "testmpnn_diffusion"

Yup - wonder what that's all about.

Maybe related to "message-passing neural networks" (mpnn), like this

---

Graphics work with these tasks.

I think it went to almost 500k, but I took a look at 20:35 UK time just as parts of boinc-process came back online and after a refresh it was all back
A glance now (01:38 UK time) and it shows 266k, so it's coming down slowly

Now the server are green, but there are over 18k wu pending validation. Increasing.

---

Graphics work with these tasks.

And also wus seems ok, no errors despite the name "test"....

---

Snd seems a new kind of simulations: "testmpnn_hallucinated" and "testmpnn_diffusion"

Yup - wonder what that's all about.

Maybe related to "message-passing neural networks" (mpnn), like this

Very likely. Thanks for the link - looks like good work.

---

I think it went to almost 500k, but I took a look at 20:35 UK time just as parts of boinc-process came back online and after a refresh it was all back
A glance now (01:38 UK time) and it shows 266k, so it's coming down slowly

Now the server are green, but there are over 18k wu pending validation. Increasing.

Now pink - boinc-process is down again and 56k awaiting validation.
And not too many tasks left to come down either.
We continue to be very hand-to-mouth atm

---

Some more work would be nice.
It's been freezing the last few mornings here, and the system has been keeping the lounge room almost comfortable.

Buit now it's out of work, and tomorrow morning if more work doesn't come along, it'll be almost as cold inside as it is outside (or an upgraded version over at Ralph & some new work there would be nice- either this or that, or even both would be nice).

---

Grant
Darwin NT

Still... 'completed awaiting validation'...
More credits gone, along with electricity and time?