rfsoc_studio
literary
Our great sponsors
rfsoc_studio | literary | |
---|---|---|
1 | 1 | |
22 | 11 | |
- | - | |
0.0 | 0.0 | |
over 1 year ago | over 1 year ago | |
Jupyter Notebook | Jupyter Notebook | |
BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rfsoc_studio
-
This week I am looking at the RFSoC Studio and PYNQ. Really interesting especially is you can get a RFSOC 2x2
Looks like the author forget to post the GitHub repository for the original work. You can grab it here: https://github.com/strath-sdr/rfsoc_studio
literary
-
Automated PDF Reports with Python Notebooks
Eh, I think this misses the point of why Jupyter Notebooks are useful, and who is using them.
I agree that in terms of literate programming as Knuth defined it, Notebooks are not great. There are tools to improve that story; I wrote https://github.com/agoose77/literary which at least lets you do a bit more "tangling and weaving" than you can out of the box. It doesn't let you define functions in arbitrary order, or implement fragments of a code block, but it does let you "boil down" a literate representation into something that is zero-cost at runtime and imports. There's also nbdev, although it's not my cup of tea.
The real point, though, is that most data-scientists aren't using (imo) notebooks to write and share libraries of code. Instead, they're using notebooks as semi-reproducible reports. I'm a physicist, and that's what I've been using Jupyter for. For me, Jupyter Notebooks are fantastic - the cell mechanism lends itself to rich-outputs that augment the narrative, and present the information in-line with the code that wrote it.
For me, the biggest gap here is writing _libraries_ that are leveraged in these notebooks. That's why I wrote Literary - to try and resolve some of the pain points that currently require you to use two tools (Jupyter Lab & e.g. PyCharm). I'm not saying it will work for everyone, or solve all of the problems, but for me it's enough to write my analysis as a package, so that's a limited success in my book.
What are some alternatives?
finn-examples - Dataflow QNN inference accelerator examples on FPGAs
mercury - Convert Jupyter Notebooks to Web Apps
Alveo-PYNQ - Introductory examples for using PYNQ with Alveo
Audio-Spectrum-Display - Version 1.0 of ESP32 powered Audio Spectrum Display
fastai - The fastai deep learning library
voila - Using VoilĂ with matplotlib example
AcademicContent - Free tech resources for faculty, students, researchers, life-long learners, and academic community builders for use in tech based courses, workshops, and hackathons.