-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow custom subsampling for each CoregPipeline
step separately.
#137
Comments
I think an easy fix for #135 would be to rename "max_points" by subsample. |
Currently, the The In many cases, including ICP in many programs, subsampling is on by default. So it having subsampling by default is not untrodden ground. |
Good to know for the fraction/count, that's quite useful (if well document, indeed!) |
I will work on it. |
This is not solved by #141! |
True! |
This is now implemented by #436 (forgot to link that old issue)! |
As mentioned by @adehecq in #135,
Deramp
is considerably slower thanNuthKaab
, so subsampling is preferred. However, subsampling does not necessarily need to be done on theNuthKaab
step, so another argument was added. This should be possible in another way, and below is an example:Each
Coreg
approach gets asubsample
(or similar) optional argument which is empty by default.self.fit()
can now accept asubsample
argument which may be a string that says e.g."custom"
, whereby it searches for the subsampling attribute withinself
. This means that one can do something along:Now,
NuthKaab
will run at full resolution, andDeramp
will run at half.It could also be that
subsample
forself.fit
should beNone
by default (which in turn would mean 1.0, unless specified upon instantiation). Then it would just be:The advantage of this approach over the argument added in #135 is that it would work on all
Coreg
subclasses; not justDeramp
.The text was updated successfully, but these errors were encountered: