Hi all. For what it's worth, I just cloned the git tree from berkeley with:
git clone git://casper.berkeley.edu/mlib_devel.git and it works fine, as far as a quick test. I instantiated an fft_biplex_real_2x block, and a fft_wideband_real, and they ran fine, and are OK under the mask. My installation matches the signatures that David speaks of below, except there's an "8" missing off the end of the casper_library.mdl hash. It should be 27e1f49f5af8933300b0441c9da6c253e10066f8 At any rate, it works for me. :) John > Hi, Andrea, > > On Sep 1, 2010, at 6:10 , Andrea Mattana wrote: > >> ??? Error using ==> reuse_block at 42 >> biplex_core block (mask) does not have a parameter named >> 'conv_latency'. > > This is very helpful. This tells us (at the risk of restating the > obvious) that the init scripts are trying to set the 'conv_latency' > mask parameter of the biplex_core block, but the biplex_core block it > is using does not have this parameter. I just started a totally new > model, added an fft_biplex_real_2x block, and it worked fine. This > was using the 10.1 tools and the latest mlib_devel.git version > (eab23d2fcb8e1f89db697edad8d3ec9fba7c8c50). If you look under the > mask of the fft_biplex_real_2x block, select the biplex_core block, > and choose "Edit|Edit Mask..." (or type CTRL-M), you should see the > conv_latency parameter in the mask parameters (see attached image). > > Is it possible that your library browser is picking up an older > casper_library.mdl file from somewhere else on your system? You can > run "which --all casper_library" and you should see only one > casper_library.mdl listed. Based on your earlier message, I suspect > that the casper_library.mdl file that you want to be using is in... > > /usr/local/hdl/casper/mlib_devel/casper_library/casper_library.mdl > > You can also check this by opening the "CASPER DSP Blockset" (right- > click on the name in the library browser) and then selecting "File| > Properties...". You should be able to find the full path of the > source file in the displayed dialog. (This is based on Windows; I am > not sure if it is the same on Linux.) > > If you are using the casper_library.mdl file from a directory that > you think should be OK, the next step would be to verify that it > really is what you think it is. You can try things like... > > $ cd /usr/local/hdl/casper/mlib_devel > > $ git status > > $ git branch -av > > $ git log -10 --oneline casper_library/casper_library.mdl > > $ git hash-object casper_library/casper_library.mdl > > If you are using the latest from mlib_devel.git (i.e. > eab23d2fcb8e1f89db697edad8d3ec9fba7c8c50), the last two commands will > give... > > $ git log -10 --oneline casper_library/casper_library.mdl > 6f87da3 Fix Misc/armed_trigger block > 2d0bf0e Improve fft_biplex_real_2x block > 05b6b95 Change latency in fft_biplex_real_2x/bi_real_unscr_2x > ad2e026 Fix WGN source and begin split of casper_library > fbbe3cb X engine cross-polarisation correction > d60fff2 mods to xengine block in casper library > 1967df0 bugfixes to x engine. > 914d207 X engine mods to support 4antennas (special case). > 1ab1a14 pfb_fir_real conv_latency parameter added > a03d785 large fft fix and clean-up > > $ git hash-object casper_library/casper_library.mdl > 27e1f49f5af8933300b0441c9da6c253e10066f > > If you still can't resolve the problem, please email the output of > all the above git commands. If this does resolve the problem, please > send the clues you used to figure it out to the list so future users > can benefit. > > Thanks, > Dave > >
