CREATE A LOADCASE¶
Creates a new Loadcase entity in the d3VIEW assembler, binding it to a template, optional workflow, loading type, and target response. Use this worker whenever a simulation scenario must be formally registered as a named loadcase before downstream solve or post-processing steps.
When to use¶
Tagged: assembler, loadcase, loadcase_create, scenario.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Name | name | text | — | ✓ | Unique human-readable name for the loadcase; used as the primary display label throughout the platform (required). |
| Product Type | product_type | text | Barrier | ✓ | Type of physical entity that applies the load (e.g. ‘Barrier’, ‘Impactor’); defaults to ‘Barrier’. |
| Template | template_id | remote_lookup | — | ✓ | Platform template to associate with the loadcase; selected via remote lookup — defines the response and KPI structure. |
| Workflow | workflow_id | remote_lookup | — | Optional workflow to attach to this loadcase; leave blank if no automated execution pipeline is needed. | |
| Description | description | text | — | Free-text human-readable description of the loadcase purpose; optional. | |
| Code | code | text | — | Short alphanumeric code or identifier for the loadcase, used for reporting or traceability; optional. | |
| Type of Loading | load_type | select | displacement | ✓ | Physical nature of the applied load — one of: displacement, velocity, acceleration, temperature, inflation (gas), or explosion; defaults to ‘displacement’. |
| Loading Value | load_value | text | 1.0 | Scalar magnitude of the applied load in the units implied by load_type; defaults to 1.0. | |
| Target Name | target_name | text | Target | Name of the response quantity used as the optimization or pass/fail target (usually matches a response defined in the template); defaults to ‘Target’. | |
| Target Value | target_value | text | 1.0 | Numerical target value for the named response; defaults to 1.0. | |
| Regulation Code | regulation_code | text | — | Applicable regulatory or standards code (e.g. FMVSS, ECE); leave blank if no regulation governs this loadcase. | |
| Country | country | text | US | ✓ | Country jurisdiction for the regulation or test protocol (ISO 2-letter code); defaults to ‘US’. |
| Simulation Files | files | file | — | Optional simulation input files (e.g. LS-DYNA decks, include files) to attach to the loadcase; accepts multiple files. | |
| Options | options | keyvalue | — | Arbitrary key-value pairs for any additional metadata or solver options that do not map to a dedicated field; stored as a name/value table. | |
| Extra Data | extra_data | textarea | — | Supplementary structured data payload for extending loadcase metadata beyond the standard fields; optional. | |
| Project | project_id | remote_lookup | — | Select a Project |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Loadcase Id | loadcase_id | scalar | Platform-assigned unique identifier of the newly created loadcase; passed downstream to scenario setup, solver submission, or post-processing workers. |
Disciplines¶
- cae.preprocessing.scenario
Auto-generated from platform schema. Worker id: assembler_create_loadcase. Schema hash: a9e1db0adf32. Hand-curated docs in workerexamples/ override this page when present.