Project:LHS Graphs and Visualizations: Difference between revisions

From London Hackspace Wiki
m (→‎Metrics: Babbage deprecation)
 
(18 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Project|members=[[User:Teabot|Elliot]]}}
{{Project|members=[[User:Teabot|Elliot]]}}
===Overview===
==Overview==
I'd like to supplement [http://hack.rs/cacti/graph_view.php?action=tree&tree_id=1 the Cacti graphs] that we have for LHS bandwidth and power with metrics that provide insight to the growth of our community and organisation over time.
I have supplemented [http://hack.rs/cacti/graph_view.php?action=tree&tree_id=1 the Cacti graphs] that we have for LHS bandwidth and power with [http://hack.rs/cacti/graph_view.php?action=tree&tree_id=5 metrics] that provide insight to the growth of our community and organisation over time.


Phase 1 is complete and we now [http://hack.rs/cacti/graph_view.php?action=tree&tree_id=5 chart the following]:
To chart the metrics various bits of data are exposed in a Cacti friendly way.
* Number of members
* IRC activity
* Wiki activity
* Mailing list activity


Later I'd like to investigate:
==Metrics==
* Website visitors and/or page impressions
===Number of members===
* Space occupancy


==In progress==
We may have to wait 12 months before it becomes interesting.
 
====Space occupancy====
I have located two Laser Diode Retroreflective Sensors in our stores which I intend to use to monitor space occupancy by having the beams cross the main doorway. The beams will be staggered so that direction (arriving, leaving) can be determined by the order in which the beams are broken. I was thinking of mounting them at waist height.
 
* This will probably get caught out by clusters of people: --[[81.105.17.61]]
** We only need an approximate count
** The doorway is narrow so it's unlikely that the steps of more than one individual will overlap.
** Most of the time people won't arrive in clusters
* Can we detect some other event such as the door opening after a prolonged lights-out period to force the count to zero? --[[81.105.17.61]]
** Yes, using the door/lights data for reset would be good if  we get large amounts of drift - but I don't plan to just yet
** This might fail if people spend the night there.  AIUI this happens rarely enough that we may not care about the inaccuracy.
** We could also use some kind of probabilistic model with the 'door-open' and 'bell' data
 
=====Location=====
The current mounting location has the lasers In close proximity in the middle of the entrance way. To avoid issues with occlusion of beams by coats etc, the coat hooks have been moved to the next wall along, with the lab coats. This arrangement greatly simplifies the detection of the true direction of someone entering/leaving the space.
 
Detection works reasonably well but there is currently a reset delay of 1 second meaning that a person following another at an interval at less than one second will not be detected. It turns out that this is quite common and leads to 'under-counting'.
 
The occupancy level is currently [http://hack.rs/cacti/graph.php?action=view&local_graph_id=35&rra_id=all charted on cacti]. The [https://github.com/londonhackspace/spacensus python script] that provides the data to cacti implements only the 'pool for status' command, but will later allow more control and configuration of the counting sensors.
 
=====Hardware=====
These sensors appear to be in working order. They'd should be safe to use below child-head height. They were manufactured in 1996 and use a [http://en.wikipedia.org/wiki/Laser_safety#Class_II Class II] laser rated at 3mW with a wavelength of 655-670nm ([[Media:Banner-q45bb6ll.pdf|datasheet]]). The model number is: Q45BB6LL
 
A good signal can be obtained at 1.5m by using a reflector made of aluminium tape.
 
* [http://www.flickr.com/photos/travelbot/5411266701 spacensus v0.1 board]
 
==Desired==
 
====Website visitors and/or page impressions====
The main site and the Wiki use Google Analytics and this has an API. This [http://code.google.com/apis/analytics/docs/gdata/gdataCommonQueries.html documented method] looks promising:
  https://www.google.com/analytics/feeds/data?metrics=ga%3Avisits%2Cga%3Apageviews&start-date=2010-11-29&end-date=2010-12-13&max-results=50
 
==Done==
 
To chart the initial metrics various bits of data are exposed in a Cacti friendly way.
 
====Number of members====
 
'''COMPLETE''' - but may have to wait 12 months before it becomes interesting.


This data is stored in an Sqlite database on [[Turing]].  See the [https://github.com/londonhackspace/hackspace-foundation-sites/blob/master/etc/schema.sql Schema]. It can be queried like so:
This data is stored in an Sqlite database on [[Turing]].  See the [https://github.com/londonhackspace/hackspace-foundation-sites/blob/master/etc/schema.sql Schema]. It can be queried like so:
Line 61: Line 16:
   WHERE subscribed = true;
   WHERE subscribed = true;


Cacti runs on babbage but the members database is on Turing. There is a PHP script on Turing to expose the member numbers and then a script on babbage to pull this in with a HTTP request.
Cacti runs on chomsky but the members database is on Turing. There is a PHP script on Turing to expose the member numbers and then a script on chomsky to pull this in with a HTTP request.
 
''Code:'' https://github.com/londonhackspace/monitoring


'''Code:''' https://github.com/londonhackspace/monitoring
''URL:'' http://london.hackspace.org.uk/member_stats.php
'''URL:''' http://london.hackspace.org.uk/member_stats.php


====Wiki statistics====
===IRC statistics===
'''COMPLETE'''
''See project: [[Project:Ircensus|ircensus]]''


===Wiki statistics===
* We get this using the MediaWiki API:
* We get this using the MediaWiki API:


Line 95: Line 52:
A Perl script generates the following output for cacti: '''<tt>pages:759 articles:215 views:229656 edits:7368 images:186 users:166 activeusers:22 admins:61 jobs:13</tt>'''
A Perl script generates the following output for cacti: '''<tt>pages:759 articles:215 views:229656 edits:7368 images:186 users:166 activeusers:22 admins:61 jobs:13</tt>'''


'''Code:''' https://github.com/londonhackspace/monitoring
''Code:'' https://github.com/londonhackspace/monitoring


====IRC statistics====
===Mailing list activity===
 
'''COMPLETE'''
 
There is a bot ([https://github.com/londonhackspace/ircensus ircensus]) in the #london-hack-space channel that collects data on the following:
* Active users (/5min)
* Number of messages (/5min)
* Total users
 
This bot runs on [[Babbage]] and has an HTTP interface that outputs: '''<tt>london-hack-spaceMessages:5 london-hack-spaceActiveUsers:2 london-hack-spaceTotalUsers:102</tt>'''
  http://localhost:42002/
 
====Mailing list activity====
 
'''COMPLETE'''


* My thanks to JamesG for his assistance and '78.86.160.161' for the original idea. We poll and scrape the groups page for members and and message count.
* My thanks to JamesG for his assistance and '78.86.160.161' for the original idea. We poll and scrape the groups page for members and and message count.
Line 119: Line 62:
We have a script that outputs: '''<tt>members:693 messages:3123</tt>'''
We have a script that outputs: '''<tt>members:693 messages:3123</tt>'''


'''Code:''' https://github.com/londonhackspace/monitoring
''Code:'' https://github.com/londonhackspace/monitoring
 
===Space occupancy===
''See project: [[Project:Spacensus|spacensus]]''
 
[[Category:Projects]]
[[Category:Infrastructure]]
[[Category:Space_Infrastructure_Projects]]

Latest revision as of 11:52, 5 January 2016

LHS Graphs and Visualizations


Members Elliot
QR code

Overview

I have supplemented the Cacti graphs that we have for LHS bandwidth and power with metrics that provide insight to the growth of our community and organisation over time.

To chart the metrics various bits of data are exposed in a Cacti friendly way.

Metrics

Number of members

We may have to wait 12 months before it becomes interesting.

This data is stored in an Sqlite database on Turing. See the Schema. It can be queried like so: 

 SELECT COUNT(id)
 FROM users
 WHERE subscribed = true;

Cacti runs on chomsky but the members database is on Turing. There is a PHP script on Turing to expose the member numbers and then a script on chomsky to pull this in with a HTTP request.

Code: https://github.com/londonhackspace/monitoring

URL: http://london.hackspace.org.uk/member_stats.php

IRC statistics

See project: ircensus

Wiki statistics

  • We get this using the MediaWiki API:
 http://wiki.hackspace.org.uk/w/api.php?action=query&meta=siteinfo&siprop=statistics&format=xml

It returns: 

 <?xml version="1.0"?>
 <api>
   <query>
     <statistics
       pages="759"
       articles="215"
       views="229656"
       edits="7368"
       images="186"
       users="166"
       activeusers="22"
       admins="61"
       jobs="13"
     />
   </query>
 </api>


A Perl script generates the following output for cacti: pages:759 articles:215 views:229656 edits:7368 images:186 users:166 activeusers:22 admins:61 jobs:13

Code: https://github.com/londonhackspace/monitoring

Mailing list activity

  • My thanks to JamesG for his assistance and '78.86.160.161' for the original idea. We poll and scrape the groups page for members and and message count.
 http://groups.google.com/group/london-hack-space

We have a script that outputs: members:693 messages:3123

Code: https://github.com/londonhackspace/monitoring

Space occupancy

See project: spacensus

Retrieved from ‘https://wiki.london.hackspace.org.uk/w/index.php?title=Project:LHS_Graphs_and_Visualizations&oldid=48830’