submits expr for evaluation using the remote batch submission environment env.
Details and Options
- RemoteBatchSubmit is used to submit batch jobs for asynchronous evaluation on batch computation providers.
- The currently supported batch computation providers are "AWSBatch", "AzureBatch" and "CharityEngine".
- RemoteBatchSubmit returns a RemoteBatchJobObject representing the resulting batch job on the batch computation provider.
- The environment env should be a RemoteBatchSubmissionEnvironment expression.
- If the batch computation provider being used has no required environment settings, then env may also be the name of the provider as a string, such as in RemoteBatchSubmit["CharityEngine",expr], which is equivalent to RemoteBatchSubmit[RemoteBatchSubmissionEnvironment["CharityEngine"],expr].
- The RemoteBatchJobObject returned by RemoteBatchSubmit will have "Single" as the value of its "JobType" property.
- The following options are supported by RemoteBatchSubmit:
ForwardCloudCredentials Automatic whether to copy the local session's Wolfram Cloud credentials into the remote session IncludeDefinitions True whether to automatically include dependencies of the expression LicensingSettings Automatic licensing settings to use RemoteInputFiles <||> association of local files to be uploaded to the provider RemoteProviderSettings <||> association of provider-specific settings for the job TimeConstraint Automatic a timeout for the job to be supplied to the provider
- The default value Automatic of the ForwardCloudCredentials option corresponds to True if the provider being used supports forwarding of cloud credentials, or False if the provider does not.
- The default value Automatic of the LicensingSettings option creates a new on-demand license entitlement with kernel count and expiration limits based on the job's configuration.
- When running jobs using the default on-demand licensing configuration, Wolfram Engine license usage is charged against your Wolfram Service Credits balance on a pay-as-you-go basis.
- Supported RemoteProviderSettings keys are listed on each remote submission provider's documentation page.
- The value of the TimeConstraint option can be an integer number of seconds or a "TimeUnit" quantity. The default value Automatic indicates to use the default timeout defined by the provider.
Examplesopen allclose all
Basic Examples (2)
Submit a job with settings for the "AWSBatch" provider specifying how many vCPUs (processor cores) to allocate to the job container:
The "AWSBatch" provider supplies an additional "JobStatusReason" job property indicating the reason for the job's failure:
Possible Issues (1)
Using the default on-demand licensing settings, RemoteBatchSubmit will refuse to submit a job if your Service Credits balance is insufficient to create a license entitlement based on the job processor count and TimeConstraint:
Reduce the number of processor cores and/or the TimeConstraint:
Wolfram Research (2020), RemoteBatchSubmit, Wolfram Language function, https://reference.wolfram.com/language/ref/RemoteBatchSubmit.html.
Wolfram Language. 2020. "RemoteBatchSubmit." Wolfram Language & System Documentation Center. Wolfram Research. https://reference.wolfram.com/language/ref/RemoteBatchSubmit.html.
Wolfram Language. (2020). RemoteBatchSubmit. Wolfram Language & System Documentation Center. Retrieved from https://reference.wolfram.com/language/ref/RemoteBatchSubmit.html