This study consists of the spatial transcriptomics data generated by : 1. Visium CytAssist Spatial Gene Expression for FFPE (10x) for steatotic liver disease-associated hepatocellular carcinoma (SLD-HCC) (n=7) and non-SLD-HCC (n=5) 2. CosMxTM Human Universal Cell Characterization RNA Panel (1000-plex); NanoString, USA for n=4 SLD-HCC and n=4 non-SLD-HCC. The goal of this data is to compare SLD-HCC vs non-SLD-HCC as well as response to immunotherapy
In order to confirm the predicted impact of the PD-associated allele of rs144814361 on BAG3 promoter, we proceeded with genome editing of the TH-REP1 cell line by using prime editing to insert the “T” allele at the position chr10:119651405 in the BAG3 promoter. 3 replicates for each condition: 1) iPSC Wild Type 2) SNP-BAG3 variant in iPSC 3) SNP-BAG3 variant in smNPC. Allelic imbalance is further assessed using read counting at this specific position.
This study entails whole genome sequencing of an interleukin (IL)-12 b-1 receptor-deficient individual who presented with a chronic systemic Salmonella Enteritidis infection that did not resolve with standard IFNg and antibiotic treatment. Whole genome sequencing of the patient’s parents are also included.This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/
Brain metastasis (BM) of colorectal cancer (CRC) is rare but lethal, and lacks effective therapies or a good understanding of its genomic landscapes. We conduct an analysis of whole-exome sequencing (WES) and whole-genome sequencing (WGS) data on 19 trios of patient-matched BMs, primary CRC tumors, and adjacent normal tissue to (1) document genomic signatures during the evolution of CRC BM; (2) identify clinically actionable targets for the BM treatment; and (3) identify potential drivers in CRC BM.
Solve-RD – solving the unsolved rare diseases is a research project funded by the European Union’s Horizon 2020 research and innovation programme under grant agreement No 779257 from 1 January 2018 to 31 March 2024. Six European Reference Networks (ERNs; ERN-RND, -ITHACA, -EuroNMD, -GENTURIS, -RITA and -EpiCare) contributed data and samples to one or more of the four cohorts for data re-analysis and novel omics. For more information see https://solve-rd.eu/results/solve-rd-data/.
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.
Patients included in this study were over 18 years of age and had a histology-confirmed diagnosis of glioblastoma multiforme (GBM). Exclusion criteria were the previous administration of any anti-tumor therapy including radiation therapy. All patients gave written informed consent. The study was approved by the local ethics committee (TUM Medical school) and conducted following the Declaration of Helsinki. During resection of the tumors, tumor tissue and tissue from normal appearing brain within the operative channel was collected. Blood was drawn during the surgical procedure. Single cell suspensions were prepared from the tumor tissue, the normal appearing brain, and the blood. CD4+ T cells and CD8+ T cells were sorted by flow cytometry. Only patients with a complete set of specimens (CD4+ tumor infiltrating lymphocytes (TIL), CD8+ TIL, CD4+ T cells from normal appearing brain, CD8+ T cells from normal appearing brain, blood-derived CD4+ and CD8+ T cells) containing a minimum of 1000 cells in each sorted sample were further analyzed (n=9). Total RNA was isolated from sorted cell populations using the RNAeasy Plus micro kit (Qiagen, 74034). Quality and integrity of total RNA was controlled on a Bioanalyzer 2100 (Agilent Technologies). Library preparation for bulk-sequencing of poly(A)-RNA was done as described previously (Parekh et al., 2016). Briefly, barcoded cDNA of each sample was generated with a Maxima RT polymerase (ThermoFisher Scientific, EP0742) using oligo-dT primer containing barcodes, unique molecular identifiers (UMIs) and an adaptor. Ends of the cDNAs were extended by a template switch oligo (TSO) and full-length cDNA was amplified with primers binding to the TSO-site and the adaptor. NEB UltraII FS kit was used to fragment cDNA. After end repair and A-tailing, a TruSeq adapter was ligated and 3'-end-fragments were finally amplified using primers with Illumina P5 and P7 overhangs. In comparison to previous descriptions (Parekh et al., 2016), the P5 and P7 sites were exchanged to allow sequencing of the cDNA in read 1 and barcodes and UMIs in read 2 to achieve a better cluster recognition. The library was sequenced on a NextSeq 500 (Illumina) with 59 cycles for the cDNA in read 1 and 16 cycles for the barcodes and UMIs in read 2. Data were processed using the published Drop-seq pipeline (v1.0) to generate sample- and gene-wise UMI tables (Macosko et al., 2015). Reference genome (GRCh38) was used for alignment. Transcript and gene definitions were used according to the Genecode Annotation Version 35.
Clinical data suggest that BMI and gestational weight gain (GWG) are strongly interconnected phenotypes, however the genetic basis of the latter is rather unclear. Here we aim to investigate the genetic factors associated with GWG from the perspective of the genetics of obesity.
This is a study of 100 patients with the aim to provide transcriptomic sequencing data analysis of cells isolated from bronchioalveolar lavage and blood samples from critically ill patients with pneumonia on an intensive care unit in order to investigate the host contribution to disease. This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/
Type 1 diabetes mellitus (T1DM) is a prototypic endocrine autoimmune disease resulting from an immune-mediated destruction of pancreatic insulin-secreting beta-cells. A comprehensive immune cell phenotype evaluation in T1DM has not been performed thus far at the single. In this cross-sectional analysis, we generated a single-cell transcriptomic dataset of peripheral blood mononuclear cells (PBMCs) from 46 manifest T1DM (Stage 3) cases and 31 matched controls.Our study reveals a surprisingly strong systemic dimension at the level of immune cell network in T1DM, defines disease-relevant molecular subtypes and has the potential to guide non-invasive test development and patient stratification.
