In this follow-up to the previous part of the manuscript on computational ecology, I explore some of the ways to facilitate collaborations between data users and data producers. You can read the first part to get up to speed, and then feel free to comment and give feedback.
Deep down, I feel like there are two types of person in me when I am confronted to a science problem. First, there’s the artist. The big-picture, pie-in-the-sky guy, with creativity, and moxie, and a “We’ll sweat the details later” kind of attitude. And then, there’s the craftsman. The stickler for details, the one in charge of making sure that everything is clear, the one who understand the tools and knows how to use them. This is maybe especially important for computational research, but we need to understand how these two persons-in-us, the artist and the craftsperson, interact.
What is computational ecology? I am working on a manuscript to discuss this topic in the context of ecological synthesis. Since it is almost ready, I would love to get some feedback. And so I have pasted below a part of the introduction. If this little experiment goes well, I will add another section next week, before making it public as a preprint. Think of this as a trailer. To an academic article. Because these, I guess, are the times we live in.
Every time I hear about Big Data in ecology, I cringe a little bit. Some of us may be lucky enough to have genuinely big data, but I believe this is the exception rather than the norm. And this is a good thing, because tiny data are extremely exciting – in short, they offer the challenge of isolating a little bit of signal in a lot of noise, and this is a perfect excuse to apply some really fun tools. And one of my favorite approaches for really small data is ABC, Approximate Bayesian Computation. Let’s dig in!
Don’t we love patterns? This is, after all, one of the purpose of ecology as a science: to describe and document what it is, exactly, that species and individuals and communities and ecosystem do. And in order to do so, we look at them, and transcribe what we see. And so if you happen to find a pattern, this is noteworthy ecology that should be published, whereas the lack of a pattern means the opposite. And now, please, this madness has to stop.
There are very few domains of ecology for which we know any general laws. This is particularly true in the “mess” that is community ecology. Even most recent attempts at conceptual unification rarely go beyond the fact that community ecology is driven by selection, drift, speciation, and dispersal. But so does everything else, as far as living organisms are concerned. Not that we should abandon community ecology, but we need to recognize how little we are able to generalize any of the things we know. Can we replicate ecological results?
In a few weeks, I will be giving a talk at the Association Francophone pour le Savoir annual meeting in McGill University, about how advanced research computing (aka high performance computing) can accelerate discoveries in biodiversity sciences and ecology. Collecting data on any ecosystem, no matter how small, is painstaking. It is long. It is expensive. And as a result, we have a relatively small amount of data. So what could advanced research computing possibly deliver?