You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening this issue to propose to cleanup the current TMJets implementation, in such a way that we end-up with two methods (say TMJets1 and TMJets2) and rely directly on the functions in TaylorModels (makes life easier to mantain the package). I'm in the process upgrading TaylorModels (finally, sorry for the long delay), see JuliaIntervals/TaylorModels.jl#165, which use newer versions of TaylorSeries and TaylorIntegration with improved performance.
I can work on this, but I need some guidence from your side.
The text was updated successfully, but these errors were encountered:
I'm opening this issue to propose to cleanup the current TMJets implementation, in such a way that we end-up with two methods (say TMJets1 and TMJets2) and rely directly on the functions in TaylorModels (makes life easier to mantain the package). I'm in the process upgrading TaylorModels (finally, sorry for the long delay), see JuliaIntervals/TaylorModels.jl#165, which use newer versions of TaylorSeries and TaylorIntegration with improved performance.
I can work on this, but I need some guidence from your side.
The text was updated successfully, but these errors were encountered: