Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

heatmap - name and position of gene of itnerest #1133

Open
mvukk opened this issue Mar 29, 2022 · 1 comment
Open

heatmap - name and position of gene of itnerest #1133

mvukk opened this issue Mar 29, 2022 · 1 comment

Comments

@mvukk
Copy link

mvukk commented Mar 29, 2022

Dear all,

For my data set, I am interested how it looks over TSS throughout different chromosome, however once I got the result I noticed some regions really pop out (in blue on the example shown below). And I would like to know what are those TSS exactly. Is it possible to extract information and if yes how?

image

Also for a different question that I have I would like to get position on the heatmap of my gene(s) of interest (example provided below), eg. adding a gene label/name on a heatmap, is that possible and if yes how?

image
Thank you,
Regards,
Maja

@dpryan79
Copy link
Collaborator

The .mat.gz file that's used as input into plotHeatmap is just a compressed text file that's (more or less) human readable. I'm pretty sure the name of the feature is present on each line in there.

Regarding your second question, you can't print labels for each row in the heatmap. Unless you only have a few genes/transcripts/etc. the labels would be too small to be readable (we typically don't even print each row in the heatmap, since it's smaller than a pixel!). What you can do is specify multiple region files when you run compute matrix. Have a look here for an example: https://deeptools.readthedocs.io/en/develop/content/tools/plotHeatmap.html#usage-examples

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants