-
Notifications
You must be signed in to change notification settings - Fork 35
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
AssertionError: norm(G * v .- curr) / norm(curr) - multiple failures #370
Comments
@ranjanan -- out of curiosity is there any way that one can "hack" the solver error threshold if that is indeed the problem throwing these errors? I'm not even sure how that error is arising and maybe that's a stupid question, but I figured I would at least ask. |
@ptfreeman-csp there isn't a way to hack that solver error tolerance. It's in there to make sure the solver has converged to the required relative tolerance. Let me take a look at these files. |
@ptfreeman-csp I've requested access to the files through my email. |
Hi @ranjanan -- I was able to get Omniscape to run successfully using some older versions of Omniscape and supporting packages using the Project.toml and Manifest.toml from @gagecarto who outlined his fix here. I will share those files with you and the input files. |
I see, thanks for the update @ptfreeman-csp. That solver check is in there so you can know that you can trust your answers. There are a lot of really ill-conditioned matrices in here, so it's always good to know that the linear solver has converged. |
I'm going to keep this open and try and isolate one of the linear solves that is failing and then study it. |
Yikes - so even if the (now working) older version runs without crashing or
errors, some of the outputs may be erroneous? That’s concerning. Let me
know what you find.
…On Wed, Dec 28, 2022 at 12:33 PM Ranjan Anantharaman < ***@***.***> wrote:
I'm going to keep this open and try and isolate one of the linear solves
that is failing and then study it.
—
Reply to this email directly, view it on GitHub
<#370 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUE56ZZIOXWGYYIEFKXMFD3WPSPYPANCNFSM6AAAAAASWFC3TA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
In theory, yes. Although the version you said things worked on also has a check for convergence and you're saying it worked. So could be a less concerning bug somewhere too. It would be easier for me if you can reproduce this error with a Circuitscape advanced mode problem though. Is that easy to do on your end? |
This problem runs fine as of 5.11.2 |
I don't understand how that can be possible - perhaps it's the combination of dependencies I have in my Julia environment. |
Does this mean running Omniscape with Circuitscape version 5.11.2 (or maybe you mean 5.12.2) fixes it? The current release of Omniscape uses 5.11. |
Honestly I’m not sure - I tried running all of this with the fully updated
versions of Circuitscape and Omniscape and it didn’t run properly on my
machine and I don’t know how @ranjan got it to run.
On Mon, Jan 16, 2023 at 9:17 AM mir ***@***.***> wrote:
This problem runs fine as of 5.11.2
Does this mean running Omniscape with Circuitscape version 5.11.2 fixes
it? The current release of Omniscape uses 5.11.
—
Reply to this email directly, view it on GitHub
<#370 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUE56Z6TZMY6KMIQI5OQSDTWSV7B7ANCNFSM6AAAAAASWFC3TA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Patrick T. Freeman
Scientist
Pronouns: he/him
Conservation Science Partners, Inc.
11050 Pioneer Trail, Suite 202
Truckee, CA 96161
P: 209.712.7865 | csp-inc.org <http://www.csp-inc.org/>
|
@ranjanan can you confirm you used Circuitscape 5.12.2? |
Can confirm this still happens with Circuitscape 5.12.2 (this time at "100%" completion with 9 minutes to go on a 3 day run)
|
@ranjanan can this just be changed to throw a warning stating that results may be inaccurate when the assertion fails instead of throwing an error? |
I am still having this issue, I would prefer not to use the older environment fix used in this thread: https://github.com/Circuitscape/Omniscape.jl/issues/127 if at all possible. |
I'm also still having this issue, but unlike the above, my moving window failures do not occur on NA/NaN or correspondingly high resistance cells. Have there been any developments? (BTW, I'm using Omniscape [0.5.8]). |
I also having the issue in Circuitscape (not using Omniscape) when I set the precision to "single". Circuitscape v5.13.1 / Julia v1.9.3 |
Have just run into this same issue (julia/1.9.4) for runs with 25 or 50 mile windows using resistance surfaces that are fine for smaller windows. Tinkered with small changes in block size, hoping it might nudge the windows past some problematic pixel arrangement, but to no effect. Am not relishing the idea of having to mess around with a painfully arrived at series of window/block cell sizes. Hopefully I can identify the cells and try a method in another thread for fixing them individually... |
For future reference, if anyone is coming across this issue because they're getting the same error, make sure you're using Circuitscape 5.13.3 or greater (to check your version of Circuitscape, enter the Package prompt by typing |
Describe the bug, with logs
I have been running into an issue running Omniscape (that calls aspects of Circuitscape) and @vlandau suggested that I cross-post here for help. I'm in desperate search for help as I am mystified as to why this error is occurring and also on a rapidly approaching deadline. I am trying to run two rather large omni-directional connectivity models with substantial moving window sizes (but that aren't the most massive among other species that have run just fine using this exact workflow). Omniscape runs (in this case for over four hours) with one message that a moving window has failed at a particular cell but otherwise fine and then 20 minutes before complete I got the error message pasted below. I ran a much smaller test area that was only a small component of the larger raster and the model ran successfully without errors so I'm not sure what is happening here.
**How to reproduce (PLEASE ATTACH YOUR PROBLEM FILES) **
I have included the source and resistance layers and the .ini file in this folder. I reproduce my .ini text here for one of the species that I'm running into trouble with in case anyone spots any problems. I have to provide you specific access to the folder so just request access to the folder.
Circuitscape and Julia version
Circuitscape v5.11.2
Omniscape v0.5.8
Julia Version 1.6.1
Commit 6aaedecc44 (2021-04-23 05:59 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: AMD EPYC 7763 64-Core Processor
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-11.0.1 (ORCJIT, generic)
Additional context
I have run several other models with slightly different footprints but all in the same general area without issue.
The text was updated successfully, but these errors were encountered: