sokrypton / sokrypton/ColabFold
Maximal input size reduction between 1.5.2 and 1.5.5
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 2.9k
- Forks
- 747
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
The same input on the same hardware that fit into memory on an older version of ColabFold will still run on newer versions.
Current Behavior
On 1.5.2 a 4644 AA input ran fine but 1.5.5 runs out of memory, even after truncating to 4484 AA.
Steps to Reproduce
- Install ColabFold 1.5.2 (3564546) via LocalColabFold.
- Download this input and run as follows.
CUDA_VISIBLE_DEVICES=1 nohup colabfold_batch --templates --amber *.fasta . >&/dev/null &
- Install ColabFold as above. This results in 1.5.5 9a5c316.
- Run the same input as above.
I am unable to reproduce step 1.
I have also tried running 1.5.5 with a truncated input to no avail.
ColabFold Output
Context
I am running on GPU 1 because 0 is usually occupied. I used nvidia-smi to ensure no other processes were running on the GPU .
Environment
Server specifications
NVIDIA GeForce RTX 4090 video card running driver version 530.30.02 and CUDA 12.1.
Operating system and version
Ubuntu 22.04.3 LTS
Contributor guide
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 linked log.txt outputs for versions 1.5.2 and 1.5.5, then run the documented colabfold_batch command with the linked FASTA inputs on the stated RTX 4090 environment. Trace the change between commits 3564546 and 9a5c316 that affects memory use. Done means identifying the regression and confirming that the original input runs within the earlier memory limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- bioinformatics, machine-learning, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100