CloudCompare forum

Hi

I get

"[FILTER BY VALUE]
Failed to read a numerical parameter: max value (after min value). Got 'FILTER_SF' instead."

For this .bat

for %%f in (E:\LIDAR_JAPAN\MMS8_Prototype_3\MMS\02_Ground_Clean\*.las) DO (
"C:\Program Files\CloudCompare\cloudcompare.exe" -SILENT -O -GLOBAL_SHIFT AUTO "%%f" -AUTO_SAVE OFF -C_EXPORT_FMT PLY -SET_ACTIVE_SF 9 -FILTER_SF MIN N_SIGMA_MIN 0 -SET_ACTIVE_SF 7 -FILTER_SF 0 1 -SET_ACTIVE_SF 0 -SF_COLOR_SCALE ColorScale_Intensity_Fixed.xml -SF_CONVERT_TO_RGB FALSE -REMOVE_ALL_SFS -PLY_EXPORT_FMT BINARY_LE -SAVE_CLOUDS
)


The error is for sure here "-FILTER_SF MIN N_SIGMA_MIN 0 ", I whant to filet from the minimum value to the median value. I'm trying to split a road scan based on the GPS time. Since the dataset is manually cut in half and each half has GPS time values extreme one another.


According to the command details

"You can use special words in place of numbers that CC will replace by the actual SF values:

'MIN' = min value
'DISP_MIN' = min displayed value
'SAT_MIN' = min saturation value
'MAX' = max value
'DISP_MAX' = max displayed value
'SAT_MAX' = max saturation value
'N_SIGMA_MIN {N}' = mean - N * standard deviation
'N_SIGMA_MAX {N}' = mean + N * standard deviation"



cc 2.13 alpha 01/07/2023 (I'm downloading april beta just in case)
same issue with april version :|

looks like the mean + version works!

"-FILTER_SF MIN N_SIGMA_MAX 0"


My only doubt is that I see this printed in the log
[FILTER BY VALUE]
Interval: [MIN - 0]


I would spect the MIN value - MEDIAN VALUE-0 to be printed

later on after file creaton the values are printed in the file name

08OE1794_FILTERED_[-177279_-89501.8]_FILTERED_[0_1]_2023-05-12_19h24_35_545




Interval: [0 - MAX] and then the range with numbers [ -177279 -89501.8 ]

That said, since I just needed median value I got away but the MEDIAN - N is broken, so there seems to be a bug

yet, if I use:

-FILTER_SF N_SIGMA_MAX 0 MAX

I get this error
Failed to read a numerical parameter: min value (after "-FILTER_SF"). Got 'N_SIGMA_MAX' instead.

YET, if I use this, -FILTER_SF N_SIGMA_MIN 0 MAX, it works.

My confussion intensifies :D

Well, it may not be clear in the documentation, but you can only use MIN/DISP_MIN/SAT_MIN/N_SIGMA_MIN for the min boundary. And equivalently, MAX/DISP_MAX/SAT_MAX/N_SIGMA_MAX for the max boundary.

I could change that if necessary?

Apologies for the late repply I did not see your answer.

I was able to get away with the available options in the end. If I ever find a case where I can´t workaround I may come to beg for adding numerical values :D

tx