-
Notifications
You must be signed in to change notification settings - Fork 0
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
Updating iSEEnrich & iSEEinit #10
Conversation
On it soon! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comments in the specific location - the functionality add-ons are perfectly fine, well done in thinking that out!
We might need to fortify a bit the behavior, see the point where we could add some checks.
The other main thought - how often do we expect to have a list as input? Just asking because a vector is easy to check in its content (it has to be uniform), so would be the column of the dataframe. But a list could be a wild wild west of things that can be placed in the individual elements - a character, a vector, a data.frame, they would simply fit, but our unlist
ing would be brutalized. Are there specific use cases that give us back lists? Otherwise we could think of having only vectors and df supported
clusters <- "Primary.Type" | ||
groups <- "Secondary.Type" | ||
reddim_type <- "PCA" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a pointer again to note down what we can also do: Trigger the errors by selecting wrong values for such parameters - see the comment above about adding some extra checks at the beginning of the function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks fede for the review 🙏 ! i included changes according to your suggestions. I also added a new parameter to call the features column name if |
…nal but leads to a cleaner console output/a full catching round
…iSEEfier into updating_iSEEnrich&iSEEinit
I added a few edits in the tests, mainly to catch all console output types - such as "a message while still throwing an error afterwards", or some specific messages where these are thrown. Otherwise, LGTM 😉 |
Ok, quick correction - we still need two small pieces to be updated, namely
|
Done! I think now it's ready to merge and push into bioconductor repository 😃 |
It is! The GHA failures are somehow due to the orgDb packages, so my guess is that this is transient (I think) |
@federicomarini would you please test the changes i made on the
iSEEinit
andiSEEnrich
functions? I changed thefeatures
input ofiSEEinit
to be anything (vector,list or dataframe). and foriSEEnrich
I added a couple of plots for visualization. Thanks!!