12011 results for "coin buying fc 26 Visit Buyfc26coins.com for latest FC 26 coins news..2Dtf"

in 185.20 milliseconds.

• BLUEPRINT release August 2015, ChIP-Seq for segmented neutrophil of bone marrow, on genome GRCh38

  ChIP-Seq data for 4 segmented neutrophil of bone marrow sample(s). 20 run(s), 19 experiment(s), 19 alignment(s) on human genome GRCh38. Part of BLUEPRINT release August 2015. Analysis documentation available at http://ftp.ebi.ac.uk/pub/databases/blueprint/releases/20150820/homo_sapiens/README_chipseq_analysis_ebi_20150820

  Dataset EGAD00001001588

• Raw FASTQ files from TSO500 hybrid capture sequencing of prostate cancer tissue and plasma.

  This dataset contains raw genomic sequencing data in FASTQ format for a total of 49 libraries. It includes 22 samples derived from formalin-fixed paraffin-embedded (FFPE) tissue and 27 samples from plasma cell-free DNA (cfDNA). All samples were processed using the Illumina TruSight Oncology 500 (TSO500) hybrid capture panel to identify relevant genomic alterations. These files represent the primary, non-aligned data used for the comparative performance analysis described in the associated study.

  Dataset EGAD50000002463

• 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

• Genome-Wide Association Study of Breast Cancer in the African Diaspora - the ROOT study

  The paucity of data on the genetic epidemiology of breast cancer for racial/ethnic groups other than those of European ancestry hinders the development of innovative interventions to reduce health disparities. Women in the African Diaspora experience a disproportionate burden of pre-menopausal breast cancer in comparison to all other races for reasons that remain unknown and understudied. This higher proportion of early-onset breast cancer might suggest a stronger genetic component in these populations. Genome-wide association studies (GWAS) have revealed several genetic loci that confer risk of breast cancer. Because all GWAS started the discovery stage in women of European ancestry and replicated mainly in women of European ancestry, we propose a novel approach for a GWAS in indigenous African women to identify alleles associated with breast cancer risk which will then be replicated in other populations. This innovative design builds on our current understanding of the etiologic heterogeneity in breast cancer and the distribution of breast cancer molecular subtypes which differ between women of African ancestry and women of European ancestry. The major objective of the proposed studies is to get to the "root" causes of breast cancer by identifying breast cancer risk alleles in a pooled sample of women of African ancestry and to replicate our findings in other populations. To achieve this objective, we conducted a case control study of breast cancer in women of African ancestry, including Africans living in Nigeria, African Americans and African Barbadians. We will genotype ~3800 individuals using the Illumina HumanOmni2.5-Quad platform. We will conduct both standard and novel genetic analyses of the data to map genes associated with breast cancer susceptibility, verify genotyping and carry out fine-mapping studies in genes or regions showing association with breast cancer risk, and replicate in other African American and non-African American populations. By pooling unique resources from studies throughout the African Diaspora, this study has the potential to identify risk alleles in several genes that contribute to increased breast cancer risk and may have implications for early detection, prognosis and treatment of breast cancer in ALL women. This should ultimately lead to improved outcomes for those who suffer a disproportionate burden of early-onset breast cancer.

  Study phs000383

• Cooperative Study of Sickle Cell Disease (CSSCD)

  The Cooperative Study of Sickle Cell Disease was initiated in 1977 to determine the natural history of sickle cell disease (SCD) from birth to death in order to identify those factors contributing to the morbidity and mortality of the disease. Specific objectives included: 1) to study the effect of sickle cell disease on growth and development from birth through adolescence 2) to study the conditions or events that may be related to the onset of painful crises 3) to obtain data on the nature, duration, and outcome of major complications of SCD 4) determine the nature, prevalence, and age- related incidence of organ damage due to SCD, and 5) study the role of SCD and its interaction with selected health events.Phases 2 and 3 of the study involved followup of the infant cohort. A total of 709 infants (age less than 6 months) were enrolled during Phase 1 of the Cooperative Study of Sickle Cell Disease (CSSCD), and Phases 2 and 3 of the CSSCD was designed to follow these children for an additional 10 years. The study objectives included: 1) define prospectively the natural history of sickle cell disease; 2) determine the relationships between cognitive and academic functioning and brain status as determined by MRI; 3) determine the cognitive or behavioral markers of silent infarct; 4) determine the relationship of family functioning on the Family Environment Scale (FES) to brain status, cognitive functioning, and social and demographic factors; 5) continue studies that will enhance the state of knowledge on the influence of sickle cell disease on the psychosocial adjustment of children and adolescents. Phase 2A of the study sought to examine the progression of organ damage in the heart, lung, kidney, and liver in adult cohort patients (born before 1/1/56) enrolled in phase 1 of the study between 3/79 and 5/81. A total of 620 patients from 11 centers were eligible for phase 2A.Instructions for requesting individual-level data are available on BioData Catalyst at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BioData Catalyst. For questions about availability, you may contact the BioData Catalyst team at https://biodatacatalyst.nhlbi.nih.gov/contact.

  Study phs002362

• Mayo-Perlegen LEAPS (Linked Efforts to Accelerate Parkinson's Solutions) Collaboration

  We performed a two-tiered, whole-genome association study of Parkinson disease (PD). For tier 1, we individually genotyped 198,345 uniformly spaced and informative single-nucleotide polymorphisms (SNPs) in 443 sibling pairs discordant for PD. For tier 2a, we individually genotyped 1,793 PD-associated SNPs (P<.01 in tier 1) and 300 genomic control SNPs in 332 matched case-unrelated control pairs. We identified 11 SNPs that were associated with PD (P<.01) in both tier 1 and tier 2 samples and had the same direction of effect. For these SNPs, we combined data from the case-unaffected sibling pair (tier 1) and case-unrelated control pair (tier 2) samples and employed a liberalization of the sibling transmission/disequilibrium test to calculate odds ratios, 95% confidence intervals, and P values. A SNP within the semaphorin 5A gene (SEMA5A) had the lowest combined P value (P=7.62E-6). The protein encoded by this gene plays an important role in neurogenesis and in neuronal apoptosis, which is consistent with existing hypotheses regarding PD pathogenesis. A second SNP tagged the PARK11 late-onset PD susceptibility locus (P=1.70E-5). In tier 2b, we also selected for genotyping additional SNPs that were borderline significant (P<.05) in tier 1 but that tested a priori biological and genetic hypotheses regarding susceptibility to PD (n=941 SNPs). In analysis of the combined tier 1 and tier 2b data, the two SNPs with the lowest P values (P=9.07E-6; P=2.96E-5) tagged the PARK10 late-onset PD susceptibility locus. Independent replication across populations will clarify the role of the genomic loci tagged by these SNPs in conferring PD susceptibility. Note: The following instruments were used: 1)clinical assessments form and manual; 2) sibling screening form and manual; 3) unrelated control screening and manual; and 4) risk factors questionnaire and manual. All cases underwent #1, as did sibling controls screening positive (see below). Unrelated controls were not examined. All siblings underwent #2. All unrelated controls underwent #3. All subjects (cases, sibling controls, and unrelated controls) underwent #4. Any publications using the data are to cite the original American Journal of Human Genetics article (Maraganore et al., 2005). Investigators using the data collection instruments are to acknowledge Drs. Maraganore and Rocca, and cite grants ES-10751 and NS-33978.

  Study phs000048

• Effect of Crohn's Disease Risk Alleles on Enteric Microbiota

  This UH2/UH3 demonstration project entitled "Effects of Crohn's disease risk alleles on enteric microbiota" is focused on characterizing intestinal associated microbiota in patients with ileal Crohn's disease (ileal CD), ulcerative colitis (UC) and control patients without inflammatory bowel diseases (non-IBD). We hypothesize that genetic factors that affect Paneth cell function, contribute to compositional changes in intestinal microbiota. These changes in microbiota may lead to reduction of protective commensal organisms and increased numbers of aggressive organisms that incite intestinal inflammation. This hypothesis is being tested by high throughput 16S rRNA sequence analysis of de-identified ileal and colonic tissues that have been archived at Washington University St. Louis, University of North Carolina, Mount Sinai Hospital and the Cleveland Clinic. Multivariate analysis of the metagenomic data will be conducted with genotyping metadata (highly reproducible CD risk alleles, including NOD2 and ATG16L1) and phenotyping metadata (e.g. age, gender, race, body mass index, medications and smoking.) Shotgun sequencing will be performed on selected fecal specimens linked to ileal tissues to identify additional, or auxiliary, or synergistic pathogenic factors or other functional changes in the microbiome. Because members of this research team have observed that a chronic viral infection is required for the Paneth cell defect in Atg16l1 hypomorphic mice, a major focus of these studies will be towards identifying potential viral triggers for the defective Paneth cell phenotype in individuals harboring the ATG16L1 risk allele. Novel genetic probes for protective and aggressive organisms will be developed by mining bacterial genome and shotgun sequencing data. Genomic sequences will be produced for candidate protective and aggressive strains (e.g. adherent-invasive strains of E. coli) isolated from human intestinal tissues where there is limited existing genome information. Quantitative qPCR assays using the novel as well as established genetic probes will be conducted to test the hypothesis that an imbalance between protective and aggressive organisms is associated with genetic factors that affect Paneth cell function. Our combined expertise in multiple disciplines across multiple institutions, our demonstrated ability to collect a large number of well-phenotyped samples with longitudinal clinical information that will be linked to host response and morphologic studies, and our consortium's capacity for high-throughput sequencing will be used to investigate how alterations in human microbiome relate to CD risk alleles and CD pathogenesis.

  Study phs000255

• Nicotine Addiction Genetics and Correlates

  Ascertainment: Families were ascertained through panels of adult Australian twins, and a sample of spouses of Australian twins. Families with at least one offspring who was identified as a current or former smoker in an earlier survey. Screening telephone interviews were conducted with index cases to provide confirmation of a history of heavy cigarette smoking, to obtain confirmation of a history of heavy cigarette smoking, and to obtain additional information on the history of cigarette use and the survival status of other family members, and their full siblings and parents. Index cases were the affected spouse of a twin, or the affected twin from pairs discordant for a history of heavy smoking, or a randomly chosen twin from pairs where both have a history of regular smoking (i.e., has smoked at least 100 cigarettes lifetime), and at least one live biological parent to identify sibships with at least one affected sib pair (ASP) concordant for heavy smoking, and at least one living parent. If permission was granted by the index case, eligible family members were contacted and invited to provide a blood sample and to complete a telephone diagnostic interview. In families with just one available biological parent, and additional unaffected sibling who had never smoked on a regular basis (i.e., has smoked fewer than 100 cigarette lifetime, but has experimented with cigarettes once or twice) was included (when available) to help compensate for the loss of information due to missing parental phenotypes. (Target N=400 Australian families with approximately 600 ASPs; and 600 TDT trios comprised of a nicotine dependent index case and both biological parents). Diagnostic Assessment: The telephone diagnostic interview assessed DSM-IV and modified DSM-IIIR diagnoses (i.e., without time clustering) for nicotine dependence, alcohol and other drug dependence and abuse, major depression, and childhood conduct disorder. Most diagnostic assessments were based on the SSAGA/SSAGA-II, developed for the multi-site gene-mapping alcoholism study (the Collaborative Study on the Genetics of Alcohol. An exception was the tobacco section, which was developed directly from the CIDI and DIS (as the original SSAGA did not include a diagnostic section on nicotine dependence). 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 phs001299

• Genetic Epidemiology of COPD (COPDGene) Funded by the National Heart, Lung, and Blood Institute

  Chronic obstructive pulmonary disease (COPD) is the fourth leading cause of death in the United States and the only leading cause of death that is steadily increasing in frequency. This project will establish a racially diverse cohort that is sufficiently large and appropriately designed for genome-wide association analysis of COPD. A total of 10,000 subjects will be recruited, including control smokers, definite COPD cases (GOLD Stage 2 to 4), and subjects not included in either group (GOLD 1 or GOLD-Unclassified). This cohort will be used for cross-sectional analysis, although long-term longitudinal follow-up will be a future goal. The primary focus of the study will be genome-wide association analysis to identify the genetic risk factors that determine susceptibility for COPD and COPD-related phenotypes. Detailed phenotyping of both cases and controls, including chest CT scan assessment of emphysema and airway disease, will allow identification of genetic determinants for the heterogeneous components of the COPD syndrome. The hypotheses to be studied are: 1) Precise phenotypic characterization of COPD subjects using computed tomography, as well as clinical and physiological measures, will provide data that will enable the broad COPD syndrome to be decomposed into clinically significant subtypes. 2) Genome-wide association studies will identify genetic determinants for COPD susceptibility that will provide insight into clinically relevant COPD subtypes. 3) Distinct genetic determinants influence the development of emphysema and airway disease. The initial phase of genome-wide association analysis included 500 COPD cases and 500 control subjects (all non-Hispanic White) genotyped with the Illumina Omni-1 chip. The second phase genotyped the entire study cohort using the Illumina Omni-Express chip. Unique aspects of the study include: 1) Inclusion of large numbers of African American subjects (approximately 1/3 of the cohort); 2) Obtaining chest CT scans (including inspiratory and expiratory images); and 3) Inclusion of the full range of disease severity. The COPDGene_v6 Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs000179 COPDGene_v6 Cohort. phs000296 ESP LungGO COPDGene phs000765 COPDGene_Geno

  Study phs000179

• Overcoming Clinical Resistance to EZH2 Inhibition Using Rational Epigenetic Combination Therapy

  Essential epigenetic dependencies have become evident in many cancers. Based on functional antagonism between BAF/SWI/SNF and PRC2 in SMARCB1-deficient sarcomas, we and colleagues recently completed the clinical trial of the EZH2 inhibitor tazemetostat, leading to its FDA approval. However, the principles of tumor response to epigenetic therapy in general and tazemetostat in particular remain unknown. Using functional genomics of patient tumors and diverse experimental models, we defined molecular mechanisms of tazemetostat resistance. We found distinct classes of acquired mutations that converge on the RB1/E2F axis, decoupling EZH2-dependent differentiation and cell cycle control. This allows tumor cells to escape tazemetostat-induced G1 arrest despite EZH2 inhibition and suggests a general mechanism for effective EZH2 therapy. Using RNA-sequencing of patient tumor specimens, we identified specific genes as markers of a deficient RB1/E2F axis, which we propose as prospective biomarkers for therapy stratification. This offers a paradigm for rational epigenetic combination therapy suitable for immediate translation to clinical trials.This study was performed on archived tumor tissue collected as part of the above clinical trial at Memorial Sloan Kettering Cancer Center. Patient tumors were classified into "Response" or "Progression" groups based on RECIST 1.1 criteria. "Response" included tumors exhibiting a complete response, partial response, or stable disease. All other tumors were classified under the "Progression" group. Archived frozen tumor samples were weighed and up to 20-30mg were homogenized in RLT buffer, followed by extraction using the AllPrep DNA/RNA Mini Kit (QIAGEN catalog 80204) according to the manufacturer's instructions. RNA was eluted in 13 μL nuclease-free water. After RiboGreen quantification and quality control by Agilent BioAnalyzer, 1 μg of total RNA with DV200 percentages varying from 78% to 100% underwent ribosomal depletion and library preparation using the TruSeq Stranded Total RNA LT Kit (Illumina catalog RS-122-1202) according to instructions provided by the manufacturer with 8 cycles of PCR. Samples were barcoded and sequenced using NovaSeq 6000 in a PE150 mode, with the NovaSeq 6000 S4 Reagent Kit (Illumina). On average, 84 million paired reads were generated per sample and 70% of the data mapped to mRNA. For analysis, read adaptors were trimmed and quality filtered using 'trim_galore' and mapped to GRCh38/hg19 reference genome using STAR v2.7.9 with default parameters.

  Study phs003188