This readme.txt file was generated on 2025-01-16 by Amy Waananen and updated on 2025-05-04. ------------------- GENERAL INFORMATION ------------------- 1. Title of Dataset: Supporting data for “The fitness effects of outcrossing distance depend on parental flowering phenology in fragmented populations of a tallgrass prairie forb." 2. Author Information Principal Investigator Contact Information Name: Waananen, Amy Institution: University of Minnesota Email: waana001@umn.edu ORCID: 0000-0002-7940-3210 Associate or Co-investigator Contact Information Name: Ison, Jennifer L Institution: College of Wooster Email: jison@wooster.edu ORCID: 0000-0003-3857-285 Associate or Co-investigator Contact Information Name: Shaw, Ruth G Institution: University of Minnesota Email: shawx016@umn.edu ORCID: 0000-0001-5980-9291 Associate or Co-investigator Contact Information Name: Wagenius, Stuart Institution: Chicago Botanic Garden Email: swagenius@chicagobotanic.org ORCID: 0000-0003-0655-0823 3. Date published or finalized for release: Pending final manuscript acceptance 4. Date of data collection: 2006 to 2021 5. Geographic location of data collection: Grant County and Douglas County, Minnesota, USA. Most sites are located within Solem Township (45.804167, -95.683333). We have not provided exact coordinates here due to conservation concerns. However, we will share those locations with scientists who are conducting legitimate research on this species, on the grounds that the exact locations are not published in future studies. Please see contact information above. 6. Information about funding sources that supported the collection of the data: This work was supported by NSF, including REU, ROA, RET & RAHSS supplements (awards 2051562, 2050455, 1557075, 1555997, 1355187, 1052165, 1051791, 0545072, 0544970, 0521245, and 0083468). 7. Overview of the data (abstract): The much-studied phenomena of isolation-by-distance and isolation-by-time inform our understanding of mating patterns and population genetic processes, such as inbreeding and local adaptation. These processes influence progeny fitness. However, the offspring fitness effects of parental isolation in space and time have not been investigated together. Over 16 years, we measured fitness of offspring from parents comprising a range of interparent distances (0 to >9 km) and asynchronies (0-13 days between start dates) in 13 populations of a tallgrass prairie forb, Echinacea angustifolia. We used Aster life-history analysis to assess the offspring fitness effects of interparent distance and asynchrony. Interparent asynchrony modified the relationship between interparent distance and offspring fitness. The offspring with the highest fitness had parents from highly distant source populations and a maternal plant that flowered late relative to the paternal plant. Interestingly, the order in which the parental plants flowered, rather than the absolute difference in their flowering, better predicted offspring fitness. Morphological constraints related to timing of reproduction, rather than genetic mechanisms alone, may have contributed to the effects of interparent asynchrony. We suggest management strategies to promote outcrossing over space and time. -------------------------- SHARING/ACCESS INFORMATION -------------------------- 1. Licenses/restrictions placed on the data: Private - for peer review only. 2. Links to publications that cite or use the data: NA 3. Was data derived from another source? Paternity assignments were derived from Reed WJ, Ison JL, Waananen A, Shaw FH, Wagenius S, Shaw RG. 2022. Genetic variation in reproductive timing in a long-lived herbaceous perennial. American Journal of Botany 109: 1861–1874. 4. Terms of Use: We plan to submit these data upon acceptance to the Data Repository for the U of Minnesota (DRUM). By using these files, users agree to the Terms of Use. https://conservancy.umn.edu/pages/drum/policies/#terms-of-use --------------------- DATA & FILE OVERVIEW --------------------- 1. File List A. Filename: offspring_fitness_data.csv Short description: This file contains information about offspring survival and reproduction, i.e. fitness. B. Filename: fitness_predictors.csv Short description: This data set contains information interparent distance and interparent asynchrony, as well as associated information (e.g., parental source population codes and start dates of flowering). C. Filename: analysis_code.R Short description: Contains code to compile the data and perform aster analyses to assess the relationship interparent distance, interparent asynchrony, and progeny fitness. 2. Relationship between files: The R code reads in and analyzes data from the two CSV files. -------------------------- METHODOLOGICAL INFORMATION -------------------------- 1. Description of methods used for collection/generation of data: See associated manuscript. 2. Methods for processing the data: See details in manuscript and within the R script. Data here have been minimally pre-processed. Processing steps that led to the files include compiling the coordinates of parental source populations and using these to calculate offspring interparent distances. We have omitted this here based on concerns regarding sharing coordinates, as detailed above. In addition, we have pre-filtered the paternity assignments to those with >80% confidence. 3. Instrument- or software-specific information needed to interpret the data: R session information for the analysis (see more detail below); R version 4.3.1 (2023-06-16 ucrt) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 11 x64 (build 22631) 4. Standards and calibration information, if appropriate: N/A 5. Environmental/experimental conditions: Old field prairie restorations in west central Minnesota, USA. 6. Describe any quality-assurance procedures performed on the data: In the field, we enter offspring fitness data in pairs. We perform field checks for any unusual records within the same season of observation. 7. People involved with sample collection, processing, analysis and/or submission: Many interns with were involved in data collection. Please see the 'flog' (field blog) for entries related to the offspring fitness measurements the years. All co-authors were involved in data processing and curation. Amy was responsible for analysis and submission. ----------------------------------------- DATA-SPECIFIC INFORMATION FOR: fitness_predictors.csv ----------------------------------------- rows: 439 cols: A. Name: cgPlaId Description: unique identifier for offspring (numeric) B. Name: parentDist Description: Distance between parental source population medoids in meters (numeric) C. Name: diffStartDir Description: Directional difference in parental start dates of flowering (anthesis). Maternal start date of flowering minus paternal start date of flowering. (numeric) D. Name: cgPlaId.dam Description: unique identifier for the paternal plant (numeric) E. Name: cgPlaId.sire Description: unique identifier for the paternal plant (numeric) F. Name: popCd.dam Description: source population of the maternal plant (character) G. Name: popCd.sire Description: source population of the paternal plant (character) H. Name: ach_pos Description: position of the fruit (achene) within the maternal head. top = the achene was one of the 1-10th uppermost fruits; t2 = the achene was one of the 11-30th uppermost fruits; bot = the achene was one of the lowermost 30 fruits; head = the achene was from elsewhere within the head, exclusive from the other categories. (character) I. Name: start.dam Description: the start date of flowering for the maternal plant in the year of mating (2005) J. Name: start.sire Description: the start date of flowering for the paternal plant in the year of mating (2005) ----------------------------------------- DATA-SPECIFIC INFORMATION FOR: offspring_fitness_data.csv ----------------------------------------- rows: 3961 cols: 47 A. Name: cgPlaId Description: common garden plant Id (numeric) B. Name: row Description: common garden location coordinate / easting or row coordinate in meters (numeric) C. Name: pos Description: common garden location coordinate / northing or position coordinate in meters (numeric) D. Name: yrPlanted Description: year planted (numeric) We annually assess the following for each plant: E. Name: ld[observation year] Description: living during observation year / 1 = yes, 0 = no (binary) F. Name: fl[observation year] Description: flowering during observation year / 1 = yes, 0 = no (binary) G. Name: hdCt[observation year] Description: head count / if flowering, count of heads per plant for observation year (numeric) * H. Name: achCt[observation year] Description: achene count / count of achenes per plant for observation year (numeric) ** * here are the rules for what we consider a head: If a head was measured as normal, bent, tilted or indented (or combinations of those) it will be considered a countable head. (hdStatusCd 1-4,12-16) If a head was listed as dud, crisp, no florets, vertical development, no hd, whole head weird, or gone it is not counted as a head. However, head status is adjusted based on achenes counted: Heads are counted only if the achene count from that head is greater than 0. Heads with 0 achenes are not included in the head count for the plant. ** here is an explanation for negative numbers in acheneCt: We use “-9999” as code for “missing data” in the achCt field for each head. If the plant had multiple heads & a count was missing for one of the heads, -9999 was summed together with the good achene count(s). So far, we don’t have any instances where more than one head has a missing achene count per plant; but if we do, I’ll make a note of it. So if hdCt > 1 & acheneCt < 0 adding 9999 to acheneCt will give you the acheneCt for the heads that are not missing data. ----------------------------------------- R SESSION INFORMATION FOR GENERATING RESULTS FROM: analysis_code.R ----------------------------------------- R version 4.3.1 (2023-06-16 ucrt) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 11 x64 (build 22631) Matrix products: default locale: [1] LC_COLLATE=English_United States.utf8 LC_CTYPE=English_United States.utf8 LC_MONETARY=English_United States.utf8 [4] LC_NUMERIC=C LC_TIME=English_United States.utf8 time zone: America/Chicago tzcode source: internal attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] here_1.0.1 patchwork_1.1.3 ggplot2_3.4.4 tidyr_1.3.0 dplyr_1.1.3 aster_1.1-2 loaded via a namespace (and not attached): [1] trust_0.1-8 gtable_0.3.4 compiler_4.3.1 tidyselect_1.2.0 Rcpp_1.0.11 scales_1.2.1 [7] lattice_0.21-8 R6_2.5.1 generics_0.1.3 classInt_0.4-10 sf_1.0-14 ggrepel_0.9.4 [13] tibble_3.2.1 units_0.8-4 rprojroot_2.0.4 munsell_0.5.0 DBI_1.1.3 pillar_1.9.0 [19] rlang_1.1.1 utf8_1.2.4 sp_2.1-1 cli_3.6.1 withr_2.5.1 magrittr_2.0.3 [25] class_7.3-22 grid_4.3.1 rstudioapi_0.15.0 ggspatial_1.1.9 lifecycle_1.0.3 vctrs_0.6.4 [31] KernSmooth_2.23-21 proxy_0.4-27 glue_1.6.2 fansi_1.0.5 e1071_1.7-13 colorspace_2.1-0 [37] purrr_1.0.2 tools_4.3.1 pkgconfig_2.0.3