Opened 5 years ago

Closed 5 years ago

#1939 closed help (answered)

Probel with new JULES routine (no rule to make target)

Reported by: s.mangeon Owned by: um_support
Component: UM Model Keywords: jules, new routines
Cc: Platform: PUMA
UM Version: 8.4


Good afternoon,

The name of the job I use is xmegi. The local branches on PUMA I compile are:
(JULES) /home/s.mangeon/JULES/development_codes/um8.4_inferno1.0
(UM) /home/s.mangeon/um/vn8.4_UKCA-INFERNO

I am trying to introduce new science transferring from JULES into the UM. I do this by creating two new modules, inferno_io.F90 and inferno.F90 (and another fire_vars.F90 in control which contains variables to pass onto the um atmospheric side). These sit within a local modified version of jules@um8.4. I have enabled a local copy in FCM configuration for JULES. I then call upon the inferno_io module within atmos_physics2, but this seems to create an issue at the build stage:

make: * No rule to make target inferno_io.done', needed by atmos_physics2.done'. Stop.

I've committed these changes in the latest JULES, but I imagine the older version @um8.4 has a different way of assessing what needs to be compiled.

Would you know in which files I should add links to these new routines in order for them to be included in the build?

Thanks a lot,

Change History (6)

comment:1 Changed 5 years ago by simon

Do you have a runid for your build job?


comment:2 Changed 5 years ago by s.mangeon

The latest run's leave in ~/output is named as such:

So I guess the run id is 142743?

the jobID is xmegi though

comment:3 Changed 5 years ago by simon


Sorry, missed the runid (=jobid) in the first sentence. Which machine are you compiling on, and what's your username on it?

comment:4 Changed 5 years ago by s.mangeon


I am running on Monsoon from puma, and my usernames are smange and s.mangeon respectively.


comment:5 Changed 5 years ago by simon


It's possible that your JULES changes aren't being picked up as they are in a new directory. You could either place them into an existing directory or create a JULES branch with your changes and see if the build system automatically picks them up. Unfortunately I don't have access to the JULES repository, but there may be docs available inside which explains how to set up new directories correctly.

comment:6 Changed 5 years ago by ros

  • Resolution set to answered
  • Status changed from new to closed
  • UM Version changed from <select version> to 8.4

Ticket closed due to inactivity.

Note: See TracTickets for help on using tickets.