Opened 14 months ago
Closed 13 months ago
#3136 closed help (fixed)
negative mass in set_thermodynamic
Reported by: | amenon | Owned by: | um_support |
---|---|---|---|
Component: | UM Model | Keywords: | set_thermodynamic |
Cc: | Platform: | ARCHER | |
UM Version: | 10.9 |
Description
Dear CMS,
I am getting the following error in one of my simulations:
???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!! ? Error code: 100 ? Error from routine: set_thermodynamic ? Error message: A total of 4 points had negative mass in set_thermodynamic. This indicates the pressure fields are inconsistent between different levels and the model is about to fail. ? Error from processor: 3615 ? Error number: 24 ????????????????????????????????????????????????????????????????????????????????
I recognize that this is a known UM failure point as shown in https://code.metoffice.gov.uk/trac/um/wiki/KnownUMFailurePoints
I re-ran the LAM forecast a few times and they are persistently failing with this error. I also copied this suite fresh and tried to run it. But I am still getting this error. Could you please advice how to proceed with this now?
The suite id is u-bq536 in Archer.
Thanks,
Arathy
Change History (7)
comment:1 Changed 14 months ago by dcase
comment:2 Changed 14 months ago by amenon
Thanks for looking into this, Dave. Here is the path:
/home/amenon/cylc-run/u-bq536/log/job/20180812T0000Z/INCOMPASS_km1p5_RA1T_qcons_um_fcst_000/05/job.err
comment:3 Changed 14 months ago by dcase
Have you managed to run this with a shorter timestep? I can't see one which isn't 75s
comment:4 Changed 13 months ago by amenon
Hi Dave,
As you suggested offline, I ran this simulation by reducing the time step to 25s and it succeeded one cycle without generating the above error. Now I have changed it back to 75s. I will let you know if the same error appears again.
Thanks,
Arathy
comment:5 Changed 13 months ago by dcase
That's a nice result (I was hopeful rather than confident of that working).
If you are happy, then can we close the ticket? You can always re-open it if the error reappears and can't be solved like this.
comment:6 Changed 13 months ago by amenon
Sure, we can close the ticket now. Thanks Dave.
comment:7 Changed 13 months ago by dcase
- Resolution set to fixed
- Status changed from new to closed
Would you mind giving me a path to the log file with the error? Wherever I look I see jobs succeeding.. Thanks