This PROVISIONING_DATA_94_19_README.txt file was generated on 26-04-2022 by Chay Halliwell GENERAL INFORMATION 1. Title of Dataset: 'Data from: Coordination of care by breeders and helpers in the cooperatively breeding long-tailed tit, Aegithalos caudatus'. 2. Author Information Corresponding Investigator Name: Mr Chay Halliwell Institution: University of Sheffield, Sheffield, UK Email: challiwell1@sheffield.ac.uk Co-investigator 1 Name: Andrew P. Beckerman Institution: University of Sheffield, Sheffield, UK Email: a.beckerman@sheffield.ac.uk Co-investigator 2 Name: Marion Germain Institution: University of Sheffield, Sheffield, UK Email: m.germain@sheffield.ac.uk Co-investigator 3 Name: Samantha C. Patrick Institution: University of Liverpool, Liverpool, UK Email: Samantha.Patrick@liverpool.ac.uk Co-investigator 4 Name: Amy E. Leedale Institution: Liverpool Hope University, Liverpool, UK Email: leedala@hope.ac.uk 3. Date of data collection: 1994-2019 4. Geographic location of data collection: Rivelin Valley, Sheffield, UK 5. Keywords: Evolution, Behaviour, Parental care, Coordination, Conflict, Provisioning 6. Language information: English DATA AND FILE OVERVIEW: 1. Description of dataset This is a dataset of provisioning watches taken at long-tailed tit (Aegithalos caudatus) nests during the period at which both parents (and also sometimes helpers) provision chicks (Day 6-16). These data were collected either by observation directly or by subsequent video review of sample provisioning watches. The primary focus of this study was the order that the individuals (carers) provisioned the brood and employed a null model randomization procedure to estimate the level of coordination (either alternation or synchrony) expected by chance. Observed values of alternation and synchrony were calculated directly from each provisioning watch. Expected values of alternation and synchrony were calculated from the median of null model generated randomised sequences from each provisioning watch. These values of interest were then combined into a single dataframe along with general information e.g. brood size, watch duration for subsequent analysis (Collective watch data.csv). Another dataframe was used to investigate the level of coordination by each individual carer (Individual watch data.csv). For analysis of effect of relatedness to brood on helper behaviour pairwise relatedness was generated using the social pedigree data. 2. File list: File 1 name: Raw provisioning data.csv File 1 description: Full list of identities and times, to the nearest minute, each carer provisioned the brood during each given watch File 2 name: Collective watch data.csv File 2 description: Each watch's average values, both observed and expected, for number of alternated and synchronised visits AND general nest and watch information File 3 name: Individual watch data.csv File 3 description: Each individual carer's average values per watch, both observed and expected, for the number of alternated and synchronised visits AND general nest and watch information File 4 name: Relatedness data.csv File 4 description: Social pedigree network for all known birds within dataset, including known dams and sires as well as reconstructed dams and sires based on loci relatedness reconstruction using KINGROUP and CERVUSv2 METHODOLOGICAL INFORMATION Provisioning watches were performed on average every other day between 6 days after recorded hatching and fledging, usually on day 16. These watches were performed either by an observer directly or by video recording for later review. Time of feed and identity of each carer were recorded to the nearest minute. Identification was achieved by unique colour ring combinations. Key nest information e.g. brood size, hatch date were recorded by field observers. Data were then processed so that we recorded the total number of alternated and synchronised feeds by all individuals, per watch (Collective watch data.csv) AND per each individual, per watch (Individual watch data.csv). Observed values must be compared to the baseline level of expected values per watch (Collective watch data.csv) AND per individual per watch (Individual watch data.csv) so we generated expected values as follows: The orders of feeds within each provisioning watch were randomised in such a manner that the length of time between feeds for each individual were conserved in duration, but their position was randomised. We repeated this process 1000 times per watch and calculated the number of alternated and synchronised visits per watch, the median value of which is considered the 'expected' number of alternated or synchronised feeds. DATA-SPECIFIC INFORMATION FOR: Raw provisioning data.csv 1. Number of variables: 14 2. Number of rows: 20992 3. Variable list: Nest: Unique identifier for each nest date: The DD/MM/YYYY data the watch was performed/recorded Brood age: Number of days since recorded hatching Approximate duration: Rough approximation (in hours) of time spent watching nest Start time: Time (hh:mm:ss) the watch started End time: Time (hh:mm:ss) the watch ended Real time: Time of day (hh:mm:ss) each feed was recorded Time into video: Time into each recording (hh:mm:ss) (where appropriate) a feed was recorded FemaleID/MaleID/Helper1ID etc.: Unique identifier for each carer and 'f' designates which of these carers each feed time corresponds to ID: Unique identifier for each watch 4. Missing data codes: NA - Not applicable 5. Abbreviations used: ID - Identification 6. Other relevant information: NA DATA-SPECIFIC INFORMATION FOR: Collective watch data.csv 1. Number of variables: 30 2. Number of rows: 1590 3. Variable list: ID: Unique identifier for each provisioning watch Nest: Unique identifier for each nest RowRef: Row reference 1-1591 Year: Unique identifier for each year the watch was performed during Data type: Whether the data was taken directly from field observation (observed) or from null model randomization (expected) Brood size: The number of live offspring recording in the nest at day 10 post-hatching Brood age: The number of days, since recorded hatching, that a watch was performed Total feeds: The total number of feeds performed by all carers during a given watch AMax: The total percentage of visits during a given watch which could theoretically be alternated (or synchronized). Formula as follows: 100 - ((Number of feeds by highest feed rate carer - Number of feeds by all remaining carers)/Total number of feeds)*100 Alternated visits: Number of alternated visits Percent alt: Percentage of visits which were alternated Percent of AMax: Percentage of visits which could be alternated which were Synchronised1min visits: Number of synchronized visits (1-minute interval) Synchronised2mins visits: Number of synchronized visits (2-minute interval) Synchronised3mins visits: Number of synchronized visits (3-minute interval) Percent sync1min: Percent of visits which were synchronized (1-minute interval) Percent sync2mins: Percent of visits which were synchronized (2-minute interval) Percent sync3mins: Percent of visits which were synchronized (3-minute interval) Percent of AMax Sync2mins: Percent of visits which could be synchronized which were (2-minute interval). MaleID/FemaleID/Helper1ID etc.: Unique identifier for each carer CarerIDs: Unique identifier for all carers present during a given watch Watch time: Number of hours since the start of the day 00:00 the watch was started Total feed rate: The number of feeds performed by all carers per hour Julian hatch date: The number of days since March 1 each year that the eggs hatched Carer number: The number of carers observed provisioning during a given watch Watch duration: The time, in minutes, between the first and last recorded feed during a given watch 4. Missing data codes: NA - Not applicable 5. Abbreviations used: Alt: Alternation Sync: Synchrony Mins: Minutes Ref: Reference Max: Maximum 6. Other relevant information: 'Visits' and 'Feeds' are used interchangeably DATA-SPECIFIC INFORMATION FOR: Individual watch data.csv 1. Number of variables: 21 2. Number of rows: 7951 3. Variable list: ID: Unique identifier for each provisioning watch Feeds: Number of feeds by each individual per watch Data type: Whether the data was taken directly from field observation (observed) or from null model randomization (expected) Alt feeds: Number of alternated visits Percent alt: Percentage of each carer's visits which were alternated Sync feeds: Number of synchronized visits (2-minute interval) Percent sync2mins: Percentage of each carer's visits which were synchronized (2-minute interval) Carer status: Factor designating whether a carer was a breeding female (female), breeding male (male) or non-breeding helper (helper) CarerID: The unique identifier for each carer Total feed rate: The number of feeds performed by all carers per hour Brood size: The number of days, since recorded hatching, that a watch was performed Carer number: The number of carers observed provisioning during a given watch Watch duration: The time, in minutes, between the first and last recorded feed during a given watch Watch time: Number of hours since the start of the day 00:00 the watch was started Brood age: The number of days, since recorded hatching, that a watch was performed Julian hatch date: The number of days since March 1 each year that the eggs hatched AMax: The total percentage of visits during a given watch which could theoretically be alternated (or synchronized). Formula as follows: 100 - ((Number of feeds by highest feed rate carer - Number of feeds by all remaining carers)/Total number of feeds)*100 Year: Unique identifier for each year the watch was performed during nest: Unique identifier for each nest Individual feed rate: The number of feeds performed by each carer per hour RowRef: Row reference 1-7950 4. Missing data codes: NA - Not applicable 5. Abbreviations used: Alt: Alternation Sync: Synchrony Mins: Minutes Ref: Reference Max: Maximum 6. Other relevant information: 'Visits' and 'Feeds' are used interchangeably DATA-SPECIFIC INFORMATION FOR: Relatedness data.csv 1. Number of variables: 4 2. Number of rows: 4310 3. Variable list: id: The unique identifier for each individual BreedGroup: The unique family each individual is from dam: The mother of each unique individual sire: The father of each unique individual 4. Missing data codes: NA - Not applicable 5. Abbreviations used: Breed: Breeding 6. Other relevant information: Some relationships are known from social pedigree network (BreedGroup < 100000), others are from genetic reconstruction using KINGROUP and CERVUSv2 (BreedGroup > 100000) NAs are from individuals whose pedigree was not known