search

UCSB-VRL / bisqueUCSB

An ML Platform for storing, analyzing, and visualizing your data all in the browser.
https://bisque2.ece.ucsb.edu
Other
35 stars 10 forks source link
bioinformatics cloud-computing computer-vision deep-learning docker image-processing kubernetes machine-learning medical-imaging python threejs

readme

workflow

🔭 Overview

DOCUMENTATION

BisQue is a web-based platform specifically designed to provide researchers with organizational and quantitative analysis tools for up to 5D image data. Users can extend BisQue by creating their own modules that take advantage of cutting edge machine learning algorithms. BisQue’s extensibility stems from two core concepts: flexible metadata facility and an open web-based architecture. Together these empower researchers to create, develop and share novel multimodal data analyses.

💡 Features

Start using BisQue now by Requesting an account!

✅ Getting Started

Docker Installation

asciicast

Download

Ensure you have the latest release by first running the following pull command:

  docker pull amilworks/bisque-module-dev:git

Intro: BisQue Docker Container

Run the BisQue Docker Container

To run the docker version of BisQue locally, start a bisque server on the host port 8080:

docker run --name bisque --rm -p 8080:8080 amilworks/bisque-module-dev:git

and point your browser at http://localhost:8080. You should see a BisQue homepage similar to the one on bisque2.ece.ucsb.edu. If you do not see the homepage, check to make sure that port 8080 is not being used by another container or application and that you have correctly mapped the ports using -p 8080:8080, where -p is short for port.

Registering Modules

To register all the modules to your local server:

Custom Modules, Copying Folders out of the Container

If you would like to build and test your own module locally, using host mounted modules will make life easier to build, test, debug, and deploy locally.

  1. Copy the module directory out of the container and into the folder on your local system named container-modules. 

         docker cp bisque:/source/modules container-modules
  2. Copy your module into the container-modules folder on your local system.

  3. Restart the container with host mounted modules. Be careful with the command $(pwd)/container-modules that we are using here. If the /container-modules is not in the specified path, you will not see any of the modules during the registration process.

      docker stop bisque
  docker run --name bisque --rm -p 8080:8080 -v $(pwd)/container-modules:/source/modules  amilworks/bisque-module-dev:git
  4. Register your module from the above steps in "3. Registering Modules. ", using the Module Manager.

Pushing your Module to Production. If you feel that your module is ready to be added to the production version of BisQue, please feel free to contact us and we will gladly begin the process.

Data Storage

Use an external data directory so you don't lose data when the service stops

docker run --name bisque --rm -p 8080:8080 -v $(pwd)/container-data:/source/data  amilworks/bisque-module-dev:git

View Downloaded Images, Running Containers

List all the docker images on your system:

docker images

List all running containers on your system:

docker ps

SSH into the Container

If you would like to see everything inside the container, you can use the following command while the container is running:

docker exec -it amilworks/bisque-module-dev:git bash

The -it flag enables you to run interactively inside the container. There are numerous other flags you can take advantage of as shown here:

--detach ,      -d    Detached mode: run command in the background
--detach-keys         Override the key sequence for detaching a container
--env ,         -e    Set environment variables
--interactive , -i    Keep STDIN open even if not attached
--privileged          Give extended privileges to the command
--tty ,         -t    Allocate a pseudo-TTY
--user ,        -u    Username or UID (format: <name|uid>[:<group|gid>])
--workdir ,     -w    Working directory inside the container

Now, let's say you want to ssh into an image without fully starting BisQue. More precisely, you want to ssh into a non-running container. You can accomplish this by running:

docker run -it amilworks/bisque-module-dev:git bash

If you want to exit, simply type exit and you will be taken back outside of the container.

Stop the Container

Say you are done playing with your container for today, you can stop the container by using the following command:

docker stop amilworks/bisque-module-dev:git 
docker stop {YOUR_CONTAINER_NAME} #  <--- If you named the container

💾 Documentation

BisQue Documentation

The official documentation covers the BisQue cloud service running live at UCSB, module development for the platform, and the BQAPI. If you have any questions, feel free to reach out. We will be continuously updating the documentation so check back often for updates!

Papers using BisQue

Team

Acknowledgments

License