Skip to content
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

numpy > 2.0 produces unexpected results #435

Open
jmorese opened this issue Oct 16, 2024 · 0 comments
Open

numpy > 2.0 produces unexpected results #435

jmorese opened this issue Oct 16, 2024 · 0 comments

Comments

@jmorese
Copy link

jmorese commented Oct 16, 2024

When numpy > 2.0 installed we found unexpected behavior in resample and set_index.

Test one:

 a = tp.event_set(
     timestamps=[1.5, 5.0, 8.0, 9.0],
     features={"f1": [1.0, 2.0, 3.0, 4.0]}
 )
 b = tp.event_set(timestamps=[-1.2, 1.6, 6.0, 10.0])
 c = a.resample(b)
 c

Expected: [ nan, 1, 2, 4]
Obtained:
Image

Test two:

 a = tp.event_set(
     timestamps=[1.5, 5.0, 8.0, 9.0],
     features={"f1": [1.0, 2.0, 3.0, 4.0], "f2" : ["a", "a", "b", "b"]}
 )
 a.set_index('f2')

Expected: Same event set with an index.
Obtained:
Image

Versions installed:
numpy 2.1.1
temporian 0.9.0
python 3.11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant