https://github.com/cjabradshaw/legumestatus
R Code for correlating life history with status (threatened/invasive) of legumes
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
○codemeta.json file
-
○.zenodo.json file
-
✓DOI references
Found 2 DOI reference(s) in README -
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (9.6%) to scientific vocabulary
Keywords
Repository
R Code for correlating life history with status (threatened/invasive) of legumes
Basic Info
Statistics
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
- Releases: 0
Topics
Metadata Files
README.md
Predicting legume threat or invasive status
R Code for correlating life history with status (threatened/invasive) of legumes
Code & data from this article:
Bradshaw, CJA, X Giam, HTW Tan, BW Brook, NS Sodhi. 2008. Threat or invasive status in legumes is related to opposite extremes of the same ecological and life-history attributes. Journal of Ecology 96: 869-883
Abstract
The urgency and scale of the global biodiversity crisis requires the application of generalized predictors of a species’ likelihood of going extinct or becoming invasive in non-native areas. A common approach is to correlate species’ ecological and life-history characteristics (attributes, traits) with the probability of becoming either threatened (responding negatively to human activity), or invasive (responding positively). The limitation of previous studies is that the fates of becoming threatened or invasive have generally been treated in isolation. Here we consider the problem of threat and invasiveness in unison based on analysis of one of the largest-ever species attributes data bases (8906 species) compiled for a single plant family (Fabaceae). We used generalized linear mixed-effects models (using taxonomic grouping to control for within-family phylogenetic relationships) to correlate species’ life-history and ecological traits to three response variables: probability of being (i) threatened or not, (ii) invasive or not, and (iii) threatened or invasive. We found that tall, annual, range-restricted species with tree-like growth forms, inhabiting closed-forest and lowland sites are more likely to be threatened. Conversely, climbing and herbaceous species that naturally span multiple floristic kingdoms and habitat types are more likely to become invasive. These results support the idea that at least for one of the richest plant families, species’ life-history and ecological traits correlate with a fate response to anthropogenic global change. Our results show that species do demonstrate particular susceptibility to either fate based on their evolved traits, and that traits generally correlated with invasiveness are also those that correlate with a reduced probability of becoming threatened.
R file
legume.r
Data file
legume4.csv
Owner
- Name: Corey Bradshaw
- Login: cjabradshaw
- Kind: user
- Location: Adelaide, South Australia
- Company: Flinders University
- Website: http://globalecologyflinders.com
- Twitter: conservbytes
- Repositories: 15
- Profile: https://github.com/cjabradshaw
Matthew Flinders Professor of Global Ecology @GlobalEcologyFlinders @CABAH
GitHub Events
Total
Last Year
Committers
Last synced: about 2 years ago
Top Committers
| Name | Commits | |
|---|---|---|
| Corey Bradshaw | c****w@g****m | 10 |
Issues and Pull Requests
Last synced: about 2 years ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0