Hi CASPERites, Thanks to all those who got in touch to share details of instruments. I've just sent an email to those on the author list. If you count yourself a CASPER developer and believe you should be an author, but didn't get this email, it's probably because
- I couldn't find contact details based on your github account or - I misplaced your email when I tried to collate a list of names. In either case, please get in touch asap. There is about ~0% chance I didn't lose any email in the transcription process, so please don't feel offended if you were left out (and, sorry!) -- but please *do* let me know! Thanks, Jack On Tue, 12 Jul 2016 at 17:10 Jack Hickish <jackhick...@gmail.com> wrote: > Hi CASPERites, > > The JAI is having a special issue for radio astronomy DSP, and I think it > would be really great if there was a paper submitted representing the > current state of CASPER hardware/software/toolflow efforts. > > One awesome thing to have in such a paper would be a comprehensive table > of instruments utilising casper technologies. This would also make for a > helpful page on the wiki. To this end, I'd really appreciate it if > CASPERites who have built or deployed instruments could send me a brief > description of their systems including, if possible -- > > Name of experiment. (eg, "PAPER") > Brief description. (eg. "128 dual-pol antenna, 100-200 MHz FX packetized > correlator") > Year deployed. > CASPER Hardware used (eg. "8 ROACH2s, 16 ADC16s") > Functionality provided by CASPER hardware (eg. "Digitization and > channelisation") > Relevant citation (obviously peer-reviewed is better, but I know that > writing-up is not entirely how a lot of us roll... (bonus points for > including bibtex)) > Any other notes. > > I was envisaging including the CASPER advisory board, and all who have > made commits to the casper-astro/mlib_devel repository as authors on this > paper. However, there are many others who have contributed to > hardware/software, who don't appear here and in any case many of the users > making commits don't supply real names or emails. > ***If you wish to be an author on this paper please let me know by > replying to this email*** > I would suggest that anyone working so support the CASPER collaboration or > fitting a vague and inclusive definition of "CASPER developer" should be an > author, though if this ends up becoming controversial I will defer to the > wisdom of the advisory board. > The deadline for JAI submission for the special edition is 15th Aug, so > time is pretty tight. In the very near future I'll be get in touch with all > those who would like to be authors and share details to those wishing to > make edits / contributions. (Though I suspect any determined casperite > could probably figure out where the source code for this paper is....) > > Obviously any comments, on- or off-list are gratefully received. > > Cheers > > Jack > > > > > >
