ModelOp Center provides a CLI-based “test utility”to utility” to allow users to test their model within a ModelOp Runtime without officially registering the model with ModelOp Center. This is particularly useful if there is complex code in your model, custom integrations or data pipelines, or custom dependencies that need to be tested for compatibility.
...
Please follow the steps mentioned here to download and setup set up the ModelOp CLI : Install CLI
Overview of commands
The help for the moc commands is presented in Linux man page format.
...
User moc iterative command to test model source code and assets on ModelOp Runtime. moc iterative has sub-commands to run different types of jobs and deploy the model as REST. Before using any commands, the CLI needs to know which engine to use for the commands. To set the target engine for the command please see the engine use command. Description for the sub-commands is as shown below.
...
| Code Block |
|---|
moc iterative engine [--help]
moc iterative engine <command> [--help]
moc iterative engine reset [--help]
moc iterative engine score [--help]
moc iterative engine status [--help]
moc iterative engine use <engine URL|name> [flags] |
...
| Code Block |
|---|
moc iterative engine reset |
score
Description
Use this command to send records for scoring to the target runtime set using the moc iterative engine use command.
Options
--input
Specify a file to use as the source of the input records. When not set, input records are read from stdin.
Arguments
The command does not take any arguments
Examples
| Code Block |
|---|
moc iterative engine score --input input.json
moc iterative engine score < input.json
echo '"my-input-string"' | moc iterative engine score |
status
Description
Use this command to know the status of the target runtime set using the moc iterative engine use command.
...