keras
keras copied to clipboard
Updated timeseries_dataset_from_array
Hello,
@divyashreepathihalli @qlzh727 @gowthamkpr solution of #16315
I added a feature for seq-to-seq, too. If targets are defined for each step in window, this is a useful feature.
Thanks.
I created a unit test for the element_shape as is mentioned in the issue.
I delete the seq_to_seq flag.
@qlzh727
I added the drop_remainder flag.
Thanks.
@qlzh727
I changed the seq_to_seq terminology to many_to_many as is described in the example 3 in docstring.
I point to Option 1 and Option 2 in the example as the thing with the same result, but cleaner code.
Thanks.
@fchollet
Please, Can you review it?
@markub3327 Can you please resolve conflicts? Thank you!
@gbaned
Please concretize conflicts. It's not so clear to me. Thanks.
Hi @markub3327 Can you please resolve conflicts here https://github.com/keras-team/keras/pull/16533/conflicts ? Thank you!
Hi @gbaned all is done. You can merge.
Now many_to_many functionality is provided by the old procedure .... original Example 3.
Hi @fchollet / @qlzh727 Any update on this PR? Please. Thank you!
@fchollet @qlzh727
Here is the benchmark: https://gist.github.com/markub3327/7534c726208811e2312445455c7884c0
Took a look at the benchmark. Is looks like timeseries_dataset_from_array2, which I guessing is the new version, is actually performing noticeably worse. Is that correct? We will probably not be able to land this with a performance regression.
Hi @markub3327 Any update on this PR? Please. Thank you!
No..... my solution is using clearer code and more methods from TF.Dataset API, but it was slow.
Hello, Thank you for submitting a pull request.
We're currently in the process of migrating the new Keras 3 code base from keras-team/keras-core to keras-team/keras.
Consequently, merging this PR is not possible at the moment. After the migration is successfully completed, feel free to reopen this PR at keras-team/keras if you believe it remains relevant to the Keras 3 code base. If instead this PR fixes a bug or security issue in legacy tf.keras, you can instead reopen the PR at keras-team/tf-keras, which hosts the TensorFlow-only, legacy version of Keras.