Thank you for the reply.
Apologies for not making the equation clear. The issue is not related to light time delay. The measurement classes have considered the light time delay when generating measurements.
I am generating measurements using Orekit measurement generator for LEO satellite and using that simulated measurement to do OD.
Since the OD is performed with simulated measurements, I wanted to do a comparison of the state error. ( real simulated state vs estimated state).
I am getting a sort of offset in-state error that is independent of the measurement error.
I have initialized a propagator builder and passed that to a generator.
// In the measurement generation..
final NumericalPropagator propagatorForGen = propBuilder.buildPropagator(propBuilder.getSelectedNormalizedParameters());
final ObservableSatellite satellite = generator.addPropagator(propagatorForGen);
// Copy of the propagator to simulate the states
final NumericalPropagatorBuilder propagatorBuilderCopy = propBuilder.copy();
final NumericalPropagator propagatorCopy = propagatorBuilderCopy.buildPropagator(propagatorBuilderCopy.getSelectedNormalizedParameters());
I am generating TDOA measurements using two locations and using Elevation Detector.
After measurement generation, I am taking the observation times and propagating the propagatorCopy to the measurement times to get the real simulated state.
I am not sure whether the propagation in the measurement generation and the propagation with the propagatorCopy outside measurement generation produces the same PVCoordinates sequence. I have another post with a related issue. Propagting with Numerical Propagator - #3 by luc
Therefore estimated state with the measurements and simulated states may not be comparable to finding the state error. !!
This is why I was asking whether there is a way to access the propagated states in the generator.