Opened 7 years ago

Closed 7 years ago

#1163 closed help (completed)

Identical jobs giving different results

Reported by: laurahb Owned by: ros
Component: UM Model Keywords:
Cc: Platform: MONSooN
UM Version: 7.3


I have two jobs that are identical but are giving different results.
The first is xiyum, which set going last week. The second is xiyuq, which is a copy of xiyum, which I ran today. After one month of the simulation the meteorology is evolving differently.
The working copy I used to build from in each case is in my own directory and I know that this has not changed since 3 weeks ago.
Do you know of anything to do with Monsoon that might have changed to cause this?

Change History (3)

comment:1 Changed 7 years ago by ros

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

Hi Laura,

Must admit I'm currently confused by this. I wondered if FCM had at some point got itself confused and you'd got an incorrect extract, but the contents of both /ppsrc directories are the same.

I've just tried copying your jobs and running them, but they both fall over with a namelist read error in NLCFILES and I can't currently see why. Have you seen this before?


comment:2 Changed 7 years ago by ros

Hi Laura,

I see from the query you have raised with the Met Office, that you have tried taking a copy of xiyum and rerunning it using the executable from xiyum and that this gave different results but the same as xiyuq. Could you please try taking another copy of xiyum and recompiling and rerunning and see what happens?

At the moment the only thing I can think of is that either an input file has changed or some library on MONSooN has changed…..


comment:3 Changed 7 years ago by ros

  • Resolution set to completed
  • Status changed from accepted to closed

Ticket closed.

Note: Laura solved her own problem. The problem was actually that something strange happened at the beginning of the xiyum run. So that was the one that was wrong, and the other copies made since were actually correct.

Note: See TracTickets for help on using tickets.