-
Notifications
You must be signed in to change notification settings - Fork 7
Conversation
This is the first merge after renaming the upstream branch to Sarek. Lots of changes compared with my previous version.
…better setting when LogR and BAF measurements are based on NGS data
Incorporates recent changes in the documentation of the master project.
Added a specific example of how to run Ascat on GRCh37 on Bianca
Added info about the --containerPaths flag
…le xxxx.cnv.txt that contain the predicted CNV regions. The format of xxxx.cnv.txt is the same, but the change is that all segments are now written out, not only the ones with copy number != 2. This will make it easier to compare the figure xxxx.ASCATprofile with the textfile xxxx.cnv.txt. Now all regions in the figure are included in the text file. I have also updated the documentation to reflect these changes.
small format update
Thanks a lot for the PR. Have you consider updating to a more recent ASCAT version? |
Hi!
Have you consider updating to a more recent ASCAT version?
I noted that there is a new release out (v5.2.5) , so I can test it.
If which cases would we want to change this gamma parameter?
We should always use gamma=1. Other values of gamma should only be used when the input comes from SNP genotyping arrays. Here is an explanation of the gamma parameter from the Ascat documentation:
"The parameter represents the drop in LogR for a change from two copies to one copy in 100% of cells. Gamma theoretically should equal 1, but due to array background signal and bespoke array normalisation procedures, in practice it is often significantly lower. …. For massively parallel sequencing data, gamma should always be set to 1.
Best,
Malin
|
Thanks a lot, that would be marvelous. Did you manage to make some test data so I can set up some test for ASCAT in Sarek? |
Thanks a lot, that would be marvelous.
Did you manage to make some test data so I can set up some test for ASCAT in Sarek?
No, I have not yet done that. When I tried to run Ascat for a small chunk of the genome before, but it didn’t work. Do you think we can use the HCC1143 WGS sample as test data?
The problem is that it takes quite long to run.
Best,
Malin
|
Another update included in this PR (forgot to mention it above): |
The do provide data here for ASCAT: https://github.com/Crick-CancerGenomics/ascat/tree/master/ExampleData <https://github.com/Crick-CancerGenomics/ascat/tree/master/ExampleData>
And also here for Allelecount: https://github.com/cancerit/alleleCount/tree/dev/testData <https://github.com/cancerit/alleleCount/tree/dev/testData>
Maybe we can work something out with that?
I can check what is there. How long time can the test-runs take?
That's good to know, did you add that in the docs?
I added a paragraph about the output files from Ascat in ASCAT.md. But I didn't write out specifically that all segments are included since this is the "default output format" from Ascat.
… —
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#628 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADGC5aZ8NsKSfuDqYy8ngdBp98lmcO52ks5uV-NqgaJpZM4WTTMo>.
---------------------------------------------------------------------
Malin Larsson, PhD
National Bioinformatics Infrastrucrure Sweden
SciLifeLab Bioinformatics Long-term Support (WABI)
Department of Physics, Chemistry and Biology
House B, Room 2B:586, Campus Valla
581 83 Linköping
Telephone: 070-3276037
E-mail: malin.larsson@scilifelab.se
---------------------------------------------------------------------
|
Typically less than 40 min for a test.
But since this is now the default output format, it could be good to update the docs accordingly and specify that as well, no? |
So in our case, it would be from bams to ascat results, as we can't cut it in more pieces.
OK. I have to check if that is possible. Perhaps if we generate a really “shallow” bam file for the full genome.
But I didn't write out specifically that all segments are included since this is the "default output format" from Ascat.
But since this is now the default output format, it could be good to update the docs accordingly and specify that as well, no?
Yes, I can ad a note on this.
… —
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#628 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADGC5ekKgEe3zgoeW5V1ej52QnEIIWvIks5uV_iugaJpZM4WTTMo>.
---------------------------------------------------------------------
Malin Larsson, PhD
National Bioinformatics Infrastrucrure Sweden
SciLifeLab Bioinformatics Long-term Support (WABI)
Department of Physics, Chemistry and Biology
House B, Room 2B:586, Campus Valla
581 83 Linköping
Telephone: 070-3276037
E-mail: malin.larsson@scilifelab.se
---------------------------------------------------------------------
|
You don't have to do that with this PR, don't worry too much about it.
That would be perfect. |
More detailed description of the tumor.cnvs.txt file to explain that all segments are included in the file, also those with normal copy number.
OK. I have to check if that is possible. Perhaps if we generate a really “shallow” bam file for the full genome
You don't have to do that with this PR, don't worry too much about it.
OK, perhaps when updating Ascat then.
Yes, I can ad a note on this.
That would be perfect
I have updated my ASCAT.md file with this info. Do I need to create a new PR?
|
Release 2.2.2
…operly defined in genomes.config
@malinlarsson |
update of the documentation of how GC correction files were created
small updates
This PR now includes GC correction for Ascat. The process has been documented in docs/ASCAT.md, including how the GC correction files were generated. Still to do: Update to Ascat 2.5.2, but can we do that in a separate PR? |
Update of the Ascat process:
In bin/run_ascat.r, in the call to ascat.runAscat() the parameter gamma is set to 1. Gamma was previously not set, which means that the default value 0.55 was used. Gamma =1 is recommended when running Ascat on NGS data (please see https://www.crick.ac.uk/research/labs/peter-van-loo/software). The documentation of Ascat is updated accordingly.
The documentation of INSTALL_BIANCA.md was updated with some information that I learned during my own installation.
PR checklist
./scripts/test.sh -p docker -t ALL
).docs
is updatedCHANGELOG.md
is updatedREADME.md
is updatedLearn more about contributing: https://github.com/SciLifeLab/Sarek/blob/master/.github/CONTRIBUTING.md