-
Notifications
You must be signed in to change notification settings - Fork 124
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
Run From Anywhere #125
base: main
Are you sure you want to change the base?
Run From Anywhere #125
Conversation
…ver a drone file and updated it
… it's probably fine to just leave it.
Adds the docker file necessary to build the image and also the .drone.jsonnet
Cut version tag
…s not already been set. This provides the freedom to use a blast that hasn't been installed in the main directory
Syncing our branch with the original repo.
minor cleanup to the Dockerfile
…nd error in setting the default path in the make_msa.sh script
This PR cleans up some of the unnecessary lines in the Dockerfile it also fixes a bug in the make_msa.sh script where the variables were set.
fixed the typo in the database path
Hi @BrandonFrenz ! This looks very useful! Has it been made possible to run RFAA from anywhere or in a docker container on your branch? Thanks a lot! |
Hey @wehs7661. I'm not sure if you're asking whether it's possible to use this code without using a docker container or whether a docker container exists in this branch that will work. The answer is yes to both. There is a docker file that builds the image you will need included in this branch, you can see an example of how to run it in the examples directory of this branch. If you want to run it without a docker container but get rid of the requirement to run from the main repository you need to set the following 3 environment variables to the proper database paths. |
…rovided additional information on how to set the input arguments
…eTTAFold-All-Atom into run-from-anywhere
Hi @BrandonFrenz , thanks for the prompt reply!
I was actually asking about both. Sorry for not being clear! Good to know that both are working!
This works perfectly for me. Thanks so much! |
Glad to hear it! |
This PR updates all the relevant code so that jobs can be launched from any directory as long as the proper environment variables are set. It is intended to be fully backward compatible with the existing method of running from the main directory.
This PR also includes a docker file capable of building a container that can run RoseTTAFoldAllAtom, as well as an update to the READ.ME which describes how to use it and a new directory with an example for how to run a job inside the docker container.