You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okay, you can say that this is because I defined an anonymous function. But I definitely imagine that one of the main use cases of this aggregation will be with anonymous functions.
which is better. But maybe it would be even better if we changed the title to use function_name(property), which would display here as average_green(status). I think this is more reasonable. If someone used mean as the function, then the field would display as mean(status) which makes super much sense!
The text was updated successfully, but these errors were encountered:
@kavir1698 I also think it is important that in step! docstring the return type dataframe is discussed in more detail. The behavior differs fundamentally when aggregators is a vector or a dictionary. Because on the latter, the row number is actually the step number, but if it is a vector the column number is actually the step number.
This is definitely not something I would imagine without reading it at the documentation.
In the forest fire model I am doing:
which returns:
Okay, you can say that this is because I defined an anonymous function. But I definitely imagine that one of the main use cases of this aggregation will be with anonymous functions.
On the otherhand, using a named function:
gives
which is better. But maybe it would be even better if we changed the title to use
function_name(property)
, which would display here asaverage_green(status)
. I think this is more reasonable. If someone usedmean
as the function, then the field would display asmean(status)
which makes super much sense!The text was updated successfully, but these errors were encountered: