-
Notifications
You must be signed in to change notification settings - Fork 21
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
Is it possible to track the length of an evolution in time within the provided dataset? #1
Comments
Hello Erik, Amiunique stores fingerprints only when a change occurs in at least one of the attribute of the fingerprint. The creationDate corresponds to the time where the fingerprint was collected. updateDate corresponds to the last or first time (I'm not sure, I should verify in the code) where we verified if the fingerprint has changed, but no changed occurred. Finally, endDate corresponds to the date where the fingerprint changed. Warning: for privacy reasons, the times are rounded, so you may see two events appearing at the same time. Moreover, the database we distribute is only a sample of the whole database. Concerning your second question -- "Is it possible to track the length of an evolution in time before a break in the chain occurs?" -- I'm not sure I understand it correctly. If you want to know how long a fingerprint, as characterised by its combination of attributes, remains constant, then you need to subtract endDate and creationDate. I hope my explanations helped you, otherwise feel free to ask me any questions. Antoine |
Hello,
Your research is interesting. As I play around with the example data in this repo I'm curious about a couple things. What do creationDate, updateDate and endDate mean?
Is it possible to track the length of an evolution in time before a break in the chain occurs?
Example query of the dt fields for a single user_tracking_id
The text was updated successfully, but these errors were encountered: