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

Updates to CrosscheckFingerprints documentation. #1520

Closed
wants to merge 1 commit into from

Conversation

samuelklee
Copy link
Contributor

@samuelklee samuelklee commented May 29, 2020

Changes comments on the fields in the CrosscheckMetric class to Javadoc, in response to https://gatk.broadinstitute.org/hc/en-us/community/posts/360058443032-Interpretting-CrosscheckFingerprints-metrics and subsequent discussion on Slack.

Reviewers can use this PR to add additional documentation and updates, if desired.


Checklist (never delete this)

Never delete this, it is our record that procedure was followed. If you find that for whatever reason one of the checklist points doesn't apply to your PR, you can leave it unchecked but please add an explanation below.

Content

  • Added or modified tests to cover changes and any new functionality
  • Edited the README / documentation (if applicable)
  • All tests passing on Travis

Review

  • Final thumbs-up from reviewer
  • Rebase, squash and reword as applicable

For more detailed guidelines, see https://github.com/broadinstitute/picard/wiki/Guidelines-for-pull-requests

@@ -78,23 +78,23 @@
* and sample for VCF files) and then optionally aggregates it by library, sample or file, to increase power and provide
* results at the desired resolution. Output is in a "Moltenized" format, one row per comparison. The results will
* be emitted into a metric file for the class {@link CrosscheckMetric}.
* In this format the output will include the LOD score and also tumor-aware LOD score which can
* help assess identity even in the presence of a severe loss of heterozygosity with high purity (which could
* In this format, the output will include both the LOD score and the tumor-aware LOD score; the latter can
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We may want to expand upon this documentation, I just fixed up a few typos I noticed. I also found it confusing that this text was mostly---but not faithfully---reproduced in the tool summary (and hence did not fix the corresponding typos there).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

One other comment while I'm here---"moltenize/d" is a very idiosyncratic term to describe this type of table reshaping. Why not just "molten/melted"?

Copy link
Contributor

Choose a reason for hiding this comment

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

I have no strong feelings about moltenized....if you think that "molten" is more clear, go for it!

@@ -59,51 +59,54 @@ public Boolean isMatch() {
}
}

/** The data type. */
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These descriptions should probably be expanded, I just changed them to Javadoc and fixed up a few LEFT vs. RIGHT typos.

Copy link
Contributor

@yfarjoun yfarjoun left a comment

Choose a reason for hiding this comment

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

looks good. thanks!

@@ -78,23 +78,23 @@
* and sample for VCF files) and then optionally aggregates it by library, sample or file, to increase power and provide
* results at the desired resolution. Output is in a "Moltenized" format, one row per comparison. The results will
* be emitted into a metric file for the class {@link CrosscheckMetric}.
* In this format the output will include the LOD score and also tumor-aware LOD score which can
* help assess identity even in the presence of a severe loss of heterozygosity with high purity (which could
* In this format, the output will include both the LOD score and the tumor-aware LOD score; the latter can
Copy link
Contributor

Choose a reason for hiding this comment

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

I have no strong feelings about moltenized....if you think that "molten" is more clear, go for it!

@samuelklee
Copy link
Contributor Author

Thanks @yfarjoun! As discussed on Slack with Comms, they’ll take over this PR and use it to address the above comments and make further changes.

@derekca
Copy link
Contributor

derekca commented Jul 28, 2020

Hi @yfarjoun, I've made a few clarifying revisions to the intro — CrosscheckFingerprints_Revised

Please take a look and incorporate them as appropriate.

@yfarjoun
Copy link
Contributor

yfarjoun commented Aug 11, 2020 via email

@kbergin
Copy link
Contributor

kbergin commented Feb 22, 2021

Hi @derekca - would you be able to incorporate your suggested wording into this PR? Going through open Picard PRs and hoping to get them merged in :)

@derekca
Copy link
Contributor

derekca commented Feb 26, 2021

@kbergin Just found out about this now... I never got pinged for these responses for some reason.

I either do not have the correct permissions, or am not familiar enough with git, to be able to incorporate these changes to the doc.

@kbergin
Copy link
Contributor

kbergin commented Feb 26, 2021

@samuelklee would you be able to incorporate the changes that Derek linked above and close out this PR?

@gbggrant
Copy link
Contributor

Hi @samuelklee I'm assigning this back to you as it seems to have stalled out.

@samuelklee
Copy link
Contributor Author

Apologies @gbggrant, I should've noted here that User Ed is on this, as was decided on the gatk-userliaison Slack.

I'm probably not actually familiar enough with the tool to make detailed changes or provide a review---I originally opened the PR to help get the ball rolling in response to some discussions I happened to see on Slack and the GATK Forum. I made some obvious changes and fixed some typos, but I think @derekca or someone else more qualified than me will have to bring this home!

@samuelklee samuelklee removed their assignment Mar 18, 2021
@jessicaway
Copy link
Member

@knoblett Has the User Ed team has had a chance to look at this?

@gbggrant
Copy link
Contributor

@samuelklee is there anything holding this PR up from being merged? It's been waiting a while.

@gbggrant gbggrant assigned gbggrant and unassigned knoblett and derekca May 27, 2021
@samuelklee
Copy link
Contributor Author

samuelklee commented Jun 1, 2021

@gbggrant sorry, just seeing your mention after the long weekend. Just wanted to note that this PR was never completed, to my knowledge. As stated a few times above, I made some cursory fixes to get the ball rolling but handed things over to User Ed to finish up. It looks like @derekca came up with some additional changes in #1520 (comment) that were never incorporated.

@gbggrant
Copy link
Contributor

gbggrant commented Sep 1, 2021

@samuelklee can you and @derekca work to get the updated documentation integrated into this PR? I have tried reading the text file provided in the comment above, but it is in a very different format than used in the picard comment and usage statement.

@gbggrant gbggrant assigned samuelklee and derekca and unassigned gbggrant and samuelklee Sep 1, 2021
@samuelklee
Copy link
Contributor Author

samuelklee commented Sep 1, 2021

@gbggrant thanks for making sure this doesn’t fall through the cracks! Unfortunately, my position is still the same as in #1520 (comment) (and I’m also currently on vacation!) User Ed, somebody more familiar with the tool, or anyone else with the bandwidth to review and incorporate the changes in the text file should bring this home.

Again, I only opened this PR as a courtesy with the understanding that others would close it out—no good deed, I suppose! If no one else cares to finish it up, then feel free to close it. Seems a bit of shame to miss a chance to improve documentation, but it’s no skin off my back.

EDIT: see https://broadinstitute.slack.com/archives/CDNPV40AK/p1614274505007300, https://broadinstitute.slack.com/archives/CDNPV40AK/p1590778639131700, https://broadinstitute.slack.com/archives/CDNPV40AK/p1584385024062800, and contemporaneous messages for more context.

@samuelklee samuelklee removed their assignment Sep 1, 2021
@samuelklee
Copy link
Contributor Author

samuelklee commented Sep 13, 2021

@bhanugandham could I possibly recruit you to reassign or otherwise shepherd this PR?

I'm assuming the edits suggested above by @derekca are good and are an improvement over any typo fixes I might've introduced above. The only nitpick I have upon skimming is that I still think we should still use the standard "molten" to refer to the dataframe melt operation, instead of the rather idiosyncratic "moltenized" (which has <500 hits on Google!)

Can you find someone to incorporate those edits along with the changes I've made to the code? I think you should just be able to add onto this PR, but feel free to copy the branch and open another if needed.

I'm fine with punting on additional changes to the Javadoc, although as commented above I think they could bear expansion.

@derekca
Copy link
Contributor

derekca commented Sep 15, 2021

I'm assuming the edits suggested above by @derekca are good and are an improvement over any typo fixes I might've introduced above. The only nitpick I have upon skimming is that I still think we should still use the standard "molten" to refer to the dataframe melt operation, instead of the rather idiosyncratic "moltenized" (which has <500 hits on Google!)

Thanks for the input, I've fixed the comment about molten outputs in the new version.

I've gone ahead and created a separate pull request, 1721, for revising the introduction to this doc.

@samuelklee samuelklee force-pushed the sl_crosscheckfingerprints_docs branch from 23d9d66 to 68f779a Compare September 16, 2021 00:31
@samuelklee
Copy link
Contributor Author

samuelklee commented Sep 16, 2021

Great, thanks @derekca! @gbggrant I've rebased and will wait for tests to pass again before merging. Perhaps then @derekca can resolve any conflicts over in his PR and merge afterwards.

EDIT: Wait, nevermind---I see that @derekca incorporated my changes as well over there. In which case, feel free to close this copy or do what you will with it, whenever you like!

@bhanugandham
Copy link
Contributor

@samuelklee and @gbggrant I apologize i didn't see the comments. I was on vacation the last week and a half and just got back today. Looks like @derekca has taken care of this? Please let me know if there is anything else i can help with. Sorry again for the delay!

@samuelklee
Copy link
Contributor Author

No worries, @bhanugandham. Sorry, didn’t realize you were off! I think @derekca is on top of the other PR. Not sure who will review, but I’ll leave that up to you all. Thanks again to both of you!

@bhanugandham
Copy link
Contributor

Sounds good! Thanks Sam!

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

Successfully merging this pull request may close these issues.

8 participants