2018/February

overarching goal

data streams

data streams:

• sensor data from a physical sensor (raspberry pi, gpio, radio, sdr)
• wiki data - historical evolution, graph analysis
• rojo/jupiter/maya/cronus hardware status - collectd, netdata
• rojo/jupiter log data
• network log info from bro
• twitter/news scraping

dashboards

monitoring with dashboards:

• various data sources mentioned above
• building visualizations and graph dashboards with Grafana
• building and designing monitoring systems for understanding complex, live, evolving systems
• minimizing time to setup, add metrics, gain insight, visualize, repeat

dashbaord software:

• Grafana
• Graphite

networking

monitoring hardware

• network tap/switch
• wired router

new router:

• website with database of embedded dev boards: board-db.org
• Banana Pi R2 is designed with built-in switch hardware, so it's intended to be used as a Raspberry Pi for home routers, of sorts. Long term, this would be a good hardware platform.
• Banana Pi R2 Link: [1]

rollover

blog posts

• Project Euler 172
• Bots
• bootstrap table presenting results of Rubik's Cube investigation - Rubiks Cube/Bootstrap

bots

charlesreid1 bot:

• build spreadsheet, parse to build awesome list and bot

Bots/Charlesreid1

bot instrumentation:

• dashboard, monitoring, statistics, status
• bot dashboard with grafana

apollo bots:

• 14/15/16/17
• incorporate lunar surface dialogue
• link to apollo 11 audio: https://www.nasa.gov/mission_pages/apollo/40th/a11_audio_db.html
• Spacelog (mercury, gemini, pre-11 apollo missions): http://spacelog.org/

genealogy

Genealogy photos:

• Photos cropped/organized by family
  • 2011
  • 2017
  • Rename scheme
  • Notes - A2k11
  • Notes - R2k11
  • Notes - A2k17
  • Notes - K2k17
  • Notes - R2k17
• Send email to fam with link on Dropbox

Writing:

• Pauline and Bruce chapters
• Historical research planning

complete

data store (db)

the database is the central thread for everything.

get a database solution up and running over the management lan.

minimize friction and time to bring up/explore/check new collection.

Note: minimizing friction mainly just comes down to (a) getting it running, thank you very much docker, and (b) familiarity with syntax. everything else is pretty seamless.