Error when performing accessibility analysis
YG1975 opened this issue · comments
Current Behavior
The accessibility analysis analysis makes errors as in the screenshot below. I tried it on 2 different analysis and selections with the same mistake. I am using Accessmod Docker version 5.7.17 (installed on 11.01.2022) on Mac OS Monterey.
The scenario processed table is produced, but not the raster.
Expected Behavior
Possible Solution
Steps to Reproduce
Detailed Description
Can you repeat the analysis using just the tag "test" ?
Thanks !
It gives the same issue unfortunately
Ok, maybe an issue with time / integer encoding.
Is that blocking for you ? The next slot for debugging will be in February. Maybe we could arrange something sooner with @nicolasray
(Note for myself )
1966020 / 60 => 32767
(32767).toString(2)
'111111111111111'I had the same issue with the geographic coverage analysis. As I need to produce these analyses in the coming days, I will first of all try if it is the same issue with VirtualBox. If this is the case, it means indeed it would be necessary to arrange something sooner...
Ok. I will take some time to tackle this tomorrow.
Could you share the project (.am5p) ? Temporary Dropbox link or similar. By email if it contains non-public / sensitive data.
Maybe a with a quick description of the analysis : coverage, travel time, zones, etc. If the config does not matter, I will figure out what to use.
Thanks !
Hello, I tried to import the project into the VirtualBox version but it failed. I will send you emails to continue this discussion
AccessMod 5.7.17 on VirtualBox + Docker or the old one, 5.6.* ?
AccessMod 5.7.17 on both VirtualBox and Docker versions
You can't import a project in any version ?
The import works; I could import the other day a project into the 5.7.17 Docker version and now I just succeeded to import into the 5.7.17 VirtualBox version the project exported from the Docker version (for some reason the 1st attempt did not work but now this is OK). I am currently running the accessibility analysis on the VirtualBox version to see if there is still the issue that triggered this thread.
The accessibility analysis just worked in the VirtualBox version! As I restarted the computer in the mean time, this might have an impact on the issue; i will then try to redo the analysis in the Docker version and see if the problem persists
Unfortunately in the Docker version the problem persists:
Thanks for the follow up. I will take that from here tomorrow.
Ok, 3 runs, all success. 120, 60 and unlimited.
Could you post a screenshot of a failing Accessibility analysis settings ? thanks :)
Or just write down the name of the merged land cover, scenario, or facilities used. And any non default config.
So here are the screenshots of parameters for failed analyses, Please note that I only select 5 facilities in this run (the ones of the province "East" for which column "emonc_fina" is "CEmONC"). These are the parameters I used when it last failed yesterday and I sent you the latest message :
I just tried again now with these parameters and same error message
ok. I dont get it. Maybe we should set up a screen sharing session. I will contact you directly.
Maybe I've missed a bit of information here. I tried this 4 times. All success with the settings you provided and 5 facilities, as shown below ( copy-pasted here from the facilities table ) :
| 32 | true | no | no | no | 50 | 1497 | East | Gatsibo | Ngarama_DH | D02F035 |
|---|---|---|---|---|---|---|---|---|---|---|
| 50 | true | no | no | no | 50 | 1422 | East | Kayonza | Rwinkwavu_DH | D03F052 |
| 58 | true | no | no | no | 50 | 1600 | East | Kirehe | Kirehe_DH | D04F059 |
| 72 | true | no | no | no | 50 | 1619 | East | Ngoma | Kibungo_RH | D05F073 |
| 118 | true | no | no | no | 1011 | 1541 | East | Rwamagana | Rwamagana_PH | D07F119 |
The resulting travel time map:
As this issue happened on my former computer that crashed, I will wait to get my new one and reproduce the issue. To be followed...
Is there any news on this ?
I just re-tested and now all seems to work. It was probably due on the environment on my former computer. In case anything happens again in the future I will open a new issue. Thank you again for your help!
Great.
Thanks.
I close this and if required, please reopen it