Morning Tom The init scripts for the PFB weren't actually ever telling you that you had an error. Now they do. So you will see some error messages if you open a design with the old PFB block. And unfortunately, the way the init scripts are called, you may see the popup more than a few times. So delete the PFB block and replace it with the one from the library and you should be okay.
Regards Paul On 5 April 2012 01:29, Tom Kuiper <[email protected]> wrote: > ** > Hi Jason! > > I recently got an account on a machine at JPL that has the CASPER toolflow > running under Red Hat. It has ISE 13.4. I got the SKA-SA mlib_devel > library and put it in my home directory. I started Simulink after adding > this library to the Matlab search path. Then I loaded the r_spec_1ghz > model. It came up with none of the blocks connected and an error message > pop-up about some vector having width 0 instead of 16. (Sorry to be vague > but my notes are at work and I'm not.) I OK'ed that and then tried to > update the diagram. That got me an unending set of error pop-ups. I had > to log in from another computer and kill all my MATLAB processes. > > Do you have any thoughts about this? > > Thanks and regards > > Tom > > > On 03/05/2012 12:02 AM, Jason Manley wrote: > > For those interested, here is a design similar to tut3 for the katADC... > > Attached is an example of an RFI monitoring system that we used last year > to do some electric fence measurements, along with some basic software to > control it. Apologies for the messy nature... it was thrown together rather > hurriedly. Still, it should demonstrate most of what you want. It uses the > KATADC in interleaved mode to give a ~900MHz band from a 900MHz, 0dBm clock > source. > > There is a katadc yellow block in the SKA-SA mlib_devel library and I > think it's already made its way into the "stable", standard CASPER library. > Get ours here: https://github.com/ska-sa/mlib_devel > > The yellow block initialises the ADC and everything automatically, so you > shouldn't need anything else in the way of software to configure it. But if > you want to play with it, the katadc control software resides in corr (the > packetised correlator control package), available on pypi: > http://pypi.python.org/pypi/corr or get the bleeding-edge version here: > https://github.com/ska-sa/corr/. CORR's probably got a lot more in there > than you need but you can rip-out the bits you want (see src/katadc). > > Jason > > PS: > to use the included software, run rfi_init.py, then run either rfi_spec or > rfi_time.py to bring up some plots. Try 'em with the -h flag to see > command-line options. You will need corr installed to make this lot work > and you'll also need to modify line 13 in src/cam.py to reflect your > roach's IP address. You can also add antenna calibration files and things > to take calibrated electric field measurements so this is a useful little > instrument. > > > > > On 04 Mar 2012, at 21:38, Tom Kuiper wrote: > > > I would like to test a set-up that I've just configured. I've got a > KatADC in Z-Doc 0 of a ROACH-1. The signal is going into IF 0. Pretty > much anything will do, though. It's easy to swap Z-Docs and IF inputs, so > that's not a constraint. > > > > Even the first stage of a FX correlator would be fine. The ROACH is > connected to a computer with a 10 GBe card and there are two GPU enabled > computers, also with 10 GBe ports, on the same subnet. > > > > The KatADC version of Workshop 2010 Tutorial 3 is nice because it has a > graphical output that shows everything is working, i.e., I don't have to do > anymore work :-) . > > > > Thanks and regards, > > > > Tom > > > > -- > > I or me? http://www.oxforddictionaries.com/page/145 > > > > > > > > > > -- > I or me? http://www.oxforddictionaries.com/page/145 > >
