Cy

Seems like bugs come from the `input.2` file (not exised) that parsed to report markdown parameter `blast_gff`. Sorry I don't know how to fixed this problem for now, due to...

I try to change the CUSTOME_DATDABASE_REPORT process input, `CUSTOM_DATABASE.out.gff` instead of `MERGED_ANNOTATION.out.gff`, and it works out, though not sure whether it is a proper solution. ``` # bacannot/workflows/bacannot.nf 297 //...

> Hi @lam-c , > > For the `REPORT` module, I think now I've fixed on your branch, which has the PR opened, the gff channel that is given as...

> Hi @lam-c , > > For the `REPORT` module, I think now I've fixed on your branch, which has the PR opened, the gff channel that is given as...

@fmalmeida Sorry I might mix the branches when running the test. The reports meet demand, and I will use the pr branch to run local analysis. Thanks again!

Thank you all for your patience and elaboration, that really helps a lot. Also, the entry point at binning stage #439 also fits my need.