Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Error in rule bigslice" and "Macro Syntax Error" for bigscape output report #370

Open
alpole23 opened this issue Feb 20, 2025 · 0 comments

Comments

@alpole23
Copy link

Hi Devs,

Question regarding some output errors for bigscape and bigslice.
I am running a bgc analysis of a small group of custom genbank genome files with the following rules:

  seqfu: TRUE
  mash: TRUE
  fastani: TRUE
  checkm: TRUE
  antismash: TRUE
  query-bigslice: TRUE
  bigscape: TRUE
  bigslice: TRUE
  automlst-wrapper: FALSE
  arts: FALSE
  roary: FALSE
  cblaster-genome: FALSE
  cblaster-bgc: FALSE
  gtdbtk: FALSE 

All of the workflows function fine except for bigscape and bigslice. I have attached a snippet from the snakemake log file as well as the log file from the ./logs/bigscape/bgc_genomes_antismash_7.1.0/ log folder. I also attached the snakemake log file of the report build.

bigscape.log

snakemake_log_bigscape_snippet.txt

snakemake_report_build_log.txt

After building the reports and serving them up, there is a "Macro Syntax Error" for the bigscape tab shown in the screen capture below.

Image

Aside from the bigscape error, I also encountered an unrelated error with bigslice. Logs are below.

snakemake_log_bigslice_snippet.txt

Any help on a resolution for these errors would be greatly appreciated and let me know if you need more information. Thanks!

@alpole23 alpole23 changed the title "Error in rule bigslice" and _"Macro Syntax Error"_ for bigscape output report "Error in rule bigslice" and "Macro Syntax Error" for bigscape output report Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant