The main WIPP UI application, for uploading images, creating image processing workflows and much more.
Developped in Angular 7.

Run npm ci to install dependencies using versions locked in package-lock.json for reproducibility.

A configuration file defining links between the WIPP-frontend and other tools must be placed at src/assets/config/config.json.
The following properties are expected to be defined in this file:

• argoUiBaseUrl: URL of the Argo Workflows Dashboard, for workflow execution monitoring,
• tensorboardUrl: URL of TensorBoard, for TensorFlow jobs monitoring,
• jupyterNotebooksUrl: URL of JupyterHub, for Jupyter Notebooks,
• plotsUiUrl: URL of Plots app for scatterplots visualization.

We provide a sample configuration file sample-config.json at the root of this repository defining a default configuration for the Argo Dashboard URL at localhost:30501 (sample argo-ui service patch to achieve this configuration available here).
This sample configuration file assumes that the other tools are not deployed and will redirect to "Page not found" in a development setup.

Please refer to the main WIPP repository to learn more about external tools configuration for WIPP.

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Modify the environment property apiRootUrl in the environment.ts file from apiRootUrl: 'http://localhost:8080/api' to apiRootUrl: 'http://*IP_ADDRESS*:8080/api' (*IP_ADDRESS* being the IP address of your machine).

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Run ng test to execute the unit tests via Karma.

Run ng e2e to execute the end-to-end tests via Protractor.

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

We are following the Gitflow branching model for the WIPP development.

Please follow the Contributing guidelines

NIST Disclaimer