-
Notifications
You must be signed in to change notification settings - Fork 14
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
referral analysis issue #371
Comments
Thanks for reporting this. It should handle this fine. I remember something – maybe related – occurring when subsetting a large number of facilities. Solved by : e504dce, issue #209 What you can do :
Notes for myself: The error text reported was not the real issue. Internally, the referral module also use the faulty method e.g. here |
Hi Fred, So I tried a few things listed below:
I've sent you an e-mail with a link to my project and logs. Thanks! |
Thanks. So, this seems to be linked to the request size, as 10'000 LAST would still require a lots of bytes in the the SQL string : |
…during v.extract. A range conversion helper has been created to use 'cats' range parameter. Seems to work fine up to 50'000 facilities and various samples
Should be solved in 5.8.1-alpha.6 |
@rewrew21 : great if you can check that it is now working for you in the latest version 5.8.1-alpha.6 (or 5.8.1 at the end of this week). |
Current Behavior
I am trying to run a referral analysis FROM 30'000 households TO 15 facilities. To save time, I've checked the "permute groups" box. But when I launch the analysis it crashes after a few seconds with the following error message: "2 nodes produced errors; first error: cannot open the connectionCallcheckForRemoteErrors(val)".
I have tried this analysis on MAC and Windows environments (both latest versions with the latest updates), and both times with the latest AM version on Docker (with latest update) AND the latest version of AM on VirtualBox (with latest udpate). I've also played around with the number of cores used and ram, still no luck
However, when I run the analysis without checking the "permute groups" box, it works fine (I stopped the analysis after an hour because it would have taken more than 4 days).
Finally, I tried to run the analysis FROM the 15 facilities TO the 30'000 households (isotropic) without the "permute groups" box checked, it crashed as well.
So I'm wondering if the issue is with the very high number of facility points (or households here)...
Thanks in advance for your help!
Andrew
The text was updated successfully, but these errors were encountered: