The goal of this international collaborative project is to identify genes responsible for Schizophrenia in the Xhosa population of South Africa. The vast majority of the genetic basis for Schizophrenia has yet to be explained. We hypothesize that genes and pathways important to Schizophrenia will harbor different, severe disease-causing mutations in different affected individuals. Given the genetic diversity of African populations, we expect to find genes for Schizophrenia that have not yet emerged from studies of other populations. This project will also foster the development of gene discovery research for neuropsychiatric disorders in Africa. Our approach will identify genes important for the disorder in populations worldwide. These genes will stimulate future efforts to develop more effective treatment and prevention strategies.
Cohort Description The Genetic Epidemiology of COPD (COPDGene) study is a non-interventional, multicenter, longitudinal, case-control study at 21 US sites of smokers with a ≥10 pack-year history of smoking, with and without COPD, and healthy never smokers. The initial goal was to characterize disease-related phenotypes and explore associations with susceptibility genes. Data Being Submitted Wave 1 questionnaire data includes 397 variables for up to 3683 COPDGene participants in C4R. Wave 2 questionnaire data includes 447 variables for up to 2191 COPDGene participants in C4R. Dried Blood Spot/Serosurvey data includes 7 variables for up to 1692 COPDGene participants in C4R. Derived data includes 43 variables for up to 4082 COPDGene participants in C4R. Phenotype data includes 113 variables for up to 4082 COPDGene participants in C4R.
The diagnosis of the genetic etiology of deafness contributes to the clinical management of patients. We performed the following four genetic tests in three stages for 52 consecutive deafness subjects in one facility. We used the Invade assay and Sanger sequencing for the GJB2 gene or SLC26A4 gene in the first stage test, TaqMan genotyping assay in second stage test, and targeted exon sequencing using the massively parallel DNA sequencing in third stage test. Overall, we identified the genetic cause in 40% (21/52) of patients. The diagnostic rates of the first-, second- and third-stage genetic testing were 17%(9/52), 9%(4/43) and 21% (8/39), respectively. The combination approach using these genetic tests appears to be useful as a diagnostic tool for deafness patients. We recommended that genetic testing for the screening of common mutations in deafness genes using the Invader assay or TaqMan genotyping assay be performed as the initial evaluation. For the remaining undiagnosed cases, targeted exon sequencing using MPS is clinically and economically beneficial. This data set was MPS reads data (fastq) for 39 sensorineural hearing loss patients.
This is an in vitro genome-wide CRISPR/cas9 screen in human glioblastoma stem cells, screening for genes essential for survival of these cells. These cells express cas9 and have been transfected with a guide RNA library causing gene knockouts. We will analyse the sequencing data for depletion of guide RNAs.
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.
14 TNBC tumors with tumor percentage ~90% were selected for in silico spike-in experiment
This is a prospective observational study seeking to identify pathogens in cases of unexplained neurological disease, particularly those in which there is a presumed infectious cause. This next generation analytical approach will hopefully allow for rapid identification of foreign genomic material, and through a sophisticated bioinformatics pipeline developed in the DeRisi lab, these foreign genomic sequences can be aligned to all known sequences in publicly available databases (i.e. GenBank) which may allow for identification of novel pathogens or known pathogens that are not frequently tested for as part of standard diagnostic work-ups.
In this study we will exploit the bacterial clustered regularly interspaced short palindromic repeats (CRISPR) system to perform a genome-wide single-guide RNA (sgRNA) library to screen for genes required for proliferation and survival in human organoids.
We have hypothesized that methylation differences induced by trisomy 21 (T21) contribute to the phenotypic characteristics and heterogeneity in T21. In order to determine the methylation differences in T21 without the interference of the interindividual genomic variation, we have used fetal skin fibroblasts from monozygotic (MZ) twins discordant for T21. We also used skin fibroblasts from MZ twins concordant for T21, normal MZ twins without T21, and unrelated normal and T21 individuals. We applied Reduced Representation Bisulfite Sequencing (RRBS) to generate genome wide nucleotide resolution of DNA methylation based on high throughput sequencing between each pair of samples. RRBS revealed differentially methylated promoter regions (DMRs) in MZ twins discordant for T21 that have also been observed in unrelated normal and T21 individuals. The identified DMRs are enriched for genes involved in embryonic organ morphogenesis. These DMRs are maintained in iPS cells generated from this twin pair and are correlated with the gene expression changes. We have also observed an increase in DNA methylation level in the T21 methylome compared to the normal euploid methylome. This observation is concordant with the up regulation of DNA methyltransferase enzymes (DNMT3B and DNMT3L) and down regulation of DNA demethylation enzymes (TET2 and TET3) in the iPSC of the T21 versus normal twin. Additionally, two sets of T21 MZ twins discordant for heart defect highlighted DMRs in genes that are associated with heart development. In conclusion the study of DNA methylation differences in MZ twins discordant for genomic abnormalities is a promising approach to understand the molecular pathophysiology of aneuploidies.
PALMO (Platform for Analyzing Longitudinal Multi-omics data) is a platform for analyzing longitudinal data from bulk as well as single cell. It allows to identify inter-, intra-donor variations in genes over longitudinal time points. The analysis can be done on bulk expression dataset without known cell type information or single cell with cell type or user defined groups. It allows to infer stable and variable features in a given donor and each cell type or a user defined group. The outlier analysis can be performed to identify technical/biological perturbed samples in a donor or a participant. Further, differential analysis can be performed to decipher time-wise changes in gene expression in a cell type. The data that is available in the dbGaP is the demo longitudinal samples used in the study, which includes hashed raw fastq files for single-cell RNA-sequencing (scRNA-seq) and non-hashed fastq files for single-cell ATAC-sequencing (scATAC) experiment.
