14659 results for "PLOS+ONE+Pennsylvania+German+ACS+language+code+pdc+open+access+study"

in 90.76 milliseconds.

• Institut Jules Bordet Data Access Committee for EGAS00001002685 study

  Dac EGAC00001000748

• Data Access Committee for Tumor Progression Study at Karolinska Institute

  Dac EGAC00001000778

• Data Access Committee for the Medulloblastoma Host Genome Study

  Dac EGAC00001000910

• Southern African Prostate Cancer Study (SAPCS) Data Access Committee

  Dac EGAC00001002768

• AmsterdamUMC Data Access Committee for the EPIC-CD study

  Dac EGAC00001003480

• Idiosyncratic and generic single nuclei and spatial transcriptional patterns in papillary and anaplastic thyroid cancers

  Thyroid cancer is the most common endocrine malignancy. This dataset encompasses two types of thyroid cancer : anaplastic which is the most de-differentiated and aggressive one, and papillary which is the most common one. We profiled 14 patients, including 10 papillary and 4 anaplastic thyroid carcinomas, using both single nuclei RNA sequencing and spatial transcriptomics to link single cell resolution RNA sequencing with tissue morphology and better understand inter and intratumoral thyroid cancer heterogeneity.

  Study EGAS00001007574

• Whole Exome and Whole Genome Profiling as well Genome-Wide Methylation Profiling from Early to Advanced Chronic Lymphocytic leukemia (CLL), Genome-Wide Methylation Profiling in Monoclonal B Cell Lymphocytosis (MBL)

  Serial whole exome sequencing of samples collected from 21 patients at multiple time points during progression from early to late chronic lymphocytic leukemia (CLL) and one matching non-tumor tissue sample from each patient. Additional whole genome sequencing of samples from 3 selected patients. Genome-wide B cell methylation compared between 5 healthy donors from the same age group as patients, 20 patients with monoclonal B cell lymphocytosis and in serial CLL samples with matching whole exome sequencing. Moreover, genome-wide single-cell RRBS-profiling of B cells from one healthy donor and from one patient with CLL was performed using a protocol newly developed by the A. Meissner group.

  Study phs001431

• Pediatric B-cell precursor acute lymphoblastic leukemia samples with very early relapse

  In this study we performed a genomic analysis of diagnosis-relapse pairs of 12 children who relapsed very early, followed by a deep-sequencing validation of all identified mutations. In addition, we included one case with a good initial treatment response and on-treatment relapse at the end of upfront therapy.

  Study EGAS00001005615

• Single-cell somatic copy number variants in brain using different amplification methods and reference genomes

  Low coverage paired end Illumina WGS from cells amplified with Picoplex, PTA, and droplet MDA. Two brains with Multiple System, Atrophy, one control, and non-brain controls (fibroblasts, NA12878)

  Study EGAS50000000020

• Whole-exome sequences of ovarian clear cell carcinomas and paired normal DNA

  Whole-exome sequencing dataset for the Australian Ovarian Cancer Study (AOCS) and The Jikei University School of Medicine (JIKEI) ovarian clear cell carcinoma (OCCC) clinical outliers project, representing 10 donors. Consists of 20 fastq files: one normal and one tumour from each patient.

  Dataset EGAD00001006004

• English Longitudinal Study for Ageing (ELSA) Genetic Data Access

  Dac EGAC00001000270

• Ludwig Data Access Committee for the Study of Oesophageal Cancer

  Dac EGAC00001000978

• Hoag Family Cancer Institute Carcinoid Multiomic Study Data Access Committee

  Dac EGAC00001003084

• 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

• Adaptive Therapy Exploits Fitness Deficits in Chemotherapy-Resistant Ovarian Cancer to Achieve Long-Term Tumor Control Open Access

  Drug resistance results in poor outcomes for cancer patients. Adaptive therapy is a potential strategy to address drug resistance that exploits competitive interactions between sensitive and resistant subclones. Here, we showed that adapting carboplatin dose according to tumor response (adaptive therapy) significantly prolonged survival of murine ovarian cancer models compared to standard carboplatin dosing, without increasing mean daily drug dose or toxicity. Platinum resistant ovarian cancer cells exhibited diminished fitness when drug was absent in vitro and in vivo, which caused selective decline of resistant populations due to reduced proliferation and increased apoptosis. Conversely fitter, sensitive cells re-grew when drug was withdrawn. Using a bioinformatics pipeline that exploits copy number changes to quantify the emergence of treatment resistance, analysis of cell‐free DNA obtained longitudinally from ovarian cancer patients during treatment showed subclonal selection through therapy, and measurements of resistant population growth correlated strongly with disease burden. These preclinical findings pave the way for future clinical testing of personalized adaptive therapy regimens tailored to the evolution of carboplatin resistance in individual ovarian cancer patients.

  Study EGAS50000001142

• Drug screening of patient-derived organoids from colorectal peritoneal metastases

  Colorectal cancer (CRC) patients with peritoneal metastases (CRPM) have limited treatment options and the lowest CRC survival rates. We trialed the possibility of organoid directed precision treatment for CRPM patients. CRPM organoids (peritonoids) isolated from patients underwent next-generation sequencing and medium-throughput drug panel testing ex vivo to identify specific drug sensitivities for each patient. We measured the utility of such a service including: success of peritonoid generation, time to cultivate peritonoids, reproducibility of the medium-throughput drug testing, and documented changes to clinical therapy as a result of the testing. Peritonoids were successfully generated and validated from 68% (19/28) of patients undergoing standard care. Genomic and drug profiling was completed within 8 weeks and a formal report ranking drug sensitivities was provided to the medical oncology team upon failure of standard care treatment. This resulted in a treatment change for 2 patients, one of whom had a partial response despite previously progressing on multiple rounds of standard care chemotherapy. The barrier to implementing this technology in Australia is the need for drug access and funding for off-label indications. In conclusion, our approach is feasible, reproducible and can guide novel therapeutic choices in this poor prognosis cohort, where new treatment options are urgently needed. This platform is relevant to many solid organ malignancies.

  Study phs002023

• Joslin Study on the Genetics of Type 2 Diabetes

  Between 1993 and 2003, families were recruited in the Joslin Study on the Genetics of Type 2 Diabetes for the presence of an autosomal dominant mode of inheritance of diabetes. Recruiting and screening of families occurred through probands who were receiving medical care at the Joslin Clinic (Boston, MA). Screening of families included 1) a proband and at least one sibling with type 2 diabetes, 2) diabetes occurring in at least three generations, 3) diabetes inherited on one side of the prospective family. Probands had to have a diabetes diagnosis between the age range from 10 to 60 years. Demographic data, clinical data, and family history were collected from participating family members, along with blood and urine samples. This study includes genetic and phenotypic data from one family examined in Simeone, Wilkerson, et. al. (NPJ Genomic Medicine 2022, PMID: 35869090). Genotype data for 14 family members and whole genome sequencing data for 6 individuals were generated with the goal of identifying a potential genetic cause of disease in this family. To de-identify this family and protect confidentiality, information on sex in phenotype data and variants identified in X, Y, and MT chromosomes have been removed in compliance with IRB guidelines.

  Study phs002959

• DAC for Sarcopenia HNSCC

  Data access committee for Sarcopenia HNSCC study

  Dac EGAC50000000420

• Exome Sequencing of Spanish Patients with rare genetic diseases.

  Whole exome sequencing of Spanish patients suffering from a rare genetic disease. The study was carried out in 2013 as a part of a public call from CNAG (Centro Nacional de Análisis Genómico), where data of eight spanish families were sent to analyse. The study concluded with three solved cases: two of aniridia and one syndromic RP.

  Study EGAS00001004028

• A Case Controlled Etiologic Study of Sarcoidosis (ACCESS-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. Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from (ACCESS) include Bronchial Lavage, DNA, Peripheral Blood Mononuclear Cells, and Plasma. Please note that use of biospecimens in genetic research is subject to a tiered consent. Objectives: To determine the etiology of sarcoidosis by establishing a case control, multi-center study. In addition to etiology, this study also sought to examine socioeconomic variables and the clinical course of patients with sarcoidosis, including quality of life.Background: Sarcoidosis is a chronic granulomatous disorder of unknown cause that is characterized by activation of T-lymphocytes and macrophages. For many years, sarcoidosis was presumed to be an atypical manifestation of tuberculosis because of the similarity between the inflammatory responses of the two diseases. However, as culture techniques became more widely employed to diagnose tuberculosis and it became less common, it became clear that sarcoidosis was not simply a variation of tuberculosis. Data on the etiology of sarcoidosis have come from diverse sources: in clinical investigations, alveolitis has been found to precede granulomatous inflammation; in case control studies, familial aggregation has been identified; and in case reports, recurrence of granulomatous inflammation has been observed after lung transplantation. The cause may not prove to be a single, known exposure. Interactions of exposures with genetic dispositions could have important implications for our understanding of immune responses as well as the pathogenesis of sarcoidosis.Participants: 736 participants with sarcoidosis enrolled within 6 months of diagnosis from 10 clinical centers in the U.S. Using the ACCESS sarcoidosis assessment system, organ involvement was determined for the whole group and for subgroups differentiated by sex, race, and age (Conclusions: The initial presentation of sarcoidosis is related to sex, race and age, and it tends to remain stable over two years in the majority of patients. The etiology is probably multifactoral with both genetic and environmental factors contributing.Specimen Details: The PBMC for this study are pelleted and suspended in guanidinium-based solution and are nonviable.

  Study phs004276

• Netherlands Cancer Institute (NKI-AVL) general DAC

  Data is available under reasonable request. All data requests will be reviewed by the NKI IRB and must be supported by the Principal Investigator of the study. The researcher will need to sign a data access agreement with the NKI after approval. Go to https://ega.nki.nl to fill out the form to request access.

  Dac EGAC50000000055

• NICHD Genomic and Proteomic Network for Preterm Birth Research (GPN)

  We performed genome-wide association studies (GWAS) to study the Spontaneous Preterm birth (SPTB). Maternal and neonatal DNA from 743 SPTB (20 to and less than 34 weeks), and 752 controls (39 to and less than 42 weeks) who fully consented for public research usage were collected from participants in several clinical centers in Alabama, Illinois, New York, North Carolina, Rhode Island, Texas, and Utah. Cases were 1:1-matched with controls according to race/ethnicity (White, Hispanics, African Americans, and Others), maternal age (<20, 20-29, 30-39, 40+), and parity (yes or no). To determine the case-control status for each participant, a Gestational Age (GA) was determined. DNA samples were taken from blood or saliva if blood was not available. Automated DNA extractions were performed on the Qiagen M48 robot, and samples were organized in 96-well plates with barcoding and sample tracking systems. Subsequent manipulations were performed on the Biomek FX liquid handling workstation with 96-channel pipetting. DNA quantitation was performed by dye-based assay on a Molecular Devices SpectraMax Plus plate reader. Samples were genotyped using Affymetrix Genome-Wide Human SNP Array 6.0. This work was conducted at the Microarray Facility at the University of Pennsylvania. Patient data were collected through chart reviews and patient interviews, which included Demographic information (parental age, race, ethnicity, etc.); Medical history (pre-pregnancy weight, height, medications, STD history, medical conditions, etc.); Social history (marital status, years of education, alcohol use and tobacco use); Obstetrical history including outcome of all prior pregnancies and dates of termination; History of preterm labor or premature rupture of membranes symptoms, evaluation or hospitalization for those symptoms in current pregnancy; Medications taken during current pregnancy; History of cervical evaluation (manually or ultrasonographically) or fetal fibronectin measurements; Pregnancy complications; Labor (type, indications, membrane status, and induction method); Delivery type and indications for cesarean section; Neonatal outcome (sex, weight, length, Apgar score, neonatal complications, admission to intensive care unit, etc.); and Maternal family history of SPTB.

  Study phs000714

• Investigation of chromatin accessibility in clear cell renal cell carcinoma using ATAC-seq

  To identify regions of open and accessible chromatin in clear cell renal cell carcinoma (ccRCC), we performed ATAC-seq on the 786-O, A-498, UM-RC-2 ccRCC cell lines, as well as HK-2 normal renal epithelium cell line, cultured under normoxic (20% O2) and hypoxic (0.05% O2) conditions. Data are provided in raw fastq and processed narrowPeak fomats. Data were processed using the nf-core atacseq pipeline.

  Dataset EGAD50000001885

• Data Access Committee for the Metastatic Breast Cancer Whole-exome sequencing study

  Dac EGAC00001000434

• Cancer Affected Patients - Data Access Committee

  Access to the cancer cohort is made available by completing the data access agreement for review by the data access committee and will be granted to qualified investigators for appropriate use. Individuals requesting access to the data need to comply with the terms of a Data Access Agreement (DAA) and are requested to use the data only in approved and ethical ways.

  Dac EGAC50000000037