Skip navigation
All Places > PI Developers Club > Hackathons > Blog > 2017 > March
2017

First of all, I would like to thank all of you that participated. This was OSIsoft's first ever attempt at a virtual hackathon and it went way better than expected and that was because of you, the participants. You did not make the judges lives easy with the quality of your submissions. In fact the judging was so difficult the judges felt the need to break the mold of the traditional first, second and third prize and give awards based on categories instead, calling them 2 second and 2 first place winners. So without further adieu ...

 

Most Creative Use of External Data

Servelec Controls Team 1 and their PI in The Sky, Hackathon Entry - Servelec Group - Team 1 . The team was made up of GBADI0, Gregor Emslie, Michael Nelson, and James Todd. For their award, each member will receive a 100% discount to PI Developers Club for 1 year.

 

Biggest Potential Business Impact

Servelec Controls Team 2 and their C.H.A.P.S. and L.A.D.Y. entry, Hackathon - Servelec Group - Team 2. The team was made up of Timothy MacLaren, Sarah Wallace, Marija Markovic, and Leslie Shields. For their award, each member will receive a 100% discount to PI Developers Club for 1 year.

 

Best in Show

Magion with the ScatterPlot Matrix, PI Visualization Hackathon - Magion Scatterplot Matrix. The team was made up of only one member, David Golverdingen. For his award, David will receive an Oculus Rift VR headset and a 100% discount to PI Developers Club for 1 year.

 

Best in Show

Exele with their Event Map, Exele Event Map - OSIsoft Visualization Virtual Hackathon 2017 Entry. The team was made up of Dan Fishman, James Sconfitto, and Michael Kiefer. For their award, they will each receive an Oculus Rift VR headset and each member will receive a 100% discount to PI Developers Club for 1 year.

 

Best OSIsoft Submission

Team Doomguy and their augmented reality PI view, PROJECT-OPERATION-PI-TANGO-DOOM-3D. The team was made up Johnathan Burns, Simon Boka, Phillip Little, and Andrew Bathon.

 

 

I would like to thank all of those who helped organize the hackathon and have it run smoothly:

 

And our judges:

 

I will be contacting all of the winners shortly to arrange prizes!

Team - "A Little Outgunned"

Our team name was chosen because we're not developers, but still wanted to work out how to make visualization symbols - and had lots of fun doing it. Here's what we came up with:

 

2017-03-13 14_39_08.png

 

Pretty simply, if you drag out an attribute to form this symbol, it finds all associated event frames with the element owning that attribute and lists them out by their template name, showing when each event started. We chose this symbol because we wanted a simple and effective way to quickly include events into a dashboard. Industry applications are broad, from viewing times of ore deliveries (as in the below video), downtimes of assets, trips, anything that occurs that you want to see in an asset overview display. If these are set up as event frames, dragging out this symbol into a display instantaneously lets you view when these events occurred.

 


 

Disclaimer: The symbol isn't ready for prime time, and is very unfinished. It would take a fair bit of work before putting into production, but someone a little less outgunned than us could probably do this fairly quickly.

 

GitHub Repo for this project can be found here.

 

Using libraries:

Event Drops

d3

Hello Visualization Virtual Hackathon participants!

 

The time has come to allow submissions. To submit your entry, create a personal blog post and add a link to it as a comment to this post. As submissions are made, I will update this post with links to all of them.

 

To create your personal blog post, click the pencil in the upper right hand corner and select Blog Post .

 

The hackathon end March 13th, 12:00 AM EDT (GMT - 4), and please remember each blog post submission should have the following:

  • A description of the general purpose of your project, including who and why someone would use it
  • A picture of your project in use
  • A video that demonstrates your project, http://camstudio.org/ is a nice screen capturing tool
  • A link to your GitHub repository where your source code is located. Please note that all source code must be published under the Apache 2.0 license.

 

Good luck!

 

Current Submissions