Difference between revisions of "UKCA Chemistry and Aerosol vn10.9 Tutorial 11"

From UKCA
Line 15: Line 15:
 
rose stem --group=vm_n48_ukca_eg_noomp -S GENERATE_KGO=true
 
rose stem --group=vm_n48_ukca_eg_noomp -S GENERATE_KGO=true
   
  +
within a vanilla copy of the vn10.9 trunk. When this runs for the first time the two KGO tasks will fail, but when this happens the KGO is installed. You just need to re-trigger these two tasks to run again, and they will succeed and the suite will stop.
within a vanilla copy of the vn10.9 trunk.
 
   
 
For more information on the VM you should read-through [https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_X10.pdf umdp_X10].
 
For more information on the VM you should read-through [https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_X10.pdf umdp_X10].

Revision as of 15:10, 13 December 2017

UKCA Chemistry and Aerosol Tutorials at vn10.9

What you will learn in this Tutorial

In this tutorial you will go through a worked example showing you how to commit code to the UM trunk.

You should also open the working practices for the UM page on MOSRS and read through that as well.

This can only be completed on the Virtual Machine, as rose-stem does not currently work on ARCHER.

Before you start this Tutorial

Before you start this tutorial you will need to have a working Virtual Machine where known good output (or KGO) has been installed for the vm_n48_ukca_eg_noomp. You can do this by running the command

rose stem --group=vm_n48_ukca_eg_noomp -S GENERATE_KGO=true

within a vanilla copy of the vn10.9 trunk. When this runs for the first time the two KGO tasks will fail, but when this happens the KGO is installed. You just need to re-trigger these two tasks to run again, and they will succeed and the suite will stop.

For more information on the VM you should read-through umdp_X10.

Create a ticket

You will need to fill-in several headings. These can all be changed later if needed.

  • Summary: Give a short description of what the change is for.
  • Description: Give a longer and more detailed description.
  • Type: Putting enhancement is usually fine here.
  • Milestone: This should be the UM (or Mule) version that you are targeting. If you don't know a particular version leave this as Hopefully, and if you aren't targeting a version then you can put this as Not for Builds. In this example please use Not for Builds.
  • Severity: Usually changes will be minor or significant, depending on if results are changed. Usually wholesale and trivial aren't used very often. This doesn't matter too much, as the Code Reviewer will often change this during their review.
  • Keywords: When working on UKCA, please include UKCA and SC0138 (this is to make it easy to search for UKCA tickets)

Once you have created it, you should Modify it and start work and then click submit. This will change the ownership to you and change the ticket statue to in_progress. You will now be able to find your ticket on your view tickets page.

You can find an example of this here: um:#3639.

Make a branch

Please make a branch as covered in Tutorial 4, e.g.

fcm branch-create --type dev -k ticket_number your_branch_name fcm:um.x_tr@vn10.9

and then check-out your branch by

fcm checkout fcm:um.x_br/dev/userid/vn10.9_your_branch_name


UKCA Chemistry and Aerosol Tutorials at vn10.9


Written by Luke Abraham 2017