Divisão de Observação da Terra e Geoinformática

Ferramentas do usuário

Ferramentas do site

Visitou:
interimage:batch_processing

Diferenças

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

Link para esta página de comparações

Ambos lados da revisão anteriorRevisão anterior
Próxima revisão		Revisão anterior
interimage:batch_processing [2014/04/06 20:22] – rsilvainterimage:batch_processing [2014/04/09 09:01] (atual) – rsilva
Linha 1: Linha 1:
 [[interimage:|InterIMAGE wiki]]  [[interimage:|InterIMAGE wiki]] 
- 
- 
- 
- 
- 
- 
- 
- 
  
 ====== Batch Processing ====== ====== 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  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  to allow the execution of the so called pipelines. So, for example, now it is possible to 
Linha 20: Linha 12:
 different ROIs without having to change them using the interface. In fact, it is possible to write a  different ROIs without having to change them using the interface. In fact, it is possible to write a 
 batch file that executes different InterIMAGE instances to classify hundreds of images  batch file that executes different InterIMAGE instances to classify hundreds of images 
-with little user interaction. +with little user interaction.
  
-To execute InterIMAGE in batch mode one should call it from the command line with at +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 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:  least these two following parameters: 
  
Linha 53: Linha 47:
 The semantic network file (.net) is the one that stores the classes that are expected to  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  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).  views (land cover / land use). 
 +
  
  
 ====resourceImage==== ====resourceImage====
  
-//resourceImage=“<resource_name,image_file>”//+//resourceImage=“<resource_name#image_file>”//
  
 With this option it is possible to change the images that are used in an interpretation.  With this option it is possible to change the images that are used in an interpretation. 
 Resource name is the key given to an image resource in InterIMAGE. Resource name is the key given to an image resource in InterIMAGE.
 +
  
  
 ====resourceShape==== ====resourceShape====
  
-//resourceShape=“<resource_name,shape_file>”//+//resourceShape=“<resource_name#shape_file>”//
  
 With this option it is possible to change the shapefiles that are used in an interpretation.  With this option it is possible to change the shapefiles that are used in an interpretation. 
 Resource name is the key given to a shape resource within InterIMAGE.  Resource name is the key given to a shape resource within InterIMAGE. 
 +
  
  
Linha 78: Linha 75:
 ====parameterOperator==== ====parameterOperator====
  
-//parameterOperator=“<@parameter_value_mask@,value>”//+//parameterOperator=“<@parameter_value_mask@#value>”//
  
 With this option it is possible to change the value of an operator parameter.  With this option it is possible to change the value of an operator parameter. 
Linha 87: 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. 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 93: Linha 92:
 ====parameterDecisionRule==== ====parameterDecisionRule====
  
-//parameterDecisionRule=“<parameter_value_mask,value>”//+//parameterDecisionRule=“<parameter_value_mask#value>”//
  
 With this option it is possible to change the value of a decision rule parameter.  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"// **Example**: //**interimage** ... "parameterDecisionRule=00001#75"//
Linha 104: Linha 103:
  
 =====Examples===== =====Examples=====
 +
  
  
Linha 116: Linha 116:
 It's possible to run an interpretation on a different image. It's possible to run an interpretation on a different image.
  
-//**interimage** "projectFile=project_name\project_name.gap" "outputDecisionRule=decision_rule.dt" "outputShapeFile=results.shp" "resourceImage=image_key,new_image"//+//**interimage** "projectFile=project_name\project_name.gap" "outputDecisionRule=decision_rule.dt" "outputShapeFile=results.shp" "resourceImage=image_key#new_image"//
  
   * //project_name// is the name of your project;   * //project_name// is the name of your project;
Linha 123: Linha 123:
   * //image_key// is the key given to the image when the project was created;   * //image_key// is the key given to the image when the project was created;
   * //new_image// is the new image file path.   * //new_image// is the new image file path.
 +
  
  
Linha 130: Linha 131:
 It's possible to run an interpretation using a different shapefile. If the shapefile is used in a project to define a ROI, this parameter could be used to interpret a different ROI. It's possible to run an interpretation using a different shapefile. If the shapefile is used in a project to define a ROI, this parameter could be used to interpret a different ROI.
  
-//**interimage** "projectFile=project_name\project_name.gap" "outputDecisionRule=decision_rule.dt" "outputShapeFile=results.shp" "resourceShape=shape_key,new_shape"//+//**interimage** "projectFile=project_name\project_name.gap" "outputDecisionRule=decision_rule.dt" "outputShapeFile=results.shp" "resourceShape=shape_key#new_shape"//
  
   * //project_name// is the name of your project;   * //project_name// is the name of your project;
Linha 152: Linha 153:
   * The //decision_rule// file should be created at the creation of the project;   * The //decision_rule// file should be created at the creation of the project;
   * //new_semantic_network// is the new semantic network path.   * //new_semantic_network// is the new semantic network path.
 +
 +
  
  
Linha 157: Linha 160:
 ====Changing Operator and Decision Rule Parameters==== ====Changing Operator and Decision Rule Parameters====
  
-It's possible to run an interpretation changing the values of specific parameters in the interpretation project.+It's possible to run an interpretation changing the values of specific parameters in the interpretation project. With these 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). 
  
 //**interimage** "projectFile=project_name\project_name.gap" "outputDecisionRule=decision_rule.dt" "outputShapeFile=results.shp" "parameterOperator=@scale@#20" "parameterDecisionRule=00001#75"// //**interimage** "projectFile=project_name\project_name.gap" "outputDecisionRule=decision_rule.dt" "outputShapeFile=results.shp" "parameterOperator=@scale@#20" "parameterDecisionRule=00001#75"//
Linha 165: Linha 168:
   * The //decision_rule// file should be created at the creation of the project;   * 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;   * //@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.
interimage/batch_processing.1396815737.txt.gz · Última modificação: 2014/04/06 20:22 por rsilva