-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Bug]: How does one change the x-axis label for plots using tm_g_ipp? #915
Comments
Thanks @krissy-bios for reporting and sharing your broader use case, we'll look into it. |
Hi @krissy-bios, Although this does not fix some of the displayed text hard-coded into the options panel for the module, please note that for now you can customize the x-axis text via the
Let me know if this helps! |
Hi, chiming in here (I work along side Krissy :D) : Would this solve this issue? In the example we're using three different visit variables. So would need to dynamically update the x-axis label based on what variable is selected as the visit variable. Please see example below on how how we implement tm_g_ipp:
|
What happened?
How do I change the x-axis label for the timepoint variable? One feature of teal that we love is the ability to select the x-axis variable from a drop down menu since we have varying definitions of timepoint in our study. However, there doesn't appear to be a way to change the x-axis label associated with this variable. This is a bug, or an oversight, because it creates incorrect plots if the label "Visit" is the appropriate selection. Nor does it allow me to add the units of the visit variable to the axis label, which is also important. In addition, it is feasible to also create plots across the age of the individual, not simply the time. Retaining the x-axis simply as a timepoint variable prevents one from utilizing the graphing future to its fullest extent. Please let me know if I am missing this in the documentation or if this is a change that may be made in the program itself. Thank you!
sessionInfo()
No response
Relevant log output
No response
Code of Conduct
Contribution Guidelines
Security Policy
The text was updated successfully, but these errors were encountered: