Difference between revisions of "WRF porting to NCI machine"
m (Protected "WRF porting to NCI machine" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
|
(No difference)
|
Revision as of 01:43, 9 April 2019
These are the steps to follow to install new WRF versions on NCI machine. Only for admins within the wrf group at NCI. If starting from scratch:
- Update the Github fork of NCAR Github in coecms/WRFV3
- Under your own project, clone the WRF github repo: https://github.com/coecms/WRF and create a new branch for the new version (named Vx.x.x)
- Add https://github.com/coecms/WRFV3.git as a remote (named NCAR if you want to copy-paste the commands) and fetch
- In the new branch, run the command:
>
git merge -s recursive -Xsubtree=WRFV3 -Xtheirs --allow-unrelated-histories NCAR_WRF/master
> You may need another branch than master to pick up a specific release.
- Clone into /projects/WRF with wrf group ownership. Make sure the master branch there points to the new version branch.
If you already have a clone of the coecms/WRF repo:
- Update the Github fork of NCAR Github in coecms/WRFV3
- In your local clone, fetch the NCAR remote
- Create a new branch for the new version (named Vx.x.x)
- In the new branch, run the command:
>
git merge -s recursive -Xsubtree=WRFV3 --allow-unrelated-histories NCAR_WRF/master
> You may need another branch than master to pick up a specific release.
- Clone into /projects/WRF with wrf group ownership. Make sure the master branch there points to the new version branch.
Follow same steps for WPS, but remote is called NCAR_WPS and -Xsubtree=WPS
Jenkins setup
- Add a new parameter for the version. Just the numbers, no "V".
- Create a branch for that version in wrf-testing repo. Exact same name as the previous step parameter.