SAGE Documentation

Scenarios View

Displays user scenario(s). A scenario is similar to the concept of a project where it contains a collection of parts (input datasets, output datasets, etc) that are part of the scenario. Users will launch jobs on the HPC machines that run workflows using the inputs in their scenario and when a project completes, the outputs should be added to the users scenario. A user might have multiple scenarios open at once, close scenarios, or even delete scenarios from their scenario view (deleted from the view, but still in the repository) so we'll need to manage which scenarios are in a session and what is their current state (open/closed). For example, I might have scenario A, B and C stored in a local repository, but only A and B are loaded into my application.

Scenario

A scenario will contain user data specific to a scenario (or project).

private String title;
private String description;
private Set<DatasetBean> dataSets;
private RMIServiceBean serviceBean;

Repository View

Contains defined repositories for storing data, scenarios, and beans that describe them. Rather than a single repository view, this might actually be multiple views that are defined to show a particular type of data, something like "Data Repository View" that shows input/output datasets, "Scenario Repository View" that shows all defined scenarios, "Service Repository View" that shows defined RMI service endpoints for launching jobs, etc. This might be too much disparate information to display in a single view.

Repository

Functional Requirements

1. Import datasets that will be used as input to HPC workflows such as Mesh files, input files (e.g. mach number, poisson ratio, etc)
2. Store output datasets
3. Store scenarios
4. Store defined RMI services
5. Store known-hosts