D3HSP EXTRACTOR FROM SIMULATION¶
Parses a named section from the LS-DYNA d3hsp output file attached to a simulation and returns the extracted data as structured responses. Use this worker to pull summary statistics, mass properties, GISSMO failures, contact info, material curves, or any other d3hsp section into the workflow for downstream processing.
When to use¶
Tagged: binout, contact, d3hsp, d3hsp2xml, extraction, gissmo, ls-dyna, mass.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Simulation | simulation_id | remote_lookup | — | Remote lookup reference to the LS-DYNA simulation whose d3hsp file will be parsed; accepts one or more simulation IDs — leave blank only if the simulation is supplied by an upstream worker. | |
| Response Name | response_name | text | — | ✓ | Label assigned to the extracted response object; used as the response name when saving results to the platform (required, free-text string). |
| Select Section | d3hsp_section | select | summary | ✓ | Section of the d3hsp file to extract; choose from options such as summary, mass, parameters, gissmo_failures, contact, materials, curves, etc. — defaults to ‘summary’. |
| Options | d3hsp_options | textarea | — | Optional JSON or key-value string passed directly to the d3hsp2xml extractor to control section-specific parsing behavior (e.g., part ID for curve_by_id); leave empty if no extra options are needed. | |
| Auto Save | auto_save | select | — | When set to ‘yes’, extracted responses are persisted to the platform database and re-fetched as saved response records; defaults to ‘no’, which returns in-memory extracted data without saving. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Extractions | extractions | dataset | |
| Logs | logs | dataset | Dataset containing the extraction process logs from the Simlyzer engine, including any warnings or errors encountered during d3hsp parsing. |
| Responses | responses | dataset | Dataset of extracted response objects (vectors or curve groups) corresponding to the requested d3hsp section; when auto_save is ‘yes’, contains saved response records with platform metadata. |
Disciplines¶
- cae.postprocessing.extraction
Auto-generated from platform schema. Worker id: d3hsp_extractor. Schema hash: 79c3847e8400. Hand-curated docs in workerexamples/ override this page when present.