Custom Query (3327 matches)


Show under each result:

Results (61 - 63 of 3327)

Ticket Resolution Summary Owner Reporter
#1776 answered Job stops midway through the run and does not archive properly annette dilshadshawki

Hi Helpdesk,

I am running a job, xlzch, I was able to run it successfully for 10 years. However since then I have run it again, only making changes to an emissions ancillary file, now it only runs up to 6 years. I thought this was strange but then I just ran it again from the start in case this was just a random glitch, but the same thing is happening.

Here is the latest .leave file but it contains virtualy no information regarding why the simulation stopped after 6 years:


There is another thing that I noticed, which I also noticed with another job that also failed to run after 30ish years, xlzci (a copy of xlzch with some changes to the emissions), which is that there seems to be a problem with the archiving of ocean dump files, as well as other ocean and sea ice files. I'm not sure if the scripts that I am using are working properly.

The scripts can be found here:


Also, it should be automatically archiving to MASS via MOOSE, but it only seems to save the atmos files and not the ocean and sea ice files.

moo ls moose:/crum/xlzch
moo ls moose:/crum/xlzci

Finally, xlzci also failed and only seems to have exceeded the time limit:


Please accept my apologies as this ticket has many questions but they all seem to be linked.

Please could you provide some assistance on this issue?

Many thanks,

Best, Dill

#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.

#1778 answered FCM on archer does not recognise keywords annette swr05npk

I am trying to run the standard GA6.0 N96 AMIP simulation at UM 10.3 on ARCHER. I copied suite u-aa894 into my suite u-ab340 and adapted it (with some difficulty) to submit to ARCHER. The difficulty arose because there were only two choices for HPC system in the Met Office job: Met Office and NCI (Australia).

Anyway, the suite fell over when it tried to run the INSTALL_ANCIL_RESOURCE task on ARCHER. It crashed with the following error:

[FAIL] file:/work/n02/n02/pappas/cylc-run/u-ab304/share/data/etc/um_ancils_gl=source=fcm:ancil_data.xm_tr/ancil_versions/n96e_orca025/GA6.0_AMIP/v5/ancils: bad or missing value

From puma, I can see that this file exists, because

fcm extract fcm:ancil_data.xm_tr/ancil_versions/n96e_orca025/GA6.0_AMIP/v5/ancils

succeeds. However, on ARCHER:

fcm extract fcm:ancil_data.xm_tr/ancil_versions/n96e_orca025/GA6.0_AMIP/v5/ancils

Extract command started on Fri Dec 18 16:42:31 2015.
->Parse configuration: start
[FAIL] fcm:ancil_data.xm_tr/ancil_versions/n96e_orca025/GA6.0_AMIP/v5/ancils: location keyword not defined

So I suspect my suite failed because FCM on ARCHER cannot resolve the ancil_data.xm_tr keyword. Indeed, issuing

fcm keyword-print

on ARCHER yields no output, while on puma the same command prints loads of keywords and their respective paths.

I managed to get around this issue by installing the ancils file in my /work directory, then pointing the Rose suite to that file, but it seems to me that FCM on ARCHER should be able to resolve keywords if these suites to work "out of the box".

Note: See TracQuery for help on using queries.