- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes GeoMFlow, a multi-frame optical-flow estimator that injects pretrained geometry features (from a frozen VGGT encoder) into the recurrent refinement stage via FiLM-style conditioning, while keeping the original matching pathway untouched. It reports state-of-the-art results on Sintel, KITTI, and Spring, including the top rank on the KITTI online benchmark.
Critical strengths
-
By conditioning only the context branch and leaving the matching pathway and cost volumes completely untouched, the method avoids disturbing the pretrained correspondence representation, and the plug-in stays lightweight and architecture-agnostic. This makes it easy to attach to modern flow estimators with minimal risk, which is a practical merit of the design.
-
Comparing DINOv2, DAv2, and VGGT under an identical backbone and training protocol isolates the effect of the representation source itself, and the same conditioning interface is shown to transfer between a multi-frame and a two-frame architecture.
Critical weaknesses
-
The method is essentially a combination of existing components, that is, VGGT features, align them, and inject them into the context branch with an off-the-shelf FiLM layer. Similar ideas have already been explored by concurrent works like FlowSeek(depth information), so the novelty is not that strong.
-
It's not clear to me why,why,why geometry priors actually help. The paper only argues that flow is the image-plane projection of 3D motion, so geometry features should help, but what specific information do VGGT features actually provide for flow?
There are no probing or visualization experiments, and I honestly don't see the mechanism.
Actually, it's similar to the first question. Why use geometry, model is work?
- In Table 5, the w/o Geo baseline is 0.381 EPE; with geometry added, Full FT only reaches 0.377, while Frz Both jumps to 0.329. This large gain seems to come from the training recipe of "freezing encoders and only training the adaptation ++ refinement modules", not from geometry conditioning itself.
However, the paper never includes a w/o Geo + Frz Both control, so this explanation cannot be ruled out.
Questions for authors
Please answer the question carefully and convince me why geometry is effective?
After reading the entire text, the most memorable thing for me is that geometry is easy to use, but I don't know why or under what circumstances it is easy to use