To add to what Dave has said. I found that having no control over the
relative size and placement of the blocks when using xBlocks made it hard
to see what was happening, making the design write-only and hard to debug.
Generating scipts can be tedious though. The mdl2m.m script in the
casper_libra
Hi David, and list,
The slack group is called casper-astro. Please drop me an email if you want
to be invited!
Cheers
Jack
On Fri, 30 Aug 2019, 3:31 pm Forbes, David C - (dforbes), <
dfor...@email.arizona.edu> wrote:
> Hi,
>
>
>
> I never wrote down the names of the Slack chat groups for the CA
I could be wrong, but as I recall, the block diagrams created via xBlocks were
(at least at the time) not very conducive to visualizing the structure of the
diagrams (e.g. lots of lines/traces overlaid on top of each other). This was
not a serious problem when everything worked as it should, bu
Hi,
I never wrote down the names of the Slack chat groups for the CASPER projects.
I'd like to join.
Are these written anywhere that I could find them? I looked on the CASPER
website with no luck .
David Forbes Steward Observatory / ARO
University of Arizonadfor...@ema
i don't know much about xblocks, so can't add much to jack's comments,
except:
about a dozen years ago chris dick and others at xilinx recommended casper
use xblocks,
so hong chen tried it out, and ported several of the casper dsp blocks.
i think it worked well, and hong chen liked xblocks, but i
Or.. move to verilog/VHDL and use black boxes? :)
On Fri, 30 Aug 2019 at 14:14, Franco 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 deb
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
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
Hi Nikita,
On line 91 you define `rply` to be a list of 16 empty lists, then on
line 148 you try to write in a loop to 64 elements of `rply`. But
there are only 16, so your script errors.
As an aside, you could achieve the same as:
rply = [[],[],[], ]
with
rply = [[] for i in range(16)]
which
Hi all,
I'm testing the tut_spec with a redpitaya (14bits) using just the
example from the tutorial "python tut_spec.py -f tut_spec.fpg -r
rp-xx.local " and I get an error on the line
spec0=fpga.snapshots.accum0_snap_ss.read(arm=False)['data']
...
(from snap.py) RuntimeError: accum0_snap_ss.r
Dear Casperites
I am working on Roach2 and 5Gsps ADC1x5000-8.
During data acquisition for 4 element interferometer I am having following
issue in python code. I want to plot and record all the 6 baselines at a
time from a single python file.
please find the attached python code file.
Kindly hel
11 matches
Mail list logo