Clarification on LargeScaleMeanShift processing messages

OTB Usage
1

In the following run:

otbcli_LargeScaleMeanShift -in QB_1_ortho.tif -spatialr 50 -ranger 80 -minsize 1 -mode.vector.out regions_s50_r80.shp -tilesizex 1024 -tilesizey 1024 -ram 2048
2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: Default RAM limit for OTB is 256 MB
2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: GDAL maximum cache size is 1995 MB
2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: OTB will use at most 8 threads
2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: Smoothing step...
2023-03-07 10:14:27 (INFO): Loading metadata from official product
2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: Margin of 5001 pixels applied to each tile to stabilized mean shift filtering.

2023-03-07 10:14:27 (WARNING) LargeScaleMeanShift: Margin value exceed the input image size.

2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: Mode Search is disabled.

2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: Number of tiles: 1 x 1
2023-03-07 10:14:27 (INFO) LargeScaleMeanShift: Tile shifting ...
  1. Why do I get the message “Default RAM limit for OTB is 256 MB” if I have set ram to 2048?
  2. Why is there a Tile shifting if there is only 1 tile?
2

Hi

the Default RAM limit is always set to 256Mb, it is not related to the RAM parameter you pass because it is a default one. I agree that the message should be “User RAM Limit is set to 2048Mo instead.”
The Tile shifting message is always displayed by OTB otbAppLogINFO(<< “Tile shifting …”); even it the tile is 1x1, it could be changed

Best regards