Giter Club home page Giter Club logo

Comments (3)

vigneshrajap avatar vigneshrajap commented on August 14, 2024 2

But is it not being reset inside the RANSAC loop, due to where it is placed? The } that ends the RANSAC for loop is placed right below best_no_inliers, so at every iteration, it is reset to 0 instead of keeping the previous best value.

Yes you are right. I just got lucky then 😃

from poly_nav.

jorgemiar avatar jorgemiar commented on August 14, 2024 1

The idea of that function is to find "two lines" using RANSAC, so I repeat the whole k (100) iterations of RANSAC two times if you notice. You see "both_lines_found" parameter.

Yes, got that.

About "best_no_inliers" part, it is reset to zero outside the loop for detecting the best fit of the second line.

But is it not being reset inside the RANSAC loop, due to where it is placed? The } that ends the RANSAC for loop is placed right below best_no_inliers, so at every iteration, it is reset to 0 instead of keeping the previous best value.

Overall, follow the "jfr" branch. That's the last time, the code was used. The code is quite brute forced and can be improved a lot. I guess you managed to got the core idea of this code. You can improve it by reducing the parameters that are introduced to obtain this particular pattern. Good luck.

Alright thanks!!

from poly_nav.

vigneshrajap avatar vigneshrajap commented on August 14, 2024

The idea of that function is to find "two lines" using RANSAC, so I repeat the whole k (100) iterations of RANSAC two times if you notice. You see "both_lines_found" parameter.

About "best_no_inliers" part, it is reset to zero outside the loop for detecting the best fit of the second line.

That's true, scan points are the same for every ransac loop. But it is reset to zero for estimating one more line otherwise "scan_pts_index_array" will run out of memory and create segmentation fault.

I see that scan points into X,Y and theta is the same for detecting both lines. They can be done only one time somehow. Then "s_pt" is not needed.

Overall, follow the "jfr" branch. That's the last time, the code was used. The code is quite brute forced and can be improved a lot. I guess you managed to got the core idea of this code. You can improve it by reducing the parameters that are introduced to obtain this particular pattern. Good luck.

from poly_nav.

Related Issues (1)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.