Re: [casper] Matlab components for toolflow

[Nimish Sane]

Thanks a lot Andrew!

We are using pfb_fir_real. So that is not a problem. I will try the new FFT
block very soon.

Thanks,

Nimish

On Sep 26, 2013, at 5:53 PM, Andrew Martens  wrote:

 Hi Dale

Just pushed my update to ska-sa repo on github. Replacement script
(doubles2unsigned.m) seems to be working (for basic simulations, currently
running more in-depth tests).

Calls to fi() have been removed from the FFT family as far as I can tell,
there are some still lurking in the new pfb_fir_generic scripts but those
need work in other ways so the standard pfb_fir_real should be used for the
moment.

Sorry it took a while, you now have more options.

Regards
Andrew

 Hi Andrew,

 We are desperate to complete a design by this week in order to support our
software development team over the weekend, but we are stuck right now due
to this issue.  If you do manage to find a work-around and can provide a
block update, please let us know.

 Many Thanks,
Dale


On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens  wrote:

> Hi Dave
>
> I use fi to convert coefficients to be stored from parallel matlab double
> precision format into single unsigned words that will accurately be
> converted back by slicing and using convert blocks. I think it is possible
> to create the same functionality, I will have a quick try.
>
> Cheers
> Andrew
>
>
>  Hi, Andrew,
>>
>> Can you elaborate on how you use fi?  I think much of the functionality
>> can be accomplished by judicious use of the multiplication, rounding, and
>> modulo math (for wrapping) or "x(x>max)=max" (for saturation).  It might be
>> possible to create a "clean room" replacement function that does what you
>> need.
>>
>> Thanks,
>> Dave
>>
>> On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
>>
>>  Hi
>>>
>>>  Thanks Andrew! Would you know approximately how much time it would take
 for you to look into this? Meanwhile, would you know the latest commit that
 does not use fi, and hence, does not need Floating-point toolbox?

  Replacing fi will be difficult. I will probably rather provide a
>>> parameter that allows the user to choose not to pack coefficients next to
>>> each other in the same BRAM (which fi is part of now). This will allow the
>>> user to trade off BRAM for license fees :)
>>>
>>> The last commit not using fi would be before my FFT upgrade, so
>>> somewhere near the first quarter of the year.
>>>
>>> Regards
>>> Andrew
>>>
>>>  Thanks,

 Nimish


 On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
 dav...@astro.berkeley.edu> wrote:
 Thanks, Andrew!

 Dave

 On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:

  Hi
>
> I do use the fi constructor to generate fixed point values when
> generating twiddle values for storage.
>
> I will see if it can be done in another way as it seems wasteful to
> require a license just for that.
>
> Regards
> Andrew
>
>
>  Thanks, Nimish,
>>
>> Looking at the recently updated casper-astro repository, the
>> following mask init scripts use the "fi" function (technically a
>> "constructor", I think) to crete fixed point objects:
>>
>> casper_library/cosin_init.m
>> casper_library/feedback_osc_init.m
>> casper_library/pfb_fir_coeff_gen_init.m
>>
>> Any block that uses the scripts (e.g. via sub-blocks) will probably
>> need a Fixed Point Toolbox license.  I suspect it wouldn't be too 
>> difficult
>> to rewrite these files in a way that maintain the functionality, but 
>> avoids
>> the "fi" (and any related) call(s).
>>
>> It looks like Andrew Martens introduced at least some of the "fi"
>> dependencies, so maybe he would be willing to redo the relevant bits of
>> these files?
>>
>> Dave
>>
>> On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
>>
>>  Some more investigation:
>>>
>>> I am seeing these messages:
>>>
>>> License checkout failed.
>>> License Manager Error -5
>>> Cannot find a license for Fixed_Point_Toolbox.
>>>
>>> Troubleshoot this issue by visiting:
>>> http://www.mathworks.com/support/lme/R2012b/5
>>>
>>> Diagnostic Information:
>>> Feature: Fixed_Point_Toolbox
>>> License path:
>>> /home/observer/.matlab/R2012b_licenses:/home/observer/tools/MATLAB/R2012b/licenses/license.dat:/home/observer/tools/MATLAB/R2012b/licenses/license_fpgadev_277254_R2012b.lic
>>> Licensing error: -5,357.
>>> Simulink:Masking:Bad_Init_Commands: Error in
>>> 'fft_wideband_real_core/fft_wideband_real/fft_direct/butterfly0_0/twiddle/coeff_gen/feedback_osc':
>>> Initialization commands cannot be evaluated.
>>> Backtrace 1: reuse_block:138
>>> Backtrace 2: coeff_gen_init:498
>>> Backtrace 3: reuse_block:51
>>> Backtrace 4: add_convert_init:496
>>> Backtrace 5: draw_basic_partial_cycle:407
>>> Backtrace 6: cosin_init:165
>>> Backtrace 7: xl

Re: [casper] Matlab components for toolflow

[Andrew Martens]

Hi Dale

Just pushed my update to ska-sa repo on github. Replacement script 
(doubles2unsigned.m) seems to be working (for basic simulations, 
currently running more in-depth tests).


Calls to fi() have been removed from the FFT family as far as I can 
tell, there are some still lurking in the new pfb_fir_generic scripts 
but those need work in other ways so the standard pfb_fir_real should be 
used for the moment.


Sorry it took a while, you now have more options.

Regards
Andrew


Hi Andrew,

We are desperate to complete a design by this week in order to support 
our software development team over the weekend, but we are stuck right 
now due to this issue.  If you do manage to find a work-around and can 
provide a block update, please let us know.


Many Thanks,
Dale


On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens > wrote:


Hi Dave

I use fi to convert coefficients to be stored from parallel matlab
double precision format into single unsigned words that will
accurately be converted back by slicing and using convert blocks.
I think it is possible to create the same functionality, I will
have a quick try.

Cheers
Andrew


Hi, Andrew,

Can you elaborate on how you use fi?  I think much of the
functionality can be accomplished by judicious use of the
multiplication, rounding, and modulo math (for wrapping) or
"x(x>max)=max" (for saturation).  It might be possible to
create a "clean room" replacement function that does what you
need.

Thanks,
Dave

On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:

Hi

Thanks Andrew! Would you know approximately how much
time it would take for you to look into this?
Meanwhile, would you know the latest commit that does
not use fi, and hence, does not need Floating-point
toolbox?

Replacing fi will be difficult. I will probably rather
provide a parameter that allows the user to choose not to
pack coefficients next to each other in the same BRAM
(which fi is part of now). This will allow the user to
trade off BRAM for license fees :)

The last commit not using fi would be before my FFT
upgrade, so somewhere near the first quarter of the year.

Regards
Andrew

Thanks,

Nimish


On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon
mailto:dav...@astro.berkeley.edu>> wrote:
Thanks, Andrew!

Dave

On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:

Hi

I do use the fi constructor to generate fixed
point values when generating twiddle values for
storage.

I will see if it can be done in another way as it
seems wasteful to require a license just for that.

Regards
Andrew


Thanks, Nimish,

Looking at the recently updated casper-astro
repository, the following mask init scripts
use the "fi" function (technically a
"constructor", I think) to crete fixed point
objects:

casper_library/cosin_init.m
casper_library/feedback_osc_init.m
casper_library/pfb_fir_coeff_gen_init.m

Any block that uses the scripts (e.g. via
sub-blocks) will probably need a Fixed Point
Toolbox license.  I suspect it wouldn't be too
difficult to rewrite these files in a way that
maintain the functionality, but avoids the
"fi" (and any related) call(s).

It looks like Andrew Martens introduced at
least some of the "fi" dependencies, so maybe
he would be willing to redo the relevant bits
of these files?

Dave

On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:

Some more investigation:

I am seeing these messages:

License checkout failed.
License Manager Error -5
Cannot find a license for Fixed_Point_Toolbox.

Troubleshoot this issue by visiting:
http://www.mathworks.com/support/lme/R2012b/5

Diagnostic Information:
Feature: Fixed_Point_Toolbox
License

Re: [casper] Matlab components for toolflow

[G Jones]

What about just checking out an older version of the libraries pre-'fi'?
On Sep 26, 2013 2:32 PM, "Nimish Sane"  wrote:

> Yes, that is what I am trying right now (old netlist). Jack's FP license
> had reached its limit. So that did work anyways.
>
> Thanks,
>
> Nimish
>
>
> On Thu, Sep 26, 2013 at 1:58 PM, David MacMahon  > wrote:
>
>> Hi, Nimish,
>>
>> If you have a netlist you are happy with then just use that one.  There
>> is no need to regenerate a new netlist unless you want a bugfix or a change
>> in latencies (e.g. to improve timing).
>>
>> Dave
>>
>> On Sep 26, 2013, at 8:32 AM, Nimish Sane wrote:
>>
>> > Thanks Jack! I was thinking of using the black box which was generated
>> using earlier toolflow and library, but this may be better. If someone with
>> a license is willing to do this, please let me know. I will be happy to
>> share the mask parameter configuration.
>> >
>> > The most annoying part of this is that even for the 30 day trial
>> version of this toolbox, I need to wait for someone to call me within 3
>> business days!
>> >
>> > Thanks a lot,
>> >
>> > Nimish
>> >
>> >
>> > On Thu, Sep 26, 2013 at 9:28 AM, Jack Hickish 
>> wrote:
>> > If you're really desperate, presumably someone on this list with a
>> license can precompile the fft block for you, which you could then black
>> box? Or generate the block, disable the init script, and send it to you?
>> >
>> > Not necessarily suggesting that this is a better strategy than just
>> reverting your library to before fi was introduced, or waiting for a fix,
>> but a possibility perhaps?
>> >
>> > cheers,
>> > Jack
>> >
>> > On 26 Sep 2013 12:12, "Gary, Dale E."  wrote:
>> > Hi Andrew,
>> >
>> > We are desperate to complete a design by this week in order to support
>> our software development team over the weekend, but we are stuck right now
>> due to this issue.  If you do manage to find a work-around and can provide
>> a block update, please let us know.
>> >
>> > Many Thanks,
>> > Dale
>> >
>> >
>> > On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens 
>> wrote:
>> > Hi Dave
>> >
>> > I use fi to convert coefficients to be stored from parallel matlab
>> double precision format into single unsigned words that will accurately be
>> converted back by slicing and using convert blocks. I think it is possible
>> to create the same functionality, I will have a quick try.
>> >
>> > Cheers
>> > Andrew
>> >
>> >
>> > Hi, Andrew,
>> >
>> > Can you elaborate on how you use fi?  I think much of the functionality
>> can be accomplished by judicious use of the multiplication, rounding, and
>> modulo math (for wrapping) or "x(x>max)=max" (for saturation).  It might be
>> possible to create a "clean room" replacement function that does what you
>> need.
>> >
>> > Thanks,
>> > Dave
>> >
>> > On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
>> >
>> > Hi
>> >
>> > Thanks Andrew! Would you know approximately how much time it would take
>> for you to look into this? Meanwhile, would you know the latest commit that
>> does not use fi, and hence, does not need Floating-point toolbox?
>> >
>> > Replacing fi will be difficult. I will probably rather provide a
>> parameter that allows the user to choose not to pack coefficients next to
>> each other in the same BRAM (which fi is part of now). This will allow the
>> user to trade off BRAM for license fees :)
>> >
>> > The last commit not using fi would be before my FFT upgrade, so
>> somewhere near the first quarter of the year.
>> >
>> > Regards
>> > Andrew
>> >
>> > Thanks,
>> >
>> > Nimish
>> >
>> >
>> > On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
>> dav...@astro.berkeley.edu> wrote:
>> > Thanks, Andrew!
>> >
>> > Dave
>> >
>> > On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:
>> >
>> > Hi
>> >
>> > I do use the fi constructor to generate fixed point values when
>> generating twiddle values for storage.
>> >
>> > I will see if it can be done in another way as it seems wasteful to
>> require a license just for that.
>> >
>> > Regards
>> > Andrew
>> >
>> >
>> > Thanks, Nimish,
>> >
>> > Looking at the recently updated casper-astro repository, the following
>> mask init scripts use the "fi" function (technically a "constructor", I
>> think) to crete fixed point objects:
>> >
>> > casper_library/cosin_init.m
>> > casper_library/feedback_osc_init.m
>> > casper_library/pfb_fir_coeff_gen_init.m
>> >
>> > Any block that uses the scripts (e.g. via sub-blocks) will probably
>> need a Fixed Point Toolbox license.  I suspect it wouldn't be too difficult
>> to rewrite these files in a way that maintain the functionality, but avoids
>> the "fi" (and any related) call(s).
>> >
>> > It looks like Andrew Martens introduced at least some of the "fi"
>> dependencies, so maybe he would be willing to redo the relevant bits of
>> these files?
>> >
>> > Dave
>> >
>> > On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
>> >
>> > Some more investigation:
>> >
>> > I am seeing these messages:
>> >
>> > License checkout failed.
>> > 

Re: [casper] Matlab components for toolflow

[Nimish Sane]

Yes, that is what I am trying right now (old netlist). Jack's FP license
had reached its limit. So that did work anyways.

Thanks,

Nimish


On Thu, Sep 26, 2013 at 1:58 PM, David MacMahon
wrote:

> Hi, Nimish,
>
> If you have a netlist you are happy with then just use that one.  There is
> no need to regenerate a new netlist unless you want a bugfix or a change in
> latencies (e.g. to improve timing).
>
> Dave
>
> On Sep 26, 2013, at 8:32 AM, Nimish Sane wrote:
>
> > Thanks Jack! I was thinking of using the black box which was generated
> using earlier toolflow and library, but this may be better. If someone with
> a license is willing to do this, please let me know. I will be happy to
> share the mask parameter configuration.
> >
> > The most annoying part of this is that even for the 30 day trial version
> of this toolbox, I need to wait for someone to call me within 3 business
> days!
> >
> > Thanks a lot,
> >
> > Nimish
> >
> >
> > On Thu, Sep 26, 2013 at 9:28 AM, Jack Hickish 
> wrote:
> > If you're really desperate, presumably someone on this list with a
> license can precompile the fft block for you, which you could then black
> box? Or generate the block, disable the init script, and send it to you?
> >
> > Not necessarily suggesting that this is a better strategy than just
> reverting your library to before fi was introduced, or waiting for a fix,
> but a possibility perhaps?
> >
> > cheers,
> > Jack
> >
> > On 26 Sep 2013 12:12, "Gary, Dale E."  wrote:
> > Hi Andrew,
> >
> > We are desperate to complete a design by this week in order to support
> our software development team over the weekend, but we are stuck right now
> due to this issue.  If you do manage to find a work-around and can provide
> a block update, please let us know.
> >
> > Many Thanks,
> > Dale
> >
> >
> > On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens 
> wrote:
> > Hi Dave
> >
> > I use fi to convert coefficients to be stored from parallel matlab
> double precision format into single unsigned words that will accurately be
> converted back by slicing and using convert blocks. I think it is possible
> to create the same functionality, I will have a quick try.
> >
> > Cheers
> > Andrew
> >
> >
> > Hi, Andrew,
> >
> > Can you elaborate on how you use fi?  I think much of the functionality
> can be accomplished by judicious use of the multiplication, rounding, and
> modulo math (for wrapping) or "x(x>max)=max" (for saturation).  It might be
> possible to create a "clean room" replacement function that does what you
> need.
> >
> > Thanks,
> > Dave
> >
> > On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
> >
> > Hi
> >
> > Thanks Andrew! Would you know approximately how much time it would take
> for you to look into this? Meanwhile, would you know the latest commit that
> does not use fi, and hence, does not need Floating-point toolbox?
> >
> > Replacing fi will be difficult. I will probably rather provide a
> parameter that allows the user to choose not to pack coefficients next to
> each other in the same BRAM (which fi is part of now). This will allow the
> user to trade off BRAM for license fees :)
> >
> > The last commit not using fi would be before my FFT upgrade, so
> somewhere near the first quarter of the year.
> >
> > Regards
> > Andrew
> >
> > Thanks,
> >
> > Nimish
> >
> >
> > On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
> dav...@astro.berkeley.edu> wrote:
> > Thanks, Andrew!
> >
> > Dave
> >
> > On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:
> >
> > Hi
> >
> > I do use the fi constructor to generate fixed point values when
> generating twiddle values for storage.
> >
> > I will see if it can be done in another way as it seems wasteful to
> require a license just for that.
> >
> > Regards
> > Andrew
> >
> >
> > Thanks, Nimish,
> >
> > Looking at the recently updated casper-astro repository, the following
> mask init scripts use the "fi" function (technically a "constructor", I
> think) to crete fixed point objects:
> >
> > casper_library/cosin_init.m
> > casper_library/feedback_osc_init.m
> > casper_library/pfb_fir_coeff_gen_init.m
> >
> > Any block that uses the scripts (e.g. via sub-blocks) will probably need
> a Fixed Point Toolbox license.  I suspect it wouldn't be too difficult to
> rewrite these files in a way that maintain the functionality, but avoids
> the "fi" (and any related) call(s).
> >
> > It looks like Andrew Martens introduced at least some of the "fi"
> dependencies, so maybe he would be willing to redo the relevant bits of
> these files?
> >
> > Dave
> >
> > On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
> >
> > Some more investigation:
> >
> > I am seeing these messages:
> >
> > License checkout failed.
> > License Manager Error -5
> > Cannot find a license for Fixed_Point_Toolbox.
> >
> > Troubleshoot this issue by visiting:
> > http://www.mathworks.com/support/lme/R2012b/5
> >
> > Diagnostic Information:
> > Feature: Fixed_Point_Toolbox
> > License path:
> /home/observer/.matlab/R2012b

Re: [casper] ROACH TGE Multicast

[David MacMahon]

Hi, Wes,

You could probably coax the current 10 GbE block to do multicast.  Since the 10 
GbE block assumes that all locally connected devices (i.e. on the same subnet) 
have the same the first 24 bits of the IP address as the core's own IP address. 
 So you could choose a block of 256 consecutive multicast addresses and assign 
the core's IP address in there and then you could send to 255 other multicast 
groups.  You'd have to manually populate the ARP tables since multicast IP 
packets must be sent in Ethernet packets with a multicast MACs.  This "trick" 
would mean that the core would only send multicast packets and would not be 
able to send unicast packets.

Ideally, the 10 GbE block would be modified to recognize multicast destination 
IP addressed and then add in the derived MAC address automatically instead of 
getting it from the ARP table.  Then it could send both multicast and unicast 
packets.

It would be another matter to get the core to listen to multicast packets 
(especially multiple multicast groups).  I think that would be a little more 
complicated (unless you set its IP address to a single multicast IP and that's 
the only multicast group you want it to join).

Hope this helps,
Dave

On Sep 19, 2013, at 1:45 AM, Wesley New wrote:

> Hi all,
> 
> I am looking at implementing multicasting on the Ten Gig Ethernet cores for 
> ROACH. Has anyone looked at doing this before or even implemented it and not 
> committed it to the CASPER repo? Any comments and suggestions would be 
> welcome.
> 
> Thanks
> 
> Wes
> 
> 
> Wesley New
> South African SKA Project
> +2721 506 7365
> www.ska.ac.za
> 
> 

Re: [casper] Matlab components for toolflow

[David MacMahon]

Hi, Nimish,

If you have a netlist you are happy with then just use that one.  There is no 
need to regenerate a new netlist unless you want a bugfix or a change in 
latencies (e.g. to improve timing).

Dave

On Sep 26, 2013, at 8:32 AM, Nimish Sane wrote:

> Thanks Jack! I was thinking of using the black box which was generated using 
> earlier toolflow and library, but this may be better. If someone with a 
> license is willing to do this, please let me know. I will be happy to share 
> the mask parameter configuration.
> 
> The most annoying part of this is that even for the 30 day trial version of 
> this toolbox, I need to wait for someone to call me within 3 business days!
> 
> Thanks a lot,
> 
> Nimish
> 
> 
> On Thu, Sep 26, 2013 at 9:28 AM, Jack Hickish  wrote:
> If you're really desperate, presumably someone on this list with a license 
> can precompile the fft block for you, which you could then black box? Or 
> generate the block, disable the init script, and send it to you?
> 
> Not necessarily suggesting that this is a better strategy than just reverting 
> your library to before fi was introduced, or waiting for a fix, but a 
> possibility perhaps?
> 
> cheers,
> Jack
> 
> On 26 Sep 2013 12:12, "Gary, Dale E."  wrote:
> Hi Andrew,
> 
> We are desperate to complete a design by this week in order to support our 
> software development team over the weekend, but we are stuck right now due to 
> this issue.  If you do manage to find a work-around and can provide a block 
> update, please let us know.
> 
> Many Thanks,
> Dale
> 
> 
> On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens  wrote:
> Hi Dave
> 
> I use fi to convert coefficients to be stored from parallel matlab double 
> precision format into single unsigned words that will accurately be converted 
> back by slicing and using convert blocks. I think it is possible to create 
> the same functionality, I will have a quick try.
> 
> Cheers
> Andrew
> 
> 
> Hi, Andrew,
> 
> Can you elaborate on how you use fi?  I think much of the functionality can 
> be accomplished by judicious use of the multiplication, rounding, and modulo 
> math (for wrapping) or "x(x>max)=max" (for saturation).  It might be possible 
> to create a "clean room" replacement function that does what you need.
> 
> Thanks,
> Dave
> 
> On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
> 
> Hi
> 
> Thanks Andrew! Would you know approximately how much time it would take for 
> you to look into this? Meanwhile, would you know the latest commit that does 
> not use fi, and hence, does not need Floating-point toolbox?
> 
> Replacing fi will be difficult. I will probably rather provide a parameter 
> that allows the user to choose not to pack coefficients next to each other in 
> the same BRAM (which fi is part of now). This will allow the user to trade 
> off BRAM for license fees :)
> 
> The last commit not using fi would be before my FFT upgrade, so somewhere 
> near the first quarter of the year.
> 
> Regards
> Andrew
> 
> Thanks,
> 
> Nimish
> 
> 
> On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon  
> wrote:
> Thanks, Andrew!
> 
> Dave
> 
> On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:
> 
> Hi
> 
> I do use the fi constructor to generate fixed point values when generating 
> twiddle values for storage.
> 
> I will see if it can be done in another way as it seems wasteful to require a 
> license just for that.
> 
> Regards
> Andrew
> 
> 
> Thanks, Nimish,
> 
> Looking at the recently updated casper-astro repository, the following mask 
> init scripts use the "fi" function (technically a "constructor", I think) to 
> crete fixed point objects:
> 
> casper_library/cosin_init.m
> casper_library/feedback_osc_init.m
> casper_library/pfb_fir_coeff_gen_init.m
> 
> Any block that uses the scripts (e.g. via sub-blocks) will probably need a 
> Fixed Point Toolbox license.  I suspect it wouldn't be too difficult to 
> rewrite these files in a way that maintain the functionality, but avoids the 
> "fi" (and any related) call(s).
> 
> It looks like Andrew Martens introduced at least some of the "fi" 
> dependencies, so maybe he would be willing to redo the relevant bits of these 
> files?
> 
> Dave
> 
> On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
> 
> Some more investigation:
> 
> I am seeing these messages:
> 
> License checkout failed.
> License Manager Error -5
> Cannot find a license for Fixed_Point_Toolbox.
> 
> Troubleshoot this issue by visiting:
> http://www.mathworks.com/support/lme/R2012b/5
> 
> Diagnostic Information:
> Feature: Fixed_Point_Toolbox
> License path: 
> /home/observer/.matlab/R2012b_licenses:/home/observer/tools/MATLAB/R2012b/licenses/license.dat:/home/observer/tools/MATLAB/R2012b/licenses/license_fpgadev_277254_R2012b.lic
> Licensing error: -5,357.
> Simulink:Masking:Bad_Init_Commands: Error in 
> 'fft_wideband_real_core/fft_wideband_real/fft_direct/butterfly0_0/twiddle/coeff_gen/feedback_osc':
>  Initialization commands cannot be evaluated.
> Backtrace 

Re: [casper] Matlab components for toolflow

[Jack Hickish]

If you send the parameters to me I'll give it a go
On 26 Sep 2013 16:32, "Nimish Sane"  wrote:

> Thanks Jack! I was thinking of using the black box which was generated
> using earlier toolflow and library, but this may be better. If someone with
> a license is willing to do this, please let me know. I will be happy to
> share the mask parameter configuration.
>
> The most annoying part of this is that even for the 30 day trial version
> of this toolbox, I need to wait for someone to call me within 3 business
> days!
>
> Thanks a lot,
>
> Nimish
>
>
> On Thu, Sep 26, 2013 at 9:28 AM, Jack Hickish wrote:
>
>> If you're really desperate, presumably someone on this list with a
>> license can precompile the fft block for you, which you could then black
>> box? Or generate the block, disable the init script, and send it to you?
>>
>> Not necessarily suggesting that this is a better strategy than just
>> reverting your library to before fi was introduced, or waiting for a fix,
>> but a possibility perhaps?
>>
>> cheers,
>> Jack
>> On 26 Sep 2013 12:12, "Gary, Dale E."  wrote:
>>
>>> Hi Andrew,
>>>
>>> We are desperate to complete a design by this week in order to support
>>> our software development team over the weekend, but we are stuck right now
>>> due to this issue.  If you do manage to find a work-around and can provide
>>> a block update, please let us know.
>>>
>>> Many Thanks,
>>> Dale
>>>
>>>
>>> On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens wrote:
>>>
 Hi Dave

 I use fi to convert coefficients to be stored from parallel matlab
 double precision format into single unsigned words that will accurately be
 converted back by slicing and using convert blocks. I think it is possible
 to create the same functionality, I will have a quick try.

 Cheers
 Andrew


  Hi, Andrew,
>
> Can you elaborate on how you use fi?  I think much of the
> functionality can be accomplished by judicious use of the multiplication,
> rounding, and modulo math (for wrapping) or "x(x>max)=max" (for
> saturation).  It might be possible to create a "clean room" replacement
> function that does what you need.
>
> Thanks,
> Dave
>
> On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
>
>  Hi
>>
>>  Thanks Andrew! Would you know approximately how much time it would
>>> take for you to look into this? Meanwhile, would you know the latest 
>>> commit
>>> that does not use fi, and hence, does not need Floating-point toolbox?
>>>
>>>  Replacing fi will be difficult. I will probably rather provide a
>> parameter that allows the user to choose not to pack coefficients next to
>> each other in the same BRAM (which fi is part of now). This will allow 
>> the
>> user to trade off BRAM for license fees :)
>>
>> The last commit not using fi would be before my FFT upgrade, so
>> somewhere near the first quarter of the year.
>>
>> Regards
>> Andrew
>>
>>  Thanks,
>>>
>>> Nimish
>>>
>>>
>>> On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
>>> dav...@astro.berkeley.edu> wrote:
>>> Thanks, Andrew!
>>>
>>> Dave
>>>
>>> On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:
>>>
>>>  Hi

 I do use the fi constructor to generate fixed point values when
 generating twiddle values for storage.

 I will see if it can be done in another way as it seems wasteful to
 require a license just for that.

 Regards
 Andrew


  Thanks, Nimish,
>
> Looking at the recently updated casper-astro repository, the
> following mask init scripts use the "fi" function (technically a
> "constructor", I think) to crete fixed point objects:
>
> casper_library/cosin_init.m
> casper_library/feedback_osc_**init.m
> casper_library/pfb_fir_coeff_**gen_init.m
>
> Any block that uses the scripts (e.g. via sub-blocks) will
> probably need a Fixed Point Toolbox license.  I suspect it wouldn't 
> be too
> difficult to rewrite these files in a way that maintain the 
> functionality,
> but avoids the "fi" (and any related) call(s).
>
> It looks like Andrew Martens introduced at least some of the "fi"
> dependencies, so maybe he would be willing to redo the relevant bits 
> of
> these files?
>
> Dave
>
> On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
>
>  Some more investigation:
>>
>> I am seeing these messages:
>>
>> License checkout failed.
>> License Manager Error -5
>> Cannot find a license for Fixed_Point_Toolbox.
>>
>> Troubleshoot this issue by visiting:
>> http://www.mathworks.com/**suppor

Re: [casper] Matlab components for toolflow

[Nimish Sane]

Thanks Jack! I was thinking of using the black box which was generated
using earlier toolflow and library, but this may be better. If someone with
a license is willing to do this, please let me know. I will be happy to
share the mask parameter configuration.

The most annoying part of this is that even for the 30 day trial version of
this toolbox, I need to wait for someone to call me within 3 business days!

Thanks a lot,

Nimish


On Thu, Sep 26, 2013 at 9:28 AM, Jack Hickish  wrote:

> If you're really desperate, presumably someone on this list with a license
> can precompile the fft block for you, which you could then black box? Or
> generate the block, disable the init script, and send it to you?
>
> Not necessarily suggesting that this is a better strategy than just
> reverting your library to before fi was introduced, or waiting for a fix,
> but a possibility perhaps?
>
> cheers,
> Jack
> On 26 Sep 2013 12:12, "Gary, Dale E."  wrote:
>
>> Hi Andrew,
>>
>> We are desperate to complete a design by this week in order to support
>> our software development team over the weekend, but we are stuck right now
>> due to this issue.  If you do manage to find a work-around and can provide
>> a block update, please let us know.
>>
>> Many Thanks,
>> Dale
>>
>>
>> On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens  wrote:
>>
>>> Hi Dave
>>>
>>> I use fi to convert coefficients to be stored from parallel matlab
>>> double precision format into single unsigned words that will accurately be
>>> converted back by slicing and using convert blocks. I think it is possible
>>> to create the same functionality, I will have a quick try.
>>>
>>> Cheers
>>> Andrew
>>>
>>>
>>>  Hi, Andrew,

 Can you elaborate on how you use fi?  I think much of the functionality
 can be accomplished by judicious use of the multiplication, rounding, and
 modulo math (for wrapping) or "x(x>max)=max" (for saturation).  It might be
 possible to create a "clean room" replacement function that does what you
 need.

 Thanks,
 Dave

 On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:

  Hi
>
>  Thanks Andrew! Would you know approximately how much time it would
>> take for you to look into this? Meanwhile, would you know the latest 
>> commit
>> that does not use fi, and hence, does not need Floating-point toolbox?
>>
>>  Replacing fi will be difficult. I will probably rather provide a
> parameter that allows the user to choose not to pack coefficients next to
> each other in the same BRAM (which fi is part of now). This will allow the
> user to trade off BRAM for license fees :)
>
> The last commit not using fi would be before my FFT upgrade, so
> somewhere near the first quarter of the year.
>
> Regards
> Andrew
>
>  Thanks,
>>
>> Nimish
>>
>>
>> On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
>> dav...@astro.berkeley.edu> wrote:
>> Thanks, Andrew!
>>
>> Dave
>>
>> On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:
>>
>>  Hi
>>>
>>> I do use the fi constructor to generate fixed point values when
>>> generating twiddle values for storage.
>>>
>>> I will see if it can be done in another way as it seems wasteful to
>>> require a license just for that.
>>>
>>> Regards
>>> Andrew
>>>
>>>
>>>  Thanks, Nimish,

 Looking at the recently updated casper-astro repository, the
 following mask init scripts use the "fi" function (technically a
 "constructor", I think) to crete fixed point objects:

 casper_library/cosin_init.m
 casper_library/feedback_osc_**init.m
 casper_library/pfb_fir_coeff_**gen_init.m

 Any block that uses the scripts (e.g. via sub-blocks) will probably
 need a Fixed Point Toolbox license.  I suspect it wouldn't be too 
 difficult
 to rewrite these files in a way that maintain the functionality, but 
 avoids
 the "fi" (and any related) call(s).

 It looks like Andrew Martens introduced at least some of the "fi"
 dependencies, so maybe he would be willing to redo the relevant bits of
 these files?

 Dave

 On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:

  Some more investigation:
>
> I am seeing these messages:
>
> License checkout failed.
> License Manager Error -5
> Cannot find a license for Fixed_Point_Toolbox.
>
> Troubleshoot this issue by visiting:
> http://www.mathworks.com/**support/lme/R2012b/5
>
> Diagnostic Information:
> Feature: Fixed_Point_Toolbox
> License path: /home/observer/.matlab/R2012b_**
> licenses:/home/observer/tools/**MATLAB/R2012b/licenses/**

Re: [casper] Matlab components for toolflow

[Jack Hickish]

If you're really desperate, presumably someone on this list with a license
can precompile the fft block for you, which you could then black box? Or
generate the block, disable the init script, and send it to you?

Not necessarily suggesting that this is a better strategy than just
reverting your library to before fi was introduced, or waiting for a fix,
but a possibility perhaps?

cheers,
Jack
On 26 Sep 2013 12:12, "Gary, Dale E."  wrote:

> Hi Andrew,
>
> We are desperate to complete a design by this week in order to support our
> software development team over the weekend, but we are stuck right now due
> to this issue.  If you do manage to find a work-around and can provide a
> block update, please let us know.
>
> Many Thanks,
> Dale
>
>
> On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens  wrote:
>
>> Hi Dave
>>
>> I use fi to convert coefficients to be stored from parallel matlab double
>> precision format into single unsigned words that will accurately be
>> converted back by slicing and using convert blocks. I think it is possible
>> to create the same functionality, I will have a quick try.
>>
>> Cheers
>> Andrew
>>
>>
>>  Hi, Andrew,
>>>
>>> Can you elaborate on how you use fi?  I think much of the functionality
>>> can be accomplished by judicious use of the multiplication, rounding, and
>>> modulo math (for wrapping) or "x(x>max)=max" (for saturation).  It might be
>>> possible to create a "clean room" replacement function that does what you
>>> need.
>>>
>>> Thanks,
>>> Dave
>>>
>>> On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
>>>
>>>  Hi

  Thanks Andrew! Would you know approximately how much time it would
> take for you to look into this? Meanwhile, would you know the latest 
> commit
> that does not use fi, and hence, does not need Floating-point toolbox?
>
>  Replacing fi will be difficult. I will probably rather provide a
 parameter that allows the user to choose not to pack coefficients next to
 each other in the same BRAM (which fi is part of now). This will allow the
 user to trade off BRAM for license fees :)

 The last commit not using fi would be before my FFT upgrade, so
 somewhere near the first quarter of the year.

 Regards
 Andrew

  Thanks,
>
> Nimish
>
>
> On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
> dav...@astro.berkeley.edu> wrote:
> Thanks, Andrew!
>
> Dave
>
> On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:
>
>  Hi
>>
>> I do use the fi constructor to generate fixed point values when
>> generating twiddle values for storage.
>>
>> I will see if it can be done in another way as it seems wasteful to
>> require a license just for that.
>>
>> Regards
>> Andrew
>>
>>
>>  Thanks, Nimish,
>>>
>>> Looking at the recently updated casper-astro repository, the
>>> following mask init scripts use the "fi" function (technically a
>>> "constructor", I think) to crete fixed point objects:
>>>
>>> casper_library/cosin_init.m
>>> casper_library/feedback_osc_**init.m
>>> casper_library/pfb_fir_coeff_**gen_init.m
>>>
>>> Any block that uses the scripts (e.g. via sub-blocks) will probably
>>> need a Fixed Point Toolbox license.  I suspect it wouldn't be too 
>>> difficult
>>> to rewrite these files in a way that maintain the functionality, but 
>>> avoids
>>> the "fi" (and any related) call(s).
>>>
>>> It looks like Andrew Martens introduced at least some of the "fi"
>>> dependencies, so maybe he would be willing to redo the relevant bits of
>>> these files?
>>>
>>> Dave
>>>
>>> On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
>>>
>>>  Some more investigation:

 I am seeing these messages:

 License checkout failed.
 License Manager Error -5
 Cannot find a license for Fixed_Point_Toolbox.

 Troubleshoot this issue by visiting:
 http://www.mathworks.com/**support/lme/R2012b/5

 Diagnostic Information:
 Feature: Fixed_Point_Toolbox
 License path: /home/observer/.matlab/R2012b_**
 licenses:/home/observer/tools/**MATLAB/R2012b/licenses/**
 license.dat:/home/observer/**tools/MATLAB/R2012b/licenses/**
 license_fpgadev_277254_R2012b.**lic
 Licensing error: -5,357.
 Simulink:Masking:Bad_Init_**Commands: Error in
 'fft_wideband_real_core/fft_**wideband_real/fft_direct/**
 butterfly0_0/twiddle/coeff_**gen/feedback_osc': Initialization
 commands cannot be evaluated.
 Backtrace 1: reuse_block:138
 Backtrace 2: coeff_gen_init:498
 Backtrace 3: reuse_block:51
 Backtrace 4: add_convert_init:496
 Backtrace 5: draw_basic_partial_cycle:407
 Backtrace 6: cosin_init:165
>>>

Re: [casper] Matlab components for toolflow

[Gary, Dale E.]

Hi Andrew,

We are desperate to complete a design by this week in order to support our
software development team over the weekend, but we are stuck right now due
to this issue.  If you do manage to find a work-around and can provide a
block update, please let us know.

Many Thanks,
Dale


On Thu, Sep 26, 2013 at 5:43 AM, Andrew Martens  wrote:

> Hi Dave
>
> I use fi to convert coefficients to be stored from parallel matlab double
> precision format into single unsigned words that will accurately be
> converted back by slicing and using convert blocks. I think it is possible
> to create the same functionality, I will have a quick try.
>
> Cheers
> Andrew
>
>
>  Hi, Andrew,
>>
>> Can you elaborate on how you use fi?  I think much of the functionality
>> can be accomplished by judicious use of the multiplication, rounding, and
>> modulo math (for wrapping) or "x(x>max)=max" (for saturation).  It might be
>> possible to create a "clean room" replacement function that does what you
>> need.
>>
>> Thanks,
>> Dave
>>
>> On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:
>>
>>  Hi
>>>
>>>  Thanks Andrew! Would you know approximately how much time it would take
 for you to look into this? Meanwhile, would you know the latest commit that
 does not use fi, and hence, does not need Floating-point toolbox?

  Replacing fi will be difficult. I will probably rather provide a
>>> parameter that allows the user to choose not to pack coefficients next to
>>> each other in the same BRAM (which fi is part of now). This will allow the
>>> user to trade off BRAM for license fees :)
>>>
>>> The last commit not using fi would be before my FFT upgrade, so
>>> somewhere near the first quarter of the year.
>>>
>>> Regards
>>> Andrew
>>>
>>>  Thanks,

 Nimish


 On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon <
 dav...@astro.berkeley.edu> wrote:
 Thanks, Andrew!

 Dave

 On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:

  Hi
>
> I do use the fi constructor to generate fixed point values when
> generating twiddle values for storage.
>
> I will see if it can be done in another way as it seems wasteful to
> require a license just for that.
>
> Regards
> Andrew
>
>
>  Thanks, Nimish,
>>
>> Looking at the recently updated casper-astro repository, the
>> following mask init scripts use the "fi" function (technically a
>> "constructor", I think) to crete fixed point objects:
>>
>> casper_library/cosin_init.m
>> casper_library/feedback_osc_**init.m
>> casper_library/pfb_fir_coeff_**gen_init.m
>>
>> Any block that uses the scripts (e.g. via sub-blocks) will probably
>> need a Fixed Point Toolbox license.  I suspect it wouldn't be too 
>> difficult
>> to rewrite these files in a way that maintain the functionality, but 
>> avoids
>> the "fi" (and any related) call(s).
>>
>> It looks like Andrew Martens introduced at least some of the "fi"
>> dependencies, so maybe he would be willing to redo the relevant bits of
>> these files?
>>
>> Dave
>>
>> On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:
>>
>>  Some more investigation:
>>>
>>> I am seeing these messages:
>>>
>>> License checkout failed.
>>> License Manager Error -5
>>> Cannot find a license for Fixed_Point_Toolbox.
>>>
>>> Troubleshoot this issue by visiting:
>>> http://www.mathworks.com/**support/lme/R2012b/5
>>>
>>> Diagnostic Information:
>>> Feature: Fixed_Point_Toolbox
>>> License path: /home/observer/.matlab/R2012b_**
>>> licenses:/home/observer/tools/**MATLAB/R2012b/licenses/**
>>> license.dat:/home/observer/**tools/MATLAB/R2012b/licenses/**
>>> license_fpgadev_277254_R2012b.**lic
>>> Licensing error: -5,357.
>>> Simulink:Masking:Bad_Init_**Commands: Error in
>>> 'fft_wideband_real_core/fft_**wideband_real/fft_direct/**
>>> butterfly0_0/twiddle/coeff_**gen/feedback_osc': Initialization
>>> commands cannot be evaluated.
>>> Backtrace 1: reuse_block:138
>>> Backtrace 2: coeff_gen_init:498
>>> Backtrace 3: reuse_block:51
>>> Backtrace 4: add_convert_init:496
>>> Backtrace 5: draw_basic_partial_cycle:407
>>> Backtrace 6: cosin_init:165
>>> Backtrace 7: xlUpdateIcon:207
>>> Backtrace 8: xlBlockLoadCallback:79
>>> Backtrace 9: UpdateDiagramCB:221
>>>
>>> If I turn OFF the option "Generate coeffs with multipliers where
>>> useful", these messages do not appear. Still, I get the following error:
>>> Error in 'fft_wideband_real_core/fft_**
>>> wideband_real/fft_biplex_real_**4x/biplex_core/fft_stage_10/**
>>> butterfly_direct/twiddle/**coeff_gen': Initialization commands
>>> cannot be evaluated.
>>>
>>>
>>> Caused by:
>>> Error in 'fft_wideband_real_core/fft_**
>>>

Re: [casper] Matlab components for toolflow

[Andrew Martens]

Hi Dave

I use fi to convert coefficients to be stored from parallel matlab 
double precision format into single unsigned words that will accurately 
be converted back by slicing and using convert blocks. I think it is 
possible to create the same functionality, I will have a quick try.


Cheers
Andrew


Hi, Andrew,

Can you elaborate on how you use fi?  I think much of the functionality can be accomplished by 
judicious use of the multiplication, rounding, and modulo math (for wrapping) or 
"x(x>max)=max" (for saturation).  It might be possible to create a "clean room" 
replacement function that does what you need.

Thanks,
Dave

On Sep 25, 2013, at 7:36 AM, Andrew Martens wrote:


Hi


Thanks Andrew! Would you know approximately how much time it would take for you 
to look into this? Meanwhile, would you know the latest commit that does not 
use fi, and hence, does not need Floating-point toolbox?


Replacing fi will be difficult. I will probably rather provide a parameter that 
allows the user to choose not to pack coefficients next to each other in the 
same BRAM (which fi is part of now). This will allow the user to trade off BRAM 
for license fees :)

The last commit not using fi would be before my FFT upgrade, so somewhere near 
the first quarter of the year.

Regards
Andrew


Thanks,

Nimish


On Wed, Sep 25, 2013 at 1:24 AM, David MacMahon  
wrote:
Thanks, Andrew!

Dave

On Sep 24, 2013, at 10:13 PM, Andrew Martens wrote:


Hi

I do use the fi constructor to generate fixed point values when generating 
twiddle values for storage.

I will see if it can be done in another way as it seems wasteful to require a 
license just for that.

Regards
Andrew



Thanks, Nimish,

Looking at the recently updated casper-astro repository, the following mask init scripts use the 
"fi" function (technically a "constructor", I think) to crete fixed point 
objects:

casper_library/cosin_init.m
casper_library/feedback_osc_init.m
casper_library/pfb_fir_coeff_gen_init.m

Any block that uses the scripts (e.g. via sub-blocks) will probably need a Fixed Point 
Toolbox license.  I suspect it wouldn't be too difficult to rewrite these files in a way 
that maintain the functionality, but avoids the "fi" (and any related) call(s).

It looks like Andrew Martens introduced at least some of the "fi" dependencies, 
so maybe he would be willing to redo the relevant bits of these files?

Dave

On Sep 24, 2013, at 5:00 PM, Nimish Sane wrote:


Some more investigation:

I am seeing these messages:

License checkout failed.
License Manager Error -5
Cannot find a license for Fixed_Point_Toolbox.

Troubleshoot this issue by visiting:
http://www.mathworks.com/support/lme/R2012b/5

Diagnostic Information:
Feature: Fixed_Point_Toolbox
License path: 
/home/observer/.matlab/R2012b_licenses:/home/observer/tools/MATLAB/R2012b/licenses/license.dat:/home/observer/tools/MATLAB/R2012b/licenses/license_fpgadev_277254_R2012b.lic
Licensing error: -5,357.
Simulink:Masking:Bad_Init_Commands: Error in 
'fft_wideband_real_core/fft_wideband_real/fft_direct/butterfly0_0/twiddle/coeff_gen/feedback_osc':
 Initialization commands cannot be evaluated.
Backtrace 1: reuse_block:138
Backtrace 2: coeff_gen_init:498
Backtrace 3: reuse_block:51
Backtrace 4: add_convert_init:496
Backtrace 5: draw_basic_partial_cycle:407
Backtrace 6: cosin_init:165
Backtrace 7: xlUpdateIcon:207
Backtrace 8: xlBlockLoadCallback:79
Backtrace 9: UpdateDiagramCB:221

If I turn OFF the option "Generate coeffs with multipliers where useful", these 
messages do not appear. Still, I get the following error:
Error in 
'fft_wideband_real_core/fft_wideband_real/fft_biplex_real_4x/biplex_core/fft_stage_10/butterfly_direct/twiddle/coeff_gen':
 Initialization commands cannot be evaluated.


Caused by:
Error in 
'fft_wideband_real_core/fft_wideband_real/fft_biplex_real_4x/biplex_core/fft_stage_10/butterfly_direct/twiddle/coeff_gen/cosin':
 Initialization commands cannot be evaluated.

Unable to check out a license for the Fixed-Point Toolbox.





I will let you know if I find something more.


Thanks,




Nimish







On Tue, Sep 24, 2013 at 7:36 PM, David MacMahon  
wrote:
Thanks.  I was hoping to narrow it down a little more than that.  There's a lot 
of stuff inside that little green block!

Dave

On Sep 24, 2013, at 4:33 PM, Nimish Sane wrote:


To be precise, that is the only green block in the design apart from bunch of 
gateway blocks and XSG block (as I am black boxing it).

Thanks,

Nimish


On Tue, Sep 24, 2013 at 7:32 PM, Nimish Sane  wrote:
The design only has fft_wideband_real block, and whenever I click "Apply/Ok" or 
"Update Diagram", I get these error messages. These are the only error messages I see in 
Matlab window. So it is definitely the fft_wideband_real block.

Thanks,

Nimish


On Tue, Sep 24, 2013 at 7:30 PM, David MacMahon  
wrote:
Thanks, Nimish,

Is there any other info that might help pinpoint which block and/or init script 
is causing Matlab to look for a Fixed_Point_T