-
Notifications
You must be signed in to change notification settings - Fork 703
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
{bio}[fosscuda/2019b] RoseTTAFold v1.0.0 w/ Python 3.7.4 #13795
{bio}[fosscuda/2019b] RoseTTAFold v1.0.0 w/ Python 3.7.4 #13795
Conversation
…orch-1.8.1.eb and patches: RoseTTAFold-1.0.0_cpu_mem_from_env.patch, RoseTTAFold-1.0.0_db_paths_from_env.patch, RoseTTAFold-1.0.0_fix_cache_directory.patch, RoseTTAFold-1.0.0_lddt_path.patch, RoseTTAFold-1.0.0_no_conda.patch, RoseTTAFold-1.0.0_use_eb_paths.patch
I'm not sure if there is anything we could add as sanity check. Maybe something like #!/bin/bash
#SBATCH --job-name=RoseTTAFold
#SBATCH --output=rosettafold-job-out.%J
#SBATCH --time=48:00:00
#SBATCH --nodes=1
#SBATCH --cpus-per-task=16
#SBATCH --gres=gpu:rtx2080ti:1
module load RoseTTAFold/1.0.0-fosscuda-2019b-Python-3.7.4-PyTorch-1.8.1
export BFDPATH=/scratch/pdbs/bfd
export PDB100PATH=/scratch/pdbs/pdb100_2021Mar03
export UNIREF30PATH=/scratch/pdbs/UniRef30_2020_06
export MEM=$SLURM_MEM_PER_NODE
export CPU=$SLURM_CPUS_PER_TASK
run_pyrosetta_ver.sh input.fa $PWD |
Test report by @zemu-unile |
@boegelbot please test @ generoso |
@SebastianAchilles: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 922869452 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
@boegelbot please test @ generoso
Failed with |
@boegelbot please test @ generoso |
@SebastianAchilles: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 923717491 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Failed because generoso has no sources for |
@zemu-unile Could you change the HH-Suite dependency from |
One problem here is that HH-Suite 3.3.0 is in 2020 toolchains but RoseTTAFold needs 2019b due to requiring old TensorFlow 1.x. I am not sure if we should port HH-Suite 3.3.0 to 2019b. @Micket any thoughts on this? |
Good point, however I don't see any issue having an EC for 3.2.0 and 3.3.0 in 2019b. But you are right, the proper way would be to patch 3.2.0 to make it work. |
We would need to add an exception for the CI to allow multiple version in the same toolchain. But yes that is possible. |
The Problem with TensorFlow 1.x is that it needs an older Cuda version. I'm still hoping that RoseTTAFold will switch to TensorFlow 2.x |
Good point! Okay, then I suggest to add HH-Suite 3.3.0 to 2019b with an exception. Do you agree? |
Opened a PR for HH-Suite #14191 |
…asyconfigs into 20210823110414_new_pr_RoseTTAFold100
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.
closing this since |
(created using
eb --new-pr
)