otb issueshttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues2019-08-08T08:16:58Zhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1857monteverdi does not display correctly and cannot render images2019-08-08T08:16:58Zwaynedoumonteverdi does not display correctly and cannot render images### Description
monteverdi does not display correctly.
1. icons and text are very big
2. opened images do not appear in the canvas (or maybe the canvas does not display)
![Screen_Shot_2019-02-23_at_12.25.49_AM](/uploads/be7a060e3d2708...### Description
monteverdi does not display correctly.
1. icons and text are very big
2. opened images do not appear in the canvas (or maybe the canvas does not display)
![Screen_Shot_2019-02-23_at_12.25.49_AM](/uploads/be7a060e3d2708233ddc7abd02c8e577/Screen_Shot_2019-02-23_at_12.25.49_AM.png)
### Steps to reproduce
Compiled from source according to the guide using superbuild.
### Configuration information
macOS mojave, OTB 6.6.1, build from superbuild, all deps using superbuildhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1853Upgrade gdal version to 2.4.0 in Superbuild2019-06-25T09:07:51ZJulien MichelUpgrade gdal version to 2.4.0 in SuperbuildUpgrade gdal version to 2.4.0 in SuperbuildUpgrade gdal version to 2.4.0 in Superbuild7.0.0Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1831Logging in python wrapper2019-03-13T16:10:18ZArthur VincentLogging in python wrapper## Description
This feature request is about logging.
## Feature request
The `otbAppLogINFO` seems to be disable if otb's applications are used through python wrapper.
Is it possible to enable this function using python's binding ?
...## Description
This feature request is about logging.
## Feature request
The `otbAppLogINFO` seems to be disable if otb's applications are used through python wrapper.
Is it possible to enable this function using python's binding ?
Thanks,Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1820Option to initialize K-means with user-defined centroids2019-05-06T08:24:22ZaloboaOption to initialize K-means with user-defined centroidsIt would be nice if K-means could be initialized to user-defined centroids, as in most
implementations. In case one of the classes is distinct but rare (i.e., objects on the sea surface), the sampling strategy for the initial centroids i...It would be nice if K-means could be initialized to user-defined centroids, as in most
implementations. In case one of the classes is distinct but rare (i.e., objects on the sea surface), the sampling strategy for the initial centroids is very inefficient.
e.g., in R:
```
kmeans(x, centers, iter.max = 10, nstart = 1, algorithm = c(“Hartigan-Wong”, “Lloyd”, “Forgy”, “MacQueen”), trace=FALSE) ## S3 method for class ‘kmeans’ fitted(object, method = c(“centers”, “classes”), …)
Arguments
x numeric matrix of data, or an object that can be coerced to such a matrix (such as a numeric vector or a data frame with all numeric columns).
centers either the number of clusters, say k , or a set of initial (distinct) cluster centres. If a number, a random set of (distinct) rows in x is chosen as the initial centres.
```
Option to initialize K-means with user-defined centroids
/label ~feature
7.0.0Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1814ExtractROI should make "mode.fit.im" and "mode.fit.ref" as optional parameters2020-11-02T10:32:33ZRashad KanavathExtractROI should make "mode.fit.im" and "mode.fit.ref" as optional parameters### Description
Cannot run otb::ExtractROI in qgis. An error says 'mode.fit.im' value is None, even when 'mode' parameter is set to 'standard'. This is because these parameters are marked mandatory in descriptor files.
See below outpu...### Description
Cannot run otb::ExtractROI in qgis. An error says 'mode.fit.im' value is None, even when 'mode' parameter is set to 'standard'. This is because these parameters are marked mandatory in descriptor files.
See below output from ./bin/otbcli_ExtractROI -help
```
Parameters:
MISSING -in <string> Input Image (mandatory)
MISSING -out <string> [pixel] Output Image [pixel=uint8/uint16/int16/uint32/int32/float/double/cint16/cint32/cfloat/cdouble] (default value is float) (mandatory)
-mode <string> Extraction mode [standard/fit/extent/radius] (mandatory, default value is standard)
-mode.fit.im <string> Reference image (mandatory)
-mode.fit.vect <string> Reference vector (mandatory)
-mode.extent.ulx <float> X coordinate of the Upper left corner (mandatory, default value is 0)
-mode.extent.uly <float> Y coordinate of Upper Left corner point (mandatory, default value is 0)
-mode.extent.lrx <float> X coordinate of Lower Right corner point (mandatory, default value is 0)
-mode.extent.lry <float> Y coordinate of Lower Right corner point (mandatory, default value is 0)
-mode.extent.unit <string> Unit [pxl/phy/lonlat] (mandatory, default value is pxl)
-mode.radius.r <float> Radius (mandatory, default value is 0)
-mode.radius.unitr <string> Radius unit [pxl/phy] (mandatory, default value is pxl)
-mode.radius.cx <float> X coordinate of the center (mandatory, default value is 0)
-mode.radius.cy <float> Y coordinate of the center (mandatory, default value is 0)
-mode.radius.unitc <string> Center unit [pxl/phy/lonlat] (mandatory, default value is pxl)
-startx <int32> Start X (mandatory, default value is 0)
-starty <int32> Start Y (mandatory, default value is 0)
-sizex <int32> Size X (mandatory, default value is 0)
-sizey <int32> Size Y (mandatory, default value is 0)
-cl <string list> Output Image channels (mandatory, no default value)
-elev <group> Elevation management
-elev.dem <string> DEM directory (optional, off by default)
-elev.geoid <string> Geoid File (optional, off by default)
-elev.default <float> Default elevation (mandatory, default value is 0)
-ram <int32> Available RAM (MB) (optional, off by default, default value is 128)
-inxml <string> Load parameters from XML (optional, off by default)
-progress <boolean> Report progress
-help <string list> Display long help (empty list), or help for given parameters keys
```
"mode.fit.*" parameters shouldn't be bothered when value of 'mode' parameter is set to 'standard'. The sub-parameters of "mode.fit" are not optional and cause failure in qgis. Running this app on command line is working.
But QGIS requires (and is right) all mandatory parameters must be set. Parameters (like above) that depend on value of another parameter must be marked optional.
### Steps to reproduce
Run otb::ExtractROI with qgis
### Configuration information
OS, OTB version or tag, information related to build (binaries, superbuild, system libs ...)7.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1532Synchronized writers2020-01-16T15:14:35ZJulien MichelSynchronized writersIn Orfeo ToolBox, there are several filters that produces multiple output images. For now, writing all those output to separate files is inneficient, since the streaming mechanism will end up executing the filter on the whole dataset sev...In Orfeo ToolBox, there are several filters that produces multiple output images. For now, writing all those output to separate files is inneficient, since the streaming mechanism will end up executing the filter on the whole dataset several time.
The workaround is to pack all those outputs in a single output image using `ImageListToVectorImageFilter`, but this is not a good solution in many cases : the different ouptut might represent very different things that should not resid in a single `VectorImage`, and sometimes the different ouptuts have different types (for instance if their is an output mask along with a scalar image).
We need to enable synchronization between writer, so that once a stream is calculated by the filter, all corresponding output files are updated.7.1.0Cédric TraizetCédric Traizet