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

scalebar for hic matrix gets cutoff #440

Open
rikrdo89 opened this issue Mar 18, 2023 · 1 comment
Open

scalebar for hic matrix gets cutoff #440

rikrdo89 opened this issue Mar 18, 2023 · 1 comment
Labels

Comments

@rikrdo89
Copy link

When plotting a hic matrix (from a cool file) , using the default settings from the make_tracks_file command, the scalebar gets cutoff on the left. The default transform is log1p, and the values of the scale bar with this transform are expressed as multiples of 10s (n x 10), which makes the label go off the plotting area. Is there a way to assign more plotting area to the left? or to change the notation of the scale bar to avoid using x 10?

Interestingly, when I use log transform, the matrix scale bar that gets plotted does not have any numbers. (is there a way to add them?)

With log1p:
image

With log:
image

Using pyGenomeTracks 3.8

@lldelisle
Copy link
Collaborator

Hi,
Indeed, this is annoying.

  1. a. For the labels that goes out of the image. This is something that I know and I would like to fix and I drafted a PR here: Remove dpi in tracks #292 The trick I use is to export as pdf and open with inkscape so I can get back the labels but I know this is annoying and I hope this will be fix in the 4.0. Unfortunately, for the moment, I do not find the time to change it...
  2. b. For the scientific notation, are you sure it is the log1p? Would you mind to give me the line of the log which says the min-max value? So I can have a look.
  3. I am also aware of this and this is an old piece of code that I would like to change in 4.0. When choosing log or log1p, it forces to use 1, 2, 5, 10, 20, 50 but the developers did not think that we could have values below 1. So when this is the case you get no tick... Sorry.

@lldelisle lldelisle added the bug label Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants