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.

Sign up for GitHub

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

Jump to bottom

Problème avec les timestamp #9

Closed
bguil opened this issue Jun 21, 2020 · 3 comments
Closed

Problème avec les timestamp #9

bguil opened this issue Jun 21, 2020 · 3 comments

Comments

@bguil
Copy link

bguil commented Jun 21, 2020

C'est arborator qui gère les timestamp actuellement.

Je pense qu'il y a des incohérences car, par exemple, dans le project NAIJA-PRAAT_19.06, sample ABJ_INF_12_Evictions_MG, il y a des valeurs comme:

# user_id = bernard.l.caron
# sent_id = ABJ_INF_12_Evictions_MG__51
# timestamp = 1592599048911
…
…

# user_id = bernard.l.caron
# sent_id = ABJ_INF_12_Evictions_MG__50
# timestamp = 1592570701.78661
…

Le premier timestamp est un INT en millisecondes et le deuxième est un FLOAT en secondes.
@bguil bguil mentioned this issue Jun 22, 2020
Closed
@marinecourtin
Copy link
Member

Fixed, will be closed when it's pushed to prod.

@bguil
Copy link
Author

bguil commented Jul 10, 2020

We decided to use the format INT given in millisecond.

@bguil
Copy link
Author

bguil commented Jul 30, 2020

All timestamps in both servers now follow the format "INT in millisecond"

@bguil bguil closed this as completed Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bguil @marinecourtin