The results of diploid and aneuploid are reversed in test_copykat_heatmap.jpeg, why?

Open
#99 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
r

Research direction

Reproduce the issue with the provided copykat() call and inspect test_copykat_heatmap.jpeg alongside the returned copykat.test object. Trace how diploid and aneuploid labels are assigned and rendered in the heatmap, then verify the behavior across runs. Done means the displayed labels consistently match the underlying classifications or the cause of any intentional reversal is documented.

Written by the indexing model from the issue text.

Description

Sorry to bother you, when I run the following code:
copykat.test <- copykat(rawmat=exp.rawdata,
id.type="S",
ngene.chr=5,
win.size=25,
KS.cut=0.1,
sam.name="test",
distance="euclidean",
norm.cell.names="",
output.seg="FLASE",
plot.genes="TRUE",
genome="hg20",
n.cores=4)
Sometimes, the results of diploid and aneuploid were logical in the test_copykat_heatmap.jpeg; while sometimes the results of diploid and aneuploid were reverse in the test_copykat_heatmap.jpeg. Which should be aneuploid , but titled with diploid. Can you tell me why this happend and how to solve it. Best wish

Dominant language
R
Stars
305
Forks
66
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from navinlabcode/copykat

All issues in navinlabcode/copykat

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.