Re: [casper] ROACH2 4-element correlator compilation error

2018-01-29 Thread Jack Hickish
Hi Bela, You might try increasing the Java heap size - https://www.mail-archive.com/casper@lists.berkeley.edu/msg04642.html - that's been known to help in some cases. Cheers Jack On Mon, Jan 29, 2018, 11:50 PM James Smith wrote: > So updating the diagram at the moment

Re: [casper] ROACH2 4-element correlator compilation error

2018-01-29 Thread James Smith
So updating the diagram at the moment produces no error, and you can see the datatypes on the wires? On Tue, Jan 30, 2018 at 9:49 AM, Bela Dixit wrote: > hie James, > I was getting some errors related to block, I corrected that error. > After that it was proceeding but

Re: [casper] ROACH2 4-element correlator compilation error

2018-01-29 Thread Bela Dixit
hie James, I was getting some errors related to block, I corrected that error. After that it was proceeding but while synthesizing it stuck. Thanks & Regards, Bela Bela Dixit Electronics and Telecommunication engg(digital system) On Tue, Jan 30, 2018 at 1:07 PM, James Smith

Re: [casper] ROACH2 4-element correlator compilation error

2018-01-29 Thread James Smith
Hello Bela, That is a bit long - what happens if you just do Ctrl+D? Does it return any messages? I also find that on Simulink if you select *Display -> Signals & Ports -> Port Data Types *it produces a more useful result. Regards, James On Tue, Jan 30, 2018 at 9:33 AM, Bela Dixit

Re: [casper] ROACH2 4-element correlator compilation error

2018-01-29 Thread Bela Dixit
Hie James, I have waited around 7 to 9 hours, still I am getting same warnings. Thanks & Regards, Bela On Tue, Jan 30, 2018 at 12:22 PM, James Smith wrote: > Hello Bela, > > That looks fine - there are normally lots of warnings. You just need to > wait, these compiles

Re: [casper] ROACH2 4-element correlator compilation error

2018-01-29 Thread James Smith
Hello Bela, That looks fine - there are normally lots of warnings. You just need to wait, these compiles can take several hours sometimes depending on their complexity. Average for mine have been 1.5-2 hours. Regards, James On Tue, Jan 30, 2018 at 8:48 AM, Bela Dixit

Re: [casper] Writing calibrated data to QDR of ROACH2

2018-01-29 Thread Homin Jiang
Thanks, Jack. I have done it by myself. I grabbed the derived the parameters, then use "qdr_apply" in "qdr.py" to write those parameters back to ROACH2s every times after power cycled. It works fine, best homin On Tue, Jan 30, 2018 at 4:33 AM, Jack Hickish wrote: > Hi

Re: [casper] Writing calibrated data to QDR of ROACH2

2018-01-29 Thread Jack Hickish
Hi Homin, No-one replied to this, so i'll bite. In principle you could do this, but there is no canned way to obtain/save/reload the calibrations. They are implemented by stepping some MMCMs (rather than a register containing fixed offsets) so you'd have to count the steps during calibration, and

Re: [casper] sharing CASPER equipment

2018-01-29 Thread David MacMahon
To further John's comments, Breakthrough Listen has a completely separate set of HPC servers installed at Green Bank that are connected to the same Ethernet switch as the ROACH2s and the VEGAS spectrometer's HPC servers. When using the BL backend, up to 4 of the 8 ROACH2s are configured to

Re: [casper] sharing CASPER equipment

2018-01-29 Thread John Ford
Hi Tom. I think this is reasonably easy to manage. At Green Bank, the spectrometer consists of 8 ROACH-2s that are all reprogrammed for different observing modes. The modes are personalities stored on disk and loaded on command. It works fine. You do have to coordinate to make sure only one