-
Notifications
You must be signed in to change notification settings - Fork 0
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
docs: add documentation #222
Conversation
# TODO example | ||
even though it's not public (it should be?) |
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.
I only see this method used in this class. If there's code similar to this in other places, we can move to utility functions
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.
|
||
Try GRCh38 first, then GRCh37. | ||
|
||
# TODO example for this? |
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.
Did you want to add examples in here or new issue?
Remaining TODO
|
docs/source/transcript_selection.rst
Outdated
* "Validating reference sequences" # TODO what does this mean? | ||
* "Validating exon structure" # TODO what does this mean? |
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.
@korikuzma can you clarify these two lines? They're taken from the previous markdown docs file
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.
IIRC validating reference sequences means ensuring actual reference sequence matches expected reference sequence for a given ac/pos. Exon structure has to deal with ensuring exon numbers are the same.
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.
🙌
If unable to find a match on GRCh38, this method will then attempt to drop down | ||
to GRCh37. | ||
|
||
# TODO example for inputs that demonstrate this? |
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.
@korikuzma do you have an example set of inputs handy for this?
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.
Not off the top of my head. We can make a separate issue if needed.
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.
(sorry, this duplicates a comment you had above. Probably not necessary if there isn't a good example available -- I was just trying to illustrate different code branches based on input)
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.
No worries. It is good to have an example and see if our test suite covers it. I just don't know off the top of my head and would have to dig into the test data
close #209 , address #11
Because of how many different things CST can do, I tried to embed a lot of explanation/instructions directly in the API reference rather than writing it out separately.
psycopg2
and is also unhappy with every one of my attempts to install the binary manually. I've gone ahead and just done a basic manual test, but the logging won't be as pretty.