Is Rose being remove from JASMIN?

[MariaPVG]

Hi everyone,

Sorry if this is not the place for this question; it might be deeply JASMIN-related, but I haven’t received an answer for this. I ran multiple experiments of a JULES standalone version in JASMIN before August. After that, I had to extend different services on JASMIN and with the Met Office. Now that I have returned to run the models, I have found some issues:

1. When I tried to open the suite “rose edit&“, the is a message saying:
   ”The Rose configuration editor has been removed. The old Rose 2019 GUI remains compatible with Rose 2 configurations.”
   I am not sure what I should use instead.
2. I wanted to run my model, so I ran that from the terminal using “cylc vip“, and the message that pops up is:
   ”WARNING - Backward compatibility mode ON - support for suite.rc files will be removed at 8.7.0
   PluginError: Error in plugin cylc.pre_configure.rose
   ConfigProcessError: env=METO_ILAMB_INPUT_DIR: SCRATCH: unbound variable”
   That happened for every model I tried, so it was not because of a specific model error, but something else.

Do you have any idea/information that might help me?

Best wishes,

Maria Velásquez-García

[dpmatthews]

Rose is still available. However, now that the operating system on the Cylc server has been upgraded, it is longer possible to run Python 2 applications which means that rose edit is not available at the moment - sorry. We hope to have a Python 3 version of rose edit available soon.

@MariaPVG

SCRATCH: unbound variable

This implies that you are referring to an environment variable SCRATCH which is not defined on JASMIN.

[MariaPVG]

Hi David,

Thank you very much for your response. It is good to know that the errors don’t have the same origin and that I might be able to easily solve the “SCRATCH” error. I was advised to add SCRATCH in the rose-suite.conf of my suite, as the output file I am using, so I literally just added
SCRATCH=‘/work/scratch-pw3/eempvg/’ in a new line.

But my code is still failing with the same error. Do you happen to have any advice?.

Best wishes,

Maria Paula

[grenville]

Maria Paula

in /home/users/eempvg/roses/u-ds632/suite.rc, add

SCRATCH = {{SCRATCH}}

in an [environment] section - maybe under [jules_run] (or add one to [root])

Grenville

[MariaPVG]

Hi Grenville,

Thanks for replying. I followed your instructions, copying SCRATCH = {{SCRATCH}} on [environments] in [jules_run] and/or [root]. I tried the three options only in [root], only in [jules_root], and in both, but none of the above worked; I received the same error message.

Best wishes,

Maria Paula

[grenville]

Maria Paula

Which suite are you trying to run - where is the output?

Grenville

[MariaPVG]

Hi Grenville,
I am running the suite u-ds632, which is a copy of u-dl323, with a couple of changes that I have made, some of which aim to get the model running again. Because neither u-dl323 nor any of the experiments over JULES, which were running without issues three months ago in JASMIN, are now functioning.. I am outputting results in /work/scratch-pw3/eempvg/and then copying them to another machine.

Note: the original model is the JULES u-cc669 suite created for the ISIMIP2 project.

Best wishes,

Maria Paula

[grenville]

Maria Paula

I don’t see u-ds632 in your cylc-run directory?

Grenville

[MariaPVG]

Hi Grenville,

It hasn’t had a chance to run. I ran it “cylc vip” and in less than 10 seconds, the error pops up. The same if I try to run u-dl323 or any of the suites you see there (all are related in some instances with the u-cc669).

Maria Paula

[grenville]

Maria Paula

You could add

export SCRATCH=/work/scratch-pw3/eempvg

to your .profile or .bashrc

Grenville

[MariaPVG]

Hi!, yep it works
At least it solves it:

There is a new error, though.

Maria Paula

[MariaPVG]

Hi Grenville,

I just removed the “[0]” in the line with the error, and it seems to be working now. I cannot confirm with 100% certainty because my GUI has not been working for a week now (another issue I am trying to resolve). But the model already created the folder on my cylc-run, which is a good start.

Thanks for your help.

Best wishes,

Maria Paula

[MariaPVG]

Hi!,
I celebrate too quickly, my model is trying to load the module intel/19.0.0 (i.e, module load intel/19.0.0), and it seems that JASMIN doesn’t recognise that anymore. Do you happen to know if that was replaced by something else, perhaps a new version?.

Best wishes,

Maria Paula

[MariaPVG]

Hi!
Some updates:
I found that somebody else had this same error, so I followed the recommendations:

Module errors when running an old JULES suite (u-bq898)

Hi CMS team, I am planning to replicate a JULES simulation from 2022 (u-dq898) (vn5.6). I am new to the JASMIN and cylc user interface. I have made necessary changes to the paths of output files. I have commented a few modules which were throwing errors (e.g. module load intel/19.0.0; module load eb/OpenMPI/intel/3.1.1). Now with these changes I am getting an error as shown in the fig below. [Screenshot 2025-06-17 at 15.31.48] Help me in fixing this issue and simulate the JULES suite u-dq89…

After that, I got this other error:

Porting existing JULES suite to Cylc8/LOTUS2

Hi Dave, Thanks very much for the help. Yes, I was able to run the suite (u-do123) in compatibility mode and I’m almost there, except now I’m getting an error when compiling JULES on cylc2. The error message I get at the fcm_make stage is: [FAIL] mpif90 -obin/jules.exe o/jules.o -L/tmp/YMemrtGpVm -ljules -L/apps/jasmin/supported/libs/netcdf/intel2024.2.0/4.9.2//lib -L/apps/jasmin/supported/libs/netcdf/intel202 4.2.0/fortran/4.6.1/lib -L/group_workspaces/jasmin2/jules/admin/curl/curl-lotus-par…

Then I changed my Jules3_vn7.5/etc/fcm-make/platform/
jasmin-lotus-intel.cfg as recomended; but, I still have the same error.

I would appreciate it if you could provide any further recommendations.

Best wishes,

Maria Paula

[dcase]

Looking at those old tickets should fix compiler issues ( I hope)

The config file should be correct.

The environment and modules can also be taken from rose stem, ie these:

            module load oneapi/compilers/24.2.0
            module load oneapi/mpi/24.2.0
            module load netcdf/intel2024.2.0/4.9.2
            module load netcdf/intel2024.2.0/fortran/4.6.1
            export HDF5_LIBDIR=/apps/jasmin/supported/libs/hdf5/intel2024.2.0/1.14.4-2/lib
            export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HDF5_LIBDIR
            export NETCDF_FORTRAN_ROOT=/apps/jasmin/supported/libs/netcdf/intel2024.2.0/fortran/4.6.1

Let us know if you can’t build with this set up

[MariaPVG]

Hi David,
I did update the information you sent me in the suite. You can find it below:
Changeset 332783 for d/s/6/3/2/trunk/location/JASMIN/suite.rc – roses-u
And I also updated the following file:
/home/users/eempvg/MODELS/Jules3_vn7.5/etc/fcm-make/platform/jasmin-lotus-intel.cfg (perhaps I need to change another file?)

I might be doing something wrong, but I’m not sure where.

Best wishes,

Maria Paula

[dcase]

If you read the error message for the build (the job.err) you see that dependencies for curl are missing.

The trunk points you to a different curl installation, which works on the new JASMIN set up. Look at the config there:

https://code.metoffice.gov.uk/trac/jules/browser/main/trunk/etc/fcm-make/platform/jasmin-lotus-intel.cfg

ie you want this in your library path:

$JASMIN_JULES_BASE_DIR/admin/curl/curl-8.9.1_central/lib/

This one doesn’t have the dependencies which are missing from the new JASMIN. I hope that copying that config file will help you build

[MariaPVG]

Hi David,

I am really sorry, I do understand what you are saying, but I did it. I changed that specific line:
$JULES_NETCDF_LIB_PATH = $NETCDF_ROOT/lib $NETCDF_FORTRAN_ROOT/lib $JASMIN_JULES_BASE_DIR/admin/curl/curl-8.9.1_central/lib/ $HDF5_LIBDIR

But I still got the same error, I am not sure from where it is reading it wrong:

Sorry If I am missing something.

Best wishes,

Maria Paula

[dcase]

You are running a suite which tries to build from source code on the repository. It looks for jules vn7.5 and uses that, so it always uses the config file at vn 7.5

One way around this is to branch the code at vn 7.5, then use the new configuration files in your branch, and tell the suite to use the revision of your new branch.

I think you’d change these lines in your suite to point to the new branch of jules

JASMIN_JULES_FCM=‘fcm:jules.x_tr’
JASMIN_JULES_REVISION=‘vn7.5’

so set them to the branch and revision number once you’ve changed your branch to have the new configuration, then your suite will pick it up hopefully

[MariaPVG]

Hi Dave,

Thanks for your suggestion, I did my best to do what you said, but I am not really skilled in JULES, and not having an interface (i.e., rose edit) is not helping. So, I made the branch and changed the lotus intel:
jasmin-lotus-intel.cfg in main/branches/dev/mariapaulavelasquezgarcia/vn7.5_jules_vn7.5_mpvg/etc/fcm-make/platform – JULES
and the runtime:
(https://code.metoffice.gov.uk/trac/jules/browser/main/branches/dev/mariapaulavelasquezgarcia/vn7.5_jules_vn7.5_mpvg/rose-stem/include/jasmin/runtime.rc

After it, I pointed my suite’s JASMIN_JULES_FCM to my branch. I’m really uncertain that I did it properly, but here it is:
Changeset 333266 for d/s/6/3/2/trunk/rose-suite.conf – roses-u

Then I got the following error, which might indicate I didn’t do it properly:

Note: just to mentioned I also tried just pointing to my model folder and got the same error.

I’m really sorry for my slow advancement, and I really appreciate your support.

Best wishes,

Maria Paula