Empirically, we all know larger mpsi slows down the ForceFreeStates.
The hand waving reason is the 10s of thousands of spline interpolations done during the ODE integration are a bit slower. But why would this be the case when we are using hints to cleanly provide the knot locations of interest and these are only slowly (and monotonically) incrementing? It seems like there would be effectively no search difference with knot number in this case. Is there some further optimization of the spline evaluation calls that would make this loop insensitive to the spline knot length? It seems like there should be.
@mgyoo86 might have some insights.
Possible topic for David Smitth ( @drsmith48 ) and UW hackathon
Empirically, we all know larger
mpsislows down the ForceFreeStates.The hand waving reason is the 10s of thousands of spline interpolations done during the ODE integration are a bit slower. But why would this be the case when we are using hints to cleanly provide the knot locations of interest and these are only slowly (and monotonically) incrementing? It seems like there would be effectively no search difference with knot number in this case. Is there some further optimization of the spline evaluation calls that would make this loop insensitive to the spline knot length? It seems like there should be.
@mgyoo86 might have some insights.
Possible topic for David Smitth ( @drsmith48 ) and UW hackathon