Skip to content

Circuitscape cannot find files with 'compute()' but runs fine if used with 'start()' #397

Open
@MountainCedar

Description

@MountainCedar

I'm having an issue where Circuitscape can work fine if run immediately after if I use start() to generate an .ini file and then run, but gives an error if I try to compute() that exact same .ini file generated from the start() process (i.e. if at step 10 I select to "run later", then try to compute that .ini file). I'm running Julia 1.9.3 in a Windows environment, and have encountered this with both the stable and development version of Circuitscape. The error it gives is:

julia> compute("C:\Users\Human\Desktop\Restoration_Project_2023\Analysis\output.ini")
[ Info: 2023-10-11 11:53:13 : Precision used: Double
[ Info: 2023-10-11 11:53:15 : Reading maps
ERROR: the file "(Browse for a resistance file)" does not exist
Stacktrace:
[1] error(s::String)
@ Base .\error.jl:35
[2] read_raster
@ C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\io.jl:503 [inlined]
[3] _grid_reader(T::Type, file::String)
@ Circuitscape C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\io.jl:114
[4] read_cellmap(habitat_file::String, is_res::Bool, #unused#::Type{Float64})
@ Circuitscape C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\io.jl:91
[5] load_raster_data(T::Type, V::Type, cfg::Dict{String, String})
@ Circuitscape C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\io.jl:442
[6] raster_one_to_all(T::Type, V::Type, cfg::Dict{String, String})
@ Circuitscape C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\raster\onetoall.jl:4
[7] _compute(T::Type, V::Type, cfg::Dict{String, String})
@ Circuitscape C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\run.jl:49
[8] macro expansion
@ .\timing.jl:393 [inlined]
[9] compute(path::String)
@ Circuitscape C:\Users\Human.julia\packages\Circuitscape\qlA9V\src\run.jl:31
[10] top-level scope
@ REPL[10]:1

At first I thought this might be related to a file pathing issue on Windows, but have tried '\\', '/', and '\' syntaxt well as selecting the path using file picker manually - and all work to run the job if it is run at step 10 of start() - but otherwise throw an error if that same .ini file generated though start() is used with compute()

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions