On Feb 13, 2008, at 12:15 AM, Ben Webb wrote:
True. I guess I did it for the same reason you did the AngleRestraint :-)Daniel Russel wrote:I think it would be good to have an AnglesRestraint which stores a list of chains and applies an AngleRestraint-like restraint to each triple ineach chain. It is easier to set up and maintain than a whole mess of AngleRestraints and more efficient too. Comments?Why do it this way? It's hardly in line with the way distance restraints are now handled. I instead suggest a TripletScore class which works likethe existing SingletonScore and PairScore classes. You get a bit more flexibility that way, surely.
Anyway, here is the more flexible patch, hopefully not missing too many pieces
Attachment:
angles
Description: Binary data
%pythonprepend ChainTripletRestraint::ChainTripletRestraint %{ args[0].thisown=0 %} %pythonprepend AngleTripletScore::AngleTripletScore %{ args[0].thisown=0 %}