.. _auto_lsdyna_add_histories:

*PARSES LS-DYNA KEYWORD ADD *DATATABASE_HISTORY CARDS TO THE KEYWORD*
=====================================================================

Parses an LS-DYNA keyword file attached to a simulation and injects `*DATABASE_HISTORY` cards based on a supplied histories dataset, then replaces the original attachment with the modified keyword file. Use this worker whenever you need to programmatically add output-history tracking entities to an existing LS-DYNA deck before submission.

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

Tagged: ``database_history``, ``deck_edit``, ``history_cards``, ``keyword``, ``lsdyna``, ``preprocessing``.

Inputs
------

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

   * - Label
     - ID
     - Type
     - Default
     - Required
     - Description
   * - Simulation
     - simulation_id
     - remote_lookup
     - —
     - ✓
     - Platform simulation record to which the target keyword file belongs; select the parent simulation from the remote lookup.
   * - Attachment ID
     - attachment_id
     - remote_lookup
     - —
     - ✓
     - File attachment ID of the LS-DYNA keyword (.k / .key) file to be modified; the list is filtered to attachments of the selected simulation.
   * - Histories
     - histories
     - dataset
     - 1
     - ✓
     - Dataset of *DATABASE_HISTORY entries (entity type and IDs) to be appended to the keyword file; each row should specify the history card type and the corresponding entity ID(s).

Outputs
-------

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

   * - Label
     - ID
     - Type
     - Description
   * - Simulation Id
     - simulation_id
     - integer
     - Integer ID of the simulation whose keyword attachment was updated, passed downstream for chaining to solver-submission or further deck-authoring workers.

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

- cae.preprocessing.deck_authoring

.. raw:: html

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