This is the main batch that was tested as batch 559.
More than the usual number of INVALID THETA should be expected, as these tasks are going to get slammed around a bit to see what happens.

Thanks for the heads-up. Looks like these will run longer (if they finish) than the earlier recent 56* batches.

---

More than the usual number of INVALID THETA should be expected, as these tasks are going to get slammed around a bit to see what happens.

On this box under Linux, all three I got failed with sigsegv segmentation error, two had previously failed on other boxes, one with invalid theta the other with a segmentatin fault.

Hi Dave

The part of your post where you mention "invalid theta" and "segmentation fault" close together has triggered a thought:

I wonder if SIGSEGV on Linux is the same as INVALID THETA on Windows?
Which triggered another thought:
Have I ever seen the two mentioned together in the same error listing?
(I don't think that I have.)

When the weekend is over, I'm going to mention this to Oxford.

Hi Les,

possibly but I am sure I have had "invalid theta" on native linux tasks in the past. Not sure about segmentation violation on windows? The tasks were not failing at the same points either, one one my machine ran for longer than the previous one (could be because mine is quite slow) but on another task the windows machine ran for longer and it is quite a lot faster than this box.

However going through my tasks from the other place, invalid theta has only been under wine and sigsegv only on Linux so even if my historical memory is correct, your guess may be right with more recent builds for different platforms.

This failed an Windows with invalid theta and on Linux with segfault:

https://www.cpdn.org/cpdnboinc/workunit.php?wuid=11005566
https://www.cpdn.org/cpdnboinc/workunit.php?wuid=11006391

---

Linux Users Everywhere @ BOINC

Those starting parameter sets must be way out there. Out of 9 batch 564 tasks I have started only 1 has made it as far as 2 hours. If they are all like this it won’t take long to dispose of them, even if they are reissued 3 or 4 times.

The only real problem is this could be hard on Crunchers with low bandwidth caps. They might want to deselect the hadam3ps tasks until they are out of the system.

---

I must be incredibly lucky. I'm running 6, 4 in linux and 2 in Wine/Windows. So far all are progressing along nicely, the Wine/Windows tasks are past 60% and the linux ones are past 20%.

2 on Linux at 18 hours, plus 1 last one just started, 2 on Wine at 24 hours, and 2 on Win 7 at just under 4 hours.

Looks like luck of the drawer.
I think that the way it works, is that the generator creates a task from several lists of values, drops it in the bin, increments one of the lists to get the next set of values, drops that in the bin, etc.
When the required number of tasks has been created, it stops.

So if a computer asks for a number of tasks at once during a "quiet period", it may get all of the tasks with only slightly different values.

I figured that there probably would be stable regions in the data sets that yield viable climates scattered like islands through a vast sea of variables that don’t work together. I guess that I just haven’t downloaded from one of those islands.

---

JUst had two of these as re-treads that have failed with

<stderr_txt>
forrtl: severe (17): syntax error in NAMELIST input, unit 5, file /var/lib/boinc-client/projects/climateprediction.net/hadcm3s_83ys_201412_120_564_011007447/jobs/climate.cpdc, line 396, position 20
Image PC Routine Line Source

after about a few seconds.