Re: use of "Octave:invalid-input-arg" as warning id

[Nicholas Jankowski]

On Tue, Dec 15, 2015 at 10:46 AM, Juan Pablo Carbajal <address@hidden> wrote:

On Tue, Dec 15, 2015 at 4:37 PM, Nicholas Jankowski <address@hidden> wrote:
> On Tue, Dec 15, 2015 at 10:27 AM, Carlo De Falco <address@hidden>
> wrote:
>>
>>
>> On 15 Dec 2015, at 16:21, Juan Pablo Carbajal <address@hidden>
>> wrote:
>>
>> > I think the cleanest thing is to not generate any warnings, unless of
>> > course, we are attaching to mathworks idiosyncrasy.
>>
>> does anyone know what does Matlab do in this case?
>> c.
>>
>>
>>
>
> not overly familiar with the toolset.  Sample code I can run to reproduce?
>
>

ode45(@(x,t)[x(2), -(2*pi*3)^2*x(1)], [0 1], [1 0]);

Matlab 2015a. 

>> ode45(@(x,t)[x(2), -(2*pi*3)^2*x(1)], [0 1], [1 0])
Attempted to access x(2); index out of bounds because numel(x)=1.

Error in @(x,t)[x(2),-(2*pi*3)^2*x(1)]


Error in odearguments (line 87)
f0 = feval(ode,t0,y0,args{:});   % ODE15I sets args{1} to yp0.

Error in ode45 (line 113)
[neq, tspan, ntspan, next, t0, tfinal, tdir, y0, f0, odeArgs, odeFcn, ...
 

is that what you were going for?