.. _auto_simulation_import_from_server:

*IMPORT SIMULATION FROM SERVER*
===============================

Creates a new simulation record on the d3VIEW platform by importing one or more files directly from a server path (no upload required). Use this worker when simulation result files already reside on a mounted server volume and need to be registered as a platform simulation without transferring data.

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

Tagged: ``file_import``, ``import``, ``lsdyna``, ``nastran``, ``platform_integration``, ``remote_file``, ``server``, ``simulation``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Simulation Name
     - sim_name
     - text
     - —
     - ✓
     - Human-readable name assigned to the new simulation record; must be unique within the target project and is required.
   * - Simulation Description
     - sim_desc
     - textarea
     - —
     - 
     - Optional free-text description providing context about the simulation (e.g., load case, model version, analyst notes); leave blank if not needed.
   * - Simulation Tags
     - input_sim_tags
     - text
     - —
     - 
     - Optional comma-separated tags to classify the simulation for search and filtering within the platform (e.g., 'frontal,barrier,v2.3').
   * - Files
     - files
     - remote_file
     - —
     - ✓
     - One or more server-side file paths (browsed via /storage2 file explorer) to import; select all relevant result files (e.g., d3plot, binout, .out) for the simulation.
   * - Make A Copy
     - copy_over
     - string
     - no
     - 
     - Controls whether the server files are copied into platform-managed storage ('yes') or referenced in-place ('no', default); choose 'yes' if the source files may be moved or deleted.
   * - Solver Type
     - solver_type
     - string
     - LS-DYNA
     - 
     - Solver type associated with the imported files; defaults to 'LS-DYNA' — set to 'Nastran' when importing Nastran result sets so the platform applies the correct post-processing parsers.
   * - Project ID
     - input_project_id
     - remote_lookup
     - —
     - 
     - Platform Project ID under which the new simulation will be registered; looked up from the user's project list — leave null to assign to the default project.

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Simulation Id
     - simulation_id
     - integer
     - Integer ID of the newly created simulation record on the platform; use this in downstream workers (e.g., post-processing, reporting) to reference the imported simulation.

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

- cae.postprocessing.extraction
- data.io.file
- platform.integration

.. 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_import_from_server</code>. Schema hash: <code>78b32398f800</code>. Hand-curated docs in <code>workerexamples/</code> override this page when present.
   </p>