-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Intuitive file/input names #73
Conversation
Layth17
commented
Oct 27, 2022
•
edited
Loading
edited
- syntax check
- functionality check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! I especially like that the one input is no longer called file
.
@@ -182,7 +182,9 @@ task hlaConsensus { | |||
|
|||
#Create an exact copy of optitype calls, to be bundled with other relevant | |||
#files for convenience/later review. Always generated, | |||
with open("hla_calls/optitype_calls.txt", "w") as o_c: | |||
#NOTE(Layth): this hla_consensus step actually gets passed results from | |||
#Optitype for class I and PHLAT for class II. hla_calls will include both results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be nice to follow up on this tool and fix some of the existing comments (and the variable name?) to reflect its true contents.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 🪄