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

Usage instructions unclear #16

Open
andreped opened this issue Aug 30, 2022 · 4 comments
Open

Usage instructions unclear #16

andreped opened this issue Aug 30, 2022 · 4 comments

Comments

@andreped
Copy link
Contributor

Just tried to install the generated binary release from the latest artefact and it crashes.

I believe we should thoroughly test if the software can be run as a binary.

Ideally, the user should not need to run anything from the terminal, that somewhat defeats the purpose of having a user friendly tool, if the end user is forced to open a terminal to use the tool.

Might be that we have to run something from the terminal, for instance to setup training on the server, but ideally we should not need to.

Perhaps we could schedule a meeting discussing this further and getting RootPainter3D running on my machine?

When all this is running it would also be ideal to make a simple tutorial video demonstrating how to get started and using the software :) We could make this as an Issue (or feature request rather) when that is relevant.

@Abe404
Copy link
Owner

Abe404 commented Aug 31, 2022

The client and server are designed to be ran on different machines.

The server is typically ran from source, while the client installers should work OK. At least they used to, and I am sure it wont be hard to get this working again.

I think there are benefits to keeping them separate as in many situations the client machine does not have a suitable GPU and the only way to run the application is via connection to a remote GPU.

So the client build process is not a problem for me using my old scripts, but I'm not sure I totally understand what you have done recently so we might need to work through that together.

Bundling the server into the client installer might be really tricky, as it has a dependency on pytorch and CUDA. I'm also not sure it fits the intended use case.

@Abe404
Copy link
Owner

Abe404 commented Aug 31, 2022

I will work on creating some instructions. They will include terminal though. The idea is that teams are composed of people with different abilities. Someone (linux sys admin) can setup the server and get it started and then other users (no command line / terminal knowledge) can just install the client that connects with the server. This is based on what was developed / proposed for https://nph.onlinelibrary.wiley.com/doi/full/10.1111/nph.18387 or preprint: https://www.biorxiv.org/content/10.1101/2020.04.16.044461v1.full

Moving away from this model might not be entirely straight forward, but perhaps there is also scope for a more streamlined installer for users who have high powered deep learning workstations. That would include an application that bundled both client and server in one installer (I get the impression that's what you are looking for?).

@Abe404 Abe404 self-assigned this Aug 31, 2022
@Abe404
Copy link
Owner

Abe404 commented Aug 31, 2022

I downloaded the hepatic vessels data from http://medicaldecathlon.com/

I will work on trying to get a model that segments something in this dataset and then try to detail the install process.

@Abe404
Copy link
Owner

Abe404 commented Aug 31, 2022

We agreed a video is a good way to solve this. With an installation guide per OS. Perhaps a video per OS also.

But first we will get the auto-build of the installers working as discussed here: #19

@Abe404 Abe404 removed their assignment Jun 22, 2023
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

2 participants