RosettaCommons / RosettaCommons/RFdiffusion
Question on intended bin definitions for L2D Loss in RFDiffusion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 644
- PR merge metrics
- No merged PRs in 30d
Description
I’m working with RFDiffusion and have been comparing the L2D loss described in the Supplementary Information against how it’s computed in RosettaFold2’s publicly available code (for example, in c6d_to_bins2). I noticed that, although both use 37 bins for distances and dihedrals, the supplement defines equal-width bins over 0–18.5 Å (or 2π/37 for angles), whereas the code uses DMIN = 2 Å, DMAX = 20 Å split into 36 uniform bins plus a catch-all bin. The RFDiffusion code‑base uses those same DMIN/DMAX and bin counts, so I wondered if the Supplementary Information might contain a typo. Could you please confirm which scheme is the intended one?
Thank you very much for your time and for sharing your work.
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 by comparing the Supplementary Information with the publicly available RosettaFold2 c6d_to_bins2 implementation and the RFdiffusion code's DMIN/DMAX settings and bin counts. Done means documenting which binning scheme is intended and confirming whether the Supplementary Information contains a typo.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100