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

Inconsistency in get_root_timestamps #512

Open
bdpedigo opened this issue Dec 20, 2024 · 5 comments
Open

Inconsistency in get_root_timestamps #512

bdpedigo opened this issue Dec 20, 2024 · 5 comments

Comments

@bdpedigo
Copy link
Contributor

client = CAVEclient("minnie65_phase3_v1")
root_ids = [
    864691136137805181,
    864691136237725199,
    864691135778700477,
    864691137055175542,
]
timestamps = client.chunkedgraph.get_root_timestamps(root_ids, latest=True)
print(timestamps)

gives

[datetime.datetime(2024, 10, 25, 20, 13, 10, 925000, tzinfo=<UTC>)
 datetime.datetime(2024, 12, 16, 7, 14, 45, 712000, tzinfo=<UTC>)
 datetime.datetime(2024, 12, 20, 21, 1, 7, 458073, tzinfo=<UTC>)
 datetime.datetime(1969, 12, 31, 23, 59, 59, 999000, tzinfo=<UTC>)]

Note that for the last ID the year is 1969...

But if I just query that one,

client = CAVEclient("minnie65_phase3_v1")
root_id = 864691137055175542
client.chunkedgraph.get_root_timestamps(root_id, latest=True)

I get something reasonable

[datetime.datetime(2024, 10, 15, 22, 17, 53, 503000, tzinfo=<UTC>)]
@bdpedigo
Copy link
Contributor Author

bdpedigo commented Dec 20, 2024

based on the milliseconds column, I bet this has to do with the timestamp shifting (so may be a caveclient issue)

EDIT: it looks like even before the shift the timestamp is 1970

@akhileshh
Copy link
Contributor

akhileshh commented Jan 6, 2025

Reading directly from the chunkedgraph (minnie3_v1) yields these timestamps, do they look correct?

[datetime.datetime(2024, 1, 30, 20, 22, 44, 689000, tzinfo=datetime.timezone.utc),
 datetime.datetime(2023, 5, 16, 23, 6, 11, 459000, tzinfo=datetime.timezone.utc),
 datetime.datetime(2024, 7, 9, 19, 27, 37, 99000, tzinfo=datetime.timezone.utc),
 datetime.datetime(2024, 6, 13, 19, 58, 8, 870000, tzinfo=datetime.timezone.utc)]

@bdpedigo
Copy link
Contributor Author

bdpedigo commented Jan 6, 2025

they look at least like more plausible dates - is this with latest=True?

@akhileshh
Copy link
Contributor

No, these are just the raw timestamps, when these IDs were actually created.

@akhileshh
Copy link
Contributor

Using the logic to determine latest, the last one gives 0 so this bug is on server.

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

2 participants