E57_ERROR_BAD_CHECKSUM error handling on command line

[jukka.alander]

Hello,

We are processing E57 scans on a command line script. Sometimes it happens that there is failure in file transfer and E57 is corrupt.

Currently, command line processing will keep on processing those scans CC was able to read before error in the file, like this;
___________________
.........
[LOADING]
Opening file: 'E:\temp\922_1krs.e57'
[E57] 'formatName' - ASTM E57 3D Imaging Data File
[E57] 'guid' - {329E082E-5C6D-4CA7-AFA3-1728B5DC8348}
[E57] 'versionMajor' - 1 (INTEGER)
[E57] 'versionMinor' - 0 (INTEGER)
[E57] Reading new scan node (0)
[E57] Reading new scan node (1)
[E57] Reading new scan node (2)
[E57] Reading new scan node (3)
[E57] Reading new scan node (4)
[E57] Error: checksum mismatch, file is corrupted (E57_ERROR_BAD_CHECKSUM)
context: fileName=E:\temp\922_1krs.e57 computedChecksum=935982091 storedChecksum=2484617588 page=6755328 length=21129353216
An error occurred while loading '922_1krs': the third-party library in charge of saving/loading the file has thrown an exception
Found one cloud with 118902064 points
Found one cloud with 140416667 points
Found one cloud with 40002868 points
Found one cloud with 40734730 points
Auto-save is disabled
[MERGE CLOUDS]
[SUBSAMPLING]
............
______________________________

... and will eventually save data.

I think it would be good to be able to halt the processing completely if an error like this occurs.

Br,
Jukka

[daniel]

Hum, that would be a big change of behavior. Not sure what other users would think about that?

[daniel]

Hum, that would be a big change of behavior. Not sure what other users would think about that?

[jukka.alander]

Hum, that would be a big change of behavior. Not sure what other users would think about that?

I understand, it's not a good idea to change command line basic behavior and break scripts people already use.

I'll take a look at alternative methods how these broken files could be recognized before processing in CC.