.. _auto_simulation_create_from_text: *CREATE SIMULATION FROM TEXT* ============================= Creates a new d3VIEW simulation record from raw text-based input deck content, registering it under a chosen project and/or study. Use this worker when an upstream step synthesizes or modifies keyword content programmatically and the result must be persisted as a named simulation before solving. When to use ----------- Tagged: ``create``, ``deck``, ``keyword``, ``lsdyna``, ``platform``, ``simulation``, ``text``. Inputs ------ .. list-table:: :header-rows: 1 :widths: 20 20 20 20 20 20 * - Label - ID - Type - Default - Required - Description * - Simulation Name - input_sim_name - text - Simulation <%DATE%> - ✓ - Human-readable name for the new simulation record; defaults to 'Simulation ' if left unchanged — override to something descriptive when creating multiple simulations in a loop. * - Simulation Description - input_sim_desc - textarea - — - - Optional free-text description stored with the simulation record to provide context about its purpose or configuration. * - Simulation Tags - input_sim_tags - text - — - - Optional comma-separated tags to attach to the simulation record for filtering and search within d3VIEW. * - Main Input File - input_main_file_name - textarea - Simulation.k - ✓ - File name (including extension) assigned to the main input deck, e.g. 'Simulation.k' for LS-DYNA keyword files; must match any *INCLUDE references in the deck text. * - Solver Type - solver_type - scalar - lsdyna - ✓ - Solver identifier string (e.g. 'lsdyna') that determines how the platform parses and submits the input deck; defaults to 'lsdyna' — change only if targeting a different supported solver. * - Input Data - input_main_file_text - textarea - *KEYWORD *END - ✓ - Full text content of the main input deck (LS-DYNA keyword format by default); must begin with *KEYWORD and end with *END at minimum — upstream workers typically populate this via template substitution. * - Project ID - input_project_id - remote_lookup - — - - Optional d3VIEW project ID under which the simulation is organized; looked up via /api/user/projects — leave null to create the simulation outside any project. * - Include Files - include_files - file - — - - Optional list of auxiliary files (e.g. material includes, geometry files) referenced by the main input deck via *INCLUDE; repeat the field for each additional file. * - Responses - responses - vector - — - - Optional repeating vector-type response definitions that specify time-history output channels to track for this simulation (see d3VIEW Glossary: curveinput). * - Response List - responses_by_dataset - dataset - — - - Optional repeating dataset-type response list providing response name, type, and default value in tabular form as an alternative to the vector-based responses input (see d3VIEW Glossary: datasetinput). * - Study ID - study_id - remote_lookup - — - - Optional d3VIEW study ID used to associate this simulation with an existing parametric or design study; looked up via /api/user/studies — leave null if no study grouping is needed. 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 d3VIEW simulation record, used by downstream workers (e.g. solver submission, response extraction) to reference this simulation. Disciplines ----------- - cae.preprocessing.deck_authoring - platform.job_submission - platform.workflow .. raw:: html

Auto-generated from platform schema. Worker id: simulation_create_from_text. Schema hash: 7ea6936e0e06. Hand-curated docs in workerexamples/ override this page when present.