72 results for ""developer+diary"+"autumn"+game+'developer+diary'+'autumn'+'download'"

in 7.70 milliseconds.

• EGA QuickView

  EGA QuickView Secure and Remote Access to EGA Files What is EGA QuickView? EGA QuickView is a FUSE file system that allows secure and remote access to EGA files. It is a hybrid of sshfs and crypt4ghfs, which means it uses ssh to connect to the EGA distribution servers, downloads data in Crypt4GH format, and transparently decrypts those files. It is compatible with Linux and macOS 12. Why use EGA QuickView? EGA QuickView is a highly useful and convenient tool for anyone who needs to access EGA files remotely and securely. The software offers a quick and convenient way to browse through EGA files without the need for complete downloads, thus saving bandwidth and time. Whether you are a medical professional requiring access to sensitive patient data or a research scientist working on a project that involves EGA files, EGA QuickView provides a highly useful solution. The software boasts advanced security features, ensuring that your data is safe and protected at all times. Get started with EGA QuickView To get started with EGA QuickView, visit the EGA QuickView GitHub repository for more information and installation instructions.

  Documentation access/download/visualisation/ega-quickview

• 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

• Human genomic and phenotypic synthetic data for the study of rare diseases

  The purpose of this dataset is to facilitate development of technical implementations for rare disease data integration, analysis, discovery, and federated access. This synthetic dataset includes clinical and genomic data from 6 rare disease cases. It consists of 18 whole genomes (6 index cases with their parents) which have genetic background based on public human data sequenced in the context of the Illumina Platinum initiative (Eberle, MA et al. (2017)) and made available by the HapMap project (https://www.genome.gov/10001688/international-hapmap-project). In each of the cases, real causative variants correlating with the phenotypic data provided were spiked-in. The cases included in this synthetic dataset correspond to the following type of disorders: CASE 1- Congenital myasthenic syndrome (Autosomal Dominant -de novo variant) CASE 2- Macular dystrophy (Autosomal Dominant) CASE 3- Muscular dystrophy (Autosomal Recessive-compound heterozygous variants) CASE 4- Mitochondrial disorder (Autosomal Recessive-consanguineous case - homozygous variant) CASE 5- Breast cancer (Autosomal Dominant) CASE 6- Similar as case 1 for patient matchmaking tests: Congenital myasthenic syndrome (Autosomal Dominant-de novo variant) For each case you will be able to download the following data: clinical information (phenopackets per individual and pedigree per family), raw genomic data (FASTQ and BAMs) and processed genomic data (vcfs). When using the data, the following should be acknowledged: the RD-Connect GPAP (https://platform.rd-connect.eu/), EC H2020 project EJP-RD (grant # 825575), EC H2020 project B1MG (grant # 951724) and Generalitat de Catalunya VEIS project (grant # 001-P-001647).

  Study EGAS00001005702

• Subpopulations and Intermediate Outcome Measures in COPD Study (SPIROMICS)

  Subpopulations and Intermediate Outcome Measures in COPD Study Description Subpopulations and intermediate outcome measures in COPD study (SPIROMICS) supports the prospective collection and analysis of phenotypic, biomarker, genetic, genomic, and clinical data from subjects with COPD for the purpose of identifying subpopulations and intermediate outcome measures. It is funded by the National Heart, Lung, and Blood Institute and is coordinated by the University of North Carolina at Chapel Hill. Molecular fingerprinting and extensive subject phenotyping will be performed to identify disease subpopulations and to identify and validate surrogate markers of disease severity which will be useful as intermediate outcome measures for future clinical trials. Secondary aims are to clarify the natural history of COPD, to develop bioinformatic resources that will enable the utilization and sharing of data in studies of COPD and related diseases, and to create a collection of clinical, biomarker, radiographic, and genetic data that can be used by external investigators for other studies of COPD. Participating Institutions: Research participants for SPIROMICS will be enrolled, phenotyped, and followed at twelve SPIROMICS Clinical Centers: Columbia University, Temple University, Johns Hopkins University, Wake Forest University, University of Michigan, University of Illinois at Chicago, University of Iowa, University of Utah, National Jewish Health, University of Alabama at Birmingham, University of California at San Francisco, and University of California at Los Angeles. The University of North Carolina at Chapel Hill serves as the Genomics and Informatics Center. The Radiology Reading Center is based at the University of Iowa. The PFT Reading Center is based at the University of California at Los Angeles. Study Design: SPIROMICS is a prospective cohort study that enrolled approximately 2,981 participants at twelve clinical centers over five years. Participants are distributed across four enrollment strata (i.e., Never-smokers, Smokers without COPD, Mild/Moderate COPD, and Severe COPD). Study Visits: Participants have up to four in-person visits (Baseline and Annual Clinic Visits at years 1, 2, 3 after Baseline). Study questionnaires and spirometry are completed at all main study visits. Blood and urine samples are collected at visits 1, 2, and 4. Sputum samples are collected at Visit 1. The CT scans are completed and Baseline and Visit 2. Participants also receive quarterly follow-up calls to assess health status and determine if an exacerbation has occurred. Substudies A. Bronchoscopy and Immunophenotyping Substudy The Bronchoscopy Substudy enrolled a total of 251 participants. These participants will be recruited across all four study strata. This substudy includes two study visits. During the first visit sputum samples are collected for Immunophenotyping analysis at the Immunophenotyping Core Lab based at the University of Michigan. Participants then return for a second visit during which samples are collected via bronchoscopy, including bronchoalveolar lavage, epithelial brushings and bronchial biopsies. Immunophenotyping analysis is also conducted on BAL and blood collected during the bronchoscopy study visit. B. Repeatability Substudy The entire baseline clinic visit was repeated on 98 volunteers to determine reliability of measurement procedures. All baseline study-related procedures and questionnaires, including the CT scan, was re-administered and new samples of blood, urine, saliva, and sputum was collected. Field center staff processed these biospecimen samples according to the same protocol. C. Exacerbation Substudy The Exacerbation Substudy is a prospective, longitudinal observational study of 204 participants, which will allow the assessment of participant driven health care utilization (HCU) events and symptom-defined exacerbation events over time. HCU driven events are defined by change in medical treatment in response to a perceived COPD Exacerbation. Symptom-based events will be defined by using EXACT-PRO (EXacerbations of Chronic Pulmonary Disease Tool - Patient Reported Outcome) a daily symptom diary developed to measure the frequency, severity, and duration of exacerbations in clinical trials. All participants are provided with a PDA on which to complete the diary. Participants reporting a possible COPD exacerbation will be brought into the study clinic for a study visit to collect biological specimens and questionnaire data. The overall objectives of the exacerbation substudy are to: Obtain clinical data and specimens on SPIROMICS participants before and during an acute COPD exacerbation defined by: Health care utilization triggered by the subject, or Symptomatic change (triggered by an EXACT defined threshold) Describe symptomatic changes occurring around HCU and symptom-defined (EXACT) events and their relationship to clinical and specimen data Characterize the non-exacerbation "stable" state in COPD using the EXACT, including: Symptom variability (EXACT), Clinical data and specimen parameters during a stable state (baseline), The relationship between clinical and specimen data and symptom severity and variability. Explore the characteristics of stable patients, defined as those who do not experience HCU or symptom-defined (EXACT) events during the sub-study period, using baseline clinical data and specimens and compare these characteristics with patients who experience HCU and/or symptom-defined events. Examine the relationship between HCU and symptom-defined exacerbation frequency during the first one-year period of follow-up for exacerbations and health outcomes, including 12-month change in lung function and COPD health status, and longer term morbidity and mortality, with the latter derived from long-term data from the larger SPIROMICS study.

  Study phs001119

• NHLBI TOPMed: SubPopulations and InteRmediate Outcome Measures In COPD Study (SPIROMICS)

  Subpopulations and Intermediate Outcome Measures in COPD Study Description Subpopulations and intermediate outcome measures in COPD study (SPIROMICS) supports the prospective collection and analysis of phenotypic, biomarker, genetic, genomic, and clinical data from subjects with COPD for the purpose of identifying subpopulations and intermediate outcome measures. It is funded by the National Heart, Lung, and Blood Institute and is coordinated by the University of North Carolina at Chapel Hill. Molecular fingerprinting and extensive subject phenotyping will be performed to identify disease subpopulations and to identify and validate surrogate markers of disease severity, which will be useful as intermediate outcome measures for future clinical trials. Secondary aims are to clarify the natural history of COPD, to develop bioinformatic resources that will enable the utilization and sharing of data in studies of COPD and related diseases, and to create a collection of clinical, biomarker, radiographic, and genetic data that can be used by external investigators for other studies of COPD. Participating Institutions: Research participants for SPIROMICS will be enrolled, phenotyped, and followed at twelve SPIROMICS Clinical Centers: Columbia University, Temple University, Johns Hopkins University, Wake Forest University, University of Michigan, University of Illinois at Chicago, University of Iowa, University of Utah, National Jewish Health, University of California at San Francisco, and University of California at Los Angeles. The University of North Carolina at Chapel Hill serves as the Genomics and Informatics Center. The Radiology Reading Center is based at the University of Iowa. The PFT Reading Center is based at the University of California at Los Angeles. Study Design: SPIROMICS is a prospective cohort study that enrolled approximately 2,981 participants at twelve clinical centers over five years. Participants are distributed across four enrollment strata (i.e., Never-smokers, Smokers without COPD, Mild/Moderate COPD, and Severe COPD). Study Visits: Participants have up to four in-person visits (Baseline and Annual Clinic Visits at years 1, 2, 3 after Baseline). Study questionnaires and spirometry are completed at all main study visits. Blood and urine samples are collected at visits 1, 2, and 4. Sputum samples are collected at Visit 1. The CT scans are completed and Baseline and Visit 2. Participants also receive quarterly follow-up calls to assess health status and determine if an exacerbation has occurred. Substudies Bronchoscopy and Immunophenotyping Substudy The Bronchoscopy Substudy will enroll 50 subjects per site, for a total of 300 participants. These participants will be recruited across all four study strata. This substudy includes two study visits. During the first visit, sputum samples are collected for Immunophenotyping analysis at the Immunophenotyping Core Lab based at the University of Michigan. Participants then return for a second visit during which samples are collected via bronchoscopy, including bronchoalveolar lavage, epithelial brushings and bronchial biopsies. Immunophenotyping analysis is also conducted on BAL and blood collected during the bronchoscopy study visit. Repeatability Substudy The entire baseline clinic visit was repeated on 98 volunteers to determine reliability of measurement procedures. All baseline study-related procedures and questionnaires, including the CT scan, were re-administered and new samples of blood, urine, saliva, and sputum were collected. Field center staff processed these biospecimen samples according to the same protocol. Exacerbation Substudy The Exacerbation Substudy is a prospective, longitudinal observational study of up to 400 participants, which will allow the assessment of participant-driven health care utilization (HCU) events and symptom-defined exacerbation events over time. HCU-driven events are defined by change in medical treatment in response to a perceived COPD Exacerbation. Symptom-based events will be defined by using EXACT-PRO (EXacerbations of Chronic Pulmonary Disease Tool - Patient Reported Outcome), a daily symptom diary developed to measure the frequency, severity, and duration of exacerbations in clinical trials. All participants are provided with a PDA on which to complete the diary. Participants reporting a possible COPD exacerbation will be brought into the study clinic for a study visit to collect biological specimens and questionnaire data. The overall objectives of the Exacerbation Substudy are to: Obtain clinical data and specimens on SPIROMICS participants before and during an acute COPD exacerbation defined by Health care utilization triggered by the subject, or Symptomatic change (triggered by an EXACT defined threshold) Describe symptomatic changes occurring around HCU and symptom-defined (EXACT) events and their relationship to clinical and specimen data, Characterize the non-exacerbation "stable" state in COPD using the EXACT, including: Symptom variability (EXACT), Clinical data and specimen parameters during a stable state (baseline), The relationship between clinical and specimen data and symptom severity and variability. Explore the characteristics of stable patients, defined as those who do not experience HCU or symptom-defined (EXACT) events during the sub-study period, using baseline clinical data and specimens, and compare these characteristics with patients who experience HCU and/or symptom-defined events. Examine the relationship between HCU and symptom-defined exacerbation frequency during the first one-year period of follow-up for exacerbations and health outcomes, including 12-month change in lung function and COPD health status, and longer-term morbidity and mortality, with the latter derived from long-term data from the larger SPIROMICS study.

  Study phs001927

• Reading about genomic analysis of pan-neuroblastoma

  There are virtually no research fields that do not benefit from the large-scale genomic analysis that are so popular nowadays. For research into diseases with highly diverse clinical behavior like pediatric neuroblastoma, nevertheless, this type of approach has been a game-changer. Samuel W. Brady and colleagues, from St. Jude Children’s Research Hospital in Memphis, have gathered data from 702 neuroblastomas which were profiled by whole genome sequencing (WGS, n = 205), whole exome sequencing (WES, n = 539), and/or RNA-Seq. Less than half of the samples were generated during this study, while the others were obtained from previous work. Part of the WES data was indeed deposited in EGA in 2012 (EGA study EGAS00001000213). A scratchy summary about the huge work from Samuel W. Brady and colleagues, published in Nature Communications this October 2020 “These findings suggest that the sympathetic nervous system, the tissue from which neuroblastoma arises, is susceptible to different oncogenic insults at different times during development, which could be explored in future investigations using animal models.” Conclude the authors, highlighting the importance of their findings. Pediatric neuroblastomas are classified according to clinical and molecular features into low, intermediate, and high risk. Age plays a critical role in the classification, with younger children having an overall better prognosis. The samples included in this study belonged to all ages and risk-groups: the aim of such set up is the identification of age-associated molecular aberrations. The authors defined a mutational landscape of pediatric neuroblastoma including rare driver events, impossible to pick with a smaller data set. Interestingly, most driver mutations' frequency was found to be age-related. Those include alterations on MYCN, TERT, PTPRD, and Ras pathway, in addition to the previously reported ATRX. In addition, the large data set allowed the authors to define co-existence relations between the mutations (mutual exclusion or co-occurrence) which is a crucial puzzle piece to unravel the mechanisms driving the pathogenesis. Enjoy this really interesting article, open source on Pubmed.

  Blog genomic-analysis-of-pan-neuroblastoma

• Glial Cell Line-Derived Neurotrophic Factor (GDNF) Polymorphisms and Anxiety, Depression

  GDNF gene variants were studied as possible risk factors of depression or anxiety on a young sample. The association study involved eight (rs1981844, rs3812047, rs3096140, rs2973041, rs2910702, rs1549250, rs2973050 and rs11111) GDNF single nucleotide polymorphisms and anxiety and depression scores measured by the Hospital Anxiety and Depression Scale (HADS) on 708 Caucasian young adults with no psychiatric history. Results provided significant effects of two single nucleotide polymorphisms on anxiety scores following the Bonferroni correction for multiple testing (p=0.00070 and p=0.00138 for rs3812047 and rs3096140, respectively). Haplotype analysis confirmed the role of these SNPs (p=0.00029). A significant sex-gene interaction was also observed since the effect of the rs3812047 A allele as a risk factor of anxiety was more pronounced in males. This is the first demonstration of a significant association between the GDNF gene and mood characteristics demonstrated by the association of two SNPs of the GDNF gene (rs3812047 and rs3096140) and individual variability of anxiety using self-report data from a non-clinical sample. Reprinted from Kotyuk et. al., 2013 (Kotyuk, E., Keszler, G., Nemeth, N., Ronai, Z., Sasvari-Szekely, M., and Szekely, A. (2013). Glial Cell Line-Derived Neurotrophic Factor (GDNF) as a Novel Candidate Gene of Anxiety. PLoS One,8, (12) PMID: 24324616), with permission from Publisher (All content of articles published in PLOS journals is open access. You can read about our open access license here: http://www.plos.org/about/open-access/. To summarize, this license allows you to download, reuse, reprint, modify, distribute, and/or copy articles or images in PLOS journals, so long as the original creators are credited (e.g., including the article's citation and/or the image credit); Laura Perry; Staff EO;PLOS ONE)

  Study phs000713

• How to use EGA Webin?

  EGA Webin EGA Webin serves as a platform for registering metadata for array based submissions, large scale sequence submission as well as for legacy EGA submission accounts (ega-box-XXXX). For large scale submitters of sequence data you have also the option to submit metadata via XMLS programmatic submission, while new submitters are advised to utilise the Submitter Portal for their submissions. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. WEBIN actions: Register metadata for a sequence submission Register study, samples, experiments, runs, DAC, policy and dataset/s after file upload. Register components for your array-based metadata submission Register study, samples, DAC or policy before uploading files. Edit existing submission metadata Change or update previously submitted metadata. Register metadata for a sequence submission Ensure that all sequence files have been encrypted before uploading them to your submission account using the EgaCryptor. Go to the EGA Webin and log in using your submission account name (ega-box-XXX) and password. Register components of your metadata submission Study Samples Data Access Committee (DAC) Data access policy Dataset For array-base submissions: Study, Samples, Data Access Committee (DAC) and Data access policy may all be registered BEFORE file upload and dataset registration through the array-base template. Register your Study Go to the “Studies (Projects)” box Click on “Register Study” and fill in the information related to your study. Click on “Submit”, this will save the information and generate an EGA study ID. To use the study accession number in a publication, the study has to be previously released on the EGA website, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX.Further information about EGA can be found on https://ega-archive.org and “The European Genome-phenome Archive in 202 "(10.1093/nar/gkab1059)" Register your Samples Go to the “Samples” box Click on “Register Samples” Select “Download spreadsheet to register samples” and customise your template, there is a default EGA template (EGA default checklist) but more attributes can be added if required. For the EGA default checklist, there are mandatory,recommended and optional attributes. As well custom fields which can be added if required. Mandatory attributes Field Name Description tax_id Taxonomy ID of the organism as in the NCBI Taxonomy database. Entries in the NCBI Taxonomy database have integer taxon IDs. See our tips for sample taxonomy here scientific_name Scientific name of the organism as in the NCBI Taxonomy database. Scientific names typically follow the binomial nomenclature. For example, the scientific name for humans is Homo sapiens. sample_alias Unique name of the sample. If not selected system will auto generate an unique alias sample_title Title of the sample sample_description Description of the sample phenotype *** Where possible, please use the Experimental Factor Ontology (EFO) to describe your phenotypes. Recommended attributes Field Name Description subject_id Identifier for the subject where the sample has been derived from gender * Sex Optional attributes Field Name Description sex sex of the organism from which the sample was obtained disease_site Affected organ sample type Affected organ donor_id ** Identifier of the donor where the sample has been derived from *Gender should be described as 'male', 'female' or 'unknown'. If 'unknown' due to a known sex chromosome aneuploidy, please create a user defined attribute called 'Sex chromosome karyotype' and add the appropriate value, for example, 'XXY'. **Donor id (Subject id) should be a de-identified subject handle. If unknown, please add 'unknown' to the field. ***Phenotypes should, where possible, be an Experimental Factor Ontology accession. If a term cannot be found to describe your phenotype please use free text. All sample phenotypes considered important for further analysis of the data should be provided (for example, tumour type), additional phenotype attributes can be created by defining your own attributes; use the notion 'phenotype2', 'phenotype3', etc. After you have customised the fields for the sample submission, download the template and fill in the information. Example of the sample template: Finally upload the sample template to get the EGA accession IDs for the samples. Register your Data Access Committee (DAC) Further information on the role of your DAC Go to the “Data Access” box Click on “Register Dacs” Input the information about the DAC and register at least one main DAC contact. Register your Data Access Policy Your Data Access Policy provides the terms and conditions of data use, this is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAC). Go to the “Data Access” box Click on “Register Policies” Select the DAC to which this policy will be linked to and fill in the policy information. Submitting your Runs and Analyses This section is only for sequence data submission, for array-based submission it can be skipped. Please refer to our Submitting array based metadata Runs Registration Go to the “Raw Reads (Experiments and Runs)” box Click on “Submit Reads” Select “Download spreadsheet template for Read submission” Select the template corresponding to your submission type For the templates you have the option to customise the optional fields. To check their description click on “Show Description “ Download the template and fill in the required information. Example of the runs template: We recommend that Fastq, BAM, and CRAM read files are submitted using Webin-CLI When using this interface instead of Webin-CLI, raw sequences must be uploaded in one of the supported data formats before they can be submitted. The files can be uploaded using FTP or Aspera. The study and the sequenced samples must be pre-registered before the raw reads are submitted. Please note that each individual study and sample should be registered only once. You will be asked to provide information about the sequencing libraries and instruments. Submitting your Dataset This section is only for sequence data submissions, for array based submissions it can be skipped. Please refer to our Submitting array based metadata The dataset describes the data files, defined by the run (EGARXXXXXXXXXXX) and analysis (EGAZXXXXXXXXXXX) accessions that make up the dataset and links the collection of data files to a specified Data Access Committee and Data Access Policy. As a result, you must have registered your Reads and experiments, Data Access Committee (DAC) and Data access policy before submitting your Dataset. Please consider the number of datasets that your submission consists of, for example, a case control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Please contact EGA Helpdesk for further assistance. Go to the “Data Access” box Click on “Register Dataset” Select the Data Access Committee (DAC) and Data access policy Register your dataset After submitting your dataset you should contact the EGA Helpdesk to provide a release date for your dataset. Datasets are automatically held (i.e. not released) unless they are affiliated to a study that has already been released. Edit/update existing submission metadata Go to the “Report” section of the object you would like to edit. Locate the object and click on the arrow under action. An option menu will be displayed. Objects can be edited through their XML or with the WEBIN menu. After an object has been edited, changes would be available on the website until the submission is released again. Please contact the EGA Helpdesk if you require further assistance.

  Documentation submission/metadata/submission/EGA_webin

• 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

• Quick Guide for data submission

  Quick Guide This is a quick guide to submit data to the EGA. Please select data type to display the right detailed instructions. Sequence data Array-based data Get your submission account You first need to create your EGA user. Then, once your account has been verified by the Help Desk team, request your submission account and provide details of the data type and platform(s) in your submission. Register Study/DAC Use Submitter Portal to register your study, samples, Data Access Committee (DAC) and Policy. Upload data Encrypt your data files using the and upload it to your inbox using SFTP. Register experiments and runs Associate each data file to a registered sample and study by Linking files to samples. Details of the experimental procedure you followed must be provided. Finalise your submission Group your runs/analysis into datasets and link them to your new or existing DAC and policy using DAC Portal. Data request are done at a dataset level, thus files within a datasets must share release conditions. Release and admin When finalising the submission, set a released date to instruct our Helpdesk to release your study. All registered studies are automatically placed on hold until the named submission or DAC contact instructs our Helpdesk for the study to be released. Get your submission account Fill the submission form and provide details of the data type and platform(s) in your submission. Register Study/DAC Use EGA Programmatic submission to register your study, samples, Data Access Committee (DAC) and Policy. Upload data Encrypt your data files using the EgaCryptor and upload it using default FTP clients or Aspera. Complete the Array-Format (AF) spreadsheet Download the AF spreadsheet and complete all four sections. Return the spreadsheet to the EGA helpdesk. Release and admin Instruct our Helpdesk to release your study. All registered studies are automatically placed on hold until the named submission or DAC contact instructs our Helpdesk for the study to be released.

  Documentation submission/quickguide