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

comp_report finds errors to be fixed in GAMBLR.data and GAMBLR.results #8

Closed
vladimirsouza opened this issue Oct 31, 2023 · 2 comments

Comments

@vladimirsouza
Copy link
Contributor

vladimirsouza commented Oct 31, 2023

This bug happens when GAMBLR.data is loaded.

library(GAMBLR.datra)
> comp_report(this_sample = "HTMCP-01-06-00422-01A-01D",
+                   out = "reports/",
+                   export_individual_plots = TRUE)
Using the bundled CN segments (.seg) calls in GAMBLR.data...
Error:  You have given one or more unsupported or deprecated argument to  assign_cn_to_ssm . Please check the documentation and spelling of your arguments.
Offending argument(s): from_flatfile,use_augmented_maf
@vladimirsouza
Copy link
Contributor Author

There is another error when GAMBLR.results is loaded.

>       comp_report(this_sample = "HTMCP-01-06-00422-01A-01D",
+                    out = "reports/",
+                    export_individual_plots = TRUE)
                                                                                                                   
Error in get_sample_wildcards(this_sample_id, seq_type) :                                                          
  object 'seq_type' not found
In addition: Warning message:
In if (tissue_status_filter == "normal") { :
  the condition has length > 1 and only the first element will be used

@vladimirsouza vladimirsouza changed the title fancy_v_count can't internally run assign_cn_to_ssm comp_report finds errors to be fixed in GAMBLR.data and GAMBLR.results Oct 31, 2023
@mattssca
Copy link
Contributor

Thanks for reporting this. I can have a look at this and propose a fix.

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

2 participants