Without the correction of getSecularAccelerationMoon(), the conjunction I'm looking at would be 3min 52 seconds earlier than in Solex.
With the current correction for 26 to 25.858, it's 2min 31 seconds earlier than in Solex
With the proposed correction for 26 to 23.895, it would be 16min 30 seconds later
So for this data point anyway, the current correction seems to be giving the best result.
Maybe we shouldn't change anything until some more testing can clarify things
Without the correction of getSecularAccel erationMoon( ), the conjunction I'm looking at would be 3min 52 seconds earlier than in Solex.
With the current correction for 26 to 25.858, it's 2min 31 seconds earlier than in Solex
With the proposed correction for 26 to 23.895, it would be 16min 30 seconds later
So for this data point anyway, the current correction seems to be giving the best result.
Maybe we shouldn't change anything until some more testing can clarify things