Custom Query (3332 matches)


Show under each result:

Results (13 - 15 of 3332)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#1007 fixed "Unable to locate a modulefile": MetUM error at vn7.3 ros sosprey


I am running a job at vn7.3 on MONSooN and am geeting the following error:

ModuleCmd_Load.c(200):ERROR:105: Unable to locate a modulefile for 'xlc/v10.1.0.0'

I have been told that I may need to get explicit access to the NEMO/CICE repository for the job I am running. Is the error consistent with this?

ciao, Scott.

#1777 worksforme "rosie go" crashes on search annette swr05npk

I suspect this is really a Met Office issue, but I don't know where to file a bug report for Rose.

You can crash "rosie go" on puma very easily, using the following steps:

  1. Load the GUI
  2. Highlight a job
  3. Enter a search string that returns no results (e.g., "gargle bargle fargle").

"rosie go" will crash with a stack trace:

Traceback (most recent call last):
  File "/home/fcm/rose-2015.06.0/lib/python/rosie/browser/", line 602, in handle_activation
  File "/home/fcm/rose-2015.06.0/lib/python/rosie/browser/", line 1373, in update_toolbar_sensitivity
    has_output = self.handle_view_output(test=True)
  File "/home/fcm/rose-2015.06.0/lib/python/rosie/browser/", line 1017, in handle_view_output
    id_ = SuiteId(id_text=self.get_selected_suite_id(path))
  File "/home/fcm/rose-2015.06.0/lib/python/rosie/", line 330, in __init__
    raise SuiteIdTextError(None)
rosie.suite_id.SuiteIdTextError: None: invalid suite ID

I suspect that this is because the application expects to have a job highlighted in the viewer window, but there is no job to highlight because the search returns no results. There appears to be no trap for this condition, so the application just crashes.

I am filing this here, because I managed to crash the application ~5 times in the first hour I was using it before I realised what was happening. I am sure that others will do the same and wonder why.

I am happy to report this to the Met Office if you tell me where their Rose bug tracker lives.

#3002 fixed 'Convergence failure in BiCGstab, omg is NaN' error - again, but not in usual place um_support charlie


Sorry to bother you once again, but my current suite (u-bk944) has again failed, giving me the error below:

???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
?  Error code: 1
?  Error from routine: EG_BICGSTAB
?  Error message: Convergence failure in BiCGstab, omg is NaN
?        This is a common point for the model to fail if it
?        has ingested or developed NaNs or infinities
?        elsewhere in the code.
?        See the following URL for more information:
?  Error from processor: 144
?  Error number: 12

I have seen this error many times before, but only usually at the very beginning of the simulation i.e. at the very first timestep. It is usually a catch-all error for missing data that where the model expects actual data, or vice versa - and usually results from an error in one of my ancillary files.

However, on this occasion, the error has occurred ~32 years into the simulation. So it can't be anything to do with my ancillary files, or any change that I have made. It has just occurred within the simulation itself. Please would you be able to advise on what I need to track this error down?

Many thanks,


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.