User Tools

Site Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
lab:pigi:software [2014/05/24 09:03] – [License] chronolab:pigi:software [2017/03/25 13:08] (current) – [Convert CPM to uSv/h] chrono
Line 1: Line 1:
 ====== Software ====== ====== Software ======
 +
 +Check it out on github: https://github.com/apollo-ng/PiGI
  
 ===== Overview ===== ===== Overview =====
Line 5: Line 7:
 ==== pyGI Server ==== ==== pyGI Server ====
  
-The pyGi server component is implemented in python and uses the RPi.GPIO python library to take care of the interrupt handling generated by the impulses coming from the PiGI. A LevelDB instance stores the collected data and distributes live and historical data to connected websocket clients (webGI). It also provides a http module to deliver the actual webGI client, so that any device/system can use the geiger counter without having to install native software first.+The pyGi server component is implemented in python and uses the RPi.GPIO python library to take care of  handling the interrupts, generated by the impulses coming from the PiGI.  
 + 
 +A LevelDB instance stores the collected data and websockets are used for the distribution of live and historical data to connected clients (webGI).  
 + 
 +Naturally, it also provides an HTTP module to deliver the actual webGI client, so that any user can access the geiger counter without having to install native software first.
  
 ==== webGI Client ==== ==== webGI Client ====
Line 16: Line 22:
 [{{:lab:webgi-historypanel.jpg?183|History View}}] [{{:lab:webgi-historypanel.jpg?183|History View}}]
 [{{:lab:webgi-tracevisualizer.jpg?185|Ion Trace Visualizer}}] [{{:lab:webgi-tracevisualizer.jpg?185|Ion Trace Visualizer}}]
 +
 +~~CL~~
 +
 In the future, with more time and the help of other enthusiastic developers, there will also be a ready-to-download image, with kernel, OS and counting, logging & data sharing infrastructure, which just needs to be copied to the SD card so that it works out-of-the-box. In the future, with more time and the help of other enthusiastic developers, there will also be a ready-to-download image, with kernel, OS and counting, logging & data sharing infrastructure, which just needs to be copied to the SD card so that it works out-of-the-box.
  
Line 103: Line 112:
  
 ===== Notes ===== ===== Notes =====
 +
 +==== GeigerJSON Template ====
 +
 +<sxh javascript; toolbar:false>
 +{
 +    "type" : "geigerjson",
 +    "timestamp": 1393878981,
 +    "geostamp": {
 +        "lat": 48
 +        "lon": 11,
 +        "alt": 560
 +    }
 +    "node_uuid":"9b70c59c-a313-11e3-a61f-001f161087c0",
 +    "parameters": {
 +        "tube_id" : "LND712",
 +        "dead_time" : 0.000190,
 +        "tube_factor" : 0.00233,
 +        "opmode" : "[stationary|mobile]"
 +        "window": "[abc|bc|c]"
 +    },
 +    "data" : {
 +        "source": "[sim|test|env]",
 +        "cps" : 10,
 +        "cps_dtc" : 11,
 +        "cpm" : 600,
 +        "cpm_dtc" : 610,
 +        "totalcount" : 12345,
 +        "totalcount_dtc" : 12456,
 +        "edr" : 0.89,
 +        "edr_avg_15m" : 0.90
 +    },
 +    "annotation" : "my radioactive moment"
 +}
 +</sxh>
  
 ==== INES Scale for reference ==== ==== INES Scale for reference ====
Line 116: Line 159:
 <x>D = R * conversion factor</x> <x>D = R * conversion factor</x>
  
-So to get from cps to µSv/h (only units here, not really a correct equation):+So to get from cpm to µSv/h (only units here, not really a correct equation):
  
-<x>µSv/h = cps * tube and energy specific conversion factor</x>+<x>µSv/h = cpm * tube and energy specific conversion factor</x>
  
  
Trace:

Page Tools