Currently the scheduler does not allow cancelling algorithms that are
running. This is really important especially in the case of algorithms that
perform several long-running sub-tasks. For example, the path finder
network scaling algorithm basically computes successively higher order
weighting matrices and takes a very long time to run (one user reported
that it ran for 2 hours on a 2000 node network). In such a case, suppose
the user realizes that the algorithm has been given the wrong parameter,
there is no way to stop the algorithm other than stop IVC!
Although stopping threads is not possible in Java, at the very least, we
should probably provide an indication to every algorithm that the user has
requested stopping the algorithm. Not all algorithms will comply with this
request (some may not be able to comply), but at least we will have the
least we can.
Log in to post a comment.
