Hi @xtanh ,
Thank you for making unistab available to the community.
However, I had to go through 'compiler hell', 'dependency puzzles' and model architecture traps to finally have it installed.
The major pain points are:
- The current dependency stack (Python 3.7 / PT 1.12) creates significant friction on modern RTX 40-series hardware;
- The mandatory compilation of OpenFold CUDA kernels is brittle;
- the software should provide a seamless fallback to native PyTorch operators if C++ extensions fail to compile;
- Furthermore, the strict key-checking in the model loader makes it nearly impossible to perform lightweight environment fixes without triggering a
RuntimeError
To enhance the accessibility of UniStab for the structural biology community, I highly recommend transitioning to a Container-first distribution (Docker/Singularity). Additionally, implementing a native PyTorch fallback for the OpenFold kernels would significantly reduce the high entry barrier caused by C++ compilation errors on modern HPC environments.
Best -- Joanet
Hi @xtanh ,
Thank you for making unistab available to the community.
However, I had to go through 'compiler hell', 'dependency puzzles' and model architecture traps to finally have it installed.
The major pain points are:
RuntimeErrorTo enhance the accessibility of UniStab for the structural biology community, I highly recommend transitioning to a Container-first distribution (Docker/Singularity). Additionally, implementing a native PyTorch fallback for the OpenFold kernels would significantly reduce the high entry barrier caused by C++ compilation errors on modern HPC environments.
Best -- Joanet