CONVERTS LS-DYNA MATERIAL TO DATABASE JSON¶
Parses an LS-DYNA input file, extracts all material card definitions (including optional MAT_ADD_EROSION data), and ingests them into a d3VIEW material database as structured JSON records. Use this worker to bulk-populate or refresh a material library database from an existing LS-DYNA deck.
When to use¶
Tagged: database, ingest, json, keyword, lsdyna, mat_add_erosion, material, material_library.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Database Name | database_name | text | — | ✓ | Name to assign to the newly created material database entry in d3VIEW; must be unique within the platform. |
| LS-DYNA Input File | lsdyna_file | file | — | ✓ | LS-DYNA keyword input file (.k, .key, or .inc) containing the material cards to be parsed and imported. |
| Include MAT ADD EROSION Information | include_mat_add_erosion | select | no | Controls whether MAT_ADD_EROSION keyword data is extracted alongside the base material cards; defaults to ‘no’ — set to ‘yes’ when failure/erosion parameters are needed in the database. | |
| Parent Database | parent_database_id | remote_lookup | — | Optional existing database whose user permissions and column layout will be inherited by the newly created database; leave blank to create an independent database. | |
| Meta-data | meta_file | dataset | — | Optional dataset containing a ‘Material ID’ column used to enrich or filter imported records with additional metadata; leave blank if no supplemental metadata is available. | |
| Order Columns | order_columns | select | no | When set to ‘yes’, reorders the database columns to match the column sequence defined in the supplied meta_file; defaults to ‘no’. | |
| Map Columns | map_columns | mapper | — | Column-mapping definition that aligns extracted LS-DYNA material fields to columns in the meta_file dataset; leave unconfigured if no meta_file is provided. | |
| Return Records | return_records | select | no | When set to ‘yes’, returns parsed material records as a dataset output without persisting a new database entry; useful for preview or downstream processing without committing to the database. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Database Id | database_id | integer | Integer ID of the newly created (or updated) d3VIEW material database; null when ‘return_records’ is set to ‘yes’ and no database is created. |
| Records | records | dataset | Dataset containing one row per imported material, with columns corresponding to the parsed LS-DYNA material parameters and any mapped metadata fields; populated only when ‘return_records’ is set to ‘yes’. |
Disciplines¶
- cae.preprocessing.deck_authoring
- data.dataset.ingest
- engineering.material.library
Auto-generated from platform schema. Worker id: lsdyna_material_to_database. Schema hash: b6aca3eef389. Hand-curated docs in workerexamples/ override this page when present.