GABAergic interneurons are essential for neural circuit function and their loss or dysfunction is implicated in human neuropsychiatric disease. In vitro methods for interneuron generation hold promise for studying human cellular and functional properties and ultimately therapeutic cell replacement. We used a protocol for generating cortical interneurons from hESCs and analyzed the properties and maturation timecourse of cell types using single-cell RNAseq (data available at GEO under: GSE93802 on March 10 2017). Transcriptomic profiles of the hESC-derived interneurons were compared to several different populations of cells from mid-gestation human neocortex that showed differing levels of PAX6 and SOX2 expression. For this study, 104 samples of 100 human neocortical cells each, have been sorted based on SOX2 and PAX6 expression, mRNA recovered from the fixed cells by FRISCR, and transcriptomic profiles generated by SmartSeq2. The RNA-seq data from the 104 100-cell samples is included in this dbGaP study.
High grade serous ovarian cancer (HGSC) is frequently characterized by homologous recombination (HR) DNA repair deficiency, and while most such tumors are sensitive to initial treatment, acquired resistance is common. We undertook a multi-omics approach to interrogating mechanisms of resistance, using multiple autopsy samples collected from 15 women with HR-deficient HGSC.
Charcot Marie Tooth disease (CMT) is an umbrella term that covers any inherited peripheral neuropathy. People with CMT have a problem with the nerves that go to the feet and hands that cause muscle and sensation loss, as well as difficulty with balance. There are at least forty genes that, when mutated, cause CMT. The purpose of this study is to look at the natural history of CMT to see how it changes over time. Particular emphasis will be put on studying people with CMT1B, CMT2A, CMT4A, and CMT4C, though all people with CMT are encouraged to participate. Participants are invited back on a yearly basis to determine how the changes are occurring. Objectives: Determine the natural history and genotype-phenotype correlations of disease-causing mutations in CMT1B, CMT2A, CMT4A and CMT4C as well as other forms of CMT Determine the capability of the newly developed CMTPeds score and the Minimal Dataset to measure impairment and perform longitudinal measurements in patients with multiple forms of CMT over a ten-year window This is a longitudinal study of individuals with CMT. Study participants will be invited to be re-evaluated every year. Evaluations will consist of neurological histories and examinations, selected nerve conduction studies (NCS) as well as completion of assorted clinical outcome measures including the CMTNS, Minimal Dataset, and Peds CMT Scale. Selected CMT patients and controls will also receive glabrous skin biopsies.
The INGenious trial planed to enroll a total of 6,000 patients, with 2,000 patients assigned to a pharmacogenetic testing arm and 4,000 to a control arm who will be followed, but not tested. It is randomized between an intervention arm and one that receives no intervention in order that the genotyped group can be compared with one in which undisturbed, routine clinical care is carried out in patients taking the same drugs. Both arms will be followed for a year after being prescribed a targeted medication. Patients randomized into the intervention arm that are prescribed one or more of the 27 targeted index medication will receive pharmacogenomic testing using a custom micro-array measuring 43 Single nucleotide polymorphisms in 14 genes. The study is being conducted by the Indiana University School of Medicine and the Indiana University Institute of Personalized Medicine in collaboration with the Eskenazi and Indiana University Health Systems and will evaluate the economic and clinical outcomes associated with embedding a pharmacogenomics program in a system that serves as the primary health care safety-net in Indianapolis, Indiana. By successfully implementing a pharmacogenomics program and integrating it with the Electronic Health Record and Clinical Decision Support system, physicians will be able to optimize patient care by delivering tailored therapeutic decisions based on the patient's individual genetics.
Comprehensive transcriptional characterization of bone marrow stromal cells by RNA sequencing was performed to determine the molecular properties/signatures of endothelium during niche formation.Here, we identify a rare subset of cells in the human fetal BM that co-express endothelial and stromal markers, including low-affinity nerve growth factor receptor (LNGFR/CD271). They display transcriptional reprogramming consistent with endothelial-to-mesenchymal transition (EndoMT), reflected in their potential to generate stromal cells with in vivo BM niche forming capacity.
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.
Ependymomas are common childhood brain tumours that occur throughout the nervous system, but are most common in the paediatric hindbrain. Current standard therapy comprises surgery and radiation, but not cytotoxic chemotherapy as it does not further increase survival. Whole-genome and whole-exome sequencing of 47 hindbrain ependymomas reveals an extremely low mutation rate, and zero significant recurrent somatic single nucleotide variants. Although devoid of recurrent single nucleotide variants and focal copy number aberrations, poor-prognosis hindbrain ependymomas exhibit a CpG island methylator phenotype. Transcriptional silencing driven by CpG methylation converges exclusively on targets of the Polycomb repressive complex 2 which represses expression of differentiation genes through trimethylation of H3K27. CpG island methylator phenotype-positive hindbrain ependymomas are responsive to clinical drugs that target either DNA or H3K27 methylation both in vitro and in vivo. We conclude that epigenetic modifiers are the first rational therapeutic candidates for this deadly malignancy, which is epigenetically deregulated but genetically bland.
Salivary gland cancer (SGC) is a rare cancer for which systemic treatment options are limited. Therefore, it is important to characterize its genetic landscape in search for actionable aberrations. This research aimed to identify these actionable aberrations by NGS-based analysis of DNA (single and multiple nucleotide variants, copy number variants, microsatellite instability and tumor mutational burden) in a large cohort of SGC patients. DNA was extracted from archival tissue of 119 patients with various SGC subtypes and sequenced using a targeted NGS panel encompassing 523 cancer related genes (TruSight Oncology 500, TSO500). The 119 patients included 46 AdCC patients, 43 SDC patients, 15 MEC patients, 9 AciCC patients and 6 patients with other subtypes (1 secretory carcinoma, 1 polymorphic adenocarcinoma (PAC), 1 adenocarcinoma NOS, 1 myoepithelial carcinoma, 1 epithelial/myoepithelial carcinoma and 1 mixed PAC/myoepithelial carcinoma). Median exon coverage ranged from 80-904 (median 308) unique reads and the median percentage of exon coverage with at least 100 unique reads was median 96.6% in these 119 samples.
Primary T cell immunodeficiency disorders are genetically heterogenous. Mutations in genes required for specific stages of T cell development within the thymus can lead to reduced numbers of circulating T cells. On the hand, T cells may not egress from the thymus normally leading to profound T cell lymphopenia. As a result, patients with these disorders succumb to a range of severe opportunisitic infections unless allogeneic transplantation is performed. We wish to whole exome sequence a Caucasian family in which the index case shows features of impaired T cell egress from the thymus. Importantly, known genes implicated in T cell immunodeficiency including CORO1A have been seqeuenced and found to normal in this individual.
Sebaceous tumours are a rare cutaneous cancer with potential for aggressive behaviour. However, limited information is available on these cancers with few published cases. Here we wish to exome sequence these cancers to define the first genomic landscape for this malignancy. We will extract RNA from formalin-fixed, paraffin-embedded (FFPE) cores. Cores may be obtained from lesional and non-lesional tissues of primaries as well as matching metastases. The extracted RNA will be used for RNA sequencing.
