Member Site › Forums › Rosetta 3 › Rosetta 3 – Applications › Error with the mpi version of simple_cycpep_predict
- This topic has 5 replies, 2 voices, and was last updated 4 years, 11 months ago by Anonymous.
-
AuthorPosts
-
-
February 5, 2020 at 1:16 pm #3388Anonymous
Dear users and developers,
I recently compiled rosetta with MPI enabled and tried to use the simple_cycpep_predict application. It produced the following error:
ERROR: Assertion `seqpos != 0` failed.
ERROR:: Exit from: src/core/pose/variant_util.cc line: 167
protocols.cyclic_peptide_predict.SimpleCycpepPredictApplication_MPI: (2) {0} [ ERROR ] Exception in SimpleCycpepPredictApplication caught:
protocols.cyclic_peptide_predict.SimpleCycpepPredictApplication_MPI: (2) {0} [ ERROR ]
File: src/core/pose/variant_util.cc:167
[ ERROR ] UtilityExitException
ERROR: Assertion `seqpos != 0` failed.
At first, it looked like an error in the input file but the input files seem valid as the non-mpi compiled version of the application works just fine…
Any hint on what’s wrong here (I’m using Rosetta 2019.35, but there is no change to this part of the code in the newest versions, according to the commit logs)?
Best,
Florent
-
February 6, 2020 at 6:36 am #15135Anonymous
Can you post the full backtrace, or contents of the ROSETTA_CRASH.log file? Without that, it’s hard to know what’s going wrong.
Also, try it with the latest Rosetta. Whether or not the variant_util.cc file has changed, the code that called that function could have. I do fix a lot of bugs over time, and this one might already have been fixed.
-
February 6, 2020 at 2:21 pm #15138Anonymous
The job didn’t produced any ROSETTA_CRASH.log file. Attached is the output of the command, generated with the latest (2020.03.61102) Rosetta. I uploaded my input files as well.
I’m recompiling rosetta with different `extra` flags to see whether it impacts the function behavior or not.
Thanks for your help
-
-
February 6, 2020 at 6:49 am #15136Anonymous
Reading through the code, it looks like you might get that error if you are:
- cyclizing through a sidechain-sidechain isopeptide bond, AND
- not specifying isopeptide bond indices
If specifying the indices with -cyclic_peptide:sidechain_isopeptide_indices <int> <int> solves the problem, let me know. I should add a better, more informative error message to catch that.
-
February 6, 2020 at 1:46 pm #15137Anonymous
The error occurs for a `terminal_disulfide` cyclization. No isopeptide around.
-
February 10, 2020 at 7:07 pm #15141Anonymous
>The error occurs for a `terminal_disulfide` cyclization. No isopeptide around.
Ah! That’s a clue.
Could you:
– Compile in debug mode (./scons.py -j8 mode=debug extras=mpi,serialization simple_cycpep_predict) and rerun? That should spit out a backtrace when it crashes.
– Send me a reproducible test case at vmulligan@flatironinstitute.org? Then I can fix the bug and be sure that it is fixed.
-
-
AuthorPosts
- You must be logged in to reply to this topic.