<div dir="ltr">What is the wwv ssr project?<div><br></div><div>cheers, Graham ve3gtc</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 14, 2019 at 7:58 PM Kristina Collins via TangerineSDR <<a href="mailto:tangerinesdr@lists.tapr.org">tangerinesdr@lists.tapr.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Stephen,<br>
<br>
That's a reasonable concern. I should note that it's part of a larger<br>
feature on the use of ham radio for space science, covering HamSCI and<br>
the WWV SSR project as well. Tangerine isn't the focus, but I'd like<br>
to touch on it as part of the discussion of the PSWS and related<br>
citizen science activity in the ham community.<br>
<br>
I'll be on the TeamSpeak call this evening and look forward to<br>
checking in with folks then.<br>
<br>
73,<br>
-KC<br>
<br>
On 10/14/19, Stephen Roland Kaeppler via TangerineSDR<br>
<<a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a>> wrote:<br>
> Hi All-<br>
><br>
> I saw the thread about the elevator pitch into EOS. I am a little bit<br>
> concerned that this might be premature? Shouldn't we have a working<br>
> prototype first and then perhaps pitch what it can be used for? Or possibly<br>
> some initial data?<br>
><br>
> I am open to other options, but EOS is a broad audience, so I feel we should<br>
> have something that is more complete... but that is my just my two cents.<br>
><br>
> 73,<br>
> Steve AD0AE<br>
> ------------------------------------------------------------<br>
> Stephen R. Kaeppler, Ph.D.<br>
> Assistant Professor<br>
> Department of Physics and Astronomy<br>
> Clemson University<br>
> Clemson, SC 29634<br>
> Email: <a href="mailto:skaeppl@clemson.edu" target="_blank">skaeppl@clemson.edu</a><br>
> Phone: 864-656-4275<br>
> Web: <a href="http://science.clemson.edu/kaeppler/" rel="noreferrer" target="_blank">http://science.clemson.edu/kaeppler/</a><br>
> Amateur Radio Callsign: AD0AE<br>
> ------------------------------------------------------------<br>
><br>
><br>
> On 10/14/19, 12:00 PM, "TangerineSDR on behalf of<br>
> <a href="mailto:tangerinesdr-request@lists.tapr.org" target="_blank">tangerinesdr-request@lists.tapr.org</a>" <<a href="mailto:tangerinesdr-bounces@lists.tapr.org" target="_blank">tangerinesdr-bounces@lists.tapr.org</a> on<br>
> behalf of <a href="mailto:tangerinesdr-request@lists.tapr.org" target="_blank">tangerinesdr-request@lists.tapr.org</a>> wrote:<br>
><br>
> Send TangerineSDR mailing list submissions to<br>
> <a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:tangerinesdr-request@lists.tapr.org" target="_blank">tangerinesdr-request@lists.tapr.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:tangerinesdr-owner@lists.tapr.org" target="_blank">tangerinesdr-owner@lists.tapr.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of TangerineSDR digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: TangerineSDR Digest, Vol 7, Issue 10 (Scotty Cowling)<br>
> 2. Re: Elevator Pitch for Tangerine PSWS (Scotty Cowling)<br>
> 3. Re: Seeking your Review and Comment on Tangerine SBC<br>
> Functional Specification (Engelke, Bill)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Sun, 13 Oct 2019 13:59:08 -0700<br>
> From: Scotty Cowling <<a href="mailto:scotty@tonks.com" target="_blank">scotty@tonks.com</a>><br>
> To: <a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a><br>
> Subject: Re: [TangerineSDR] TangerineSDR Digest, Vol 7, Issue 10<br>
> Message-ID: <<a href="mailto:c238a2b4-38c7-0854-141d-e46844bcf4a5@tonks.com" target="_blank">c238a2b4-38c7-0854-141d-e46844bcf4a5@tonks.com</a>><br>
> Content-Type: text/plain; charset=utf-8; format=flowed<br>
><br>
> Hi Larry,<br>
><br>
> Welcome to the list! What kind of data are you looking for in the 15 to<br>
> 30 MHz spectrum? Are you just looking for energy content or are you<br>
> looking to demodulate certain sub bands? Or maybe energy content in<br>
> specific sub-bands?<br>
><br>
> Just trying to get an idea of the processing that the TangerineSDR will<br>
> need to do on the input data in order to make sure that we can fulfill<br>
> your use case.<br>
><br>
> 73,<br>
> Scotty WA2DFI<br>
><br>
> On 2019-10-12 09:29, Larry Dodd via TangerineSDR wrote:<br>
>> Hi<br>
>> I?m a member of the NASA volunteer RadioJOVE project. We are very<br>
>> interested in your work to produce a PSWS with TangerineSDR. We monitor<br>
>> the 15 to 30 MHz spectrum 24/7/365 for Jupiter storms, Solar avtivity and<br>
>> the ionosphere in general and looking for an SDR to meet our future needs.<br>
>> Thanks to everyone working on this project.<br>
>> Larry<br>
>> K4LED<br>
>><br>
>>> On Oct 12, 2019, at 12:00 PM, <a href="mailto:tangerinesdr-request@lists.tapr.org" target="_blank">tangerinesdr-request@lists.tapr.org</a> wrote:<br>
>>><br>
>>> ?Send TangerineSDR mailing list submissions to<br>
>>> <a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a><br>
>>><br>
>>> To subscribe or unsubscribe via the World Wide Web, visit<br>
>>> <a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
>>> or, via email, send a message with subject or body 'help' to<br>
>>> <a href="mailto:tangerinesdr-request@lists.tapr.org" target="_blank">tangerinesdr-request@lists.tapr.org</a><br>
>>><br>
>>> You can reach the person managing the list at<br>
>>> <a href="mailto:tangerinesdr-owner@lists.tapr.org" target="_blank">tangerinesdr-owner@lists.tapr.org</a><br>
>>><br>
>>> When replying, please edit your Subject line so it is more specific<br>
>>> than "Re: Contents of TangerineSDR digest..."<br>
>>><br>
>>><br>
>>> Today's Topics:<br>
>>><br>
>>> 1. Elevator Pitch for Tangerine PSWS (Kristina Collins)<br>
>>> 2. Re: Elevator Pitch for Tangerine PSWS (Phil Erickson)<br>
>>><br>
>>><br>
>>> ----------------------------------------------------------------------<br>
>>><br>
>>> Message: 1<br>
>>> Date: Fri, 11 Oct 2019 15:06:22 -0400<br>
>>> From: Kristina Collins <<a href="mailto:kvc2@case.edu" target="_blank">kvc2@case.edu</a>><br>
>>> To: <a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a><br>
>>> Subject: [TangerineSDR] Elevator Pitch for Tangerine PSWS<br>
>>> Message-ID:<br>
>>> <<a href="mailto:CAEeerr78U8UZP96jECqp3wW%2BwQEZpjg5_oE-E7GuiYOZcxKEpQ@mail.gmail.com" target="_blank">CAEeerr78U8UZP96jECqp3wW+wQEZpjg5_oE-E7GuiYOZcxKEpQ@mail.gmail.com</a>><br>
>>> Content-Type: text/plain; charset="utf-8"<br>
>>><br>
>>> Hi all,<br>
>>><br>
>>> I'm putting together an article for Eos (<a href="http://eos.org" rel="noreferrer" target="_blank">eos.org</a>) on the use of ham<br>
>>> radio<br>
>>> in geoscience, focusing on the two versions of the PSWS. What salient<br>
>>> points should I be making about the Tangerine and its role? I have a few<br>
>>> hundred words to work with for that part of the article.<br>
>>><br>
>>> Bonus question for the space scientists in the audience (looking at you,<br>
>>> Phil & Nathaniel): What should I say about TIDs and other phenomena we<br>
>>> want<br>
>>> to characterize?<br>
>>><br>
>>> -KC<br>
>>> -------------- next part --------------<br>
>>> An HTML attachment was scrubbed...<br>
>>> URL:<br>
>>> <<a href="http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20191011/b0ab43b4/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20191011/b0ab43b4/attachment-0001.html</a>><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> Message: 2<br>
>>> Date: Fri, 11 Oct 2019 15:08:46 -0400<br>
>>> From: Phil Erickson <<a href="mailto:phil.erickson@gmail.com" target="_blank">phil.erickson@gmail.com</a>><br>
>>> To: TAPR TangerineSDR Modular Software Defined Radio<br>
>>> <<a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a>><br>
>>> Subject: Re: [TangerineSDR] Elevator Pitch for Tangerine PSWS<br>
>>> Message-ID:<br>
>>> <CAAZaqEuy31y=S5Q=<a href="mailto:6k3TOTJ4%2Bg9CH%2BodKCSZu2U_AxjisJONkQ@mail.gmail.com" target="_blank">6k3TOTJ4+g9CH+odKCSZu2U_AxjisJONkQ@mail.gmail.com</a>><br>
>>> Content-Type: text/plain; charset="utf-8"<br>
>>><br>
>>> Hi Kristina,<br>
>>><br>
>>> I can't answer that question until I see the context of the rest of<br>
>>> the<br>
>>> article. Best to put a draft together and share it in an editable<br>
>>> online<br>
>>> place such as Overleaf (if LaTeX source) or Google Docs, and then we can<br>
>>> crowdsource it.<br>
>>><br>
>>> Cheers<br>
>>> Phil<br>
>>><br>
>>>> On Fri, Oct 11, 2019 at 3:07 PM Kristina Collins via TangerineSDR <<br>
>>>> <a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a>> wrote:<br>
>>>><br>
>>>> Hi all,<br>
>>>><br>
>>>> I'm putting together an article for Eos (<a href="http://eos.org" rel="noreferrer" target="_blank">eos.org</a>) on the use of ham<br>
>>>> radio<br>
>>>> in geoscience, focusing on the two versions of the PSWS. What salient<br>
>>>> points should I be making about the Tangerine and its role? I have a<br>
>>>> few<br>
>>>> hundred words to work with for that part of the article.<br>
>>>><br>
>>>> Bonus question for the space scientists in the audience (looking at<br>
>>>> you,<br>
>>>> Phil & Nathaniel): What should I say about TIDs and other phenomena we<br>
>>>> want<br>
>>>> to characterize?<br>
>>>><br>
>>>> -KC<br>
>>>> --<br>
>>>> TangerineSDR mailing list<br>
>>>> <a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
>>>> <a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
>>>><br>
>>><br>
>>> --<br>
>>> ----<br>
>>> Phil Erickson<br>
>>> <a href="mailto:phil.erickson@gmail.com" target="_blank">phil.erickson@gmail.com</a><br>
>>> -------------- next part --------------<br>
>>> An HTML attachment was scrubbed...<br>
>>> URL:<br>
>>> <<a href="http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20191011/b6bd032d/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20191011/b6bd032d/attachment-0001.html</a>><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> Subject: Digest Footer<br>
>>><br>
>>> TangerineSDR mailing list<br>
>>> <a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
>>> <a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
>>><br>
>>><br>
>>> ------------------------------<br>
>>><br>
>>> End of TangerineSDR Digest, Vol 7, Issue 10<br>
>>> *******************************************<br>
><br>
><br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Sun, 13 Oct 2019 15:59:08 -0700<br>
> From: Scotty Cowling <<a href="mailto:scotty@tonks.com" target="_blank">scotty@tonks.com</a>><br>
> To: <a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a><br>
> Subject: Re: [TangerineSDR] Elevator Pitch for Tangerine PSWS<br>
> Message-ID: <<a href="mailto:5f9d9f8d-dec2-53d4-9cb9-a6c60d04185d@tonks.com" target="_blank">5f9d9f8d-dec2-53d4-9cb9-a6c60d04185d@tonks.com</a>><br>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
><br>
> Hi Kristina,<br>
><br>
> The main points of the TangerineSDR are:<br>
> Wide-band Direct Sampling DDC (four 500MByte/s digital input paths) with<br>
> on-board FPGA<br>
> High-speed data interfaces (USB 3.0 (@5Gbps) *and* dual GBe)<br>
> Modularity and expandability (up to 4 RF input channels, selectable<br>
> oscillator quality (TCXO/OCXO/GPSDO) and expandable low- and high-speed<br>
> I/O)<br>
> Easy pairing with SBC or Desktop PC (dual GBe ports) allows inexpensive<br>
> pre-processing and network authentication<br>
><br>
> Is that some help in filling a few hundred words? The above is more like<br>
> a features list, so here are a few tie-ins to PSWS:<br>
> oscillator can be upgraded to GPSDO for PSWS high-resolution data<br>
> time-stamping<br>
> dual, synchronously clocked 14-bit ADCs for synchronous RF sampling<br>
> seamlessly integrates with a Single-Board Computer to provide PSWS<br>
> pre-processing and authentication<br>
> high-speed data interfaces provide wide simultaneous receive bandwidth?<br>
> (>20MHz via GBe, >100MHz USB3.0 maximum)<br>
> FPGA can split data into eight 192KHz simultaneous virtual receive<br>
> streams, each centered anywhere within 0-60MHz antenna input<br>
><br>
> Hope some of this is helpful.<br>
><br>
> 73,<br>
> Scotty WA2DFI<br>
><br>
> On 2019-10-11 12:06, Kristina Collins via TangerineSDR wrote:<br>
>> Hi all,<br>
>><br>
>> I'm putting together an article for Eos (<a href="http://eos.org" rel="noreferrer" target="_blank">eos.org</a> <<a href="http://eos.org" rel="noreferrer" target="_blank">http://eos.org</a>>) on<br>
>> the use of ham radio in geoscience, focusing on the two versions of<br>
>> the PSWS. What salient points should I be making about the Tangerine<br>
>> and its role? I have a few hundred words to work with for that part of<br>
>> the article.<br>
>><br>
>> Bonus question for the space scientists in the audience (looking at<br>
>> you, Phil & Nathaniel): What should I say about TIDs and other<br>
>> phenomena we want to characterize?<br>
>><br>
>> -KC<br>
>><br>
><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20191013/06d71c12/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20191013/06d71c12/attachment-0001.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Mon, 14 Oct 2019 15:22:30 +0000<br>
> From: "Engelke, Bill" <<a href="mailto:bill.engelke@ua.edu" target="_blank">bill.engelke@ua.edu</a>><br>
> To: Rob Wiesler <<a href="mailto:robert.wiesler@case.edu" target="_blank">robert.wiesler@case.edu</a>>, "TAPR TangerineSDR Modular<br>
> Software Defined Radio" <<a href="mailto:tangerinesdr@lists.tapr.org" target="_blank">tangerinesdr@lists.tapr.org</a>><br>
> Subject: Re: [TangerineSDR] Seeking your Review and Comment on<br>
> Tangerine SBC Functional Specification<br>
> Message-ID: <<a href="mailto:52047bd0a2254d3c80ed98c98973629a@ua.edu" target="_blank">52047bd0a2254d3c80ed98c98973629a@ua.edu</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> Rob, I added the distribution list as you suggested. I greatly value your<br>
> knowledgeable feedback, so please keep it coming.<br>
><br>
> Regarding Celery: I am not crazy about Celery; I mention it only because it<br>
> is used in the SatNOGS system. We have decided that we wish base the PSWS<br>
> Central Control system/database on SatNOGS (at least for Phase 1), as its<br>
> functionality and UI seems to overlap so much on our needs. Having said that<br>
> (since you mention that Celery may not fit the need), we should probably<br>
> discuss what data is going to be generated, and then seek the right package<br>
> for managing the uploads. (As an aside, I have the entire SatNOGS system<br>
> running on a server; if you like, we can look at it together on a Zoom<br>
> session, and see what they are actually using Celery for).<br>
><br>
> On the topic of heterogeneous vs homogeneous data, right now we envision two<br>
> distinct data types:<br>
><br>
> 1. Raw I/Q data from ring buffer ("Use Case 1"). These data are stored in<br>
> ring buffer in Digital RF format. On request from Central Control, a<br>
> selected chunk of data (from start time A to end time B) are to uploaded.<br>
> Upon receipt, Central Control stores these as Digital RF files, with the<br>
> file name being generated automatically, and the file name being stored in<br>
> the database.<br>
><br>
> 2. Pre-processed data. ("Use Case 3") This case is for users with low<br>
> bandwidth. An upload occurs about once per second (or could be as low as<br>
> once per minute). GNURadio samples the bands (normally a few Hz around each<br>
> WWV station), and does an FFT. The FFT is uploaded (along with magnetometer<br>
> data) and stored directly in a database table.<br>
><br>
> (There is a third situation, "Use Case 2," or "firehose," where raw data is<br>
> streamed directly to a server. Central Control does not support that; it<br>
> would be received by the institution's server farm or supercomputer).<br>
><br>
> Use Case 3, best I can tell, matches what SatNOGS does: they pre-process<br>
> received spectrum into a waterfall, and that's what they upload. We can<br>
> certainly ask them why they picked Celery to use (for all I know, maybe they<br>
> regret it). Maybe they are using Celery for something else (i.e., not for<br>
> uploading). Its complexity definitely increases project risk.<br>
><br>
> There are numerous other queueing packages. I have used IBM's Websphere MQ<br>
> (works great, but costs a fortune) and MQTT, both with good success;<br>
> however, I also gather we need to distinguish between task queueing and data<br>
> queueing. Maybe there is an apples-to-oranges here. Anyway , let me know<br>
> your thoughts.<br>
><br>
> -73- Bill, AB4EJ<br>
><br>
><br>
> -----Original Message-----<br>
> From: Rob Wiesler <<a href="mailto:robert.wiesler@case.edu" target="_blank">robert.wiesler@case.edu</a>><br>
> Sent: Saturday, October 12, 2019 6:03 PM<br>
> To: Engelke, Bill <<a href="mailto:bill.engelke@ua.edu" target="_blank">bill.engelke@ua.edu</a>><br>
> Subject: Re: Seeking your Review and Comment on Tangerine SBC Functional<br>
> Specification<br>
><br>
> Bill, I won't re-add the mailing list to the distribution list without your<br>
> permission, but in general please keep responses on-list, as it becomes<br>
> difficult for anyone else to participate otherwise.<br>
><br>
> On Wed, Oct 9, 2019 at 4:33 PM Engelke, Bill <<a href="mailto:bill.engelke@ua.edu" target="_blank">bill.engelke@ua.edu</a>> wrote:<br>
>> Rob - for file backlogs, the plan is to use Celery,<br>
>> (<a href="http://www.celeryproject.org/" rel="noreferrer" target="_blank">http://www.celeryproject.org/</a>) , this works very well for uploading<br>
>> the large # of files for SatNOGS, and integrates well with Django. I<br>
>> had been hoping to continue to use that. (I will still research<br>
>> inotify so I know what it can do as well ) -<br>
><br>
> I highly recommend not adding a dependency on Celery for this particular<br>
> thing (or, preferably, at all). Celery is a queue for asynchronous<br>
> processing of heterogeneous tasks, while what we need is a queue for serial<br>
> processing of homogeneous data. We don't want our individual data files to<br>
> end up in different tasks, because that implies a separate connection to<br>
> upload each file (versus a single TCP stream where each data file is sent in<br>
> serial for better throughput).<br>
> We want one upload task, and a data queue (not a task queue) sitting in<br>
> front of it. If SatNOGs uses Celery, it's probably not involved in the step<br>
> you're thinking of, and if I'm wrong about that, then that's a giant,<br>
> fluorescent red flag saying that we shouldn't be following their lead on<br>
> this.<br>
><br>
> I'll also point out that Celery is a incredibly complicated library<br>
> (>7000 lines without counting dependencies) that introduces a ton of<br>
> dependencies. The Celery FAQ gives lame, half-baked excuses for why this<br>
> doesn't matter, but it definitely does matter (which I could get into, but<br>
> for now that's outside the scope of this document). The only upside is that<br>
> Celery is actually packaged for Debian, so if we did decide to use it (for a<br>
> purpose to which it's actually suited), those dependencies are somewhat more<br>
> manageable.<br>
><br>
> Why do you think that Django integration is relevant? I wasn't aware that<br>
> there was any interaction between the store-forward mechanism and a web page<br>
> running on the SBC. Even if we want to publish how many stored, unsent data<br>
> files there are (and how much space they're taking up (In memory? On disk?)<br>
> and how much space is left), there are significantly better ways to do<br>
> that.<br>
><br>
> The first draft of this email had more reasons not to use Celery, because it<br>
> isn't at all suited as a store-forward system. Now that I'm awake and<br>
> thinking clearly, we don't necessarily want to store every single data file<br>
> to an actual disk in case of power loss before the upload catches up with<br>
> the backlog (since that's currently a sticking point for the ringbuffer), so<br>
> those points are moot.<br>
> However, I will say that if we overcome the problems associated with the<br>
> ringbuffer, then Celery is *definitely* not what we want to use.<br>
> Note also that inotify still works in a memory-backed tmpfs, so if we wanted<br>
> to write an in-memory data queue first, then turn it into a on-disk<br>
> ringbuffer later, that would be a trivial change.<br>
><br>
> ------------------------------<br>
><br>
> Subject: Digest Footer<br>
><br>
> TangerineSDR mailing list<br>
> <a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
> <a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
><br>
><br>
> ------------------------------<br>
><br>
> End of TangerineSDR Digest, Vol 7, Issue 12<br>
> *******************************************<br>
><br>
><br>
> --<br>
> TangerineSDR mailing list<br>
> <a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
> <a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
><br>
<br>
-- <br>
TangerineSDR mailing list<br>
<a href="mailto:TangerineSDR@lists.tapr.org" target="_blank">TangerineSDR@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org" rel="noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org</a><br>
</blockquote></div>