14465 results for "PLOS+ONE+Pennsylvania+German+ACS+language+code+pdc+open+access+study"

in 12.76 milliseconds.

• 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

• Whole_genome_sequence_of__third_generation_family_member__SFHS_

  Previously we performed deep WGS on 6 parents and 13 children from 3 large families from the Scottish Family Health Study to identify de novo mutations. This prelim is cover the additional sequencing of one grandchild from one of these three families. The inclusion of a third generation individual will provide additional experimental validation for the de novo mutations found in the initial trio. As in the previous study, the DNA will be WGS to a depth of approximately 25X to achieve this purpose.

  Study EGAS00001000429

• AmsterdamUMC Data Access Committee for the EPIC-CD study

  The current data access committee reviews and assesses data requests of researchers that seek to gain access to data acquired as part of the EPIC-CD project as performed at the AmsterdamUMC, Amsterdam, Netherlands.

  Dac EGAC50000000097

• Cholesterol and Pharmacogenetics (CAP) Study

  The Cholesterol and Pharmacogenetics Study was a 6-week open label, non-randomized study of 40mg/day simvastatin treatment in 335 black and 609 white (944 total) men and women. Plasma lipids and lipoproteins were measured on two occasions prior to treatment and at 4 and 6 weeks of treatment. The study was designed to test for genetic associations with baseline measurements and changes in response to simvastatin treatment. Whole genome genotyping was performed on 592 white CAP study participants in two stages. In Stage 1, 304 were genotyped for 314,621 SNPs to tag for common genomic variation. In Stage 2, 290 participants were genotyped, including 280 who were genotyped for 620,901 SNPs. Two samples were excluded due to gender discrepancies. More recently, CAP self-reported black participants were genotyped on Illumina Omni2.5Exome chips. PolyA-selected strand-specific RNA-seq libraries were generated in several batches from lymphoblastoid cell lines (LCLs) derived from 268 white and 165 black CAP participants. The LCLs were exposed to sham buffer (control) or 2 uM activated simvastatin for 24 hours, producing a total of 866 100/101 bp paired end RNA-seq libraries sequenced on Illumina HiSeq 2000 machines.

  Study phs000481

• FHS-Net Social Networks

  Note: Data Use Restrictions: The data must only be used for genetic research projects solely in the area of health-related social-network research. This study compiles detailed information on family and social ties linked to participants in the offspring cohort of the Framingham Heart Study. The investigators took computerized information from self-report data used by the FHS for over 30 years to facilitate health exam scheduling. These tracking sheets asked participants to identify people close to them, which were assumed by the investigators to indicate a social tie. Individuals are listed as "egos" (if the ties are from their perspective) and/or "alters" (if they are linked as a friend or family members to one of the other participants). All egos were FHS offspring participants while alters could be FHS participants in any cohort or non-participants. This information was combined with internal FHS pedigree data on family ties to list family member alters (as well as the nature of their relationship). The resultant dataset therefore includes each ego-alter tie, the nature of their relationship and the start and end dates for their ties for each of seven waves for the offspring study. Due to privacy concerns, all exam dates for individuals are listed relative to the initial FHS exam date. The study investigators chose a random, confidential date, to which all initial exam dates are linked (by number of months from random date to initial exam date). With this information, researchers can have access to the temporal relationships among participants&#39; exam dates while remaining unaware of the actual exam dates for individual participants. During each clinic exam cycle, the participants undergo a detailed examination including physical examination, medical history, laboratory testing, and electrocardiogram. Over the years, other tests (that may not be performed at every exam cycle) have included pulmonary function, lifestyle, physical function, cognitive function questionnaires, and various noninvasive cardiovascular tests including echocardiograms. This study involves phenotypic data from these exams including (when available) basic body measurements (height, weight, blood pressure), laboratory values (blood sugar levels, LDL levels), information on smoking and alcohol use, and tests of depression and cognitive functioning. Important links to apply for individual-level data Data Use Certification Requirements (DUC) Instructions to Request Authorized Access Apply here for controlled access to individual level data Participant Protection Policy FAQ In 1948, researchers recruited men and women from the town of Framingham, Massachusetts, beginning the first round of extensive physical examinations and lifestyle interviews that would later be analyzed for common patterns related to CVD development. Initially, the Framingham Heart Study enrolled 5,209 men and women from the Framingham area who were between the ages of 28 and 62 years. Beginning in 1971, the Framingham Heart Study enrolled 5,124 men and women, who were either offspring of the original cohort or spouses of those offspring. In 2002, 4,095 third generation participants (men and women) were enrolled.

  Study phs000153

• Single cell atlas of human glioma

  We profiled 87 primary-recurrentpatient-matched paired GBM specimens with single-nucleus RNA and bulk-DNA sequencing and single-cell open-chromatin and spatial transcriptomics/proteomics assays. We found that recurrent GBMs are characterized by a shift to a mesenchymal phenotype in response to therapy

  Dataset EGAD00001008811

• Psoriasis Patient PBMC scRNA-seq data

  This dataset contains raw and processed data of four scRNA-seq PBMC samples from four Psoriasis patients (Pso3 = male, Pso4 = female, Pso7 = female, Pso8 = male). Raw sample libraries were prepared with 10x 5'-kit v2 multiplexing the individual samples using TrueSeq barcoded antibodies to stain the cells. Resulting sequencing data consists of four FASTQs (2 x antibody multiplex to demultiplex the samples + 2 x transcriptome data containing the typical cell x UMI barcode data for count matrix generation). The raw sequencing data was processed with cellranger 6.0.1 with the GRCh38 3.0.0 reference and cell to sample assignment was subsequently done with couhto 1.1.0 (https://github.com/dmalzl/counhto) employing the same algorithm as cellranger multi (couldn't be used here though as multi does not handle 5'-chemistry data). Processed data contains all main outputs of cellranger count in raw text format or in h5 formats including the used feature reference for (i.e. antibody barcode to sample assignment) as well as the computed cell to sample assignment computed by counhto. For further details including all used code in the analysis of the data please consult https://doi.org/10.5281/zenodo.13846873

  Dataset EGAD50000001102

• The Chromatin Landscape of Pathogenic Transcriptional Cell States in Rheumatoid Arthritis

  In this study, we characterized 24 rheumatoid arthritis (RA) synovial tissue chromatin classes (i.e., cell states defined by chromatin accessibility) across 5 cell types (T, B/plasma, myeloid, stromal, and endothelial). We also investigated the transcription factors that may regulate these chromatin classes, their connections to transcriptional cell states in a proposed superstate model, and their interplay with RA pathology through associations with histological parameters and risk variants.As part of the Accelerating Medicines Partnership (AMP) network, we obtained 18 synovial tissue samples from 14 RA and 4 osteoarthritis (OA) patients for this study. Samples were collected from 7 clinical sites. We performed a 10x single cell ATAC-seq experiment on each sample.We further collected synovial tissue samples from 11 RA patients and 1 OA patient from 2 clinical sites; each sample was used for a 10x single cell multimodal ATAC and Gene Expression experiment.For additional support of the proposed superstate model, we also collected peripheral blood mononuclear cells (PBMCs) from 4 RA patients, sorted for 4 populations (CD4+CD127-CD25hi Tregs, CD4+CD127-CD25int Tregs, CD4+CD25-PD1+CXCR5- TPH, CD4+CD25-PD1+CXCR5+ TFH), tagged each population with a hashing antibody, and pooled populations for one multimodal sequencing run.The FASTQ files are available for controlled access via dbGaP. Additional data can be found on Synapse.The presence of pooled subjects inflates the automatically-generated subject count; the actual consented subject count for this data is 34.

  Study phs003417

• A Pilot Study of Neoadjuvant Nivolumab, Ipilimumab and Intralesional Oncolytic Virotherapy for HER2-Negative Breast Cancer

  This study was a single arm phase 1 trial that assessed the regimen safety and feasibility as well as tumor response in patients with localized HER2-negative breast cancer treated with talimogene laherparepvec (T-VEC) in combination with nivolumab and ipilimumab. The primary objective was to evaluate the safety and adverse event profile of this treatment combination. Six patients were enrolled, four having relapses after prior neoadjuvant chemotherapy, and two who were previously untreated. One patient had a pathological complete response, three patients had pathological partial responses, one showed no significant response, and one had disease progression. Biopsies demonstrated increased immune cell infiltration in samples from patients who responded to therapy. In this study, the checkpoint blockade immunotherapy combined with T-VEC provided responses in patients with advanced or relapsed HER2-negative breast cancer at the expense of long-term toxicities.

  Study phs003316

• DCCT/EDIC Epigenetics (DNA Methylation) Study

  Metabolic memory (persistent benefits of early glycemic control on preventing/delaying diabetic complications development) was observed in the Diabetes Control and Complications Trial (DCCT) and follow-up Epidemiology of Diabetes Interventions and Complications (EDIC) study, dbGaP phs000086.v3.p1, but mechanisms are unclear. We investigated the involvement of epigenetic DNA methylation (DNAme) by examining its associations with preceding glycemic history, and subsequent complications development over 18 years in blood DNAs of 499 randomly-selected DCCT/EDIC participants with type 1 diabetes. We found associations between DNAme near DCCT-closeout and mean-DCCT-HbA1c at 186 CpGs (FDR&lt;15%, including 43 at FDR&lt;5%), many located in complications-related genes. These CpGs are enriched in C/EBP motifs, enhancer/transcription regions in blood cells/progenitors, and open chromatin-states in myeloid cells. Remarkably, several CpGs in combination explain 68-97% of the mean-DCCT-HbA1c risk of complications development during EDIC. DNAme at key CpGs appears to mediate the association between hyperglycemia and complications in metabolic memory, through modifying myeloid cell enhancer activity.

  Study phs002024