Daniel Cameron
Daniel Cameron
If I use the run instructions in the README instead of cmd I get: ``` $ Weaver PLOIDY -f SIMU.fa -S FINAL_SV -s SNP -g REGION -w X.bam.wig -r 0...
I then thought that maybe you weren't raising any error messages if the input files specified did not exist. Rerunning in the INPUT directory results in: ``` $ Weaver PLOIDY...
Changing `-r 0` to `-r 1` as recommended in https://github.com/ma-compbio/Weaver/issues/11 results in: ``` $ Weaver PLOIDY -f SIMU.fa -S FINAL_SV -s SNP -g REGION -w X.bam.wig -r 1 -m map100mer.bd...
Uncommenting main.cpp:250 indicates that BIN is set to an empty string
I think we can get away without any left/right normalisation because we can directly report the entire intervals. E.g. the example above would be represented as: ``` breakpoint: { breakends:...
> Let us clarify the run case of Weaver; Weaver does not directly use a matched normal. So to clarify: when the weaver paper states ` If there is matched...
Would running `Weaver PLOIDY` on the tumour and normal separately then running `Weaver LITE` on a merged bam and passing it coverage estimates equal to the sum of the T...
What's the current state of this? Does the API now support multi-threading? Even just multithreading support for reading would be immensely useful. Thanks
Has there been any progress on this? The example supplied with weaver isn't complete and many of the files are pre-computed. Is it possible to supply a wrapper shell script...