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

Updating iSEEnrich & iSEEinit #10

Merged
merged 22 commits into from
Oct 4, 2024
Merged

Conversation

NajlaAbassi
Copy link
Owner

@federicomarini would you please test the changes i made on the iSEEinit and iSEEnrich functions? I changed the features input of iSEEinit to be anything (vector,list or dataframe). and for iSEEnrich I added a couple of plots for visualization. Thanks!!

@federicomarini
Copy link
Collaborator

On it soon!

Copy link
Collaborator

@federicomarini federicomarini left a 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 unlisting would be brutalized. Are there specific use cases that give us back lists? Otherwise we could think of having only vectors and df supported

R/iSEEinit.R Outdated Show resolved Hide resolved
R/iSEEinit.R Show resolved Hide resolved
R/iSEEnrich.R Show resolved Hide resolved
R/iSEEnrich.R Show resolved Hide resolved
Comment on lines +6 to +8
clusters <- "Primary.Type"
groups <- "Secondary.Type"
reddim_type <- "PCA"
Copy link
Collaborator

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

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@NajlaAbassi
Copy link
Owner Author

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 features is data.frame 2ba6ac4

…nal but leads to a cleaner console output/a full catching round
@federicomarini
Copy link
Collaborator

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 😉

@federicomarini
Copy link
Collaborator

federicomarini commented Oct 2, 2024

Ok, quick correction - we still need two small pieces to be updated, namely

  • the News.md file (useful to let others know what we added, gets "published upon release" by Bioc)
  • the DESCRIPTION to have a proper version bump, so that the changes propagate & the package gets the build triggered once we push upstream

@NajlaAbassi
Copy link
Owner Author

Ok, quick correction - we still need two small pieces to be updated, namely

* [x]  the News.md file (useful to let others know what we added, gets "published upon release" by Bioc)

* [x]  the DESCRIPTION to have a proper version bump, so that the changes propagate & the package gets the build triggered once we push upstream

Done! I think now it's ready to merge and push into bioconductor repository 😃

@federicomarini
Copy link
Collaborator

It is!
Merge & push 😉

The GHA failures are somehow due to the orgDb packages, so my guess is that this is transient (I think)

@NajlaAbassi NajlaAbassi merged commit 980b074 into devel Oct 4, 2024
1 of 4 checks passed
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

Successfully merging this pull request may close these issues.

2 participants