Please note that n=2, but both myself and a friend of met have met people working in life science labs that were assigning research assistants to manually count cells in images, and manually sweeping through images to find stills that were in focus.
Please note that n=2, but both myself and a friend of met have met people working in life science labs that were assigning research assistants to manually count cells in images, and manually sweeping through images to find stills that were in focus.
I enjoyed my time there a lot, I was building tools to help very smart and motivated people solve cool science problems. My users sat across the lab bench from me (the original open office plan?) and iteration/feedback cycles were super fast. People were appreciative and I could see how much time I was saving them. It was very motivating. Some of the more useful stuff I built got picked up by other labs in the group.
Maybe I'll do that kind of thing again someday, if I decide I've had my fill of megacorp programming.
e.g., a month ago I made a small machine for a dental research lab that basically added a feature to a piece of test equipment. The feature was so basic and obvious, I have no idea why the equipment didn't already have it. But it was an opportunity for me to step in and make a small piece of hardware to do what they need at little cost.
A few months before that I made a GUI for a customized bit of veterinary equipment, and so on... These jobs are out there. They're quick and easy for an experienced engineer but the problem is finding them consistently. My main focus these days is trying to do just that.
The image processing was pretty simple. Object identification and cell counting, mostly. There are already good open-source tools to do this kind of thing, so my contribution was mostly integrating those tools into the lab's workflows to make people more efficient.
I wrote some simple embedded code and MATLAB programs to create a better user interface for one of our custom-built microscopes. The users could specify the types of scans they wanted at a higher level and the system would automatically gather the data, then present the results and let the user re-run with adjusted parameters.
The bioinformatics thing was the coolest and most ambitious project, although we only partially realized our goal in the time I was there. It helps automate some of the more tedious and easy-to-screw-up bits of planning cloning/transgenic experiments.
They develop open-source platforms that are inspired by and seek to solve problems lived firsthand by collaborators (such as myself) and the greater scientific community.
The Broad has created an environment and provided resources to enable engineers to do great work. The DSP feels like a blend between tech company and academic research institution. The people I've interacted with are technically superb (and also nice).
If you are interested in contributing to the intersection of life science and compute, would strongly recommend you check them out.
This may be off topic if you consider above to not be sufficiently "blue collar", but biomedicine in general (from the entire spectrum of basic science all the way to care delivery) is in dire need of smart computational folks.
Really? That seems a few decades behind the times.
More specifically, software is usually not a direct expense so it needs to be paid from the grant overhead, but the university frequently wants to build new buildings or something else instead. It's the same for private government contractors.
The LIF is a binary blob wrapped in an XML structure. There has been some good work done by the people Open Microscopy Environment building some Java libraries for parsing these files, but to be quite frank I'm a bit rough around the edges when it comes to working with Java and all the computer vision stuff I know is in Python and C++.
If you're serious about this offer, then I can look into getting you some samples (if you can't easily find them yourself). But full disclosure, I don't think any PI or lab that I know of would be able to afford GPU compute hours, but most of them have access to a cluster, so if you can deliver a JAR (or a Docker container) I could demonstrate how they could quickly deploy that themselves on their own hardware.
I can take a Stab, but the file format and Java stuff could be a problem. Let's see