-
Notifications
You must be signed in to change notification settings - Fork 0
5 9 2014: Installing CBP Phase 5 Model and HSPF
rburghol edited this page Dec 20, 2021
·
1 revision
Agenda:
- We need to make sure that at least one of us has “sudo” permissions to do this (Denton gave me an email that I think says I have perms, but I have yet to log in and verify).
- Done - logged in and verified
- Insure necessary system software is in place to compile Phase 5.3 model (yum, gnu Fortran g77, Git, csh – sudo access needed to install these)
- Done - appears that Andrew has successfully installed all compiler stuff, including g77
- Decide on locations in system tree for installing the model(s). I use “/opt/model” as the root dir for my models, then store the different versions as “p53” and “p52”, etc. Since we may end up trying to compile the base version and the version that I have modified to run on our machines, there may be multiple directories needed.
- Done - /opt/model/p53
- Decide on the name for the user group that will have access to these modeling folders. Anyone who works on running models, or compiling them for that matter, needs to be part of a group with write perms on the modeling directories. I use “cbpmodel” as the group on the nodes that Denton and I administer.
- Done (as root):
groupadd cbpmodel
- Done (as root):
- Get all of us added to the modeling group. Change the perms for the CBP model code installs so that it is all group writable
- Done (as root):
usermod -aG cbpmodel rob; usermod -aG cbpmodel jcandr1
- Done (as root):
- Configure Git for code management. This will allow us to actually create a working project to save our progress for subsequent installs on CentOS machines. We will need to create a project on git Hub or some other free service, get accounts for us, and then start the process of code management. A little time now will save a lot of hassle later (the CBP team would do well to have this set up if they really wanted to promote wider use of the model).
- Try to compile the code in the first install directory. See lots of errors. Curse a bunch (Bill can show you how), then figure out what we need to change.
- I will scour my install for changes that I have made that helped compilation, but I have not made a formal package, so it will be a process of hunting and pecking.