Opened 3 months ago

Closed 3 months ago

#2728 closed help (fixed)

Postprocessing to Jasmin

Reported by: charlie Owned by: ros
Component: UM Model Keywords:
Cc: Platform: NEXCS
UM Version: 10.7

Description

Hi,

Whilst I am in the process of getting my suite to work (see ticket #2703), another job I need to do is to change the archiving/postprocessing so that it goes to /nexcs instead of where it's currently going, Monsoon. I need to do this for 2 of my suites: u-bc205 and u-be195.

I am following your instructions at http://cms.ncas.ac.uk/wiki/Docs/PostProcessingApp, but in my suite u-bc205 there is no option to change the archive_command (there is a radio button next to Moose, then another radio button, but nothing else.

Please can you help?

Charlie

Change History (10)

comment:1 Changed 3 months ago by ros

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

Hi Charlie,

Suite u-bc205 is using an old version of postproc which doesn't have the ARCHER/JASMIN settings in it. You will need to upgrade post-processing first as described in the "Upgrading post-processing app" at the top of the page you link to above. This will take you to a page on the MOSRS. Then follow the instructions for "upgrading to a new release version" specifically "The procedure for updating the postproc app version from the MOCI repository, and using the central meta-data". Upgrade to version postproc_2.2

Once you've done that let me know.

Regards,
Ros.

comment:2 Changed 3 months ago by charlie

Okay, first problem: when I get to step 6 of the instructions, I get the following error:

bc205/app/fcm_make_pp> rose app-upgrade postproc_2.2
Traceback (most recent call last):
  File "/opt/python/gnu/2.7.9/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/opt/python/gnu/2.7.9/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/common/fcm/rose-2018.06.0/lib/python/rose/upgrade.py", line 814, in <module>
    main()
  File "/common/fcm/rose-2018.06.0/lib/python/rose/upgrade.py", line 722, in main
    return_objects = parse_upgrade_args()
  File "/common/fcm/rose-2018.06.0/lib/python/rose/upgrade.py", line 715, in parse_upgrade_args
    opts.conf_dir, config_file_path, mode="upgrade") +
  File "/common/fcm/rose-2018.06.0/lib/python/rose/macro.py", line 1472, in load_conf_from_file
    return_config_map=True)
  File "/common/fcm/rose-2018.06.0/lib/python/rose/config.py", line 1264, in load_with_opts
    node = self.load(source, node)
  File "/common/fcm/rose-2018.06.0/lib/python/rose/config.py", line 1405, in load
    ConfigSyntaxError.BAD_SYNTAX, file_name, line_num, 0, line)
rose.config.ConfigSyntaxError: /home/d05/cwilliams/roses/u-bc205/app/fcm_make_pp/rose-app.conf(12): expecting "[SECTION]" or "KEY=VALUE"
branches/dev/pierremathiot/postproc_2.0_dev_icb_trajectory_date_tag_output_name@1657

comment:3 Changed 3 months ago by charlie

And I can't do it within the GUI either, again following the instructions, because whenever I open up fcm_make_pp (which is necessary in order for it to appear in the upgrade window), the entire thing crashes.

comment:4 Changed 3 months ago by ros

Hi Charlie,

When you removed the branches from pp_sources you've not removed them all leaving a trailing branch at the end of app/fcm_make_pp/rose-app.conf

Remove that branch and the upgrade of fcm_make_pp will work ok.

Cheers,
Ros.

comment:5 Changed 3 months ago by charlie

Sorry, I thought that was a different line. Now removed, and it's now worked.

comment:6 Changed 3 months ago by ros

Great. Now you can proceed through the configuration and NEXCS setup instructions here: http://cms.ncas.ac.uk/wiki/Docs/PostProcessingApp

I would fcm commit your suite to save the upgrade changes before you start these.

Cheers,
Ros.

comment:7 Changed 3 months ago by charlie

Okay, committed and about to follow instructions. Do you think it is wise to do both steps i.e. "Configuring postprocessing" and "Configuring transfer application"? Presumably if I only did the first step, data would stay in /projects on NEXCS and I would have to transfer it to group workspace manually?

Also, will I have to go through the upgrade process for my other suite, u-be195?

Charlie

comment:8 Changed 3 months ago by ros

Hi Charlie,

If you want your data on JASMIN I would use the transfer app to do it automatically; that's what it was written for. If you don't configure the transfer app then yes you will have to transfer all the data across manually.

You only need to upgrade post processing if ARCHER/NEXCS post processing settings aren't already in the suite.

Regards,
Ros.

comment:9 Changed 3 months ago by charlie

Very many thanks Ros, all done. At least something was relatively easy!

comment:10 Changed 3 months ago by charlie

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.