20311 results for "Fc coins Buyfc26coins.com is EA Sports official for FC 26 coins They are efficient and quick always..Z2Xg"

in 20.32 milliseconds.

• RNA sequencing from High-grade B-cell lymphoma, not otherwise specified: an LLMPP study

  RNA-seq for 26 newly added samples in High-grade B-cell lymphoma, not otherwise specified: an LLMPP study, and 32 samples from a previously uploaded dataset.

  Dataset EGAD50000001365

• Sequencing data for oesophageal and related samples - OACs release 2 (RNA)

  Dataset EGAD00001003839

• Short-read (RNA-seq)

  The goal of this project was to perform long-read RNA sequencing (LR-seq, PacBio) in combination with short-read RNA-seq for systematic characterization of the isoform diversity in primary breast tumor samples. We sequenced the full-length transcriptomes of 26 breast tumors and 4 normal breast samples.

  Dataset EGAD00001006596

• Submitter Portal API

  Submitter Portal API The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have an ega-box (submission account), you can skip this step.  Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal-api

• Evolution of GBM through therapy

  Primary glioblastoma (GBM) tumours recur following treatment. This is likely due to intratumour heterogeneity (ITH), which reduces the effectiveness of cancer therapies by enabling therapy-driven tumour evolution: Darwinian selection of genotypically and/or phenotypically distinct cells (subclones) that resist treatment to seed regrowth of an even less treatable recurrence. To investigate this we sequenced a pilot cohort of nine paired primary and locally recurrent GBM tumours, alongside matched blood samples, in order to begin characterising therapy resistant cells and thereby infer the mechanisms by which they evaded treatment. These data were included in the first data release from the Glioma Longitudinal AnalySiS (GLASS) consortium.

  Study EGAS00001003546

• Tumor-associated preferred end coordinates and somatic variants as signatures of circulating tumor DNA

  Cell-free DNA fragmentation is a nonrandom process. We showed that cell-free DNA fragments with ends at certain genomic coordinates had higher likelihoods of being derived from hepatocellular carcinoma. Other coordinates were associated with cell-free DNA molecules originating from the liver. Quantitative assessment of cell-free DNA molecules bearing these respective groups of end signatures correlated with the amounts of tumor-derived or liver-derived DNA in plasma. There were millions of tumor-associated plasma DNA end coordinates across the genome. Due to their high prevalence, they were more readily detectable than somatic mutations as a cancer signature in plasma. Hence, detection of tumor-associated plasma DNA ends may offer a cost-effective means of capturing evidence for the presence of cancer through liquid biopsy assessment.

  Study EGAS00001003160

• POISED (Peanut Oral Immunotherapy: Safety, Efficacy, and Discovery)

  Phase 2 POISED (Peanut Oral Immunotherapy: Safety, Efficacy, Discovery) Study In this randomized, double-blind, placebo-controlled (DBPC) clinical trial, blinded placebo group received oat flour, whereas in active participants, dosage was built-up for over ~ 52 weeks and subsequently maintained on 4000 mg peanut protein, daily for next 52 weeks. 80 (98.77%) per-protocol active participants passed the food challenge at week 104. Subsequently, for 12 weeks, peanut ingestion was avoided in a randomized group of 51 blinded active participants (i.e., peanut avoidance group). 21 (41.2%) participants in the peanut avoidance group passed the 4000 mg double-blind, placebo-controlled food challenge (DBPCFC) without any allergic reaction at week 117, thus demonstrating sustained unresponsiveness. These 21 participants continued oral immunotherapy (OIT) for every three months and afterwards were allowed to continue peanut OIT discontinuation if they passed. 8 participants passed the DBPCFCs, 12 months after peanut discontinuation (week 156), i.e. they achieved long-term sustained unresponsiveness with no allergic reaction in response to food challenge. For detailed description, please refer to Chinthrajah et al., PMID: 31522849.

  Study phs003071

• Genomic Characterization CS-MATCH-0007 Arm B

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing, RNA sequencing and if possible, whole-genome, methylation and miRNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH clinical trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm B is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with HER2- activating mutations are treated with Afatinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002028

• Genomic Characterization CS-MATCH-0007 Arm Z1B

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm Z1B is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with CCND1, CCND2, and/or CCND3 amplifications are treated with Palbociclib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002180

• A Randomized, Double-Blind, Crossover Study of Sodium Phenylbutyrate (Buphenyl) and Low-Dose Arginine (100 mg/kg/day) Compared to High-Dose Arginine (500 mg/kg/day) Alone on Liver Function, Ureagenesis and Subsequent Nitric Oxide Production in Patients with Argininosuccinic Aciduria (ASA)

  Individuals with Urea Cycle Disorders (UCD) cannot remove ammonia, a waste product, from the blood. At present there is little information on the use of sodium phenylbutyrate (Buphenyl™) in children with argininosuccinic aciduria (ASA). It is hoped that this drug may help lower ammonia and argininosuccinic acid levels in patients with ASA. Through this study we hope to learn whether the use of sodium phenylbutyrate (Buphenyl™) in patients with ASA, in addition to diet and arginine therapy, will decrease liver damage and the number of periods during which ammonia levels are high. The primary study objective is to determine if the treatment of ASA patients with sodium phenylbutyrate (Buphenyl™) in conjunction with lowered doses of arginine improves liver function as measured by short-term assessment of synthetic activity and the use of stable isotope tracers to assess ureagenesis and nitric oxide production. Twelve patients with ASA will be studied using a randomized, cross-over design. Medical records will be reviewed to confirm the diagnosis prior to enrollment. Patients will be on the each arm of the study for one week each preceded by a three day washout period. Patients will come to the Baylor College of Medicine General Clinical Research Center in Texas Children's Hospital for an inpatient hospitalization. This hospitalization is for diet control, clinical evaluation, and stable isotope infusions for measurement of in vivo rates of ureagenesis and nitric oxide production. During the washout periods Buphenyl™ or other alternative route medications, e.g., benzoate, will be discontinued and arginine will be administered at the standard therapeutic dose of 500 mg/kg/day or 10 grams/m2. Following randomization, subjects will be maintained on either high-dose arginine (500 mg/kg/day or 10 grams/m2) alone, or the alternative of low-dose arginine (100 mg/kg/d or 2 grams/m2) along with sodium phenylbutyrate (500 mg/kg/day or 10 grams/m2). For the second week they will be crossed over to the other arm of the study preceded by another three day washout. Previous medications and dietary protein intake (0.6 g/kg/day or current metabolic diet) will be continued during both arms of the study. The two arms may be performed as separate ten-day admissions. The decision to design the study with two arms, high-dose arginine and low-dose arginine/Buphenyl™, was reached after weighing several considerations. First, the current accepted practice for treatment of ASA is high-dose arginine. Based on metabolic flux studies, we have quantified the effects of this dose of arginine as compared to standard doses of Buphenyl™/phenylacetate on ureagenesis. Since the study is not designed or intended to address the independent effects of Buphenyl™ as compared to arginine alone, Buphenyl™ was added for safety reasons to accommodate loss of clearance of nitrogen by decreasing the arginine dose. Moreover, based on our experience with recruiting for previous versions of this study, most ASA patients with liver dysfunction are on an alternative route ammonia scavenger medication in addition to arginine. We found that this has in fact become an accepted practice. Hence, when considering study design from both a safety and recruitment perspective, it was most reasonable to design the study to investigate specifically the hypothesis that the production and presence of argininosuccinic acid leads to liver dysfunction. Since both low-dose arginine with Buphenyl™ and high-dose arginine alone lead to a decreased production of argininosuccinic acid, and both are currently accepted therapies in ASA and UCDs in general, the need to address their effects distinctly is not being investigated at this time. Sodium phenylbutyrate dosage will be 500 mg/kg/day in patients weighing less than 20kg and 10 g/m2/day in larger patients. Daily dosage will be given in equally divided doses 4 times per day. In order to ensure that the study remains double-blind to investigators, study staff and subjects, the Investigational Pharmacy Service at Texas Children's Hospital will dispense both the Buphenyl™ and arginine in powder form which is compounded into capsules or will be mixed with syrpalta (up to 5 grams will dissolve in 10cc liquid) and administered orally or through nasogastric or gastrostomy tube. No nasogastric tube should be placed or gastrostomy performed solely for the purpose of inclusion in this study. Because the reported adverse effects of sodium phenylbutyrate include gastritis, participants will be started on a standard dose of ranitidine (Zantac™), or comparable drug, during both arms of the study.

  Study phs001305

• Evaluation Study of Congestive Heart Failure and Pulmonary Artery Catheterization Effectiveness (ESCAPE-BioLINCC)

  Accessing Data Please refer to “Authorized Access” below regarding accessing data through the BioData Catalyst ecosystem. The data from this accession is not available for download through dbGaP. Objectives To test whether pulmonary artery catheter use was safe and could improve clinical outcomes in participants hospitalized with recurrent heart failure. Background Pulmonary artery catheters have been used to guide adjustment of therapy in multiple settings, but recent studies have raised concern that pulmonary artery catheters may lead to increased mortality in hospitalized participants. Participants A total of 433 participants at 26 sites were enrolled, and randomly assigned to receive therapy guided by clinical assessment and the pulmonary artery catheter or clinical assessment alone. Patients with acute decompensation in which the attending heart failure physician considered pulmonary artery catheterization (PAC) was required or likely to be required within the next 24 hours were entered into a PAC registry. A total of 439 patients were added to the registry. Conclusions Therapy to reduce volume overload during hospitalization for heart failure led to marked improvement in signs and symptoms of elevated filling pressures, with or without the pulmonary artery catheter. Addition of the pulmonary artery catheter to careful clinical assessment did not impact overall mortality and hospitalization. Future trials should test noninvasive assessments with specific treatment strategies that could be used to better tailor therapy for both survival time and survival quality as valued by participants. (Binanay, C. et al., JAMA, 2005)

  Study phs003782

• Genomic Characterization CS-MATCH-0007 Arm Z1I

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm Z1I is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with BRCA1, BRCA2 mutations are treated with AZD1775. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002058

• Genomic Characterization CS-MATCH-0007 Arm Z1A

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm Z1A is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with NRAS mutations are treated with Binimetinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs001973

• Genomic Characterization CS-MATCH-0007 Arm W

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm W is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with FGFR fusions, mutations, amplifications are treated with AZD4547. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including tumor tissue and whole blood.

  Study phs001948

• Genomic Characterization CS-MATCH-0007 Arm S2

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm S2 is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with GNAQ or GNA11 mutations are treated with Trametinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002178

• Genomic Characterization CS-MATCH-0007 Arm R

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm R is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with BRAF fusions, non-V600K or non-V600E mutations, are treated with Trametinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002029

• Genomic Characterization CS-MATCH-0007 Arm S1

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm S1 is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with NF1 mutations are treated with Trametinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002153

• Genomic Characterization CS-MATCH-0007 Arm I

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm I is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with PIK3CA mutations (without KRAS Mutation or PTEN Loss) are treated with Taselisib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002181

• Genomic Characterization CS-MATCH-0007 Arm U

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm U is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with NF2 loss are treated with Defactinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002179

• Genomic Characterization CS-MATCH-0007 Arm C1

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm C1 is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with MET amplification are treated with Crizotinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002177

• Genomic Characterization CS-MATCH-0007 Arm P

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm P is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with PTEN loss by IHC are treated with the drug GSK2636771. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002152

• Genomic Characterization CS-MATCH-0007 Arm Q

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm Q is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with HER2 amplification are treated with Kadcyla® (ado-trastuzumab emtansine). This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including tumor tissue and whole blood.

  Study phs001926

• Cerebrospinal fluid cfDNA sequencing for classification of central nervous system glioma

  Primary central nervous system (CNS) gliomas can be classified by characteristic genetic alterations. In addition to solid tissue obtained by surgery or biopsy, cell-free DNA (cfDNA) derived from cerebrospinal fluid (CSF) is an alternative source of material for genomic analyses. Experimental design: We performed targeted next-generation sequencing (NGS) of CSF cfDNA in a representative cohort of 85 patients presenting with with suspicion of primary or recurrent glioma at two neurooncological centers. Copy-number variation (CNV) profiles, single nucleotide variants (SNVs), and small insertions/ deletions (indels) were combined into a molecular-guided tumor classification. Comparison with the solid tumor was performed for 38 cases with matching solid tissue available. Results: Cases were stratified into four groups: glioblastoma (n = 32), other glioma (n = 19), non-malignant (n = 17) and no confirmed diagnosis available (n = 17). We introduce a molecular-guided tumor classification, enabling identification of tumor entities and/ or cancer specific alterations in 75.0 % (n = 24) of glioblastoma and 52.6 % (n = 10) of other glioma cases. The overlap between CSF and matching solid tissue was highest for CNVs (26-48 %) and SNVs at pre-defined gene loci (44 %), followed by SNVs/indels identified via uninformed variant calling (8-14 %). A molecular-guided tumor classification was made 23.5 % (n = 4) of cases with no confirmed diagnosis available. Conclusions: We developed a workflow for targeted sequencing of CSF cfDNA as well as a strategy for interpretation and reporting of sequencing results based on a molecular-guided tumor classification in glioma.

  Study EGAS50000000060

• Whole-exome Sequencing Combined with Functional Genomics Reveals Novel Candidate Driver Cancer Genes in Endometrial Cancer

  Endometrial cancer is the most common gynecological malignancy, with more than 280,000 cases occurring annually worldwide. Although previous studies have identified important common somatic mutations in endometrial cancer, they have primarily focused on a small set of known cancer genes and have thus provided a limited view of the molecular basis underlying this disease. Here we developed an integrated systems biology approach to identifying novel cancer genes contributing to endometrial tumorigenesis. We first performed whole-exome sequencing on 13 endometrial cancers and matched normal samples, systematically identifying somatic alterations with high precision and sensitivity. We then combined bioinformatics prioritization with high-throughput screening (including both shRNA-mediated knockdown and expression of wild type and mutant constructs) in a highly sensitive cell viability assay. Our results revealed 12 potential driver cancer genes including 10 tumor suppressor candidates (ARID1A, INHBA, KMO, TTLL5, GRM8, IGFBP3, AKTIP, PHKA2, TRPS1 and WNT11) and two oncogene candidates (ERBB3 and RPS6KC1). The results in the “sensor” cell line were recapitulated by siRNA-mediated knockdown in endometrial cancer cell lines. Focusing on ARID1A, we integrated mutation profiles with functional proteomics in 222 endometrial cancer samples, demonstrating that ARID1A mutations frequently co-occur with mutations in the phosphatidylinositol 3-kinase (PI3K) pathway and are associated with PI3K pathway activation. siRNA knockdown in endometrial cancer cell lines increased AKT phosphorylation supporting ARID1A as a novel regulator of PI3K pathway activity. Our study presents the first unbiased view of somatic coding mutations in endometrial cancer and provides functional evidence for diverse driver genes and mutations in this disease.

  Study EGAS00001000318

• How to encrypt files with EGACryptor

  File preparation Due to the processes used at the EGA for file archival the use of non-alphanumeric characters in a filename will cause issues in archival. By convention whitespaces in filenames are to be avoided and should be replaced with the underscore character (_). Before encrypting your files please make sure that any files that will be uploaded to EGA do not use special characters such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &  Crypt4gh EGACryptor Files encrypted with EGACryptor must be uploaded via FTP EGACryptor The EGACryptor v.2.0.0 is a JAVA-based application which enables submitters to produce EGA compliant encrypted files along with files for the encrypted and unencrypted md5sum for each file to be submitted. The application will generate an output folder that will by default mirror the directory structure containing the original files. This output folder can subsequently be uploaded to the EGA FTP staging area via an FTP or Aspera client. Download EgaCryptor Download EgaCryptor Using the EgaCryptor Using the EgaCryptor Encrypting single file Encrypting multiple files Encrypting all files in folder Points to note Troubleshooting Troubleshooting Download EGACryptor The required jar files can be obtained by downloading EgaCrytptor jar file After the file has been downloaded, extraction of the zipped archive is required. The EGACryptor has been built to work with Java Runtime Environments from version 6 and above and with the OpenJDK Environment. Please refer to the relevant resources for installation guidance. Installing the latest version of the OpenJDK will include the JCE files. If your installation of Java JRE is less than 1.8.0_151 will require the manual installation of the JCE Policy Files. You can verify the version of the Java SE Runtime Environment (JRE) installed by using the command: $ java -version If you need to install the JCE please follow the instructions below: Installing the JCE policy files (due to licensing terms and conditions the required policy files must be downloaded direct from the ORACLE website) : Download the unlimited strength JCE policy files (JRE 6 / JRE 7/ JRE 8) Uncompress and extract the downloaded file. This will create a subdirectory called JCE. This directory contains the following files: README.txt, COPYRIGHT.html, local_policy.jar and US_export_policy.jar Install the two policy JAR files by replacing the existing ones in your java home directory. Install the two policy JAR files by replacing the existing ones in your directory. The standard place for JCE jurisdiction policy JAR files is: /lib/security [Unix] or \lib\security [Win32] Notes: refers to the directory where the Java SE Runtime Environment (JRE) was installed. Additional performance enhancements that have been included in the EGACryptor V2.0.0: The ability to parallelise the processing of datasets through the use of the resources on a system. Multicore systems will allow the user to specify n-1 cores for an n-core system. The use of this feature on clusters may speed up the processing of datasets that have large file numbers but consult your local cluster guide to ensure that there are not monopolising resources that are needed by other system users. The default for this process remains single threaded. 3 levels of system usage can be specified. Full usage within the limits detailed above. A limited mode that will ensure that 50% of the system resources are available for other tasks. Maximum mode is limited to 75% of system resources, this allows encryption to be prioritised but allows for the system to be usable for light alternate tasks. Finally there is a throttling mode that allows you to specify the exact number of computational threads to be used. the EGACryptor is able to ingest a structured directory and will output a directory with the same structure containing the encrypted files along with the md5checksums for the plain and encrypted files. The entire output directory can then be uploaded to the EGA for archival. as with the input path, it is now possible to specify the output path. the options have been updated inline with the upgraded functionality. The tool can only be used via the command line. The EGACryptor is designed to perform a single task, encrypting your data, for upload of these files please refer to our uploading guide Using the EgaCryptor Below are the three ways on how the EGACryptor tool can be used: Encrypting a single file : java -jar ../EGA-Cryptor_2_0_0.jar -i example1.bam Encrypting multiple files : java -jar ../EGA-Cryptor_2_0_0.jar -i "example1.bam,example2.bam" Encrypting all the files within a folder java -jar ../EGA-Cryptor_2_0_0.jar -i path/to/target/directory By default the EGACryptor v2 will create a new output directory containing all encrypted files and the relevant checksums within the target directory. If a specific directory is desired this can be specified by using the -o flag. This can be achieved in a similar manner to the following example: java -jar ../EGA-Cryptor_2_0_0.jar -i /path/to/target/directory -o /path/to/output/directory The tool will output three files per input file: file.gpg ( encrypted file ) file.md5( file md5 sum value file ) file.gpg.md5 ( encrypted file md5 sum value file ) All output files must then be uploaded to your submission account using Aspera or FTP. Further documentation on how to upload files: FTP and Aspera. Points to note Remember to provide the path to EgaCryptor.jar and run the command from within the directory the file/s are located. ECryptor writes files to the source directory of your local file system, as a result you must have write-access permissions for the source directory. Troubleshooting If in doubt about the function of the EGACryptor it is recommended to first consult the built-in documentation. This can be accessessed by using the -h flag as stated in the following table. Built-in Commands Table: list of the command line options built into EGA-Cryptor v2.0.0. Command line Option Action --------------------- ----------- -f Set this option to allow application to create maximum threads to utilise full capacity of cores/processors available on machine -h Use this option to view the bult-in help menu * -i File(s) to encrypt. Provide file/folder path or comma separated file path if multiple files in double quotes -l Set this option to allow application to create maximum threads equals to 50% capacity of cores/processors available on machine -m Set this option to allow application to create maximum threads equals to 75% capacity of cores/processors available on machine -o Path of the output file. This is optional. If not provided then output files will be generated in the same path as that of source file (default: output- files) -t Set this option if user wants to control application to create maximum threads as specified. Application will calculate no. of cores/processors available on machine & will create threads accordingly Encryption Errors UnixFileSystem.createFileExclusively (Native Method) The error is thrown by UNIX ("UnixFileSystem.createFileExclusively(Native Method)"). It appears that the user does not have write-access to the file system where the file to be uploaded is located. EGACryptor always writes MD5 checksums into files before uploading them to the server, and these files are created in the same location where the uploaded file itself resides.Solution: address your directory permission issue and re-run the command. Install JCE Unlimited Strength Jurisdiction Policy files The JCE policy unlimited strength jurisdiction files should be installed according to your current java version If you are still facing difficulty with the EGACryptor v.2 after having consulted the documentation please contact the EGA Helpdesk.

  Documentation submission/data/file-preparation/egacryptor