stories from the Public Lab community
The Public Lab Kits Initiative uses Raspberry Pi cameras more and more, and was in need of a workflow to generate customized operating system images for specific needs such as the Microscope and Lego Spectrometer Kits.
In general, while Raspberry Pi mini-computer boards are amazing, there's a significant barrier for many people to use them, which is the installation and configuration of the memory card with useful software -- like camera software, for example!
We wanted to have a way to generate different pre-loaded SD cards, repeatably and reliably, for different uses. And we wanted people to be able to simply insert an SD card, plug in the camera and power, and start using the Raspberry Pi as a camera as quickly as possible.
We also had a desire to build a process whereby the community could participate in the construction of the operating system that we distribute with our kits and also to share recipes and ready-made images for usage in specific scenarios.
The default operating system image is meant to simplify the workflow for kit users, so these well-defined features needed to be set up:
I was contracted for this and so I had to come up with great shoulders to stand on in order to deliver all features! Disclosure: I am also Public Lab's part time Systems Administrator.
Fortunately thanks to the great work of the Hypriot Project, and the Gitlab CI service, we are able to iterate quickly and collaboratively, from an orderly and flexible base.
Please consider this release a Beta to try out
The documentation is included with the combined image. You may also read it online.
We also have a page for Q&A, troubleshooting, and activity guides here.
Adding a new "recipe" is quite easy -- it is possible to fork our repository, make your modifications and open a pull request, which our system will use to generate a new custom image. You can then download a fully built customized image ready to be burnt into your Pi¹.
¹: Tested on Pi Zero W only.
We'll be thrilled to see this repository evolve in alignment with the communities's needs.
Follow related tags:
raspberry-pi blog raspbian with:warren
Today we're announcing a new feature you may have noticed over the past few weeks! For a long time, emails about new posts or comments on PublicLab.org have been from an address called firstname.lastname@example.org -- how unfriendly! But it's because, unlike a mailing list, you couldn't just write a reply email. Remember this?
Thanks to amazing work by a number of Google Summer of Code fellows (#soc), but primarily by Naman Gupta, you can now just write back a reply email, as long as you're sending from the same email you're signed up with. (log in and check this here)
(This will work for any email you get from email@example.com that has a post id in the subject line, like this:
Title of the email (#1234) -- that's most of them!)
It's a new feature, so give it a try, and report back if you have any trouble!
This means that, soon enough, we will be relying more on the PublicLab.org website as a forum, rather than on our old Google Groups. To stay in touch with others working on topics you care about, be sure to SUBSCRIBE using the many prompts on the site, for example at the top of any topic page (linked to from your dashboard, or the front of PublicLab.org!):
You may have noticed a lot of changes on PublicLab.org recently -- this has been made possible by a dramatically growing community of software contributors, joining us through our new coding Welcome Page at code.publiclab.org, as well as through programs like Rails Girls, Outreachy, Google Summer of Code and Google Code-In -- and with support from the DIAL Open Source Center and the Schmidt Foundation's 11th Hour Project.
Hundreds of new people (see the bottom of code.publiclab.org) have started showing up to help fix bugs, implement new features, and help others in turn join in our efforts -- a very Public Lab spirit! And we've made serious efforts to reach out to and welcome members of groups that are under-represented in open source. You can read about our outreach work here. The result is that the collaboration systems we use across this community are getting refined and improved faster than ever!
Our code contributor community is built on a commitment to mutual benefit -- we can't create good software without welcoming in newcomers, and we are deeply invested in supporting contributors to learn new skills and grow as coders, designers, project leaders, and "cooperators". Unlike many open source communities, much of our capacity is aimed at helping people become proficient coders, and to learn and apply new skills.
But we also seek to change coding culture by recognizing how important communication, mutual support, and affirmative and welcoming tone are. As part of this, we seek to improve ourselves and help contributors learn how to support one another, welcome in a diverse and inclusive community, and build a more positive and equitable society by doing things a little differently.
Follow related tags:
community gsoc blog code
At the Public Lab non-profit, we are committed to the ethical and respectful use of personal information. In our work, and to serve our community and those we work with, we need to make use of personal information in a number of ways. We always seek to protect individual privacy while we fulfill our responsibilities and mission, and when these must be balanced, we seek to do so transparently and in good faith.
We've done our best to explain things in plain language, and as thoroughly as possible, even providing new information on IP-address anonymization at a supporting page here: https://publiclab.org/wiki/location-privacy#Privacy+Policy+Location
Most of it affects only those people who sign up and create an account on PublicLab.org, attend an event, or otherwise interact actively with Public Lab websites and systems.
Finally, it's been our intent in this document to explain why we handle different kinds of data in order to fulfill our role hosting these spaces and fulfilling the Public Lab mission.
Please give it a look -- thank you!
Follow related tags:
blog privacy privacy-policy gdpr
This Northeast regional Barnraising was like no other because it started with people exchanging stories of disaster. It was an appropriate ice breaker since the first day was dedicated to crisis convening. I shared my experience of an earthquake that hit while I was at a café in Philadelphia. I remember my inner dialogue went from "possible subway work" to "nearby construction" to the gut instinct that this was an earth shaking event. How much time did I lose arguing with myself? What would I do differently next time? As others shared their encounters questions arose: How many people have experienced natural disasters? What does emergency relief look like? What should it look like?
It's hard to compare a small earthquake that merely puts people on edge, to a hurricane with flooding that causes loss of homes, jobs, food and electricity. Testimonies from flood survivors, (who I'm now renaming flood wranglers) provided details of rising waters and destruction in so many communities---New Jersey, Texas, Florida, El Salvador and Puerto Rico. I know I was swept by the emotions of sadness, fear and anger hearing about their situations. Yet there were also stories of community leaders, bartering and rebuilding that brought hope. After another day of Barnraising, the stories started to sound similar. In fact, you could have exchanged locations and faces, but the same problems were surfacing.
The greatest thing about a Barnraising is that it not only provides a safe place to discuss problems, but it also encourages sharing current solutions while working on new ones. One of the best tools I heard presented was the common bicycle. They can be used for transporting supplies and medical aids, as they are nimble when most roads are jammed or impassible. Bikes are also able to be hacked to become generators to recharge phones--that's something everyone should have in place!
One of the sessions that got me most excited was creating a "Communication Checklist". Solid ideas were put on paper about the best ways to communicate during a disaster when electricity fails. Details include using flyers with bold/cultural images to communicate meeting places and times, connecting with community leaders, using libraries as hubs, encouraging face-to-face communication and supplying printouts of resources.
Choices of resources are often not controlled by communities, and one session addressed that problem by creating a blueprint for a Rapid RFP (Request for Proposal). It includes a transition/handoff plan, deliverables, timeline and transparent budget. This entire process would help to ensure that a community receives the right help it needs and would also put into place a checks and balances for how the process is working out.
Checks and balances is probably just the shadow of what I encountered on this Barnraising. The most memorable part was hearing quavering voices as truths were shared across all disasters including government mistrust, racism, receiving inappropriate supplies, neglect, hunger, sickness and homelessness. Still these discussions are so fresh in my mind and I'm so thankful for those that were able to stand up in front of the group and be so honest. We need to hear this---the world needs to hear this. So, what can we do to make disasters less disastrous? Here's what I learned so far:
We cannot escape that all things are interconnected and I know that I'm still learning how to ask for and accept help. For those that attended the Barnraising, please do add in your thoughts on what you learned or what could be helpful in a disaster. I remain in awe of flood wranglers and those serving in disasters.
Follow related tags:
barnraising newark blog northeast
Pascagoula, Mississippi hosts 12 facilities that report to the federal Toxics Release Inventory, six of which are within a mile-and-a-half radius of the Cherokee Forest Community (2016 Reported toxic release data here). Below is the story of Barbara Weckesser, and her struggle to get out.
“Today, I couldn't sit outside for all the noise. We itch all the time. My eyes burn all the time. People who move here get sick. The children who were unhealthy here move away and seem to get better. My husband’s health conditions have gotten worse here. It has been a nightmare. I’m wondering how quick can I get bought out, and get out of here?”
Over the past couple of years we’ve done all we can think of to document our concerns and share them with the “right people.” We got the Mississippi Department of Environmental Quality (MDEQ) to come in and do some testing. They came out three or four times, and each test shows something in those air canisters, even though none of the tests they did were done the way they were supposed to; they didn’t leave them out for the required 24 hours, and they all came back with stuff in them.
A while ago, Mississippi Phosphates agreed to put in a monitor and within three days it showed that there was sulfuric acid in the air, and two or three days after that, again. Then, for 28 days that the monitor read “over.” MDEQ’s response to me was “Oh, it was turned off. That’s why it read over.” It wasn’t off; the monitor was reporting sulfuric acid. We have all that data. But when MS Phosphates went belly up, that monitor went belly up too. (Mississippi Phosphates closed and their former site is now listed on the Federal Priority List as a Superfund site.)
We keep odor logs. I’ve got a book, it’s about 13 or 14 inches thick, and it’s by the date for when we’ve written odor reports. I’ve also paid for tests myself. We’ve done particulate matter monitoring and have gotten elevated levels, and we’ve paid for bucket air sampling as well. Each time it shows something in it, but each time they say it’s not something that’s going to hurt you. But when you look at the cancer rates around here, and the number of people who have passed away from cancer just in the past year and a half, something is causing it.
Most of the tests we’ve done have been for particulate matter because that was the cheaper test to do, but that doesn’t capture the chemicals. We want to target the pollutants coming from Chevron, and the bucket sampling can do that, but it requires that you take the samples and get them in the mail right away. It’s not easy to do. It’s too time- and energy-intensive, and too expensive.
We’ve gotten our test results in a public meeting on record. I wanted to use it as a way to put pressure on the new mayor. He promised he would get us out of this situation. Let’s see if he holds it up.
MDEQ said “hit them on their permits” and made us all go to permit training. I said sure, I’d love to hit them on their permits, but we can’t take them on on account of their permits because MDEQ hasn’t made them follow through to renew them. Why is our government letting these companies operate without permits, without them being renewed? They’re not bringing these renewals up for public comment, and even when they do, we comment and nothing changes.
Here we sit, our hands are tied, and they can pretty much do what they want to unless we can find something that we can bring them all in on. And the one thing we can bring them all in on is health. Right now, we’re working on starting up a health survey with Dr. Wilma Subra. We’re also working with an attorney, but the work he would need to do is really expensive. It would be great to have an inexpensive and easy way to prove these chemicals are in the air here. I would also love to have some legal environmental health advice for what else we can do to bring these companies to the table to say, “Yes, we did that. Yes, we will work with this subdivision to get them out.”
Follow related tags:
gulf-coast mississippi blog pollution
Since 2011, Public Lab community members around the world have been building and using modified consumer cameras to take multispectral photographs, enabling thousands of people around the world to explore the world around them using vegetation analysis tools such as #NDVI. As illustrated above, comparing infrared and visible light can offer clues to plant health, and DIY cameras like Public Lab's can make this kind of analysis possible on a very small budget.
(this post was cross-posted on the Globe.gov blog)
You can see just a few of these on Infragram.org, and in the new (beta) NDVI tool in MapKnitter.org. Here, DIY aerial infrared photos of a farm in Canada can help reveal healthier and less healthy areas of crops:
Building on an initial low-cost technique for modifying consumer cameras to take multispectral photographs (by switching a filter behind the lens), Public Lab community contributors have developed a suite of web-based multispectral analysis tools to lower barriers and engage members of the public in using these techniques for the analysis of agriculture, land use, runoff and water quality, wetlands restoration, urban planning, hydroponics, and many other applications.
Now, in partnership with the AREN project at NASA and in collaboration with the GLOBE program (and with support from Google Summer of Code), Public Lab is now developing a set of in-classroom materials and resources for students to learn about earth observation and image analysis in an experiential way, from constructing their own multispectral cameras to using the free and open source spectral analysis tools provided by Public Lab. These images show the two types of single-camera modifications - one resulting in a blue-toned image, and one in a red-toned one. It's also possible to do this with two cameras.
If you teach in or out of a classroom and are interested in how remote sensing, satellite imaging, or vegetation analysis could be part of your education work, we're eager to work with you!
Learn more at PublicLab.org/infragram and check out our starter kits for modifying cameras at https://store.publiclab.org/collections/diy-infrared-photography
Follow related tags:
balloon-mapping near-infrared-camera ndvi education