forked from zju3dv/LoFTR
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
16 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
""" A config only for reproducing the ScanNet evaluation results. | ||
We remove border matches by default, but the originally implemented | ||
`remove_border()` has a bug, leading to only two sides of | ||
all borders are actually removed. However, the [bug fix](https://github.com/zju3dv/LoFTR/commit/e9146c8144dea5f3cbdd98b225f3e147a171c216) | ||
makes the scannet evaluation results worse (auc@10=40.8 => 39.5), which should be | ||
caused by tiny result fluctuation of few image pairs. This config set `BORDER_RM` to 0 | ||
to be consistent with the results in our paper. | ||
""" | ||
|
||
from src.config.default import _CN as cfg | ||
|
||
cfg.LOFTR.MATCH_COARSE.MATCH_TYPE = 'dual_softmax' | ||
|
||
cfg.LOFTR.MATCH_COARSE.BORDER_RM = 0 |
This file contains 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
This file contains 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
This file contains 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