CustomModelFineTuningJob Class    
Note
This is an experimental class, and may change at any time. Please see https://aka.ms/azuremlexperimental for more information.
Constructor
CustomModelFineTuningJob(**kwargs: Any)Methods
| dump | Dumps the job content into a file in YAML format. | 
dump
Dumps the job content into a file in YAML format.
dump(dest: str | PathLike | IO, **kwargs: Any) -> NoneParameters
| Name | Description | 
|---|---|
| dest 
				Required
			 | The local path or file stream to write the YAML content to. If dest is a file path, a new file will be created. If dest is an open file, the file will be written to directly. | 
Exceptions
| Type | Description | 
|---|---|
| Raised if dest is a file path and the file already exists. | |
| Raised if dest is an open file and the file is not writable. | 
Attributes
base_path
creation_context
The creation context of the resource.
Returns
| Type | Description | 
|---|---|
| The creation metadata for the resource. | 
hyperparameters
id
inputs
log_files
model
The model to be fine-tuned. :return: Input object representing the mlflow model to be fine-tuned. :rtype: Input
model_provider
The model provider. :return: The model provider. :rtype: str
outputs
queue_settings
Queue settings for job execution. :return: QueueSettings object. :rtype: QueueSettings
resources
Job resources to use during job execution. :return: Job Resources object. :rtype: JobResources
status
The status of the job.
Common values returned include "Running", "Completed", and "Failed". All possible values are:
- NotStarted - This is a temporary state that client-side Run objects are in before cloud submission. 
- Starting - The Run has started being processed in the cloud. The caller has a run ID at this point. 
- Provisioning - On-demand compute is being created for a given job submission. 
- Preparing - The run environment is being prepared and is in one of two stages: - Docker image build 
- conda environment setup 
 
- Queued - The job is queued on the compute target. For example, in BatchAI, the job is in a queued state - while waiting for all the requested nodes to be ready. 
- Running - The job has started to run on the compute target. 
- Finalizing - User code execution has completed, and the run is in post-processing stages. 
- CancelRequested - Cancellation has been requested for the job. 
- Completed - The run has completed successfully. This includes both the user code execution and run - post-processing stages. 
- Failed - The run failed. Usually the Error property on a run will provide details as to why. 
- Canceled - Follows a cancellation request and indicates that the run is now successfully cancelled. 
- NotResponding - For runs that have Heartbeats enabled, no heartbeat has been recently sent. 
Returns
| Type | Description | 
|---|---|
| Status of the job. | 
studio_url
task
Get finetuning task.
Returns
| Type | Description | 
|---|---|
| The type of task to run. Possible values include: "ChatCompletion" "TextCompletion", "TextClassification", "QuestionAnswering","TextSummarization", "TokenClassification", "TextTranslation", "ImageClassification", "ImageInstanceSegmentation", "ImageObjectDetection","VideoMultiObjectTracking". |