SUBMITS MULTIPLE SIMULATIONS FROM SERVER FILES¶
Submits multiple simulations to an HPC cluster using input decks already present on the server, creating one simulation record per file. Use this worker when you need to batch-launch solver jobs from pre-staged server-side files within a defined project and study context.
When to use¶
Tagged: batch_submit, files, hpc, job_submission, server_files, simulation.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Server Files | server_files | remote_file | — | ✓ | One or more server-side input deck files (e.g., LS-DYNA .key/.k files) already staged on the HPC server; each file will generate a separate simulation job. |
| Optional Simulation Prefix | simulation_prefix | text | — | ✓ | Optional text prefix prepended to each auto-generated simulation name to aid identification; leave blank if no custom naming convention is needed. |
| Setting Name | hpcconfig | remote_lookup | — | ✓ | HPC settings record (cluster config, queue, resource limits) selected from the platform registry; determines where and how each job is submitted. |
| Response Template | template_id | remote_lookup | — | Optional response template to associate with each submitted simulation for automated KPI extraction after the run completes; leave unset to skip template binding. | |
| Study | study_id | text | — | ✓ | Identifier of the study under which all submitted simulations will be grouped; must match an existing study in the platform. |
| Project | project_id | text | — | ✓ | Identifier of the project to which the study and simulations belong; must match an existing project in the platform. |
| Tags | tags | text | — | ✓ | Comma-separated metadata tags attached to every submitted simulation to support search and filtering in the platform (e.g., ‘baseline,v1,frontal’). |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Simulations | simulations | dataset | Dataset containing one row per submitted simulation, including simulation IDs, names, status, and associated metadata returned by the platform after job submission. |
Disciplines¶
- platform.hpc_config
- platform.job_submission
Auto-generated from platform schema. Worker id: job_submit_simulations_from_server_files. Schema hash: 09b7eada80ea. Hand-curated docs in workerexamples/ override this page when present.