CREATE PHYSICALTEST FROM DATASET

Creates a new physical test record in d3VIEW from a tabular dataset, where each column in the supplied records becomes a response channel. Use this worker to programmatically register physical test results—along with metadata such as location, speed, temperature, and product details—without manual data entry.

When to use

Tagged: dataset, ingest, physical_test, physicaltest, response_creation, test_registration.

Inputs

Label	ID	Type	Default	Required	Description
Name	input_name	text	—	✓	Display name for the new physical test record; used as its primary label throughout the platform — required, free-text string.
Description	input_desc	textarea	—	✓	Human-readable description of the physical test, providing context such as test objectives or specimen details — required, free-text string.
Records	records		—	✓	Tabular dataset whose columns are converted into individual response channels on the physical test; each column header becomes the response name — required, typically passed from an upstream dataset transform or CSV worker.
Tags	tags	text	—		Comma-separated keyword tags to aid search and filtering of the physical test record within the platform — optional, free-text string.
Files	files	file	—		One or more supplementary files (e.g., raw data files, setup photos, calibration sheets) to attach to the physical test record — optional, repeatable file upload.
Test Location	test_location	text	—		Name or identifier of the facility or lab where the test was conducted (e.g., ‘Detroit Lab A’) — optional, free-text string.
Test Type	test_type	text	—		Classification of the test procedure (e.g., ‘frontal impact’, ‘tensile’, ‘fatigue’) — optional, free-text string.
Product Type	product_type	text	—		Category or class of the product under test (e.g., ‘seat belt’, ‘bumper assembly’) — optional, free-text string.
Product Name	product_name	text	—		Specific product name or model identifier for the specimen being tested — optional, free-text string.
Serial Number	serial_number	text	—		Serial or part number of the physical specimen used in the test, enabling traceability — optional, free-text string.
Test Temperature	test_temperature	text	—		Ambient or specimen temperature at time of test (include units, e.g., ‘23 °C’) — optional, free-text string.
Test Speed	test_speed	text	—		Test speed or loading rate (include units, e.g., ‘56 km/h’) — optional, free-text string.
Test Software	test_software	text	—		Name and version of the data acquisition or analysis software used during the test (e.g., ‘DynaView 4.2’) — optional, free-text string.
Test Hardware	test_hardware	text	—		Description of the test rig, DAQ hardware, or instrumentation setup used (e.g., ‘Kistler 9257B load cell’) — optional, free-text string.
Responsetemplate	responsetemplate_id	remote_lookup	—		Platform ID of a response template to apply to the newly created physical test, pre-populating expected response channels and KPIs — optional, resolved via remote lookup against available templates.
Project	project_id	remote_lookup	—		Platform ID of the project to which this physical test should be associated, enabling project-level grouping and access control — optional, resolved via remote lookup against available projects.

Outputs

Label	ID	Type	Description
Physicaltest Id	physicaltest_id	integer	Integer identifier of the newly created physical test record in d3VIEW; use this ID as a reference in downstream workers (e.g., response extraction, reporting, or correlation).

Disciplines

• cae.postprocessing.response
• data.dataset.ingest

---

Auto-generated from platform schema. Worker id: physical_create_from_dataset. Schema hash: 8e0f29f08ecb. Hand-curated docs in workerexamples/ override this page when present.