model_id
allows you to specify the model you wish to use. Check your model library on the Deepomatic platform to find the id of the model you want to use.concepts
is a name given to the output of the step and that you need when you want to use this output in other steps. There can be only one concept in the arguments of an Inference step.model_id
and concepts
are exactly the same as the Inference step.routing_name
corresponds to the concept
name of the inference step preceding the current step. routing_values
must be coherent with the concept names that your model has been trained on. A PredictionRouter step is then only compatible with a specific set of models.top_prediction
is optional and lets you filter even more the regions generated by a preceding inference step, by using only the top prediction when relevant. By default, top_prediction
is False
. This argument is particularly useful for tagging or classification models, for which the model generates a prediction for all predicted concepts.detector
step. The items_router
step then creates branches for the different categories of items detected. Finally, for one of those categories, concept_2
, the bounding boxes are sent to another model to determine the type of concept_2.concept_name
argument) with the resulting value in the default region of the corresponding entry (it assumes that all provided regions have the same entry).concept_name
: name of the concept with which the value is stored in the default region of the corresponding entryconcept_name_to_count
: a region is counted (once) if at least one of its concept has a name included in concept_name_to_count
. If no concept names are provided, counts all the regions.concept_name
) with the resulting value in the default region of the corresponding entry (it assumes that all provided regions have the same entry).concept_name
: name of the concept with which the value is stored in the default region of the corresponding entryconcept_names_to_count
label_names_to_count
. If no label is provided, counts all the predictions.ComparisonOperator
evaluates a comparison operator taking 2 input concepts and returns a concept with the result.concept_name
: name of the concept with which the resulting value is stored in the default region of the first given entry (always a Boolean)concept_names_of_operands
: name of the concepts with which the values are stored. Each entry has a concept in the associated default region that has the same name as the entry to directly access the valueoperator
: an option from the list below"<"
- lower than"<="
- lower or equal"=="
- equal"!="
- not equal">"
- above">="
- above or equalLogicalOperator
evaluates a logical operator taking 2 input concepts and returns a concept with the result.concept_name
: name of the concept with which the resulting value is stored in the default region of the first given entry (always a Boolean)concept_names_of_operands
: name of the concepts with which the values are stored. Each entry has a concept in the associated default region that has the same name as the entry to directly access the valueoperator
: an option from the list below"and"
or "&&"
- AND"or"
or "||"
- OR"not"
or "!"
- NOT"nand"
- NAND (False if all input values are False)"nor"
- NOR (True if all input values are False)NegationOperator
negates the boolean concept provided in the given region.concept_name
: name of the concept with which the resulting value is stored in the default region of the given entry (always a Boolean)concept_names_to_negate
: name of the concept with which the Boolean value to negate is stored.MathOperator
evaluates a mathematical operator taking two input concepts and returns a concept with the result.concept_name
: name of the concept with which the resulting value is stored in the default region of the first given entry (always a Number)concept_names_of_operands
: name of the concepts with which the values are stored. Each entry has a concept in the associated default region that has the same name as the entry to directly access the valueoperator
: an option from the list below"+"
- add"-"
- substract"*"
- multiply"/"
- true div"**"
OR "pow"
- power"%"
- moduloHasLabel
steps indicate if a label is predicted in the given region. It creates a concept named after concept_name
in the input region with value True
if a label was found, False
otherwise.concept_name
: name of the concept with which the value is stored in the default region of the corresponding entrylabel_names_to_find
.concept_names_to_find
is provided, the predictions whose concept name is not included in concept_names_to_find are ignored.HasWorkflowConcept
steps indicate if a workflow concept exists in the given region. It creates a concept named after concept_name
in the input region with value True
if a label was found, False
otherwise.concept_name
: name of the concept with which the value is stored in the default region of the corresponding entryconcept_names_to_find
is provided, the predictions whose concept name is not included in concept_names_to_find are ignored.FlowController
stops a branch execution according to a concept value. It retrieves the concept named after concept_name
in the first input region. If its value is different from expected_value
, the branch execution is stopped. Otherwise, an input is forwarded (the second one if there are two inputs, the only one if there is only one).concept_name
concept)concept_name
: indicates the name of the concept to look for in the first input.expected_value
: value that is expected to enforce the condition for the concept that is retrieved.