The babette R Package: How to Sooth the Phylogenetic BEAST2

Post provided by Richel Bilderbeek

 What is babette?

‘babette‘ is an R package that works with the popular phylogenetic tool BEAST2. BEAST2 uses one or more alignments and a model setup to create a Bayesian posterior of jointly estimated model parameters and phylogenies.

babette lets you call BEAST2 from an R script. This makes it easier to explore models and/or alignments than using the graphical user interface programs that BEAST2 provides. It will also help you to improve the reproducibility of your work with BEAST2.

babette Tutorial Videos

If you’re new to phylogentic analyses, the video ‘babette demo‘ demonstrates the package. It has all of the information that you need to be able to start using the package

Continue reading


The Global Pollen Project: An Update for Methods Readers

Post Provided by Andrew C. Martin

The Global Pollen Project is an online, freely available tool and data source developed to help people identify and disseminate palynological resources. Palynology – the study of pollen grains and other spores – is used across many fields of study including modern and fossil vegetation dynamics, forensic sciences, pollination, and beekeeping. To help make pollen identification quicker and more transparent, we developed the Global Pollen Project (GPP) – an open, peer-reviewed database of global pollen morphology, where content and expertise is crowdsourced from across the world. Our approach to developing this tool was open: open code, open data, open access. It connects to other data services, including the Global Biodiversity Information Facility and Neotoma Palaeoecology Database, to provide occurrence data for each taxon, alongside pollen images and metadata. Continue reading

HistMapR: 12 Months from Coffee Break Musings to a Debut R Package

Post provided by Alistair Auffret

I was really happy to hear that our paper, ‘HistMapR: Rapid digitization of historical land‐use maps in R’ was shortlisted for the 2017 Robert May Prize, and to be asked to write a blog to mark the occasion. The paper was already recommended in an earlier blog post by Sarah Goslee (the Associate Editor who took care of our submission), and described by me in an instructional video, so I thought that I would write the story of our first foray into making an R package, and submitting a paper to a journal that I never thought I would ever get published in.

Background: Changing Land-Use and Digitizing Maps

Land-use change in Europe is often typified by land-drainage to create arable fields.

Land-use change in Europe is often typified by land-drainage to create arable fields.

Land-use change is largely accepted to be one of the major threats to biodiversity worldwide at the moment. At the same time, a warming climate means that species’ ranges need to move poleward – something that can be hampered by changing land use. Quantifying how land use has changed in the past can help us to understand how species diversity and distributions respond to environmental change.

Unfortunately, quantifying this change by digitizing historical maps is a pretty tedious business. It involves a lot of clicking around various landscape features in a desktop GIS program. So, in many cases, historical land use is only analyzed in a relatively small number of selected landscapes for each particular study. In our group at Stockholm University, we thought that it would be useful to digitize maps over much larger areas, making it possible to assess change in all types of landscape and assess biodiversity responses to land-use change at macroecological scales. The question was, how could we do this? Continue reading

Code-Based Methods and the Problem of Accessibility

Post provided by Jamie M. Kass, Matthew E. Aiello-Lammens, Bruno Vilela, Robert Muscarella, Cory Merow and Robert P. Anderson

The namesake of our software and founder of the field of biogeography, Alfred Russel Wallace. Photo ©G. W. Beccaloni

The namesake of our software and founder of the field of biogeography, Alfred Russel Wallace. Photo ©G. W. Beccaloni

In ecology, new methods are increasingly being accompanied by code, and sometimes even full command-line software packages (usually in R). This is great, as it makes analyses more reproducible and transparent, which is essential for the development of open science. In an ideal world, code would have informative annotation, generalized functions for multipurpose use, and be written in a legible and consistent manner. After all, the code may be used by ecologists with a wide range of programming experience.

In reality, code is often poorly commented (or not commented at all!), hard to reuse for other projects, and difficult to interpret. To add to that, most code isn’t actively maintained, so users are on their own if they try to commandeer it for new purposes. Further, ecologists with little or no programming knowledge are unlikely to benefit from methods that exist only as poorly documented code. In a positive development, some new methods are accessible through software with graphic user interfaces (GUIs) developed by programmers spending significant time and effort. But too often these end up as tools with flashy controls and insufficient instruction manuals. Continue reading