With just a few individuals left to send off as redos, most of the focus on the milkweed project has moved towards analysis. Analysis is inherently tricky because there is a lot of trial and error. There are essentially a few options for analysis. You can use someone else’s software, you can modify someone else’s to fit your needs, OR you can make your own. The last one is obviously extremely time intensive, so our hope was to find a software we could use to fit our needs.

If there’s one thing that I’ve learned from my three years of research, it’s that its super important to go with the flow. Since my last update my milkweed project has taken on an entirely new shape. After discovering that glyphosate herbicides do not act as a proxy for connectedness, I decided to use a different approach and expand on my project from last summer.

My original plan was to use common Milkweed as a study system to understand the impact of clonality and group survival. By intentionally adding a pathogen, such as an herbicide, the spread of the negative effects can be witnessed in a clonally connected plant. The goal of this experiment is to see how far the pathogens travel in a patch, how long it takes for other plants to die, and if there is any preferential sharing. For instance, sometimes younger plants are favored in sharing. Herbicide will be used as a proxy for connectedness and physiological integration.