Hi community, I need some help with GroupBy node aggregation methods which require a parameter, as the Quantile method does. I am experiencing unexpected results while setting the parameter to 0.25 (for the first quartile value, or any other, BTW) and getting back always the 0.5 quantile value. May the use of flow variables in the node affect its functioning? What am I missing there? I’ll much appreciate comments regarding this point.
Hi,
when you write “unexpected results” could you provide some more details?
I just created a small example where it seems to work. Please check:
1 Like
Yes, sure, the Quantile method of aggregation has a parameter button named Edit, that opens a small window where the Quantile value can be set. It has originally the value 0.50, I change it to 0.25, press OK twice, run the node and the result shows 0.5-quantile(“variable_name”) with the median value below it. When I change the quantile value to 0.75 the result is exactly the same - the median value.
I’ve seen this behavior before — sometimes when using flow variables to control the aggregation parameter, the node doesn’t update the UI field correctly or defaults to 0.5 if the variable isn’t passed properly. Double-check that the flow variable is correctly mapped to the quantile parameter in the “Flow Variables” tab, and make sure it’s actually resolving to 0.25 at runtime. Also worth testing with a hardcoded value to confirm it’s not a logic issue upstream. Hope that helps narrow it down!
@JScheidegger : In addition to Santatra have you checked the settings of the groupby node in my example workflow?
@ActionAndi , I did try, but got this: ERROR NewWorkflowContainerEditPolicy Problem downloading and importing repository object ‘260624_GroupBy_variables’ from ‘https://api.hub.knime.com/repository/Users/actionandi/Public/01%20-%20KNIME%20Forum/260624_GroupBy_variables:data’