CRITICAL BUG: 'rna_fragments.dat' is missing from ALL installation methods (Conda, Binaries, Git Clone/LFS, SCons)

[RogerioBioII]

Hello Rosetta Team,

I am unable to get a working installation of Rosetta because the critical file rna_fragments.dat seems to be missing from all public distribution channels. This file is required to run the rna_denovo application.

After extensive troubleshooting, I have confirmed the file is missing from every possible installation method:

Official Binary Releases (v3.14): Both the Ubuntu and Linux binary packages were extracted, and a find command confirms rna_fragments.dat is not included.

Official Conda Package: conda install rosetta completes, but a find command within the environment confirms rna_fragments.dat is not in the database.

Git Clone from Source: git clone of the repository followed by git lfs pull fails silently (the pull command does nothing and downloads no LFS objects). A recursive search of the repository confirms that there is no .gitattributes file, so LFS may not be in use.

SCons Build System: Running ./scons.py database fails with the error: scons: *** Do not know how to make File target 'database'. This shows the build system itself cannot fetch the database.

Conclusion: There appears to be no working public method for a new user to obtain the necessary files to run rna_denovo.

Could you please advise on the correct, functional procedure to obtain a complete Rosetta installation with the full database?

Thank you.

[roccomoretti]

To clarify, where are you getting the information that "rna_fragments.dat" is required to run rna_denovo? From what I can tell, the rna_denovo application uses the file 1jj2.torsions for fragments by default, not rna_fragments.dat. (There is a note about using alternative torsion sets, but that doesn't mention "rna_fragments.dat".) I also cannot seem to find any reference in the code to rna_fragments.dat, and it's absent from a Google search as well.

To help debug this, could you provide A) the exact text (copy&paste) of any error message you're getting B) the full command line of what you're running when you get the error and C) where you got that command line from.