Opened 10 years ago

Closed 9 years ago

#541 closed help (fixed)

HadCM3 job that ran ok on Phase2A blows up on Phase2B

Reported by: jcrook Owned by: lois
Component: UM Model Keywords:
Cc: Platform:
UM Version: 4.5


I had a job xesac which I ran successfully on Phase2A earlier in the year. I have now taken a copy of this job (xesah) and changed the target machine and number of processors N/S and E/W to 4 and 6 respectively. I also changed the compile options to compile and run for 2 months. The first month produces output which has Nan for the surface temperature. Looking at the xesah000.xesah.d10320.t121455.leave file it looks like something goes wrong around timestep 1100. The job is starting from the same start dump as xesac.

Change History (2)

comment:1 Changed 10 years ago by lois

  • Owner changed from um_support to lois
  • Status changed from new to accepted

Hello Julia,

we have not done much testing on phase 2b as it is going to be upgraded in December, so we will take not of this problem and put it on the list of things to be investigated after the final phase of the upgrade. In the mean time I hope that all is working on the XT4 (phase 2a).


comment:2 Changed 9 years ago by ros

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