The aim of this project is to differentiate human embryonic stem cells to an extra-embryonic fate, specifically the hypoblast. This is of uttermost importance given the current lack of human hypoblast stem cells. We hypothesized that the pluripotent characteristics of the starting human embryonic stem cell population may dictate the competency for extra-embryonic cell fate specification. Based on this hypothesis and using human embryonic stem cells maintained in different naïve-like culture regimes, we have now developed conditions that allow the differentiation of human embryonic stem cells to a stable GATA6+ SOX2- population. This suggests that these cells may be putative human hypoblast stem cells. To validate this finding here we propose to perform RNA sequencing experiments of the differentiated human embryonic stem cells. By comparing their RNA expression profile to the single cell sequencing data of the human embryo that we are currently generating, we will be able to determine the identity of our GATA6+ SOX2- cells, and establish whether they represent the in vivo human hypoblast. This dataset contains all the data available for this study on 2020-04-20.
T cells develop from circulating precursor cells, which enter the thymus and migrate through specialised sub-compartments that support their maturation and selection. In humans, this process starts in early fetal development and is highly active until thymic involution in adolescence. To map the micro-anatomical underpinnings of this process in pre- and early postnatal stages, we established a novel quantitative morphological framework for the thymus, the Cortico-Medullary Axis, and used it to perform a spatially resolved analysis. By applying this framework to a curated multimodal single-cell atlas, spatial transcriptomics, and high-resolution multiplex imaging data, we demonstrate establishment of the lobular cytokine network, canonical thymocyte trajectories and thymic epithelial cell distributions within the first trimester of fetal development. We pinpoint tissue niches of thymic epithelial cell progenitors and distinct subtypes associated with Hassall’s corpuscles and uncover divergence in the timing of medullary entry between CD4 vs. CD8 T cell lineages. These findings provide a basis for a detailed understanding of T lymphocyte development and are complemented with a holistic toolkit for cross-platform imaging data analysis, annotation, and Organ Axis construction (TissueTag), which can be applied to any tissue.
Rituximab, a CD20+ B cell depletion therapy, is frequently used in the treatment of systemic lupus erythematosus (SLE). However, variability in patient response highlights the need for a deeper understanding of the underlying immune cell dynamics of B cell depletion and repopulation. In this study, we conducted longitudinal single-cell profiling of nine SLE patients treated with rituximab from pretreatment to up to 15 months post-treatment. These were compared to eight healthy controls. We profiled PBMCs via 10X Genomics single-cell RNA, surface protein (CITE-seq), B cell receptor (BCR), and T cell receptor (TCR) sequencing and sequenced bulk BCR repertoires in parallel. For single cell sequencing, 10 pools were created with an equal number of cells from 4 samples each. Samples collected at different timepoints from the same patient were distributed across different pools to allow demultiplexing of individuals using genotypes captured from the scRNA-seq data. Libraries were pooled using a ratio of GEX:CITE:TCR:BCR=9:2:1:1 and were sequenced across two lanes of the NovaSeq 6000. For bulk BCR sequencing, individual samples were demultiplexed using primer barcodes and paired-end BCR amplicon reads were merged prior to submission; data are provided as unmapped single-end reads.
The BLUEPRINT project is a large-scale project investigating epigenetic mechanisms involved in blood formation, in health and disease. The human variation workpackage (WP10) of the project seeks to characterize the effect of common sequence variation on the epigenome status of a cell. To do this, the project will use highly purified blood cells to minimise "experimental noise" and therefore enhance the power to discover modest effects. Two peripheral blood cell types, the CD14+CD16- monocyte (an important central orchestrator of adaptive immunity and a bridge between innate and adaptive immunity) and the CD65+CD9- neutrophilic granulocyte (the frontline cell for innate immunity) have been selected for this purpose. The two types of cells will be obtained at high purity from adult blood (AB) of 200 healthy males and females, respectively. Cells will be purified by using already validated and fully operational protocols that are based on density gradient centrifugation of the buffy coat obtained from whole blood, followed by magnetic bead-based purification using monoclonal antibodies against Cluster of Differentiation (CD) lineage-specific cell surface markers. This data set contains functional genomics data for gene expression and chromatin state.
Recent work in the Campbell group has revealed somatic mutations present in normal, non-cancerous human skin. A subset of the mutations conferred selective advantages to the host cells, leading to clonal expansions and raising the risk for future cancer development. Capturing such somatic mutations in normal tissue is important to advance our understanding about carcinogenesis and could provide prospective medical insights. In this project, our goal is to detect somatic mutations in normal (pre-cancerous) liver tissue. Using Laser Microdissection technology, we will dissect individual liver lobules from patient samples and submit these to sequencing. For each patient sample, we aim to sequence multiple lobules to characterise the mutagenic burden. Samples will be taken from patients with different liver disease aetiologies, including alcoholism and obesity, with a view on distinguishing the prevalent mutation types occurring in each disease context. We will perform targeted sequencing, initially using the WTSI cancer panel. Later we aim to use a novel bait set that captures both cancer genes as well as genes relevant to the non-cancerous samples (ie. genes implicated in hereditary disorders, immune sequences). . This dataset contains all the data available for this study on 2019-04-08.
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.
This dataset includes raw data (.idat) for the Illumina Human450k beadchip and methylation levels (.txt files). Methylation level were treated for normalization and background substraction. We removed probes with at least one of the following characteristics: (1) weak signal (p > 0.01) (2128 CpG sites), (2) SNP-enriched sites (4100 sites), (3) out of a CpG context (not on a CG) (3149 sites), or (4) located on sex chromosomes (11,129 sites). A total of 465,071 CpG sites were analyzed initially. Signal was then normalized, first by scaling to the internal controls using the methylumi R package, then by applying the method of subset-quantile within array normalization (SWAN) implemented in the minfi R package.
The 100 European-descent (EUB) and 100 African-descent (AFB) Belgians studied were genotyped for a total of 4,301,332 SNPs on the Illumina HumanOmni5-Quad BeadChips. Whole-exome sequencing was carried out for the same 200 individuals with the Nextera Rapid Capture Expanded Exome kit, on the Illumina HiSeq 2000 platform, with 100-bp paired-end reads. This kit delivers 62 Mb of genomic content per individual, including exons, untranslated regions (UTR), and microRNAs. Omni5 and exome datasets were merged, yielding a concordance rate between platforms of 99.93%.
nasopharyngeal carcinoma genome-wide human SNP array data for 423 NPC cases and 573 controls
Column 1 rsid: SNP identifier;Column 2 chromosome: name of chromosome on which the SNP is located;Column 3: position: base pair position on the chromosome;Column 4 minor_test_allele: the base that constitutes the minor allele;Column 5 major_allele: the base that constitutes the major allele;Column 6 maf: the frequency of the minor allele, indicated as a fraction of 1;Column 7 allele_freq_cases: the minor allele frequency in cases;Column 8 allele_freq_controls: the minor allele frequency in controls;Column 9 regression_pvalue: the p-value for the difference in allele frequency between cases and controls;Column 10 odds_ratio: the odds ratio, as calculated using logistic regression under an additive model with adjustment for the first ten principal components of ancestry
