16802 results for "sec+and+unspecified+malignant+neoplasm"

in 35.48 milliseconds.

• Measurement of SARS-CoV-2 variants fraction in infected alveolar cells

  With the continuous emergence of highly transmissible SARS-CoV-2 variants, the comparison of their infectivity has become a critical issue for public health. However, a direct assessment of the viral characteristic has been challenging due to the lack of appropriate experimental models and efficient methods. Here, we conducted full-length transcriptome sequencing of single human alveolar cells infected by multiple SARS-CoV-2 variants, including GR (B.1.1.119), Alpha (B.1.1.7), Delta (B.1.617.2), and Omicron (BA.1). Using unique mutations of each VOC, we calculated the fraction of VOCs in infected cells.

  Study EGAS00001006730

• Autozygosity pilot - Born in Bradford (2014-11-20)

  The offspring of first cousin marriages have ~6% of their genome autozygous, i.e. homozygous identical by descent, or even more if there was further consanguinity in their ancestry. In the UK there are large populations with very high first cousin marriage rates of 20-50%. Sequencing the exomes of a sample of these individuals has the potential both to support genetic health programmes in these populations, and to provide genetic research information about rare loss of function mutations. This pilot study based on existing cohort samples from the Born In Bradford study will identify homozygous individuals for almost all variants down to an allele frequency around 1%, plus individuals carrying hundreds of new homozygous rare loss-of-function variants, and will support development of community relations and ethics for a wider study currently being designed. The data deposited in the EGA consist of low coverage whole exome sequencing on these samples.Data Access is controlled by the Wellcome Trust Sanger Institute DAC and the Born In Bradford Executive Group. This dataset contains all the data available for this study on 2014-11-20.

  Dataset EGAD00001001079

• An atlas of the developing human fetal spine

  The primitive streak emerges during the 14th day of human development and establishes dorsoventral and antero-posterior (craniocaudal) body axes. Segmentation along the craniocaudal axis is governed by Hox genes; four clusters of transcription factors whose 3’ to 5’ expression correlates with position along the axis. The precise utilisation of Hox genes in different cell types remains incompletely characterised in humans. In this study, we applied single-cell and spatial transcriptomics to contiguous regions of the human fetal spine between the 5th and 13th post-conception weeks. We built a detailed developmental atlas to examine the segmental expression of Hox genes across different cell types, observing that the Hox code was displayed by all anatomically fixed cell types along the craniocaudal axis. By contrast, mature derivatives of neural crest cells retained the anatomical Hox code of their origin within the crest, a pattern reproduced across neural crest derivatives in other human fetal organs. These findings indicate that scars of Hox gene expression persist in crest cells which may serve as barcodes of neural crest migration.

  Dataset EGAD00001009801

• Whole blood RNA sequencing of individuals from Nepal

  This study utilized blood samples collected in Lalitpur, Nepal as part of the Strategic Typhoid Alliance across Africa and Asia (STRATAA) study. The dataset comprises whole blood RNAseq of 376 febrile individuals from Nepal. Blood was collected in PAXgene tubes and sent to Monash University (Melbourne, Australia) where RNA was extracted using the PAXgene Blood RNA kit before being sent to the Wellcome Sanger Institute (Hinxton, UK) for sequencing. Library prep used NEBNext Ultra II RNA custom kits on an Agilent Bravo WS automation platform with poly(A) pulldown. After PCR, plates were purified using Agencourt AMPure XP SPRI beads and libraries were quantified using Biotium Accuclear Ultra high sensitivity dsDNA Quantitative kits. Pooled libraries were normalised to 2.8 nM. Samples were globin depleted using KAPA RNA HyperPrep with RiboErase. Libraries were then subjected to 2x100bp paired-end sequencing on Illumina NovaSeq. Each library was sequenced to an average of 80 million reads. The STRATAA study was approved by the Nepal Health Research Council (NHRC, ref 283 306/2015) and OxTREC (Oxford Tropical Research Ethics Committee, ref 39-15). All participants provided informed consent for human genetic tests.

  Dataset EGAD00001011131

• The Mood and Methylation Study (MMS)

  The Mood Methylation Study (MMS) is an observational study designed to understand epigenetic mechanisms underlying major depression symptoms (MDD) using a co-twin control design. Twins enrolled in the MMS were monozygotic (MZ) twin pairs discordant on lifetime history of MDD. All twins were members of the Washington State Twin Registry (WSTR), a community-based twin registry consisting of over 10,000 twin pairs. Lifetime and current MDD diagnoses were determined using the Structured Clinical Interview for DSM-IV Research Version (SCID-4-RV). DNA methylation in blood monocytes was measured using the Infinium HumanMethylationEPIC BeadChip. Monocyte gene expression was quantified by paired end RNA-seq (50 PE). Zygosity of the twin pairs included in the MMS was self-reported and confirmed using the polymorphic SNPs included in the DNA methylation array.

  Study phs002858

• Hereditary Cancer Predisposition Syndromes and Uveal Melanoma

  Uveal melanoma (UM) is a subtype of melanoma characterized by the strong contribution of genetic rather than environmental factors in the pathogenesis of the disease, making it an ideal model disease to study the genetic basis of cancer. The long-term goal of our laboratory is to determine the genes and mechanisms responsible for hereditary cancer predisposition associated with UM. BAP1 has been identified as a candidate gene with definitive association with predisposition to UM. However, pathogenic variants in BAP1 are detected in only a small subset of UM patients even those with strong personal and family history of cancer suggesting the existence of other candidate genes. The goal of this project is to identify novel candidate genes contributing to hereditary predisposition to UM in patients with no detectable germline pathogenic variant in BAP1.

  Study phs001943

• Transcriptomics of Liver and PBMCs in Alcohol-Associated Liver Disease

  This study was designed to characterize the transcriptome of alcohol-associated hepatitis using RNA sequencing (RNA-seq) technology for both liver tissue biopsies and peripheral blood mononuclear cells (PBMCs) extracted from blood samples, in order to identify expressed genes that are markers of the disease. To distinguish genes that differentiate alcohol-associated hepatitis from other inflammatory liver diseases, we compared the RNA-seq data generated from participants with alcohol-associated hepatitis, alcohol-associated cirrhosis, chronic hepatitis C infection, non-alcohol-associated fatty liver disease, and healthy controls. We utilized computational approaches to demonstrate that gene expression data generated from either liver tissue or blood samples can be used to identify a small set of gene biomarkers to distinguish between these liver diseases. The raw RNA-seq data will be available through dbGaP.

  Study phs003112

• Hereditary Gastric Cancer Syndromes: An Integrated Genomic and Clinicopathologic Study of the Predisposition to Gastric Cancer

  Gastric cancers are cancers of the stomach. Hereditary cancers are passed from parent to child. Researchers want to gather data about hereditary gastric cancers. Bulk RNA sequencing (RNA-seq) of signet ring cells (SRCs) and adjacent non-SRC epithelium (NEP) was performed on laser-capture microdissected (LCM) regions of interest found in risk-reducing total gastrectomy specimens from hereditary diffuse gastric cancer (HDGC) patients (Clinicaltrials.gov ID: NCT03030404). Twenty patients (6 male, 14 female) with confirmed HDGC were identified. Analysis of differentially expressed genes (DEGs) demonstrated upregulation of certain individual epithelial–mesenchymal transition (EMT) and proliferation genes. SRC regions had significant enrichment in pathways involved in T cell signaling. CIBERSORTx predicted significant increases in the presence of regulatory T cells (Tregs) specific to SRC regions.

  Study phs003422

• Ribosome profiling shows variable sensitivity to detect open reading frames for conventional and different types of cryptic T cell antigens

  The aim of the study was to explore the sensitivity of ribosomal profiling to detect ORFs for cryptic antigens targeted by T cells in immune responses. Ribosomal profiling was performed for six EBV-LCLs. Detection of conventional and cryptic MiHA-encoding ORFs was compared. The data showed that open reading frames (ORFs) for conventional MiHAs as well as cryptic MiHAs in upstream ORFs were frequently detected with similar sensitivity. However, only a limited number of MiHAs in in reading frames alternative to protein-coding sequences and no ORFs derived from long non-coding RNAs were detected. In conclusion, Ribo-seq for identification of antigen-encoding ORFs is useful to screen for cryptic antigens in upstream ORFs as potential targets for immunotherapy.

  Study EGAS50000000322

• Adeno-associated virus in the liver: natural history and consequences in tumor development

  Adeno-associated virus (AAV) is a defective mono-stranded DNA virus, endemic in human population (40-80%). AAV infection has long been considered as non-pathogenic1, however few years ago we reported for the first time recurrent clonal AAV2 insertion in the pathogenesis of human hepatocellular carcinoma (HCC) developed on normal liver. These clonal viral insertions target cancer driver genes, including CCNA2, CCNE1, TERT, TNFSF10 and MLL4, leading to their overexpression. The viral inserted sequences involved in almost all the cases the 3’ inverse tandem repeat (ITR) of AAV2, which is important for virus integration in host DNA and exhibits a promoter/enhancer activity. Here, we used RNA sequencing (RNA-seq) to investigate their functional impact on the tissue, such as fusion transcript generation events.

  Study EGAS00001003310

• The long term effects of chemotherapy on normal blood - Nanoseq dataset

  In developed countries, ~10% of individuals are exposed to systemic chemotherapy for cancer and other diseases. Many chemotherapeutic agents act by increasing DNA damage in cancer cells, hence triggering cell death. However, there is limited understanding of the extent and consequences of collateral DNA damage to normal tissues. To investigate the impact of chemotherapy on mutation burdens and cell population structure of a normal tissue we sequenced blood cell genomes from 23 individuals, aged 3-80 years, treated with a range of chemotherapy regimens. Substantial additional mutation loads with characteristic mutational signatures were imposed by some chemotherapeutic agents, but there were differences in burden between different classes of agent, different agents of the same class and different blood cell types. Chemotherapy also induced premature changes in the cell population structure of normal blood, similar to those of normal ageing. The results constitute an initial survey of the long-term biological consequences of cytotoxic agents to which a substantial fraction of the population is exposed during the course of their disease management, raising mechanistic questions and highlighting opportunities for mitigation of adverse effects.

  Dataset EGAD00001015340

• Systemic mutagen exposures reported by normal kidney cell genomes - bulk kidney samples (NanoSeq)

  Lifestyle, environmental and other exposures to exogenous mutagens generate somatic mutations in normal human cells in vivo and increase cancer risk. However, the global repertoire of exogenous mutagen exposures is uncertain. Using single-molecule duplex sequencing of normal kidney (n=319) and blood (n=272) samples from 10 countries, we show that kidney proximal tubule cells exhibit higher mutation rates than most normal cell types despite low cell division rates. Compared to cells from kidney glomeruli, medulla, distal tubules, or peripheral blood, proximal tubule cells show marked enrichment of mutational signatures due to the exogenous carcinogenic mutagens, aristolochic acids, and of several signatures of unknown causes. The results suggest the existence of multiple, common, systemically circulated mutagens affecting human populations and indicate that the genomes of kidney proximal tubule cells report such exposures with high sensitivity.

  Dataset EGAD00001015825

• Systemic mutagen exposures reported by normal kidney cell genomes - kidney cancer samples (whole-genome sequencing)

  Lifestyle, environmental and other exposures to exogenous mutagens generate somatic mutations in normal human cells in vivo and increase cancer risk. However, the global repertoire of exogenous mutagen exposures is uncertain. Using single-molecule duplex sequencing of normal kidney (n=319) and blood (n=272) samples from 10 countries, we show that kidney proximal tubule cells exhibit higher mutation rates than most normal cell types despite low cell division rates. Compared to cells from kidney glomeruli, medulla, distal tubules, or peripheral blood, proximal tubule cells show marked enrichment of mutational signatures due to the exogenous carcinogenic mutagens, aristolochic acids, and of several signatures of unknown causes. The results suggest the existence of multiple, common, systemically circulated mutagens affecting human populations and indicate that the genomes of kidney proximal tubule cells report such exposures with high sensitivity.

  Dataset EGAD00001015826

• Gene expression and Cancer

  Dac EGAC00001001727

• CHIP and LOY in AD

  Dac EGAC00001003606

• Resuscitation Outcomes Consortium (ROC) Hypertonic Saline (HS) Trial Shock Study and Traumatic Brain Injury Study (TBI) (ROC-HS/TBI-BioLINCC)

  Data Access NOTE Please refer to the "Authorized Access" section below for information about how access to the data from this accession. Access differs from many other dbGaP accessions.ObjectivesShock: To determine if prehospital administration of 7.5% hypertonic saline with 6% Dextran-70 (HSD) or 7.5% hypertonic saline alone (HS), compared to current standard therapy with normal saline (NS), as an initial resuscitation fluid, affects survival following traumatic injury with hypovolemic shock.TBI: To determine whether out-of-hospital administration of hypertonic fluids improves neurologic outcome following severe traumatic brain injury (TBI).Background Trauma is the leading cause of death among North Americans between the ages of 1 and 44 years. The majority of these deaths result from hypovolemic shock or severe brain injury. Participants in hypovolemic shock develop a state of systemic tissue ischemia then a subsequent reperfusion injury at the time of fluid resuscitation. Conventional resuscitation involves the IV administration of a large volume of isotonic or slightly hypotonic (lactated ringers, LR) solutions beginning in the prehospital setting. Although not conclusive, prior studies have suggested that alternative resuscitation with hypertonic saline (7.5%) solutions may reduce morbidity or mortality in these participants. Furthermore, hypertonic fluids may have specific advantages in the brain-injured participant, as they may aid in the rapid restoration of cerebral perfusion and prevent extravascular fluid sequestration, thereby limiting secondary brain injury. In addition, recent studies have demonstrated that hypertonicity significantly alters the activation of inflammatory cells, an effect that may reduce subsequent organ injury from ischemia-reperfusion and decrease nosocomial infection. The majority of previous clinical trials have focused on the use of HSD. The potential for 7.5% saline alone (HS) to have similar effects has not been well studied. Removal of the dextran component may enhance the anti-inflammatory effects of this solution, which could improve secondary outcomes such as acute respiratory distress syndrome (ARDS), multiple organ failure syndrome (MOFS) and rates of nosocomial infections. Participants Shock: There were 893 participants that were randomized (853 enrolled).TBI: There were 1282 participants enrolled and 6-month outcomes data were available for 1087 (85%).Design Shock: Multicenter, randomized, blinded clinical trials involving 114 emergency medical services agencies in North America within the Resuscitation Outcomes Consortium were conducted from May 2006 to August 2008. Initial resuscitation fluid, 250 mL of either 7.5% saline per 6% dextran 70 (hypertonic saline/dextran, HSD), 7.5% saline (hypertonic saline, HS), or 0.9% saline (normal saline, NS) administered by out-of-hospital providers. Primary outcome was 28-day survival. On the recommendation of the data and safety monitoring board, the study was stopped early (23% of proposed sample size) for futility and potential safety concern.TBI: Multicenter, double-blind, randomized, placebo-controlled clinical trials involving 114 North American emergency medical services agencies within the Resuscitation Outcomes Consortium were conducted between May 2006 and May 2009. A single 250-mL bolus of 7.5% saline/6% dextran 70 (HSD), 7.5% saline (HS), or 0.9% saline (NS) initiated in the out-of-hospital setting. The main outcome measure was a six-month neurologic outcome based on the Extended Glasgow Outcome Scale (GOSE) (dichotomized as >4 or ≤4). The study was terminated by the data and safety monitoring board after randomization of 1331 participants, having met prespecified futility criteria.Conclusions Shock: Among injured participants with hypovolemic shock, initial resuscitation fluid treatment with either HS or HSD, compared with NS, did not result in superior 28-day survival. However, interpretation of these findings is limited by the early stopping of the trial (PMID: 21178763).TBI: Among participants with severe TBI not in hypovolemic shock, initial resuscitation with either HS or HSD, compared with normal saline, did not result in superior 6-month neurologic outcome or survival (PMID: 20924011).

  Study phs003777

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• Study of Clinical Efficacy of Antimicrobial Therapy Strategy Using Pragmatic Design in Idiopathic Pulmonary Fibrosis (CleanUP IPF-BioLINCC)

  Data Access NOTE: Please refer to the &#8220;Authorized Access&#8221; section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objectives To investigate whether the addition of antimicrobial treatments improves outcomes compared to usual care alone among patients with idiopathic pulmonary fibrosis. Background Idiopathic pulmonary fibrosis (IPF) is a chronic progressive lung disease. Lung dysbiosis, characterized by increased bacterial load and/or loss of diversity, has been reported in patients with IPF and may contribute to hospitalization and death. Clinical trials investigating other chronic disorders suggest that antimicrobial therapy favorably alters the lung microbial community. The CleanUP IPF study was initiated to determine if an antimicrobial treatment reduces respiratory hospitalization or death among patients with IPF. Participants A total of 513 participants were enrolled. 254 participants were randomized to receive antimicrobials, of those 128 were randomized to receive co-trimoxazole and 126 were randomized to receive doxycycline. 259 participants were randomized to receive usual care alone. Design CleanUP IPF was a randomized, unblinded, multicenter study. Patients were randomized to receive antimicrobials in addition to usual care or usual care alone. Antimicrobials included co-trimoxazole (trimethoprim 160 mg/sulfamethoxazole 800 mg twice daily plus folic acid 5 mg daily) or doxycycline (100 mg once daily if body weight Data collected included diffusion capacity of lungs for carbon monoxide (DLCO), forced vital capacity (FVC), and occurrence of severe adverse events. Several questionnaires were administered to assess quality of life, including the impacts of shortness of breath, fatigue, and chronic cough on participants. The primary end point was time to first nonelective respiratory hospitalization or all-cause mortality. The study was terminated early due to futility. Conclusions Among adults with idiopathic pulmonary fibrosis, the addition of co-trimoxazole or doxycycline to usual care, compared with usual care alone, did not significantly improve time to nonelective respiratory hospitalization or death. Martinez FJ, Yow E, Flaherty KR, et al. Effect of Antimicrobial Therapy on Respiratory Hospitalization or Death in Adults With Idiopathic Pulmonary Fibrosis: The CleanUP-IPF Randomized Clinical Trial. JAMA. 2021;325(18):1841-1851. doi:10.1001/jama.2021.4956

  Study phs004314

• The Haemgen RBC study

  Anaemia is a major determinant of global ill-health. To refine our understanding of the genetic factors influencing red blood cell formation and function, we carried out a meta-analysis of genome-wide association studies (GWAS) for six red blood cell traits: haemoglobin (HB), mean cell haemoglobin (MCH), mean cell haemoglobin concentration (MCHC), mean cell volume (MCV), packed cell volume (PCV) and red blood cell count (RBC). We provide genome-wide association results for 62,553 people of European ancestry using up to 2,644,161 autosomal SNPs. Participants with extreme measurements (>+/-3SD from mean) were excluded on a per phenotype basis. Imputation was done using haplotypes from HapMap Phase 2. SNP associations with each phenotype were tested by linear regression using an additive genetic model. Associations were tested separately in each cohort, with principal components and other study specific factors as covariates to account of population substructure. We then carried out meta-analysis of results from the individual cohorts using z-scores weighted by square root of sample size. SNPs with MAF<1% (weighted average across cohorts) were removed, as were SNPs with weight <50% of phenotype sample size. Anaemia is a major determinant of global ill-health. To refine our understanding of the genetic factors influencing red blood cell formation and function, we carried out a meta-analysis of genome-wide association studies (GWAS) for six red blood cell traits: haemoglobin (HB), mean cell haemoglobin (MCH), mean cell haemoglobin concentration (MCHC), mean cell volume (MCV), packed cell volume (PCV) and red blood cell count (RBC). We provide genome-wide association results for 62,553 people of European ancestry using up to 2,644,161 autosomal SNPs. Participants with extreme measurements (>+/-3SD from mean) were excluded on a per phenotype basis. Imputation was done using haplotypes from HapMap Phase 2. SNP associations with each phenotype were tested by linear regression using an additive genetic model. Associations were tested separately in each cohort, with principal components and other study specific factors as covariates to account of population substructure. We then carried out meta-analysis of results from the individual cohorts using z-scores weighted by square root of sample size. SNPs with MAF<1% (weighted average across cohorts) were removed, as were SNPs with weight <50% of phenotype sample size.

  Study EGAS00000000132

• Pathology and tumor biology DAC

  Dac EGAC00001001287

• Senior Director, Grants and Contracts

  Dac EGAC00001003387

• Evolution of Chromatin Architecture and Transcriptional Regulation in Mammals

  Changes in gene expression are a critical force driving the evolution of form and function. As a result, the mechanisms by which gene expression evolves have become a subject of intense interest. A number of investigators have measured evolutionary changes in gene expression at the chromatin, mRNA, and protein levels, leading to new insights about how species evolve. However, studies of different stages in gene expression have not always been in agreement. For example, the extremely rapid rates of evolutionary changes that have been widely observed at enhancers appear to conflict with the slower rates observed in mRNA abundance. We recently completed a major comparative study in primates showing that this disparity between enhancer and mRNA evolution, in part, reflects extensive compensation at enhancers that jointly determine transcription at target genes. Likewise, related findings have demonstrated that post-transcriptional changes buffer protein abundance to relatively more common differences in mRNA expression. Together, these recent findings demonstrate that evolutionary changes affecting multiple stages of transcriptional regulation often have interdependent effects on gene expression. Here we propose to determine how stages early during transcriptional regulation work in concert, either to conserve gene expression through compensatory changes across stages, or, in rare cases, to change mRNA in ways that alter organism phenotypes. Our central hypothesis is that interactions between stages are common, especially at long evolutionary time-scales. To test this hypothesis we propose an ambitious plan to collect rich genomic data profiling distinct stages of gene expression in two cell types and three tissues from nine mammalian species. We have focused our study on several early rate-limiting steps in mRNA production, using molecular assays selected to provide orthogonal sources of information about chromatin architecture (Hi-C/Hi-ChIP), accessibility (ATAC-seq), transcription (PRO-seq), and mRNA levels (RNA-seq). This project will produce the largest resource of genomic data uniformly collected across mammals to date. We will integrate genomic data using a suite of new computational tools, which together will provide a new understanding of how distinct regulatory stages work in concert during regulatory evolution.

  Study phs002146

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• Optimizing Primary Stroke Prevention in Children with Sickle Cell Anemia (STOP II)

  The STOP II trial evaluated whether prophylactic transfusion in patients with sickle cell disease and high risk of stroke can be safely halted after 30 months of treatment during which patients became low risk for stroke.Stroke causes substantial morbidity in children with sickle cell disease. To prevent first strokes, the Stroke Prevention Trial in Sickle Cell Anemia (STOP) used prophylactic transfusions in children who were identified by transcranial Doppler (TCD) ultrasonography as being at high risk for stroke. This strategy reduced the incidence of stroke among such children from 10% per year to less than 1% per year, leading to recommendations for TCD screening and prophylactic transfusion for children with abnormal velocities on ultrasonography. Despite the reduced risk of stroke, long-term use of transfusions can cause adverse side effects, such as iron overload or alloimmunization. However, cessation of transfusions is associated with recurrence of stroke, and at the time of the STOP II trial, there were no clinical or laboratory indicators to guide the duration of prophylaxis. Therefore the STOP II trial was initiated to determine whether transfusions could be limited by monitoring patients with TCD examinations after transfusions were halted and resuming transfusions if the examination indicated a high risk of stroke.The trial was halted for safety concerns after 79 of a planned 100 children were randomized. Discontinuation of transfusion for the prevention of stroke in children with sickle cell disease resulted in a high rate of reversion to abnormal blood-flow velocities on Doppler studies and stroke incidence.Instructions for requesting individual-level data are available on BioData Catalyst at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BioData Catalyst. For questions about availability, you may contact the BioData Catalyst team at https://biodatacatalyst.nhlbi.nih.gov/contact.

  Study phs002386

• Genome-wide Association Study of Myasthenia Gravis

  The purpose of this project was to conduct a genome-wide associate study to search for the genetic factors that predispose to myasthenia gravis. The rationale for this study lies in the fact that, although the immunological and physiological processes affecting the neuromuscular junctions of myasthenia gravis patients are well understood, the spectrum of genetic factors that predispose to myasthenia gravis and influence its disease manifestations are not well known. Identification of the myasthenia gravis-related genes will shed light on the fundamental cellular events underlying myasthenia gravis, and will provide focus for research aimed at developing therapies that alter the natural course of the disease. A consortium of fourteen institutions in North America collected DNA samples from 1028 people diagnosed with autoimmune myasthenia gravis. Relevant clinical data have been collected for each patient, including age of onset, severity of disease, response to drug therapy, personal and family history of other autoimmune diseases. Genotyping of the case cohort was performed in the Laboratory of Neurogenetics, National Institute on Aging, National Institutes of Health, Bethesda, MD. Genotyping of the case cohort was performed using the HumanOmniExpress-12v1_C SNP array manufactured by Illumina Inc. For the control cohort, we downloaded genotype data from dbGAP (accession phs000196.v2.p1) for 1,998 US neurologically normal individuals. The control cohort had been previously genotyped at the Center for Inherited Disease Research at Johns Hopkins University on HumanOmni1-Quad version 1.0B beadchips (Illumina) as part of the NeuroGenetics Research Consortium GWAS of Parkinson&#39;s disease. Analyses were confined to the 677,673 autosomal SNPs that were common to both chips. Of the 1028 samples which were genotyped, 21 samples were excluded due to mismatched genders, 9 were excluded due to low genotype call rate, 5 samples were excluded as duplicates, and 25 samples were excluded as ethnic outliers. The remaining 972 samples were used in analysis.

  Study phs000726