1. Log in to the Jarvice platform once your account is created: https://platform.jarvice.com/login-page
2. From the jarvice dashboard page, select the ‘Compute’ tab and select EXN/Aero from the list. A link will pop up below that says EXN/Aero Suite: Run the EXN/Aero suite directly in your browser. Click this link.
3. Select the resource allocation. You can choose one of four compute node hardware layouts:
- 4 CPU + 1 Nvidia K40
- 4CPU + 0.5 Nvidia K80
- 16 CPU + 2 Nvidia K40
- 16 CPU + 2 Nvidia K80
Roughly speaking, two K40 cards are about equal to 1 K80 card in terms of memory and parallel core.
GPU computations tend to be memory-limited; for an incompressible isothermal flow, you can expect to fit about 50 million control volumes on a K80 card.
4. After selecting resources, click ‘Continue’. Use default options under ‘Select Vault. This will give a succession of two pop-up screens that contain launching scripts. Click to continue through these.
The ‘Dashboard’ tab will show that an EXN/Aero job has started. This display updates automatically. The image takes 30 – 60 seconds to boot up. You will know it is ready when it a ‘connect’ button appears beneath the job information.
The connect button opens a browser-based remote connection to the EXN/Aero desktop.
You can also connect with TigerVNC client, which has less display latency. the ‘help’ button to the right of the ‘connect’ button provides information on how to run through TigerVNC.
5. Click the ‘Connect’ link and a new browser tab will connect you to the EXN/Aero desktop. There are two icons — one for the file manager, and one for EXN/View.
EXN/View and EXN/Vizer take 20-30 seconds to launch. Double click and wait patiently please!
Your account-bound persistent storage directory is /data. This is the only directory that persists when the server is shut down. You must store all simultion files and results files in ‘/data’ if you wish to keep them.
6. When the run is complete and data is downloaded or safely stored in ‘/data’, remember to shut down the server.
Closing the browser-based remote desktop does not kill the session. You must click ‘Shutdown’ on the dashboard and confirm shutdown to end a session otherwise compute hours will continue counting and Nimbix will bill your account for them.
Please re-read the above and make it part of standard procedures…we don’t want our users to be billed for hours they do not use.
7. To double check that the job was terminated, the job should appear in the ‘Recent Jobs’ tab on the dashboard. You will also receive a ‘job shutdown’ email from Nimbix.
If you encounter an error shutting down a job, please reach out to Nimbix directly. They are very responsive and can make sure you are not accidentally billed for a job that was left running because of the error