-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
p532c Compile - errors with run_etm.csh, getafoload.f #5
Comments
Can you list the commands that you used to run this? Also, what path were you in when running? Thanks! |
I followed the Readme file on the server to do a test run: "cd ../../run/standard/ |
Cool - I am going through the run process step by step now to see where the stuff blows up. The system does these things in order when you call "run_all.csh p532cal_062211 stmary":
So far, I have completed steps 1-3, and it looks like from your error that something blows up around the time of the ETM conversion to WDM part. Which is probably fairly simple to fix. If you want to pick up this process at the "run_etm.csh" step, that would be cool. |
Can you please explain this further? Did you run these .csh separately? Do you want me to run them separately too and see where I get the error? |
Yes and yes :). But you can start at step 4 since I completed steps 1-3 in your model tree just to be certain that we had the same conditions. |
Thanks Rob. Yes, the issues's in the fourth one "run_etm.csh p532cal_062211 stmary". The first three work ok. |
OK - I think that it may be worth taking this to the CBP listserv to see if anyone has insight. I suspect that it has something to do with the shell that they are using "csh" and how it handles file paths, because it is not finding the "random.ksh" file, but that file is most certainly present in the install tree. I am guessing this random.ksh gives them some string to use for a temp file name or something. Can you try to reach out to the list? |
Sure! Who would be the best person to ask? Gary Shenk? |
I was able to resolve this error by installing "ksh" (it was not on my computer before). That error's gone now, but I get another error with "run_etm.csh p532cal_062211 stmary": PROBLEM FILE WRITTEN Error: opening wdm= *** "PROBLEM in etm PROBLEM FILE WRITTEN Error: opening wdm= *** |
This interesting - it seems like it makes it through many run files OK, but is failing at afo? Here is acopy of the log justfor info:
|
I exactly get the same thing. Thought to take this away? |
Not at the moment, no. I suspect that something may be failing before he
tries to run the AFO, and then it is not stepping back a directory so that
the path that it's looking for doesn't exist relative to where it is.
Not sure if that makes any sense :-)
…On Fri, Apr 14, 2017 at 3:01 PM eascesharif ***@***.***> wrote:
I exactly get the same thing. Thought to take this away?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEXAIoaqAVWGsY5xNzFEbQrfQq8ZwpI-ks5rv8KPgaJpZM4M9xmg>
.
|
I can verify that the file that is looking for does in fact exist. Which is
why I think it's getting confusing.
…On Fri, Apr 14, 2017 at 3:04 PM Robert Burgholzer ***@***.***> wrote:
Not at the moment, no. I suspect that something may be failing before he
tries to run the AFO, and then it is not stepping back a directory so that
the path that it's looking for doesn't exist relative to where it is.
Not sure if that makes any sense :-)
On Fri, Apr 14, 2017 at 3:01 PM eascesharif ***@***.***>
wrote:
> I exactly get the same thing. Thought to take this away?
>
>
>
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub
> <#5 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AEXAIoaqAVWGsY5xNzFEbQrfQq8ZwpI-ks5rv8KPgaJpZM4M9xmg>
> .
>
|
The wdm files are smaller in the afo folder compared to the other folders (land uses) at: ./p532c/tmp/wdm/land Although I see (in the log report) that the UCI has been generated similar to the other land uses. |
I think The error is it that it's saying it can't find it, but it could be that it's in properly formed in the air is misleading. One way to check it out would be to do an export of that WDMWD I am but it could be that it's in properly formed in the air is misleading. One way to check it out would be to do an export of that WDM using wdimex - any luck oj bay model listserv? |
I contacted Dave and Gary, but haven't heard from them yet. No sure if
they're the best people to reach out for this issue, so let me know if you
have anyone better in mind.
…On Fri, Apr 14, 2017 at 6:03 PM, rburghol ***@***.***> wrote:
I think The error is it that it's saying it can't find it, but it could be
that it's in properly formed in the air is misleading. One way to check it
out would be to do an export of that WDMWD I am but it could be that it's
in properly formed in the air is misleading. One way to check it out would
be to do an export of that WDM using wdimex - any luck oj bay model
listserv?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AX2uYBNGlwCJHIJiMUtI3sTZ5mpyLFyVks5rv-0cgaJpZM4M9xmg>
.
--
Ebrahim Ahmadisharaf, Ph.D.
Postdoctoral Associate
Biological Systems Engineering Department
Virginia Polytechnic Institute and State University
Blacksburg, VA 24060
Webpage: ww2.bse.vt.edu/ahmadisharaf
<https://sites.google.com/vt.edu/ebrahim-ahmadisharaf>
|
I think the best approach is to contact the listserv - https://sourceforge.net/p/npsource/mailman/npsource-cbpmodel/ |
Just posted it there. It's pending approval by the moderator. Can you later check and see if you see it? It's my first time posting this, so wanted to make sure that everyone can see it ok. |
Ahh - just subscribe to the list and you should be good to go. |
From John Massey at CBP:
|
Can you please explain this a bit further? I don't get what needs to be done |
Sorry if that was vague. The shaded text block is the output of a routine called "diff" that compares changes between 2 files. The lines marked with "<" are the original file line, and the lines marked with ">" are the lines that were changed in the new version. The "6c6" references are in the format "line # in file1"c"line # of file 2" So, if you open the files on our install and edit the lines that correspond to "<" to have the text shown with ">" you should be good to go. Note: diff syntax is "diff file1 file2" and the "<" and ">" are relative to the order of the files in the command, NOT any implied Before/After - so if you run "diff file1 file2" the "<" will pertain to file1 and ">" to file2, whereas if you ran "diff file2 file1" the "<" would pertain to file2, and the ">" would pertain to file1. |
There's a mix of situtations in those two files (main.f and getafoload.f) in my folder (.\p532c\code\src\etm\etm_and_postproc). Some of them currently match ">" lines and some match "<". I tried changing all but got the same modeling error that I had before. |
Did you remember to remove the old executables and recompile after the code changes? |
no. do you mean cleaning the make files? |
Yup - and I think that we ran into situations in the past where the "make clean" didn't always remove all files, so you may want to do an "ls -l" and not the dates of the etm_and_postproc executables to make sure that they get updated after you compile, if not, you will have to remove them manually then recompile. |
hmm. now I see an error when compiling the code: "Warning: Character length of actual argument shorter than of dummy argument 'tabnam' (11/64) at (1)
Error: PARAMETER attribute conflicts with DUMMY attribute in 'wdmfil' at (1) Of what John said, I don't see a change in the line (wdmfil=dfile+10). do you? I also don't recall we exactly faced the first error. do you? If not, should I open a new thread for it? |
Seems like the issue that is critical to solving this one, so let's just solve it here. And, it is likely part of the replacement code that they sent? Can you include the line before the error printout so that we can see what the code that caused it was? |
Yeah - the change he made was to comment out the line -- the line is ignored when "C" is the first character of a line in fortran. |
I amend my statement, I think that he actually UN-commented that line:
There appear to be a couple of other instances where that was done. |
Just looking through this, I think my assignment of the pre and post fioles may have been wrong -- perhaps the "CLOUDFISH" files, i.e. "<" are what we are supposed to change them TO. You may have indicated earlier that it appeared the changes were going in a different direction than what I said. Can you let me know which way you have been making the changes? I will follow up with John to get clarification as well. |
Adding "C" in the beginning of those lines took that error away, but still no output's generated. " creating data output for PL1_5910_0001 p532cal_062211 Although I see "set_tree" in that directory. Thoughts? |
Can you give me some more details? You're saying this error went away:
and now it proceeds farther along the routine? How much farther along? |
The error was on river segment "PL1_5910_0001", land segment "A24037" and land use "afo". It's not stuck there anymore in the "etm" module (run_etm.csh). It goes further down and seems like it fails at the last module (summarize_output_aveann.csh). |
Cool - sounds like we need to debug summarize_output_aveann.csh - can you migrate your code changes to deq2 for me? I will verify that they work there, and produce the same new error :), and then commit them to git. |
Hey - I renamed this issue and propose opening another thread to debug "run_scenario_postproc.csh"
|
Yes, we got the error on 4 (etm), but we don't get any error until 8. |
I can run all the "csh" of the "run_all.csh", except the last one (summarize). I get this: "usage: summarize_output_aveann.csh scenario basin year1 year2 |
I can't copy the files to deq2 computer. does this folder (p532c-ubuntu) still exist? |
I get an error when transferring the files. "rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.0]" |
Although I don't get any compiling error, I get the following error when running p532c:
"HSPF simulation completed.
../../..//run/useful/random.ksh: Command not found.
At line 15 of file main.f (unit = 5, file = 'stdin')
Fortran runtime error: End of file
‘../../..//config/blank_wdm/river.wdm’ -> ‘PL1_5910_0001.wdm’
Land Loads and transfer wdms for
p532cal_062211 PL1_5910_0001 1985 2005
PROBLEM FILE WRITTEN
Problem opening following file
../../../output/etm/p532cal_062211/A24037toPL1_5910_0001.etm
PROBLEM in etm
PROBLEM FILE WRITTEN
Problem opening following file
../../../output/etm/p532cal_062211/A24037toPL1_5910_0001.etm"
The text was updated successfully, but these errors were encountered: