Re: [Npsource-cbpmodel] github Phase 5.3 WSM

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

And... as a follow up - I think that the software is assuming that the file "getatdep.a" is already precompiled and ready, but that causes an error on Ubuntu - presumably because the copy of "getatdep.a" is compiled for RH.  ASo, when I delete the "getatdep.a" to eliminate a linker error (not a Lewis Linker error mind you), I get a "not found".

So, I think I need to find whatever source code generates getatdep.a - anyone got any leads?

Thanks!
/r/b

From: Burgholzer, Robert (DEQ) [mailto:Rob...@de...]
Sent: Monday, April 10, 2017 4:22 PM
To: nps...@li...
Cc: Paul Duda
Subject: [Npsource-cbpmodel] github Phase 5.3 WSM

Wanted to post an update to the watershed model compilation on Ubuntu, and to ask a question about "make clean" support.  The project is now on github as cbp_wsm (the whole shootin match is there since it is so much more than just HSPF). https://github.com/rburghol/cbp_wsm/

Status: We have cleared up many of the errors - hspf 12.1 (and it's variants) compiles without any trouble.  Most of the errors were just a case of the f77 compiler on Ubuntu being somewhat pickier with variable syntax choices.  Gotten to where now the only errors are fortran linking errors, indicative of a binary file sneaking it's way into the source tree from another machine.

So, to my question - is there a syntax for "make clean", that works automagically like "compile_all.sh"??

Thanks!
/r/b

From: Anurag Mishra [mailto:Anu...@re...]
Sent: Wednesday, March 22, 2017 1:40 PM
To: nps...@li...<mailto:nps...@li...>
Cc: Paul Duda
Subject: Re: [Npsource-cbpmodel] github + AWS image + p6 changes to hspf

Robert

RESPEC has added multiple versions of HSPF on Github.

https://github.com/respec/FORTRAN

~A

ANURAG MISHRA

650.962.1864  office  //  650.395.7224 cell

From: Burgholzer, Robert (DEQ) [mailto:Rob...@de...]
Sent: Wednesday, March 22, 2017 10:32 AM
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?

*
Confidentiality Notice: This E-mail and any attachments is covered by the Electronic Communications Privacy Act, 18 U.S.C. & 2510-2524, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, and permanently delete the original and destroy any copy, including printed copies of this email and any attachments thereto.