Or...... move to verilog/VHDL and use black boxes? :) On Fri, 30 Aug 2019 at 14:14, Franco <[email protected]> wrote: > > Hi Jack, > > I see. We actually found problems when trying to script xBlocks within an > xBlock, we got some weird block connection error, but I guess that is > something solvable with some debugging. We'll evaluate if we stay with xBlock > scripting or we switch back to standard simulink scripting. > > Thanks for the info! > > Franco > > On Fri, Aug 30, 2019 at 4:39 PM Jack Hickish <[email protected]> wrote: >> >> Hi Franco, >> >> I don't think there's any reason not to use xblocks. Someone can >> correct me if I'm wrong. >> >> Several years ago there was a quest to move the whole casper library >> to xblocks -- https://github.com/casper-astro/xblocks_devel/ -- but it >> never seemed to get traction and the original libraries won over. I >> suspect had the project been more aggressive about just replacing the >> casper libraries it would have caught on. >> >> Cheers >> Jack >> >> On Thu, 29 Aug 2019 at 12:34, Franco <[email protected]> wrote: >> > >> > Dear Casperites, >> > >> > I've recently been playing around with the creation of block libraries and >> > I found out about Xilinx's API for programmatic model creation (xBlock). I >> > find it particularly convenient because you don't have to explicitly >> > position the blocks, as the software does all the positioning for you, and >> > for what I tested the results are pretty nice. >> > >> > However when I checked in the CASPER library, only a few blocks are >> > created using xBlock, and moreover, some blocks where re-implemented from >> > xBlock to standard Matlab block scripting. >> > >> > So my question is: is there any reason why I should avoid using xBlock? >> > The only inconvenient I have had with it for now is that you have to >> > install some additional libraries in Linux to make it work, which I didn't >> > find it documented anywhere. >> > >> > Thanks, >> > >> > Franco Curotto >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "[email protected]" group. >> > To unsubscribe from this group and stop receiving emails from it, send an >> > email to [email protected]. >> > To view this discussion on the web visit >> > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CACBfcEmKHeDGr5ny5HH2ruqvHgYr-VbNbyyPjpJz5eR1C-JaRA%40mail.gmail.com. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKSn%2Bgy-f4HFRXYsNAoheHDJxYA_EzFcXyxUgwnM_STxWtA%40mail.gmail.com. > > -- > You received this message because you are subscribed to the Google Groups > "[email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CACBfcEmHFEofvwv%3DqP1bvtaEdsx2hm-RKtXAFtEQ5vQ2ahsL3A%40mail.gmail.com.
-- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKSk-sEz1g-33Yom5K6XOoGSjODdW7uvgbrmvHG4NO9ZZjw%40mail.gmail.com.
