# Build-gnuradio statistics

**URL:** <https://www.ruby-forum.com/t/build-gnuradio-statistics/235054>\
**Category:** GNU Radio\
**Created:** [May 28, 2013, 6:17pm UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054 "2013-05-28T18:17:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alcina](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a587f6/32.png) [@alcina](https://www.ruby-forum.com/u/alcina)\
**Post date:** [May 28, 2013, 6:17pm UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054/1 "2013-05-28T18:17:04Z")

</div>

So, I’ve added a exit-handler routine to build-gnuradio to try to  
capture some basic statistics about success/failure when the script is  
run.

I’d like some suggestions about automating uploading of this one-liner  
of stats data to some website somewhere so that I can review it.  
Maybe something we can turn on on the [gnuradio.org](http://gnuradio.org) website?

I can’t use e-mail, because that would involve grokking the callers  
local e-mail environment. And that would have privacy implications.

–  
Marcus L.  
Principal Investigator  
Shirleys Bay Radio Astronomy Consortium

> **[Live Draw HK Tercepat | Result HK | HK Pools | Live HK | HK Prize Hari Ini](https://www.sbrac.org/)**
>
> Temukan live draw hk tercepat melalui halaman hk pools yang resmi dan dapatkan result hk prize melalui live hk secara langsung di situs kami.

---

<div class="post-metadata">

**Author:** ![Marcus\_DSLeech](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@Marcus\_DSLeech](https://www.ruby-forum.com/u/Marcus_DSLeech)\
**Post date:** [May 28, 2013, 6:32pm UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054/2 "2013-05-28T18:32:16Z")

</div>

On Tue, May 28, 2013 at 9:14 AM, Marcus D. Leech [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> I’d like some suggestions about automating uploading of this one-liner of  
> stats data to some website somewhere so that I can review it.  
> Maybe something we can turn on on the [gnuradio.org](http://gnuradio.org) website?

You could ask in the script if the user wants to send feedback via email  
or  
not, with the default set to no. Otherwise, any automated system would  
likely be negatively perceived.

That said, I could see having an email processing bot on [gnuradio.org](http://gnuradio.org)  
turn  
received emails into a statistics page, said bot being written by you of  
course 🙂

---

<div class="post-metadata">

**Author:** ![Marcus\_DSLeech](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@Marcus\_DSLeech](https://www.ruby-forum.com/u/Marcus_DSLeech)\
**Post date:** [May 28, 2013, 6:44pm UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054/3 "2013-05-28T18:44:33Z")

</div>

On 05/28/2013 12:30 PM, Johnathan C. wrote:

> You could ask in the script if the user wants to send feedback via  
> [http://corganlabs.com](http://corganlabs.com)  
> So–trade maint of statistics page for maint of build-gnuradio itself?  
> It’s a trap! 🙂

---

<div class="post-metadata">

**Author:** ![Marcus\_DSLeech](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@Marcus\_DSLeech](https://www.ruby-forum.com/u/Marcus_DSLeech)\
**Post date:** [May 28, 2013, 6:57pm UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054/4 "2013-05-28T18:57:24Z")

</div>

On 05/28/2013 12:44 PM, Martin L. wrote:

> Hi,
> 
> I would solve this with a small PHP Script on the webserver (or  
> whatever scripting language is available on the webserver). The script  
> can evaluate the called URL including parameters.
> 
> So in the build gnuradio script you would call something like this  
> wget [http://example.com/script.php?param1=5&param2=pi](http://example.com/script.php?param1=5&param2=pi)

> The Script on the webserver will now have access to param1 and param2  
> and can store them in a Database, or whatever you would like to do and  
> can return (echo) a few charakters (e.g. 1 ok, 0 malformed parameter).  
> Yes, I was thinking something through wget as well…

> Yours  
> Martin

I’ll have to think about this. I don’t want to add even more work to my  
workload, but I would like to understand what fraction of build-gnuradio  
invocations are failing, and why.

–  
Marcus L.  
Principal Investigator  
Shirleys Bay Radio Astronomy Consortium

> **[Live Draw HK Tercepat | Result HK | HK Pools | Live HK | HK Prize Hari Ini](https://www.sbrac.org)**
>
> Temukan live draw hk tercepat melalui halaman hk pools yang resmi dan dapatkan result hk prize melalui live hk secara langsung di situs kami.

---

<div class="post-metadata">

**Author:** ![Marcus\_DSLeech](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@Marcus\_DSLeech](https://www.ruby-forum.com/u/Marcus_DSLeech)\
**Post date:** [May 29, 2013, 12:40am UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054/5 "2013-05-29T00:40:22Z")

</div>

So, given that my website maintains raw access logs that are available  
to me, I’ve updated build-gnuradio to do a wget call to a  
non-actually-there  
.php so that I can grab some parameters that will show up in the raw  
logs, that I can process from time to time. Easy peasy.

The exit() handler in Gnu Radio now asks you politely if you’d like to  
contribute to the stats, but it doesn’t force it.

–  
Marcus L.  
Principal Investigator  
Shirleys Bay Radio Astronomy Consortium

> **[Live Draw HK Tercepat | Result HK | HK Pools | Live HK | HK Prize Hari Ini](https://www.sbrac.org)**
>
> Temukan live draw hk tercepat melalui halaman hk pools yang resmi dan dapatkan result hk prize melalui live hk secara langsung di situs kami.

---

<div class="post-metadata">

**Author:** ![Marcus\_DSLeech](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@Marcus\_DSLeech](https://www.ruby-forum.com/u/Marcus_DSLeech)\
**Post date:** [May 28, 2013, 6:46pm UTC](https://www.ruby-forum.com/t/build-gnuradio-statistics/235054/6 "2013-05-28T18:46:18Z")

</div>

Hi,

I would solve this with a small PHP Script on the webserver (or whatever  
scripting language is available on the webserver). The script can  
evaluate the called URL including parameters.

So in the build gnuradio script you would call something like this  
wget [http://example.com/script.php?param1=5&param2=pi](http://example.com/script.php?param1=5&param2=pi)

The Script on the webserver will now have access to param1 and param2  
and can store them in a Database, or whatever you would like to do and  
can return (echo) a few charakters (e.g. 1 ok, 0 malformed parameter).

This way the build gnuradio script can then evaluate the content of the  
downloaded file to see if anything went wrong.

For this to work you only need HTTP access to the script webserver on  
the install PC. Many PCs are behind Firewalls that drop traffic on Port  
25 if you try to use Email, but port 80 is almost always oppen.

I also agree with Jonathan, that sending back feedback should be a  
opt-in decision during the installation.

Yours  
Martin

Am 28.05.2013 18:30, schrieb Johnathan C.:
