Vecma

access_supermuc

vytautas.jancauskas@lrz.de (vytautas.jancauskas@lrz.de@undisclosed.example.com) — 2020-02-12T09:23:41+0000

Access to SuperMUC-NG To get access to larger amounts of CPU hours on SuperMUC-NG a proposal needs to be submitted via the Gauss Centre for Supercomputing website. There are three types of projects - test, regular and large scale. Regular projects can have up to 45 million CPU hours allocated and large scale project proposals are for projects that require more than that. If the user just needs to have access to the VECMAtk infrastructure they can be added to the existing project that was create…

vecma-testbed - [The Leibniz Rechenzentrum (LRZ)]

vytautas.jancauskas@lrz.de (vytautas.jancauskas@lrz.de@undisclosed.example.com) — 2020-02-12T09:12:20+0000

VECMA Infrastructure IMPORTANT: To get access to the VECMA Infrastructure, users need to follow instructions provided on VECMA Wiki: How to get access to the infrastructure Poznan Supercomputing and Networking Center (PSNC) PSNC (www.man.poznan.pl) is providing its biggest HPC system, “Eagle”, comprising 33,000 cores, with 300TB of memory, and operating at 1.4 petaFLOPS, to a total of at least 5 million CPU hours over the 36-month duration of VECMA. A

glossary - [Sensitivity Analysis] typo correction

dave.wright@ucl.ac.uk (dave.wright@ucl.ac.uk@undisclosed.example.com) — 2019-04-03T10:26:46+0000

Overview VVUQ is Validation, Verification and Uncertainty Quantification. Validation is the process of analyzing the accuracy with which the model represents the real world process (Oberkampf, 2010). Verification is the process of identifying whether the computational model accurately simulates the underlying (usually mathematical) model and its solution (Oberkampf, 2010). Verification can be divided into code verification (finding and fixing errors in the numerical algorithms or in the sour…

proposal_patterns - created

dave.wright@ucl.ac.uk (dave.wright@ucl.ac.uk@undisclosed.example.com) — 2019-03-07T16:05:21+0000

Patterns Patterns within VECMA are abstractions that describe, in a non-application specific manner, a workflow or algorithm for conducting validation, verification, uncertainty quantification or sensitivity analysis. Two classes of pattern are developed within the project: Uncertainty Quantification Patterns (UQPs), focussed on uncertainty quantification and propagation or sensitivity analysis, and Validation & Verification Patterns (VVPs), concerned with validation and verification. The rema…

046.png - created

dave.wright@ucl.ac.uk (dave.wright@ucl.ac.uk@undisclosed.example.com) — 2019-03-07T16:03:35+0000

044.png - created

dave.wright@ucl.ac.uk (dave.wright@ucl.ac.uk@undisclosed.example.com) — 2019-03-07T15:51:02+0000

vecma-wp4

olivier.hoenen@ipp.mpg.de (olivier.hoenen@ipp.mpg.de@undisclosed.example.com) — 2019-02-13T12:14:25+0000

WP4 - Applications Needs and requirements Application Description Questionnaire You can find the online questionnaire here and the answers with some analytics here. Acceptance Use Cases (AUCs) Below is a possible template for an AUC: ## One-line summary of the AUC Give a one-line summary. ## Applicable Software Role Required Choose one or more of: * Local site management (scheduling / running jobs on a local site) * Simulated execution software (exascale simulator) * Cross-site schedulin…

qcg-pilotjobs

bbosak@man.poznan.pl (bbosak@man.poznan.pl@undisclosed.example.com) — 2019-01-31T11:47:12+0000

QCG PilotJob User Guide This webpage provides basic instruction how to use the QCG PilotJob tool in the VECMA environment. For the complete reference documentation of the tool please go to this link What is QCG PilotJob? QCG PilotJob is a computing job playing a role of a container over a number of subordinate computing jobs. It allows to execute many subordinate jobs in a single scheduling system allocation. Direct submission of a number separate jobs to a scheduling system can result in…

32-cert_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T09:26:45+0000

30-cert_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T09:19:05+0000

29-cert_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T08:24:48+0000

28-grant_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T07:53:15+0000

27-grant_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T07:50:37+0000

26-zespol_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T07:36:38+0000

25-grant_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T07:26:36+0000

24-granty_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T07:23:37+0000

23-grant_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-16T07:17:11+0000

20-cert_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-15T21:52:09+0000

19-cert_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-15T21:42:30+0000

18-uslugi_v2.png - created

piontek@man.poznan.pl (piontek@man.poznan.pl@undisclosed.example.com) — 2018-11-15T21:25:49+0000