Skip to content
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

Running selBestModel or loadreg by "water year" extremely slow, R session must be killed to exit #9

Open
AllisonOliver opened this issue Feb 26, 2016 · 4 comments

Comments

@AllisonOliver
Copy link

This is similar in theme to the other active issue posted right now.. I am running rloadest with selBestModel (and I have tried with loadreg) to calculate average daily load by "water year". I have no problems doing this by "month" or by "day" (takes about 5-8 minutes). I have run two successfully, each taking about 20 minutes... however, the last three I have tried to run have run for about 3 to 8 hours.. and I receive the error:
"Error: Unable to establish connection with R session" before it eventually finishes. I have one run that never went to completion (it ran 15 hours) and I finally killed the R session to exit.

These files are, theoretically, all the same (just different watersheds, files are the same for each) and the models being run are also very similar (all model 4 or 6). Any idea why this would be happening or what I might do to calculate this a different way?

Thanks for your help!

@dlorenz-usgs
Copy link
Member

The time required for predicting loads is dependent on the square of the
number of data points that must be processed to complete the entire time
frame. For a daily time step, computing water-year required only 365 or 366
individual data points. For an instantaneous time step, it takes 100 time
the number of data points and at least 10,000 times longer to compute.

The time required can also be very dependent on extrapolations, when
convergence of the variance estimate is extremely slow. This often happens
when users substitute a very small value, say .01 or 0.001, for 0 flows.
Zero flows are correctly handled in recent version of rloadest.

On Fri, Feb 26, 2016 at 10:43 AM, AllisonOliver [email protected]
wrote:

This is similar in theme to the other active issue posted right now.. I am
running rloadest with selBestModel (and I have tried with loadreg) to
calculate average daily load by "water year". I have no problems doing this
by "month" or by "day" (takes about 5-8 minutes). I have run two
successfully, each taking about 20 minutes... however, the last three I
have tried to run have run for about 3 to 8 hours.. and I receive the error:
"Error: Unable to establish connection with R session" before it
eventually finishes. I have one run that never went to completion (it ran
15 hours) and I finally killed the R session to exit.

These files are, theoretically, all the same (just different watersheds,
files are the same for each) and the models being run are also very similar
(all model 4 or 6). Any idea why this would be happening or what I might do
to calculate this a different way?

Thanks for your help!


Reply to this email directly or view it on GitHub
#9.

@AllisonOliver
Copy link
Author

Ah... ok, that clarifies things quite a bit. So I should just expect very slow times, and the run will eventually complete? Great to know, thank you.

@dlorenz-usgs
Copy link
Member

There is an argument to predLoad called seopt. The default is "exact,"
which forces the exact computation of all of the variances and covarainces
and takes along time in this case. The alternative is "approximate," which
does a linear approximation to the total variance and is much faster.

On Fri, Feb 26, 2016 at 12:00 PM, AllisonOliver [email protected]
wrote:

Ah... ok, that clarifies things quite a bit. So I should just expect very
slow times, and the run will eventually complete? Great to know, thank you.


Reply to this email directly or view it on GitHub
#9 (comment).

@AllisonOliver
Copy link
Author

Great to know, yes.. it is much faster! I am looking for exact computation so I will just let it take it's time, but very useful for future endeavours. Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants