# Creating NEMO\_4.0.4\_GO8 branch on Monsoon2

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/creating-nemo-4-0-4-go8-branch-on-monsoon2/988>\
**Category:** Rose/Cylc and FCM\
**Tags:** Monsoon2\
**Created:** [4 May 2023 12:43 UTC](https://cms-helpdesk.ncas.ac.uk/t/creating-nemo-4-0-4-go8-branch-on-monsoon2/988 "2023-05-04T12:43:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![twilder](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/twilder/32/257_2.png) [@twilder](https://cms-helpdesk.ncas.ac.uk/u/twilder)\
**Post date:** [4 May 2023 12:43 UTC](https://cms-helpdesk.ncas.ac.uk/t/creating-nemo-4-0-4-go8-branch-on-monsoon2/988/1 "2023-05-04T12:43:43Z")

</div>

I am working with the GOSI9p8.0 ORCA025 rose suite u-cn052(M), which uses the nemo source code ‘branches/UKMO/NEMO\_4.0.4\_GO8\_package@15748’ located [here](https://code.metoffice.gov.uk/svn/nemo/NEMO/branches/UKMO/NEMO_4.0.4_GO8_package/). I would like to take this branch and modify the source code. However, when I go to create that branch on Monsoon, the result is always a branch from the main nemo trunk, regardless of the options chosen e.g. with --bob (branch of branch) and/or specifying @revision\_number. See a snippet from the command line below:

```auto
twilder@xcslc0:~/NEMO/branches> fcm bc -k 652 --bob NEMO_4.0.4_GO8_package_qgleith https://code.metoffice.gov.uk/svn/nemo/NEMO/branches/UKMO/NEMO_4.0.4_GO8_package@15748

[info] Source: https://code.metoffice.gov.uk/svn/nemo/NEMO/trunk@15557 (15748)

[info] /usr/bin/vim: starting commit message editor...

Change summary:

--------------------------------------------------------------------------------

A https://code.metoffice.gov.uk/svn/nemo/NEMO/branches/dev/thomaswilder/r15557_NEMO_4.0.4_GO8_package_qgleith

--------------------------------------------------------------------------------

Commit message is as follows:

--------------------------------------------------------------------------------

NEMO branch of GO8 to test QG Leith implementation in a copy of rose suite u-cn052.

#652: Created /NEMO/branches/dev/thomaswilder/r15557_NEMO_4.0.4_GO8_package_qgleith from /NEMO/trunk@15557.

--------------------------------------------------------------------------------

Create the branch?

Enter "y" or "n" (or just press <return> for "n")

```

Could anyone advise on this?

---

<div class="post-metadata">

**Author:** ![twilder](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/twilder/32/257_2.png) [@twilder](https://cms-helpdesk.ncas.ac.uk/u/twilder)\
**Post date:** [18 May 2023 15:02 UTC](https://cms-helpdesk.ncas.ac.uk/t/creating-nemo-4-0-4-go8-branch-on-monsoon2/988/2 "2023-05-18T15:02:13Z")

</div>

Thought I’d update this post with a solution.

For some reason, `fcm bc ...` just would not work. I came across [this](https://code.metoffice.gov.uk/trac/GO/wiki/GODocumentation/GO8.0/NemoUpgradeInstructions#no1) on the code.metoffice site. Essentially, I copied the branch i needed and placed it in a dev branch

```auto
svn copy https://code.metoffice.gov.uk/svn/nemo/NEMO/branches/UKMO/NEMO_4.0.4_GO8_package@15748 https://code.metoffice.gov.uk/svn/nemo/NEMO/branches/dev/thomaswilder/NEMO_4.0.4_GO8_package_QGLeith

```

I then checked out the new branch into my local Monsoon directory,

```auto
svn co https://code.metoffice.gov.uk/svn/nemo/NEMO/branches/dev/thomaswilder/NEMO_4.0.4_GO8_package_QGLeith .

```

I can now make changes and commit these to a branch.