[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [IMP-dev] thoughts on the reorg



Daniel Russel wrote:
So to make the next iteration of the proposal:
1) the IMP kernel module is simplified to contain only the IMP kernel proper which is basically some subset of IMP/*.h, perhaps without decoratorbase and ParticleRefiner.

That makes sense, but not until dependent projects are in the build system, because obviously they would need to be updated.

2) We add a module IMP_misc or IMP_core which contains all the existing restraints, states and decorators and stuff and has a more open access policy.

There are two separate modules here: misc and core. misc is for stuff that doesn't fit anywhere else (e.g. ParticleRefiner) and can be very open, even today. Other stuff that is relied upon by others will move from the kernel into core (e.g. nonbonded lists). But that won't happen today - it needs to wait for the dependent projects to be updated. By its very nature, it should also be less open than misc.

3) We adopt a convention of labelling things in IMP_misc as to their maturity.

That makes sense for misc. But everything in core should be stable.

	Ben
--
                      http://salilab.org/~ben/
"It is a capital mistake to theorize before one has data."
	- Sir Arthur Conan Doyle