Re: multiple $bound_step calls

You probably want to make that the smallest step within the
corresponding analog "island" for mixed signal, requiring all evaluation
to obey the smallest step would probably have a severe performance
penalty. Also, I wouldn't want to insist that all blocks are
re-evaluated because one called $bound_step within a given island, you
really only want to do that if something coming out of the block changes
that will affect other blocks, e.g. a block may be polling some input,
but its output is through some delay filter, so you wouldn't need to
re-evaluate downstream stuff until the filter output changes.

BTW, while this may be ambiguous is there a pressing need to clarify it?

Kev.

On 06/14/2012 12:27 PM, Marq Kole wrote:
>
> Hi All,
>
>
>
> What should happen when the $bound_step system task is called multiple
> times? The LRM does not say anything about it so this leaves room for
> ambiguity. There are a couple of options, but I think the most
> appropriate is that the smallest argument of all activated $bound_step
> calls takes precedence. This will make sure that the part of the model
> that requires the smallest maximum time step gets its way. The parts
> of the model that can do with larger maximum time steps should also be
> able to live with a smaller time step.
>
>
>
> I will make a Mantis item for this issue. If you have alternative
> views on this matter I would be interested to hear.
>
>
>
> Cheers,
>
> Marq
>
>
>
>
>
> *Marq Kole*
>
> Senior Architect AMSRF Simulation
>
> NXP Semiconductors / Central R&D / Foundation Technology
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.