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

in 15.08 milliseconds.

• Highly differentiated, fusion-negative rhabdomyosarcoma.

  Sequencing was performed using OncoPanel v.2 (OPv2), an Agilent SureSelect custom designed bait set consisting of the coding regions of 504 genes, previously linked to human cancer. Sequencing wa sperformed on an Illumina HiSeq 2500. 14 highly differentiated, fusion-negative rhabdomyosarcoma tumor samples, and 8 non-matched normal skeletal muscle samples weer sequenced. BAM files are available for download.

  Dataset EGAD00001003746

• Distribution of data using Live Distribution

  Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation access/download/files/live-outbox

• The Chinese University of Hong Kong Hereditary Spastic Paraplegia Data

  The dataset contains the whole genome sequencing data of a family with two unaffected parents and two probands that showed Hereditary spastic paraplegias symptoms. Sequencing reads were aligned to human genome (GRCh38) using BWA-MEM, followed by indel-realignment and PCR-duplicates marking. Alignment results are available for download in BAM format.

  Dataset EGAD00001002146

• GWAS for Membranous Nephropathy

  Primary membranous nephropathy (MN) is a rare autoimmune cause of kidney failure. This dataset is from a genome-wide association study (GWAS) designed to identify novel genetic risk loci for MN. The provided cohort (named as European-1 Cohort) is composed of 611 cases of primary MN and 1,246 healthy controls of European ancestry. This cohort was used in the GWAS meta-analysis, as described in the manuscript entitled "Genetic architecture of membranous nephropathy and its potential diagnostic implications" (Nature Communications 2020, in press).The genome-wide summary statistics, including trans-ethnic meta-analysis across 8 GWAS cohorts of European and East Asian ancestry and ethnicity specific meta-analyses, are freely available for download on the Kiryluk lab website: http://www.columbiamedicine.org/divisions/kiryluk/resources.php.

  Study phs001984

• Phase II Therapeutic Trial of Mexiletine in Non-Dystrophic Myotonia (IND #77,021)

  Non-dystrophic myotonias are a group of rare muscle disorders caused by abnormalities in different muscle cell membrane proteins. Patients experience delayed muscle relaxation that causes impaired physical activity, stiffness, and pain. Mexiletine has been shown to be beneficial for symptoms of myotonia in case reports of patients with non-dystrophic myotonia, however, current management of these patients primarily depends on individual practitioners&#39; preference. This study is a placebo-controlled, double-blind, cross-over treatment trial using mexiletine in non-dystrophic myotonias. The results, if positive, will permit the identification of mexiletine as an effective therapy for myotonia, making it a first-line therapy for patients with non-dystrophic myotonia. The specific aim of this proposal is to perform a randomized, double-blind, placebo-controlled cross-over study to assess whether mexiletine improves both quantitative and qualitative measures of myotonia in patients with non-dystrophic myotonia. Given the rarity of non-dystrophic myotonia, large randomized controlled treatment trials in these disorders have not been feasible in the past. Primary Outcome Measure: Patient-assessed symptom: stiffness as measured by an Interactive Voice Response Diary (IVR). Secondary Outcome Measures: a) patient-assessed pain, weakness, and fatigue as measured by IVR; b) clinical myotonia assessment; c) quality of life as measured by INQoL, SF36; d) a quantitative measure of grip myotonia; e) measurement of CMAP after short and long exercise; f) grading of myotonia on needle EMG.

  Study phs001311

• Data access policy

  Investigators who download restricted data from this dataset should: - Not attempt to identify individual human research participants from whom the data were obtained. - Acknowledge in all oral or written presentations, disclosures, or publications the specific dataset(s) or applicable accession number(s) and the repositories through which the investigator accessed any data. Any user requesting access to this data must apply for authorization, which is granted by the Data Access Committee (DAC). The DAC will review and approve or disapprove all requests from the research community for data access. Decisions to grant access are made based on whether the request conforms to the specifications of the Research Ethics Committee approval and program specific requirements or procedures (if any).

  Dac EGAC50000000504

• Download Metadata

  Metadata Distribution Welcome to the realm of Metadata Distribution within the EGA ecosystem! Our Metadata REST API empowers you to effortlessly retrieve metadata from the expansive landscape of EGA. By utilising this API, you gain access to publicly available insights across various EGA domains, including studies, samples, experiments, runs, analyses, policies, DACs, and datasets. Furthermore, this API facilitates cross-referencing of objects, enabling you to gather, for example, all the datasets associated with a specific DAC, seamlessly. In addition, we have added the ability to query private data using the metadata API. If you possess the necessary permissions, you can access behind-the-login private data for a specified list of datasets. Metadata Distribution Index Identifiers Dataset Mappings Website Download Metadata API - Private Identifiers At the core of EGA's organisational structure are unique accessions that serve as essential tags for our diverse objects. Here's a quick overview of the accessions and their corresponding object types: EGA Accession ID EGA Object description EGAS EGA Study Accession ID EGAC EGA DAC Accession ID EGAP EGA Policy Accession ID EGAN EGA Sample Accession ID EGAR EGA Run Accession ID EGAX EGA Experiment ID EGAZ EGA Analysis Accession ID EGAD EGA Dataset Accession ID EGAB EGA Submission ID EGAF EGA File Unique Accession ID For further information check our metadata schema documentation. Dataset Mappings For authorised datasets, comprehensive mappings reveal meaningful connections: Sample_file: This file presents information about the linkage between samples and files available in the dataset. Study_experiment_run_sample: This file presents information about the linkage between studies, experiments, runs, and samples within the dataset. Study_analysis_sample: This file presents information about the linkage between studies, analyses, and samples contained within the dataset. Run_sample: This file presents information about the linkage between runs and samples within the dataset. Analysis_sample: This file presents information about the linkage between analyses and samples within the dataset. An empty file indicates the absence of corresponding information. Website Download Our website serves as your gateway to downloading metadata. Simply navigate to the dataset page, and you'll find a blue Metadata button. Once authenticated, you can click this button for authorised datasets. If you lack permissions for a particular dataset, request access by clicking the 'Request Access' button. For authorised datasets, choose your preferred metadata format: CSV, TSV, or JSON. Metadata API - Private Leverage the power of programmatic metadata downloads! Start by authenticating yourself with your credentials to obtain an access token. With this token, programmatically query private information. Queries mirror the structure of the Public Metadata API. However, behind the login, you can delve into specific mapping information (as mentioned above in dataset mappings) alongside object-level exploration. Authentication An active session is required to work with the API. Each time you log in with your credentials a new session is started, which is identified by an access_token. Below an example on how to obtain one using curl: curl https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token \ -d 'client_id=metadata-api' \ -d 'username=...' \ --data-urlencode 'password=...' \ -d 'grant_type=password' All responses from the API are in JSON format. A successful response should include a new token to be used for the session: {"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiA...TNw", "expires_in":300, "refresh_expires_in":1800, "refresh_token":"eyJhbGciOiJIUzI1NiIsInR5cCIgOiA...pTX10", "token_type":"Bearer", ... } Save the access_token value and include it in the API call headers. Example query usage Below you can find some example of queries available behing authentication and authorisation. Querying study-experiment-run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_experiment_run_sample \ -H 'Authorization: Bearer access_token' Querying run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/run_sample \ -H 'Authorization: Bearer access_token' Querying study-analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_analysis_sample \ -H 'Authorization: Bearer access_token' Querying analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/analysis_sample \ -H 'Authorization: Bearer access_token' Querying sample-file mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/sample_file \ -H 'Authorization: Bearer access_token' You can get a different output format by adding one of these options to the curl command: -H 'Accept: text/tsv' -H 'Accept: application/json' -H 'Accept: text/csv' For more detailed information, refer to the Metadata API Specification.

  Documentation access/download/metadata

• Archive growth Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue In this section, we expose the overall volume of data available to download and the different archived file types. EGA Archive growth in size and number of files The below figure represents the EGA archive growth in size (TB) and number of files. EGA Archive Growth per year lineChart('ega-archive-growth', 'https://stats.ega-archive.org/growth/archive', ['Volume (TB)'], ['T']) Archive files The below figure represents on a initial level, the percentage of archived files by data technology. The second level, acessible by clicking in the required extension, displays the number of files by extension archived in the ega archive. Please click over the extension to learn more about the files. EGA Archived Files barChart('ega-archived-files', 'https://stats.ega-archive.org/extensions', false ,'', true)

  Documentation about/statistics/archive

• Human Liver Cohort (HLC)

  The Human Liver Cohort (HLC) study aimed to characterize the genetic architecture of gene expression in human liver using genotyping, gene expression profiling, and enzyme activity measurements of Cytochrom P450. The HLC was assembled from a total of 780 liver samples screened. DNA samples were genotyped on the Affymetrix 500K SNP and Illumina 650Y SNP genotyping arrays. Only data from those samples which were collected postmortem are accessible through this submission. These 228 samples represent a subset of the 427 samples included in the Human Liver Cohort Publication (Schadt, Molony et al. 2008, PMID: 18462017). RNA samples were profiled on a custom Agilent 44,000 feature microarray composed of 39,280 oligonucleotide probes targeting transcripts representing 34,266 known and predicted genes, including high-confidence, noncoding RNA sequences. Gene Expression data for the samples from which it could be obtained is available in GEO under accession number GSE9588. Results and networks will be made available for download from Sage Bionetworks.

  Study phs000253

• Pomalidomide for the Treatment of Bleeding in HHT (PATH-HHT)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To determine efficacy (reduction in severity of epistaxis), tolerability, and improvement in quality of life of pomalidomide compared to placebo after 24 weeks of treatment.Background: This study addresses the efficacy of pomalidomide in the treatment of epistaxis in patients with Hereditary Hemorrhagic Telangiectasia (HHT) who have anemia and/or require blood transfusion or iron infusion for treatment of bleeding-induced anemia and iron deficiency. HHT (also known as Osler-Weber-Rendu disease) is an inherited bleeding disorder. Over 95% of patients develop recurrent epistaxis, which may be severe and result in chronic anemia, need for iron infusions and blood transfusions, substantial psychiatric comorbidity (including depression and post-traumatic stress disorder) and reduction in health-related quality of life (HRQoL). HHT is clinically diagnosed using the Curacao criteria, which consists of 1) spontaneous and recurrent epistaxis, 2) telangiectasias at characteristic sites, 3) visceral arteriovenous malformations (AVMs) or telangiectasias, and 4) a first degree relative with HHT (inheritance is usually autosomal dominant). Patients with three criteria are considered to have definite HHT, and those with 2 criteria probable HHT. HHT affects approximately 1 in 3,800 individuals. Significant manifestations of HHT often do not appear until the third or fourth decades, sometimes later.Participants: 144 patients from 11 clinical centers were enrolled.Design: This is a multi-center, double blind, randomized placebo-controlled trial that investigated the efficacy and safety of pomalidomide in patients with HHT and chronic epistaxis leading to iron-deficiency anemia or requiring intravenous iron infusions or blood transfusion.Screening evaluation included the Epistaxis Severity Score (ESS) with three-month recall, which reflected the patient's history of epistaxis and bleeding over the prior three months, as well as detailed review of iron infusion and red cell transfusion over the preceding six months. Eligible patients were provided a diary to record the duration of each epistaxis event that occurred during the 4 weeks prior to the baseline visit, and then returned for the baseline randomization visit, at which time patients underwent genetic testing, if this had not been previously performed, and completed an ESS with 4-week recall and quality of life assessments. Patients were randomized 2:1, stratified by study site, to either pomalidomide 4 mg/day or matching placebo during each of six 28 day cycles (24 weeks). Patients were seen every four weeks during treatment, and at a 4-week post-treatment follow-up visit to measure the ESS (with 4-week recall), laboratory assessments including iron stores and need for iron infusion, CBC, and metabolic profile. Patients were assessed for adverse events (AE) throughout the study. Treatment dosage could be reduced, or temporarily or permanently discontinued following AE-specific guidelines related to fatigue, cytopenias or other toxicities.Quality of life assessments were completed at baseline, and the 12- and 24-week visits, and the 4-week post-treatment follow-up visit using validated NIH instruments of 1) Neuro-QOL satisfaction with social roles and activities, 2) PROMIS emotional distress &#8211; depression, and 3) PROMIS fatigue, and the HHT-specific quality of life instrument developed specifically for this study. The effect of pomalidomide on duration of epistaxis was assessed via diary between weeks 8-12, 20-24 and the 4-week post-treatment period.Conclusions: Among patients with HHT, pomalidomide treatment resulted in a significant, clinically relevant reduction in epistaxis severity. No unexpected safety signals were identified (Al-Samkari et al., 2024; PMID: 39292928)

  Study phs003948

• About

  About What's the EGA? The European Genome-phenome Archive (EGA) is a global network for permanent archiving and sharing of personally identifiable genetic, phenotypic, and clinical data generated for the purposes of biomedical research projects or in the context of research-focused healthcare systems. Jointly managed by the European Bioinformatics Institute (EMBL-EBI) in Cambridge (UK) and the Centre for Genomic Regulation (CRG) in Barcelona, we aim to advance biomedical research and promote personalised medicine worldwide by enabling discovery of and access to human genomic and health research data. The EGA contains data collected from individuals whose consent agreements authorise data release for specific research use to bona fide researchers. We ensure strict security measures to control access to the data and maintain patient confidentiality. With expertise in data management and technical infrastructure, we promote FAIR data reuse and enable researchers to share their data securely. By leveraging public funding and our strategic partnerships, the EGA provides a free service for permanent data storage, data discovery, and secure data access. In addition, we foster a federated network to provide transnational access to human research data in compliance with legal frameworks. For additional information about the EGA, please contact: Helen Parkinson and Mallory Freeberg EMBL European Bioinformatics Institute Arcadi Navarro, Roderic Guigó, and Jordi Rambla Center for Genomic Regulation History The European Genome-phenome Archive was launched in 2008 at the European Bioinformatics Institute (EMBL-EBI), an outstation of the European Molecular Biology Laboratory (EMBL), to address an identified need for archiving and sharing the results of genome-wide association studies from the Wellcome Trust Case Control Consortium. With the signing of a memorandum of understanding in 2013 and a formal agreement in 2016, the EGA became a joint project of EMBL-EBI and the Centre for Genomic Regulation (CRG). The two institutes work together to support the EGA services, including supporting submissions, website, strategic leadership, and data infrastructure developments. In 2022, the Federated EGA was officially launched with the signature of the first five countries: Finland, Germany, Norway, Spain, and Sweden. With more than 20 additional nodes worldwide preparing to join, the Federated EGA aims to become the largest human omics data sharing initiative towards understanding human health and disease. EGA overview If you're a researcher you may need to deposit, manage, or access genomic data in a secure and regulated way. The European Genome-phenome Archive (EGA) is a platform that facilitates these processes, ensuring that sensitive data is stored and shared in accordance with legal and ethical regulations. Submission process To start a submission, you need to become an EGA submitter. For that, you’ll need to sign a Data Processing Agreement (DPA) with us, that defines the terms and conditions under which your data will be processed and shared within the EGA system. The access to each study is controlled by its Data Access Committee (DAC). The DAC is responsible for managing data access requests and ensuring that the release of data is in accordance with the General Data Protection Regulation (GDPR). Please, note that once your data is released, all public metadata related to your study and dataset(s) will be searchable on the EGA website. However, the files are only accessible under controlled access, which means that a DAC has to agree to a previous data access request. Request process It is possible to submit an access request to data stored at the EGA. The DAC assigned to the study will assess the request and, if approved, grant access to the data. Requesters must provide sufficient justification for your request and comply with the intended data usage in order to get access to it. Each dataset is covered by a Data Access Agreement (DAA) that defines the terms and conditions of use for the specified dataset/s. The DAA is created and provided by the DAC, and must be signed by the individual requesting access to the given dataset/s. Download process Once the request for access is approved, the data and metadata can be downloaded. The EGA offers various download options to fit the needs: it is possible to preview files without downloading them, download specific files of interest, or even download terabytes of data. Overall, the EGA provides a secure and regulated environment for depositing, managing, and accessing human data. Regardless of the role - submitter, DAC member, or requester - the EGA provides assistance for each while ensuring that sensitive data is managed in an ethical and responsible manner. More information on how EGA handles data is available in the EGA dataflow.

  Documentation about/ega

• COVID-19 Multiomics Atlas

  We provide a single-nuclei RNA-sequencing (snRNA-seq) dataset derived from four COVID-19 patients, generated using the 10x Chromium Next GEM Single Cell v3.1 kit. For our study, these were integrated with snRNA-seq data with 12 publicly available sc/snRNA-seq datasets, comprising organ donor lung samples (n=89) and COVID-19 lung tissue samples (n=51). Additionally, we provide a spatial transcriptomic dataset characterizing different histopathological stages of diffuse alveolar damage, across a cohort of 33 COVID-19 patients. This was generated using the Nanostring Whole Transcriptome Assay (WTA) with regions of interest (ROIs) sized 400 µm² each. This integrated multi-omics analysis of snRNA-seq, histology, and spatial transcriptomics data, is available for exploration and download via our web portal: https://covid19-multiomicatlas.cellgeni.sanger.ac.uk/.

  Dataset EGAD00001015404

• 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

• Human Pilocytic Astrocytoma Single Cell RNA Sequencing

  Pilocytic astrocytoma (PA), the most common childhood brain tumor, is a low-grade glioma with a single driver BRAF rearrangement. Here, we perform scRNAseq in six PAs using methods that enabled detection of the rearrangement. When compared to higher-grade gliomas, a strikingly higher proportion of the PA cancer cells exhibit a differentiated, astrocyte-like phenotype. A smaller proportion of cells exhibit a progenitor-like phenotype with evidence of proliferation. These express a mitogen-activated protein kinase (MAPK) program that was absent from higher-grade gliomas. Immune cells, especially microglia, comprise 40% of all cells in the PAs and account for differences in bulk expression profiles between tumor locations and subtypes. These data indicate that MAPK signaling is restricted to relatively undifferentiated cancer cells in PA, with implications for investigational therapies directed at this pathway. Note that 931 out of 1234 samples in the Sequence Read Archive (SRA) passed QC and have transcript count data available from the Broad Institute Single Cell Portal. The transcript count data can be found at https://singlecell.broadinstitute.org/single_cell/study/SCP271/pilocytic-astrocytoma-single-cell-rna-seq#study-download

  Study phs001854

• European Genome-phenome Archive 15th Anniversary Celebration

  2023 marks the 15th Anniversary of the EGA, jointly managed by the European Bioinformatics Institute (EMBL-EBI) and the Centre for Genomic Regulation (CRG). To mark the occasion, a simultaneous celebration was held in both institutions on the 13th of December 2023. The teams gathered online to play a quiz game and celebrate all the achievements and milestones with two wonderful anniversary cakes. In 2008, the European Genome-phenome Archive was created at the EBI-EMBL in Cambridge to guarantee that human genome and phenome data were available to the international scientific community while data privacy was preserved. The six-person staff at the beginning of the project is now far behind us, with a team that reaches the number of 35 members. Since 2013, the European Bioinformatics Institute and the Centre for Genomic Regulation share responsibility for The European Genome-phenome Archive (EGA). At that time, the EGA had data for about 0,5 petabytes. Currently, the Archive contains more than 12 petabytes. 2023 comes to an end with several good news. The EGA has been renewed as an ELIXIR Core Data Resource. This was announced during the GA4GH 11th Plenary held in San Francisco last September when ELIXIR-Beacon was also confirmed to be a GA4GH Driver Project. Thus, the Beacon API has maintained this title since 2018. What’s more, the first Federated EGA dataset is now live on our website. This year we also launched new services for EGA users in September. By the numbers, in 2023 the EGA counts 2.5 PB archived, 371 studies published, 208 new submitters and 19 active projects in which the team is participating, among others. We look forward to continuing to support your research in 2024!

  Blog 15-anniversary

• 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 &#8220;Authorized Access&#8221; 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&#39;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