I ran into the following problem:

350w_100167956 - PH 1 TS 259247 - 01/12/1825 23:30 - H:M:S=0316:51:47 AVG= 4.40 DLT= 2.59
350w_100167956 - PH 1 TS 259248 - 02/12/1825 00:00 - H:M:S=0316:51:48 AVG= 4.40 DLT= 1.79
Phase over, going into post_processing()
In pre_initialise_phase (part 1 of 3)
In initialise_phase (part 2 of 3)
Calculating global means for files .pa|.x1|.nc
Calculating regional means for .pa|.x1|.nc
Calculating global means for files .pc|.x1|.nc
Calculating regional means for .pc|.x1|.nc
Calculating global means for files .pd|.x1|.nc
Calculating regional means for .pd|.x1|.nc
Calculating global means for files .pe|.x1|.nc
GMTS: Error: Time variable found, but values not found (tdimlen was 0)
2004-11-25 02:52:32 [climateprediction.net] Unrecoverable error for result 350w_100167956_0 (process got signal 11)
2004-11-25 02:52:32 [climateprediction.net] Unrecoverable error for result 350w_100167956_0 (process got signal 11)
2004-11-25 02:52:32 [climateprediction.net] Computation for result 350w_100167956 finished

What can cause such a segmentation fault?

Tilman

hmm, how is your disk space?

10GB of free space should be enough, shouldn't it :-)

> 10GB of free space should be enough, shouldn't it :-)

yeah, I just noticed this msg:

GMTS: Error: Time variable found, but values not found (tdimlen was 0)

Sounds like a disk error in the middle of the post-phase processing, so it explains the crash, although it is annoying that it happened. This code has been pretty reliable so I imagine it "burped" on a disk write.

It just happened again, same computer, same error message, but different work unit. And there is enough disk space available.

I have another computer running CPDN, who will finish phase 1 in a few weeks, so we will see whether the problem is computer related.