22951 results for "ega"

in 32.61 milliseconds.

• Geographic variation of mutagenic exposures in kidney cancer genomes – filtered vcf files (Mutographs)

  Geographic variation of mutagenic exposures in kidney cancer genomes – filtered vcf files (Mutographs)

  Dataset EGAD00001012222

• Geographic variation of mutagenic exposures in kidney cancer genomes – patient metadata files (Mutographs)

  Geographic variation of mutagenic exposures in kidney cancer genomes – patient metadata files (Mutographs)

  Dataset EGAD00001012223

• Geographic variation of mutagenic exposures in kidney cancer genomes – copy number variants (Mutographs)

  Geographic variation of mutagenic exposures in kidney cancer genomes – copy number variants (Mutographs)

  Dataset EGAD00001013727

• Genome and transcriptome sequence data from a neuroblastoma tumor patient

  Genome and transcriptome sequence data from a neuroblastoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015264

• Genome and transcriptome sequence data from a neuroblastoma tumor patient

  Genome and transcriptome sequence data from a neuroblastoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015265

• Genome and transcriptome sequence data from a neuroblastoma tumor patient

  Genome and transcriptome sequence data from a neuroblastoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015267

• Genome and transcriptome sequence data from a osteosarcoma tumor patient

  Genome and transcriptome sequence data from a osteosarcoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015270

• Genome and transcriptome sequence data from a craniopharyngioma tumor patient

  Genome and transcriptome sequence data from a craniopharyngioma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015273

• Genome and transcriptome sequence data from a neuroblastoma tumor patient

  Genome and transcriptome sequence data from a neuroblastoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015277

• Genome and transcriptome sequence data from a osteosarcoma tumor patient

  Genome and transcriptome sequence data from a osteosarcoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015278

• Genome and transcriptome sequence data from a angiosarcoma tumor patient

  Genome and transcriptome sequence data from a angiosarcoma patient, generated as part of the BC Cancer Agency's Pediatric Personalized Onco-Genomics study

  Dataset EGAD00001015290

• Genotype-Tissue Expression (GTEx) (2025-07-28)

  Dual snRNAseq and ATACseq of replicate PBMC samples for 10X beta testing. . This dataset contains all the data available for this study on 2025-07-28.

  Dataset EGAD00001015663

• Vulval Squamous Cell Carcinoma Spatial Transcriptomics

  This dataset contains raw paired-end fastq files from 10x Genomics Visium spatial transcriptomics platform of four early-stage VSCC cases (PMID: 39787746)

  Dataset EGAD00001015461

• TrypanoGen+ Microbiome

  TrypanoGen+ data containing fastq files from 138 samples.

  Dataset EGAD00001015464

• Geographic and age-related variations in mutational processes in colorectal cancer - sequence data (Mutographs)

  Geographic and age-related variations in mutational processes in colorectal cancer - sequence data (Mutographs)

  Dataset EGAD00001015485

• HCA Organoids | Colon - Cancer, Multiome Sequencing Data

  Multiome sequencing of patient tissue and patient derived organoids in colon cancer

  Dataset EGAD00001015504

• How to upload Crypt4GH files

  Uploading files Users who hold 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. To manage the available resources, we enforce a limit of 10TB per submission account at any one time. If you exceed this limit, a “permission denied” message will be displayed. This will prevent you from uploading more files, but connecting to your inbox.For submissions larger than 10TB, please perform uploads in 10TB batches: register all the metadata and then finalise the submission. Upload the next batch of files and repeat the same metadata registration and finalisation process until you have completed the file upload. Further information can be found in the SP documentation. INBOX FTP The INBOX is only compatible with files encrypted using the Crypt4gh tool Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated, you will be able to request a submitter role. [Optional] Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g., ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. To upload files to your account, you can use the graphical user interface (GUI) or the command line. Graphical User Interface (GUI)We recommend using FileZilla, a free, open-source FTP client. However, you can use any other GUI that allows connecting over the SFTP protocol. For FileZilla as your GUI, follow these steps to upload files: Create a new connection in Site Manager (File > Site Manager) and select the following options (Figure 1): Protocol: SFTP - SSH File Transfer ProtocolHost: __EGA_INBOX_DOMAIN__Logon Type: Key fileUser: your EGA usernameKey file: Path/to/your/private_keyFigure 1: Process of establishing a new connection to __EGA_INBOX_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 inbox, ensuring seamless data transfers.Click Connect, and you will log in remotely to your home directory. You can think of this folder as a storage "in the EGA cloud" in which you will add your files for the EGA. The uploading area has three folders:To-encrypt: Files uploaded in this folder will be encrypted automatically on the fly.Encrypted: Files uploaded in this folder must already be encrypted with Crypt4gh. Upload your files here if your connection is unstable or you have problems completing the upload into-encrypt.Etc: This folder contains two files that allow the server to show you your username and group instead of some internal numbers. Please do not upload files here; otherwise, you will obtain a permission denied error. Find the files you want to upload by browsing your local storage (left side of your screen in FileZilla). Select all the files you want to upload, then right-click on them and select Upload (Figure 2). Figure 2: Step-by-step process of manually uploading files to __EGA_INBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can transfer data from their local storage to the "EGA cloud" by following the depicted steps Please note that regardless of which folder you upload your files in, both folders (to-encrypt, encrypted) will point to the same path (/) (Figure 3). Therefore, you will see your files in both folders. Figure 3: Both folders, to-encrypt and encrypted, point to the same path (/)" If your connection is unstable, please encrypt your files first using Crypt4gh. Then upload them to the ‘encrypted’ folder. The example above shows how to connect to __EGA_INBOX_DOMAIN__ using the private key. However, if you prefer to log in using your credentials, you can do so. Please go to the Frequently Asked Questions (FAQs)  for more information. SFTP command line To upload files securely to your private area of the EGA, you can use SFTP(Secure File Transfer Protocol) with your favorite FTP client. Here's what you need to know to get started: Connect to the target host __EGA_INBOX_DOMAIN__. This is the new hostname for the EGA SFTP service. Log in with your EGA username and key files (or password). Upload files to your private EGA inbox to ensure that only you can access the files. By following these steps, you can securely upload your files to the EGA for safe storage and sharing. Using the SFTP command line client in Linux/Unix Open a terminal and type sftp username@hostnameEnter your EGA passwordTo see a list of available SFTP commands, type helpsftp> put – Upload filesftp> get – Download filesftp> cd path – Change remote directory to ‘path’sftp> pwd – Display remote working directorysftp> lcd path – Change the local directory to ‘path’sftp> lpwd – Display local working directorysftp> ls – Display the contents of the remote working directorysftp> lls – Display the contents of the local working directoryType the "put" command to upload files. For example: put *.bamUse the bye command to close the connection (SFTP session). After uploading- Once you have uploaded files to the inbox, please bear in mind that the checksum needs to be calculated, which can take up to two days. You will only be able to link your files to a run/analysis once the encrypted checksum has been calculated.- When linking your files to the 'Run' or 'Analysis', ensure that the file name matches the file path '/name' in the INBOX folder.- Please delete the files from your SFTP INBOX after all the runs/analyses have been registered and files are ingested (SP > Files > Files ingested). This will clear your inbox space an allow you to upload more files. This will also prevent the files from reappearing in your Submitter Portal inbox. Frequently Asked Questions Specific to the inbox What username should I use to log in to my inbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username.  If you have forgotten your registered username, please contact our Helpdesk team for assistance. How are checksums calculated in your inbox? If you encrypt the file beforehand and upload it to the "encrypted" folder, the unencrypted checksum will not be calculated until the file is ingested (i.e., until it is used in a run/analysis). If the file is uploaded to the "to-encrypt" folder, then both checksums are calculated.Please bear in mind that after files have been uploaded to the inbox, the checksum must be calculated, which can take from a few hours to two days.  Specific to using keys to authenticate 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_INBOX_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 submission/data/uploading-files/inbox

• WTCCC case-control study for Breast cancer - Combined Controls

  WTCCC genome-wide case-control association study for Breast cancer (BC) - Combined Controls.

  Study EGAS00000000025

• Genome-wide association study of severe malaria in Gambian mother-father-child trios

  Genome-wide association study of severe malaria in Gambian mother-father-child trios

  Study EGAS00000000087

• Genome-wide association study of severe malaria in Ghanain mother-farther-child trios

  Genome-wide association study of severe malaria in Ghanain mother-farther-child trios

  Study EGAS00000000088

• EGAD00000000006

  WTCCC1 project Hypertension (HT) samples

  Dataset EGAD00000000006

• EGAD00010000742

  Subset 1 of osteoarthritis cases genotyped on Illumina610k from the arcOGEN Consortium (http://www.arcogen.org.uk/) with broader consent.

  Dataset EGAD00010000742

• EGAD00010000768

  Replication data for HipSci normal samples using both HumanCoreExome-12_v1 and HumanOmni2.5-8 BeadChips

  Dataset EGAD00010000768

• Tandem duplication of chromosomal segments is common in ovarian and breast cancer genomes

  Tandem duplication of chromosomal segments is common in ovarian and breast cancer genomes

  Dataset EGAD00001000050

• Single-cell genome sequencing reveals DNA-mutation per cell cycle

  Single-cell genome sequencing reveals DNA-mutation per cell cycle

  Dataset EGAD00001000154

• Helleday_HRAS Project

  This experiment is looking at the mutational signatures generated by engineered HRAS mutations by using whole genome sequence generated on massively parallel next generation sequencers.

  Dataset EGAD00001000302

• Methylated DNA immunoprecipitation sequencing of untreated and castration resistant prostate cancer

  Methylated DNA immunoprecipitation sequencing of 28 untreated prostate cancers, 11 castration resistant prostate cancers, and 12 benign prostatic hyperplasias.

  Dataset EGAD00001000610

• Dataset for Parkinson's disease target re-sequencing project

  The dataset regards the sequencing of coding and putative regulatory sequences of 38 genes associated to either sporadic or Mendelian form of Parkinson's disease

  Dataset EGAD00001001029

• FASTQ NGS dataset for EGAS00001001632:New Brain Tumor Entities Emerge from Molecular Classification of CNS-PNETs

  Dataset EGAD00001001927

• pe_meta_20170131

  Inverse variance weighted fixed effect meta-analysis of three European GWAS studies of the offspring of Pre-eclampsia affected births (2658 Cases and 308267 Controls).

  Dataset EGAD00010001211

• OA_knee-G-1

  Genotyping of knee osteoarthritis patients who have undergone total joint replacement

  Dataset EGAD00010001285

• BBMRI - BIOS project - Freeze 2 - methylation

  BBMRI - BIOS project - Freeze 2 - methylation

  Dataset EGAD00010001416

• iPSC variation file (VCF) for EBiSC

  EBiSC Whole Genome Sequencing processed VCF including VEP consequences

  Dataset EGAD00001003934

• Whole exome sequencing Data from a child with ALPI deficiency and parents

  This dataset contains raw sequences (BAM files) of P1 trio: mother, father and affected child (P1). Whole exome sequencing (WES).

  Dataset EGAD00001004048

• Genomic alterations in MM - CEL

  RNA from the same tumor sample (n=98) was also processed using the 3' IVT kit (Affymetrix) and hybridized to U133 Plus 2.0 arrays (Affymetrix).

  Dataset EGAD00010001577

• DNA methylation of Rhabdomyosarcoma tumors

  DNA methylation data from patient RMS tumor samples from Illumina 450 K arays

  Dataset EGAD00010001596

• Yemen_Somali.Omni5

  The individuals were assayed for genome-wide SNP genotypes using the Illumina Human Omni5 Bead Chip (Illumina), which surveys 4,284,426 single nucleotide markers regularly spaced across the genome

  Dataset EGAD00010001651

• usgwas-no-QC_update

  Understanding Society GWAS, all samples

  Dataset EGAD00010000890

• CNV dataset

  Rare CNVs from schizophrenia cases and controls

  Dataset EGAD00010001074

• Colorectal cancer methylation profiling

  4 AC samples, each with adenoma, carcinoma and normal colon tissue (12 samples in total) were analysed on the Infinium MethylationEPIC BeadChip for copy number alteration analyses.

  Dataset EGAD00010001691

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

  Dataset EGAD00001005375

• MalariaGEN-MassArray_b37

  EGAS00001001311: Genome-wide study of resistance to severe malaria in eleven worldwide populations: Sequenom MassArray genotypes

  Dataset EGAD00010001799

• PromethION (and Illumina) WGS and MinION transcriptome for a patient with diffuse large B-cell lymphoma.

  Dataset EGAD00001006204

• PE-META-EUROPE_CENTRAL_ASIA-MATERNAL

  Fixed effect meta-analysis summary statistics combining GWAS of maternal preeclampsia cases and controls from Europe (UK, Iceland, Norway, Denmark and Finland) and Central Asia (Kazakhstan and Uzbekistan).

  Dataset EGAD00010001988

• PE-META-EUROPE_CENTRAL_ASIA-FETAL

  Fixed effect meta-analysis summary statistics combining GWAS of fetal (baby) preeclampsia cases and controls from Europe (UK, Iceland, Norway, and Denmark) and Central Asia (Kazakhstan and Uzbekistan).

  Dataset EGAD00010001983

• Normal pancreas cells cohort

  Mixed exocrine and purified ductal and de-differentiated acinar human cells obtained from normal pancreases. Ductal and de-differentiatedacinar cells where isolated by FACS after 4 days culture of the exocrine mixed population

  Dataset EGAD00010002007

• KuwaitPopGenetics

  Genome-wide Genotyping of 620 Arab individuals using Illumina iSelect platform with HumanOmniExpress bead chips

  Dataset EGAD00010002063

• methylation_mifepristone_set

  Raw methylation from breast biopsies in BRCA mutation carriers or controls before and after 3 months of preventive mifepristone treatment.

  Dataset EGAD00010002073

• P50_P681_P763_PTC209_DMSO_24h_48h_72h_Illumina HT12v4_Gene_Expression.xlsx

  Expression dataset for DAC+PTC209 treated CD34 sorted primary CML bone marrow samples

  Dataset EGAD00010002210

• Benchmark Dataset DIA Clinical Proteomics LymphNodes E.coli

  Real patient variability Benchmark Dataset for Optimization of DIA data analysis workflows

  Dataset EGAD00010002223