Doubt about initialization order for additional state and derivatives

Hi folks,

I might have found a small logic flaw in the additional state and derivative’s workflow.
There is a “yield” mechanism so that a provider than depends on another one doesn’t get called before it at each propagation step. To be thourough, this waiting system should be extended to the initialization no?
At the moment, the init methods are called in an arbitrary order in initializeAdditionalData in AbstractPropagator. Opinions?

Cheers,
Romain.

You are right, this logic should be generalized.