Running Feel++ Applications in the Portal

when running into some strange portal behavior, first try to logout/login from the portal before reporting an issue.

1. Purchase a Feel++ application

To purchase an application from the Marketplace you have to be registered and logged in as a EndUser at least.

The process is the following:

  • connect to the Marketplace, in Home (top left Marketplace page) you will find all available apps (All categories).

  • Click on Add to Cart to purchase the app you want.

  • Click on Shopping Cart and Checkout to go on

    • fill the required forms for shipping address

    • provide a shipping address if not already defined

    • provide a billing address if not already defined

    • Finalize your order by clicking on Checkout

To use the app, you will have to wait that the owner/seller of the app validate you order. To check the status of your order:

  • go to My Inventory

  • go to Product Orders

You shall be able to see your products and their status in each product form.

2. Benchmarks and Examples Catalogue

Go to the Feel++ Case Studies guide to discover examples and benchmarks for the different Feel++ applications.

3. Running an Feel++ application in Experiments

  • Select Create App Instance

    • define an ID (the ID is used later by the experiment tool to identify the experiment)

    • select a registered app in the menu

At this point you should have a page with all the options that need to be filled before moving to Deploy Instance

Portal FeelppCFDApp
Figure 1. Web interface of the Feel++ CFD app

The fields to fill may be grouped into categories:

  • specs for running simulations

  • HPC settings

  • specs retrieving singularity images

  • specs for singularity image

The EndUser shall only need to fill the fields related to the 1st and 2nd category. The fields that are to be filled by EndUser are marked in bold.

Table 1. List of keys specs for running simulations
Key Description Default Notes

feelpp_<toolbox slug name>_cli

command line options

""

feelpp_<toolbox>_case

string that describe the location of the testcase

``

Table 2. List of keys to be defined for HPC settings
Key Description Default Notes

job_tasks

number of tasks to be used in parallel

10

shall depends on batch system and selected partition

job_max_time

maximum allowed time for run (minutes and seconds)

'00:30:00'

depends on batch system and selected job_partition

job_partition

partition to be used on the supercomputer

thin-shared

depends on HPC system

Once filled, click on Create Instance. The default parametrization should work right away.

This results in the execution on the selected HPC resource of the bootstrap script included in the app definition.

Any error will result in a message at the top of the page, below the menus.

The next step is to Deploy Instance:

  • select the ID, you defined in the previous step, in the *App instance * menu

  • click on Deploy, wait until the button in blue turns green

To Run Instance, the procedure is similar:

  • select the ID, you defined in the previous step, in the App instance menu

  • click on RUN

These steps may take some minutes to be performed. A red button will indicates an error. Check the message in the frame below the status button. To have more details about the actual error is more tricky; we recommend to:

  • make sure you have unchecked the cleanup option

  • connect to the HPC resource

  • move to the selected base_dir/working_prefix<id>

  • check the logs

base_dir, working_prefix are filled within the portal Experiments. The <id> is a random character generated by the deployment.

An other option is to run the app using the orchestrator CLI. see this file for details

You may cleanup the execution of the job ID by

  • UnDeploy your Instance

    • select the ID, you defined in the previous step, in the *App instance * menu

    • click on UnDeploy

  • Destroy your Instance

    • select the ID, you defined in the previous step, in the *App instance * menu

    • click on Destroy

4. Setting up an Remote Desktop resource in Visualization

  • Go to {uri-msoportal-visu-www}[Visualization]

  • Select Settings

  • Define a Remote Desktop resource

Name: cesga
Host: vis.lan.cesga.es
User: [Your cesga user]
Password: [Your cesga password]
Remote Desktop Tools: [select item in the sliding menu]
List command: /opt/cesga/vis/bin/desktops
Create command: /opt/cesga/vis/bin/getdesktop

4.1. Running an Remote Desktop resource in Visualization

  • Go to Visualization

  • Click Desktop Available

    • Select your Infrastructure in the sliding menu

[NOTE]: if no Remote desktop is defined, you will receive a warning message. Create a Setting, then go back to this step.

  • Click on Create

  • Click either on Desktop or View Only

it should start a web page within your browser. In this page you should be able to:

  • start a 'terminal' and check the output of your simulation

  • start a post-processing GUI:

    • either by loading ParaView

    • or using singularity Ensight[EnSight] image

  • to quit just click on Menu/logout (top left)

For more details on using ParaView or EnSight please check XXXX.

The result are stored in $Lustre/feel/<workdir_prefix>_<date>_<id> if you have chosen to use the <hpc_volumes> bindmount option: $Lustre/feel:/feel.

Check the output of the script in <basedir>/<workdir_prefix>_<date>_<id> to see the exact name of this directory.