sokrypton / sokrypton/ColabFold
Add a --version argument
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
colabfold_batch --version, colabfold_search --version, colabfold_split_msas --version should all return the version of the release.
Current Behavior
No version returned, no --version argument
Steps to Reproduce (for bugs)
colabfold_search --version
ColabFold Output (for bugs)
$ ./colabfold_search --version
usage: colabfold_search [-h] [-s S] [--db1 DB1] [--db2 DB2] [--db3 DB3] [--use-env {0,1}] [--use-templates {0,1}]
[--filter {0,1}] [--mmseqs MMSEQS] [--expand-eval EXPAND_EVAL] [--align-eval ALIGN_EVAL]
[--diff DIFF] [--qsc QSC] [--max-accept MAX_ACCEPT] [--db-load-mode DB_LOAD_MODE]
[--threads THREADS]
query dbbase base
colabfold_search: error: the following arguments are required: query, dbbase, base
Context
We try to make reproducible workflows. Version stamps are critical to this process.
Your Environment
HPC cluster, slurm
Various linux/unix
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 locating the entry points for colabfold_batch, colabfold_search, and colabfold_split_msas and determine how the release version is defined. Verify that each command accepts --version and returns the release version without requiring its normal positional arguments.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100