Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
V
VIPSCore
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
VIPS
VIPSCore
Commits
17ed40cd
Commit
17ed40cd
authored
2 years ago
by
Tor-Einar Skog
Browse files
Options
Downloads
Patches
Plain Diff
Correct path variable name
parent
62b8aebb
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/create_client.md
+5
-5
5 additions, 5 deletions
docs/create_client.md
with
5 additions
and
5 deletions
docs/create_client.md
+
5
−
5
View file @
17ed40cd
...
@@ -5,20 +5,20 @@ Running a model is a matter of creating a client that is able to send a POST req
...
@@ -5,20 +5,20 @@ Running a model is a matter of creating a client that is able to send a POST req
The
**endpoint for running a model**
is:
The
**endpoint for running a model**
is:
```
```
{{vips
logic
_url}}/models/{{MODEL_ID}}/run
{{vips
core
_url}}/models/{{MODEL_ID}}/run
```
```
**Get the model ID**
by simply connecting to
**Get the model ID**
by simply connecting to
```
```
{{vips
logic
_url}}/models/
{{vips
core
_url}}/models/
```
```
So you must create a model configuration object and pass it in the request body. Each model has its own set of input data.
So you must create a model configuration object and pass it in the request body. Each model has its own set of input data.
To see a
**configuration example for a specific model**
, query
To see a
**configuration example for a specific model**
, query
```
```
{{vips
logic
_url}}/models/{{MODEL_ID}}/sampleconfig
{{vips
core
_url}}/models/{{MODEL_ID}}/sampleconfig
```
```
Here's a sample for the Carrot rust fly temperature model (PSILARTEMP)
Here's a sample for the Carrot rust fly temperature model (PSILARTEMP)
...
@@ -50,7 +50,7 @@ The `"loginInfo"` property is only relevant when running the model through the V
...
@@ -50,7 +50,7 @@ The `"loginInfo"` property is only relevant when running the model through the V
An explanation of the input parameters should be provided for each model from this endpoint:
An explanation of the input parameters should be provided for each model from this endpoint:
```
```
{{vips
logic
_url}}/models/{{MODEL_ID}}/usage
{{vips
core
_url}}/models/{{MODEL_ID}}/usage
```
```
If not, please contact the model provider and notify them.
If not, please contact the model provider and notify them.
...
@@ -112,7 +112,7 @@ Each model has its own output parameters, given in "allValues". They all provide
...
@@ -112,7 +112,7 @@ Each model has its own output parameters, given in "allValues". They all provide
The exact interpretation of the warningStatus is provided by the model, and can be read from this endpoint:
The exact interpretation of the warningStatus is provided by the model, and can be read from this endpoint:
```
```
{{vips
logic
_url}}/models/{{MODEL_ID}}/warningstatusinterpretation
{{vips
core
_url}}/models/{{MODEL_ID}}/warningstatusinterpretation
```
```
Example from the PSILARTEMP model:
Example from the PSILARTEMP model:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment