mantik.runs.remote¶
Functions¶
|
Module Contents¶
- mantik.runs.remote.submit_run(project_id: uuid.UUID, name: str, experiment_repository_id: uuid.UUID, code_repository_id: uuid.UUID, branch: str | None, commit: str | None, data_repository_id: uuid.UUID | None, data_branch: str | None, data_commit: str | None, mlflow_mlproject_file_path: str, entry_point: str, mlflow_parameters: dict, backend_config: pathlib.Path | str | dict, connection_id: uuid.UUID | None, compute_budget_account: str | None)[source]¶
- Parameters:
project_id (ID of the project to which the run should be linked)
name (Name of the Run)
experiment_repository_id (ID of the experiment repository) – to which the run should be linked
code_repository_id (ID of the code repository) – where the mlproject is located
branch (Name of the code repository's branch)
commit (Name of the code repository's commit (has precedence over branch))
data_repository_id (ID of the data repository) – where the data is located, this is optional
data_branch (Data branch to checkout. Defaults to newest.)
data_commit (Data commit to checkout. Takes precedence over data_branch.)
mlflow_mlproject_file_path (Path in your code directory) – to the MLproject file
entry_point (entry point name)
mlflow_parameters (Mlflow parameters present in your entry point)
backend_config (path to backend configuration file) – relative to path from where this command is called. It has to be a local file.
connection_id (Mantik Connection UUID)
compute_budget_account (Name of the compute budget account on HPC)
- Return type:
Response from the mantik API that contains the run id