mhostetter
commented
4 years ago The webserver language (or Python version) is completely independent of the flowgraph (3.7 vs 3.8) or the webpage operation. So it can be a Python 2 or 3 Flask application or a node application. The flowgraph-to-webserver interface is ZMQ PUB/SUB and the webserver-to-webpage interface is web sockets. As long as the Python 3 conversion supports those, which it will, it will be interoperable. So there isn't a need for a PMT serializer/deserializer program.
I do agree on the utility of recording and playing back data, however. That was actually the intent of my other project gr-sqlite. If you connect a SQLite Sink to the ADS-B Decoder output that will log those packets to a database. You can create a separate flowgraph that reads back those packets (in time order) and transmits them to the webserver. That flowgraph would be a SQLite Timed Source connected to the ZMQ Pub Message Sink. I could easily create an example and add it the the examples/ directory.
potto216
I would be interested in getting the Web Server to run in Python 3 with the GNURadio 3.8 packages. It seems like this could be accomplished independent of the demodulator conversion, by writing a Python program to simulate the serialization of the pmt key/values and pushing them over the ZMQ socket to the web server. This test program would also serve as a way to validate the functionality of the web server. Matt, what are your thoughts on this?