[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Default merged to stable for upcoming 4.2 release
From: |
c. |
Subject: |
Re: Default merged to stable for upcoming 4.2 release |
Date: |
Thu, 6 Oct 2016 09:29:39 +0200 |
On 6 Oct 2016, at 09:22, Marco Caliari <address@hidden> wrote:
>
> This is the most flexible. What is the current strategy for, say, ode23tb?
> This function uses the embedded method of order three for the estimates, but
> the method of order two for advancing in time. In this case, q = oder_dt =
> order_interp = 2. Right?
we don't have ode23tb at the moment ...
but for example in odebwe and odefwe the same method with different timesteps
is used to estimate the error
so also there q = oder_dt = order_interp = 1.
c.
> Marco
- Re: Default merged to stable for upcoming 4.2 release, (continued)
- Re: Default merged to stable for upcoming 4.2 release, c., 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, Marco Caliari, 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, c., 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, Marco Caliari, 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, c., 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, Marco Caliari, 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release,
c. <=
- Re: Default merged to stable for upcoming 4.2 release, Schöps , Sebastian, 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, Marco Caliari, 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, Schöps , Sebastian, 2016/10/06
- Re: Default merged to stable for upcoming 4.2 release, Schöps , Sebastian, 2016/10/06