LHC@home

no jobs since last night; consequently, the tasks download queue was stopped

no jobs since last night; consequently, the tasks download queue was stopped

The workflow I injected yesterday is not sending jobs to the Condor server, and the previous one drained its queue. I've submitted a new workflow; if it also doesn't start then I'll raise a ticket with CERN IT.

---

no jobs since last night; consequently, the tasks download queue was stopped

The workflow I injected yesterday is not sending jobs to the Condor server, and the previous one drained its queue. I've submitted a new workflow; if it also doesn't start then I'll raise a ticket with CERN IT.

It looks like they were blocked by a bug in the testbed system. They've been manually moved to "staged" and one is now showing as "running-open" so hopefully jobs will start flowing soon.
[Edit] Yes, I'm starting to see numbers in the "pending" and "running" columns. [/Edit]

---

Back again,
thank you, Ivan.

Ivan wrote;

They've been manually moved to "staged" and one is now showing as "running-open" so hopefully jobs will start flowing soon.
[Edit] Yes, I'm starting to see numbers in the "pending" and "running" columns. [/Edit]

tasks and jobs are working well now.

However, something must have happened to the credit points count:

while so far, on a given computer it looked like this:
Run time: 50,758.06 - CPU time: 48,439.31 - points: 457.32

it now shows:
Run time: 51,814.97 - CPU time: 49,660.55 - points: 15.63

what happened?

Reported device peak FLOPS

Run time: 50,758.06 - CPU time: 48,439.31 - points: 457.32

Device peak FLOPS 3.40 GFLOPS

Run time: 51,814.97 - CPU time: 49,660.55 - points: 15.63

Device peak FLOPS 0.12 GFLOPS

However, something must have happened to the credit points count:
while so far, on a given computer it looked like this:
Run time: 50,758.06 - CPU time: 48,439.31 - points: 457.32
it now shows:
Run time: 51,814.97 - CPU time: 49,660.55 - points: 15.63
what happened?

This is also, when a new .vdi is started.
After a few runnings, it coming back with the Credits.

Reported device peak FLOPS

Run time: 50,758.06 - CPU time: 48,439.31 - points: 457.32

Device peak FLOPS 3.40 GFLOPS

Run time: 51,814.97 - CPU time: 49,660.55 - points: 15.63

Device peak FLOPS 0.12 GFLOPS

this is really strange. I didn't change anything on that machine, neither hardware nor software.
Any idea how come?

My last three CMS have errored with EXIT_NO_SUB_TASKS, and the number of unsent tasks is down to 62.
It looks like the automatic shutdown mechanism is working, and we are heading into stormy weather.

the number of unsent tasks is down to 62.

now, the number has reached zero :-(

Sorry, I went back to sleep this morning without checking the number of jobs running... New batch is on its way.
Good thing I only have one birthday a year! 🙂

---

Good thing I only have one birthday a year! 🙂

congratulations, anyway :-)

Good thing I only have one birthday a year! 🙂

congratulations, anyway :-)

Cheers, Erich.. I'll have a rotationally symmetric birthday in 27 years,,, Not sure I'll last that long!

---

Are you 50, 61, 72 or 74?

Happy Birthday anyway!!

---

Happy Birthday Ivan!
:-)

Are you 50, 61, 72 or 74?

No, not by my definition of rotationally symmetric, but I'll give you points for two of them.
I should have said that this one is, too.

Happy Birthday anyway!!

Thanks, everyone.

---

Ah, perhaps you meant "flippable top to bottom", leaving only 88 and 101. So then you're either 61 or 74... But neither of those seems flippable to me - sigh!

So maybe you need to help me (us?) further...

Ciao, Ben

---

Ivan,
good luck and health for your new year.
Ben,
my favorite for Ivans Birthday is hex 48 ;-)).

Well my hint is Ivan is older than me and younger than Ben

Well my hint is Ivan is older than me and younger than Ben

That's almost certainly true. And as I see it, 1 and 8 are pretty much (180-degree) rotationally symmetric in themselves, 2 & 5 aren't (they need a reflection as well), which leaves 6 and 9.

---