why not plant?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- jupyter-notebook, python
- Domain
- bioinformatics, machine-learning
Research direction
The issue names no files, tests, or entry points. First clarify what “plant BGCs prediction” should cover and whether it requests a new capability or reports missing support; then identify the existing prediction workflow and define plant-specific acceptance criteria before estimating implementation.
Written by the indexing model from the issue text.
Description
plant BGCs prediction
- Dominant language
- Jupyter Notebook
- Stars
- 161
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
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.
More from Merck/deepbgc
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
installing deepbgc Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
EBI-Metagenomics/mgnifams#62 ·
-
Difficulty 2/5 Half a day Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100