REMOTE JOB SUBMISSION¶
Submits a job to a remote d3VIEW server using the specified HPC configuration, polls for completion status at a configurable interval, and syncs the finished simulation files back to the local server. Use this worker when compute or data must reside on a separate d3VIEW instance from the orchestrating workflow.
When to use¶
Tagged: cross_server, d3view, file_sync, hpc, job_submission, polling, remote_job_submission.
Inputs¶
| Label | ID | Type | Default | Required | Description |
|---|---|---|---|---|---|
| Simulation Name | remote_job_input_sim_name | text | — | Optional human-readable label assigned to the simulation on the remote server; leave blank to use the remote server’s auto-generated name. | |
| HPC Setting Name | remote_job_input_hpc_config | remote_lookup | — | ✓ | Required remote-lookup reference to the named HPC settings profile that defines queue, solver version, and resource limits on the remote server. |
| Main Input File | remote_job_input_main_file | file | — | ✓ | One or more primary solver input files (e.g. LS-DYNA .k / .key decks) to be uploaded and executed on the remote server; at least one file is required. |
| Include Files | remote_job_input_include_files | file | — | Optional repeatable list of supplementary include or data files (e.g. material cards, geometry includes) that the main input file references. | |
| Parameters | remote_job_input_parameters | dataset | — | Optional repeatable dataset(s) of named parameter key-value pairs used for parametric substitution into the solver deck on the remote server. | |
| Template ID | remote_job_input_template_id | remote_lookup | — | Optional remote-lookup reference to a response/post-processing template on the remote server to associate with the submitted simulation. | |
| Study ID | remote_job_input_study_id | remote_lookup | — | Optional remote-lookup reference to an existing study on the remote server under which the new simulation should be grouped. | |
| Remote Server URL | remote_job_input_remote_url | text | — | ✓ | Full base URL of the target d3VIEW server including protocol and port (e.g. https://portal.d3view.com:3093); required for all remote API calls. |
| Remote Username | remote_job_input_remote_user | text | — | ✓ | Email address or username of the account on the remote d3VIEW server used to authenticate the job submission. |
| Remote API Key | remote_job_input_remote_api_key | text | — | ✓ | API key (secret token) for the remote server account; treat as a credential — store in a secrets manager and inject at runtime rather than hard-coding. |
| Polling Interval (seconds) | remote_job_input_polling_interval | integer | 30 | ✓ | How often (in seconds, 15–120) the worker checks the remote server for job completion; default is 30 s — increase for long-running jobs to reduce API traffic. |
Outputs¶
| Label | ID | Type | Description |
|---|---|---|---|
| Local Simulation | remote_job_output_local_sim_id | integer | Integer ID of the mirrored Simulation record created on the local d3VIEW server after files are synced back; use this to chain downstream post-processing workers. |
| Local HpcJob | remote_job_output_local_hpcjob_id | integer | Integer ID of the local HpcJob record that tracks the mirrored job state on the local server. |
| Remote Simulation ID | remote_job_output_remote_sim_id | integer | Integer ID of the Simulation record as created on the remote d3VIEW server; useful for direct API queries or audit logging. |
| Remote HpcJob ID | remote_job_output_remote_hpcjob_id | integer | Integer ID of the HpcJob record on the remote server; can be used to correlate remote queue logs or re-poll status independently. |
| Remote URL | remote_job_output_remote_url | text | Pass-through of the remote server URL used during submission; hidden by default and forwarded to downstream workers that need to call the same remote instance. |
| Remote Username | remote_job_output_remote_user | text | Pass-through of the remote username used during submission; hidden by default and forwarded to downstream workers requiring the same remote credentials. |
| Remote API Key | remote_job_output_remote_api_key | text | Pass-through of the remote API key used during submission; hidden by default — handle with care and avoid logging or exposing in reports. |
Disciplines¶
- platform.hpc_config
- platform.integration
- platform.job_submission
Auto-generated from platform schema. Worker id: remote_job_submission. Schema hash: feb8c7b9bff7. Hand-curated docs in workerexamples/ override this page when present.