Re: [Npsource-cbpmodel] github + AWS image + p6 changes to hspf
Status: Beta
Brought to you by:
robertwb
|
From: Burgholzer, R. (DEQ) <Rob...@de...> - 2017-03-23 19:57:17
|
Thanks a bunch Gary! I will refrain from bothering Gopal (directly) until after June, but I will keep posting on this list as we progress in case anyone else finds it useful or in case anyone will benefit. We at DEQ don't have access to AWS systems, so we need to try to make this work with Ubuntu for now, but our colleagues at VT may be putting up an AWS image at some time in the future. A couple of thoughts: * It would be super cool if you all could create a public image on AWS of your running installs (once the dust settles of course) - then folks could just spin up a copy at their leisure -- provided they had AWS accounts of course :). * Just FYI I set up a github account for p532c here: https://github.com/rburghol/cbp_wsm o The master branch is the most recent p532c from your ftp site, and I created a branch called "p532c-ubuntu" to reflect the changes that we need to make in order to compile successfully (thus far very minor stuff, such as adding decimal points to function calls that are defined as needed float instead of int). * I will plan on setting up and maintaining a github of the Phase 6 when you guys release it unless someone in your shop were willing to do so (your variant on HSPF has such powerful calibration utils, and such great multi-processor scalability that it really is a major contribution to the HSPF ecosystem IMO). * The bundled Hspf 11.1 (including the _g variant!) compiles just fine with f77 on Ubuntu running from CBPs compile_all.csh script. * Some of the other stuff (like etm) is where we start to run into errors, but as noted, we are making our way through them and I will send updates here. /r/b From: Gary Shenk [mailto:GS...@ch...] Sent: Thursday, March 23, 2017 11:43 AM To: nps...@li... Subject: Re: [Npsource-cbpmodel] github + AWS image + p6 changes to hspf Hey Rob, I am completely out of the nuts and bolts game at this point, but I do know the following: * Should we anticipate any change in the hspf (hspf_g, etc.) executable? 1. We've made no change in the HSPF code for P5.3.2 or p6 * It still compile nicely with f77? 1. It compiles on our local machine. * Has anyone already set up a github (or other repo) for hspf11? 1. dunno * Has anyone set up a git repo for the Phase 5 (or 6) code? 1. no * Anyone already done the above and made a public image available on AWS? 1. We've moved p5.3.2 to AWS and it works 2. We're pretty much moved to AWS with P6 and it mostly works 3. There were some issues moving to AWS, mostly with SLURM, but they have been solved. 4. Gopal knows quite a bit, but he is busy until June 1 5. John Massey (jm...@ch...<mailto:jm...@ch...>) is the AWS expert and he would probably love to talk to you about it. Gary Shenk USGS Chesapeake Bay Program Office 410 Severn Ave, Suite 112 Annapolis MD 21403 410 267 5745 410 507 2681 (c) From: Burgholzer, Robert (DEQ) [mailto:Rob...@de...] Sent: Wednesday, March 22, 2017 1:32 PM To: nps...@li...<mailto:nps...@li...> Subject: Re: [Npsource-cbpmodel] github + AWS image + p6 changes to hspf Sorry I hit send before I finished my questions: So, first I thought we'd ask: * Should we anticipate any change in the hspf (hspf_g, etc.) executable? * It still compile nicely with f77? * Has anyone already set up a github (or other repo) for hspf11? * Has anyone set up a git repo for the Phase 5 (or 6) code? * Anyone already done the above and made a public image available on AWS? Thanks! Rob From: Burgholzer, Robert (DEQ) [mailto:Rob...@de...] Sent: Wednesday, March 22, 2017 12:47 PM To: nps...@li...<mailto:nps...@li...> Subject: [Npsource-cbpmodel] github + AWS image + p6 changes to hspf Gary/others, We are into another cycle of deploying the watershed model and wanted to make sure that our efforts were efficient, and that we could share our experiences and leverage the experience of others. Thus, we have a few goals: 1. Compile and run hspf + p5.3 on an Ubuntu machine that we use 2. Populate a github repo with this code (we started this 3 years ago last time we compiled successfully but added ZERO code - what a bunch of slackers!) 3. Take the lessons learned from #1 and do the same on an AWS instance running Ubuntu 4. Create an AWS image from #2 for others to use (and for future use by the folks at VT that I am collaborating with). 5. Get our minds in order for doing this whole thing over again when Phase 6 is released. So, first I thought we'd ask: * Should we anticipate any change in the hspf (hspf_g, etc.) executable? * It still compile nicely with f77? * |