LEaRN The Lafayette Engagement and Research Network

2017-08-07 LEaRN Status Meeting (CGI)

Original CGI Document
SubjectStatus Meeting (CGI)
Project NameLEaRN
Meeting DateAugust 7, 2017
Dial-in Info

Host key: 199735

Join WebEx meeting<https://cgifederal.webex.com/cgifederal/j.php?MTID=m4a162804d9845bdfd1947806438d109a>
Meeting number: 747 675 789
Meeting password: g26tiUHP

Join by phone
Call-in toll-free number: 1-866-5573330 (US)
Call-in number: 1-443-8637759 (US)
Show global numbers<https://www.tcconline.com/offSite/OffSiteController.jpf?cc=6573812350>
Leader PIN: 1146
Conference Code: 657 381 2350

Can't join the meeting? Contact support.<https://cgifederal.webex.com/cgifederal/mc>

IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. You should inform all meeting attendees prior to recording if you intend to record the meeting.

Time / Location2017-08-07 2:00 PM CST



Discussion Items

5minReview Deadlines 
  • Upcoming Deadlines

    • Sprint completion 8/16/2017
    • August 16th finish prototypes and final design
    • July-Early August, purchasing for devices
    • Early September begin build process of devices with ULL/David Thibodaux students

Status update:

  • We need to start thinking when and where we would deploy our next sensor prototypes, and what sensors those prototypes will include.
  • Comeaux, Justin M (CGI Federal) did not get test out current and new algorithms for the O3 sensors due to higher priorities last week.
    • Testing the hardware with all the sensors connected to a Raspberry Pi was the priority.
    • Will do this after the current sprint

Status update:

  • Hardware status:
    • Alphasense higher quality PM sensors, 5 ordered
      • Communicating, but not sure if correctly
      • Still working on this
    • Power regulator works
      • ran all weekend - still cool
      • says it's undervoltaged but it bounces between 4.99V and 5.00V
        • need to monitor and check it under load
    • Custom PCB
 Firmware and device management

Status update:

  • Added new datastreams to account for new sensors manually. (Possibly make new sample.py type of files for specific sensor boxes)
    • Did not get to QA Chepudira, Karthik (CGI Federal) code below. Will get to it this week.
      • Will test out the automatic way of populating new datastreams through python provided by Chepudira, Karthik (CGI Federal).
      • Will also need a more robust way to configure firmware (yaml, etc.) as environment variables will be too limiting in some cases.

Status update:

  • LEARN-148: Clean up code for OSS release
    • Waiting for code review
  • LEARN-187: Clean up code for OSS release, pt. 2
    • In progress
 Visualization and Use Cases

Status update:

  Architecture & AnalyticsChepudira, Karthik (CGI Federal) 


  • Worked on connectivity between sensors and azure IOT directly via MQTT - Done
  • Setting up MQTT bridge with X.509 certificates - Done
  • Validate mapping for Azure Iot Hub device endpoint and thingid (deviceid) in azure function -Done
  • Plan to setup MQTT broker to map STA topics to Azure IoT topics - Done
  • Automation of device authentication for Azure IoT Hub device - Done
  • Create sensor deployment location plan and provide suggestions
    see 'SensorDeploymentConfiguration.xlsx' file here Sensor locations
  • Creating API things, data streams etc from the device manifest.
  • Make Updates to sensor code (transmit.py) to allow communication directly to azure IoT hub.
  • GitHub integration with Confluence
    • Flat HTML page output finished
      • Content links need to be filtered/removed/rewritten
        • Working on downloading assets (limited) to the be accessible from GitHub Pages
        • Will contact Steve Kirsch for working with larger assets
      • Dynamic menus filtering for GitHub Pages is finished
    • Then will automate using a cron job running on a VM hosting a Drupal instance
      • This Drupal instance may be running as part of AgileIQ infrastructure
    • Molinski, Samuel J (CGI Federal) has a prototype of JIRA integration.
      • HERE: https://github.com/LafayetteEngagementAndResearchNetwork/AirChallenge/issues
      • The team needs to review and mark any tickets that should not be migrated. To do so, label as follows:
        • 'Project Risk', 'Project Action Item', 'Project Issue', 'Non Public', 'nonPublic', 'github-ignore'.  If there is any sensitive issues I would recommend added on of them.  Also if there is any other labels I should add to the black list, I can add that if needed.
  • GitHub integration with source code
    • Code will be pushed from Bitbucket to GitHub manually for releases as appropriate
 Review Scrum Board 





Action items

Date Assigned 


Due Date

Completion Date Notes 

Risks and Issues

Risk or Issue

Date Identified 


DescriptionOwner(s)Follow-up DateNotes 
  •  Notes for this item