Opened 3 years ago

Closed 3 years ago

#2234 closed help (answered)

60km run job xnndf

Reported by: sam89 Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: Monsoon2
UM Version: 8.2



I am trying to run a job at 60km resolution.

I am getting a segmentation fault right at the start of the run, what could be causing this? I cannot work it out from the .leave file.



Change History (5)

comment:1 Changed 3 years ago by sam89

I understand segmentation faults usually are caused by something not being set up properly. Maybe something not pointing to the correct place since I copied a Global job which was running fine and edited it to run as a 60km job pointing to different ancillaries.

It does say in the .leave file about sw and lw data not being found but I'm not sure if this is what caused the segmentation error or it is an additional problem with the run.

I think previously if I've had segmentation faults I've needed to add a FCM branch or that something is pointing to the wrong place.



comment:2 Changed 3 years ago by sam89


I switched some ancillaries off and it seems to get further but now it appears to be failing in qsatmos and I looked at the .pe107 file and it appears this is the error

???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: glue_conv
? Error Code: 2
? Error Message: Deep conv went to model top at point 27 in seg 2 on

call 1

? Error generated from processor: 87
? This run generated 2 warnings

I have no idea how to fix this though.



comment:3 Changed 3 years ago by sam89


I just ran the job without the IAU file added and it appears to work fine xnndf000.xnndf.d17212.t131841.leave

The IAU file is making the job unstable for some reason. I have tried adding the perturbations all in one go at the beginning and over a 3 hour period but both of these fail the same way as the original one that is added over a 60minute period.


comment:4 Changed 3 years ago by sam89

I gave up on this run as it seems too unstable so this ticket can be closed. I eventually got the N216 output working though by starting from scratch. I am now having issues with re configuring to Global resolution so I have raised a new ticket for that job.

comment:5 Changed 3 years ago by willie

  • Resolution set to answered
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.