Closed slamander closed 4 years ago
Hi Alex, we can work on figuring out what's going on here. It would be very helpful if you could share the input raster files. You can send them to vincent(at)csp-inc.org if you prefer not to post them publicly. A dropbox or google drive link will work fine..
I wonder if the dropbox folders linked in the .ini file are publicly accessible.
Edit: obviously they are local paths.
@ViralBShah seems that this is a problem with read_raster
. I wrote that function so I will try to debug and get it patched today once I get the input files.
Hey, thanks for the quick response! Let me know if this link works: https://drive.google.com/drive/folders/1lgoPAOV5ZsfJB_EyngiHFdx2mgPmQ4n-?usp=sharing habitat file: "AZI_ARM.asc" point locations: "node_AZI_ARM.asc" I'm also uploaded my include file, in case you need it.
Thanks @slamander, I'll check it out now! Link works fine.
Looks like this is actually nothing to do with read_raster
, I jumped the gun on that since it was in the stack trace and we've had bugs in it before.
@slamander it looks like the problem may be simple. It appears that you have non-integer numbers in your node file. That file must have only integers, no decimals. It looks like that file is also identical to the resistance surface, so maybe it was just a simple error early on in the workflow?
Running a test now. I'll post back here once I confirm that the node file is in fact the issue.
We should ideally add an input validation pass so that we can give an error to the user.
We should ideally add an input validation pass so that we can give an error to the user.
Agreed. Should be easy enough to add that.
Okay -- got things working by replacing the node file with a dummy file with three manually-defined nodes. It was the decimal values in the node file that was causing this issue. @slamander just in case you haven't seen it, you can find more info on how to create/format a node file in the docs, at https://circuitscape.org/docs under "Focal node location and data type".
Closing this issue now and I'll open a new one to add that error you suggested @ViralBShah
@vlandau Thank you very much for your rapid solution!
Best, -Alex.
Happy to help! I'm glad we were able to resolve it for you. Don't hesitate to open another issue if you run into more problems.
Hello,
I am running CS v 5.7.0 on windows with Julia (through R using
JuliaCall::Julia_command()
). I've had no problems with analyses in the past. However, lately I've been receiving this error during a pairwise analysis which I have successfully ran in the past.Could anyone explain this error to me, and--if possible--provide suggestions for fixing it? I've pasted the error message, as well as supplied my .ini specifications below. If necessary I can provide my habitat and point location rasters.
Thanks in advance for your help!
-alex.
My .ini file: