Opened 5 years ago

Closed 5 years ago

#1674 closed error (invalid)

Shipway microphysics causes a crash on Monsoon Cray

Reported by: philrosenberg Owned by: um_support
Component: UM Model Keywords: CASIM
Cc: Platform: MONSooN
UM Version: 8.5


Running with the CASIM scheme and Shipway microphysics causes a crash on the Monsoon Cray system.

I get an error in my .leave file of

ATP Stack walkback for Rank 911 starting:


ATP Stack walkback for Rank 911 done
Process died with signal 11: 'Segmentation fault'
Forcing core dumps of ranks 911, 0
View application merged backtrace tree with: stat-view
You may need to: module load stat

stat-view seems to indicate that 14 processes segfault at sum_procs.f90:243.

Change History (4)

comment:1 Changed 5 years ago by grenville


I believe you must be one of the first users of CASIM - at this stage I really think your best bet is to contact its owners.

In general, please supply more information with such queries; job id, location of leave file etc.


comment:2 Changed 5 years ago by philrosenberg

Hi Grenville
Yes that is true. There are only a few of us using it. The reason I am submitting tickets is basically only because that’s what the FCM tutorial tells me to do before I create a branch to work on something. I thought that the idea was that the tickets were a means of documenting the branches. However if that isn’t the case I will stop creating tickets and apologies for creating noise - I'm still trying to work out best practice for this, and it did fee a bit odd creating a ticket which gets reported to you for my branches.

comment:3 Changed 5 years ago by ros

Hi Phil,

If you wish to create tickets as a means of documentation for your branches, this needs to be done on the UM Trac ( (likewise on the NEMOCICE Trac for NEMO/CICE branches) and not this Trac which is the UM Helpdesk. It is not compulsory to create tickets when you create a code branch, it is just a facility that is available to you should you wish to use it.


comment:4 Changed 5 years ago by annette

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