
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/7cb40e8c-c0d9-4590-95e3-153173131017%40googlegroups.com.
Thanks John,
Tried to run it on a new project folder with a new Linkage Pathways run and it produced the below errors:
Will try again.
---------RETRY #9 OUT OF 10 IN 90 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #10 OUT OF 10 IN 100 SECONDS---------
---------------------------------
ERROR: Circuitscape failed.
Note: Circuitscape can only solve 2-3 million nodes
per gigabyte of available RAM. The resistance
raster for the last corridor had 32859499 nodes.
Resistance raster values that vary by >6 orders of
magnitude can also cause failures, as can a mismatch in
core area and resistance raster extents.
---------------------------------
****Failed in step 8. Details follow.****
---------------------------------
Python error on **line 520** of s8_pinchpoints.py in Linkage Mapper Version 2.0.0:
SystemExit: 1
Completed script PinchMapper...
Failed to execute (PinchMapper).
Failed at Wed Sep 18 09:21:10 2019 (Elapsed Time: 1 hours 35 minutes 57 seconds)
My resistance surface raster contains values from 1 to 100 and is at a 10m resolution. Does this mean that I need to coarsen the resolution?
Cheers,
Gwili
From: linkage...@googlegroups.com <linkage...@googlegroups.com> On Behalf Of John Gallo
Sent: Wednesday, 18 September 2019 01:53
To: linkage...@googlegroups.com
Subject: Re: Error 000464 when running Pinchpoint Mapper
Hi Gwali,
The key here I think is "Cannot get exclusive schema lock"
This is oftenan ArcGIS issue. Often caused when the file is open in another program, and then the scehma lock gets "stuck" even when the other program is closed. Quickest solution is to close ArcMap and ArcCatalog, then to open just one, and try the operation again. If that does not work, try deleting the file that is causing the problem. In some cases, such a file was created in linkage Pathways, so in that case, best to start with a new project folder and a new Linkage Pathways run.
Good luck!
John

To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkBXNSRy_zN9VvAU2TD-GGTDPSdCLrn88%2BDfDBETJbuwdA%40mail.gmail.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/002601d56dfd%244283b920%24c78b2b60%24%40gmail.com.
Dear John,
Thank you again for you swift guidance. It is very much appreciated.
I have five resistance surfaces (representing different landcover scenarios), each contains 125,881,396 cells. 42,129,800 of these have resistance values in, the other 83,751,596 are NoData. Running these with 10 core areas.
Below is the full code where Pinchpoint Mapper fails when I select the option in the Pinchpoint Mapper window labelled ‘Calculate raster centrality using Circuitscape’ and the option ‘pairwise’, which I am trying to use to calculate area-corrected centrality for my core areas:
Messages
Executing: PinchMapper E:\LM\BAU170919_2 E:\LM\BAU170919_2\CoreAreas170919.shp CA_ID E:\LM\BAU170919_2\rs_S1BAU_120919.tif 200000 false true true Pairwise
Start Time: Wed Sep 18 07:45:13 2019
Running script PinchMapper...
---------------------------------
A record of run settings and messages can be found in your log directory:
E:\LM\BAU170919_2\run_history\log
---------------------------------
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Setting data frame spatial reference to that of core area feature class.
Making local copy of resistance raster.
Creating output folder: E:\LM\BAU170919_2\pinchpt_tmp
---------------------------------
Running script s8_pinchpoints.py
Looking for E:\LM\BAU170919_2\datapass\linkTable_s5_plus.csv
Looking for E:\LM\BAU170919_2\datapass\linkTable_s5.csv
There are 10 links in the table.
This includes 9 potential corridor links.
---------------------------------
---------------------------------
Mapping pinch points in individual corridors
using Circuitscape.
---------------------------------
If you try to cancel your run and the Arc dialog hangs,
you can kill Circuitscape by opening Windows Task Manager
and ending the cs_run.exe process.
---------------------------------
Processing link ID #1. Resistance map has 4003304 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=10) ---
--- Resistance/conductance map has 4003304 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=12) ---
--- _construct_component_map cpu(elapsed=13) ---
--- Graph has 2229667 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=11) ---
--- create_amg_hierarchy cpu(elapsed=12) ---
--- solve_linear_system cpu(elapsed=18) ---
--- single_ground_solver cpu(elapsed=18) ---
--- _create_current_maps cpu(elapsed=10) ---
--- single_ground_all_pair_resistances cpu(elapsed=57) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=6) ---
--- pairwise_module cpu(elapsed=83) ---
--- Job took 1 minutes 34 seconds to complete. ---
--- compute_raster cpu(elapsed=94) ---
--- compute cpu(elapsed=94) ---
Finished with link ID #1. 1 out of 9 links have been processed.
That took 4 minutes and 41 seconds.
Processing link ID #2. Resistance map has 2242000 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=1) ---
--- Resistance/conductance map has 2242000 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=6) ---
--- _construct_component_map cpu(elapsed=7) ---
--- Graph has 1487168 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=5) ---
--- create_amg_hierarchy cpu(elapsed=7) ---
--- solve_linear_system cpu(elapsed=8) ---
--- single_ground_solver cpu(elapsed=8) ---
--- _create_current_maps cpu(elapsed=4) ---
--- single_ground_all_pair_resistances cpu(elapsed=28) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=2) ---
--- pairwise_module cpu(elapsed=40) ---
--- Job took 0 minutes 42 seconds to complete. ---
--- compute_raster cpu(elapsed=42) ---
--- compute cpu(elapsed=42) ---
Finished with link ID #2. 2 out of 9 links have been processed.
That took 3 minutes and 20 seconds.
---------------------------------
Warning:
Circuitscape can only solve 2-3 million nodes
per gigabyte of available RAM.
Total physical RAM on your machine is ~7.8 GB.
Available memory is ~3.2 GB.
Your resistance raster has 9433433 nodes.
---------------------------------
Processing link ID #3. Resistance map has 9433433 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=8) ---
--- Resistance/conductance map has 9433433 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=26) ---
--- _construct_component_map cpu(elapsed=28) ---
--- Graph has 5597771 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=30) ---
--- create_amg_hierarchy cpu(elapsed=43) ---
--- solve_linear_system cpu(elapsed=38) ---
--- single_ground_solver cpu(elapsed=38) ---
--- _create_current_maps cpu(elapsed=17) ---
--- single_ground_all_pair_resistances cpu(elapsed=140) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=7) ---
--- pairwise_module cpu(elapsed=187) ---
--- Job took 3 minutes 17 seconds to complete. ---
--- compute_raster cpu(elapsed=197) ---
--- compute cpu(elapsed=197) ---
Finished with link ID #3. 3 out of 9 links have been processed.
That took 6 minutes and 34 seconds.
---------------------------------
Warning:
Circuitscape can only solve 2-3 million nodes
per gigabyte of available RAM.
Total physical RAM on your machine is ~7.8 GB.
Available memory is ~2.9 GB.
Your resistance raster has 11818929 nodes.
---------------------------------
Processing link ID #5. Resistance map has 11818929 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=3) ---
--- Resistance/conductance map has 11818929 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=44) ---
--- _construct_component_map cpu(elapsed=51) ---
--- Graph has 11513317 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=35) ---
--- create_amg_hierarchy cpu(elapsed=102) ---
--- solve_linear_system cpu(elapsed=109) ---
--- single_ground_solver cpu(elapsed=109) ---
--- _create_current_maps cpu(elapsed=59) ---
--- single_ground_all_pair_resistances cpu(elapsed=326) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=8) ---
--- pairwise_module cpu(elapsed=399) ---
--- Job took 6 minutes 43 seconds to complete. ---
--- compute_raster cpu(elapsed=403) ---
--- compute cpu(elapsed=403) ---
Finished with link ID #5. 4 out of 9 links have been processed.
That took 10 minutes and 36 seconds.
Processing link ID #6. Resistance map has 4563136 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=1) ---
--- Resistance/conductance map has 4563136 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=13) ---
--- _construct_component_map cpu(elapsed=15) ---
--- Graph has 4235934 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=12) ---
--- create_amg_hierarchy cpu(elapsed=36) ---
--- solve_linear_system cpu(elapsed=26) ---
--- single_ground_solver cpu(elapsed=26) ---
--- _create_current_maps cpu(elapsed=12) ---
--- single_ground_all_pair_resistances cpu(elapsed=93) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=5) ---
--- pairwise_module cpu(elapsed=118) ---
--- Job took 2 minutes 1 seconds to complete. ---
--- compute_raster cpu(elapsed=121) ---
--- compute cpu(elapsed=121) ---
Finished with link ID #6. 5 out of 9 links have been processed.
That took 5 minutes and 26 seconds.
Processing link ID #7. Resistance map has 4329471 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=4) ---
--- Resistance/conductance map has 4329471 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=14) ---
--- _construct_component_map cpu(elapsed=15) ---
--- Graph has 2464890 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=13) ---
--- create_amg_hierarchy cpu(elapsed=20) ---
--- solve_linear_system cpu(elapsed=19) ---
--- single_ground_solver cpu(elapsed=19) ---
--- _create_current_maps cpu(elapsed=8) ---
--- single_ground_all_pair_resistances cpu(elapsed=66) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=5) ---
--- pairwise_module cpu(elapsed=91) ---
--- Job took 1 minutes 36 seconds to complete. ---
--- compute_raster cpu(elapsed=96) ---
--- compute cpu(elapsed=96) ---
Finished with link ID #7. 6 out of 9 links have been processed.
That took 4 minutes and 40 seconds.
Processing link ID #8. Resistance map has 4326861 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=1) ---
--- Resistance/conductance map has 4326861 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=18) ---
--- _construct_component_map cpu(elapsed=20) ---
--- Graph has 3982425 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=13) ---
--- create_amg_hierarchy cpu(elapsed=34) ---
--- solve_linear_system cpu(elapsed=27) ---
--- single_ground_solver cpu(elapsed=27) ---
--- _create_current_maps cpu(elapsed=10) ---
--- single_ground_all_pair_resistances cpu(elapsed=93) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=5) ---
--- pairwise_module cpu(elapsed=122) ---
--- Job took 2 minutes 5 seconds to complete. ---
--- compute_raster cpu(elapsed=125) ---
--- compute cpu(elapsed=125) ---
Finished with link ID #8. 7 out of 9 links have been processed.
That took 5 minutes and 1 seconds.
Processing link ID #9. Resistance map has 4110309 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=3) ---
--- Resistance/conductance map has 4110309 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=11) ---
--- _construct_component_map cpu(elapsed=12) ---
--- Graph has 2336232 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=13) ---
--- create_amg_hierarchy cpu(elapsed=24) ---
--- solve_linear_system cpu(elapsed=12) ---
--- single_ground_solver cpu(elapsed=12) ---
--- _create_current_maps cpu(elapsed=6) ---
--- single_ground_all_pair_resistances cpu(elapsed=60) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=4) ---
--- pairwise_module cpu(elapsed=82) ---
--- Job took 1 minutes 25 seconds to complete. ---
--- compute_raster cpu(elapsed=85) ---
--- compute cpu(elapsed=85) ---
Finished with link ID #9. 8 out of 9 links have been processed.
That took 4 minutes and 35 seconds.
Processing link ID #10. Resistance map has 3133176 nodes.
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=1) ---
--- Resistance/conductance map has 3133176 nodes ---
--- Solving focal pair 1 of 1 ---
--- _construct_g_graph cpu(elapsed=9) ---
--- _construct_component_map cpu(elapsed=10) ---
--- Graph has 2986644 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=9) ---
--- create_amg_hierarchy cpu(elapsed=27) ---
--- solve_linear_system cpu(elapsed=17) ---
--- single_ground_solver cpu(elapsed=17) ---
--- _create_current_maps cpu(elapsed=15) ---
--- single_ground_all_pair_resistances cpu(elapsed=75) ---
--- Solved focal pair 1 of 1 ---
--- write_aaigrid cpu(elapsed=4) ---
--- pairwise_module cpu(elapsed=92) ---
--- Job took 1 minutes 34 seconds to complete. ---
--- compute_raster cpu(elapsed=94) ---
--- compute cpu(elapsed=94) ---
Finished with link ID #10. 9 out of 9 links have been processed.
That took 4 minutes and 44 seconds.
Building output statistics and pyramids for corridor pinch point raster
Copy of linkTable written to E:\LM\BAU170919_2\output\BAU170919_2_linkTable_s5_plus.csv
Creating shapefiles with linework for links.
---------------------------------
Mapping global pinch points among all
core area pairs using Circuitscape.
Circuitscape will be run in PAIRWISE mode.
---------------------------------
Warning:
Circuitscape can only solve 2-3 million nodes
per gigabyte of available RAM.
Total physical RAM on your machine is ~7.8 GB.
Available memory is ~3.8 GB.
Your resistance raster has 32859499 nodes.
---------------------------------
Resistance map has 32859499 nodes.
---------------------------------
If you try to cancel your run and the Arc dialog hangs,
you can kill Circuitscape by opening Windows Task Manager
and ending the cs_run.exe process.
---------------------------------
Calling Circuitscape:
--- Reading maps ---
--- load_maps cpu(elapsed=56) ---
--- Resistance/conductance map has 32859499 nodes ---
--- Solving focal pair 1 of 45 ---
--- _construct_g_graph cpu(elapsed=173) ---
--- _construct_component_map cpu(elapsed=187) ---
--- Graph has 19753762 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=159) ---
--- create_amg_hierarchy cpu(elapsed=305) ---
--- solve_linear_system cpu(elapsed=208) ---
--- single_ground_solver cpu(elapsed=208) ---
--- _create_current_maps cpu(elapsed=112) ---
--- single_ground_all_pair_resistances cpu(elapsed=864) ---
--- Solved focal pair 1 of 45 ---
--- Solving focal pair 2 of 45 ---
--- _construct_g_graph cpu(elapsed=154) ---
--- _construct_component_map cpu(elapsed=165) ---
--- Graph has 20052163 nodes, 2 focal nodes and 1 components. ---
--- _construct_g_graph cpu(elapsed=152) ---
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #1 OUT OF 10 IN 10 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #2 OUT OF 10 IN 20 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #3 OUT OF 10 IN 30 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #4 OUT OF 10 IN 40 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #5 OUT OF 10 IN 50 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #6 OUT OF 10 IN 60 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #7 OUT OF 10 IN 70 SECONDS---------
--------------------------------------------------
The following error is being reported on line 578 of "C:\gis\Linkage_Mapper_2_0_0\toolbox\Scripts\s8_pinchpoints.py":
[Errno 2] No such file or directory: 'E:\\LM\\BAU170919_2\\pinchpt_tmp\\output\\Circuitscape_cum_curmap.npy'
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Will try again.
---------RETRY #8 OUT OF 10 IN 80 SECONDS---------
Please let me know if you require any further details.
With thanks,
Gwili
From: linkage...@googlegroups.com <linkage...@googlegroups.com> On Behalf Of John Gallo
Sent: Wednesday, 18 September 2019 23:22
To: linkage...@googlegroups.com
Subject: Re: Error 000464 when running Pinchpoint Mapper
Hi Gwili,
it is unlikely that is what it means. It looks like there is something else going on. Please send the full error message.
Also, please let me know the area of the resistance surface, or the approximate number of cells. 10 m resolution should be fine for the landscape scale, but not the continental scale. Depends on the size of the landscape though.
Thanks,
John

Virus-free. www.avast.com
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/002601d56dfd%244283b920%24c78b2b60%24%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkBF0%3DQ7YQxGBTwy_n9Oe5pwBuWfXj7Ddizcu7zRFR67Cg%40mail.gmail.com.
Warning:
Circuitscape can only solve 2-3 million nodes
per gigabyte of available RAM.
Total physical RAM on your machine is ~7.8 GB.
Available memory is ~2.9 GB.
Your resistance raster has 11818929 nodes.
---------------------------------
Processing link ID #5. Resistance map has 11818929 nodes."

To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/019401d56ec9%24753ad750%245fb085f0%24%40gmail.com.
Thanks John:
Would you advise me to attempt to run it on a more powerful computer? Or aggregate to 20m pixels and try that?
With thanks again for your time,
Gwili
From: linkage...@googlegroups.com <linkage...@googlegroups.com> On Behalf Of John Gallo
Sent: Thursday, 19 September 2019 15:54
To: linkage...@googlegroups.com
Subject: Re: Error 000464 when running Pinchpoint Mapper
Thasnk Gwili,
Hmmmm. You were right, it may be too many cells, as per the warnings.
"---------------------------------
Warning:
Circuitscape can only solve 2-3 million nodes
per gigabyte of available RAM.
Total physical RAM on your machine is ~7.8 GB.
Available memory is ~2.9 GB.
Your resistance raster has 11818929 nodes.
---------------------------------
Processing link ID #5. Resistance map has 11818929 nodes."
Yes, try your original fix and see if that works. Looks to me like you may only need to resample from 10 m to 20 m cells, but you may want to go to 100 m as a first time test to be sure this is not the problem.
Other thoughts:
2) Try running it in Arc Catalog if you are doing it in Arc map. (Were you already using Arc Catalog?)
3) Try it without clicking the optional box for calculating centrality
and if all the above did not work, lets gather more data:
4) Try it All to one. instread of pairwise.
You can do fixes 1-3 all in the next run, but if you want to be sure to isolate the problem, it is ideal to do one fix at a time.
Good luck,
John

To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkARwdfc_5moc%2B0O7xaGENDy1zFYRSqSQDKUDtj%2BKYkq5A%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mapper+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/7cb40e8c-c0d9-4590-95e3-153173131017%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mapper+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkBXNSRy_zN9VvAU2TD-GGTDPSdCLrn88%2BDfDBETJbuwdA%40mail.gmail.com.
Virus-free. www.avast.com
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mapper+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/002601d56dfd%244283b920%24c78b2b60%24%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mapper+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkBF0%3DQ7YQxGBTwy_n9Oe5pwBuWfXj7Ddizcu7zRFR67Cg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mapper+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/019401d56ec9%24753ad750%245fb085f0%24%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mapper+unsubscribe@googlegroups.com.
...

To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/7cb40e8c-c0d9-4590-95e3-153173131017%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkBXNSRy_zN9VvAU2TD-GGTDPSdCLrn88%2BDfDBETJbuwdA%40mail.gmail.com.
Virus-free. www.avast.com
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/002601d56dfd%244283b920%24c78b2b60%24%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkBF0%3DQ7YQxGBTwy_n9Oe5pwBuWfXj7Ddizcu7zRFR67Cg%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/019401d56ec9%24753ad750%245fb085f0%24%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/CALL%2BJkARwdfc_5moc%2B0O7xaGENDy1zFYRSqSQDKUDtj%2BKYkq5A%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/bd828f85-e465-49be-a687-37c1c53b6374%40googlegroups.com.
Hi Gwili,Thanks for your patience on this and your thoroughness. nad for the full model dialog.
OK, so, to review at a high level, it worked at 10m, but only when the optional "calculate centrality" box was NOT checked. yes. When that was checked, it did not run. yes However, with that box checked it did run at 100m cell size yes. But then it did not at 20 m. yes, but it also ran at 30m size, Furhter, when it failed, if failed on a different pair of cores, not the same pair each time. yes Please let me know if that is not all correct.So it sounds like the centrality calculation is causing the problems. yes and specifically the 'calculate raster centrality using Circuitscape' tool
This is what I would suggest:
1) Run it at 10 m without centrality option checked. If that works, done and yes it works2) Then run the Centrality Mapper stand-alone tool. done and yes, it produces CF_Centrality values for each linkage in the link table. However, I was also looking to create CF_Central values for each of the core areas to calculate area weighted centrality.
3) Please let me know how that all worked. I may need to log an issue in git hub to fix or remove the optional calculate centrality box in Pinchpoint Mapper.Thanks!JohnJohn Gallo, Ph.D.
Senior Scientist
Conservation Biology Institute
136 SW Washington Avenue, Suite 202
Corvallis, OR 97333
Remote Office: Inglenook, CAUpdates: Action Research Newsletter
...

--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/46ae3dae-99a0-4c79-9925-bfcac29d3743%40googlegroups.com.