Re: closed loop control GSoC Design Question

[Doug Stewart]

On Tue, Jun 11, 2013 at 9:59 AM, Doug Stewart <address@hidden> wrote:

On Tue, Jun 11, 2013 at 9:35 AM, Lukas Reichlin <address@hidden> wrote:

On 11.06.2013, at 14:06, Doug Stewart <address@hidden> wrote:

> 2)   Should this project be part of the controls package?  I think yes. The controls package would have to be loaded for this SISO program to work.
>
> Doug

In the long term, yes. In the short/mid term I would prefer to create a "sisotool" package dependent on control. The reason is that it allows frequent releases (which are very likely in the early stages of development) without interfering with the rest of control.

Currently we have a "control" repository [1] for releases and a "control-time-delay" repository [2] where Thomas Vasileiou is working on integrating time delays. If you need to apply changes to existing control functions, you can clone one of the Mercurial repositories [1, 2] and experiment with your stuff there.

Lukas


[1]
https://bitbucket.org/paramaniac/control/

[2]
https://bitbucket.org/paramaniac/control-time-delay/

Thank you Lukas,  I agree with your plan.

It looks like it will just be a bunch of M files, so it will be easy to keep it separate until it is stable.

Doug

I have some sad news.

Matheus  the GSoC student that was working on the SISO tool has sent me an email saying that he is not able to continue with this project at this time.

I am encouraging him to work on it latter when he has some time.

I guess this means he will get a failing grade  at the midterm.

So sad.

Doug