22992 results for "ega"

in 106.89 milliseconds.

• Flemish_Gut_Flora_Project_phenotype

  Here, we studied well-phenotyped individuals from the Flemish Gut Flora Project (FGFP, N=1,106, Belgium) and the effect of environments on microbiome. The 69 major significant phenotypes found in this study are provided.

  Dataset EGAD00001001943

• Illumina_WGS_MET-XEN

  Whole-genome sequencing on Illumina HiSeq2000/2500 of Patient-derived xenograft derived from colorectal cancer metastasis sample

  Dataset EGAD00001002087

• SCNA-Seq of plasma DNA samples

  Low coverage whole genome sequencing for the identification of somatic copy number alterations (SCNA) and focal amplification mapping in plasma DNA of prostate cancer patients

  Dataset EGAD00001002149

• Whole genome low pass sequencing data used in HF-GBM-Tumor-Neurosphere-Xenograft

  This data set consists of 82 whole genome low pass sequencing bams used in HF-GBM-Tumor-Neurosphere-Xenograft

  Dataset EGAD00001002245

• NeurOmics_HD_Biomarker-1_V1

  This data set includes RNAseq data from 136 samples from the TRACK-HD cohort including premanifest, manifest and control subjects. Data can only be used for Huntington's disease related research.

  Dataset EGAD00001002699

• Rare coding variants in lupus risk genes

  Set of 133 bam files from patients affected with Lupus. BAM alignments for exonic variants present in 76 Lupus-related genes. VCF file describing the variants.

  Dataset EGAD00001004859

• Dataset WES of RRMM patients

  Dataset consists of forty vcf files, outcome of variant calling with caveman algorithm of matched bam file (TUMOR and NORMAL) of RRMM patients. Bam files were obtained from whole exome sequencing!

  Dataset EGAD00001005098

• Whole exome sequence of intratumor heterogeneity study

  This dataset contains whole exome sequence data from 86 samples from 6 patient. All the experiments were performed on Illumina HiSeq platform with raw reads stored in fastq format.

  Dataset EGAD00001005453

• Ovarian cancer organoid biobank - followup

  WGS of more samples in the ovarian cancer organoid biobank dataset.

  Dataset EGAD00001005707

• De novo metastatic prostate cancer cohort

  Fastq files from RNA sequencing of normal and tumor samples from 16 patients from the de novo metastatic prostate cancer cohort.

  Dataset EGAD50000002381

• 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

• PCA Atlas Chromium scRNA-seq and demultiplexing support (FASTQs, BAMs, capture-level VCFs and mapping tables)

  This dataset contains Chromium single-cell RNA-seq data and demultiplexing support for the PCA Atlas study EGAS00001008332. Included data objects: - 16 Chromium scRNA-seq FASTQ runs (EGAR accessions) for captures PCa1–PCa16. - 16 aligned BAM analyses (one Cell Ranger possorted_genome_bam.bam per capture). - 16 capture-level genotype VCF analyses derived from the Axiom UK Biobank array, used as demultiplexing panels. - demux_map.csv (EGAZ00001945520): donor–capture–sample mapping for genotype-based demultiplexing. - chromium.csv (EGAZ00001945537): run-level mapping linking captures, EGA samples, runs (EGAR), experiments (EGAX) and BAM analyses. Together these objects provide a complete view of the Chromium scRNA-seq data and the genotype-based demultiplexing support needed to reproduce donor assignment and downstream analyses.See also https://zenodo.org/records/17372603

  Dataset EGAD00001015795

• atrial appendage RNA-seq in non-, paroxysmal and persistent atrial fibrillation

  64 left atrial appendages from patients without atrial fibrillation (AF) undergoing cardiac surgery, patients with paroxysmal AF and with persistent AF (~20 per group). Trizol RNA isolation, rRNA depletion, paired transcriptome sequencing on illumina NovaSeq 6000. Provided are FastQ and BAM files. Additional data (e.g. clinical characteristics, RIN values etc.) can be provided upon reasonable request. The same RNA samples (62 out of 64) were used for miRNA sequencing. Results from miRNA seuqencing are stored in the EGA database managed by the same DAC.

  Dataset EGAD00001007693

• Targeted sequencing of 72 prostate cancer driver in 712 plasma cell free DNA samples

  Dataset contains targeted sequencing data of 712 plasma cell free DNA samples and 428 white blood cell samples collected from 428 men with metastatic prostate cancer. Target capture was performed using a hydridization-based custom Roche SeqCap EZ Choice kit, designed to capture all exons of 72 prostate cancer driver genes. Cell free DNA was extracted from 10 mL blood samples. Libraries were sequenced using Illumina HiSeq 2500 or Illumina MiSeq instruments to a median coverage of 750x. 62% of samples had ctDNA fraction above 2% of total cfDNA. Note that "Dataset type" is erroneously listed as "Amplicon sequencing", because "Captured-based targeted sequencing" or "Hybridization-based targeted sequencing" were not available options in EGA at the time of submission.

  Dataset EGAD00001004208

• HELIUS cohort

  The gut microbiota composition is unique to every individual but is shaped by common factors including diet, lifestyle, medication use, early-life determinants, living environment or genetics. Most of these factors may be influenced by ethnicity. This study explored variations in fecal microbiota composition in 6048 individuals with different ethnic backgrounds living in the same geographical area (Amsterdam, the Netherlands). The HELIUS data are owned by the Amsterdam University Medical Centers, location AMC in Amsterdam, The Netherlands. To allow sharing of microbiome data collected in HELIUS with (inter)national researchers, 16s rRNA sequence analysis has been stored at the European genome-phenome archive (EGA; accession code EGAD00001004106). This requires that access needs to be granted, also because the HELIUS data are stored with relevant phenotypical variables. Access is granted to all researchers affiliated with an internationally recognized research institution who request to use the HELIUS data within the EGA context, after having signed the data transfer agreement. Any researcher can request the data by submitting a proposal to the HELIUS Executive Board as outlined at http://www.heliusstudy.nl/en/researchers/collaboration, by email: heliuscoordinator at amsterdamumc dot nl. The HELIUS Executive Board will check proposals if they do not conflict with ethical approvals and informed consent forms of the HELIUS study.

  Study EGAS00001002969

• WTCCC case-control study for Autoimmune Thyroid Disease - Combined Controls

  WTCCC genome-wide case-control association study for Autoimmune Thyroid Disease (ATD) - Combined Controls.

  Study EGAS00000000021

• WTCCC2 Pharmacogenomic Response to Statins study

  A WTCCC2 project genome-wide study for pharmacogenomic response to statins (PR) in individuals from Scotland.

  Study EGAS00000000121

• HLA has strongest association with IgA nephropathy in genome-wide analysis

  GWAS study of families with probands with IgA nephropathy from the UK Glomerulonephritis DNA bank

  Study EGAS00000000031

• Sequencing data (BAM files) from - A mutation in VPS15 (PIK3R4) causes a ciliopathy and affects IFT20 release from the cis-Golgi. The Data Access Committee (DAC) is responsible for sequencing data release to external requestors based on consent and/or National Research Ethics terms.

  Dac EGAC00001000552

• EGAD00000000004

  WTCCC1 project Coronary Artery Disease (CAD) samples

  Dataset EGAD00000000004

• EGAD00000000005

  WTCCC1 project Inflammatory Bowel Disease (IBD) samples

  Dataset EGAD00000000005

• EGAD00010000744

  Subset 2 of osteoarthritis cases genotyped on Illumina 610k from the arcOGEN Consortium (http://www.arcogen.org.uk/) with consent for osteoarthritis studies only.

  Dataset EGAD00010000744

• EGAD00010000434

  Normalised mRNA expression

  Dataset EGAD00010000434

• EGAD00010000438

  Normalized miRNA expression data

  Dataset EGAD00010000438