Re: Aliasing of step response (3.4.2 MinGW, control-2.1.55)

[Bernhard Weller]

Lukas Reichlin-3 wrote:
> 
> Hi Bernhard
> 
> I confirm your suspicion, but I don't have a quick fix this time. The
> problem is caused by the function __sim_horizon__ at the end of the file
> __time_response__.m which calculates tfinal and dt. Do you know of a
> robust method to find an appropriate time step? I would be happy to add an
> improved version :-)
> 
> Regards,
> Lukas
> 
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
> 

Hi Lukas,

I'm not aware of of a robust algorithm for the determination of the time
step. I'm sadly not an expert of control system theory, more like a
beginner. I just thought that I point it out, maybe it was unknown - or
someone else with more knowledge is able to fix it.

Thanks for confirming my thoughts.

Bernhard

--
View this message in context: 
http://octave.1599824.n4.nabble.com/Aliasing-of-step-response-3-4-2-MinGW-control-2-1-55-tp3843066p3846404.html
Sent from the Octave - General mailing list archive at Nabble.com.