Finally hadcm3s finishing 100 %, without errors and after that they can't complete and errored out.

[quote]<core_client_version>7.12.1</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073740791 (0xc0000409)</message>
<stderr_txt>

That's a Windows error message. It's been around for years.
Googling it doesn't give anything that looks useful for end users.

Batch 774 SAFR50 region. These are using on the restart files from batch 741.

Server Status page showing 6,800ish tasks at the moment but not sure if that is all or if page updated while hopper still being filled.

Batch 774 SAFR50 region. These are using on the restart files from batch 741.

If you are running any tasks from this batch please check them because I have 2 batch 774 tasks stuck in the initialisation of the regional model (project team notified).

BOINC Manager shows the elapsed time and progress increasing as expected, but if you open the task properties dialog box the CPU time isn't changing from "---". If checkpoint or task debug is enabled BOINC's event log shows that no checkpoints are being made. When BOINC is restarted the elapsed time and progress revert to 0.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Thyme Lawn -

I had two 774 tasks waiting in the wings, so I started them to see what would happen. They both failed within seconds with some kind of "Error in Namelist".

Make sure you don't have a hidden window (Alt-Tab) with a Fortran runtime error.

---

@WB8ILI I run BOINC as a service. Yes, it does mean I can't run GPU applications on other projects, but it also means that tasks which fail with a Windows runtime error don't generate the pop-up dialog box you can get in a non-service install.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

I had two 774 tasks waiting in the wings, so I started them to see what would happen. They both failed within seconds with some kind of "Error in Namelist".

Make sure you don't have a hidden window (Alt-Tab) with a Fortran runtime error.

I have told the project about this to add to what Thyme and others have told them.

BOINC Manager shows the elapsed time and progress increasing as expected, but if you open the task properties dialog box the CPU time isn't changing from "---". If checkpoint or task debug is enabled BOINC's event log shows that no checkpoints are being made. When BOINC is restarted the elapsed time and progress revert to 0.

Do they still use a whole core of cpu time when doing this?

I received 4 of the batch 774 WU’s overnight. Started them as a test. All failed in less than 2 minutes with Fortran run time error. Win 10 on Intel 2.66 GHz processor with 8 Gb of ram.

---

BOINC Manager shows the elapsed time and progress increasing as expected, but if you open the task properties dialog box the CPU time isn't changing from "---". If checkpoint or task debug is enabled BOINC's event log shows that no checkpoints are being made. When BOINC is restarted the elapsed time and progress revert to 0.

Do they still use a whole core of cpu time when doing this?

No. SysInternals Process Explorer was showing 2 idle cores of the 8 on my i7 with less than 0.1 seconds of CPU time for both of the batch 774 models' controller + global + regional processes.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Any sign of new work in the pipeline? I’m starting to feel like Old Mother Hubbard. The cupboard is bard and my poor dogs are getting none.

---

No idea at all. Not even any hints of the withdrawn batch coming back with correct stash files or whatever was wrong fixed. Sometimes information appears on the message boards that moderators can report issues with batches on in advance, sometimes the batch doesn't go up there till it is released. So no information doesn't always mean nothing is on the way.

I have relatively slow machines so they are still busy but I would guess from the dropping number of tasks in progress that there are a lot of machines with no work by now.

10,000 10 month models in 2 batches.

Yum :)

5% guess is about 50 hours on my fast machines.

Any sign of new work in the pipeline?

batch 777 safr50 16 month tasks
about 8,000 at a guess but may be more if they are still filling the hopper.

Edit:Looks like that is all and they are going fast.

Are these the previous batch 774 ones that kept failing?

Same research project, but hopefully, with the "Oops" removed.

New batch 778, SAS50. Haven't looked at total number yet but I think from only 784 ready to send on status page, quite a small batch.

New batch 778, SAS50. Haven't looked at total number yet but I think from only 784 ready to send on status page, quite a small batch.

Yes, 1000 x 22-month South Asia at 50 km (batch list).

... and 3172 x 16-month Southern Africa at 50 km (batch list).

... and 3172 x 16-month Southern Africa at 50 km (batch list).

The goal is to study October 2015 - March 2016 heat wave and drought in Southern Africa

778's have big downloads.124.76MB! 34 minutes and only half way through uploading it's first zip.
779 and 780 also released. Part of the same project as 777

Edit: Batches seem to be behaving like buses.