14313 results for ""Pennsylvania+German"+ACS+study+'Socius'+open+access"

in 13.74 milliseconds.

• Blood Somatic Mutations in TCGA Donors Suffering from Solid Tumors

  Blood somatic mutations identified across 8,530 solid tumor patients in TCGA cohort. We reasoned that low-coverage whole-genome sequencing of blood samples routinely carried out in cancer genomics projects may be repurposed to detect clonal hematopoiesis (CH). Thus, inspired by a previous approach to identify early mutations in the development of the hematopoietic system, we implemented a pipeline to systematically carry out this "reverse" somatic mutation calling on the paired blood/tumor samples. Blood somatic mutations were called using a 'reverse' approach, in which the tumor sample taken from each patient was used as control of their germline genome. Blood somatic mutations are thus detected as variants in the blood (with respect to the human reference genome) that are absent in the tumor sample. The variant calling was carried out in our in house cluster on downloaded blood/tumor BAM files. The matched blood and tumoral BAM files -- masked and deduplicated using GATK -- of 8,530 whole-exome patients were obtained as described above. The variant calling was carried out using Strelka2 (employing default parameters) with the blood sample as the tumoral input and the tumor sample as control (reverse calling). All variants with two or more supporting reads matching the caller PASS filter and with VAF<0.5 were kept. Mutations in lowly mappable regions as defined by the DUST algorithm (k=30) and UMAP68 (36-kmers) were excluded. Contiguous variants were merged into double-base substitutions. Variants with greater frequency across the cohorts than the DNMT3A R882H or JAK2 V617F hotspot in a cohort-specific Panel of Normals and in gnomAD v2.1 were removed. This was equivalent to discarding variants present in these datasets with an allele frequency greater than 0.008 in PoN TCGA and 0.0003 in gnomAD v2.1. Additionally, common SNPs as defined by the dbSNP 151 Common UCSC track and dbSNP were excluded. Mutations within segmental duplications, simple repeats and masked regions as defined in UCSC tracks were also removed. Finally, samples with the mutation count above the 97.5 percentile of the mutation burden across the cohort were deemed unreliable and excluded for further analyses. We call the set of variants obtained after the application of these filters the full set. A more conservative subset of somatic mutations was generated from the full set of blood somatic mutations. To this end, we applied MosaicForecast, a software designed to phase mutations to polymorphisms with the aim of identifying somatic mutations in a small number of cells and also predict mosaicism for the unphased ones with a random forest classifier. As a result, we obtained a subset of mosaic-phased mutations, and a subset of mutations likely to be somatic (mosaic set).In order to obtain access to this study, please first obtain access to TCGA study (phs000178).

  Study phs002867

• RNA-Seq Profiles from the CheckMate-577 Clinical Trial

  The dataset contains RNAseq profiles of 386 patients from the CheckMate-577 (CA209-577) clinical trial whose ICF allows data deposition into a public repository. The Allprep DNA/RNA FFPE kit was used to simultaneously purify genomic DNA and total RNA from formalin-fixed, paraffin embedded (FFPE) tissue sections. RNA was analyzed using the Illumina TruSeq RNA Access method for library preparation, followed by sequencing on the Illumina NovaSeq platform with a 50bp paired-end strategy and a target read depth of 50M per sample. Fastq files are included.

  Dataset EGAD50000002394

• Query AML data

  Shallow targeted sequencing with 462 mRNA and 97 antibodies of AML patient’s bone marrow mononuclear cells from iliac crest aspirations from. Please note raw and integrated gene expression data, cell type annotation, metadata and dimensionality reduction are available as Seurat v3 objects through figshare. Access link is https://doi.org/10.6084/m9.figshare.14780127.v1 AMLQ4_SMK1 AML314 male AMLQ1_SMK2 AML116 female AMLQ3_SMK3 AML127 female AMLQ6_SMK4 AML183 male AMLQ2_SMK5 AML327 female AMLQ5_SMK6 AML334 male APLQ5_SMK7 APL124 male APLQ3_SMK8 APL142 male APLQ6_SMK9 APL218 female APLQ4_SMK10 APL147 male APLQ2_SMK11 APL223 female APLQ1_SMK12 APL224 female

  Dataset EGAD00001008185

• UNITO_Molpheno_Closed

  This dataset contains Whole Genome Sequencing, RNA-sequencing and ATAC-sequencing data obtained from PBMCs derived from blood samples of one patient with complex genomic rearrangements and the biological parents. The patient has multiple congenital anomalies and delayed development. Data access is closed.

  Dataset EGAD00001004863

• UMCU Molpheno Closed

  This dataset contains Whole Genome Sequencing and, if available, RNA-sequencing and/or ATAC-sequencing data obtained from PBMCs derived from blood samples of two patients with intellectual disability and/or multiple congenital anomalies and eight parents included in the University Medical Center Utrecht (The Netherlands). Data access is closed.

  Dataset EGAD00001004864

• Framingham Heart Study-Cohort (FHS-Cohort) - 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. Related Studies Other Framingham data available include: Imaging studies (Framingham Heart Study-Cohort (FHS-Cohort)-Imaging, phs003593), Genetics and genomics (Framingham Cohort, phs000007), Collaborative Cohort of Cohorts for COVID-19 Research (C4R): (Framingham Heart Study, phs002911), and as a component of the Sleep Heart Health Study (SHHS-BioLINCC, phs003637). Available Data Original cohort: data now include examination data from the first 32 clinical exams, selected ancillary data, and event follow-up through 2018. Offspring/Omni1 cohort: Data available include Framingham Offspring examination data from the first 9 clinical exams and selected ancillary data and event follow-up through 2019. Also included are the first 4 exams from the OMNI 1 cohort. Third Generation/Omni2/New Offspring Cohort: Data available include Framingham Generation 3 examination data from the first 3 clinical exams, selected ancillary data and event follow-up through 2019. Also included are the OMNI 2 and New Offspring (NOS) cohorts. A genetic pedigree is not provided for the Framingham phenotype only data. Objectives The objectives of the Framingham Study are to study the incidence and prevalence of cardiovascular disease (CVD) and its risk factors, trends in CVD incidence and its risk factors over time, and familial patterns of CVD and risk factors. Other important objectives include the estimation of incidence rates of disease and description of the natural history of cardiovascular disease, including the sequence of clinical signs and systems that precede the clinically recognizable syndrome and the consequences and course of clinically manifest disease. Background Original cohort: The original cohort of the Framingham Study began in 1948 under the U.S. Public Health Service and was transferred under the direct operations of the new National Heart Institute, NIH, in 1949. Participants were sampled from Framingham, Massachusetts, including both men and women. This was the first prospective study of cardiovascular disease and identified the concept of risk factors and their joint effects. Offspring/Omni1 cohort: With the aging of the Framingham cohort and with interest in familiar aggregation and heritability, a new cohort consisting of the offspring of the original cohort was sampled. Spouses of offspring were also included. This new sample, began enrollment in 1971 and constituted a second generation of participants, permitting new assessment of risk factors and outcomes, and provided a resource for the genetic analyses which were yet to come. The Offspring participants have had repeated examinations, though at typically longer intervals than the original cohort. Third Generation/Omni2/New Offspring Cohort: Thirty-one years after enrollment began for the second generation of the Framingham Heart Study (Framingham Offspring Study), Framingham investigators began enrolling adults with at least one parent enrolled in the Offspring study into the Framingham Generation 3 cohort. The addition of the third generation was expected to facilitate investigation of secular trends in risk factors and indicators of health and disease within families, to enhance statistical power to detect genetic and environmental determinants of complex diseases, and to clarify how subclinical cardiovascular disease predicts occurrence of overt clinical events. Participants Original cohort: At entry to the study in 1948-1952, the study recruited 5,209 men and women, ages 28-62 years, living in Framingham, MA. Offspring/Omni1 cohort: 5,124 men and women, ages 5-70 years at entry consisting of offspring of the original Framingham cohort (and spouses of the offspring). In 1994, the Omni Cohort 1 enrolled 507 men and women of African-American, Hispanic, Asian, Indian, Pacific Islander and Native American origins, who at the time of enrollment were residents of Framingham and the surrounding towns. Third Generation/Omni2/New Offspring Cohort: 4095 men and women, almost all who self reported their ethnicity as white, ages 19+ years at entry, with at least one parent in the Framingham Offspring study, participated in the Gen III cohort. The New Offspring Cohort enrolled spouses of Offspring participants that were not otherwise enrolled and had at least two biological children participating in Gen III. 103 New Offspring Spouses (47 men and 56 women) participated. The OMNI 2 cohort enrolled additional ethnically diverse participants, including many individuals related to the participants of Omni Cohort 1 and also individuals unrelated to Omni Cohort 1 members for a total of 410 new participants. Design The cardiovascular disease conditions under investigation include coronary heart disease (angina pectoris, myocardial infarction, coronary insufficiency and sudden and non-sudden death), stroke, hypertension, peripheral arterial disease and congestive heart failure. Original cohort: The Framingham Study is a longitudinal investigation of constitutional and environmental factors influencing the development of CVD in men and women. Examination of participants has taken place every two years and the cohort has been followed for morbidity and mortality over that time period. Offspring/Omni1 cohort: By 1975, a sample of 5,124 men and women, consisting of offspring of the original Framingham cohort (and spouses of the offspring) had participated in the study. Additional studies of these subjects have continued under research contracts. Third Generation/Omni2/New Offspring Cohort: The children of Offspring Cohort participants were initially identified who would be 20 years of age or older by the end of the enrollment period. A higher priority for recruitment was assigned to individuals who belonged to large extended families, in order to complement phenotypic and genotypic information already obtained from prior generations. The baseline examination was begun in 2002 and completed in 2005.

  Study phs003594

• SweGen genetic variation from the Swedish Twin Registry

  The dataset contains files with single nucleotide variants in VCF format for a total of 942 DNA samples, selected to represent a cross-section of the Swedish population. The samples originate from the Swedish Twin Registry (STR) and have been obtained from different geographical regions. For each of the 942 individuals, DNA was extracted from a blood sample and subject to whole genome sequencing (WGS). The WGS was performed using 2x150 bp paired-end chemistry on Illumina HiSeq X Ten instrumentation at the SciLifeLab National Genomics Infrastructure (NGI) in Stockholm and Uppsala. FASTQ files generated by WGS were analyzed using the nf-core pipeline Sarek, which includes pre-processing, alignment to the human GRCh38 reference genome, and germline variant calling. All participants gave their written informed consent and the TwinGene study was approved by the regional ethics committee (Regionala Etikprövningsnämnden, Stockholm, dnr 2007-644-31, dnr 2014/521-32). Access to phenotypic information can be requested from the Swedish Twin Registry (http://ki.se/en/research/the-swedish-twin-registry).

  Dataset EGAD50000001323

• SweGen whole-genome sequencing from the Swedish Twin Registry

  The dataset contains whole-genome sequencing data (aligned read files) in CRAM-format (lossless compression) for a total of 942 DNA samples, selected to represent a cross-section of the Swedish population. The samples originate from the Swedish Twin Registry (STR) and have been obtained from different geographical regions. For each of the 942 individuals, DNA was extracted from a blood sample and subject to whole genome sequencing (WGS). The WGS was performed using 2x150 bp paired-end chemistry on Illumina HiSeq X Ten instrumentation at the SciLifeLab National Genomics Infrastructure (NGI) in Stockholm and Uppsala. FASTQ files generated by WGS were analyzed using the nf-core pipeline Sarek, which includes pre-processing, alignment to the human GRCh38 reference genome, and germline variant calling. All participants gave their written informed consent and the TwinGene study was approved by the regional ethics committee (Regionala Etikprövningsnämnden, Stockholm, dnr 2007-644-31, dnr 2014/521-32). Access to phenotypic information can be requested from the Swedish Twin Registry (http://ki.se/en/research/the-swedish-twin-registry).

  Dataset EGAD50000001326

• 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

• Urethral Microbiome of Adolescent Males

  Urethral microbiome of adolescent males is designed to characterize the microbial communities resident in the urethra of young men, to identify differences in these communities as a function of race/ethnicity, circumcision status, sexual exposures, and uro-genital symptoms. We collect detailed sexual behavior and symptoms data using cellular telephones with Internet access. Specimens are routinely collected at monthly intervals, and intermittently following reported symptoms, specific sexual exposures, or identification of a sexually transmitted infection. We also collect periodic samples from the penile coronal sulcus to better characterize its relationship to the urethral micriobial communities. Participants are ages 14 - 17 at enrollment, and prior history of sexual exposure is not required for participation. Parental permission is obtained for each participant. The planned duration of followup is up to 4 years allowing for prospective observation of both physical and behavioral maturation from middle adolescence into young adulthood. The overall objectives of the project are to better characterize the healthy male urethral microbiome, and to use this information to better understand acquisition of urethritis and sexually transmitted infections, as well as chronic genital pain and prostatitis syndromes that become common among young adults.

  Study phs000259