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

Bioconductor submission? #36

Open
robertamezquita opened this issue Jun 17, 2019 · 5 comments
Open

Bioconductor submission? #36

robertamezquita opened this issue Jun 17, 2019 · 5 comments

Comments

@robertamezquita
Copy link

I saw some tags relating to bioc-check, and just wanted to check in on the status of Cellassign being submitted to BIoconductor. Thanks!

@kieranrcampbell
Copy link
Collaborator

Hi @robertamezquita

It's on the to-do list, and should be priority now. I'd been putting it off because of the tensorflow integration, which I'm not sure will play well with bioc, but will try and submit in the next week or so. Please let us know if any suggestions or requests.

Thanks

Kieran

@LTLA
Copy link

LTLA commented Nov 11, 2019

I've noticed that many of the issues in this repository relate around the installation of the Python dependencies. We've been working on resolving this in the context of Bioconductor packages by providing a central Python instance with a few core packages (including, yes, tensorflow). Repository here - check out the vignette and comments at LTLA/basilisk#2.

@kieranrcampbell
Copy link
Collaborator

Thanks Aaron, this could be a lifesaver. The python/tensorflow experience has not been great. I'll have a look into this when back from holiday in a couple of weeks.

@kieranrcampbell
Copy link
Collaborator

Hey @LTLA

Just made a version of cellassign that uses basilisk, seems to work nicely from my limited testing. What's the overall plan for the package? Is it going into the next Bioconductor release?

Thanks

@LTLA
Copy link

LTLA commented Nov 25, 2019

Is it going into the next Bioconductor release?

I hope so, but we're at a bit of a chicken-and-egg moment; I need to convince the core team that it's useful to get some support for it, but I can't do that until developers use it, and developers can't use it unless it's in Bioconductor.

So a good start would be to keep it on a separate branch but see if it solves any of the installation problems encountered by various users (only on Linux and Mac right now, though); this would provide the evidence of utility that I need.

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

3 participants