User Details
- User Since
- Aug 1 2016, 12:10 PM (339 w, 6 d)
Oct 13 2022
Jun 9 2022
I like the results when the scales library is used! However, when we find a way to bring back the confidence intervals, also @wiesenfa's latest solution can be used.
Jun 3 2022
First, I tried the fix with R 3.6 and can confirm that it does not break the functionality there.
May 6 2022
Could someone with R v4 double-check locally as well?
I checked on my local Windows system (R 3.6.3) and the plots seem to be correct.
Feb 11 2022
I have tested this with the provided data. The scaling of the y-axis seems to be correct now. But only the first rank is labeled on the y-axis. Can the other ranks be labeled as well?
Jan 28 2022
Thank you for investigating this! In challengeR it is covered in the way that a message is emitted saying "na.treat obligatory if report is intended to be compiled". In order to solve the mentioned issue 2, a strategy for the preferred way to handle it in VISSART should be defined. Should the user be guided to specify the NaN handling strategy? Should the user be able to generate a report but without the plots that require numeric values?
Oct 28 2021
Oct 22 2021
Oct 15 2021
One solution to approach this issue is to check if NaN values are present in the data. If so, the user should be able to select the NaN handling strategy if necessary (e.g., not for case-based ranking). So what about providing the NaN handling options after the chosen ranking method is known?
Sep 29 2021
Successfully checked the proposed fix on a Windows system for downward compatibility (R 3.6.3, ggplot2 3.3.0).
Aug 2 2021
May 7 2021
May 6 2021
Apr 26 2021
Apr 23 2021
Do you have a minimum example to reproduce this? Would be great to have that in the test checklists as well.
Mar 3 2021
In this case we solved it by upgrading BiocManager. Probably the previous version did not know about the later version of "graph".
The package "graph" was moved from CRAN to Bioconductor:
https://cran.r-project.org/web/packages/graph/index.html
Jan 28 2021
Jan 27 2021
This issue will be fixed in v1.0.1.
An update is also required in report.Rmd, visualizations.Rmd and CITATION.
This issue will be fixed in v1.0.1.