DSST Orbit Determination not working correctly in 10.1
I find that using the DSSTBatchLSModel against PV data does not seem to work correctly. Specifically

It converges to a solution, but a solution with large residuals.

The DSSTPropagator does not seem to obey physics, because with a PVT in the .in file used to initialize the estimated orbit, and a PVT value a few seconds later, I would expect very small residuals for that data value, but the residuals are surpsingly lage (100s of m and 10s of m/sec). This is true whther or not drag, radiation pression, sun/moon third body forces, etc., are turned on. Residuls are much large when hours of data are used.

I am providing all data in EME2000 coordinates and UTC (data comes from precision Grace ephemeris that is in ITRF and modified GPS seconds  I am pretty sure that all PV conversions are done correctly).

mu is correct. Switching from central body degree/order 12 to 70 does not significantly change the results.

Using iers.conventions=2010. Switching from WGS84 to CIO/2010 doesn't change the results significantly.

Latest test using propagator.min.step = 0.1 propagator.max.step = 100.0 propagator.position.error = 0.0001
but using other step sizes does not siginicantly change the results.

Modifying DSSTBatchLSModel from
parallelizer.propagate(firstDate.shiftedBy(1.0), lastDate.shiftedBy(+1.0));
to
parallelizer.propagate(firstDate.shiftedBy(1.0e3), lastDate.shiftedBy(+1.0e3));
does not significantly change the results (but why was a shift of 1 sec chosen?? If the propagation region in this line needs to strictly include the requested time range, shouldn't the extensions be configurable?).
Bottom line  something seems wrong with the physics model, but I am unable to determine what. Suggestions?