Opened 4 years ago
Closed 4 years ago
#1979 closed help (answered)
Suite error
Reported by: | amenon | Owned by: | um_support |
---|---|---|---|
Component: | UM Model | Keywords: | Nesting suite |
Cc: | Platform: | ARCHER | |
UM Version: | 10.4 |
Description
Hi Ros,
The suite is progressing now. We have split the jobs and assigned them all to the short queue (Especially after realising that Archer gives more priority to short jobs) . But the global forecast model failed at a point and the error is unclear. Could you please help me to sort out this error. Here are the links
and
Cheers,
Arathy
Change History (7)
comment:1 Changed 4 years ago by grenville
comment:2 Changed 4 years ago by amenon
Thanks Grenville. It succeeded now. I changed PRINT_STATUS from normal to PRINT_STATUS=PrStatus_Diag
comment:3 Changed 4 years ago by grenville
Arathy
How do you mean - changing the print status shouldn't fix a problem, merely supply more clues as to why it failed?
Grenville
comment:4 Changed 4 years ago by amenon
Yes it could be an odd coincidence?! I am not sure why it has ran this time, but Stu suggested reverting the print status to what it was earlier might have helped.
comment:5 Changed 4 years ago by ros
Hi Arathy,
I looked at what my copy of your suite had done and it has successfully managed to run all the glm_um_fcst tasks so maybe just a glitch with ARCHER? Doesn't look like you have changed anything major since I took a copy.
Regards,
Ros.
comment:6 Changed 4 years ago by amenon
Hi Ros,
Yes, it could be. I must have tried triggering the task without making any changes too, then we might have got a better idea. I didn't do it as I ended up doing a suicidal trigger last week.
Regards,
Arathy
comment:7 Changed 4 years ago by ros
- Resolution set to answered
- Status changed from new to closed
Arathy
Please switch on Extra diagnostic messages
gl_um→ run time controls → PRINT_STATUS
then rose suite-run —restart
Grenville