16146 results for "free fc coins and points Visit Buyfc26coins.com Alennukset toistuvista ostoista..p4v2"

in 19.07 milliseconds.

• The Finland-United States Investigation of NIDDM Genetics (FUSION) Tissue Biopsy Study

  The Finland-United States Investigation of NIDDM Genetics (FUSION) study is a long-term effort to identify genetic variants that predispose to type 2 diabetes (T2D) or that impact the variability of T2D-related quantitative traits (QTs). Most of the variants associated with T2D and related traits (glucose and insulin, anthropometrics, lipids) through genome-wide association studies (GWAS) occur in non-coding regions, suggesting a strong regulatory component to disease susceptibility. Regulatory element activity is often tissue-specific, which further complicates discovery of the causal/functional variation. Therefore, there is a critical need to identify the appropriate cell type, regulatory elements, target genes, and causal variants(s) in T2D-relevant tissues. We hypothesize that a subset of T2D and related variants alter gene expression regulation in skeletal muscle and adipose tissue - two major insulin target tissues and play key roles in insulin resistance. To that end, our study contains a comprehensive survey of genomics, epigenomics and transcriptomics in skeletal muscle and adipose tissue from individuals with glucose tolerance categories ranging from normal to T2D.For this FUSION Tissue Biopsy Study, we obtained RNA-Seq, microRNA (miRNA)-Seq, and DNA methylation (methyl)-Seq data on biopsy samples from 331 individuals from across the range of glucose tolerance: 124 normal glucose tolerance (NGT), 77 impaired glucose tolerance (IGT), 44 impaired fasting glucose (IFG), and 86 newly-diagnosed T2Ds. Participants completed two study visits, two weeks apart. First visits comprised most of the clinical phenotyping, including four-point OGTT (fasting, and 30, 60, and 120 minute post-load); BMI, WHR; lipids; blood pressure; and many other variables. Participants also completed FUSION health history, medication, and lifestyle questionnaires. On the second visit, we obtained ~250mg vastus lateralis skeletal muscle, ~750mg abdominal subcutaneous adipose, and a ~5x15mm section of abdominal skin. Visits were completed in March 2013. RNA isolation is ongoing in the Collins laboratory at the NIH, RNA and miRNA sequencing at the NIH Intramural Sequencing Center (NISC), and genotyping at the Center for Inherited Disease Research (CIDR). Individual-level data is available here for the 306 individuals who consented to data deposit. To focus on evaluation of gene expression and its regulation in skeletal muscle, we analyzed mRNA extracted from vastus lateralis skeletal muscle obtained from 271 of the 331 individual subjects from Finland, along with genome-wide genotypes. Individual-level data is available here for the 250 subjects who consented to the use of their data.Release phs001048.v2.p1 adds muscle data for an additional 42 subjects and data from adipose tissue for 276 subjects. Total RNA was isolated using Trizol extraction in the Collins laboratory at the NIH. The mRNA was poly-A selected, 24-plex libraries were generated using the Illumina TruSeq directional mRNA-seq library protocol and RNA sequencing was performed on HiSeq2000 sequencers using 101bp paired-end reads at NISC. miRNA libraries were prepared from total RNA from 296 muscle and 270 adipose samples, pooled and sequenced 50bp single-end reads on Illumina HiSeq2500. Data for 272 muscle and 251 adipose samples are available here for individuals with consent for data deposit. DNA was extracted from blood in the Collins laboratory, and genotyping on the Illumina Omni2.5M array was performed at CIDR. Genotypes were imputed using the HRC 2016 reference panel. In order to assess regions of open chromatin in skeletal muscle, we obtained muscle tissue from a commercial provider to perform ATAC-seq; these samples were sequenced at the University of Michigan DNA Sequencing Core.Release phs001048.v3.p1 adds single-nucleus (sn) RNA-seq and ATAC-seq data in 287 skeletal muscle samples out of the original 331 individuals. Individual-level data is available here for the 265 subjects who consented to the use of their data. The frozen tissue biopsy samples were processed in ten batches, each consisting of 40-41 samples. These batches were organized using a randomized block design to protect against experimental contrasts of interest including cohort, age, sex, BMI among others. Samples in each batch were pulverized, pooled together followed by nuclei isolation. The nuclei were processed on the 10X Genomics Chromium platform separately for snATAC-seq and snRNA-seq (v. 3.1 chemistry for snRNA-seq).Release phs001048.v4.p1 adds additional phenotypes and provides some corrections to several previous phenotypes.

  Study phs001048

• Diet, Genetic Factors, and the Gut Microbiome in Crohn's Disease

  We investigate the hypothesis that consistent changes in the human gut microbiome are associated with Crohn's disease, a form of inflammatory bowel disease, and that altered microbiota contributes to pathogenesis. Analysis of this problem is greatly complicated by the fact that multiple factors influence the composition of the gut microbiota, including diet, host genotype, and disease state. For example, data from us and others document a drastic impact of diet on the composition of the gut microbiome. No amount of sequencing will yield a useful picture of the role of the microbiota in disease if samples are confounded with uncontrolled variables. We aim to characterize the composition of the gut microbiome while controlling for diet, host genotype, and disease state. Diet is controlled by analyzing children treated for Crohn's disease by placing them on a standardized elemental diet, and by testing effects of different diets on the gut microbiome composition in adult volunteers. Genotype is analyzed by large scale SNP genotyping, which is already underway and separately funded--team member Hakon Hakonarson is currently genotyping 50 children a week at ~half a million loci each and investigating connections with inflammatory bowel disease. Clinical status is ascertained in the very large IBD practice in the UPenn/CHOP hospital system. Effects of diet, host genotype, and disease state on the gut microbiome are summarized in a multivariate model, allowing connections between microbiome and disease to be assessed free of confounding factors. This project is divided into four sub-studies. In the Fecal Storage Methods (FSM) study, methods of stool storage and DNA extraction are compared to examine their impact on DNA sequence analysis results. The Controlled Feeding Experiment (CaFE) addresses the effects of controlled diets on the gut microbiome. In the Cross-sectional Study of Diet and Stool Microbiome Composition (COMBO), the effects of diet analyzed using surveys and deep sequencing of stool specimens. The fourth study, Pediatric Longitudinal Study of Elemental Diet and Stool Microbiome Composition (PLEASE), examines the effects of an elemental diet treatment on pediatric patients diagnosed with inflammatory bowel disease (IBD), particularly Crohn's disease. Fecal Storage Methods (FSM): Cross-sectional study Controlled Feeding Experiment (CaFE): Controlled trial Cross-sectional Study of Diet and Stool Microbiome Composition (COMBO): Cross-sectional study Pediatric Longitudinal Study of Elemental Diet and Stool Microbiome Composition (PLEASE): Longitudinal cohort study

  Study phs000252

• Federated discovery and sharing of genomic data using Beacons

  The Beacon Project is a Global Alliance for Genomics & Health (GA4GH) initiative that enables genomic and clinical data sharing across federated networks. The project is working toward developing regulatory, ethics and security guidance to ensure proportionate safeguards for distribution of data according to the GA4GH-developed “Framework for Responsible Sharing of Genomic and Health-Related Data”. Within this Nature Biotechnology Correspondence a description of the Beacon protocol and how it can be used as a model for the federated discovery and sharing of genomic data is offered to the community. A Beacon is defined as a web-accessible service that can be queried for information about a specific allele. A user of a Beacon can pose queries of the form “Have you observed this nucleotide (e.g., C) at this genomic location (e.g., position 32,936,732 on chromosome 13)?” to which the Beacon responds with either “yes” or “no.” In this way, a Beacon allows allelic information of interest to be discovered by a remote searcher with no reference to a specific sample or patient, thereby mitigating privacy risks. The Beacon API (represented as a RESTful web application) provides a technical specification that a Beacon server must implement. The specification is open source and available online here. To simplify the process of lighting a Beacon, a free, open-source reference implementation of the latest specification has been developed. GA4GH is promoting different levels of data access (open, registered, and controlled) for convenience and for compatibility across its projects. Each so-called access tier has distinct visibility and requirements for authorization. For example, ‘open access’ Beacons are accessible to anonymous users of the internet, whereas ‘registered access’ Beacons are accessible to registered users (for example, bona fide researchers and clinicians) who have agreed to a set of conditions of data use. Many of the largest genomic archives, such as dbGaP, the European Genome-phenome Archive and the European Variation Archive, have provided access to variation data through Beacons for some or all of their datasets. Beacons can be interconnected through the Beacon Network, a directory and search engine for Beacons. Although individual Beacons answer the question “Have you observed this allele?”, the Beacon Network answers the question “Who has observed this allele?”. Beacons can be freely registered to the Beacon Network and can be searched independently or in aggregate with other connected Beacons.

  Blog federated-discovery-using-beacons

• Durvalumab Plus Tremelimumab Alone or in Combination with Low-Dose or Hypofractionated Radiotherapy in Metastatic Non-Small-Cell Lung Cancer Refractory to Previous PD(L)-1 Therapy: an Open-Label, Multicentre, Randomised, Phase 2 Trial

  Brief SummaryThis randomized phase II trial studies the side effects of durvalumab and tremelimumab and to see how well they work with or without high or low-dose radiation therapy in treating patients with colorectal or non-small cell lung cancer that has spread to other parts of the body (metastatic). Immunotherapy with durvalumab and tremelimumab, may induce changes in body's immune system and may interfere with the ability of tumor cells to grow and spread. Radiation therapy uses high energy x-rays to kill tumor cells and shrink tumors. Giving durvalumab and tremelimumab with radiation therapy may work better in treating patients with colorectal or non-small cell lung cancer.Detailed DescriptionPRIMARY OBJECTIVES:I. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 (durvalumab) and tremelimumab alone or with high or low-dose radiation in non-small cell lung cancer (NSCLC). (NSCLC Cohort) II. To compare the overall response (excluding the irradiated lesion[s]) between combined checkpoint blockade with MEDI4736 and tremelimumab alone or combined checkpoint blockade with low or high dose radiation. (NSCLC Cohort) III. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 and tremelimumab with high or low-dose radiation. (Colorectal Cohort) IV. To determine the overall response rate (excluding the irradiated lesion[s]) with combined checkpoint blockade with MEDI4736 and tremelimumab with either low or high dose radiation. (Colorectal Cohort)SECONDARY OBJECTIVES:I. To estimate median progression-free survival and overall survival. (NSCLC Cohort) II. To determine local control within the irradiated field(s) and abscopal response rates. (NSCLC Cohort) III. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells and overall response. (NSCLC Cohort) IV. To explore changes in PD-L1 expression, circulating T-cell populations, T-cell infiltration, ribonucleic acid (RNA) expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (NSCLC Cohort) V. To estimate median progression-free survival and overall survival. (Colorectal Cohort) VI. To determine local control within the irradiated field and abscopal response rates. (Colorectal Cohort) VII. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+ CD8+ T-cells and overall response. (Colorectal Cohort) VIII. To evaluate changes between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells induced by targeted low or high dose radiation. (Colorectal Cohort) IX. To explore changes in circulating T-cell populations, T-cell infiltration, RNA expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (Colorectal Cohort)OUTLINE: Patients are assigned to 1 of 2 cohorts. NOTE: This Study is only for Cohort 1. Please see phs003294 for Cohort 2COHORT 1: Patients with NSCLC are randomized to 1 of 3 arms.ARM A: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.ARM C: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses.COHORT 2: Patients with CRC are randomized to 1 of 2 arms.ARM A: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.After completion of study treatment, patients are followed for up to 12 weeks.Official TitleA Phase 2 Study of MEDI4736 (Durvalumab) and Tremelimumab Alone or in Combination With High or Low-Dose Radiation in Metastatic Colorectal and NSCLC Conditions Metastatic Colorectal CarcinomaMetastatic Lung Non-Small Cell CarcinomaStage IV Colorectal Cancer AJCC v7Stage IV Lung Non-Small Cell Cancer AJCC v7Stage IVA Colorectal Cancer AJCC v7Stage IVB Colorectal Cancer AJCC v7 Intervention/Treatment Biological: DurvalumabRadiation: Radiation TherapyBiological: Tremelimumab Other Study ID Numbers NCI-2016-01325NCI-2016-01325 ( Registry Identifier ) (REGISTRY: CTRP (Clinical Trial Reporting Program))17-71910021 ( Other Identifier ) (OTHER: Dana-Farber - Harvard Cancer Center LAO)10021 ( Other Identifier ) (OTHER: CTEP) Molecular Technologies / AssaysCyTOFIHCmIFOlinkRNAseqWES

  Study phs003295

• A Randomized Trial of Combined PD-L1 and CTLA-4 Inhibition with Targeted Low-Dose or Hypofractionated Radiation for Patients with Metastatic Colorectal Cancer

  Brief SummaryThis randomized phase II trial studies the side effects of durvalumab and tremelimumab to see how well they work with or without high or low-dose radiation therapy in treating patients with colorectal (CRC) or non-small cell lung cancer (NSCLC) that has spread to other parts of the body (metastatic). Immunotherapy with durvalumab and tremelimumab may induce changes in body's immune system and may interfere with the ability of tumor cells to grow and spread. Radiation therapy uses high energy x-rays to kill tumor cells and shrink tumors. Giving durvalumab and tremelimumab with radiation therapy may work better in treating patients with colorectal or non-small cell lung cancer.Detailed DescriptionPRIMARY OBJECTIVES:I. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 (durvalumab) and tremelimumab alone or with high or low-dose radiation in non-small cell lung cancer (NSCLC). (NSCLC Cohort) II. To compare the overall response (excluding the irradiated lesion[s]) between combined checkpoint blockade with MEDI4736 and tremelimumab alone or combined checkpoint blockade with low or high dose radiation. (NSCLC Cohort) III. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 and tremelimumab with high or low-dose radiation. (Colorectal Cohort) IV. To determine the overall response rate (excluding the irradiated lesion[s]) with combined checkpoint blockade with MEDI4736 and tremelimumab with either low or high dose radiation. (Colorectal Cohort)SECONDARY OBJECTIVES:I. To estimate median progression-free survival and overall survival. (NSCLC Cohort) II. To determine local control within the irradiated field(s) and abscopal response rates. (NSCLC Cohort) III. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells and overall response. (NSCLC Cohort) IV. To explore changes in PD-L1 expression, circulating T-cell populations, T-cell infiltration, ribonucleic acid (RNA) expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (NSCLC Cohort) V. To estimate median progression-free survival and overall survival. (Colorectal Cohort) VI. To determine local control within the irradiated field and abscopal response rates. (Colorectal Cohort) VII. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+ CD8+ T-cells and overall response. (Colorectal Cohort) VIII. To evaluate changes between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells induced by targeted low or high dose radiation. (Colorectal Cohort) IX. To explore changes in circulating T-cell populations, T-cell infiltration, RNA expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (Colorectal Cohort)OUTLINE: Patients are assigned to 1 of 2 cohorts. NOTE: This Study is only for Cohort 2. Please see phs003295 for Cohort 1COHORT 1: Patients with NSCLC are randomized to 1 of 3 arms.ARM A: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.ARM C: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses.COHORT 2: Patients with CRC are randomized to 1 of 2 arms.ARM A: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.After completion of study treatment, patients are followed for up to 12 weeks.Official TitleA Phase 2 Study of MEDI4736 (Durvalumab) and Tremelimumab Alone or in Combination With High or Low-Dose Radiation in Metastatic Colorectal and NSCLC Conditions Metastatic Colorectal CarcinomaMetastatic Lung Non-Small Cell CarcinomaStage IV Colorectal Cancer AJCC v7Stage IV Lung Non-Small Cell Cancer AJCC v7Stage IVA Colorectal Cancer AJCC v7Stage IVB Colorectal Cancer AJCC v7 Intervention/Treatment Biological: DurvalumabRadiation: Radiation TherapyBiological: Tremelimumab Other Study ID Numbers NCI-2016-01325NCI-2016-01325 ( Registry Identifier ) (REGISTRY: CTRP (Clinical Trial Reporting Program))17-71910021 ( Other Identifier ) (OTHER: Dana-Farber - Harvard Cancer Center LAO)10021 ( Other Identifier ) (OTHER: CTEP) Molecular Technologies/AssaysIHCmIFOlinkCyTOFRNAseqWES

  Study phs003294

• MediMer: A versatile do-it-yourself peptide-receptive MHC class I multimer platform for tumor neoantigen-specific T cell detection

  Peptide-loaded MHC class I (pMHC-I) multimers have revolutionized our capabilities to monitor disease-associated T cell responses with high sensitivity and specificity. To improve the discovery of T cell receptors (TCR) targeting neoantigens of individual tumor patients with recombinant MHC molecules, we developed a peptide-loadable MHC class I platform termed MediMer. MediMers are based on soluble disulfide-stabilized β2-microglobulin/heavy chain ectodomain single-chain dimers (dsSCD) that can be easily produced in large quantities in eukaryotic cells and tailored to individual patients’ HLA allotypes with only little hands-on time. Upon transient expression in CHO-S cells together with ER-targeted BirA biotin ligase, biotinylated dsSCD are purified from the cell supernatant and are ready to use. We show that CHO-produced dsSCD are free of endogenous peptide ligands. Empty dsSCD from more than 30 different HLA-A,B,C allotypes, that were produced and validated so far, can be loaded with synthetic peptides matching the known binding criteria of the respective allotypes, and stored at low temperature without loss of binding activity. We demonstrate the usability of peptide-loaded dsSCD multimers for the detection of human antigen-specific T cells with comparable sensitivities as multimers generated with peptide-tethered β2m-HLA heavy chain single-chain trimers (SCT) and wild-type peptide-MHC-I complexes prior formed in small-scale refolding reactions. Using allotype-specific, fluorophore-labeled competitor peptides, we present a novel dsSCD-based peptide binding assay capable of interrogating large libraries of in silico predicted neoepitope peptides by flow cytometry in a high-throughput and rapid format. We discovered rare T cell populations with specificity for tumor neoepitopes and epitopes from shared tumor-associated antigens in peripheral blood of a melanoma patient including a so far unreported HLA-C*08:02-restricted NY-ESO-1-specific CD8+ T cell population. Two representative TCR of this T cell population, which could be of potential value for a broader spectrum of patients, were identified by dsSCD-guided single-cell sequencing and were validated by cognate pMHC-I multimer staining and functional responses to autologous peptide-pulsed antigen presenting cells. By deploying the novel CHO producer cell-based dsSCD MHC-I MediMer platform, we hope to significantly improve success rates for the discovery of personalized neoepitope- specific TCR in the future by being able to also cover rare HLA allotypes.

  Study EGAS50000000065

• International Standards for Cytogenomic Arrays

  The International Standards for Cytogenomic Arrays (ISCA) Consortium is a rapidly growing group of clinical cytogenetics and molecular genetics laboratories committed to improving quality of patient care related to clinical genetic testing using new molecular cytogenetic technologies including array comparative genomic hybridization (aCGH) and quantitative SNP analysis by microarrays or bead chip technology. The ISCA Consortium is now working with the sequencing community to extend the goals of standardization, collaboration, and data sharing. To reflect this combined effort, we are becoming ICCG, or the International Collaboration for Clinical Genomics. Efforts of the Consortium include: Clinical Utility: The ISCA Consortium has made recommendations regarding the appropriate clinical indications for cytogenetic array testing (Miller et al. AJHG 2010, PMID: 20466091). Currently, discussions are focused on pediatric applications for children with unexplained developmental delay, intellectual disability, autism and other developmental disabilities. A separate committee has been developed to address appropriate cancer genetic applications (http://www.urmc.rochester.edu/ccmc/). Evidence-based standards for cytogenomic array design: The Consortium will develop recommendations for standards for the design, resolution and content of cytogenomic arrays using an evidence-based process and an international panel of experts in clinical genetics, clinical laboratory genetics (cytogenetics and molecular genetics), genomics and bioinformatics. This design is intended to be platform and vendor-neutral (common denominator is genome sequence coordinates), and is a dynamic process with input from the broader genetics community and evidence-based review by the expert panel (a Steering Committee with international representation). Public Database for clinical and research community: It is essential that a publicly available database be created and maintained for cytogenetic array data generated in clinical testing laboratories. This will be integrated into the current dbGaP database at NCBI/NIH and released through dbVar, and curated by a committee of clinical genetics laboratory experts. The very high quality of copy number data (i.e., deletions and duplications) coming from clinical laboratories combined with expert curation will produce an invaluable resource to the clinical and research communities. Standards for interpretation of cytogenetic array results: Using the ISCA Database, along with other genomic and genetics databases, the Consortium will develop recommendations for the interpretation and reporting of pathogenic vs. benign copy number changes as well as imbalances of uncertain clinical significance. Membership in the ISCA Consortium is open to all individuals and laboratories involved in cytogenetic array testing who are committed to free data sharing and to participation in a process to develop evidence-based standards and guidelines to improve patient care. ISCA is available through dbVar: http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd37/ http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd75/ http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd45/ http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd101/

  Study phs000205

• How to upload GPG files

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

  Documentation submission/data/uploading-files/ftp

• 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

• Molecularly matched targeted therapies plus radiotherapy in patients with newly diagnosed glioblastoma without MGMT promoter hypermethylation (N2M2/NOA-20 phase I/IIa umbrella trial)

  Background: Patients with glioblastoma without MGMT promoter hypermethylation are unlikely to benefit from temozolomide (TMZ). Trials aiming at replacing TMZ with targeted agents in not molecularly selected patient populations have failed. Methods: This phase I/IIa umbrella trial aimed at showing safety, feasibility, and preliminary efficacy of targeted compounds in addition to standard radiotherapy initiated within 42 days postoperatively. Molecular diagnostics and bioinformatic evaluation are performed within 28 days after surgery. Stratification for treatment takes place in five subtrials, including alectinib, idasanutlin, palbociclib, vismogedib and temsirolimus, according to the best matching molecular alteration. Patients without matching alterations are randomized between subtrials without strong biomarkers using atezolizumab and asunercept and TMZ as standard of care. Primary objective of the phase I parts of the trial was dose finding or dose validation. In the phase IIa trials, centrally determined progression-free survival at six months (PFS-6) is used as endpoint for efficacy with interim analyses for futility (H0: p=0.231). Results: From May 2018 through July 2022, 301 patients were enrolled and 228 treated in 13 German NOA sites. The alectinib and vismodegib subtrials were closed since no molecularly matching patients were accrued; the idasanutlin subtrial was closed prior to the optimal dose at nine patients at discretion of the company providing the drug. The TMZ subtrial showed a PFS-6 of 18.52% (10/54 patients) (p=0.831) and a median overall survival (OS) of 12.1 months. Asunercept: PFS-6 of 15.4% (4/26) (p=0.8825) and OS of 12.8 months. Atezolizumab: PFS-6 of 21.4% (9/42) (p=0.660) and OS of 11.7 months. Palbociclib with patients demonstrating CDK4 amplification or CDKN2A/B codeletion: PFS-6 of 24.4% (10/41) (p=0.4823) and OS of 12.6 months. Temsirolimus with patients demonstrating mTOR activation: PFS-6 of 39.1% (18/46) (p=0.0109) and OS of 15.4 months. The regimen-limiting toxicity (RLT)-rate is 34.8%, which is insignificantly above the predefined unacceptable rate for RLTs of 30%. Most RLTs had severity grade 3, one RLT had severity grade 4. No RLTs resulted in death. Conclusions: N2M2 allows for elaborate molecular testing being integrated into the treatment decision and efficient determination of treatment activity for patients with newly diagnosed glioblastoma. There is clinical activity of temsirolimus in patients with tumors harboring an activated mTOR pathway although this is not positively prognostic without mTOR inhibition; there is no clinical activity for asunercept and atezolizumab in not molecularly selected patients and also palbociclib in molecularly selected patients.

  Study EGAS00001008033