Skip to content
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.

add-lancet-vardict-ngscheck-links-clin-harm #44

Merged
merged 12 commits into from
Sep 23, 2019
Merged

Conversation

jharenza
Copy link
Collaborator

Purpose

Briefly describe your changes here.
Add methods for:
-Lancet
-Vardict
-NGSCheckmate
-Clinical data harmonization (disease types, MB subtyping, OS)
-Add links to D3b github workflows

Issue

What GitHub issue does your pull request address?

Pull review checklist

The PR will be considered ready for review when all four items have been checked.

Add methods for:
-Lancet
-Vardict
-NGSCheckmate
-Clinical data harmonization (disease types, MB subtyping, OS)
-Add links to D3b github workflows
add VCF filtering for mutect/strelka; fix capitalizations
Copy link
Collaborator

@cgreene cgreene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few thoughts - thanks for filling in these sections!

Copy link
Member

@jaclyn-taroni jaclyn-taroni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a few additional comments, thanks @jharenza!

Jo Lynne Rokita and others added 2 commits September 23, 2019 08:47
commit suggestions from @cgreene
fix capitalization

Co-Authored-By: Casey Greene <cgreene@users.noreply.github.com>
@jaclyn-taroni
Copy link
Member

@jharenza looks like an empty .Rhistory file snuck in with 6262e9d

Jo Lynne and others added 3 commits September 23, 2019 09:00
Co-Authored-By: Jaclyn Taroni <jaclyn.n.taroni@gmail.com>
Co-Authored-By: Jaclyn Taroni <jaclyn.n.taroni@gmail.com>
@jharenza
Copy link
Collaborator Author

@jharenza looks like an empty .Rhistory file snuck in with 6262e9d

deleted

Jo Lynne Rokita added 2 commits September 23, 2019 09:07
As an FYI - we expect this information to continually grow over time as we learn more about each of the subtypes. Information from AlexsLemonade/OpenPBTA-analysis#19 should go into this column.
add parameter change reasoning
@jharenza
Copy link
Collaborator Author

@cansav09 - sorry I think I lost your comments when I committed. To answer your questions - I am going to work with @yuankunzhu and @migbro to make the BED files available. For WGS, BED regions were only used in Lancet (so it would not run forever). So we will get one BED file for WXS/Panel, which was used for all variant callers for that data type, then one BED for WGS Lancet. This could be used for TMB in the cases where the BEDs were used.

@cansavvy
Copy link
Collaborator

@cansav09 - sorry I think I lost your comments when I committed. To answer your questions - I am going to work with @yuankunzhu and @migbro to make the BED files available. For WGS, BED regions were only used in Lancet (so it would not run forever). So we will get one BED file for WXS/Panel, which was used for all variant callers for that data type, then one BED for WGS Lancet. This could be used for TMB in the cases where the BEDs were used.

Sounds great! I will continue using the BED file I have then as a placeholder and then once those are ready, switch that in.

@jharenza
Copy link
Collaborator Author

@cansav09 - sorry I think I lost your comments when I committed. To answer your questions - I am going to work with @yuankunzhu and @migbro to make the BED files available. For WGS, BED regions were only used in Lancet (so it would not run forever). So we will get one BED file for WXS/Panel, which was used for all variant callers for that data type, then one BED for WGS Lancet. This could be used for TMB in the cases where the BEDs were used.

Sounds great! I will continue using the BED file I have then as a placeholder and then once those are ready, switch that in.

OK - I am going to try to have these in the V5 release for tomorrow :)

@jaclyn-taroni
Copy link
Member

I believe the only outstanding thing is this comment from @cgreene (#44 (comment)):

Are you looking at common variants across the population here? If so, I think that's the point to use polymorphism. Otherwise, I think variant is probably preferred. It wasn't clear to me that this was a point where the subject was focused on common variants. Maybe this means that SNP is still preferred but the sentence could be revised for clarity.

Provided @cgreene is satisfied with the disease type section

@jharenza
Copy link
Collaborator Author

I believe the only outstanding thing is this comment from @cgreene (#44 (comment)):

Are you looking at common variants across the population here? If so, I think that's the point to use polymorphism. Otherwise, I think variant is probably preferred. It wasn't clear to me that this was a point where the subject was focused on common variants. Maybe this means that SNP is still preferred but the sentence could be revised for clarity.

Provided @cgreene is satisfied with the disease type section

Yes, the way that many of the matching algorithms work are by looking at common, yet discriminatory SNPs within individuals (short of STR-typing).

@cgreene
Copy link
Collaborator

cgreene commented Sep 23, 2019

I am satisfied with disease type section.

It's still not entirely clear to me that you want polymorphism there. Are you only calling variants that are common in the population here?

@jharenza
Copy link
Collaborator Author

I am satisfied with disease type section.

It's still not entirely clear to me that you want polymorphism there. Are you only calling variants that are common in the population here?

Yes, we only use common SNPs here (similar to the days pre-STR for genotyping) - I will update the text.

Also, I will add some RNA QC.

Jo Lynne Rokita added 2 commits September 23, 2019 11:29
add RNA-Seq QC, clarify SNP information used in NGScheckmate
remove extra line 76
@jharenza
Copy link
Collaborator Author

I am satisfied with disease type section.
It's still not entirely clear to me that you want polymorphism there. Are you only calling variants that are common in the population here?

Yes, we only use common SNPs here (similar to the days pre-STR for genotyping) - I will update the text.

Also, I will add some RNA QC.

@cgreene I have updated this section - do you want to check?

This was referenced Sep 23, 2019
Copy link
Collaborator

@cgreene cgreene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@jharenza jharenza mentioned this pull request Sep 23, 2019
@jharenza jharenza merged commit 4e0099d into master Sep 23, 2019
@jharenza jharenza deleted the update-methods branch September 23, 2019 15:48
cgreene pushed a commit that referenced this pull request Sep 23, 2019
This build is based on
4e0099d.

This commit was created by the following Travis CI build and job:
https://travis-ci.com/AlexsLemonade/OpenPBTA-manuscript/builds/128774951
https://travis-ci.com/AlexsLemonade/OpenPBTA-manuscript/jobs/238231213

[ci skip]

The full commit message that triggered this build is copied below:

Merge pull request #44 from AlexsLemonade/update-methods

add-lancet-vardict-ngscheck-links-clin-harm
cgreene pushed a commit that referenced this pull request Sep 23, 2019
This build is based on
4e0099d.

This commit was created by the following Travis CI build and job:
https://travis-ci.com/AlexsLemonade/OpenPBTA-manuscript/builds/128774951
https://travis-ci.com/AlexsLemonade/OpenPBTA-manuscript/jobs/238231213

[ci skip]

The full commit message that triggered this build is copied below:

Merge pull request #44 from AlexsLemonade/update-methods

add-lancet-vardict-ngscheck-links-clin-harm
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants