You are here
Compilation
install error
hi everyone!
I install rosetta 3 using the compiler gcc3.4 , miss error:
- Read more about install error
- 1 comment
- Log in or register to post comments
How to read the output score file from rosetta?
Dear all,
I find the score file output by rosetta is different to read. For example, a score-snugdock.sf file produced by snugdock reads like the following in gedit:
https://www.dropbox.com/s/6oba8nitiwob7pb/score.PNG?dl=0
I cannot tell the column names and their corresponding values. The Rosetta documnet gives a sort command that can pick out the structure with the lowest score:
sort -nk5 score-snugdock.sf | head -n1 | awk '{print $NF}'
- Read more about How to read the output score file from rosetta?
- 1 comment
- Log in or register to post comments
libmpc.so.2: cannot open shared object file
I am attempting to install Rosetta/3.8 on a Linux Cluster running Redhat 5.6. I am compiling with gcc/4.9.3 and mpich 3.2. I have come across the following error:
/exports/apps/gcc/4.9.3/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/cc1plus: error while loading shared libraries: libmpc.so.2: cannot open shared object file: No such file or directory
- Read more about libmpc.so.2: cannot open shared object file
- 1 comment
- Log in or register to post comments
Running snugdock was crashed by "segmentation fault"
Hello everyone,
When using the following command to run snugdock in my centos 7 system:
snugdock.linuxgccrelease -s antibody_antigen_start.prepack_new.pdb \
-ensemble1 antibody_ensemble.list \
-ensemble2 antigen_ensemble.list \
-detect_disulf false \
-antibody:auto_generate_kink_constraint \
-antibody:all_atom_mode_kink_constraint \
-nstruct 20 \
-multiple_processes_writing_to_one_directory > snugdock.log 2>&1 &
- Read more about Running snugdock was crashed by "segmentation fault"
- 3 comments
- Log in or register to post comments
The problems on pdb renumbering
Hello everyone,
I am learning to do antibody-antigen docking with snugdock. The antigen I am working on has two chains (chain A and B). Before the antigen pdb file can be used for docking, it must be renumbered (changing it to a single A chain and numbering all residues continuously), am I right? There is some renumbering scripts in the Rosetta package. I have tried some of them, but none can work.
(1) The pdb_renumber.py script in the /app/rosetta_src_2017.08.59291_bundle/tools/protein_tools/scripts directory. The command:
- Read more about The problems on pdb renumbering
- Log in or register to post comments
Cannot run binaries after successful compilation
Dear all,
I have been trying to compile rosetta 3.8 for a while now without success (meathod worked will with 3.7). I have a 17.04 Ubuntu Gnome Operating System.
Compile Commands:
sudo apt install zlib1g-dev scons build-essential -y
tar -xvzf rosetta_src_3.8_bundle.tgz
cd {ROSETTA}/main/source
./scons.py mode=release bin
Result:
Successfully compiles everything, no errors printed.
- Read more about Cannot run binaries after successful compilation
- 6 comments
- Log in or register to post comments
Error when running "plot_LHOC.py"
Dear all,
When I run the following command:
$ROSETTA/main/source/scripts/python/public/plot_VL_VH_orientational_coordinates/plot_LHOC.py
It gives the following error:
- Read more about Error when running "plot_LHOC.py"
- 5 comments
- Log in or register to post comments
How to set the enviroment variable $ROSETTA3, $ $ROSETTA3_DB, $ROSETTA_TOOLS?
Dear all,
The "How To Read These Tutorials" section (https://www.rosettacommons.org/demos/latest/tutorials/How_To_Read_These_Tutorials/Tutorial_Setup) of the tutorial of Rosetta requires the following environment variables are set:
env $ROSETTA3=the path to your Rosetta/source directory
Error running unit test executable
Hello!
I was trying to test my Rosetta installation and at the begining of test I've got an error:
I didn't find any solution on Rosetta Forum.
server@localhost:~$ python test/run.py
Identifying platform...
Platform found: debug/linux/4.10/64/x86/gcc/6.3/default
Error running unit test executable for protocols.test - not all tests may be availible.
Error running unit test executable for core.test - not all tests may be availible.
- Read more about Error running unit test executable
- 14 comments
- Log in or register to post comments