wierd problem with command -LOG_FILE {filename}

If you are allergic to bug trackers, you can post here any remarks, issues and potential bugs you encounter
Post Reply
cincinatee
Posts: 6
Joined: Tue Nov 08, 2016 1:47 pm

wierd problem with command -LOG_FILE {filename}

Post by cincinatee »

I am facing some weird problem in command line mode.
this is what I run in a batch file

Code: Select all

@ECHO ON
CloudCompare -AUTO_SAVE ON -o smallA.las -o smallB.las -LOG_FILE smalllaslog.txt
and I get this output in text file as expected

[14:53:26] Auto-save is enabled
[14:53:26] [LOADING]
[14:53:26] Opening file: 'smallA.las'
[14:53:26] [LAS] smallA.las - signature: LASF
[14:53:26] [LAS] Cloud has been recentered! Translation: (-3409533.30,-5478490.66,-296.84)
[14:53:26] [LAS] Color field was all black! We ignored it...
[14:53:26] [LAS] All 'Point Source ID' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Flightline Edge' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Scan Direction' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Return Number' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Time' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Classification' values were the same (0)! We ignored them...
[14:53:26] [I/O] File 'smallA.las' loaded successfully
[14:53:26] Found one cloud with 26546 points
[14:53:26] [LOADING]
[14:53:26] Opening file: 'smallB.las'
[14:53:26] [LAS] smallB.las - signature: LASF
[14:53:26] [LAS] Cloud has been recentered! Translation: (-3409533.28,-5478490.67,-296.84)
[14:53:26] [LAS] Color field was all black! We ignored it...
[14:53:26] [LAS] All 'Point Source ID' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Flightline Edge' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Scan Direction' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Return Number' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Time' values were the same (0)! We ignored them...
[14:53:26] [LAS] All 'Classification' values were the same (0)! We ignored them...
[14:53:26] [I/O] File 'smallB.las' loaded successfully
[14:53:26] Found one cloud with 27228 points
[14:53:26] Processed finished in 0.12 s.

but when I run same command with big clouds(out of which above clouds are segmented),

Code: Select all

@ECHO ON
CloudCompare -AUTO_SAVE ON -o bigA.las -o bigB.las -LOG_FILE biglaslog.txt 
I get log of only last command .i.e -o bigB.las:

[14:52:27] [LAS] All 'Point Source ID' values were the same (0)! We ignored them...
[14:52:27] [LAS] All 'Flightline Edge' values were the same (0)! We ignored them...
[14:52:27] [LAS] All 'Scan Direction' values were the same (0)! We ignored them...
[14:52:27] [LAS] All 'Return Number' values were the same (0)! We ignored them...
[14:52:27] [LAS] All 'Classification' values were the same (0)! We ignored them...
[14:52:27] [I/O] File 'bigB.las' loaded successfully
[14:52:27] Found one cloud with 4712960 points
[14:52:27] Processed finished in 6.40 s.

If I add -C2C_DIST command with big data files,

Code: Select all

@ECHO ON
CloudCompare -AUTO_SAVE ON -o bigA.las -o bigB.las -C2C_DIST -LOG_FILE biglaslog.txt
I get log of C2C_DIST only :

[14:46:49] [I/O] File './bigA_C2C_DIST_2016-11-24_14h46_45.bin' saved successfully
[14:46:49] Processed finished in 39.91 s.
daniel
Site Admin
Posts: 7479
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: wierd problem with command -LOG_FILE {filename}

Post by daniel »

The LOG_FILE command should be the first one as the file is only opened when the command is encountered. Therefore almost all logs issued before this point won't be written in the file (some may still be written because the logs are processed asynchronously).
Daniel, CloudCompare admin
Post Reply