Someone should: log laser access


Here’s a project idea that comes up occasionally and would be useful. I don’t have time to do it, but would help and support someone who wants to take it on!


Existing Laser Telemetry

We have a laser telemetry sensor box that’s been running for about a year. It can track laser power and usage, as well as chiller temperature and filter pressure differential. It stores this in where it can be graphed and stuff. This is how @JDMc makes those data-sciency graphs in the Laser Cutter Committee Reports

Laser access / lockout

There is a raspberry pi beside the laser cutter. Users have to log in with their account and then flip a switch to turn on the laser. Everybody who has done laser training knows what I’m talking about. The Pi runs this nodejs application which has not been touched in 4 years (but works perfectly).

The idea

The laser access software knows which member turns on the laser, and it should be possible to write that to the same InfluxDB as the other laser telemetry. Perhaps for privacy reasons, it makes sense to write a pseudonymous identifier instead.

Then it would be possible to make a report to show this distribution of laser users and how much they each use it. To generate insights like:

  • Last month XX different members used the laser
  • Last month, the top 5 laser users accounted for XX% of its overall usage


If this is an interesting project to you, I’d be happy to help get you going. If you get comfortable with the laser access software, you could also clone/extend it to support other tools at VHS.

Previous “someone should” posts:


Well, actually…

  • The code got touched last just over a year ago.
  • There’s already a ./ in the home dir of the pi user on the laser-pi.
  • Currently that information is logged both on the Pi and Nomos logs it in its access logs.

AFAIK, LCC has access to the laser-pi, so, it might be fairly easy to take the output and correlate that to actual use.

That said, if anyone wants to contribute code to the ATOMS project for possible user-usage telemetry, the help is more than welcome. ATOMS is meant to replace the current laser-access tool and provide infrastructure for all tool-lock systems at VHS.

@LCC: if anyone of you doesn’t have access to the laser-pi or if the password has collectively been lost, let me know, or else if anyone on the LCC wants output of the, I’ll be happy to provide this.


Who do I provide the data to? @JDMc? @lukecyca?


Thanks for the responses Ty! We already have access to the raw data, or at least the log files on the pi. I didn’t know about (I normally just tail the log file) but that sounds like it could be useful. It makes sense that Nomos knows when the auth happens, but I assume it doesn’t know when the user logs out of the laser pi. So the laser Pi’s data is probably more useful here.

If you’re offering to turn that data into insights like the ones in the OP, then that would be awesome! Ideally it should be done in a way that can be run monthly, and I think writing the data to Influx (in addition to the log file) might make that easier, but even a one-time analysis is better than nothing.

But also are you sure you want to take this on? You already do so much IT work around VHS! I was kind of fishing for a newish member to step up and use this as a tidy little project to start getting involved. That’s the ulterior motive of a “someone should” post. :wink: