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
I was writing a gridsearch experiment for interpolation/smoothing. I train on some regular interval of data points, and validate on some intermediate points, so here's my splitter:
If I have a list of trajectories of the same length, it should work to stack the data in shape (n_obs, n_trajectories). However, if the trajectories are different lengths, I can't stack them. The only solution I can think of is to pad with nans and stack, but that's a bad idea: it requires changes to the library's model.fit(), predict() in order to implement a convention that only matters in client code.
Would love any advice on how to write a splitter for ragged (list of list) data. Or more generally, how to write a splitter for custom containers.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Looking for the latest TMZ celebrity news? You've come to the right place. From shocking Hollywood scandals to exclusive videos, TMZ delivers it all in real time.
Whether it’s a red carpet slip-up, a viral paparazzi moment, or a legal drama involving your favorite stars, TMZ news is always first to break the story. Stay in the loop with daily updates, insider tips, and jaw-dropping photos.
🎥 Watch TMZ Live
TMZ Live brings you daily celebrity news and interviews straight from the TMZ newsroom. Don’t miss a beat—watch now and see what’s trending in Hollywood.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I was writing a gridsearch experiment for interpolation/smoothing. I train on some regular interval of data points, and validate on some intermediate points, so here's my splitter:
If I have a list of trajectories of the same length, it should work to stack the data in shape (n_obs, n_trajectories). However, if the trajectories are different lengths, I can't stack them. The only solution I can think of is to pad with nans and stack, but that's a bad idea: it requires changes to the library's
model.fit()
,predict()
in order to implement a convention that only matters in client code.Would love any advice on how to write a splitter for ragged (list of list) data. Or more generally, how to write a splitter for custom containers.
Beta Was this translation helpful? Give feedback.
All reactions