Projects
A RiskScape Platform Project provides a place for project members to collaborate on RiskScape models.
A RiskScape project has:
models
results from model runs
files
members
settings
Project Members
Project members can be added either:
Directly to the project by a project admin or,
Automatically from the group
Add a project member directly to the project
This requires the project admin role on the project.
To add a new member to a project:
Go to the Settings > Members page
Select Add Member
You will be presented with a pop up window Add Member to Project
You will need to search for the user by Name or Username
Once you have found the correct user, click on their name. This will populate the Name or username field.
Select a role for the user in the project
Select Add to Project
The next time the user logs into the RiskScape platform, your project will appear on their home page.
Remove a project member from the project
This requires the project admin role on the project.
To remove a project member directly added to a project:
Go to the Settings > Members page
Locate the member to be removed
Select the - icon
Confirm that you wish to Remove the member from the project
You will receive a message in the top right of the screen to confirm that the member has been removed from the project and they will no longer appear in the project member listing.
A project member who has been added at the group level can only be removed by an Organization Admin.
Project Settings
Platform managed engines
A project admin can select all model runs for the project to be run in the cloud using a platform managed engine.
Tip
This is the preferred approach for most projects and organizations.
In this mode, each time a user goes to run a model, a cloud based engine instance will be allocated to them. The platform will pass the model parameters and files to the engine, run the model to get the results, send these results to the platform and then shut down.
Platform managed engines only run when they are needed. Viewing project files, including results, does not require an engine instance to be running.
Each member gets allocated an engine when they run a model. This means that if multiple members need to run the model at the same time, they do not block each other.
Project Admins can nominate the size of engine used by all members of their project.
Note
All cloud based engine usage charges for a project are passed through to the Organization that owns the project. This includes all usage of a project by project members outside of the owner organization.
User provided static engines
Tip
There are security implications to this approach that need to be understood, mitigated and approved by your Organization.
Rather than using a platform managed engine instance, a project admin can configure their project to engine running on a local computer.
This is a custom configuration that will need the support of Catalyst support engineers to setup. It involves the use of a reverse proxy that may not be allowed by your organization. Please consult with your IT department first.
Note
Catalyst support engineers can not provide support for User provided static engines.
Once configured, your local engine instance will make a connection to the RiskScape platform. With this connection in place the platform will then be able to pass the model parameters and files required to the host machine. The local host will run the model and then transfer the results back to the platform to be shared with other users.
Note
This approach will require your local machine to be able to connect to the platform and to be available for all project members as required to run models.
By using a provided static engine, the project will not incur engine cloud charges. The project will incur platform storage charges for the files and results stored in the platform.
When using a user provided static engine, only one model can be run at a time. If multiple model runs are started, these will queue up on the static engine instance.