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

_estimate_time_received should use time_server #314

Open
danielrichman opened this issue Apr 29, 2013 · 1 comment
Open

_estimate_time_received should use time_server #314

danielrichman opened this issue Apr 29, 2013 · 1 comment

Comments

@danielrichman
Copy link
Member

Some points are out of order. My current favourite is the unnamed listener whose clock is set to exactly the right time and day… in May rather than April.

currently:

  • uses time_created provided by the listener, excludes points outside std dev, takes mean

ideas:

  • correct time_created by using (time_server - time_uploaded)
  • if time_server provided, trust it and ignore others
  • weight listeners with time_server provided in the previous algo (4x ?)
@danielrichman
Copy link
Member Author

Draft: danielrichman@b628bbb

TODO: do something with this

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