15427 results for "Buy fc 26 coins Buyfc26coins.com is EA Sports official for FC 26 coins All coins were delivered very promptly..EDvG"

in 18.53 milliseconds.

• Jackson Heart Study (JHS) Cohort

  The Jackson Heart Study (JHS) is a large, community-based, observational study whose participants were recruited from urban and rural areas of the three counties (Hinds, Madison and Rankin) that make up the Jackson, MS metropolitan statistical area (MSA). Participants were enrolled from each of 4 recruitment pools: (1) random, 17%, (2) volunteer, 30%, (3) currently enrolled in the Atherosclerosis Risk in Communities (ARIC) Study, 31%, and (4) secondary family members, 22%. The final cohort of 5,306 participants included 6.59% of all African American Jackson MSA residents, aged 35-84, during the baseline exam (N-76,426, US Census 2000). Among these, approximately 3,600 gave consent that allows genetic research and deposition of data into dbGaP. Major components of three clinic examinations (see study history) include medical history, physical examination, blood/urine analytes, and interview questions on areas such as physical activity, stress, coping and spirituality, racism and discrimination, socioeconomic position, and access to health care. Extensive clinical phenotyping includes anthropometrics, electrocardiography, carotid ultrasound, ankle-brachial blood pressure index, echocardiography, CT chest and abdomen for coronary and aortic calcification, liver fat, and subcutaneous and visceral fat measurements, and cardiac MRI. At 12-month intervals after the baseline clinic visit (Exam 1), participants have been contacted by telephone to update information, confirm vital statistics, document interim medical events, hospitalizations and functional status, and obtain additional sociocultural information. Questions about medical events, symptoms of cardiovascular disease and functional status are repeated annually. Ongoing cohort surveillance includes abstraction of medical records and death certificates for relevant International Classification of Diseases (ICD) codes and adjudication of nonfatal events and deaths. CMS data are currently being incorporated into the dataset. Note: Regarding date variables warehoused in the Jackson Heart Study (JHS) Cohort on dbGaP, the coordinating center has developed an algorithm that will systematically review and de-identify any of the (nearly 100) date-related variable types stored in the data package. To simultaneously minimize (i) de-identifiability of the data and (ii) impact on analyses utilizing sensitive data elements, a participant-level random number was generated to avoid the necessity of sharing any potentially sensitive data. The coordinating center maintains an archived linkage of these data in their raw form and regularly reviews ad hoc requests to utilize the raw data on a project-by-project basis. The JHS Cohort is utilized in the following dbGaP substudies. To view genotypes, other molecular data, and derived variables collected in these substudies, please click on the following substudies below or in the "Substudies" section of this top-level study page phs000286 JHS Cohort. phs000402 ESP Heart GO JHS phs000498 JHS Allelic Spectrum Seq phs000499 JHS CARephs001069 MI Gen JHS phs001098 T2D GENES Exome Seq phs001356 Exome Chip phs002256 Cardiometabolic Renal Proteomics phs002369 Metabolomics Insulin Resistance

  Study phs000286

• Genome-Wide Analysis for Addiction Susceptibility Genes

  Genome wide analysis for addiction susceptibility genes is an affected sibling pair linkage study using subjects who were patients in methadone replacement treatment programs (MMTP). Such patients are highly addicted to opioids and usually to other addicting substances as well. For entry into the programs, patients had to be at least 18 years of age and had to satisfy DSM-IV criteria for opioid dependence. Despite their common substance use disorder diagnosis, patients enrolled in MMTPs generally have a heterogeneous mix of co-morbid psychiatric disorders including anti-social personality disorder, major depression and anxiety disorders, and often satisfy DSM-IV criteria of substance use disorders other than opioid dependence. Genetic analysis was carried out using genotyping data obtained from a 10K SNP array, and non-parametric linkage was assessed using MERLIN. This resulted in the identification of a linkage peak on 14q that overlapped the NRXN3 gene (neurexin 3), which was previously identified as a potential candidate gene for addiction, and subsequently identified as a target gene in other addiction studies and autism. In version 2 of this study, a text file containing 7704 SNPs with large allele frequency discrepancy as compared to 1000 Genomes is included. Users have the option to exlude these 7704 SNPs.

  Study phs001266

• Diverse_outcomes_of_controlled_human_malaria_infection_originate_from_host_intrinsic_immune_variation_and_not_var_gene_switching

  Falciparum malaria is clinically heterogeneous and the relative contribution of parasite and host factors in shaping disease severity remains unclear. We set out to explore the interaction between host inflammation and parasite variant surface antigen (VSA) expression, asking whether this relationship underpins the variation observed in controlled human malaria infection. We uncovered marked heterogeneity in the response of naive hosts to blood challenge with some volunteers maintaining a state of immune quiescence, others triggering interferon-stimulated inflammation and a small group showing transcriptional evidence of myeloid cell suppression. Significantly, only inflammatory volunteers experienced hallmark symptoms of clinical malaria. When we then tracked temporal changes in parasite VSA expression to ask whether variants associated with severe disease preferentially expand in naive hosts (as predicted by current theory) we found that var gene profiles were essentially unchanged after 10-days of blood-stage infection. These data therefore show that the diverse clinical outcomes of CHMI largely originate from host-intrinsic variation and there is no evidence for switching or selection of var genes in naïve hosts. 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/

  Study EGAS00001003766

• Defining T cell States Associated with Response to Checkpoint Immunotherapy in Melanoma

  Checkpoint blockade therapy using antibodies targeting CTLA4, PD1 or PDL1 have changed the way cancer patients with advanced disease are being treated, as evident by their FDA approval in a wide variety of malignancies, and their ability to induce high response rates when compared to conventional therapies (e.g. chemotherapy). However, even in melanoma, despite the high response rate, most patients are refractory to therapy or acquire resistance in 10-12 months. To identify key immunological elements coupled with response or resistance to checkpoint immunotherapy, we performed an unbiased analysis on 16,291 CD45+ immune cells from 32 patients (48 samples) treated with checkpoint therapy (anti-PD1=37; anti-PD1/CTLA4=11), using single cell transcriptomics. Initial unsupervised clustering of all CD45+ cells identified 11 clusters. When examining the association of these clusters with clinical outcome, we found that two clusters (B-cells, p=0.005; memory T-cells, p=0.03) were significantly enriched in responder lesions while 4 clusters (monocytes/macrophages, p=0.003; dendritic cells, p=0.015; exhausted CD8+ T-cells, p=0.005; and exhausted/cell-cycle lymphocytes, 1.3x10-5) are enriched in non-responder lesions. Next, by leveraging our unbiased single cell approach, we identified not only clusters but also specific markers associated with either responder lesions (PLAC8, LTB, LY9, SELL, TCF7, IGKC and CCR7) or non-responder ones (CCL3, CD38, HAVCR2, ENTPD1 and WARS), many of which were not previously reported to be associated with clinical outcome to checkpoint therapy. Due to the importance of CD8+ T-cells in controlling tumors, the significant association of T-cell states with clinical outcome, and their high abundance in melanoma tumors, we next focused our analysis on CD8+ T-cells and identified 2 main clusters CD8_G (with increased expression of genes linked to memory) and CD8_B (enriched for genes linked to cell dysfunction), that were significantly enriched in responder (CD8_G, p=1.4x10-6) and non-responder (CD8_B, p=0.005) lesions, respectively. Since cells with both states coexist in each of the responder and non-responder lesions, we decided to calculate the ratio between the number of cells in these 2 clusters and observed a significant separation between responders (CD8_G/CD8_B>1) and non-responders (CD8_G/CD8_B<1) when looking at all samples, baseline or post samples separately. Similar results were detected when looking at the expression of a single transcription factor, TCF7, in CD8 T-cells in an independent cohort (n=43) using a simple immunofluorescence assay. Additionally, we validated the identity and function of some of the newly identified cell states as well as their epigenetic landscape, and found that cells expressing the inhibitory molecules CD39 and TIM3, on top of being enriched in non-responder lesions, are likely to play a crucial role in T-cell exhaustion in melanoma. Collectively, our study provides extensive unbiased data in human tumors for discovery of predictors and therapeutic targets to checkpoint immunotherapy.

  Study phs001680

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! The EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• African American Multiple Myeloma GWAS

  The case set is from a case-control study designed to identify common genetic risk factors for multiple myeloma in African Americans, the population with the highest risk for this cancer. We conducted two GWAS and combined each of these with convenience controls consisting of unaffected African American participants in cohorts with existing GWAS data. We then conducted a meta-analysis of the two sets. Cases were persons of African ancestry with smoldering or active multiple myeloma identified at participating oncology clinics or through SEER registries, as part of the African American Multiple Myeloma Study (AAMMS) diagnosed from Jan 1, 1988 through July 31, 2016. The majority of the samples were collected from incident and prevalent cases diagnosed since Jan 1, 2008 (80.9%), with a minority obtained from biobanks from cases diagnosed prior to 2008 (19.1%). Additional samples were obtained from the Multiethnic Cohort (USC and University of Hawaii) (n=40), the University of California at San Francisco Multiple Myeloma Study (n=27), and from the Multiple Myeloma Research Consortium for secondary analysis (samples originally provided to MMRC by 8 additional sites (n=84)). We have identified the phenotype (smoldering myeloma, plasma cell multiple myeloma, or myeloma not otherwise specified (myeloma NOS) when myeloma phenotype was not known), sex and age at diagnosis in this data set. The initial GWAS set consisted of 1308 (1,305 passed QC) cases with DNA samples, with a GWAS performed on the Illumina Human Core. Controls consisted of 7,078 unaffected African American subjects who were participants in the African American Prostate and Breast Consortium, with existing GWAS data from the Illumina1M Duo BeadChip. The second GWAS set consisted of 529 African American multiple myeloma patients with samples (406 from University of Arkansas, results not contained in this dataset because NCI funds were not used for the collection and genotyping) with GWAS data resulting from the Illumina Mega-BeadChip v1.1. Controls were 2,390 unaffected African American participants in the Multiethnic Cohort with existing GWAS data from the same array. After QC and removal of duplicates within sets, sex mismatches, and removal of plasmacytoma cases (ICD-0 code 9731), this deposited data set contains the typed GWAS data for the Illumina Human Core (set 1) (n=1298), and for the MegaBead Chip v1.1 (set 2) (n=123), with the University of Arkansas samples removed, for a total of 1,421 case genotypes. Note that 13 samples that overlap set 1 and set 2 were included.

  Study phs001632

• Single-cell multi-omics and mtDNA genotyping of human peripheral blood cells

  This dataset comprises two mtscATAC-seq libraries (customized 10X ATAC-seq) generated from donor M80 and donor H05, and one DOGMA-seq library (customized 10X multiome) generated from donor H05, all derived from primary human peripheral blood mononuclear cells. Patient M80 is an 80-year-old male with mitochondrial encephalomyopathy, lactic acidosis, and stroke-like episodes (MELAS), while donor H05 is a healthy 5-year-old pediatric donor. The raw FASTQ files have been provided.

  Dataset EGAD50000001489

• Radiation-induced gliomas represent H3-/IDH-wild type pediatric gliomas with recurrent PDGFRA amplification and loss of CDKN2A/B

  Long-term complications such as radiation-induced second malignancies occur in a subset of patients following radiation-therapy, particularly relevant in pediatric patients due to the long follow-up period in case of survival. Radiation-induced gliomas (RIGs) have been reported in patients after treatment with cranial irradiation for various primary malignancies such as acute lymphoblastic leukemia (ALL) and medulloblastoma (MB). We perform comprehensive (epi-) genetic and expression profiling of RIGs arising after cranial irradiation for MB (n=23) and ALL (n=9). Our study reveals a unifying molecular signature for the majority of RIGs, with recurrent PDGFRA amplification and loss of CDKN2A/B and an absence of somatic hotspot mutations in genes encoding histone 3 variants or IDH1/2, uncovering diagnostic markers and potentially actionable targets.

  Study EGAS00001005243

• Whole exome sequencing data from non-small-cell lung cancer patients receiving immunotherapy prognosis

  The plasma samples and white blood cell samples were collected from 30 non-small-cell lung cancer patients and 3 healthy individuals. The solid tumor biopsy samples from 14 patients (a subset of the 30 patients) were collected. The cfDNA was extracted from their plasma samples using the QIAamp circulating nucleic acid kit from QIAGEN (Germantown, MD). The cfDNA WES library was constructed with the SureSelect XT HS kit from Agilent Technologies (Santa Clara, CA) according to the manufacturer’s protocol. In brief, 10ng of cfDNA was used as input material. After end repair/dA-tailing of cfDNA, the adaptor was ligated. The ligation product was purified with Ampure XP beads (Beckman-Coulter, Atlanta, GA) and the adaptor-ligated library was amplified with index primer in 10-cycle PCR. The amplified library was purified again with Ampure XP beads, and the amount of amplified DNA was measured using the Qubit 1xdsDNA HS assay kit (ThermoFisher, Waltham, MA). 700-1000 ng of DNA sample was hybridized to the Agilent SureSelect Human All Exon V6 (Agilent) capture library and pulled down by streptavidin-coated beads. After washing the beads, the DNA library captured on the beads was re-amplified with 10-cycle PCR. The final libraries were purified by Ampure XP beads. The library concentration was measured by Qubit, and the quality was further examined with Agilent Bioanalyzer before the final step of 2x150bp paired-end sequencing on the Illumina HiSeq X10 platform (Illumina) at an average coverage of 200. Whole-exome capture libraries of genomic DNA of the 30 non-small cell lung cancer patients were constructed via Roche SeqCap EZ Exome V3 (Roche); whole-exome capture libraries of genomic DNA of the 3 healthy individuals were constructed via Agilent SureSelect Human All Exon V6 (Agilent). Enriched exome libraries were sequenced on the Illumina HiSeq 3000 platform (Illumina) to generate 2x100bp paired-end reads at an average coverage of 200.

  Dataset EGAD00001006096

• Evolution and clinical impact of genetic epistasis within EGFR-mutant lung cancers: multi-timepoint exome sequencing of a single patient's disease

  This dataset is a time-series of EGFR-mutant NSCLC clinical specimens from an individual patient profiled using tumor-based whole exome sequencing and the data is in BAM format. DNA was extracted from FFPE for primary tumor and frozen tumor tissue samples and matched non-tumor tissue using the Qiagen Allprep DNA/RNA Mini Kit.  The library preparation protocol was based on the Agilent SureSelect Library Prep and Capture System. DNA was resuspended in a low TE buffer and sheared (Duty Cycle 5%; Intensity 175; Cycles/Burst: 200; Time: 300s, Corvaris S2 Utrasonicator).  Bar-coded exome libraries were prepared using the Agilent Sure Select V5 library kit per manfucaturer’s specifications. The libraries were run on the HiSeq2500. Raw paired end reads (100bp) in FastQ format generated by the Illumina pipeline were aligned to the full hg19 genomic assembly obtained from USCS, gencode 14, using bwa version 0.7.12. Picard tools version 1.117 was used to sort, remove duplicate reads and generate QC statistics. Tumor DNA was sequenced to median depth of 303X (range 114.39-383.41) and the matched germline DNA to average depth of 231.65.

  Dataset EGAD00001003769