-
Notifications
You must be signed in to change notification settings - Fork 59
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
pVACview reviewer response #1062
Conversation
…ithlab/pVACtools into pvacview_reviewer_response
…tarting selections, and add way for user to transform data
c07d9d3
to
6ad31a5
Compare
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.
This looks good to me with some minor issues as noted in separate comments.
I assume we can't split out the server.R file into separate modules? It would be nice if it could be split out by pvacseq/neofox/custom input to organize things a bit more.
pvactools/tools/pvacview/run.py
Outdated
@@ -16,7 +16,7 @@ def define_parser(): | |||
def main(args_input = sys.argv[1:]): | |||
parser = define_parser() | |||
args = parser.parse_args(args_input) | |||
arguments = ['{}'.format(args.r_path), "-e", "shiny::runApp('{}', port=3333)".format(args.pvacseq_dir)] |
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.
Was there a reason for this change? We need a consistent port in order for the deployed version to work.
pvactools/tools/pvacview/__init__.py
Outdated
@@ -1,5 +0,0 @@ | |||
__all__ = [ |
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 think we need to put this file back or the pvacview run command won't work correctly.
…r pvacview run command
…VACtools into pvacview_reviewer_response
…VACtools into pvacview_reviewer_response
…sing the error session(unbind-DT, mainTable)
…re generated from
…names does not break pvacview
…ts), and change names of a couple screenshots
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.
Finished review of the pVACview vignette in particular. I found a few typos and issues that lead to warnings when building the docs (title underlines too short; missing empty line after lists). I also expanded on a few explanations in the vignette where I felt more clarification could be useful.
docs/pvacview/prerequisites.rst
Outdated
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 believe that there are additional R packages needed for the new modules. Can you please add them to the installation instruction?
Co-authored-by: Susanna Kiwala <susanna.kiwala@wustl.edu>
Co-authored-by: Susanna Kiwala <susanna.kiwala@wustl.edu>
Co-authored-by: Susanna Kiwala <susanna.kiwala@wustl.edu>
…m Malachi and Susanna)
Co-authored-by: mhoang22 <98837430+mhoang22@users.noreply.github.com>
…edits Reviewing PR #1062
To add ease of use to pVACview, @huiming and I have created two new modules that can be used with input files from other neoantigen annotation tools. This includes a module for the popular tool NeoFox and a module called 'Custom' as it is meant to handle any neoantigen tool data. The new modules are implemented in the same
server.R
file as the base pVACview module but have separateui.R
.NeoFox Module:
Custom: