Thomas R. Covert
Thomas R. Covert
Note, this would be similar to `dplyr`'s `glimpse` function which I quite like...
Thanks - more complicated than I would have thought. Would it make sense to add another clause in the `mapslices` code that just checks if the function returns `Columns` instead...
In my mind, this could just be a part of `map`. In the event that `f` applied to an element of a `IndexedTabe` evaluates to a `Columns()`, map would construct...
Another approach here would that respects the `IndexedTable` goal of having a single row per key would be to add the newly created column to the set of key columns.
is this still busted? what is a sensible work around?
totally understand, just making sure I hadn't missed another solution somewhere. FYI the problem exists in `@combine()` expressions after a `groupby` as well.
Thanks for the quick response, and for helping me understand the issue! I'll try to figure out how to reformulate my problem without iterators then...
Here's the beginning of the error I get when I try to Zygote gradient the map(sum(...)) approach: ``` ERROR: Need an adjoint for constructor Base.Generator{Vector{Vector{Int64}}, var"#8#10"{Vector{Float64}}}. Gradient is of type...
Ah, I see that you were referring to the `eachslices` approach. I am trying to get the `view` based approach to work because in my application, the equivalent notion of...
`MLUtils.chunk` does indeed work! ``` using MLUtils function h2(y, X, theta, gs) deltas = X * theta mlg = map(length, groups) return mapreduce(f, +, chunk(y, size = mlg), chunk(deltas, size...