.. _auto_simulations_create_from_files:

*CREATES SIMULATIONS ONE FOR EACH FILE*
=======================================

Creates one simulation record per uploaded main input file by iterating over a list of main input files and invoking the underlying single-simulation creation worker for each. Use this worker when you need to register multiple solver runs (e.g. LS-DYNA decks) in bulk from a set of input files in a single workflow step.

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

Tagged: ``batch``, ``bulk``, ``create``, ``input_file``, ``lsdyna``, ``simulation``, ``solver``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Main Input File
     - input_main_file
     - file
     - —
     - ✓
     - One or more main solver input files (e.g. LS-DYNA .k / .key decks); one simulation is created for each file supplied — multi-select is required.
   * - Include Files
     - input_include_files
     - file
     - —
     - 
     - Optional secondary include/referenced files (e.g. *INCLUDE keyword files) that are shared across all simulations being created; leave empty if all data is self-contained in the main files.
   * - Solver Type
     - solver_type
     - string
     - lsdyna
     - 
     - Solver code identifier string (e.g. 'lsdyna'); defaults to 'lsdyna' and should only be changed when targeting a different supported solver.
   * - Project ID
     - input_project_id
     - remote_lookup
     - —
     - 
     - d3VIEW project under which all created simulations will be registered; select from the remote lookup list of available user projects.
   * - Simulation Tags
     - input_sim_tags
     - text
     - —
     - 
     - Comma-separated free-text tags to attach to every simulation created in this batch, useful for filtering and searching later.
   * - Responses
     - responses
     - vector
     - —
     - 
     - Repeating vector of response definitions (curve/KPI extractions) to associate with each simulation; leave empty if post-processing responses will be configured separately.
   * - UnCompress Files
     - unzip_files
     - select
     - no
     - 
     - Whether to decompress uploaded archive files before creating simulations ('yes') or treat them as-is ('no'); defaults to 'no'.
   * - Test ID
     - physicaltest_id
     - remote_lookup
     - —
     - 
     - Optional physical test record to link to all created simulations for sim-vs-test correlation; leave null if no physical test association is required.
   * - System Model ID
     - systemmodel_id
     - remote_lookup
     - —
     - 
     - Optional system model to associate with all created simulations; leave null if not applicable.
   * - Loadcase ID
     - loadcase_id
     - remote_lookup
     - —
     - 
     - Optional loadcase to associate with all created simulations; leave null if loadcase context is not required.
   * - HPC Setting Name
     - hpcjob_setting
     - remote_lookup
     - —
     - ✓
     - Required HPC settings profile name that defines the cluster, queue, and resource configuration used to submit each simulation job.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Simulations
     - simulations
     - integer
     - Dataset collection of all simulation records created in this batch, with each row representing a fully registered simulation object.
   * - Sim Ids
     - sim_ids
     - scalar
     - Array of integer simulation IDs corresponding to every simulation created, in the same order as the input files.
   * - First Sim Id
     - first_sim_id
     - scalar
     - Integer ID of the simulation created from the first main input file; convenient for single-file or pipeline-chaining use cases.
   * - Last Sim Id
     - last_sim_id
     - scalar
     - Integer ID of the simulation created from the last main input file; useful for downstream workers that only need to reference the final simulation in the batch.

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

- cae.preprocessing.scenario
- cae.solver
- 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>simulations_create_from_files</code>. Schema hash: <code>1b030d8f4aeb</code>. Hand-curated docs in <code>workerexamples/</code> override this page when present.
   </p>