• Capital Expenditures
  • About
  • Contact
  • Capital Expenditures
  • About
  • Contact
CAPITAL EXPENDITURES

a learning investment in DAta Science, entrepreneurship, and Biotech

by
​ ​Vanessa Mahoney

SAMPLING A POPULATION

10/7/2021

0 Comments

 
Howdy! Long time no talk! Haven't written a post in awhile! I'm glad I purchased the annual review of my domain name and it hasn't been sold to some neon ad infested site selling rectal cream for cats. Or something like that. :)

I'm now living in an awesome condo with an amazing view of Austin. I sit on my balcony all the time. I laid down that fake grass turf and cute little hippie decor and strung it with solar lights. It's my favorite place in my apartment and a no work zone -laptop not allowed. 

Last night when I was out there watching the sunset flight of the bats over the Congress Ave bridge, I thought about how few times I see other people outside on their balconies. Sad! But then I don't sit out there all day, so maybe they just don't come out at the same times I'm out there. 

I started thinking about how balcony furniture could be an indication of people who use their balconies (let's ignore how often). So here's the data science problem: what % of people use their balconies? There are 430 condos in my building. So, if we could count the number of balconies with furniture, we could find out what % of people use their balconies. Here's where sampling a population comes in: do we need to count EVERY apartment to get an accurate measure of balcony-goers? I can only see some balconies from my place, and I am not gonna go walk around with binoculars counting each apartment, not looking to be labeled creepy. ;) But luckily, we CAN get an accurate % by just observing enough of the balconies.  This is the Central Theorem, an intuitive theorem that says if we sample enough balconies, we can still get an accurate answer to the % of the whole building. 

Alright, so how we do this? How many do we need to sample? Generally 10% is sufficient. Accuracy will go up with more samples, but it can be extra work with diminishing gain.  So we are gonna sample 10% of the condos (43), but we have to make sure we RANDOMLY take these samples. Even if I could see 43 apartments from mine, that wouldn't be accurate, because it isn't random. I can't see lower apartments, and this building has east and west facing units. Why is that important? Well, it's possible there are different % percentages for lower units; maybe they don't have a great view. Maybe the %s are different for east and west. That's ok. We just want an overall figure. Our 43 samples must be randomly selected from the entire building. 


Alright, so let's say I was able to casually and not creepily get 43 samples selected from the 1st to the 44th floor. Hypothetically, let's say I found 27 with furniture, 16 without. Great, 62% of people go outside (27/43). 

But should we stop there? Do you see any problems we might have with this figure? We listed in our assumptions that furniture indicates those people go outside, but what if a portion of those without furniture go outside? Maybe they throw out a towel to tan or go out there to smoke. Our calculation also assumed that every unit was occupied. Ok, so let's say I go ask the building manager how many apartments are occupied. Let's pretend she tells me 380 of them are occupied. Now we can adjust our calculation. 
380/430 = 88.3% occupation rate. We know the 27 balconies with furniture are occupied because they must remove their stuff on vacating, so we have to adjust our non-balcony figure. We saw 16 condos without furniture, but these are the ones that might not be occupied. So, we take our 16 condos by keeping 88.3% of them. Let's do it: 16 condos x 88.3 = 14.14, so we're gonna call it 14. That means from our 43 sample size: 27 with furniture, 14 without, and 2 unoccupied units. Since we only observed 41 occupied apartments, our new calculation is 27/41 = 65.8%, up from our previous calculation of 62%.

This is a simple example of sampling, but it comes up ALL the time. The Census takes a count from people every 10 years, but in the years between they still wanna know what's going on, so they are sampling a population. Nielsen uses a sample audience to get tv ratings. When they are trying to count fish in a lake, they tag a portion of the fish then later catch a sample of fish and determine how many have tags. If they pulled 10 fish and only 1 had a tag, it tells them the portion they tagged is only about 10% of the total number of fish. Do you know when it looks like a fast moving car's wheels are moving backwards? That's because our eyes aren't sampling fast enough to see what's actually happening, not catching the frames that show us the wheels are obviously moving forward. I had a cool project at McLane that is now in production where sampling accuracy was the central tenant.

Hope you enjoyed learning a little about sampling!  





0 Comments

ARTIFICIAL iNTELLIGENCE: NOT SOMETHING TO FEAR

12/20/2018

0 Comments

 
PictureMy lecture at Mediterranean University on December 19, 2018.
This week, I gave a lecture at Mediterranean University to an awesome class of 3rd year IT students. Before I started, I asked them to share what field of software engineering interested them the most. Most of them responded with front-end, back-end, or full stack software engineering, whereas data science/ artificial intelligence was only mentioned as a casual interest by a few students. I explained that on my team, our work spans back to front end development, but that my domain was primarily data science.  

During my lecture, I told them about some of the data science projects I've done at IBM. Both during and afterwards, their questions indicated that they really understood the fundamentals of data science and also seemed quite interested. Machine learning hasn't really found a place in IT over here, but I think it should! There's a bunch of buzz words in machine learning, but I think some of the terms can be off-putting and have negative connotations, in part due to Hollywood's personification of artificial intelligence as evil.  Indeed, many of the questions from the students were "Is AI going to replace everyone's jobs?", "Why is AI always portrayed as a bad thing in movies?", and "How do you know AI won't acquire the ability to think because I saw something where it solved a problem it was even asked to solve...."? These questions betray a fear of AI, but I postulated that it's just the fear of the unknown! For AI to be useful, it's always going need to humans to tell it what to do; it flourishes with specific, repetitive tasks. Just like production factories have replaced some manual jobs, so will and should AI. But so too it is a technology that will advance our knowledge and productivity. And the creativity, emotion, context that us mortals possess - that is something computers will never be able to bring to life. Instead, AI should be seen as a tool, as something we can use to make our lives better and to enable us to focus on the problems that need our creative problem solving and human touch! 

Here's a great article that also agrees that AI is not taking over the world anytime soon. 

Picture
Dangit, that's why you wear heels instead of sneakers. :P Also, Montenegrins are tall!!!
0 Comments

GIRL POWER!

12/17/2018

1 Comment

 
PictureOur Podgorica Girls Who Code contract!!! #GIRLPOWER

Pictureschoology.com - highly recommended online learning management system!
We launched our first Girls Who Code session last week, and it was so INSPIRING!!! During our meeting we got to know each other, looked at the plan for the GWC year, explored some of the activity sets, highlighted women in tech, and made our own club contract! The girls were so engaged, passionate, and uplifting!!! Many of the girls are a little intimidated and afraid of making mistakes, but they're not letting that hold them back. What I really found amazing was that although the girls are all on different levels - ages coding experience, shyness, English language - we were all together in fostering this sense of community!   Just look at this contract! It's not just about doing things on your own, it's about empowering ourselves as a sisterhood! I left feeling so excited to see what they're going to build. 

I also wanted to point out this really awesome online learning management system, Schoology.com. I don't have access to school or GWC tools, so I created a repository for our club on this website. After creating our class (slides, activities, dates, etc) the girls just needed to enter the access code when they created a schoology profile!  It also has a ton of useful features like attendance, assignments, calendars, discussion groups, gradebook, etc. I had to be certified because I am teaching students younger than 13, but that verification was an easy process, and the service is entirely free. I definitely recommend this platform if you're teaching an online course and want a free, user-friendly platform! 

I'll end this post how we end every Girls Who Code Session: See you next time and don't forget to be awesome!  

1 Comment

American at our Faculty

12/14/2018

1 Comment

 
Picture
About a month ago a film crew came in to my office to interview me, and my host mom just showed me where it ended up! Check it out here!

​The article incorrectly states that I'm a student obtaining my PhD at the university, but who can blame them when I look so darn young. ;) Kidding. But seriously, I think it's lovely that they said "Vanessa listens to her heart". Both literally and metaphorically I do, so I would like you to take that tidbit and do what your heart tells you to do as well, no matter where it takes you! :D


1 Comment

2 MONTHS IN MONTENEGRO!

11/27/2018

2 Comments

 
PictureMe at Cijevna, the "Niagra Falls" of Montenegro, about 20 minutes outside of Podgorica!
Zdravo from Montenegro! I can't believe it, but today marks TWO MONTHS in my new home!!! I cherish every day and am so grateful that a Fulbright fellowship brought me to this beautiful country of mountains and sea, grapes and roses, brandy and roasts,  and above all, amazing colleagues and friends. 

If you follow me on social media, you've seen my constant stream of photos, but today I'd like to take the opportunity to share what I've been working on over here. For those of you who don't know, I've taken a year sabbatical from my position at IBM, and I am working as a researcher and professor at the University of Montenegro - and absolutely loving it! The pace is slower than in NYC or on a client facing project, but I must say I am loving the freedom to explore the topics and initiatives that are important to ME.  Already I've learned SO much and am so inspired by my colleagues and students. Here's a quick look at what I've been up to!

Research & Colleagues 
My office sits in the engineering floor of UCG technical campus. I am researching classification of electrocardiograms (ECG) through deep learning. I am particularly interested in unsupervised learning methods, which means even if we don't have access to an expert electrocardiologist to label the ECG with annotations like "normal beat" or "atrial flutter", this algorithm could learn what atrial flutter looks like all by itself. There are some existent technologies for ECG classification (primarily atrial fibrillation),  but analysis is not done in real time, patients don't appear to be impressed with the results, and there many other arrhythmias and conditions besides Afib. My passion has always been creation - so throughout the year my master goal is to develop a method that could actually be implemented in a device. I'm not alone in this quest; I have amazing colleagues Slobodan Đukanović, expert in signal processing and machine learning, Milan Sekularac, expert in mechanical engineering and  3D vascular cardiology, Radovan Stojanovic, expert in applied electronics, wearables, and stress detection, and Vladimir Jacimovic, expert in theoretical mathematics. (Quite a team, right? :) I am currently using the publicly available MIT-BIH arrhythmia database, but Milan has physician contacts in Montenegro and Belgrade who may be able to get us patient ECG data! Radovan has already developed ECG devices as well, and he would like me to collaborate with him to develop stress detection devices using ECG as well as various other physiological signals (galvanic skin response, temperature, motion, etc).  
Girls Who Code 
I am SO excited about this!! I hosted an info session last night, and I think we are going to have a lot of engaged girls! Girls Who Code(GWC) isn't global yet, so I can't tap into the official GWC resources, but I've been able to locate many of the open source tool-sets GWC suggests for the girls, as well as some old course materials. I've been researching the curriculum, and I had no idea how many great, free tools there are out there to help people learn to code while doing something that interests us! (Did you know you can create songs while you're learning to code?!  Check these awesome resources out below!) One of the reasons this is so dear to me is because the first step in becoming a leader in tech is realizing that you don't have to be afraid of tech. In college I thought I was one of those people who's brain didn't work like a coder, but that's simply not true. If I can achieve one thing with this program, it's removing that barrier that there's something out there that you can't do. I will never be a full stack engineer or the best coder in the room, but I know what coding can do, I can talk about it, and I can work with teams to be the best coding team in the room! This program isn't just about equipping girls with modern computing skills, it's showing them that they can be leaders in STEM.  ​
Teaching
4th Year Applied Mathematics 
I'm co-teaching applied mathematics with Vladimir to computer science and applied mathematics 4th years, and I am also overseeing the final projects of the computer science students. My students have some great ideas for final projects! Here's a few of their ideas:
  • Solving the N-Queens Problem with a Genetic Algorithm
  • A Decentralized Algorithm for Time Synchronization (they're interested in firefly synchronization and applying this phenomenon)
  • A Poisson Process model for Monte Carlo 
Pretty cool, right!? I'm going to be learning some new things along with them!
Python for Engineers
I'll be teaching Python to some of the professors and students here. Most of the audience has coding experience (Matlab, C++, Java, Fortran), so I'll be teaching a sort of advanced Python for engineers. I'll be teaching this through the MechE department, so many of the tasks they want to use Python for are new to me as well - such as solving differential equations for fluid motion and parallel programming. I've been doing research in preparing my course, and found some really great stuff - check out in the resources. 
Other Fun Stuff
  • Slobodan and I have a daily story hour, where through repetition of riveting children's stories, I am learning Serbian, and Slobodan is slowly losing his mind. I also listen to CDs in my car, make flashcards, and watch tv programming (that always seem to be violent and/or adulterous) with Serbian subtitles, so I have enrichment in the more criminal-type diction. 
  • I've learned to drive my Mini, and I'm now a half decent driver of a manual car. As long as you sign a waiver, I'd be happy to take you anywhere. 
  • Ciara and I signed up to run the half and full marathon (respectively, not each haha) in Marrakech, Morocco this January!! Ciara and Maddie are the Fulbright ETA's, and Maddie is going to come cheer us on! These girls are amazing by the way - inspiring, strong, warm, driven, and awesome. 
  • I don't know how yet, but I'm bringing four 70 pound dogs back to the US. No I know I can't, but I have four sweet pups at my ranch. 
  • I'm playing soccer! I've been the only girl on the field so far, but the guys have been really great. 
Alright that's enough from me for today. Ciao! (How awesome is it that I get to say that over here!? :) 
Resources
Deep Learning for ECG classification
MIT-BIH Database
Github: TensorFlow Implementation of QRS detection method
Paper: 
ECG arrhythmia detection from 2D CNN
Github: ECG arrhythmia detection from 2D CNN 
Unsupervised Heart-rate Estimation in Wearables with Liquid States and a Probabilistic Readout
​Cardiologist Level Arrhythmia Detection with CNN
A Novel Automatic Detection System for ECG Arrhythmias using Maximum Margin Clustering with Immune Evolutionary Algorithm
Futuristic Biosensors for Cardiac Health Care: An Artificial Intelligence Approach
Genetic Algorithm for the Optimization of features and neural networks in ECG signal classification

Interactive Coding Tools 
EarSketch: Compose a song using python or javascript
Circuits.io: Online circuit builder for Arduino projects (C++)
w3schools.com: Learn web technology and execute code (many options) in sandbox
Logic Gate Simulator: Simulate simple circuits of logic gates
K
han Academy: Create Digital Art while learning javascript
Codesters: Learn python by creating interactive stories
Actimator: Make and Publish 2D Games
WeScheme: interactive evaluator and interface for editing and running programs

Python for Engineers
Intro to Python: An open source resource for teachers and students
11 Resources for teaching and learning Python
​
Modeling and Simulation in Python
GitHub: Heat Transfer
Python, CFD, and Heat Transfer (Working Scripts)
​Finite Difference Methods for Diffusion Process
Parallel Loops in Python, R, Matlab, and Octave

2 Comments

Feature Engineering vs Learning

6/26/2018

1 Comment

 
In my field, you hear a lot of buzzwords: artificial intelligence, cognitive, neural network, deep learning, Watson (hehe gotta include that one). They sure sound good, but what do they really mean? How do they fit together?

I've copied this awesome visual from Deep Learnings in Biology that illustrates the relationships between various AI disciplines. As you can see, each of these disciplines is trying to move from an input to an output. In other words, we're trying to build an understanding of the input and make a model or prediction that helps us recreate it. One of the most important steps is figuring out what to look for in those inputs - what features are the most telling about that thing? In other words, what features are the most important in representing that thing? Machine learning often uses hand designed features - us humans try to choose the characteristics -  but as we move into representative and deep learning, the machine can actually learn the features that are the most useful for prediction
Picture
In artificial intelligence, a computer or machine  produces an output without explicitly being given the step-by-step instructions of how to produce that output (as opposed to, an Excel macro, for example, when we tell the algorithm exactly what to do.) However, the complexity of the instructions that we  give the machine can vary quite a bit. We could give the machine very specific instructions: perhaps we want a machine to classify documents, so we ingest several documents that have already been classified correctly. Let's say we have a set of documents that are press releases, legal contracts, and reports. We would feed in the text of these documents along with their classification. The machine learning algorithm would "look" at these labeled documents and "learn" what combinations of features are most probably press releases, legal contracts, or reports.  We also probably told the machine learning algorithm what features it should use to learn. We told the algorithm to use words to learn how to classify - words are one of the features. The machine learning algorithm would be looking for key words and frequency of those key words to make a decision on where that document belongs. 

In this example, we told the algorithm what it needed to learn because we provided it with the correct classifications of past data. We also told the algorithm what features it should use to learn - words, (as well as structure, sentiment, concepts and additional features we didn't talk about).  However, we don't tell the algorithm how to classify the new documents; instead, the machine has learned from the historical labeled data and takes what it learned to classify new documents.  The machine produced an output - classified new documents - but we gave it the rules. 

As you can imagine, there is great utility if we can train a machine to produce an output. However, you'll also see that in this example, we still had quite a bit of manual intervention. We had to feed in correctly labeled documents, and we also had to hand design the features that the machine should use. As such, machine learning algorithms can still be manual and time consuming because of this feature engineering step, especially when hundreds of complicated variables may be necessary to classify images, for example. 

However, what if the machine could also learn what features it should use to build models? In a more complex branch of machine learning called representative learning, the algorithm can actually discover the features that it should use to build a model. By putting in place an artificial neural network, we can create algorithms that will find important features without being told what features to look for. Basically, this type of algorithm (if given enough examples) could decipher the features that make a cat a cat, a dog a dog, and an  apple and apple. Deep learning takes it a step further, learning more complex features by first extracting simpler features and combining them (like whiskers + small triangular nose). Deep learning achieves this by building multiple layers (>2) into a neural network.  An area where deep learning algorithms are being used very successful today is medical image classification. From disease diagnosis, to cell segmentation, to tissue classification,  deep learning algorithms have reached expert-level diagnosis and recognition. 

Anyway, hope you learned something! Here's an interesting perspective on deep learning, especially as it collides with new data protection regulations. 
1 Comment

Rudolph the PureBred Pitbull

12/28/2017

0 Comments

 
Picture
This Christmas, a popular gift in our family was AncestryDNA, which is a pretty cool service that estimates your genetic origins. My father-in-law had recently discovered he was 9% Italian, which prompted a slew of hilarious, if not politically incorrect interpretations of Italian accents and imitations. Using a cheek swab, AncestryDNA tests the DNA in your sample for small single nucleotide polymorphisms, or SNPs. These SNPs, as the name implies, represent single replacements of nucleotides, such as a C (cytosine) instead of a T (thymine). SNPs usually occur between genes (away from exons or control regions), so most of the time there's no effect on health or development. These little replacements are relatively common in the human genome, occurring ~ 1 out of every 300 nucleotides, or about 10 million potential SNPs in each of us. What makes SNPs so great for genetic analysis is that their inheritance is relatively stable - if your mom has an SNP you're highly likely to have the same one. However, there are variations between populations, as over the centuries ethnic cohorts have developed their own signature blend of SNPs. While there are ~10 million SNPs, it's been shown that analysis of just 19 SNPs can identify with high probability an ethnic group. It looks like AncestryDNA uses a chip that has the ability to analyze up to 700K SNPs, so your results are probably pretty damn accurate. 

I'm mildly interested in my own genetic heritage, but something that really DID interest me was the genetic history of ...... my dog. Before you roll your eyes and stop reading, I was mostly curious, but I was also interested because my little man is getting older and I wanted to watch out for the beginnings of breed-specific health problems. I rescued my pitbull Rudy from a shelter in Brooklyn, and we had always speculated if my little brown guy was part chocolate lab, boxer, Rhodesian Ridgeback, etc. So, I shoved a swab in his mouth and sent the sample of to Wisdom Panel and anxiously awaited the results. Well the results came, and to my shock, Rudy is a purebred American Staffordshire! They threw in a cute little genetic fingerprint (probably full of a few of the SNPs that they mapped), a phylogenetic tree, a certificate that he's purebred, and lots of plots that show Rudy is squarely a Staffie. (Most people, including myself, call Staffies pitbulls. However, they're a little different, and I think we can actually see in the following chart.)
​

Picture
In this chart, principal component analysis (PCA) has been conducted on Rudy, subbreeds of Staffies, and a cohort of all other breeds. If we look at the graph, we see PC2 (principal component 2) on the y axis and PC1 (principal component 1) on the x axis. Each of the points is a dog, so each dog has a PC1 and PC2 score.  Dogs have hundreds of characteristics, and in this study, hundreds of SNPs were analyzed, so why is it that we're just graphing 2 properties of dogs? The answer is, we're not! Behind each of these components, we're getting inputs from a whole bunch of characteristics. In other words, PC1 and PC2 are new features that we've created through linear combinations of the actual variables. 

How do we decide which variables make up PC1 and PC2? If you think about it, we want to choose variables that vary the most between breeds - we want a variable that tells us something. We wouldn't want to choose something like "has 4 legs" to distinguish between dog breeds, because that tells us nothing about a sample. However, a gene like "snub nosed" will be very useful in helping us characterize our dog. A good analogy is that game 20 questions. You wouldn't waste your time asking dumb questions; you want to ask those questions that eliminate choices and help you zone in on the target. That's the same goal of PCA. Mathematically, PC1 uses values that maximize variance. Another advantage of PCA is that it take variables that may be correlated and transforms them into variables that are uncorrelated. For example, if height and weight are highly correlated - ie they increase and decrease together very closely - PCA could be used to make one variable that is a combination of height and weight. We are reducing the dimensionality by combining these 2 variables into one new feature, with little loss of information.  In 20 questions, if you had already learned that something is round, you wouldn't want to ask next if it rolled. It probably does, but that information doesn't tell you much more then you already knew. Instead, you'd want your next question to give you the best incremental clarity on what the object is - again, what PCA is mathematically trying to accomplish. 

Let's look back at Rudy's PCA graph. Basically, we have no idea what sort of characteristics we are looking at for each of these dogs - that's not the point here. What PCA does allow us to see is the different signatures of dog breeds. By design, PC1 and PC2 have been composed of the characteristics that tell us the most about the breeds. As you can see in the graph, these signatures are distinct. Rudy is clearly not in this "All Breeds Outgroup" cluster. However, he is in a few clusters, because as you can see, the signatures of these 3 American Staffordshire terrier sub-breeds overlap. What this means is that according to Wisdom Panel's analysis, there are at least 3 types of American Staffordshires, according to their genetic makeup. My guess is that one of these American Staffordshire groups is actually representative of pitbulls.
Picture
The reason I think that is because in the next chart, they also compared Rudy to "next closest breeds". As you see, the next 2 closest breeds are American Bulldogs and Bulldogs, rather than Pitbulls, so I would guess they're calling Pitbulls an American Staffie subgroup. (I sure hope that's not reluctance to share with someone that their dog is a pitbull, because it's a great thing, an not using the word will only feed the stereotype). One more thing to notice about this graph: we didn't just see these 2 new breeds as new clusters on our previous graph because a new set of PCA has been conducted. Previously, traits that separated Rudy from other breeds might be a lot less informative, now that we're trying to compare him to bulldogs. Back to our 20 questions analogy - you gotta ask different questions as possible targets start getting more similar. ​ 

That's just a little look at the science beneath these DNA services! Catch ya later, my little purebred is begging me to go outside! :)
0 Comments

Talent & Tenacity

6/28/2017

0 Comments

 
PictureWE nyc presents "Her Own Boss" - June 22 at WeWork Dumbo Heights
​Last Thursday, I managed to find the F train and get myself to the WeWork office in Dumbo for an amazing women’s entrepreneur event.  (Which is a feat – I am embarrassed by my lack of savvy when it comes to Brooklyn).  This event – “Her Own Boss!” – was presented by Women Entrepreneurs New York City (WE nyc). It was the kickoff of a series featuring local female entrepreneurs. At this session, Liz Gutman, co-founder of Liddabit Sweets, hosted a panel of impressive lady innovators:
  • Brooke Stewart, Power Moms Media
  • Michelle Brandies, Founder & CEO of Name Bubbles
  • Nicole Feliciano, Founder & Editor of Mom Trends
  • Jennifer Martin and Teresa Tsou, Co-Founders of Pipsnacks (had to pull out last minute)
 
During this event, each of these ladies spoke about their experiences and took questions from the audience of business owners, community leaders, and aspiring entrepreneurs. Each of these panelists had a different perspective, a different business and a different industry, but what they all shared was having being bitten by that bug. At different times in their lives, each of these ladies had acquired that dogged, persistent ambition to forge into new territory via startup. 

Picture
Swag from the panelists' companies! We got a bag of Truffle Pipcorn, a label and labeling pen from Name Bubbles, and an excerpt from Mom Trends!
PictureThe panelists discuss their startups to a crowd of aspiring and actualized entrepreneurs!
What I found interesting was the journey of each of these ladies into startup territory. Michelle Brandies of Name Bubbles had a “lightbulb” moment that caused her to quit her job and give it a whirl. Nicole Feliciano took a different route, gathering two years of careful and rigorous study to become an expert in her industry and her potential place in it before launching. Liz Gutman  worked for a famous pastry chef and co-founded her company with a classmate at the French Culinary Institute more or less “by accident”.

I found all of these stories interesting, because they reminded me that everyone’s story really is different. There isn’t really a perfect moment or a standard path to startup success. Not even success – to deciding it’s time to TRY.  If you have an idea, is it startup story waiting to be written?

Everyone’s story is unique, but I think the reason events like this connect us, is that we see elements of ourselves in others. The world is changing all time, and there are opportunities to innovate all around us. One of the connecting threads between the panelists at this event was that they were women. They used their perspectives as women, their motivations as mothers, and their experiences as females to build unique companies. This is another concept that I have thought a lot about recently: why are you famous? In your job, in the sports you play, in the startup that you want to build, what eminence, specialization, perspective, or talent do you possess? What do you bring that nobody else knows or can do as well as you can?
​
Identifying your unique angle is just the first step. Now you need to pair that talent with a drive and determination that is not going to yield to challenges and blockades.

Do you have it? That mix of talent & tenacity? Do you have what it takes to break through that fear and go forge your startup journey? 


Sources: 
1. WE Connect Event: Her Own Boss
2. 15 Signs that you might have Startup DNA


0 Comments

Why We Need Science

4/22/2017

0 Comments

 
This Earth Day morning, thousands are taking to the streets to march. Americans everywhere are foregoing their Saturday brunch to congregate, parade, and shout because they are frustrated, and they want to DO something about it! Today’s march brings people out for a variety of reasons: support for climate control measures frustration with the current administration, connection and activism for one’s community, widespread advocacy for science.

In fact globally, Earth Day has evolved to be more than just a platform for earth science – it’s become a diffuse global podium for people to march show support for science – innovation, education, funding, adaption –  all of these pillars of science that are being attacked. In the US, there’s been top-down rejection of evidence and reason, and it is downright terrifying.



We need science. Science is not a little niche interest that we can de-fund, seal off, and draw lines around as if it’s a detached little accessory field.  Look at the world around us - pacemakers, super computers, optical correction, space exploration, chemotherapy – we are surrounded by technological innovations that give us jobs, keep us alive, and make our lives better – and it is because of science. I’ve heard the argument that industry drives innovation, but I vehemently disagree. If we take away the curiosity, problem-solving, collaboration, and pursuit of knowledge for knowledge’s sake, than we will starve innovation and cripple our society’s ability to evolve, solve, and learn.

This is not just a fight for scientists, for scientific organizations, for university professors and elementary school science teachers. This is everyone’s fight, whether they acknowledge it or not. What’s at stake is our future. If we abandon everything that we have learned, forgo the process of science, then we will be unable to solve tomorrow’s problems. Science is for everyone. I beg that we set aside political views, protected opinions, biases and the like, and that we embrace the central core of scientific investigation: the open pursuit of facts – not just about the world that we live in, but ourselves. 
Picture
At the Sea vs Space debate at the American Museum of Natural Science, there was one issue that the astronauts and aquanauts agreed upon: we've got to advocate more funding, awareness, and support for science as a whole.
0 Comments

TMC Hackathon Weekend

4/8/2017

0 Comments

 
PicturePictured above is my powerhouse team. Clockwise from me is Erik, Shadi, and Hessam.
This post is about my amazing weekend at the Texas Medical Center Biodesign Hackathon in Houston! I assumed "hackathon" was a commonly known term, but after a few conversations with non-techies (no mom, we're not formally gathering to commit unspeakable cyber security crimes) I realized not everyone is aware or has had the opportunity to compete in an awesome event like this. So quick lesson:  "hackathon" is a derived from 2 words:
hack - hacking means clever programming that often modifies or alters standard computer software or hardware. We "hack" together a solution by using elements of this, components of that, and crafty use of that. 
marathon - although the length of hackathons varies from a day to a week, the standard is focused, intense coding or hacking. 

So that's the basic framework for a hackathon. It's honestly more of a sprint, but I suspect word-smithing of hack and sprint variations just hasn't yielded any portmanteaus that can compete with hackathon.  The Hackathon Wikipedia also accurately points out that during such a session, " eating is often informal, with participants often subsisting on food like pizza and energy drinks" . I chuckle at the language- but it's true. While TMC provided us with awesome food, our team often forgot to eat, substituting balanced meals with pickles, Monsters, and K-cup fuel. Sleep is also informal - we worked until midnight Friday night, 4am Saturday night, and 5 pm Sunday! 

This isn't some people's idea of fun, but for people passionate about creation, networking, and learning, a hackathon is an amazing experience. Moreover, this TMC hackathon was focused around healthcare! On Friday, we were presented with four unmet needs in healthcare - two in the medical device setting and two in digital health. After presentation of the unmet needs, we selected our need, formed teams, and began hacking! Meet my impressive team: Erik is CEO and Cofounder of the healthcare consulting company Calamine and came bearing rich experience in health information systems and user interface (UI) design. The amazing Shadi is a mechanical engineer and a research intern at the Texas Heart Institute, and augmented reality (AR), heat transfer, and fluid dynamics are just a few of her specialties. The talented Hessam is a PhD candidate in computer science and comes with an impressive range of skills including IoT (Internet of things) and distributed systems. Like I said, POWERHOUSE team. 

The reason this weekend was so inspiring to me isn't just because I got to meet talented people like my teammates, it was the inspired creation! What we all shared was a passion for innovating in healthcare. Working 30+ hours over a weekend, you've GOT to have passion! (Or craziness. Maybe we're all just a bit unhinged. ;) 

While my team didn't win the pitch competition, we were recognized for best tech. What we created was a real-time tracking system and analytics engine to optimize patient transport and scheduling to radiology. Getting inpatients to radiology is inefficient, in part due to all of the pieces needed including a prepped patient, equipment (wheelchair or bed), and transport staff. Moreover, there is no science to the scheduling of patients on the machines (X-ray, MRI, ulrasound, and CT). This is how we broke down the problem and solved it:
1) Problem: where is all of the stuff?
Solution: A real-time tracking system that locates patients, equipment, and staff through a ultrawide band (UWB) sensor system that can locate these assets within 5 cm. Because this system uses wireless sensors, it is low cost, high accuracy, and automatic - no manual entry required. 


2) Problem: what about all of the areas where hospitals lose WiFi signal? 
Solution: Image recognition technology reads the unique bar-code of each of the sensors. This technology means that even when signal is lost, sensors can "see" wheelchairs, patients - anything with this unique bar-code because the software has been trained to associate bar-code features with these objects. 

3) Problem: Which route should the tech transport staff take in this sprawling hospital, where radiology is 7 flights down and in another wing?
Solution: Image recognition works in concert with augmented reality to point out the optimal route. As you'll see in the video, Shadi's phone recognizes directions to the ER and actually casts an arrow on her view that directs her to the ER! 

These aren't just theoretical solutions - have a look at the 1 minute demo Shadi and Hessam created that shows how the technology works. Hessam walks around, and then we see EXACTLY where he went in this large warehouse with these long range, high accuracy wireless sensors. Next, Shadi has her phone and is walking around in the hospital, and the AR interface tells her which way to go and how long it will take. 


This was just a quick video for our pitch, but hopefully you can see how real, accurate, and EXCITING this tech is! There are companies out there trying to solve hospital operational efficiency, but our team's solution wins in terms of accuracy, image recognition, and advanced analytics.

What's really cool about this solution, is it would ALWAYS be collecting data. Nearly 24/7, we would be building a spatio (location)  temporal (time) record of patient activity. As a data scientist, that feature is a goldmine because not only is the data self-generating, but the dataset is always growing, meaning insights will become more and more rich with time.  

4) Problem: There is no science to radiology scheduling, with the patient order usually based on arrival time and urgency. Complexities such as transport delays, patient prep, and emergency cases that need imaging right away mean that expensive machines sit dormant while patient wait time drags on.  
Solution: Use the spatiotemporal data from the wireless tracking system and electronic medical record (EMR) data to build an algorithm that optimizes patient medical image scheduling. This may sound complex, but it's similar to the global optimization that happens as flights are delayed or cancelled.  When a cancellation or delay happens, the entire system adjusts to optimize airline time and money. In the hospital, the entire system is adjusted to minimize TOTAL patient wait time. There are thousands of ways to schedule, so it's not efficient to check every scenario. Instead, an efficient algorithm should check combinations until it finds one that meets certain criteria: ie emergency patients are seen first, 50 patients are imaged, and the imaging happens within 24 hours - for example. In my simulation, I planned to use an ant colony optimization (ACO) algorithm with a greedy randomized adaptive search (GRASP) to find optimized scheduling in real-time. See a little snippet of my python code here. I'm demonstrating that multiple scenarios are being tested, and when a scenario that fits the criteria is met, the loop stops.  (Check out references below to learn more). 

In close, that's what happens when four crazy, passionate creators get together for 48 hours and drink lots of coffee in an old Nabisco warehouse. I walked away from this weekend with a renewed sense of faith in the creative future of healthcare. Perhaps this system is reluctant to change, and there are more barriers and regulation than in other industries, but there are a slew of brilliant, resourceful entrepreneurs eager to tackle and solve complex problems in healthcare. 

Sources:
1. TMC Biodesign
2. Using Tracking Tools to Improve Patient Flow in Hospitals
3. The best way to improve radiology patient transport efficiency
4. Study on GRASP-ACO Algorithm for Irregular Flight Rescheduling 
5. Online Aircraft Scheduling with Ant Colony Optimization
6. An Irregular Flight Scheduling Model and Algorithm Under the Uncertainty Theory
7. Stanley - A RTLS Competitor (but we do it better :)
​8. YouTube of our Demo! 
9. Monte Carlo stimulation snippet I wrote in python 
Picture
0 Comments
<<Previous
    Picture

    Vanessa Mahoney,  PHD

    Biomedical scientist & data analyst who loves learning how things work - from mortgage-backed securities to cardiac electrophysiology to Donald Trump's comb over

     
    The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions. 

    Archives

    December 2018
    November 2018
    June 2018
    December 2017
    June 2017
    April 2017
    September 2016
    July 2016
    June 2016
    May 2016
    February 2016
    January 2016
    November 2015
    September 2015
    August 2015
    June 2015
    May 2015

    Categories

    All
    Biotech/Healthcare

    RSS Feed

    Categories

    All
    Biotech/Healthcare

Powered by Create your own unique website with customizable templates.