.. _auto_job_submit_simulation_by_config:

*SUBMIT SIMULATION BY SAVED CONFIGURATION*
==========================================

Submits one or more simulations to an HPC cluster using a previously saved HPC configuration, optionally associating a response template and study. Supports a non-blocking mode that returns job and simulation IDs immediately after submission without waiting for HPC completion.

When to use
-----------

Tagged: ``hpc``, ``job_submission``, ``non_blocking``, ``saved_config``, ``simulation``, ``submit``.

Inputs
------

.. list-table::
   :header-rows: 1
   :widths: 20 20 20 20 20 20

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Simulation
     - job_submit_simulation_id
     - remote_lookup
     - —
     - ✓
     - One or more simulations to submit, selected by name or ID from the platform simulation registry; at least one selection is required.
   * - Description
     - job_submit_simulation_description
     - textarea
     - —
     - 
     - Optional free-text description or notes to attach to the submitted simulation run; leave blank to inherit the existing simulation description.
   * - Setting Name
     - job_submit_hpcsettings_name
     - remote_lookup
     - —
     - ✓
     - Name of the saved HPC settings profile (queue, cores, memory, solver flags) to use for this submission; must exist in the platform HPC settings registry.
   * - Response Template
     - job_submit_template
     - remote_lookup
     - —
     - 
     - Optional response template to associate with the job for automated KPI extraction after completion; leave blank if no post-processing template is needed.
   * - Study ID
     - study_id
     - remote_lookup
     - —
     - 
     - Optional study to link this simulation run to, enabling grouping of related jobs under a common design exploration or certification study.
   * - Return After Submit
     - return_after_submit
     - boolean
     - False
     - 
     - When true, the worker returns immediately after job submission without waiting for HPC completion, making simulation and job IDs available at once; default is false (blocking mode).

Outputs
-------

.. list-table::
   :header-rows: 1
   :widths: 20 20 20 20

   * - Label
     - ID
     - Type
     - Description
   * - Job Submit By Config Output 1
     - job_submit_by_config_output_1
     - integer
     - Integer platform simulation ID assigned to the newly submitted simulation run, usable as a reference in downstream workers.
   * - Job Submit By Config Output 2
     - job_submit_by_config_output_2
     - integer
     - Integer HPC job ID returned by the cluster scheduler, usable for monitoring job status or retrieving results in downstream workers.

Disciplines
-----------

- platform.hpc_config
- platform.job_submission

.. raw:: html

   <hr style="margin-top:2em">
   <p style="font-size:11px;color:#888">
   Auto-generated from <code>platform</code> schema. Worker id: <code>job_submit_simulation_by_config</code>. Schema hash: <code>49f0003790fd</code>. Hand-curated docs in <code>workerexamples/</code> override this page when present.
   </p>