-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add stft
to keras_core.ops
#697
Comments
Sure, that sounds good. We already have fft and fft2 so it seems fine.
What are our options?
It's fine to follow the same argument semantics and order. However we will still need to standardize argument names so that they are consistent with Keras argument naming conventions. |
Actually
Which one do your prefer?
There are certain challenges to implement the same functionality of scipy version for all backends such as |
Hi keras-core team
I'm trying to use keras-core to build an audio model. However, I've found that there are certain operations that are missing for audio processing
tf.signal.frame
tf.signal.rfft
tf.signal.stft
etc...
I have already implemented
stft
for all backends. Is it good to add to keras-core?If that's the case, would it be better to separate
rfft
andframe
fromstft
?The working example with the the results that are passed with
np.testing.assert_allclose
(I have implemented
stft
with the signature from librosa because I think it is a more mature library for audio processing)The text was updated successfully, but these errors were encountered: