Bugs for protein input

Open
#90 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Reproduce the issue using the --protein input and the GBK file produced by deepbgc prepare, then inspect the generated .bgc.tsv output. Done means the protein_ids, bio_pfam_ids, and pfam_ids fields are populated when valid protein input is supplied.

Written by the indexing model from the issue text.

Description

@prihoda Hi! I may find a bug that:

The output file (*.bgc.tsv) does not have "protein_ids bio_pfam_ids pfam_ids" (empyt), no matter use protein file (--protein ) or change the protein file into gbk file (deepbgc prepare).

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Merck/deepbgc

All issues in Merck/deepbgc

Similar issues

More Bioinformatics issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.