Re: [casper] RA Instruments using CASPER hardware and tools

[Spiro Sarris]

NARIT (National Astronomical Research Institute of Thailand) has a
SKARAB+ADC4x3Gsps installed at TNRT (Thai National Radio Telescope).
 Development is in progress to use it for a variety of purposes including
spectrometer, packetizer, and PFB channelizer.
-Spiro

On Wed, 2022-08-31 at 12:53 +0200, Morag Brown wrote:
> Ciao dalla Sardegna, collaborati!
> 
> I'm hoping to put together a more up-to-date list of instruments that have
> been built using CASPER hardware and tools. The most current list was compiled
> in 2016 for the "A Decade of Developing Radio-Astronomy Instrumentation using
> CASPER Open-Source Technology" paper by Jack et al, so it could probably
> use updating.
> 
> The list is currently as follows: 
> 
> Spectrometers and packetizers -
> Fly’s Eye
> GUPPY
> CASPER
> BPSR
> GAVRT
> SERENDIP V.v
> HiTREKS
> NUPPI
> Skynet
> RATTY
> cycSpec
> C-BASS
> HIPSTER
> KuPol
> VEGAS
> ALMA Phasing Project
> Leuschner
> R2DBE
> DSN Transient Observatory
> VGOS
> AVN-Ghana
> COMAP
> 
> MKID readout systems -
> Columbia MKID
> Mustang2
> DARKNESS
> MEC
> BLAST-TNG
> HOLMES
> 
> Correlators and beamformers -
> KAT7
> PAPER
> ATA
> LEDA
> ARI
> MAD
> pocketcorr
> Medicina FFTT
> GMRT
> Meteor
> AMI
> MeerKAT AR-1
> FLAG
> BIRALES
> Starburst
> AMiBA
> EOVSA
> SWARM
> MeerKAT
> HERA
> 
> If you are not (or know of any instruments that are not) on this list, please
> reach out to me for it to be added?
> 
> Grazie!
> Morag
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups
> "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
> .

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/0fbde0a2fc94bab611e4315b8713bf9d9c56980c.camel%40gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools

[Adam Isaacson]

Ciao Morag,

Not Radio Astronomy, but RADAR this time - FORT (FMCW Optical Radar
Tracker) uses ROACH2 and a version of the CASPER Tools. Mike Movius ran
this project - check out my old company
https://www.reutechradar.com/products/defence/tracking-radar.

Con calore,

Adam



On Wed, Aug 31, 2022 at 5:56 PM Andrea Melis  wrote:

> Hi Morag,
>
> Please add the SARDARA (Sardinia Roach2-based Digital Architecture for
> Radio Astronomy) platform. Details here: SArdinia Roach2-based Digital
> Architecture for Radio Astronomy (SARDARA) | Journal of Astronomical
> Instrumentation (worldscientific.com)
> 
>
> Thanks!
>
> Andrea
>
>
>
> Il giorno mer 31 ago 2022 alle ore 12:53 Morag Brown 
> ha scritto:
>
>> Ciao dalla Sardegna, collaborati!
>>
>> I'm hoping to put together a more up-to-date list of instruments that
>> have been built using CASPER hardware and tools. The most current list was
>> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
>> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
>> so it could probably use updating.
>>
>> The list is currently as follows:
>>
>> *Spectrometers and packetizers -*
>> Fly’s Eye
>> GUPPY
>> CASPER
>> BPSR
>> GAVRT
>> SERENDIP V.v
>> HiTREKS
>> NUPPI
>> Skynet
>> RATTY
>> cycSpec
>> C-BASS
>> HIPSTER
>> KuPol
>> VEGAS
>> ALMA Phasing Project
>> Leuschner
>> R2DBE
>> DSN Transient Observatory
>> VGOS
>> AVN-Ghana
>> COMAP
>>
>> *MKID readout systems -*
>> Columbia MKID
>> Mustang2
>> DARKNESS
>> MEC
>> BLAST-TNG
>> HOLMES
>>
>> *Correlators and beamformers -*
>> KAT7
>> PAPER
>> ATA
>> LEDA
>> ARI
>> MAD
>> pocketcorr
>> Medicina FFTT
>> GMRT
>> Meteor
>> AMI
>> MeerKAT AR-1
>> FLAG
>> BIRALES
>> Starburst
>> AMiBA
>> EOVSA
>> SWARM
>> MeerKAT
>> HERA
>>
>> If you are not (or know of any instruments that are not) on this list,
>> please reach out to me for it to be added?
>>
>> Grazie!
>> Morag
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CALJdLK6yvEmH5rrBXP1kz4WHe%2BvsgqcYWoY8bd9L6WaRLMS9Lw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnGchuKoNEwWcbck8CrZAP6TvF933XR3bCQQ6s1-UswNuQ%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools {External}

[Glen Langston]

Also we created a clone of Guppi, called Wuppi, for West Virginia ultimate 
pulsar processor instrument.
processor that had a few publications, including this one.

This one was running at the old NRAO 140ft in Green Bank.


> 2012ApJ...760...64M2012/11
> cited: 58
> quick access to full text links quick links to lists of references, citations 
> and more quick links to data associated with this article
> A Giant Sample of Giant Pulses from the Crab Pulsar

>   • Mickaliger, M. B.;
>  
>   • McLaughlin, M. A.;
>  
>   • Lorimer, D. R.;
>  
>   • Langston, G. I.;
>  
>   • Bilous, A. V.;
>   • Kondratiev, V. I.;
>  
>   • Lyutikov, M.;
>  
>   • Ransom, S. M.;
>  
>   • Palliyaguru, N.
>  
>   • show lessOn Aug 31, 2022, at 10:22 AM, Scott Ransom 
>  wrote:
> 
> A couple other minor corrections:
> 
> It is GUPPI not "GUPPY".  And there was also PUPPI at Arecibo.  And Maybe 
> CASPER was supposed to be CASPSR?
> 
> Scott
> 
> On 8/31/22 9:59 AM, David Harold Edward MacMahon wrote:
>> SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.  It 
>> may be more correct to call them two backends for the same spectrometer.  
>> These ran at Arecibo.  Greenburst is a version of Alfaburst that is at Green 
>> Bank.
>> There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased 
>> Array Recording Instrument for Galactic Even horizon Studies”, PhRInGES was 
>> a time domain phased array beamformer for CARMA and SMA (two of the first 
>> three EHT sites).
>> Cheers,
>> Dave
>>> On Aug 31, 2022, at 12:53 PM, Morag Brown >> > wrote:
>>> 
>>> Ciao dalla Sardegna, collaborati!
>>> 
>>> I'm hoping to put together a more up-to-date list of instruments that have 
>>> been built using CASPER hardware and tools. The most current list was 
>>> compiled in 2016 for the "A Decade of Developing Radio-Astronomy 
>>> Instrumentation using CASPER Open-Source Technology" paper by Jack et al, 
>>> so it could probably use updating.
>>> 
>>> The list is currently as follows:
>>> 
>>> *Spectrometers and packetizers -*
>>> Fly’s Eye
>>> GUPPY
>>> CASPER
>>> BPSR
>>> GAVRT
>>> SERENDIP V.v
>>> HiTREKS
>>> NUPPI
>>> Skynet
>>> RATTY
>>> cycSpec
>>> C-BASS
>>> HIPSTER
>>> KuPol
>>> VEGAS
>>> ALMA Phasing Project
>>> Leuschner
>>> R2DBE
>>> DSN Transient Observatory
>>> VGOS
>>> AVN-Ghana
>>> COMAP
>>> 
>>> *MKID readout systems -*
>>> Columbia MKID
>>> Mustang2
>>> DARKNESS
>>> MEC
>>> BLAST-TNG
>>> HOLMES
>>> *
>>> *
>>> *Correlators and beamformers -*
>>> KAT7
>>> PAPER
>>> ATA
>>> LEDA
>>> ARI
>>> MAD
>>> pocketcorr
>>> Medicina FFTT
>>> GMRT
>>> Meteor
>>> AMI
>>> MeerKAT AR-1
>>> FLAG
>>> BIRALES
>>> Starburst
>>> AMiBA
>>> EOVSA
>>> SWARM
>>> MeerKAT
>>> HERA
>>> 
>>> If you are not (or know of any instruments that are not) on this list, 
>>> please reach out to me for it to be added?
>>> 
>>> Grazie!
>>> Morag
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "casper@lists.berkeley.edu " group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to casper+unsubscr...@lists.berkeley.edu 
>>> .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>>>  
>>> .
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to casper+unsubscr...@lists.berkeley.edu 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6269C4BB-1F4D-48C3-87EE-62727D9E3175%40berkeley.edu
>>  
>> .
> 
> -- 
> Scott M. RansomAddress:  NRAO
> Phone:  (434) 296-0320   520 Edgemont Rd.
> email:  sran...@nrao.edu Charlottesville, VA 22903 USA
> GPG Fingerprint: A40A 94F2 3F48 4136 3AC4  9598 92D5 25CB 22A6 7B65
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit 
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/e47b3e98-3e5b-94f7-d86f-8532c8aff0c7%40nrao.edu.

-- 
You received this message because you are subscribed to the 

Re: [casper] RA Instruments using CASPER hardware and tools

[Andrea Melis]

Hi Morag,

Please add the SARDARA (Sardinia Roach2-based Digital Architecture for
Radio Astronomy) platform. Details here: SArdinia Roach2-based Digital
Architecture for Radio Astronomy (SARDARA) | Journal of Astronomical
Instrumentation (worldscientific.com)


Thanks!

Andrea



Il giorno mer 31 ago 2022 alle ore 12:53 Morag Brown 
ha scritto:

> Ciao dalla Sardegna, collaborati!
>
> I'm hoping to put together a more up-to-date list of instruments that have
> been built using CASPER hardware and tools. The most current list was
> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
> so it could probably use updating.
>
> The list is currently as follows:
>
> *Spectrometers and packetizers -*
> Fly’s Eye
> GUPPY
> CASPER
> BPSR
> GAVRT
> SERENDIP V.v
> HiTREKS
> NUPPI
> Skynet
> RATTY
> cycSpec
> C-BASS
> HIPSTER
> KuPol
> VEGAS
> ALMA Phasing Project
> Leuschner
> R2DBE
> DSN Transient Observatory
> VGOS
> AVN-Ghana
> COMAP
>
> *MKID readout systems -*
> Columbia MKID
> Mustang2
> DARKNESS
> MEC
> BLAST-TNG
> HOLMES
>
> *Correlators and beamformers -*
> KAT7
> PAPER
> ATA
> LEDA
> ARI
> MAD
> pocketcorr
> Medicina FFTT
> GMRT
> Meteor
> AMI
> MeerKAT AR-1
> FLAG
> BIRALES
> Starburst
> AMiBA
> EOVSA
> SWARM
> MeerKAT
> HERA
>
> If you are not (or know of any instruments that are not) on this list,
> please reach out to me for it to be added?
>
> Grazie!
> Morag
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CALJdLK6yvEmH5rrBXP1kz4WHe%2BvsgqcYWoY8bd9L6WaRLMS9Lw%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools

['Lincoln Greenhill' via casper@lists.berkeley.edu]

Among current instruments, please do add:

Long Wavelength Array Sevilleta (ROACH2) and VLA North Arm (SNAP-2) sites 
(LWA/SV, LWA/NA).


LEDA is a past instrument.  I decommissioned it in Feb. 2020. (ROACH2 & 
ADC16-250/RJ45)


Cosmic Dawn Telescope pathfinder (CDT-pathfinder) is in development.

If you have time, I recommend reaching out to Cynthia Chiang @ McGill 
(hsin.chi...@mcgill.ca) regarding projects on which she is collaborating in the 
Canadian Arctic and southern Indian Ocean.  At the moment, I do not recall 
details with certainty.


All best,
Lincoln




On 8/31/22 10:45 AM, Jonathon Kocz wrote:

On that note, the COMAP system at OVRO also uses ROACH2s.

On Wed, 31 Aug 2022 at 07:37, Vikram Ravi > wrote:


DSA-110 at the Owens Valley Radio Observatory (OVRO) uses 40 SNAP-1 boards
for its f-engine, and the STARE-2 all-sky FRB project also uses a SNAP at
each site.  The SPRITE instrument at OVRO, which is resurrecting a few 10.4m
Leighton dishes, is also using CASPER hardware/toolfllow in multiple places,
including the correlator, lobe rotation, and phase switching.

On Wed, Aug 31, 2022 at 07:21, David Harold Edward MacMahon
mailto:dav...@berkeley.edu>> wrote:

Also, the “Infrared Spatial Interferometer” (ISI) project started by the
late :( Charles Townes uses CASPER hardware.



On Aug 31, 2022, at 3:59 PM, David Harold Edward MacMahon
mailto:dav...@berkeley.edu>> wrote:

SERENDIP VI and Alfaburst were spectrometers that used CASPER
hardware.  It may be more correct to call them two backends for the
same spectrometer.  These ran at Arecibo.  Greenburst is a version of
Alfaburst that is at Green Bank.

There’s also PhRInGES.  Besides being a tortured (b)acronym for
“Phased Array Recording Instrument for Galactic Even horizon Studies”,
PhRInGES was a time domain phased array beamformer for CARMA and SMA
(two of the first three EHT sites).

Cheers,
Dave


On Aug 31, 2022, at 12:53 PM, Morag Brown mailto:mbr...@sarao.ac.za>> wrote:

Ciao dalla Sardegna, collaborati!

I'm hoping to put together a more up-to-date list of instruments that
have been built using CASPER hardware and tools. The most current
list was compiled in 2016 for the "A Decade of Developing
Radio-Astronomy Instrumentation using CASPER Open-Source Technology"
paper by Jack et al, so it could probably use updating.

The list is currently as follows:

*Spectrometers and packetizers -*
Fly’s Eye
GUPPY
CASPER
BPSR
GAVRT
SERENDIP V.v
HiTREKS
NUPPI
Skynet
RATTY
cycSpec
C-BASS
HIPSTER
KuPol
VEGAS
ALMA Phasing Project
Leuschner
R2DBE
DSN Transient Observatory
VGOS
AVN-Ghana
COMAP

*MKID readout systems -*
Columbia MKID
Mustang2
DARKNESS
MEC
BLAST-TNG
HOLMES
*
*
*Correlators and beamformers -*
KAT7
PAPER
ATA
LEDA
ARI
MAD
pocketcorr
Medicina FFTT
GMRT
Meteor
AMI
MeerKAT AR-1
FLAG
BIRALES
Starburst
AMiBA
EOVSA
SWARM
MeerKAT
HERA

If you are not (or know of any instruments that are not) on this
list, please reach out to me for it to be added?

Grazie!
Morag




-- 
You received this message because you are subscribed to the Google

Groups "casper@lists.berkeley.edu "
group.
To unsubscribe from this group and stop receiving emails from it,
send an email to casper+unsubscr...@lists.berkeley.edu
.
To view this discussion on the web visit

https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com

.




-- 
You received this message because you are subscribed to the Google

Groups "casper@lists.berkeley.edu " 
group.
To unsubscribe from this group and stop receiving emails from it, send
an email to casper+unsubscr...@lists.berkeley.edu
.
To view this discussion on the web visit

https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/B8B01FDC-DF32-4E4E-AABF-B493FBC63B73%40berkeley.edu

Re: [casper] RA Instruments using CASPER hardware and tools

[Jonathon Kocz]

On that note, the COMAP system at OVRO also uses ROACH2s.

On Wed, 31 Aug 2022 at 07:37, Vikram Ravi  wrote:

> DSA-110 at the Owens Valley Radio Observatory (OVRO) uses 40 SNAP-1 boards
> for its f-engine, and the STARE-2 all-sky FRB project also uses a SNAP at
> each site.  The SPRITE instrument at OVRO, which is resurrecting a few
> 10.4m Leighton dishes, is also using CASPER hardware/toolfllow in multiple
> places, including the correlator, lobe rotation, and phase switching.
>
> On Wed, Aug 31, 2022 at 07:21, David Harold Edward MacMahon <
> dav...@berkeley.edu> wrote:
>
>> Also, the “Infrared Spatial Interferometer” (ISI) project started by the
>> late :( Charles Townes uses CASPER hardware.
>>
>>
>> On Aug 31, 2022, at 3:59 PM, David Harold Edward MacMahon <
>> dav...@berkeley.edu> wrote:
>>
>> SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.
>> It may be more correct to call them two backends for the same
>> spectrometer.  These ran at Arecibo.  Greenburst is a version of Alfaburst
>> that is at Green Bank.
>>
>> There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased
>> Array Recording Instrument for Galactic Even horizon Studies”, PhRInGES was
>> a time domain phased array beamformer for CARMA and SMA (two of the first
>> three EHT sites).
>>
>> Cheers,
>> Dave
>>
>> On Aug 31, 2022, at 12:53 PM, Morag Brown  wrote:
>>
>> Ciao dalla Sardegna, collaborati!
>>
>> I'm hoping to put together a more up-to-date list of instruments that
>> have been built using CASPER hardware and tools. The most current list was
>> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
>> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
>> so it could probably use updating.
>>
>> The list is currently as follows:
>>
>> *Spectrometers and packetizers -*
>> Fly’s Eye
>> GUPPY
>> CASPER
>> BPSR
>> GAVRT
>> SERENDIP V.v
>> HiTREKS
>> NUPPI
>> Skynet
>> RATTY
>> cycSpec
>> C-BASS
>> HIPSTER
>> KuPol
>> VEGAS
>> ALMA Phasing Project
>> Leuschner
>> R2DBE
>> DSN Transient Observatory
>> VGOS
>> AVN-Ghana
>> COMAP
>>
>> *MKID readout systems -*
>> Columbia MKID
>> Mustang2
>> DARKNESS
>> MEC
>> BLAST-TNG
>> HOLMES
>>
>> *Correlators and beamformers -*
>> KAT7
>> PAPER
>> ATA
>> LEDA
>> ARI
>> MAD
>> pocketcorr
>> Medicina FFTT
>> GMRT
>> Meteor
>> AMI
>> MeerKAT AR-1
>> FLAG
>> BIRALES
>> Starburst
>> AMiBA
>> EOVSA
>> SWARM
>> MeerKAT
>> HERA
>>
>> If you are not (or know of any instruments that are not) on this list,
>> please reach out to me for it to be added?
>>
>> Grazie!
>> Morag
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>> 
>> .
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/B8B01FDC-DF32-4E4E-AABF-B493FBC63B73%40berkeley.edu
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CA%2B5pq4%2BDd%2BJy_WAZO4a6u%2BXwSZjdwWQeOFsCJdBg0dP26bp2TA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPU71P_VDL-7KxZiV7Q-8Bb0dGRyQ%3DEtoqcqeBgO4BzPQVwsTw%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools

[Morag Brown]

Hey all!

We've decided to extend this to any instruments being planned/currently in
development using CASPER stuff. So if that's you, lemme know!

Ciao ciao!
Morag

On Wed, Aug 31, 2022 at 4:37 PM Vikram Ravi  wrote:

> DSA-110 at the Owens Valley Radio Observatory (OVRO) uses 40 SNAP-1 boards
> for its f-engine, and the STARE-2 all-sky FRB project also uses a SNAP at
> each site.  The SPRITE instrument at OVRO, which is resurrecting a few
> 10.4m Leighton dishes, is also using CASPER hardware/toolfllow in multiple
> places, including the correlator, lobe rotation, and phase switching.
>
> On Wed, Aug 31, 2022 at 07:21, David Harold Edward MacMahon <
> dav...@berkeley.edu> wrote:
>
>> Also, the “Infrared Spatial Interferometer” (ISI) project started by the
>> late :( Charles Townes uses CASPER hardware.
>>
>>
>> On Aug 31, 2022, at 3:59 PM, David Harold Edward MacMahon <
>> dav...@berkeley.edu> wrote:
>>
>> SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.
>> It may be more correct to call them two backends for the same
>> spectrometer.  These ran at Arecibo.  Greenburst is a version of Alfaburst
>> that is at Green Bank.
>>
>> There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased
>> Array Recording Instrument for Galactic Even horizon Studies”, PhRInGES was
>> a time domain phased array beamformer for CARMA and SMA (two of the first
>> three EHT sites).
>>
>> Cheers,
>> Dave
>>
>> On Aug 31, 2022, at 12:53 PM, Morag Brown  wrote:
>>
>> Ciao dalla Sardegna, collaborati!
>>
>> I'm hoping to put together a more up-to-date list of instruments that
>> have been built using CASPER hardware and tools. The most current list was
>> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
>> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
>> so it could probably use updating.
>>
>> The list is currently as follows:
>>
>> *Spectrometers and packetizers -*
>> Fly’s Eye
>> GUPPY
>> CASPER
>> BPSR
>> GAVRT
>> SERENDIP V.v
>> HiTREKS
>> NUPPI
>> Skynet
>> RATTY
>> cycSpec
>> C-BASS
>> HIPSTER
>> KuPol
>> VEGAS
>> ALMA Phasing Project
>> Leuschner
>> R2DBE
>> DSN Transient Observatory
>> VGOS
>> AVN-Ghana
>> COMAP
>>
>> *MKID readout systems -*
>> Columbia MKID
>> Mustang2
>> DARKNESS
>> MEC
>> BLAST-TNG
>> HOLMES
>>
>> *Correlators and beamformers -*
>> KAT7
>> PAPER
>> ATA
>> LEDA
>> ARI
>> MAD
>> pocketcorr
>> Medicina FFTT
>> GMRT
>> Meteor
>> AMI
>> MeerKAT AR-1
>> FLAG
>> BIRALES
>> Starburst
>> AMiBA
>> EOVSA
>> SWARM
>> MeerKAT
>> HERA
>>
>> If you are not (or know of any instruments that are not) on this list,
>> please reach out to me for it to be added?
>>
>> Grazie!
>> Morag
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>> 
>> .
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/B8B01FDC-DF32-4E4E-AABF-B493FBC63B73%40berkeley.edu
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CA%2B5pq4%2BDd%2BJy_WAZO4a6u%2BXwSZjdwWQeOFsCJdBg0dP26bp2TA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TdUWoSMd%2B8Gm71wEGiu43rbRnDvUddUZ7Tvv2%3Dax%2BPMWA%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools

[Vikram Ravi]

DSA-110 at the Owens Valley Radio Observatory (OVRO) uses 40 SNAP-1 boards
for its f-engine, and the STARE-2 all-sky FRB project also uses a SNAP at
each site.  The SPRITE instrument at OVRO, which is resurrecting a few
10.4m Leighton dishes, is also using CASPER hardware/toolfllow in multiple
places, including the correlator, lobe rotation, and phase switching.

On Wed, Aug 31, 2022 at 07:21, David Harold Edward MacMahon <
dav...@berkeley.edu> wrote:

> Also, the “Infrared Spatial Interferometer” (ISI) project started by the
> late :( Charles Townes uses CASPER hardware.
>
>
> On Aug 31, 2022, at 3:59 PM, David Harold Edward MacMahon <
> dav...@berkeley.edu> wrote:
>
> SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.
> It may be more correct to call them two backends for the same
> spectrometer.  These ran at Arecibo.  Greenburst is a version of Alfaburst
> that is at Green Bank.
>
> There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased
> Array Recording Instrument for Galactic Even horizon Studies”, PhRInGES was
> a time domain phased array beamformer for CARMA and SMA (two of the first
> three EHT sites).
>
> Cheers,
> Dave
>
> On Aug 31, 2022, at 12:53 PM, Morag Brown  wrote:
>
> Ciao dalla Sardegna, collaborati!
>
> I'm hoping to put together a more up-to-date list of instruments that have
> been built using CASPER hardware and tools. The most current list was
> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
> so it could probably use updating.
>
> The list is currently as follows:
>
> *Spectrometers and packetizers -*
> Fly’s Eye
> GUPPY
> CASPER
> BPSR
> GAVRT
> SERENDIP V.v
> HiTREKS
> NUPPI
> Skynet
> RATTY
> cycSpec
> C-BASS
> HIPSTER
> KuPol
> VEGAS
> ALMA Phasing Project
> Leuschner
> R2DBE
> DSN Transient Observatory
> VGOS
> AVN-Ghana
> COMAP
>
> *MKID readout systems -*
> Columbia MKID
> Mustang2
> DARKNESS
> MEC
> BLAST-TNG
> HOLMES
>
> *Correlators and beamformers -*
> KAT7
> PAPER
> ATA
> LEDA
> ARI
> MAD
> pocketcorr
> Medicina FFTT
> GMRT
> Meteor
> AMI
> MeerKAT AR-1
> FLAG
> BIRALES
> Starburst
> AMiBA
> EOVSA
> SWARM
> MeerKAT
> HERA
>
> If you are not (or know of any instruments that are not) on this list,
> please reach out to me for it to be added?
>
> Grazie!
> Morag
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
> 
> .
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/B8B01FDC-DF32-4E4E-AABF-B493FBC63B73%40berkeley.edu
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CA%2B5pq4%2BDd%2BJy_WAZO4a6u%2BXwSZjdwWQeOFsCJdBg0dP26bp2TA%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools

[Ramesh Karuppusamy]

Hi Morag,

The MPIfR operates two generations of pulsar instruments powered by CASPER: 
PSRIX based on iADC+ROACH1 and PSRIX2 with four ROACH2s each with two ADC5Gs.

Cheers,
Ramesh




> On 31. Aug 2022, at 12:53, Morag Brown  wrote:
> 
> Ciao dalla Sardegna, collaborati!
> 
> I'm hoping to put together a more up-to-date list of instruments that have 
> been built using CASPER hardware and tools. The most current list was 
> compiled in 2016 for the "A Decade of Developing Radio-Astronomy 
> Instrumentation using CASPER Open-Source Technology" paper by Jack et al, so 
> it could probably use updating.
> 
> The list is currently as follows: 
> 
> Spectrometers and packetizers -
> Fly’s Eye
> GUPPY
> CASPER
> BPSR
> GAVRT
> SERENDIP V.v
> HiTREKS
> NUPPI
> Skynet
> RATTY
> cycSpec
> C-BASS
> HIPSTER
> KuPol
> VEGAS
> ALMA Phasing Project
> Leuschner
> R2DBE
> DSN Transient Observatory
> VGOS
> AVN-Ghana
> COMAP
> 
> MKID readout systems -
> Columbia MKID
> Mustang2
> DARKNESS
> MEC
> BLAST-TNG
> HOLMES
> 
> Correlators and beamformers -
> KAT7
> PAPER
> ATA
> LEDA
> ARI
> MAD
> pocketcorr
> Medicina FFTT
> GMRT
> Meteor
> AMI
> MeerKAT AR-1
> FLAG
> BIRALES
> Starburst
> AMiBA
> EOVSA
> SWARM
> MeerKAT
> HERA
> 
> If you are not (or know of any instruments that are not) on this list, please 
> reach out to me for it to be added?
> 
> Grazie!
> Morag
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to casper+unsubscr...@lists.berkeley.edu 
> .
> To view this discussion on the web visit 
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/714E91C0-E322-4FCC-AE42-EB1A299C8FE0%40mpifr-bonn.mpg.de.

Re: [casper] Question of 'PCORE'、'Share_BRAM' and 'Subsystem' block

[王钊]

Hi  Morag and Dave，

Morag, I would like to thank you for your detailed explanation of my
questions. I have gained a lot!

Thank you Dave. I didn't understand EQ at first, but your explanation
helped me. Also thank you for your PAPER correlator file, which is very
helpful to me.

Cheers，
Wang

David Harold Edward MacMahon  于2022年8月31日周三 21:40写道：

> Hi, Wang,
>
> Morag is right about the mask parameter and BRAM sizing relationship.  The
> subsystem you showed is used to provide each frequency channel with its own
> “equalization” coefficient.  In the “round” block, I think “din” and the
> output of “coeffs” get multiplied together and then the 4 most significant
> bits are kept.  The idea was that the coefficients could be set to
> flatten out any variation in amplitude across the passband.  In practice
> we ended up setting all the coefficients to the same value (rather than
> individually tailoring them) because that was easier to keep track of.
>
> One other detail that the lower comment block is trying to make (I think)
> is that the data presented at “din” is all the frequency channels for one
> input followed by all the frequency channels of another input.  I think
> this was/is the normal output of the real-to-complex biplex FFT block being
> used.
>
> HTH,
> Dave
>
> On Aug 31, 2022, at 1:07 PM, Morag Brown  wrote:
>
> Hi Wang,
>
> It looks like that block is just a bram and it's surrounding logic that's
> been wrapped up as a subsystem to make things a bit easier/neater? See
> here  for
> details on subsystems in simulink. I guess that the "number of fft
> channels" parameter is linked to the bram *address width* parameter that
> specifies the size of the memory. And then I would guess that the
> coefficients for the fft itself are then written to this bram at run time.
> If you want to change any parameters of the blocks within this subsystem,
> you should just be able to double click on any block (eg. the counter,
> delays, bram etc) and change them there, but the subsystem itself was only
> set up to have that one parameter, so that is the only one you'd be able to
> change in that window.
>
> Hope that clears things up,
> Morag
>
>
>
> On Wed, Aug 31, 2022 at 12:47 PM 王钊  wrote:
>
>> Hi Jack，
>>
>> Thanks for your reply. I will read this document carefully.
>>
>> Cheers
>> Wang
>>
>> Jack Hickish  于2022年8月31日周三 16:35写道：
>>
>>> Hi Wang,
>>>
>>> If you haven't seen it already, this memo is probably useful --
>>> https://github.com/casper-astro/publications/blob/master/Memos/files/Black_box_memo.pdf
>>>
>>> The PCORE yellow block doesn't contain anything because it doesn't
>>> actually do anything in FPGA logic. All it does is tells the toolflow to
>>> include extra source files in your build, which should have been
>>> pre-generated. The memo above explains how to do this.
>>>
>>> Cheers
>>> Jack
>>>
>>> On Wed, 31 Aug 2022 at 09:00, Morag Brown  wrote:
>>>
 Hi Wang,

 I can't answer the first question, and your third is a bit confusing.
 Can you send a screenshot of the block you mean?

 As for the shared_bram - this instantiates bram on hardware that is
 exposed to the axi/wishbone (depending on the hardware) bus. You can write
 values (*vals*) to this block via casperfpga by packing your data
 using "*buf = struct.pack('>1024i', *vals)"*, and then write to the
 bram using* "fpga.write('memory device name', buf, offset)"*. To read
 from the bram you would do a "*struct.unpack('>1024i',
 fpga.read('memory device name',1024*4,0))"* call - the values 1024, 4
 and *i* will change depending on the depth of you bram and your data
 width. Within the design, you need to have a counter on the address line to
 iterate through the addresses that you are writing to, and if you are
 planning on writing to the block via casperfpga then you should set *write
 enable *and *data input* to 0; and if you are planning to write in
 over the data line, then *write enable* should be set high with the
 data line tied to wherever your values are coming from. In simulation, you
 can write an array of values (for simulation only) to the "initial values"
 text box within the block that opens when you double click. Then to see
 what the output is doing, you can add a simulink scope block to the bram
 output.

 Hope this helps a bit!

 Morag

 On Wed, Aug 31, 2022 at 7:48 AM Wang  wrote:

> Hello CASPER，
>
> I am currently looking at David's simulink model of PAPER correlator
> and some other people built simulink models.
>
> I met some questions in the process of looking at it.
> I have been exposed to simulink for a short time and it is not clear
> how some modules work.
>
> The first question.Double-click on the PCORE block and prompt me for a
> path. I imitate David's input, but no 

Re: [casper] RA Instruments using CASPER hardware and tools {External}

[Morag Brown]

Thanks Jason and Scott. And yes, Scott, you are correct about how CASPER
should be CASPSR - I was hit by autocorrect and was hoping no one would
notice ;)

On Wed, Aug 31, 2022 at 4:22 PM Scott Ransom  wrote:

> A couple other minor corrections:
>
> It is GUPPI not "GUPPY".  And there was also PUPPI at Arecibo.  And Maybe
> CASPER was supposed to be
> CASPSR?
>
> Scott
>
> On 8/31/22 9:59 AM, David Harold Edward MacMahon wrote:
> > SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.
> It may be more correct to
> > call them two backends for the same spectrometer.  These ran at
> Arecibo.  Greenburst is a version of
> > Alfaburst that is at Green Bank.
> >
> > There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased
> Array Recording Instrument
> > for Galactic Even horizon Studies”, PhRInGES was a time domain phased
> array beamformer for CARMA and
> > SMA (two of the first three EHT sites).
> >
> > Cheers,
> > Dave
> >
> >> On Aug 31, 2022, at 12:53 PM, Morag Brown  mbr...@sarao.ac.za>> wrote:
> >>
> >> Ciao dalla Sardegna, collaborati!
> >>
> >> I'm hoping to put together a more up-to-date list of instruments that
> have been built using CASPER
> >> hardware and tools. The most current list was compiled in 2016 for the
> "A Decade of Developing
> >> Radio-Astronomy Instrumentation using CASPER Open-Source Technology"
> paper by Jack et al, so it
> >> could probably use updating.
> >>
> >> The list is currently as follows:
> >>
> >> *Spectrometers and packetizers -*
> >> Fly’s Eye
> >> GUPPY
> >> CASPER
> >> BPSR
> >> GAVRT
> >> SERENDIP V.v
> >> HiTREKS
> >> NUPPI
> >> Skynet
> >> RATTY
> >> cycSpec
> >> C-BASS
> >> HIPSTER
> >> KuPol
> >> VEGAS
> >> ALMA Phasing Project
> >> Leuschner
> >> R2DBE
> >> DSN Transient Observatory
> >> VGOS
> >> AVN-Ghana
> >> COMAP
> >>
> >> *MKID readout systems -*
> >> Columbia MKID
> >> Mustang2
> >> DARKNESS
> >> MEC
> >> BLAST-TNG
> >> HOLMES
> >> *
> >> *
> >> *Correlators and beamformers -*
> >> KAT7
> >> PAPER
> >> ATA
> >> LEDA
> >> ARI
> >> MAD
> >> pocketcorr
> >> Medicina FFTT
> >> GMRT
> >> Meteor
> >> AMI
> >> MeerKAT AR-1
> >> FLAG
> >> BIRALES
> >> Starburst
> >> AMiBA
> >> EOVSA
> >> SWARM
> >> MeerKAT
> >> HERA
> >>
> >> If you are not (or know of any instruments that are not) on this list,
> please reach out to me for
> >> it to be added?
> >>
> >> Grazie!
> >> Morag
> >>
> >>
> >>
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "casper@lists.berkeley.edu " group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to
> >> casper+unsubscr...@lists.berkeley.edu  casper+unsubscr...@lists.berkeley.edu>.
> >> To view this discussion on the web visit
> >>
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
> >> <
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com?utm_medium=email_source=footer
> >.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "casper@lists.berkeley.edu" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to
> > casper+unsubscr...@lists.berkeley.edu  casper+unsubscr...@lists.berkeley.edu>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6269C4BB-1F4D-48C3-87EE-62727D9E3175%40berkeley.edu
> > <
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6269C4BB-1F4D-48C3-87EE-62727D9E3175%40berkeley.edu?utm_medium=email_source=footer
> >.
>
> --
> Scott M. RansomAddress:  NRAO
> Phone:  (434) 296-0320   520 Edgemont Rd.
> email:  sran...@nrao.edu Charlottesville, VA 22903 USA
> GPG Fingerprint: A40A 94F2 3F48 4136 3AC4  9598 92D5 25CB 22A6 7B65
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/e47b3e98-3e5b-94f7-d86f-8532c8aff0c7%40nrao.edu
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TczipCwemOPVxE_zXAVNJWuCO-R3QM4YYc-D3PP56i75g%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools {External}

[Scott Ransom]

A couple other minor corrections:

It is GUPPI not "GUPPY".  And there was also PUPPI at Arecibo.  And Maybe CASPER was supposed to be 
CASPSR?


Scott

On 8/31/22 9:59 AM, David Harold Edward MacMahon wrote:
SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.  It may be more correct to 
call them two backends for the same spectrometer.  These ran at Arecibo.  Greenburst is a version of 
Alfaburst that is at Green Bank.


There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased Array Recording Instrument 
for Galactic Even horizon Studies”, PhRInGES was a time domain phased array beamformer for CARMA and 
SMA (two of the first three EHT sites).


Cheers,
Dave


On Aug 31, 2022, at 12:53 PM, Morag Brown mailto:mbr...@sarao.ac.za>> wrote:

Ciao dalla Sardegna, collaborati!

I'm hoping to put together a more up-to-date list of instruments that have been built using CASPER 
hardware and tools. The most current list was compiled in 2016 for the "A Decade of Developing 
Radio-Astronomy Instrumentation using CASPER Open-Source Technology" paper by Jack et al, so it 
could probably use updating.


The list is currently as follows:

*Spectrometers and packetizers -*
Fly’s Eye
GUPPY
CASPER
BPSR
GAVRT
SERENDIP V.v
HiTREKS
NUPPI
Skynet
RATTY
cycSpec
C-BASS
HIPSTER
KuPol
VEGAS
ALMA Phasing Project
Leuschner
R2DBE
DSN Transient Observatory
VGOS
AVN-Ghana
COMAP

*MKID readout systems -*
Columbia MKID
Mustang2
DARKNESS
MEC
BLAST-TNG
HOLMES
*
*
*Correlators and beamformers -*
KAT7
PAPER
ATA
LEDA
ARI
MAD
pocketcorr
Medicina FFTT
GMRT
Meteor
AMI
MeerKAT AR-1
FLAG
BIRALES
Starburst
AMiBA
EOVSA
SWARM
MeerKAT
HERA

If you are not (or know of any instruments that are not) on this list, please reach out to me for 
it to be added?


Grazie!
Morag




--
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu " group.
To unsubscribe from this group and stop receiving emails from it, send an email to 
casper+unsubscr...@lists.berkeley.edu .
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com 
.


--
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 
casper+unsubscr...@lists.berkeley.edu .
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6269C4BB-1F4D-48C3-87EE-62727D9E3175%40berkeley.edu 
.


--
Scott M. RansomAddress:  NRAO
Phone:  (434) 296-0320   520 Edgemont Rd.
email:  sran...@nrao.edu Charlottesville, VA 22903 USA
GPG Fingerprint: A40A 94F2 3F48 4136 3AC4  9598 92D5 25CB 22A6 7B65

--
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/e47b3e98-3e5b-94f7-d86f-8532c8aff0c7%40nrao.edu.

Re: [casper] RA Instruments using CASPER hardware and tools

[David Harold Edward MacMahon]

Also, the “Infrared Spatial Interferometer” (ISI) project started by the late 
:( Charles Townes uses CASPER hardware.

> On Aug 31, 2022, at 3:59 PM, David Harold Edward MacMahon 
>  wrote:
> 
> SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.  It 
> may be more correct to call them two backends for the same spectrometer.  
> These ran at Arecibo.  Greenburst is a version of Alfaburst that is at Green 
> Bank.
> 
> There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased Array 
> Recording Instrument for Galactic Even horizon Studies”, PhRInGES was a time 
> domain phased array beamformer for CARMA and SMA (two of the first three EHT 
> sites).
> 
> Cheers,
> Dave
> 
>> On Aug 31, 2022, at 12:53 PM, Morag Brown > > wrote:
>> 
>> Ciao dalla Sardegna, collaborati!
>> 
>> I'm hoping to put together a more up-to-date list of instruments that have 
>> been built using CASPER hardware and tools. The most current list was 
>> compiled in 2016 for the "A Decade of Developing Radio-Astronomy 
>> Instrumentation using CASPER Open-Source Technology" paper by Jack et al, so 
>> it could probably use updating.
>> 
>> The list is currently as follows: 
>> 
>> Spectrometers and packetizers -
>> Fly’s Eye
>> GUPPY
>> CASPER
>> BPSR
>> GAVRT
>> SERENDIP V.v
>> HiTREKS
>> NUPPI
>> Skynet
>> RATTY
>> cycSpec
>> C-BASS
>> HIPSTER
>> KuPol
>> VEGAS
>> ALMA Phasing Project
>> Leuschner
>> R2DBE
>> DSN Transient Observatory
>> VGOS
>> AVN-Ghana
>> COMAP
>> 
>> MKID readout systems -
>> Columbia MKID
>> Mustang2
>> DARKNESS
>> MEC
>> BLAST-TNG
>> HOLMES
>> 
>> Correlators and beamformers -
>> KAT7
>> PAPER
>> ATA
>> LEDA
>> ARI
>> MAD
>> pocketcorr
>> Medicina FFTT
>> GMRT
>> Meteor
>> AMI
>> MeerKAT AR-1
>> FLAG
>> BIRALES
>> Starburst
>> AMiBA
>> EOVSA
>> SWARM
>> MeerKAT
>> HERA
>> 
>> If you are not (or know of any instruments that are not) on this list, 
>> please reach out to me for it to be added?
>> 
>> Grazie!
>> Morag
>> 
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "casper@lists.berkeley.edu " group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to casper+unsubscr...@lists.berkeley.edu 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>>  
>> .
> 

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/B8B01FDC-DF32-4E4E-AABF-B493FBC63B73%40berkeley.edu.

Re: [casper] RA Instruments using CASPER hardware and tools

[Gopal Narayanan]

Another LMT Instrument using CASPER hardware is WARES - Wideband Array
ROACH enabled Spectrometer - a 32-pixel spectrometer system based on
ROACH2s and ADC5Gs.

Gopal


On Wed, Aug 31, 2022 at 9:40 AM Sam Rowe  wrote:

> Ciao Morag,
>
> You can add MUSCAT and TolTEC (both at the LMT-50m) to the list of MKID
> instruments that have been built using CASPER hardware and tools.
>
> Cheers,
>
> Sam
>
>
> On Wed, 31 Aug 2022, 11:53 Morag Brown,  wrote:
>
>> *External email to Cardiff University - *Take care when replying/opening
>> attachments or links.
>> *Nid ebost mewnol o Brifysgol Caerdydd yw hwn - *Cymerwch ofal wrth
>> ateb/agor atodiadau neu ddolenni.
>>
>> Ciao dalla Sardegna, collaborati!
>>
>> I'm hoping to put together a more up-to-date list of instruments that
>> have been built using CASPER hardware and tools. The most current list was
>> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
>> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
>> so it could probably use updating.
>>
>> The list is currently as follows:
>>
>> *Spectrometers and packetizers -*
>> Fly’s Eye
>> GUPPY
>> CASPER
>> BPSR
>> GAVRT
>> SERENDIP V.v
>> HiTREKS
>> NUPPI
>> Skynet
>> RATTY
>> cycSpec
>> C-BASS
>> HIPSTER
>> KuPol
>> VEGAS
>> ALMA Phasing Project
>> Leuschner
>> R2DBE
>> DSN Transient Observatory
>> VGOS
>> AVN-Ghana
>> COMAP
>>
>> *MKID readout systems -*
>> Columbia MKID
>> Mustang2
>> DARKNESS
>> MEC
>> BLAST-TNG
>> HOLMES
>>
>> *Correlators and beamformers -*
>> KAT7
>> PAPER
>> ATA
>> LEDA
>> ARI
>> MAD
>> pocketcorr
>> Medicina FFTT
>> GMRT
>> Meteor
>> AMI
>> MeerKAT AR-1
>> FLAG
>> BIRALES
>> Starburst
>> AMiBA
>> EOVSA
>> SWARM
>> MeerKAT
>> HERA
>>
>> If you are not (or know of any instruments that are not) on this list,
>> please reach out to me for it to be added?
>>
>> Grazie!
>> Morag
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAHsow4zE4DFvXNy1hE8hhf%3DpnBK7Cz16QV-%3DLdzx4t%3D%3D7tw4RQ%40mail.gmail.com
> 
> .
>


-- 
Gopal Narayanan  Ph #: (413) 545 0925
Department of Astronomy  e-mail: go...@astro.umass.edu
University of Massachusetts  Amherst MA 01003
Pronouns: he/him/his

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CACboPVErFJ96iVP-ViGwoVZDOOxNUK7MYyBgE-Mku4%3D-kzWYaw%40mail.gmail.com.

Re: [casper] RA Instruments using CASPER hardware and tools

[David Harold Edward MacMahon]

SERENDIP VI and Alfaburst were spectrometers that used CASPER hardware.  It may 
be more correct to call them two backends for the same spectrometer.  These ran 
at Arecibo.  Greenburst is a version of Alfaburst that is at Green Bank.

There’s also PhRInGES.  Besides being a tortured (b)acronym for “Phased Array 
Recording Instrument for Galactic Even horizon Studies”, PhRInGES was a time 
domain phased array beamformer for CARMA and SMA (two of the first three EHT 
sites).

Cheers,
Dave

> On Aug 31, 2022, at 12:53 PM, Morag Brown  wrote:
> 
> Ciao dalla Sardegna, collaborati!
> 
> I'm hoping to put together a more up-to-date list of instruments that have 
> been built using CASPER hardware and tools. The most current list was 
> compiled in 2016 for the "A Decade of Developing Radio-Astronomy 
> Instrumentation using CASPER Open-Source Technology" paper by Jack et al, so 
> it could probably use updating.
> 
> The list is currently as follows: 
> 
> Spectrometers and packetizers -
> Fly’s Eye
> GUPPY
> CASPER
> BPSR
> GAVRT
> SERENDIP V.v
> HiTREKS
> NUPPI
> Skynet
> RATTY
> cycSpec
> C-BASS
> HIPSTER
> KuPol
> VEGAS
> ALMA Phasing Project
> Leuschner
> R2DBE
> DSN Transient Observatory
> VGOS
> AVN-Ghana
> COMAP
> 
> MKID readout systems -
> Columbia MKID
> Mustang2
> DARKNESS
> MEC
> BLAST-TNG
> HOLMES
> 
> Correlators and beamformers -
> KAT7
> PAPER
> ATA
> LEDA
> ARI
> MAD
> pocketcorr
> Medicina FFTT
> GMRT
> Meteor
> AMI
> MeerKAT AR-1
> FLAG
> BIRALES
> Starburst
> AMiBA
> EOVSA
> SWARM
> MeerKAT
> HERA
> 
> If you are not (or know of any instruments that are not) on this list, please 
> reach out to me for it to be added?
> 
> Grazie!
> Morag
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to casper+unsubscr...@lists.berkeley.edu 
> .
> To view this discussion on the web visit 
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/6269C4BB-1F4D-48C3-87EE-62727D9E3175%40berkeley.edu.

Re: [casper] Question of 'PCORE'、'Share_BRAM' and 'Subsystem' block

[David Harold Edward MacMahon]

Hi, Wang,

Morag is right about the mask parameter and BRAM sizing relationship.  The 
subsystem you showed is used to provide each frequency channel with its own 
“equalization” coefficient.  In the “round” block, I think “din” and the output 
of “coeffs” get multiplied together and then the 4 most significant bits are 
kept.  The idea was that the coefficients could be set to flatten out any 
variation in amplitude across the passband.  In practice we ended up setting 
all the coefficients to the same value (rather than individually tailoring 
them) because that was easier to keep track of.

One other detail that the lower comment block is trying to make (I think) is 
that the data presented at “din” is all the frequency channels for one input 
followed by all the frequency channels of another input.  I think this was/is 
the normal output of the real-to-complex biplex FFT block being used.

HTH,
Dave

> On Aug 31, 2022, at 1:07 PM, Morag Brown  wrote:
> 
> Hi Wang,
> 
> It looks like that block is just a bram and it's surrounding logic that's 
> been wrapped up as a subsystem to make things a bit easier/neater? See here 
>  for 
> details on subsystems in simulink. I guess that the "number of fft channels" 
> parameter is linked to the bram address width parameter that specifies the 
> size of the memory. And then I would guess that the coefficients for the fft 
> itself are then written to this bram at run time. If you want to change any 
> parameters of the blocks within this subsystem, you should just be able to 
> double click on any block (eg. the counter, delays, bram etc) and change them 
> there, but the subsystem itself was only set up to have that one parameter, 
> so that is the only one you'd be able to change in that window. 
> 
> Hope that clears things up,
> Morag
> 
> 
> 
> On Wed, Aug 31, 2022 at 12:47 PM 王钊  > wrote:
> Hi Jack，
> 
> Thanks for your reply. I will read this document carefully.
> 
> Cheers
> Wang
> 
> Jack Hickish mailto:jackhick...@gmail.com>> 
> 于2022年8月31日周三 16:35写道：
> Hi Wang,
> 
> If you haven't seen it already, this memo is probably useful -- 
> https://github.com/casper-astro/publications/blob/master/Memos/files/Black_box_memo.pdf
>  
> 
> 
> The PCORE yellow block doesn't contain anything because it doesn't actually 
> do anything in FPGA logic. All it does is tells the toolflow to include extra 
> source files in your build, which should have been pre-generated. The memo 
> above explains how to do this.
> 
> Cheers
> Jack
> 
> On Wed, 31 Aug 2022 at 09:00, Morag Brown  > wrote:
> Hi Wang,
> 
> I can't answer the first question, and your third is a bit confusing. Can you 
> send a screenshot of the block you mean? 
> 
> As for the shared_bram - this instantiates bram on hardware that is exposed 
> to the axi/wishbone (depending on the hardware) bus. You can write values 
> (vals) to this block via casperfpga by packing your data using "buf = 
> struct.pack('>1024i', *vals)", and then write to the bram using 
> "fpga.write('memory device name', buf, offset)". To read from the bram you 
> would do a "struct.unpack('>1024i', fpga.read('memory device 
> name',1024*4,0))" call - the values 1024, 4 and i will change depending on 
> the depth of you bram and your data width. Within the design, you need to 
> have a counter on the address line to iterate through the addresses that you 
> are writing to, and if you are planning on writing to the block via 
> casperfpga then you should set write enable and data input to 0; and if you 
> are planning to write in over the data line, then write enable should be set 
> high with the data line tied to wherever your values are coming from. In 
> simulation, you can write an array of values (for simulation only) to the 
> "initial values" text box within the block that opens when you double click. 
> Then to see what the output is doing, you can add a simulink scope block to 
> the bram output. 
> 
> Hope this helps a bit!
> 
> Morag
> 
> On Wed, Aug 31, 2022 at 7:48 AM Wang  > wrote:
> Hello CASPER，
> 
> I am currently looking at David's simulink model of PAPER correlator and some 
> other people built simulink models.
> 
> I met some questions in the process of looking at it. 
> I have been exposed to simulink for a short time and it is not clear how some 
> modules work.
> 
> The first question.Double-click on the PCORE block and prompt me for a path. 
> I imitate David's input, but no response. Then I check David's PCORE block 
> inside also nothing, may I ask what is wrong with my operation?
> 
> The second question.I see Share_BRAM blocks used a lot. I want to understand 
> the details of this block, the official website does not seem to have 
> Share_BRAM description. Also, 

Re: [casper] RA Instruments using CASPER hardware and tools

[Sam Rowe]

Ciao Morag,

You can add MUSCAT and TolTEC (both at the LMT-50m) to the list of MKID
instruments that have been built using CASPER hardware and tools.

Cheers,

Sam


On Wed, 31 Aug 2022, 11:53 Morag Brown,  wrote:

> *External email to Cardiff University - *Take care when replying/opening
> attachments or links.
> *Nid ebost mewnol o Brifysgol Caerdydd yw hwn - *Cymerwch ofal wrth
> ateb/agor atodiadau neu ddolenni.
>
> Ciao dalla Sardegna, collaborati!
>
> I'm hoping to put together a more up-to-date list of instruments that have
> been built using CASPER hardware and tools. The most current list was
> compiled in 2016 for the "A Decade of Developing Radio-Astronomy
> Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
> so it could probably use updating.
>
> The list is currently as follows:
>
> *Spectrometers and packetizers -*
> Fly’s Eye
> GUPPY
> CASPER
> BPSR
> GAVRT
> SERENDIP V.v
> HiTREKS
> NUPPI
> Skynet
> RATTY
> cycSpec
> C-BASS
> HIPSTER
> KuPol
> VEGAS
> ALMA Phasing Project
> Leuschner
> R2DBE
> DSN Transient Observatory
> VGOS
> AVN-Ghana
> COMAP
>
> *MKID readout systems -*
> Columbia MKID
> Mustang2
> DARKNESS
> MEC
> BLAST-TNG
> HOLMES
>
> *Correlators and beamformers -*
> KAT7
> PAPER
> ATA
> LEDA
> ARI
> MAD
> pocketcorr
> Medicina FFTT
> GMRT
> Meteor
> AMI
> MeerKAT AR-1
> FLAG
> BIRALES
> Starburst
> AMiBA
> EOVSA
> SWARM
> MeerKAT
> HERA
>
> If you are not (or know of any instruments that are not) on this list,
> please reach out to me for it to be added?
>
> Grazie!
> Morag
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAHsow4zE4DFvXNy1hE8hhf%3DpnBK7Cz16QV-%3DLdzx4t%3D%3D7tw4RQ%40mail.gmail.com.

Re: [casper] Question of 'PCORE'、'Share_BRAM' and 'Subsystem' block

[Morag Brown]

Hi Wang,

It looks like that block is just a bram and it's surrounding logic that's
been wrapped up as a subsystem to make things a bit easier/neater? See here
 for
details on subsystems in simulink. I guess that the "number of fft
channels" parameter is linked to the bram *address width* parameter that
specifies the size of the memory. And then I would guess that the
coefficients for the fft itself are then written to this bram at run time.
If you want to change any parameters of the blocks within this subsystem,
you should just be able to double click on any block (eg. the counter,
delays, bram etc) and change them there, but the subsystem itself was only
set up to have that one parameter, so that is the only one you'd be able to
change in that window.

Hope that clears things up,
Morag



On Wed, Aug 31, 2022 at 12:47 PM 王钊  wrote:

> Hi Jack，
>
> Thanks for your reply. I will read this document carefully.
>
> Cheers
> Wang
>
> Jack Hickish  于2022年8月31日周三 16:35写道：
>
>> Hi Wang,
>>
>> If you haven't seen it already, this memo is probably useful --
>> https://github.com/casper-astro/publications/blob/master/Memos/files/Black_box_memo.pdf
>>
>> The PCORE yellow block doesn't contain anything because it doesn't
>> actually do anything in FPGA logic. All it does is tells the toolflow to
>> include extra source files in your build, which should have been
>> pre-generated. The memo above explains how to do this.
>>
>> Cheers
>> Jack
>>
>> On Wed, 31 Aug 2022 at 09:00, Morag Brown  wrote:
>>
>>> Hi Wang,
>>>
>>> I can't answer the first question, and your third is a bit confusing.
>>> Can you send a screenshot of the block you mean?
>>>
>>> As for the shared_bram - this instantiates bram on hardware that is
>>> exposed to the axi/wishbone (depending on the hardware) bus. You can write
>>> values (*vals*) to this block via casperfpga by packing your data using
>>> "*buf = struct.pack('>1024i', *vals)"*, and then write to the bram using* 
>>> "fpga.write('memory
>>> device name', buf, offset)"*. To read from the bram you would do a 
>>> "*struct.unpack('>1024i',
>>> fpga.read('memory device name',1024*4,0))"* call - the values 1024, 4
>>> and *i* will change depending on the depth of you bram and your data
>>> width. Within the design, you need to have a counter on the address line to
>>> iterate through the addresses that you are writing to, and if you are
>>> planning on writing to the block via casperfpga then you should set *write
>>> enable *and *data input* to 0; and if you are planning to write in over
>>> the data line, then *write enable* should be set high with the data
>>> line tied to wherever your values are coming from. In simulation, you can
>>> write an array of values (for simulation only) to the "initial values" text
>>> box within the block that opens when you double click. Then to see what the
>>> output is doing, you can add a simulink scope block to the bram output.
>>>
>>> Hope this helps a bit!
>>>
>>> Morag
>>>
>>> On Wed, Aug 31, 2022 at 7:48 AM Wang  wrote:
>>>
 Hello CASPER，

 I am currently looking at David's simulink model of PAPER correlator
 and some other people built simulink models.

 I met some questions in the process of looking at it.
 I have been exposed to simulink for a short time and it is not clear
 how some modules work.

 The first question.Double-click on the PCORE block and prompt me for a
 path. I imitate David's input, but no response. Then I check David's PCORE
 block inside also nothing, may I ask what is wrong with my operation?

 The second question.I see Share_BRAM blocks used a lot. I want to
 understand the details of this block, the official website does not seem to
 have Share_BRAM description. Also, I want to see what is happening to
 Share_BRAM during simulation. What blocks can I do this with?

 The third question.I see that a yellow block (not the same color as
 Casper-libary's block)  does not have a library link. A window appears
 after double-click :
 Function Block Parameters: block's name
 Subsystem (mask)
 Parameters
 Number of fft channels (same ad fft prompt)(2^?)
 Is it a Subsystem block? If yes, how to add the function of double
 click setting parameter?

 I really hope you can reply to me, I will be very grateful!

 BW
 Wang

 --
 You received this message because you are subscribed to the Google
 Groups "casper@lists.berkeley.edu" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to casper+unsubscr...@lists.berkeley.edu.
 To view this discussion on the web visit
 https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ebeaaba6-c293-4e8b-b874-6ee82b6e387an%40lists.berkeley.edu
 

[casper] RA Instruments using CASPER hardware and tools

[Morag Brown]

Ciao dalla Sardegna, collaborati!

I'm hoping to put together a more up-to-date list of instruments that have
been built using CASPER hardware and tools. The most current list was
compiled in 2016 for the "A Decade of Developing Radio-Astronomy
Instrumentation using CASPER Open-Source Technology" paper by Jack et al,
so it could probably use updating.

The list is currently as follows:

*Spectrometers and packetizers -*
Fly’s Eye
GUPPY
CASPER
BPSR
GAVRT
SERENDIP V.v
HiTREKS
NUPPI
Skynet
RATTY
cycSpec
C-BASS
HIPSTER
KuPol
VEGAS
ALMA Phasing Project
Leuschner
R2DBE
DSN Transient Observatory
VGOS
AVN-Ghana
COMAP

*MKID readout systems -*
Columbia MKID
Mustang2
DARKNESS
MEC
BLAST-TNG
HOLMES

*Correlators and beamformers -*
KAT7
PAPER
ATA
LEDA
ARI
MAD
pocketcorr
Medicina FFTT
GMRT
Meteor
AMI
MeerKAT AR-1
FLAG
BIRALES
Starburst
AMiBA
EOVSA
SWARM
MeerKAT
HERA

If you are not (or know of any instruments that are not) on this list,
please reach out to me for it to be added?

Grazie!
Morag

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com.

Re: [casper] Question of 'PCORE'、'Share_BRAM' and 'Subsystem' block

[王钊]

Hi Jack，

Thanks for your reply. I will read this document carefully.

Cheers
Wang

Jack Hickish  于2022年8月31日周三 16:35写道：

> Hi Wang,
>
> If you haven't seen it already, this memo is probably useful --
> https://github.com/casper-astro/publications/blob/master/Memos/files/Black_box_memo.pdf
>
> The PCORE yellow block doesn't contain anything because it doesn't
> actually do anything in FPGA logic. All it does is tells the toolflow to
> include extra source files in your build, which should have been
> pre-generated. The memo above explains how to do this.
>
> Cheers
> Jack
>
> On Wed, 31 Aug 2022 at 09:00, Morag Brown  wrote:
>
>> Hi Wang,
>>
>> I can't answer the first question, and your third is a bit confusing. Can
>> you send a screenshot of the block you mean?
>>
>> As for the shared_bram - this instantiates bram on hardware that is
>> exposed to the axi/wishbone (depending on the hardware) bus. You can write
>> values (*vals*) to this block via casperfpga by packing your data using "*buf
>> = struct.pack('>1024i', *vals)"*, and then write to the bram using* 
>> "fpga.write('memory
>> device name', buf, offset)"*. To read from the bram you would do a 
>> "*struct.unpack('>1024i',
>> fpga.read('memory device name',1024*4,0))"* call - the values 1024, 4
>> and *i* will change depending on the depth of you bram and your data
>> width. Within the design, you need to have a counter on the address line to
>> iterate through the addresses that you are writing to, and if you are
>> planning on writing to the block via casperfpga then you should set *write
>> enable *and *data input* to 0; and if you are planning to write in over
>> the data line, then *write enable* should be set high with the data line
>> tied to wherever your values are coming from. In simulation, you can write
>> an array of values (for simulation only) to the "initial values" text box
>> within the block that opens when you double click. Then to see what the
>> output is doing, you can add a simulink scope block to the bram output.
>>
>> Hope this helps a bit!
>>
>> Morag
>>
>> On Wed, Aug 31, 2022 at 7:48 AM Wang  wrote:
>>
>>> Hello CASPER，
>>>
>>> I am currently looking at David's simulink model of PAPER correlator and
>>> some other people built simulink models.
>>>
>>> I met some questions in the process of looking at it.
>>> I have been exposed to simulink for a short time and it is not clear how
>>> some modules work.
>>>
>>> The first question.Double-click on the PCORE block and prompt me for a
>>> path. I imitate David's input, but no response. Then I check David's PCORE
>>> block inside also nothing, may I ask what is wrong with my operation?
>>>
>>> The second question.I see Share_BRAM blocks used a lot. I want to
>>> understand the details of this block, the official website does not seem to
>>> have Share_BRAM description. Also, I want to see what is happening to
>>> Share_BRAM during simulation. What blocks can I do this with?
>>>
>>> The third question.I see that a yellow block (not the same color as
>>> Casper-libary's block)  does not have a library link. A window appears
>>> after double-click :
>>> Function Block Parameters: block's name
>>> Subsystem (mask)
>>> Parameters
>>> Number of fft channels (same ad fft prompt)(2^?)
>>> Is it a Subsystem block? If yes, how to add the function of double click
>>> setting parameter?
>>>
>>> I really hope you can reply to me, I will be very grateful!
>>>
>>> BW
>>> Wang
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "casper@lists.berkeley.edu" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to casper+unsubscr...@lists.berkeley.edu.
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ebeaaba6-c293-4e8b-b874-6ee82b6e387an%40lists.berkeley.edu
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0Te8H4j7OH87VyJB%2BmEC%3DhO4aAmX_DnGG6RQKYMEUhxJAA%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> 

Re: [casper] Question of 'PCORE'、'Share_BRAM' and 'Subsystem' block

[Jack Hickish]

Hi Wang,

If you haven't seen it already, this memo is probably useful --
https://github.com/casper-astro/publications/blob/master/Memos/files/Black_box_memo.pdf

The PCORE yellow block doesn't contain anything because it doesn't actually
do anything in FPGA logic. All it does is tells the toolflow to include
extra source files in your build, which should have been pre-generated. The
memo above explains how to do this.

Cheers
Jack

On Wed, 31 Aug 2022 at 09:00, Morag Brown  wrote:

> Hi Wang,
>
> I can't answer the first question, and your third is a bit confusing. Can
> you send a screenshot of the block you mean?
>
> As for the shared_bram - this instantiates bram on hardware that is
> exposed to the axi/wishbone (depending on the hardware) bus. You can write
> values (*vals*) to this block via casperfpga by packing your data using "*buf
> = struct.pack('>1024i', *vals)"*, and then write to the bram using* 
> "fpga.write('memory
> device name', buf, offset)"*. To read from the bram you would do a 
> "*struct.unpack('>1024i',
> fpga.read('memory device name',1024*4,0))"* call - the values 1024, 4 and
> *i* will change depending on the depth of you bram and your data width.
> Within the design, you need to have a counter on the address line to
> iterate through the addresses that you are writing to, and if you are
> planning on writing to the block via casperfpga then you should set *write
> enable *and *data input* to 0; and if you are planning to write in over
> the data line, then *write enable* should be set high with the data line
> tied to wherever your values are coming from. In simulation, you can write
> an array of values (for simulation only) to the "initial values" text box
> within the block that opens when you double click. Then to see what the
> output is doing, you can add a simulink scope block to the bram output.
>
> Hope this helps a bit!
>
> Morag
>
> On Wed, Aug 31, 2022 at 7:48 AM Wang  wrote:
>
>> Hello CASPER，
>>
>> I am currently looking at David's simulink model of PAPER correlator and
>> some other people built simulink models.
>>
>> I met some questions in the process of looking at it.
>> I have been exposed to simulink for a short time and it is not clear how
>> some modules work.
>>
>> The first question.Double-click on the PCORE block and prompt me for a
>> path. I imitate David's input, but no response. Then I check David's PCORE
>> block inside also nothing, may I ask what is wrong with my operation?
>>
>> The second question.I see Share_BRAM blocks used a lot. I want to
>> understand the details of this block, the official website does not seem to
>> have Share_BRAM description. Also, I want to see what is happening to
>> Share_BRAM during simulation. What blocks can I do this with?
>>
>> The third question.I see that a yellow block (not the same color as
>> Casper-libary's block)  does not have a library link. A window appears
>> after double-click :
>> Function Block Parameters: block's name
>> Subsystem (mask)
>> Parameters
>> Number of fft channels (same ad fft prompt)(2^?)
>> Is it a Subsystem block? If yes, how to add the function of double click
>> setting parameter?
>>
>> I really hope you can reply to me, I will be very grateful!
>>
>> BW
>> Wang
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ebeaaba6-c293-4e8b-b874-6ee82b6e387an%40lists.berkeley.edu
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0Te8H4j7OH87VyJB%2BmEC%3DhO4aAmX_DnGG6RQKYMEUhxJAA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKS%3D2mgGySMho%2B2%3D8n0fnW-a2hAtmYaFgEGTmj3A5pUt-XQ%40mail.gmail.com.

Re: [casper] Question of 'PCORE'、'Share_BRAM' and 'Subsystem' block

[Morag Brown]

Hi Wang,

I can't answer the first question, and your third is a bit confusing. Can
you send a screenshot of the block you mean?

As for the shared_bram - this instantiates bram on hardware that is exposed
to the axi/wishbone (depending on the hardware) bus. You can write values (
*vals*) to this block via casperfpga by packing your data using "*buf =
struct.pack('>1024i', *vals)"*, and then write to the bram using*
"fpga.write('memory
device name', buf, offset)"*. To read from the bram you would do a
"*struct.unpack('>1024i',
fpga.read('memory device name',1024*4,0))"* call - the values 1024, 4 and
*i* will change depending on the depth of you bram and your data width.
Within the design, you need to have a counter on the address line to
iterate through the addresses that you are writing to, and if you are
planning on writing to the block via casperfpga then you should set *write
enable *and *data input* to 0; and if you are planning to write in over the
data line, then *write enable* should be set high with the data line tied
to wherever your values are coming from. In simulation, you can write an
array of values (for simulation only) to the "initial values" text box
within the block that opens when you double click. Then to see what the
output is doing, you can add a simulink scope block to the bram output.

Hope this helps a bit!

Morag

On Wed, Aug 31, 2022 at 7:48 AM Wang  wrote:

> Hello CASPER，
>
> I am currently looking at David's simulink model of PAPER correlator and
> some other people built simulink models.
>
> I met some questions in the process of looking at it.
> I have been exposed to simulink for a short time and it is not clear how
> some modules work.
>
> The first question.Double-click on the PCORE block and prompt me for a
> path. I imitate David's input, but no response. Then I check David's PCORE
> block inside also nothing, may I ask what is wrong with my operation?
>
> The second question.I see Share_BRAM blocks used a lot. I want to
> understand the details of this block, the official website does not seem to
> have Share_BRAM description. Also, I want to see what is happening to
> Share_BRAM during simulation. What blocks can I do this with?
>
> The third question.I see that a yellow block (not the same color as
> Casper-libary's block)  does not have a library link. A window appears
> after double-click :
> Function Block Parameters: block's name
> Subsystem (mask)
> Parameters
> Number of fft channels (same ad fft prompt)(2^?)
> Is it a Subsystem block? If yes, how to add the function of double click
> setting parameter?
>
> I really hope you can reply to me, I will be very grateful!
>
> BW
> Wang
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ebeaaba6-c293-4e8b-b874-6ee82b6e387an%40lists.berkeley.edu
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0Te8H4j7OH87VyJB%2BmEC%3DhO4aAmX_DnGG6RQKYMEUhxJAA%40mail.gmail.com.