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

UserWarning: set_ticklabels() should only be used with a fixed number of ticks #117

Open
Qingru44004 opened this issue Jan 8, 2024 · 1 comment

Comments

@Qingru44004
Copy link

Hi,

The tool has already produced some plots. But it got stuck and printed this: software/miniconda3/envs/rmats/lib/python3.10/site-packages/MISO/misopy/sashimi_plot/plot_utils/plot_gene.py:454: UserWarning: set_ticklabels() should only be used with a fixed number of ticks, i.e. after set_ticks() or using a FixedLocator.
curr_ax.set_yticklabels(curr_yticklabels,
/home/qingruxu/software/miniconda3/envs/rmats/lib/python3.10/site-packages/MISO/misopy/sashimi_plot/plot_utils/plot_gene.py:454: UserWarning: set_ticklabels() should only be used with a fixed number of ticks, i.e. after set_ticks() or using a FixedLocator.
curr_ax.set_yticklabels(curr_yticklabels,
Saving plot to:

@EricKutschera
Copy link
Contributor

That warning should not cause the program to stop. The warning is just saying that the axis labels might not end up in the expected positions. From https://matplotlib.org/stable/api/_as_gen/matplotlib.axis.Axis.set_ticklabels.html

If you are using this method, you should always fix the tick positions before, e.g. by using Axis.set_ticks or by explicitly setting a FixedLocator. Otherwise, ticks are free to move and the labels may end up in unexpected positions.

If the last thing that was printed was Saving plot to: then it seems the code stopped at this line: https://github.com/Xinglab/rmats2sashimiplot/blob/v3.0.0/src/MISO/misopy/sashimi_plot/Sashimi.py#L97
It should print a file name that includes info about the event being plotted. If some plots were already produced you could check the files in the output directory and compare to the input event files to see which event it was trying to plot

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