Since Marc asked me about using one of the restraints that was scheduled for destruction, I figured I should just go ahead and remove them all. The patch removes PairConnectivety, Torus, and Proximity restraints and their test code and the xml reading code which we already had to warn him away from.
Daniel Russel wrote: > Since Marc asked me about using one of the restraints that was scheduled > for destruction, I figured I should just go ahead and remove them all.
Questions about using IMP are best addressed right now to this list (i.e. imp-dev). That way we only have to answer them once. ;) (The list is archived, of course.) In future an imp-users list will probably take over this function, but there seems little use for it right now.
> The patch removes PairConnectivety, Torus, and Proximity restraints and > their test code and the xml reading code which we already had to warn > him away from.
It also removes the ExclusionVolumeRestraint. If anybody is using any of these restraints or the XML loader code, now would be the time to speak up. Otherwise I will commit this patch tomorrow. (There is of course no need to keep the code around for "demo" purposes, since it's not illustrative of the current IMP codebase, and if you really want it, you can dig it out of SVN anyway.) But if anybody uses any of these restraints currently, let me know and we'll replace it with a new-style restraint rather than cutting it out immediately.
Ben
participants (2)
-
Ben Webb -
Daniel Russel