What's the radius of sharpness in your code corresponds to the F1 score in MoGe-2?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thanks for this great work. MoGe-2 reports promising F1-score in the paper, but I found that there exist three boundary F1 score in your code:
Does the F1-score in MoGe-2 represents the average of "radius1_f1", "radius2_f1", "radius3_f1", or it represents either of them?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with moge/test/metrics.py lines 328-333 and inspect how radius1_f1, radius2_f1, and radius3_f1 are computed and reported. Compare those outputs with the F1-score definition and results described for MoGe-2 in the paper. Done means identifying which metric, or aggregation of metrics, corresponds to the reported score and recording that clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100