Feature/l1c matching l0 #31
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… other keypoints detectors such as SuperGlue could be then added. I just put SIFT as first example that is ready to use
This reverts commit 0643982.
lucamarini22
force-pushed
the
feature/l1c_matching_l0
branch
from
0643982 to
ee83696
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! :)
I added the method
register_l1_to_rawinL1C_eventclass to perform image registration of the L1C to the Raw granule and I also added an example of using it in thepyraws_Raw_API_demonstration.ipynbnotebook.register_l1_to_rawwithout making it dependent to a keypoint detection algorithm, so the user can choose the keypoint detector that prefers.