.. _auto_simulation_create_from_parent_simulation:

*CREATES A NEW SIMULATION BASED ON FILES FROM PARENT SIMULATION*
================================================================

Creates a new simulation by cloning selected files from an existing parent simulation, assigning a fresh name, HPC configuration, and optional post-processing template. Use this worker when you need to branch a simulation run from a known baseline without manually re-uploading input decks.

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

Tagged: ``clone``, ``deck_authoring``, ``file_copy``, ``hpc``, ``parent_simulation``, ``scenario_branching``, ``simulation``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Simulation
     - simulation_id
     - remote_lookup
     - —
     - ✓
     - ID of the parent simulation whose files will be used as the source; select from the simulations remote lookup — required.
   * - Simulation Name
     - name
     - text
     - —
     - ✓
     - Human-readable name assigned to the newly created simulation; must be unique within the project — required.
   * - Description
     - description
     - textarea
     - —
     - 
     - Optional free-text description summarising the purpose or variant of the new simulation.
   * - File Names to Copy
     - filenames_to_copy
     - text
     - —
     - 
     - Comma-separated list of file names to copy from the parent simulation (e.g. 'input.k,material.inc'); leave blank to copy all files.
   * - Main Input Filename
     - main_input_name
     - text
     - —
     - 
     - File name of the primary solver input deck within the copied set (e.g. 'main.k'); used to designate the entry-point for the HPC job.
   * - HPC Configuration
     - hpcconfig
     - remote_lookup
     - —
     - ✓
     - HPC configuration record that defines cluster, queue, and resource settings for the new simulation's job submission — required.
   * - Post-processing Template
     - template_id
     - remote_lookup
     - —
     - 
     - Optional post-processing response template ID applied to the new simulation for automated KPI extraction after the run completes.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - New Simulation
     - simulation_id
     - integer
     - Integer primary key of the newly created simulation record; use as input to downstream solver or post-processing workers.
   * - HPCJob
     - hpcjob_id
     - integer
     - Integer primary key of the HPC job created alongside the new simulation; use to monitor or poll job status in subsequent workflow steps.

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

- cae.preprocessing.deck_authoring
- cae.preprocessing.scenario
- platform.hpc_config
- platform.job_submission
- platform.workflow

.. raw:: html

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