Open MichaelCurrie opened 10 years ago
Perhaps the best way to handle this would be to make velocity (which is quite complicated, having its own module already), a "pre-feature" so that both locomotion and path can use it.
I'm not really sure about the suggested approach. Perhaps instead we just come up with a good way of documenting dependencies. Thoughts?
I think these dependencies are fine, they just need to be documented.
I recently built in the ability to selectively process features. In order to do this properly however there needs to be the ability to enable computations of dependencies.
I suggest creation of another issue which is the specification of these dependencies, and another which uses these dependencies to ensure that the dependencies are computed before any desired feature is computed.
During WormFeatures initialization, all desired features would make sure that dependencies are not in the ignored features list (in FeatureProcessingOptions).
Awkward dependencies: