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

Failed to Import Analysis Results (Mac OSX) #129

Open
JJFriesen opened this issue Oct 22, 2015 · 7 comments
Open

Failed to Import Analysis Results (Mac OSX) #129

JJFriesen opened this issue Oct 22, 2015 · 7 comments

Comments

@JJFriesen
Copy link

Using QGIS 2.10.1-Pisa and the Spatial Syntax Toolkit for QGIS version 0.1.3 on a 2010 Macbook Air I have encountered two problems.

  1. Often when verifying my axial map layers the verification freezes before producing a list or errors.

  2. When I attempt to calculate a segment or axial analysis for my own maps or for the sample maps provided on this hub (the ones without errors) using the DepthMapX remote function I receive this error message: "Failed to import the analysis results"

And this is the script I receive afterwards:

Running analysis for map layer 'axial_map':
analysis type - axial
distance - topological
topological radius - 0
calculate choice

Start: 22/10/2015 14:12:22
...
Finish: 22/10/2015 14:12:23
Post-processing: Failed!
Total running time: 0:00:01.037349"

Has anyone encountered these issues before? Is it possible that the failure to verify is caused by my hardware?

Thanks very much for any help.

JJF

@jorgegil
Copy link
Collaborator

Re 1) this usually happens under two circumstances:

  • the unlinks and axial layers are wrongly selected, especially when one sets the axial layer as unlinks;
  • the axial map is very large and in shape file format.

The first case is a matter for the user, the second can be solved by using spatialite or postgis data formats. Not sure either is the case with you.

Re 2) This has been reported in issues #9 and #101. It seems to be an issue with depthmapXnet and Yosemite (and above?).
I've recently upgraded to Yosemite and started having the problem intermittently. The problem lies in the depthmapXnet process not returning results. However, when I start depthmapXnet from the command line it seems to work fine:

  • Open the Mac OSX Terminal
  • Type: Applications/depthmapXnet-0.30v2.app/Contents/MacOS/depthmapX
  • Press the return key and depthmapXnet starts

Note: adjust the above command to the path and file name of your depthmapXnet app

Obviously this is not a solution and we are looking into the issue.

Jorge

@jorgegil jorgegil changed the title Failed to Import Analysis Results Failed to Import Analysis Results (Mac OSX) Oct 29, 2015
@jorgegil
Copy link
Collaborator

In addition to the above "solution". Instead of using Terminal, for those uneasy with the command line interface:

  • Go to the location of the depthmapXnet-0.30v2.app
  • Right click the app and select "Show Package Contents"
  • Locate the 'Contents/MacOS/depthmap' file
  • Right click it and select "Make Alias"
  • Move the new alias file to another location of you choice (and rename it, e.g. depthmapXnet)
  • Start the depthmapXnet software by double clicking this alias

This starts the terminal and the software, and now the SST works as expected.

Jorge

@tiernanmartin
Copy link

Thanks for providing these workarounds!

@chiaramartinuzzi
Copy link

image

Hi, I might have some problem as weel with the verification of the unlinks layer.
I have 5 unlinks points with the problem "single line" even if are really good located. Is there any way to "snap" the intersections? or could I change some Layer Verification Settings?
Thanks a lot your help!

@jorgegil
Copy link
Collaborator

jorgegil commented Oct 3, 2018

This question is not related to this issue. Please open a new issue, or use the space-syntax-toolkit mailing list for general usage questions to the user community:
[email protected]

Thanks

@albertpyyang
Copy link

Hi, I have the same problem "Failed to import the analysis results" but my OS is Windows 10 64bit.
How to solve the problem?
Thanks very much for any help.

image

@jorgegil
Copy link
Collaborator

jorgegil commented May 12, 2019

Well, if the issue is on windows 10 then you should check existing issues related to that OS. The problem (and solution) is completely different than on this MacOSX related post.

It seems that your problem is related to issue #172

If it's not a new issue, and there's no solution, try the mailing list as well: [email protected]

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

No branches or pull requests

5 participants