-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feat/rt cetsa tools #9
base: main
Are you sure you want to change the base?
Conversation
Please enter the commit message for your changes. Lines starting
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.
For the analysis tool, it seems that the Python wrapper is unnecessary. It could be done simply as a short bash script. That said, I don't think this should stop the branch from being merged.
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 assume that this file is identical to that provided by the client, except for the couple of line changes that you mentioned in Slack.
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.
Do the R requirements need to be installed in this specific order or can these six files be consolidated somehow?
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 Python wrapper seems completely unnecessary. It all boils down to calling the underlying R code via a subprocess
call which is identical to running it from the command-line. The python code could all be replaced with a simple shell script, or the commands could just be baked into the Dockerfile.
closed in favor of #20 |
add 2 new tools: