algo | Nyah Check , and it 's the Golang implementation | Learning library

So I use another library to solve this problem: OpenCV-python

We got have also the detection of segments( which are not disjoint) but with a hierarchy with the function findContours. The hierarchy is useful since the function detects different polygons. This implies no problems of connections we could have with the other method like explain in the post

It seems like there are threading issues. The long-running task could be blocking the UI during its calculations.

How about trying the exhaustive algorithm on the background and updating the UI (progressbar in this case) when the calculation is complete from the background?

You can use the popular Kotlin-Coroutine to achieve this.

You can copy-paste try it:

Change your timer function to

As rightly pointed out by @Alexander Petrov , you are declaring a table type with name dbo.filters

I am seeking an intuitive explanation for setting hi=mid (specifically with the while loop condition as lo and not lo<=hi). I think we should set it as hi=mid-1, since we know that mid cannot contain our answer (if it did, then we would have already returned).

There are two main potential issues here:

1. Correctness. Does the function terminate, returning the correct answer, for all inputs?

   • with hi=mid, yes. For this, we can observe that when the loop condition lo holds, mid is always strictly less than hi but not less than lo, therefore setting mid=hi reduces the search interval. We can also observe that when that alternative is exercised, the target value must be in the reduced interval if it is present at all. Since the search space is finite and is reduced at every iteration, the computation must eventually reach an interval size of 1 (and therefore terminate) if it does not find the target sooner.

   • with hi=mid-1, also yes. The argument is the same, but it is worth noting that it can be the case that mid == lo, which yields the possibility that hi would be set less than lo. That does not present a practical problem as the function is written, but it is a bit untidy.

2. Efficiency. Could the function arrive at the correct result in fewer steps?

   Using hi=mid-1 does not make the function asymptotically faster. It is O(log n) either way. Moreover, on any given problem, the two alternatives will test different sequences of values, so either alternative might happen to complete in fewer cycles than the other when the target value is present. Intuition suggests that shrinking the search interval that little bit more would be a slight win on average, especially in the case where the target value is not present, but that gain is proportionally insignificant except for in the cycles where the interval is already pretty small.

I am trying to intuitively understand how the search space reduces while developing the logic (before getting to coding) so that I can come up with a concrete algo that can work on all examples.

Either alternative works, and there is no reason to expect a noticeable speed difference. It comes down, then, to style and personal sensibility. Myself, I prefer hi=mid in this case so as to avoid ever producing a situation where hi < lo. Others might prefer hi=mid-1 for symmetry.

Side note: one cannot, on the other hand, change from lo=mid+1 to lo=mid. Because it is possible for mid=lo+(hi-lo)/2 to result in mid==lo, one needs the lo=mid+1 alternative to ensure that the interval shrinks on every cycle.

digest is not vectorized, you need to apply it for each value separately which can be achieved with rowwise.

First of all, you have too much inline code going on, this is a bad practice. Avoid using inline style when possible. So instead of changing style.display, add/remove a class or an attribute that would do the style changes within CSS, this way you can eliminate the need of loop through elements to change all their styles.

Just a quick and dirty example of what I mean:

Ok I figured it out and for the good of humanity I think I'll post my solution! Complete with sorting params.

I was using a GET instead of a POST and I totally forgot to reinject the hash into the "req" object after it was calculated (and other minor things). Anyway, several hours of tearing out my hair, so you don't have to, you get this:

You may try this rewrite rule: