[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ECEPCBBADBE6BYPT12KD0A":3,"skill-same:01M7ECEPCBBADBE6BYPT12KD0A":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M7ECEPCBBADBE6BYPT12KD0A","bio-copy-number-recurrent-cnv",null,"Identify recurrent and driver copy number alterations across a tumor cohort with GISTIC2 (G-score, Ziggurat deconstruction, focal vs broad\u002Farm-level analysis, q-values from permutation) and quantify copy-number signatures with the Steele 2022 COSMIC framework and the Drews 2022 CINSignatures framework. Covers driver-gene localization from recurrence peaks, distinguishing focal drivers from arm-level passengers, and the caller-sensitivity caveats of copy-number signatures. Use when finding recurrently amplified or deleted regions in a cohort, localizing driver genes, separating focal from broad events, running GISTIC2, or extracting copy-number mutational signatures.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-copy-number-recurrent-cnv\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bio-copy-number-recurrent-cnv\ndescription: Identify recurrent and driver copy number alterations across a tumor cohort with GISTIC2 (G-score, Ziggurat deconstruction, focal vs broad\u002Farm-level analysis, q-values from permutation) and quantify copy-number signatures with the Steele 2022 COSMIC framework and the Drews 2022 CINSignatures framework. Covers driver-gene localization from recurrence peaks, distinguishing focal drivers from arm-level passengers, and the caller-sensitivity caveats of copy-number signatures. Use when finding recurrently amplified or deleted regions in a cohort, localizing driver genes, separating focal from broad events, running GISTIC2, or extracting copy-number mutational signatures.\ntool_type: mixed\nprimary_tool: gistic2\nsource: \"https:\u002F\u002Fgithub.com\u002FGPTomics\u002FbioSkills\"\nsource_repository: \"GPTomics\u002FbioSkills\"\nsource_path: \"copy-number\u002Frecurrent-cnv\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n## Version Compatibility\n\nReference examples tested with: GISTIC 2.0.23, R 4.3+ with CINSignatureQuantification 1.2+; Python 3.10+ with SigProfilerAssignment 0.1+ (optional, COSMIC CN signatures).\n\nBefore using code patterns, verify installed versions match. If versions differ:\n- CLI: `gistic2 --help` (GISTIC 2.0 is a MATLAB-compiled binary; needs the MCR runtime)\n- R: `packageVersion('CINSignatureQuantification')`\n- Python: `pip show SigProfilerAssignment`\n\nGISTIC 2.0 has had no substantive release since ~2017; it is effectively frozen. It runs as a compiled binary against the MATLAB Compiler Runtime — there is no R or Python package. Verify the reference (`-refgene`) `.mat` file matches the genome build.\n\n# Recurrent and Driver Copy Number Alteration\n\n**\"Which copy number changes recur across my cohort, and which gene is the driver\"** -> A CNV in one tumor is an observation; a CNV recurring across many tumors beyond chance is evidence of selection. GISTIC2 separates recurrent driver events from passengers by modeling a background rate and scoring each locus by how often, and how strongly, it is altered. Copy-number signatures decompose the genome-wide pattern of alterations into the mutational processes that generated them.\n\n- CLI: `gistic2` — cohort-level recurrence, focal vs broad, driver localization\n- R: `CINSignatureQuantification` (Drews 2022); Python `SigProfilerAssignment` (Steele 2022 COSMIC)\n\n## How GISTIC2 Works — and Its Limits\n\nGISTIC2 scores each genomic marker with a **G-score** = frequency of alteration x mean amplitude, separately for amplifications and deletions. Significance (**q-value**) comes from permuting events along the genome under the null that all are passengers. **Ziggurat deconstruction** decomposes each sample's profile into the additive arm-level and focal events that produced it, so the background rate is estimated separately for broad and focal alterations — without this, ubiquitous arm-level events swamp the focal signal. A **peel-off** procedure removes the contribution of each significant peak before testing the next, so one strong driver does not mask its neighbors.\n\nTwo postdoc-level caveats define how GISTIC2 output must be read:\n\n1. **q-values are cohort-size dependent.** Larger N manufactures more \"significant\" peaks. A peak list from N=50 and one from N=500 are not comparable; recurrence *frequency* is the portable quantity, not the q-value.\n2. **GISTIC2 is only as good as its input segmentation.** Oversegmented seg files produce spurious narrow peaks. The seg file must also be correctly **centered** on diploid — a mis-centered profile (WGD genome centered on tetraploid) inverts every call before GISTIC even runs.\n\n## Decision Tree\n\n| Goal | Approach | Notes |\n|------|----------|-------|\n| Find recurrent focal drivers in a cohort | GISTIC2, focal analysis, peak regions | Driver = recurrence-peak gene with a known role |\n| Quantify arm-level \u002F broad events | GISTIC2 `-broad 1`, arm-level output | `-brlen` sets the focal\u002Fbroad length cutoff |\n| Compare cohorts of different size | Recurrence frequency, not q-value | q-value is not portable across N |\n| Characterize mutational processes | Copy-number signatures | Drews CINSignatures or Steele COSMIC CN |\n| Localize the gene within a wide peak | GISTIC2 `-genegistic 1` + known drivers | Wide peaks need orthogonal driver evidence |\n| Single tumor (no cohort) | GISTIC2 does not apply | Use focal-amplification-ecdna \u002F per-sample annotation |\n\n## Running GISTIC2\n\n```bash\n# Segment file: 6 columns -- sample, chrom, start, end, num_markers, seg.mean (log2).\n# It MUST be diploid-centered. Pool per-sample segments (e.g. cnvkit.py export seg).\ngistic2 \\\n    -b gistic_output\u002F \\\n    -seg cohort.seg \\\n    -refgene hg38.refgene.mat \\\n    -genegistic 1 \\\n    -broad 1 \\\n    -brlen 0.7 \\\n    -conf 0.99 \\\n    -armpeel 1 \\\n    -savegene 1 \\\n    -gcm extreme \\\n    -rx 0\n```\n\nKey flags: `-brlen 0.7` sets the focal\u002Fbroad cutoff at 70% of a chromosome arm; `-conf 0.99` is the peak-boundary confidence — raising it above the 0.75 default yields a wider, more conservative peak with higher confidence the true driver gene lies inside it (the trade-off is more genes per peak); `-armpeel 1` peels arm-level events before focal testing; `-genegistic 1` runs the gene-level test; `-rx 0` keeps sex chromosomes. Output `amp_genes.txt` \u002F `del_genes.txt` and `all_lesions.txt` list peaks, q-values, and genes.\n\n## Copy-Number Signatures\n\n**Goal:** Decompose the genome-wide copy-number pattern into mutational processes (HRD, chromothripsis, tandem duplication, ecDNA, whole-genome doubling).\n\n**Approach:** Two competing 2022 frameworks exist. Steele et al (Nature 2022) defined 21 pan-cancer CN signatures from a 48-channel feature matrix, now in COSMIC; Drews et al (Nature 2022) defined 17 signatures via the CINSignatures feature set. Quantify against one framework consistently; signatures require *absolute* (allele-specific) copy number.\n\n```r\nlibrary(CINSignatureQuantification)\n\n# segments: data frame with columns chromosome, start, end, segVal (total CN),\n# sample -- absolute copy number from ASCAT\u002FSequenza\u002FFACETS, NOT relative log2.\nres \u003C- quantifyCNSignatures(segments, experimentName = 'cohort',\n                            method = 'drews')\nactivities \u003C- getActivities(res)   # samples x signatures exposure matrix\n```\n\nThe critical caveat (Steele 2022): three signatures had to be discarded as oversegmentation artifacts and ten were linear combinations needing manual filtering. Signatures are sensitive to the upstream caller — Steele standardizes on ASCAT (SNP6 penalty 70; WGS across the same SNP6 positions) precisely for this reason.\n\n## Failure Modes\n\n### Comparing q-values across cohorts of different size\n\n**Trigger:** Stating that cohort A has \"more significant\" peaks than cohort B when the cohorts differ in N.\n\n**Mechanism:** GISTIC q-values fall as N rises — the same recurrence frequency clears significance in a larger cohort.\n\n**Symptom:** A larger cohort appears to have more drivers purely because it is larger; peak lists do not replicate.\n\n**Fix:** Compare recurrence *frequency* (fraction of samples altered), not q-value, across cohorts. Re-run GISTIC at matched N (subsample) if a significance comparison is unavoidable.\n\n### Oversegmented input produces spurious peaks\n\n**Trigger:** Feeding GISTIC a seg file from a noisy or over-fragmented segmentation.\n\n**Mechanism:** GISTIC interprets every segment edge as a potential focal event boundary; fragmentation creates many narrow false peaks.\n\n**Symptom:** Numerous tiny significant peaks at no known driver; peaks not replicated with a cleaner segmentation.\n\n**Fix:** Quality-control the segmentation first (see copy-ratio-segmentation); merge over-fragmented segments before pooling the cohort seg file.\n\n### Mis-centered seg file inverts everything\n\n**Trigger:** Pooling seg files that are not diploid-centered (e.g. WGD tumors centered on tetraploid).\n\n**Mechanism:** GISTIC assumes seg.mean ~ 0 is diploid; a shifted baseline turns gains into neutral and neutral into losses before any statistics run.\n\n**Symptom:** Amplification and deletion peaks swapped relative to known biology; genome-wide deletion bias.\n\n**Fix:** Center each sample's seg file on its true diploid baseline (anchor with allele-specific ploidy) before pooling. Do not rely on per-sample median centering for aneuploid cohorts.\n\n### Treating a wide GISTIC peak as a single-gene call\n\n**Trigger:** Reporting every gene inside a wide significant peak, or assuming the peak gene is the driver.\n\n**Mechanism:** Peak width reflects breakpoint heterogeneity across the cohort; a wide peak may contain dozens of genes, and the statistical peak need not coincide with the functional driver.\n\n**Symptom:** A multi-gene peak reported as one driver; the named gene is a passenger.\n\n**Fix:** Intersect peaks with known drivers (COSMIC CGC, OncoKB), expression, and dependency data. Raising `-conf` widens the peak (it does not narrow it) — peak width is set by cohort breakpoint heterogeneity, not a tunable. Wide peaks require orthogonal driver evidence — GISTIC localizes, it does not nominate.\n\n### Copy-number signatures from relative copy number\n\n**Trigger:** Running CN signatures on log2 ratios or relative segments.\n\n**Mechanism:** Signature features (segment size, copy-number state, change-point) are defined on absolute copy number; relative input gives meaningless states.\n\n**Symptom:** Implausible signature exposures; ploidy\u002FWGD signatures fire spuriously.\n\n**Fix:** Use absolute allele-specific copy number from ASCAT\u002FSequenza\u002FFACETS as input. Apply the framework's prescribed caller for the platform.\n\n## Reconciliation\n\n| Pattern | Likely cause | Action |\n|---------|--------------|--------|\n| GISTIC peak with no known driver | Wide peak, passenger locus, or fragile site | Cross-check expression\u002Fdependency; treat as candidate |\n| Focal peak inside a broad event | Arm-level event not peeled | Confirm `-armpeel 1`; inspect Ziggurat output |\n| Drews vs Steele signatures disagree | Different feature definitions and reference sets | Pick one framework; do not mix exposures |\n| Peaks change with segmentation | Input over\u002Funder-segmented | Stabilize segmentation; re-run |\n\n**Operational rule:** Report a GISTIC peak as a candidate driver locus only when (1) the input segmentation is QC-passed and diploid-centered, (2) recurrence frequency (not just q-value) is substantial, and (3) the peak contains a gene with independent driver evidence. Signatures are reportable only from absolute CN with a single, platform-matched framework.\n\n## Quantitative Thresholds\n\n| Threshold | Value | Source \u002F Rationale |\n|-----------|-------|--------------------|\n| GISTIC significance | q \u003C 0.25 | GISTIC2 default residual-q cutoff for peaks |\n| Peak-boundary confidence | `-conf 0.99` | Wider, conservative peak; higher confidence the true driver is inside (default 0.75) |\n| Focal\u002Fbroad cutoff | `-brlen 0.7` | Events > 70% of an arm are treated as broad |\n| Cohort size for stable peaks | tens to hundreds | Too few samples gives unstable peaks; q is N-dependent |\n| CN signatures input | absolute (allele-specific) CN | Steele 2022 \u002F Drews 2022; relative log2 is invalid |\n\n## Common Errors\n\n| Error \u002F symptom | Cause | Solution |\n|-----------------|-------|----------|\n| GISTIC2 will not start | MATLAB Compiler Runtime missing | Install the MCR version GISTIC was built against |\n| Amp\u002Fdel peaks swapped vs biology | Seg file not diploid-centered | Center on true ploidy before pooling |\n| Many tiny spurious peaks | Oversegmented input | QC and merge segmentation first |\n| `-refgene` errors | Build mismatch (hg19 vs hg38 .mat) | Use the matching reference .mat |\n| Implausible signature exposures | Relative CN used as input | Use absolute allele-specific CN |\n| Peak lists do not replicate | q-value compared across different N | Compare recurrence frequency |\n\n## References\n\n- Mermel CH et al 2011. GISTIC2.0 facilitates sensitive and confident localization of the targets of focal somatic copy-number alteration in human cancers. Genome Biol 12:R41\n- Beroukhim R et al 2010. The landscape of somatic copy-number alteration across human cancers. Nature 463:899\n- Steele CD et al 2022. Signatures of copy number alterations in human cancer. Nature 606:984\n- Drews RM et al 2022. A pan-cancer compendium of chromosomal instability. Nature 606:976\n- Macintyre G et al 2018. Copy number signatures and mutational processes in ovarian carcinoma. Nat Genet 50:1262\n\n## Related Skills\n\n- copy-number\u002Fallele-specific-copy-number - Absolute CN input for GISTIC and CN signatures\n- copy-number\u002Fcopy-ratio-segmentation - Segmentation quality controlling GISTIC peaks\n- copy-number\u002Fcnv-annotation - Annotating GISTIC peaks with genes and driver roles\n- copy-number\u002Ffocal-amplification-ecdna - Resolving the architecture of focal amplicons\n- copy-number\u002Fcnv-visualization - Cohort heatmaps of recurrent CNV\n- pathway-analysis\u002Fgo-enrichment - Pathway context for recurrently altered genes\n","## Version Compatibility\n\nReference examples tested with: GISTIC 2.0.23, R 4.3+ with CINSignatureQuantification 1.2+; Python 3.10+ with SigProfilerAssignment 0.1+ (optional, COSMIC CN signatures).\n\nBefore using code patterns, verify installed versions match. If versions differ:\n- CLI: `gistic2 --help` (GISTIC 2.0 is a MATLAB-compiled binary; needs the MCR runtime)\n- R: `packageVersion('CINSignatureQuantification')`\n- Python: `pip show SigProfilerAssignment`\n\nGISTIC 2.0 has had no substantive release since ~2017; it is effectively frozen. It runs as a compiled binary against the MATLAB Compiler Runtime — there is no R or Python package. Verify the reference (`-refgene`) `.mat` file matches the genome build.\n\n# Recurrent and Driver Copy Number Alteration\n\n**\"Which copy number changes recur across my cohort, and which gene is the driver\"** -> A CNV in one tumor is an observation; a CNV recurring across many tumors beyond chance is evidence of selection. GISTIC2 separates recurrent driver events from passengers by modeling a background rate and scoring each locus by how often, and how strongly, it is altered. Copy-number signatures decompose the genome-wide pattern of alterations into the mutational processes that generated them.\n\n- CLI: `gistic2` — cohort-level recurrence, focal vs broad, driver localization\n- R: `CINSignatureQuantification` (Drews 2022); Python `SigProfilerAssignment` (Steele 2022 COSMIC)\n\n## How GISTIC2 Works — and Its Limits\n\nGISTIC2 scores each genomic marker with a **G-score** = frequency of alteration x mean amplitude, separately for amplifications and deletions. Significance (**q-value**) comes from permuting events along the genome under the null that all are passengers. **Ziggurat deconstruction** decomposes each sample's profile into the additive arm-level and focal events that produced it, so the background rate is estimated separately for broad and focal alterations — without this, ubiquitous arm-level events swamp the focal signal. A **peel-off** procedure removes the contribution of each significant peak before testing the next, so one strong driver does not mask its neighbors.\n\nTwo postdoc-level caveats define how GISTIC2 output must be read:\n\n1. **q-values are cohort-size dependent.** Larger N manufactures more \"significant\" peaks. A peak list from N=50 and one from N=500 are not comparable; recurrence *frequency* is the portable quantity, not the q-value.\n2. **GISTIC2 is only as good as its input segmentation.** Oversegmented seg files produce spurious narrow peaks. The seg file must also be correctly **centered** on diploid — a mis-centered profile (WGD genome centered on tetraploid) inverts every call before GISTIC even runs.\n\n## Decision Tree\n\n| Goal | Approach | Notes |\n|------|----------|-------|\n| Find recurrent focal drivers in a cohort | GISTIC2, focal analysis, peak regions | Driver = recurrence-peak gene with a known role |\n| Quantify arm-level \u002F broad events | GISTIC2 `-broad 1`, arm-level output | `-brlen` sets the focal\u002Fbroad length cutoff |\n| Compare cohorts of different size | Recurrence frequency, not q-value | q-value is not portable across N |\n| Characterize mutational processes | Copy-number signatures | Drews CINSignatures or Steele COSMIC CN |\n| Localize the gene within a wide peak | GISTIC2 `-genegistic 1` + known drivers | Wide peaks need orthogonal driver evidence |\n| Single tumor (no cohort) | GISTIC2 does not apply | Use focal-amplification-ecdna \u002F per-sample annotation |\n\n## Running GISTIC2\n\n```bash\n# Segment file: 6 columns -- sample, chrom, start, end, num_markers, seg.mean (log2).\n# It MUST be diploid-centered. Pool per-sample segments (e.g. cnvkit.py export seg).\ngistic2 \\\n    -b gistic_output\u002F \\\n    -seg cohort.seg \\\n    -refgene hg38.refgene.mat \\\n    -genegistic 1 \\\n    -broad 1 \\\n    -brlen 0.7 \\\n    -conf 0.99 \\\n    -armpeel 1 \\\n    -savegene 1 \\\n    -gcm extreme \\\n    -rx 0\n```\n\nKey flags: `-brlen 0.7` sets the focal\u002Fbroad cutoff at 70% of a chromosome arm; `-conf 0.99` is the peak-boundary confidence — raising it above the 0.75 default yields a wider, more conservative peak with higher confidence the true driver gene lies inside it (the trade-off is more genes per peak); `-armpeel 1` peels arm-level events before focal testing; `-genegistic 1` runs the gene-level test; `-rx 0` keeps sex chromosomes. Output `amp_genes.txt` \u002F `del_genes.txt` and `all_lesions.txt` list peaks, q-values, and genes.\n\n## Copy-Number Signatures\n\n**Goal:** Decompose the genome-wide copy-number pattern into mutational processes (HRD, chromothripsis, tandem duplication, ecDNA, whole-genome doubling).\n\n**Approach:** Two competing 2022 frameworks exist. Steele et al (Nature 2022) defined 21 pan-cancer CN signatures from a 48-channel feature matrix, now in COSMIC; Drews et al (Nature 2022) defined 17 signatures via the CINSignatures feature set. Quantify against one framework consistently; signatures require *absolute* (allele-specific) copy number.\n\n```r\nlibrary(CINSignatureQuantification)\n\n# segments: data frame with columns chromosome, start, end, segVal (total CN),\n# sample -- absolute copy number from ASCAT\u002FSequenza\u002FFACETS, NOT relative log2.\nres \u003C- quantifyCNSignatures(segments, experimentName = 'cohort',\n                            method = 'drews')\nactivities \u003C- getActivities(res)   # samples x signatures exposure matrix\n```\n\nThe critical caveat (Steele 2022): three signatures had to be discarded as oversegmentation artifacts and ten were linear combinations needing manual filtering. Signatures are sensitive to the upstream caller — Steele standardizes on ASCAT (SNP6 penalty 70; WGS across the same SNP6 positions) precisely for this reason.\n\n## Failure Modes\n\n### Comparing q-values across cohorts of different size\n\n**Trigger:** Stating that cohort A has \"more significant\" peaks than cohort B when the cohorts differ in N.\n\n**Mechanism:** GISTIC q-values fall as N rises — the same recurrence frequency clears significance in a larger cohort.\n\n**Symptom:** A larger cohort appears to have more drivers purely because it is larger; peak lists do not replicate.\n\n**Fix:** Compare recurrence *frequency* (fraction of samples altered), not q-value, across cohorts. Re-run GISTIC at matched N (subsample) if a significance comparison is unavoidable.\n\n### Oversegmented input produces spurious peaks\n\n**Trigger:** Feeding GISTIC a seg file from a noisy or over-fragmented segmentation.\n\n**Mechanism:** GISTIC interprets every segment edge as a potential focal event boundary; fragmentation creates many narrow false peaks.\n\n**Symptom:** Numerous tiny significant peaks at no known driver; peaks not replicated with a cleaner segmentation.\n\n**Fix:** Quality-control the segmentation first (see copy-ratio-segmentation); merge over-fragmented segments before pooling the cohort seg file.\n\n### Mis-centered seg file inverts everything\n\n**Trigger:** Pooling seg files that are not diploid-centered (e.g. WGD tumors centered on tetraploid).\n\n**Mechanism:** GISTIC assumes seg.mean ~ 0 is diploid; a shifted baseline turns gains into neutral and neutral into losses before any statistics run.\n\n**Symptom:** Amplification and deletion peaks swapped relative to known biology; genome-wide deletion bias.\n\n**Fix:** Center each sample's seg file on its true diploid baseline (anchor with allele-specific ploidy) before pooling. Do not rely on per-sample median centering for aneuploid cohorts.\n\n### Treating a wide GISTIC peak as a single-gene call\n\n**Trigger:** Reporting every gene inside a wide significant peak, or assuming the peak gene is the driver.\n\n**Mechanism:** Peak width reflects breakpoint heterogeneity across the cohort; a wide peak may contain dozens of genes, and the statistical peak need not coincide with the functional driver.\n\n**Symptom:** A multi-gene peak reported as one driver; the named gene is a passenger.\n\n**Fix:** Intersect peaks with known drivers (COSMIC CGC, OncoKB), expression, and dependency data. Raising `-conf` widens the peak (it does not narrow it) — peak width is set by cohort breakpoint heterogeneity, not a tunable. Wide peaks require orthogonal driver evidence — GISTIC localizes, it does not nominate.\n\n### Copy-number signatures from relative copy number\n\n**Trigger:** Running CN signatures on log2 ratios or relative segments.\n\n**Mechanism:** Signature features (segment size, copy-number state, change-point) are defined on absolute copy number; relative input gives meaningless states.\n\n**Symptom:** Implausible signature exposures; ploidy\u002FWGD signatures fire spuriously.\n\n**Fix:** Use absolute allele-specific copy number from ASCAT\u002FSequenza\u002FFACETS as input. Apply the framework's prescribed caller for the platform.\n\n## Reconciliation\n\n| Pattern | Likely cause | Action |\n|---------|--------------|--------|\n| GISTIC peak with no known driver | Wide peak, passenger locus, or fragile site | Cross-check expression\u002Fdependency; treat as candidate |\n| Focal peak inside a broad event | Arm-level event not peeled | Confirm `-armpeel 1`; inspect Ziggurat output |\n| Drews vs Steele signatures disagree | Different feature definitions and reference sets | Pick one framework; do not mix exposures |\n| Peaks change with segmentation | Input over\u002Funder-segmented | Stabilize segmentation; re-run |\n\n**Operational rule:** Report a GISTIC peak as a candidate driver locus only when (1) the input segmentation is QC-passed and diploid-centered, (2) recurrence frequency (not just q-value) is substantial, and (3) the peak contains a gene with independent driver evidence. Signatures are reportable only from absolute CN with a single, platform-matched framework.\n\n## Quantitative Thresholds\n\n| Threshold | Value | Source \u002F Rationale |\n|-----------|-------|--------------------|\n| GISTIC significance | q \u003C 0.25 | GISTIC2 default residual-q cutoff for peaks |\n| Peak-boundary confidence | `-conf 0.99` | Wider, conservative peak; higher confidence the true driver is inside (default 0.75) |\n| Focal\u002Fbroad cutoff | `-brlen 0.7` | Events > 70% of an arm are treated as broad |\n| Cohort size for stable peaks | tens to hundreds | Too few samples gives unstable peaks; q is N-dependent |\n| CN signatures input | absolute (allele-specific) CN | Steele 2022 \u002F Drews 2022; relative log2 is invalid |\n\n## Common Errors\n\n| Error \u002F symptom | Cause | Solution |\n|-----------------|-------|----------|\n| GISTIC2 will not start | MATLAB Compiler Runtime missing | Install the MCR version GISTIC was built against |\n| Amp\u002Fdel peaks swapped vs biology | Seg file not diploid-centered | Center on true ploidy before pooling |\n| Many tiny spurious peaks | Oversegmented input | QC and merge segmentation first |\n| `-refgene` errors | Build mismatch (hg19 vs hg38 .mat) | Use the matching reference .mat |\n| Implausible signature exposures | Relative CN used as input | Use absolute allele-specific CN |\n| Peak lists do not replicate | q-value compared across different N | Compare recurrence frequency |\n\n## References\n\n- Mermel CH et al 2011. GISTIC2.0 facilitates sensitive and confident localization of the targets of focal somatic copy-number alteration in human cancers. Genome Biol 12:R41\n- Beroukhim R et al 2010. The landscape of somatic copy-number alteration across human cancers. Nature 463:899\n- Steele CD et al 2022. Signatures of copy number alterations in human cancer. Nature 606:984\n- Drews RM et al 2022. A pan-cancer compendium of chromosomal instability. Nature 606:976\n- Macintyre G et al 2018. Copy number signatures and mutational processes in ovarian carcinoma. Nat Genet 50:1262\n\n## Related Skills\n\n- copy-number\u002Fallele-specific-copy-number - Absolute CN input for GISTIC and CN signatures\n- copy-number\u002Fcopy-ratio-segmentation - Segmentation quality controlling GISTIC peaks\n- copy-number\u002Fcnv-annotation - Annotating GISTIC peaks with genes and driver roles\n- copy-number\u002Ffocal-amplification-ecdna - Resolving the architecture of focal amplicons\n- copy-number\u002Fcnv-visualization - Cohort heatmaps of recurrent CNV\n- pathway-analysis\u002Fgo-enrichment - Pathway context for recurrently altered genes\n",{"name":5,"source":24,"license":15,"tool_type":25,"description":7,"imported_at":26,"source_path":27,"primary_tool":28,"source_repository":29},"https:\u002F\u002Fgithub.com\u002FGPTomics\u002FbioSkills","mixed","2026-09-20","copy-number\u002Frecurrent-cnv\u002FSKILL.md","gistic2","GPTomics\u002FbioSkills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fbiology\u002Fbio-copy-number-recurrent-cnv","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bio-copy-number-recurrent-cnv",{"tool":42,"command":43},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bio-copy-number-recurrent-cnv",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bio-copy-number-recurrent-cnv","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-copy-number-recurrent-cnv\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"examples\u002Frun_gistic2.sh","SCRIPT","脚本",1749,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-copy-number-recurrent-cnv\u002Fexamples\u002Frun_gistic2.sh",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"usage-guide.md","REFERENCE","参考文档",4282,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fbiology\u002Fbio-copy-number-recurrent-cnv\u002Fusage-guide.md",[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":70},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":70},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":70},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":70},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":70},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]