Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
interimage:batch_processing [2014/04/06 17:41] rsilva |
interimage:batch_processing [2014/04/09 06:01] (current) rsilva |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| [[interimage:|InterIMAGE wiki]] | [[interimage:|InterIMAGE wiki]] | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| ====== Batch Processing ====== | ====== Batch Processing ====== | ||
| Line 25: | Line 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). | 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: | least these two following parameters: | ||
| Line 56: | Line 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). | ||
| Line 93: | Line 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. | ||
| + | |||
| Line 103: | Line 95: | ||
| 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"// | ||
