Search Results - EGA European Genome-Phenome Archive

A Genome-Wide Association Study in Patients Experiencing Musculoskeletal Adverse Events on NCIC CTG Trial MA.27 Evaluating Aromatase Inhibitors as Adjuvant Therapy in Early Breast Cancer. A Collaboration Between the NIH Pharmacogenetics Research Network and the RIKEN Yokohama Institute Center for Genomic Medicine.

Source of Patients The source of the patients for this genome-wide case control study was MA.27, which was conducted as a multi-cooperative group effort under the auspices of the NCI Breast Cancer Intergroup of North America. The NCIC Clinical Trials Group (CTG) serves as the coordinating group, with participation by the NCI-sponsored North Central Cancer Treatment Group, Eastern Cooperative Oncology Group (ECOG), Southwest Oncology Group, and Cancer and Leukemia Group B (CALGB). MA.27 involved postmenopausal women with histologically confirmed and completely resected invasive breast cancer with surgical margins clear of invasive carcinoma and DCIS in the following TMN categories (AJCC Version 6): pT1, pT2, pT3; pNx, pN0, pN1, pN2, pN3 (only when the sole basis is presence of 10 or more involved axillary nodes); MO. The primary tumor must have been ER and/or progesterone receptor positive. Patients were stratified by lymph node status at diagnosis, prior adjuvant chemotherapy, and trastuzumab use and were randomized to 5 years of adjuvant therapy with anastrozole or exemestane. The trial was activated on May 26, 2003, and reached its accrual objectives on July 31, 2008, after the randomization of 6827 North American patients, with the majority (79%) providing DNA and consent for genetic testing. Non-North American patients were also entered by the International Breast Cancer Study Group but they did not contribute DNA. From 2003 to December 21, 2004, patients also underwent a second randomization to celecoxib 400 mg twice daily or placebo but, after the entry of 1,622 patients, this treatment was discontinued because of reports of increased cardiovascular risk associated with celecoxib. Case Definition for Musculoskeletal Adverse Events Cases were defined to have had at least one of the following six MSAE): 1. pain - joint, 2. pain - muscle, 3. pain - bone, 4. arthritis, 5. joint - function, 6. musculoskeletal - other. Cases were required to have at least grade 3 toxicity, according to the NCI Common Terminology Criteria for Adverse Events v3.0, or go off treatment for any grade of the six MSAEs; and were required to have had an MSAE within the first two years (i.e., a MSAE occurring after 2 years was not be considered a case). Subjects were excluded from the case group who met the case definition while on celecoxib or in the three months after stopping celecoxib but subjects were allowed to be cases if they developed their first MSAE more than three months after stopping celecoxib. Study Design The design was a nested matched case-control study with two controls selected for each case. Random matching from the potential control group (i.e., risk-set sampling such that controls had at least the same length of followup as the timing of the case event) was done by matching the case on the following factors: 1. treatment arm (exemestane vs. anastrozole, blinded), 2. prior adjuvant chemotherapy (yes vs. no), 3. age at start of treatment (+/- 5 years), 4. Celecoxib allocation (yes vs. no). Attempts were made to exactly match each case with two controls according to the above criteria. If, however, controls could not be exactly matched, "close" matching was used to define a distance between each case and all potential controls in an optimal matching algorithm. Race is a potential confounding factor, and 94% of the MA.27 population is Caucasian, 3% are Black, 1% Asian, 1% American Indian, and 1% are of unknown race. Because there are so few non-Caucasian participants, was restricted to only Caucasians. Following identification of cases and controls, the list was sent to the CALGB Pathology Coordinating Office (PCO) at Ohio State University Medical Center for plating of the samples. Other patient factors that might influence the association of SNP genotypes with a MSAE, either as confounding factors or as effect modifiers, were included as investigational covariates. These include 1. body mass index (BMI), 2. bisphosphonate use, 3. fractures in past 10 years, 4. baseline ECOG performance status, 5. prior hormone replacement therapy, 6. prior adjuvant radiotherapy, and 7. prior taxane treatment. An Honest Broker Process was utilized to ensure patient confidentiality. Genotype Assays and Quality Control A GWAS was performed with the Illumina Human610-Quad at the RIKEN Center for Genomic Medicine. The DNA for all of the samples were adjusted to a concentration of 50 to 100 ng/µL in a final volume of 50 µL. The 96-well plates were designed to have a unique distribution pattern with x duplicates per plate to evaluate genotype concordance. Samples with <98% call rate were removed from analyses. SNPs with ambiguous call will be excluded using the following criteria: 1. low signal intensity of each allele, 2. low cluster separation score, 3. SNP call rate <0.98, 4. SNPs with Hardy Weinberg Equilibrium p-value <0.001 were excluded. X-chromosome SNPs were used to validate female sex and quality control measures were examined across the different submitting centers. For all pairs of subjects, the percentage of matching genotypes were computed to screen for unexpected duplicate samples. All SNPs found to be associated with MSAE were subjected to visual inspection of the cluster plots to verify that the genotype clustering was adequate.

Study phs000210

National Sleep Research Resource (NSRR): Cleveland Family Study (CFS)

The Cleveland Family Study (CFS) is a family-based study of sleep apnea, consisting of 2,284 individuals (46% African American) from 361 families studied on up to 4 occasions over a period of 16 years. The study began in 1990 with the initial aims of quantifying the familial aggregation of sleep apnea. National Institutes of Health (NIH) renewals provided expansion of the original cohort, including increased minority recruitment, and longitudinal follow-up, with the last exam occurring in February 2006. The CFS was designed to provide fundamental epidemiological data on risk factors for sleep disordered breathing (SDB). The sample was selected by identifying affected probands who had laboratory diagnosed obstructive sleep apnea. All first-degree relatives, spouses and available second-degree relatives of affected probands were studied. In addition, during the first 5 study years, neighborhood control families were identified through a neighborhood proband, and his/her spouses and first-degree relatives. Each exam, occurring at approximately 4-year intervals, included new enrollment as well as follow up exams for previously enrolled subjects. For the first three visits, data, including an overnight sleep study, were collected in participants' homes while the last visit occurred in a general clinical research center (GCRC). Phenotypic characterization of the entire cohort included overnight sleep apnea studies, blood pressure, spirometry, anthropometry and questionnaires. Currently, data of 710 individuals are available for use through BioData Catalyst (with genotype data available through dbGaP).The National Sleep Research Resource (NSRR) is a NIH-supported sleep data repository that offers free access to large collections of de-identified physiological signals and related clinical data from a large range of cohort studies, clinical trials and other data sources from children and adults, including healthy individuals from the community and individuals with known sleep or other health disorders. The goals of NSRR are to facilitate rigorous research that requires access to large or more diverse data sets, including raw physiological signals, to promote a better understanding of risk factors for sleep and circadian disorders and/or the impact of sleep disturbances on health-related outcomes. Data from over 15 data sources and more than 40,000 individual sleep studies, many linked to dozens if not hundreds of clinical data elements, are available (as of Feb. 2022). Query tools are available to identify variables of interest, and their meta-data and provenance.

Study phs002715

Alzheimer's Disease Sequencing Project (ADSP)

NOTICE OF CHANGE IN LOCATION FOR ALZHEIMER'S DISEASE SEQUENCING PROJECT (ADSP) GENETIC AND PHENOTYPIC DATA: ADSP whole exome and whole genome sequence data that are shared through dbGaP were mapped to the Genome Reference Consortium human genome GRCh37 (build 37). These data are from the Discovery Phase of the project (described below) and will continue to be available at this site. Please see the ADSP Design page for the complete study description. All data that are mapped to GRCh38 (hg38) are being shared through the NIA Genetics of Alzheimer's Disease Data Storage Site (NIAGADS) Data Sharing Service (DSS). For instructions on how access the ADSP Build 38 data that are shared through NIAGADS DSS, visit the Application Instructions page. STUDY DESCRIPTION FOR dbGaP BUILD 37 ADSP DATA: The overarching goals of the Alzheimer's Disease Sequencing Project (ADSP) are to: (1) identify new genomic variants contributing to increased risk of developing Alzheimer's Disease (AD), (2) identify new genomic variants contributing to protection against developing AD, and (3) provide insight as to why individuals with known risk factor variants escape from developing AD. These factors will be studied in multi-ethnic populations in order to identify new pathways for disease prevention. Such a study of human genomic variation and its relationship to health and disease requires examination of a large number of study participants and needs to capture information about common and rare variants (both single nucleotide and copy number) in well phenotyped individuals. Using existing samples from NIH funded and other studies, three NHGRI funded Large Scale Sequencing and Analysis Centers (LSAC) - Broad, Baylor, and Washington University - produced the DNA sequence data. Variant call data are being made available to the scientific community through NIH-approved data repositories. Statistical analysis of the sequence data is anticipated to identify new genetic risk and protective factors. The ADSP will conduct and facilitate analysis of sequence data to extend previous discoveries that may ultimately result in new directions for AD therapeutics. Analysis of ADSP data will be done in two phases. The Discovery Phase analysis (2014-2018) is funded under PAR-12-183. The entire Discovery dataset contains whole-genome sequencing data on 584 subjects from 113 families, and pedigree data for > 4000 subjects; whole exome sequencing data on 5096 cases 4965 controls; and whole exome sequence data on an additional 853 (682 Cases [510 Non-Hispanic, 172 Hispanic]), and 171 Hispanic Control subjects from families that are multiply affected with AD. The Replication Phase (2016-2021) analysis will be funded under RFA-AG-16-001 and RFA-AG-16-002 and is expected to include a combination of genotyping and sequencing approaches on at least 30,000 subjects. Targeted sequencing will be done by the LSACs. GRCh37 Data Releases The first ADSP data release occurred on November 25, 2013. It included the whole-genome sequencing data in BAM file format on 410 individuals. The second ADSP data release occurred on March 31, 2014, and included the whole-genome sequencing data in BAM file format for an additional 168 individuals. The third ADSP data release occurred on November 03, 2014 and included whole-exome sequencing data in BAM file format for 10,939 individuals. The fourth ADSP data release occurred on February 13, 2015 and included revised ethnic data for subjects with whole-exome sequencing data. The fifth ADSP data release occurred on July 13, 2015 and included whole-genome genotypes and updated phenotypes as well as changes to pedigree structures and sample IDs. The sixth ADSP data release occurred on December 8, 2015, and included whole-exome genotypes and updated phenotypes as well as changes to subject IDs. This seventh ADSP data release on April 12, 2016 includes: (1) WES and WGS SNV VCF files (2) WES and WGS Indel PLINK files ADSP Data Available through dbGaP: ADSP - Whole Genome Sequencing ADSP - Whole Exome Sequencing Comments DNA-Seq (BAM) n=578 n=10913 Sequence data available (plus n=38 replications w/out genotype data) Concordant SNV Genotypes (PLINK format) N/A n=10913 QC'ed genotypes that are concordant between the Atlas (Baylor's) and GATK (Broad's) calling pipelines (a subset of the consensus genotype set) Consensus Genotypes (PLINK and VCF format) n=578 n=10913 QC'ed genotypes that are concordant between Atlas and GATK pipelines as well as those that that were called uniquely by Atlas or GATK Concordant Indel Genotypes (PLINK format) n=578 n=10913 QC'ed genotypes that are concordant between the Atlas and GATK calling pipelines Phenotype Data n=4735 n=10913 Data of n=53 phenotype variables available (plus administrative data), including APOE genotype. WGS phenotypes include data of connecting family members. Please use the release notes provided by dbGaP to obtain detailed information about study release updates. The ADSP data portal provides a customized interface for users to quickly identify and retrieve files by covariates, phenotypes, and data properties such as sequencing facility or coverage. For more information about the ADSP study and the data portal, please visit https://www.niagads.org/adsp/.

Study phs000572

Out with the Java, in with the Python - new EGA data download client unveiled

We will shortly be deprecating the Java-based download client also known as API V2. The Java client began its life at the back end of 2014, and during its time has seen many developments that have served our users well. During its tenure, the Java client enabled distribution of over 6.5 million files totalling nearly 15 petabytes of data to researchers around the globe. Recent increases in genomic and phenotypic data file sizes, the number of datasets archived in the EGA, the number of users downloading data, and the diversity of download locations has meant that at times the Java client struggled to distribute data efficiently. In response, our team of developers have built a new download client with more robust features and better functionality and reliability. Enter stage left our shiny new API V3.1! The new API V3.1 will replace both API V2 and API V3. The download client for the new API V3.1 is written in Python, and the code is openly available on Github. This Python client makes https calls to the EGA AAI (https://ega.ebi.ac.uk:8443/) and to the EGA Data API (https://ega.ebi.ac.uk:8052), both of which must be accessible from the client location. In addition to general updates to improve performance, the API V3.1 has three new features enhancing the EGA distributions services. First, requested data are now downloaded over secure https connections rather than http, meaning that data can be delivered unencrypted. Instead of separately requesting, downloading, and decrypting data using the Java client, data can now be requested and downloaded using a single command without the need for decrypting. The API V3.1 also automatically verifies each file’s unencrypted md5 after download to ensure the file has downloaded correctly. Second, the new API supports segmenting and automatic resuming. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the new resume feature, downloads - both segmented and continuous stream - will automatically resume if they encounter any errors or the connection is interrupted. These features result in both a faster and more reliable download experience. Finally, the new API V3.1 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file saving both time and storage space. The new features of the Python-based API V3.1 represent significant improvements in security, speed, reliability, and flexibility that are sure to provide a better data download experience. To take full advantage of these features, users must update to Python 3.X. Considering the changes in the data structures with the new API, the upgrade to a new version of the Python client is also mandatory. Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 -U We are excited for users to try out the new features and take advantage of the multifariously growing EGA distribution services for human biomedical omics data. If you have any questions or feedback, please email the EGA Helpdesk team. We'd love to hear from you!

Blog new-ega-data-download-client

Discover Cancer Image Europe, the first release of the EUCAIM platform to fuel cancer research and data sharing

The EUCAIM consortium and the European Commission have announced the release of Cancer Image Europe, a platform to fuel collaborative innovation and data sharing across Europe. This constitutes a major milestone in EUCAIM's development and an exciting step towards achieving the project's vision and goals. The platform aims to accelerate the pace of AI development and other data-intensive cancer research activities, constituting the basis for a fully-fledged infrastructure for sharing, reusing, and exploiting cancer imaging data, especially using AI techniques. A platform paving the way for the future of cancer diagnosis and treatment Cancer Image Europe brings benefits to researchers, clinicians, and AI innovators across Europe as it addresses the fragmentation of existing cancer image repositories. The platform gathers a public catalogue of cancer imaging datasets from the repositories of the EU-funded AI for Health Imaging projects. A distributed Atlas of Cancer Imaging with over 60 million anonymised cancer image data from over 100,000 patients will be established as part of future updates. The first version of Cancer Image Europe also includes a public catalogue of cancer imaging datasets, a federated searching tool to understand the information available in the federated providers, and full integration with Life Science Login. Moreover, it reuses and adds value to key components of EU-funded research projects and infrastructure in the field of cancer. The Public Catalogue When we talk about data re-use, data discovery is key. The EUCAIM public catalogue is the result of a systematic and collaborative process to which the EGA-CRG has actively contributed. This browsing interface gathers the metadata of the available cancer imaging datasets. This descriptive information will help researchers in their data retrieval. Our contribution to the Public Catalogue comes from our experience gained in the deployment of our federated network, the Federated EGA (FEGA), and as partners in projects such as EuCanImage (AI4HI initiative), in which we worked on the definition of common data models, ontologies and data standards. The EUCAIM Project EUCAIM is a cornerstone of the European Commission-initiated European Cancer Imaging Initiative, a flagship of the Europe's Beating Cancer Plan, which aims to foster innovation and deployment of digital technologies in cancer treatment and care, to achieve more precise and faster clinical decision-making, diagnostics, treatments, and predictive medicine for cancer patients. For more information about the first release of the Cancer Image Europe platform and the EUCAIM project, please visit cancerimage.eu.

Blog discover-cancer-image-europe

NHLBI TOPMed: The Cleveland Family Study (CFS)

The Cleveland Family Study (CFS) is one cohort involved in the WGS project. The CFS was designed to provide fundamental epidemiological data on genetic and non-genetic risk factors for sleep disordered breathing (SDB). In brief, the CFS is a family-based study that enrolled a total of 2284 individuals from 361 families between 1990 and 2006. The sample was selected by identifying affected probands who had laboratory diagnosed obstructive sleep apnea. All first degree relatives, spouses and available second degree relatives of affected probands were studied. In addition, during the first 5 study years, neighborhood control families were identified through a neighborhood proband, and his/her spouses and first degree relatives. Each exam, occurring at approximately 4 year intervals, included new enrollment as well as follow up exams for previously enrolled subjects. For the first three visits, data, including an overnight sleep study, were collected in the participants' homes while the last visit occurred in a general clinical research center (GCRC). Phenotypic characterization of the entire cohort included overnight sleep apnea studies, blood pressure, spirometry, anthropometry and questionnaires. The GCRC exam (n=735 selected individuals) included more comprehensive phenotype data on a focused subsample of the larger cohort, to permit linking SDB phenotypes with cardio-metabolic phenotypes, with an interest in identifying genetic loci that are associated with these related phenotypes. In this last round of data collection, a subset of 735 individuals was selected based on expected genetic informativity by choosing pedigrees where siblings had extremes of the apnea hypopnea index (AHI). Participants underwent detailed phenotyping including laboratory polysomnography (PSG), ECG, spirometry, nasal and oral acoustic reflectometry, vigilance testing, and blood and urine collection before and after sleep and after an oral glucose tolerance test. A wide range of biochemical measures of inflammation and metabolism were assayed by a Core Laboratory at the University of Vermont. 994 individuals were sequenced as part of TOPMed Phase 1, including 507 African-Americans and 487 European-Americans. Among the sequenced individuals, 156 were probands with diagnosed sleep apnea, an additional 706 were members of families with probands, and 132 were from neighborhood control families. 298 individuals were sequenced as part of TOPMed Phase 3.5, including 169 African-Americans and 129 European-Americans. Among the newly sequenced individuals, 33 were probands with diagnosed sleep apnea, an additional 214 were members of families with probands, and 51 were from neighborhood control families. Please note: Phenotype and pedigree data are available through "NHLBI Cleveland Family Study (CFS) Candidate Gene Association Resource (CARe)", phs000284.

Study phs000954

Efficacy of a Therapeutic Treatment Trial in Angelman Syndrome

This study has been designed to evaluate the possible therapeutic benefits of L-5-methyltetrahydrofolate (Metafolin), vitamin B12, creatine and betaine in children with Angelman Syndrome (AS). This study is based on the hypotheses 1) that dietary manipulation may increase global DNA methylation; 2) that increased methylation of the paternal chromosome in AS participants may increase expression of the Angelman gene causing clinical benefit; and 3) that dietary interventions with Metafolin in conjunction with creatine, betaine, and vitamin B12 would represent little risk, but some chance for benefit. The dietary regimen is felt to be quite benign and safe. The clinical response will be measured by recording: changes in seizure activity, changes in communication skills, changes in developmental skills and changes in behavioral patterns as indicated by formal developmental assessments and clinical evaluations. We will assess the progress of the participants by monitoring their changes from baseline throughout their participation in the study and measure their improvement in particular in the developmental parameters. As a secondary aim, we plan to measure the biochemical response to these compounds by obtaining levels of homocysteine, methionine, S-adenosyl-methionine (SAM), and S-adenosyl-homocysteine (SAH). The molecular response will be measured by global DNA methylation analysis. As an exploratory aim, we hope to use control data we have previously obtained from a double blind placebo-controlled trial done in the past using betaine and folic acid to compare the development of those children who have and those who have not received medications. More specifically, we wish to compare differences in the rate of development for those children who have never received study medications (from the first trial) with those who have received medications from the present trial. Developmental parameters used in the previous trial will be consistent with those used in the present trial in order to permit these comparisons. The previous trial was conducted at Baylor College of Medicine, Rady San Diego Children's Hospital and Boston Children's Hospital whereas a group of AS participants received folic acid and betaine or placebo in a randomized double-blind basis. All the participants for the study will include patients who have a documented molecular diagnosis of AS. The participants will be seen at Baylor College of Medicine, Rady Children's Hospital of San Diego, Boston Children's Hospital and the Greenwood Genetics Center at 0 months and at 12 months for follow-up. Clinical and relevant historical data will be collected during the clinical visit and examination and also by reviewing medical and laboratory records. This information will then be entered into a HIPAA compliant clinical research database.

Study phs000701

PyEGA3 download client

PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

Documentation access/download/files/pyega3

Atherosclerosis Risk in Communities Study (ARIC-BioLINCC)

Data Access NOTE:Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. At present, the ARIC sIRB has determined that ARIC data cannot be shared with for-profit entities.Related Studies Other ARIC data available include: Imaging studies (ARIC-Imaging), Genetics and genomics (ARIC, phs000280.v8.p2), Collaborative Cohort of Cohorts for COVID-19 Research (C4R): ARIC (phs002988.v1.p1), and as a component of the Sleep Heart Health Study (SHHS-BioLINCC, phs003637.v1.p1). Available Data Data available for request include ARIC v1-v8 examination cycles, collated annual follow-up communication data for contact years 2-32, and follow-up for mortality, heart disease, and stroke events through 2019. Also included are data from ancillary studies. Objectives The objectives of ARIC are to: 1) investigate associations of factors, including those not previously measured in cohort studies, with prevalence of atherosclerosis and incidence of CHD, clinical stroke and other cardiovascular diseases; and 2) measure cardiovascular disease occurrence and trends and relate these to community levels of, and changes in, risk factors, medical care and atherosclerosis. Background At the time of project initiation, the NHLBI had long recognized the need for longitudinal studies to identify the biochemical and physiological markers and specific environmental factors which place individuals at high risk for the major atherosclerosis diseases. The development of reliable ultrasound examination of peripheral arteries enhanced the expected benefit of such studies. Community surveillance planning began for ARIC in response to recommendations of the 1978 NHLBI Workshop on the Decline in CHD Mortality and has been extended in its purpose to evaluate the large geographic differences in U.S. mortality. Participants Black and white men and women, age 45-64 at entry; sample size: 15,792. Design ARIC is a large-scale, long-term prospective study that measures associations of established and suspected coronary heart disease risk factors with both atherosclerosis and new CHD events in men and women from four geographically diverse communities. The project has two components: community surveillance of morbidity and mortality; and repeated examinations of a representative cohort of men and women in each community. The community surveillance involves abstracting hospital records and death certificates and investigating out-of-hospital deaths. The representative cohorts include approximately 4,000 persons from each community. Community surveillance data includes detailed hospital record abstraction, ECG tracings, and event adjudication. Data from out-of-hospital events in the community include physician, informant, and coroner questionnaires as well as death certificate data and event adjudication. Community surveillance ended in 2014.Cohort participants were examined four times at three year intervals between 1987 and 1998, and have been continuously contacted annually to update their medical histories. Atherosclerosis was measured by carotid ultrasonography. Risk factors studied include: blood lipids, lipoprotein cholesterols, and apolipoproteins; plasma hemostatic factors; blood chemistries and hematology; sitting, supine and standing blood pressures; anthropometry; fasting blood glucose and insulin levels; ECG findings; cigarette and alcohol use; physical activity levels; dietary aspects; and family history. Clinic visits were restarted in 2011 with ARIC visit 5.

Study phs003738

Biological Determinants of Peritoneal Dialysis Outcomes

Peritoneal Dialysis (PD) is a technique for treating kidney failure where fluid is instilled into the body's peritoneal cavity. Fluid and solutes travel across the peritoneum, and this is critical to successful PD. Studies have shown that certain demographic and clinical variables explain a small part of the variability in baseline peritoneal solute transfer rate and water transfer function across the peritoneum. This study sought to identify the common genetic variants associated with the baseline peritoneal function in patients starting treatment with PD and change in function upon treatment with PD. This study has two specific aims: Aim 1: To identify and validate genetic loci that influence the peritoneal solute transfer rate (PSTR) at start of PD. Aim 2: To identify and validate genetic loci in pre-specified biologic pathways with change in peritoneal ultrafiltration capacity. This study incorporates data from participants' peritoneal solute transfer rate in their first ever peritoneal equilibrium test (PET) and changes in the transfer of water across the peritoneal membrane over time in a sub-group of participants, demographic information, and results from laboratory analysis of DNA, blood, and dialysate. This study comprises patient populations from pre-existing biorepositories in Europe, and prospectively enrolled participants in United States, Canada, United Kingdom, and Australia. Clinical data related to the participants' peritoneal solute transfer rate from their first ever Peritoneal Equilibrium Test (PET), demographic information, and change in ultrafiltration capacity over time, are correlated with various genetic markers of interest. For individuals enrolled prospectively, blood and dialysate were collected at the first study visit. Annually, subjects either underwent a PET as standard of care or perform an additional 4-hour dwell as part of the study. These subsequent measures were utilized to determine change in ultrafiltration capacity over time. Inclusion criteria included adults over the age of 20 who are able to provide consent and had a record of a PET within 6 months of starting PD. Subjects with missing outcome data and that did not pass genotyping QC were excluded. Genotyping was performed in two batches using the Illumina InfiniumOmni2-5-8v1-3_A1 array with 2,372,784 single nucleotide variants (SNVs) in the first batch (n=1957). The second genotyping batch (n=1053) was on the InfiniumOmni2-5-8v1-4_A1 array with 2,382,209 SNVs. Imputation was performed using the Michigan Imputation Server and the HRC1.1 genotype reference. The Institutional Review Board of the University of Washington has “dbGaP-certified” the consent forms used to enroll participants in Australia, Canada, and United States and the genotype-phenotype data from the participants (n=827) deposited in the public repository. Furthermore, it has been determined that under the EU-GDPR regulations, depositing data of participants enrolled in UK, Belgium, and Sweden (n=2,023) into dbGaP “serves no lawful purpose” as the consent form used for enrolling participants did not obtain explicit permission for depositing data in a public repository.

Study phs002996

11936 results for "fc 26 switch coins Visit Buyfc26coins.com for latest FC 26 coins news..NhK9"

in 16.62 milliseconds.