Your English writing platform
Discover LudwigExact(1)
We compiled different datasets for the analyses: 1) all data combined, 2) phylogenetic subsampling, with datasets containing all of the available species from different endemic Australian radiations (to test the effect of dense taxon sampling), and 3) regional datasets that each contained all of the specimens from a given area (individual or combinations of Australian states).
Similar(59)
The "bard1" dataset was downloaded from BARD in January 2013 and is the default dataset for the analyses herein.
Our dataset for the analyses in BEAST included the cytochrome b sequence from L. fabalis (accession number U46808, [28]) and haplotype 26 (accession number JF340319) typically found in L. arcana.
The dataset for the analyses was established after linking prescriptions from databases on GP prescribing and pharmacy delivering, for a set of different drug classes (each class containing one branded and one or more generic drugs of the same chemical entity).
The databases used to build the datasets for these analyses differed between countries, most notably in terms of whether anonymous patients were tracked across pharmacies (Germany) or within a specific pharmacy only (UK and the Netherlands).
The datasets for these analyses were comprised of 359 and 543 unambiguously aligned amino acid sites, respectively.
Input datasets for these analyses included the entire DNA sequences of individual ORFs or, where noted, a set of multiple ORFs.
The datasets used for the analyses reported here were de-identified.
The datasets used for the analyses described in this manuscript were obtained from dbGaP through dbGaP accession number phs000145.v2.p2.
The datasets used for the analyses of this study are available in TreeBASE (Study Accession URL: http://purl.org/phylo/treebase/phylows/study/TB2 S15260?format=html).
The datasets used for the analyses described in this manuscript were obtained from the NINDS Database through dbGaP accession numbers phs000006.v1.p1 and pht000649.v1.p1.
Write better and faster with AI suggestions while staying true to your unique style.
Since I tried Ludwig back in 2017, I have been constantly using it in both editing and translation. Ever since, I suggest it to my translators at ProSciEditing.

Justyna Jupowicz-Kozak
CEO of Professional Science Editing for Scientists @ prosciediting.com