You are here


The problem hasn't been solved

Error when using Remodel on a protein with a chemically bound ligand

Loop Modeling

My goal is to insert a linker fragment into a protein which has a chemically bound ligand. To do that, I have relaxed the structure with the chemically bound ligand and am now trying to insert the linker fragment into my protein using Remodel. The ligand is bound to a CYX residue (modified Cystein) in my protein.

Post Situation: 

Protonating all possible sites: the problem in MOL2 file format or the innate Rosetta feature(bug)?

Small Molecules
Chemically Modified Residues

Dear Sir and Madam,

I have performed a lot of attempts in order to conduct the coupled_moves docking with ligand without it protonation. I need to specify that this ligand (in his physiologically active form) has only one Hydrogen on his sulfonamide site. Nevertheless, despite the absence of any other Hydrogens both in input .params, MOL2 and PDB file, a lot of sites (sulfonamide Nitrogen with additional undesirable Hydrogen, as well as some Carbons on a benzene ring and tail) get protonated.
By the way, Ligand_Dock application also protonates all possible ligand sites.

Post Situation: 

RosettaScripts filter BuriedUnsatHbonds2 missing still



Can the BuriedUnsatHbonds2 filter be pushed to release? It gets called in a rosetta scripts xml included in the supplementary materials for this paper (published in 2017): DOI: 10.1126/science.aan0693



Post Situation: 

symmetric design w/ hbnet and unsatisfied_buried_penalty score terms


Hi All,

I am working on designing some symmetric structures and am currently using REF2015 + hbnet. In addition, I want to add the buried_unsatisfied_penalty. When I add this term to the score function, it works and can score 'non-symmetrized' structures just fine. However, when I try to score a structure that has been 'symmetrized' I get the following error: 

File: /home/benchmark/rosetta/source/src/core/pack/guidance_scoreterms/buried_unsat_penalty/graph/

[ ERROR ] UtilityExitException

Post Situation: 


Subscribe to RSS - Unsolved