Skip to content
#software testing Dataset Open access

African and European Haplotypes Carry Different Slick PRLR Alleles in Criollo and Senepol Cattle — analysis code, figures and supporting data

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Analysis code, configuration, intermediate result tables and figure-generating scripts supporting the manuscript "African and European Haplotypes Carry Different Slick PRLR Alleles in Criollo and Senepol Cattle" (submitted to Animal Genetics). What the study does. The slick coat phenotype of tropically adapted cattle arises from independent truncating mutations of the prolactin receptor (PRLR). Allele counts locate such a variant but do not source it. This work phases the receptor gene without the minor-allele-frequency filter that phasing normally applies, so that each carrier haplotype can be read at the causal site itself, and then assigns every carrier haplotype to a reference panel separately by functional class of site, keeping N'Dama distinct from the sanga populations rather than pooling them as "African". Three truncating alleles segregating in Criollo cattle of the Caribbean and northern South America are resolved: SLICK1 (c.1382del, p.Ala461ValfsTer2) sits on a West African taurine (N'Dama) background in four of five carrier haplotypes, whereas SLICK2 (c.1489C>T, p.Arg497*) and SLICK3 (c.1394C>A, p.Ser465*) sit on European taurine backgrounds. A fourth truncating allele, SLICK5 (c.1396A>T, p.Lys466*), fails a panel-specificity test and is reported as excluded rather than assigned. Referred to its lineage-matched British control, the Senepol carries about six percentage points more West African ancestry, which keeps an African route into tropically adapted taurine cattle open. Files. The manuscript, the Supporting Information, the graphical abstract, the reference list and the README are provided as standalone files. The complete reproducible tree is in slick_ancestry_analysis_code_and_data.zip: scripts/lib/hap_ancestry/ — locus-agnostic engine for haplotype ancestry assignment by functional class (likelihood assignment, site resampling, haplotype network). Everything locus-specific lives in a single YAML. scripts/ — supervised ancestry estimation, titration calibration, lineage-paired controls, background-homozygosity control, panel-specificity filter, informativeness analysis, data acquisition, panel labelling and every figure script. config/slick.yaml — focal sites, reference panels, consequence classes. data/genotypes/ — genotypes at the three focal sites for all 1,880 phased samples, plus the panel labels; these are the inputs that regenerate Figure 1. tables/ and figures/ — the tables and figures of the article and of the Supporting Information. What this archive does not contain. The primary sequence data are public and are referenced by accession rather than redeposited: European Nucleotide Archive ERP150979, PRJEB39353 and PRJEB39924; SRA PRJNA604048; GEO GSE192471 (Senepol liver RNA-seq); Dryad doi:10.5061/dryad.th092 (high-density array genotypes); the WIDDE portal; and CLARITY doi:10.5281/zenodo.17909700 (physical-genetic map). Reference assembly ARS-UCD1.2. What changed in version 1.1.0. This version accompanies a restructured manuscript. The Summary was rewritten; the two figures that had been supplementary were promoted into the body and the supplementary material now holds tables and text only; the figure set was consolidated from eight candidates into six multi-panel figures, so that the assay calibration and the sensitivity of the ancestry estimate to the number of ancestry axes now appear together as one figure, and the population ranking now appears alongside the paired controls; two pairs of Results subsections were merged under single headings; part of the methodology that had lived only in the supplementary file was moved into Materials and methods, because a figure in the body needs its method in the body; and the haplotype network was redrawn in a vertical, single-column layout. The scientific results are unchanged. See README.md for the software environment, the data sources, and how to go from the public accessions to each reported number.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 728 citations · ⚡54
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, the results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.