imageClassifier error : GetBlockRef failed at X block offset ....., Y block offset .... what causes this and how to get rid of it?

OTB Usage
41

Just did the following with your data and package OTB-6.6.0-win64:

otbcli_BandMath.bat -out black.tif -il "ROI final 1.13.tif" -exp "im1b1"
2019-01-24 15:02:12 (INFO): No kwl metadata found in file ROI final 1.13.tif
2019-01-24 15:02:12 (INFO): Default RAM limit for OTB is 128 MB
2019-01-24 15:02:12 (INFO): GDAL maximum cache size is 403 MB
2019-01-24 15:02:12 (INFO): OTB will use at most 4 threads
2019-01-24 15:02:12 (INFO): Image #1 has 3 components

2019-01-24 15:02:12 (INFO): Estimated memory for full processing: 7786.52MB (avail.: 128 MB), optimal image partitioning: 61 blocks
2019-01-24 15:02:12 (INFO): File black.tif will be written in 62 blocks of 28000x131 pixels
Writing black.tif...: 100% [**************************************************] (81 seconds)

Works like a charm …

42

Do you have those logs somewhere ? I would like to see the partitioning you have.

43

Yes most of the commands works well but not the imageClassifier sadly.

Yep :
otbcli_BandMath.bat -out black.tif -il “ROI final 1.13.tif” -exp “im1b1”
2019-01-24 15:11:04 (INFO): No kwl metadata found in file ROI final 1.13.tif
2019-01-24 15:11:04 (INFO): Default RAM limit for OTB is 128 MB
2019-01-24 15:11:04 (INFO): GDAL maximum cache size is 356 MB
2019-01-24 15:11:04 (INFO): OTB will use at most 4 threads
2019-01-24 15:11:04 (INFO): Image #1 has 3 components

2019-01-24 15:11:04 (INFO): Estimated memory for full processing: 7786.52MB (avail.: 128 MB), optimal image partitioning: 61 blocks
2019-01-24 15:11:04 (INFO): File black.tif will be written in 62 blocks of 28000x131 pixels
Writing black.tif…: 100% [**************************************************] (153 seconds)

44

Ok, i am running classification on two different systems to check, right now.

45

I’ll keep you posted.

46

ty very much. I obtained a classification by compartimentating the ROI so i can now continue my work but it would be interesting to know what happened.

47

Windows run is at 68%, no problem so far.

Linux run was almost 90% without any issue, but got killed by admin because it was heavily using a shared node on our infrastructure.

48

Both processes completed without error.

49

What’s the problem then… is my processor burning ?

50

I have no idea, but I doubt this comes from a lack of processing power … This error comes from gdal read operations and usually means that the tiff file is corrupted.

51

but my image was normal wasn’t it ?
If it is corrupted why does it work with you but not on my pc