-
Notifications
You must be signed in to change notification settings - Fork 44
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
Feature: tp.to_numpy() #352
Comments
Hey @Musa-Sina-Ertugrul! Have someone on Discord that wanted to take on it but hasn't started, just pinged them to see if they are OK with freeing it up, I'll let you know when they get back to me. Thanks! |
Not problem If he/she wants I can work on other good first issue labels. |
Hey @Musa-Sina-Ertugrul! No answer from them on Discord so it's all yours if you want it. |
Thanks 😄 Yes, I want |
I could not managed preparing environment sorry :( Can you give this task to someone |
Hello @ianspektor |
@Musa-Sina-Ertugrul sorry to hear that - could you open an issue with what went wrong? Both so that we can help you set it up and improve the documentation for everyone else :) |
@nagavenkateshgavini sure! Let me know if you run into any issues or have any doubts. I see you've joined our Discord, feel free to write there if you prefer :) Thanks! |
Export an EventSet to numpy arrays with
tp.to_numpy(evset)
.See
tp.to_pandas()
for reference.The EventSet is flattened (its index is dropped and kept as features, with
.drop_index(keep=True)
). Returns a dictionary mapping feature names to values, + an extra "timestamps" key with the timestamps.Provide
timestamps: bool = True
andtimestamp_to_datetime: bool = True
arguments (same as intp.to_pandas()
)This needs to be tested thoroughly, see
temporian/io/test/pandas_test.py
for reference.Example:
The text was updated successfully, but these errors were encountered: