Diferenças

Aqui você vê as diferenças entre duas revisões dessa página.

--- interimage:batch_processing [2014/04/06 20:27] – rsilva
+++ interimage:batch_processing [2014/04/09 09:01] (atual) – rsilva
@@ Linha 1: / Linha 1: @@
 [[interimage:|InterIMAGE wiki]]
 ====== Batch Processing ======
-As for the version 1.41 it is possible to run InterIMAGE in batch mode. With this new operation mode it is possible to create an interpretation project and then run
+As for the version 1.39 it is possible to run InterIMAGE in batch mode. With this new operation mode it is possible to create an interpretation project and then run
 it several times without having to interact with the user interface. This was mainly done
 to allow the execution of the so called pipelines. So, for example, now it is possible to
@@ Linha 25: / Linha 16: @@
 Finally, using some options it is possible to run slightly different configurations of the same operator or decision rule (this could be used to tune automatically the parameters values).
-To execute InterIMAGE in batch mode one should call it from the command line with at
+To execute InterIMAGE in batch mode it's necessary to create a project through the user interface. After that one should call it from the command line with at
 least these two following parameters:
@@ Linha 56: / Linha 47: @@
 The semantic network file (.net) is the one that stores the classes that are expected to
 be found in a scene and also the operators that will be executed during the
-interpretation. It is possible, for example, to interpret a scene from different point of
+interpretation. With this option the original semantic network will be replaced. It is possible, for example, to interpret a scene from different point of
 views (land cover / land use).
@@ Linha 93: / Linha 84: @@
 In this case the operator parameter value should be set to @scale@ in the interface. When the project is executed in batch, the system will replace the parameter value accordingly.
@@ Linha 103: / Linha 95: @@
 With this option it is possible to change the value of a decision rule parameter.
-Note that in this case the //parameter_value_mask// must be unique and ordered numbers in this format 00001, 00002 etc. With this option it is possible to run slightly different configurations of the same decision rule (this could be used to tune automatically the decision rule parameters values).
+Note that in this case the parameter value masks must be unique and ordered numbers in this format 00001, 00002 etc. With this option it is possible to run slightly different configurations of the same decision rule (this could be used to tune automatically the decision rule parameters values).
 **Example**: //**interimage** ... "parameterDecisionRule=00001#75"//
@@ Linha 161: / Linha 153: @@
   * The //decision_rule// file should be created at the creation of the project;
   * //new_semantic_network// is the new semantic network path.
@@ Linha 175: / Linha 168: @@
   * The //decision_rule// file should be created at the creation of the project;
   * //@scale@// is an operator parameter value mask set at the creation of the project;
-  * //00001// is a decision rule parameter value mask set at the creation of the project;
+  * //00001// is a decision rule parameter value mask set at the creation of the project.