You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While performing a test for a geographic coverage analysis, I wanted to stop the process as it was taking too much time. But even after pressing twice the stop button it continued to process the analysis.
Expected Behavior
Pressing the stop button should normally stop the process
Possible Solution
Steps to Reproduce
Launch a geographic coverage analysis with many points (around 2700 in ma case). AccessMod Docker 5.7.3 and Docker 3.3.3 on Mac
Detailed Description
While performing a test for a geographic coverage analysis, I wanted to stop the process as it was taking too much time. But even after pressing twice the stop button it continued to process the analysis. I had a confirmation message saying that it would try to stop whenever possible but still continued performing.
I finally stopped the program and relaunched it without problem
The text was updated successfully, but these errors were encountered:
The technique used to stop the computation does not work since the last Shiny version upgrade in AccessMod. In fact, they changed this in 2018, but AccessMod – VM version – kept using an older version where it worked. The UI was not updated until version 5.7.9, which is the latest version. See https://github.com/fxi/AccessMod_shiny/blob/docker_alpha/changes.md for more info.
Stoping/Managing running process is a simple problem that could have been solved by a jobs based computation – queuing system – but this feature was declined. I implemented something like this in 2014 in a previous project of mine, LebaMod. It featured a queuing system and parallel computation on a large server – not requested for AccessMod either. The good news is that with the novel docker based version, we could theoretically implement something similar on top of the current app. I'm working on it.
Current Behavior
While performing a test for a geographic coverage analysis, I wanted to stop the process as it was taking too much time. But even after pressing twice the stop button it continued to process the analysis.
Expected Behavior
Pressing the stop button should normally stop the process
Possible Solution
Steps to Reproduce
Launch a geographic coverage analysis with many points (around 2700 in ma case). AccessMod Docker 5.7.3 and Docker 3.3.3 on Mac
Detailed Description
While performing a test for a geographic coverage analysis, I wanted to stop the process as it was taking too much time. But even after pressing twice the stop button it continued to process the analysis. I had a confirmation message saying that it would try to stop whenever possible but still continued performing.
I finally stopped the program and relaunched it without problem
The text was updated successfully, but these errors were encountered: