{"action":"created","issue":{"url":"https://api.github.com/repos/beast-dev/beast-mcmc/issues/837","repository_url":"https://api.github.com/repos/beast-dev/beast-mcmc","labels_url":"https://api.github.com/repos/beast-dev/beast-mcmc/issues/837/labels{/name}","comments_url":"https://api.github.com/repos/beast-dev/beast-mcmc/issues/837/comments","events_url":"https://api.github.com/repos/beast-dev/beast-mcmc/issues/837/events","html_url":"https://github.com/beast-dev/beast-mcmc/issues/837","id":175207695,"number":837,"title":"BEAST sometimes chooses the same random number seed","user":{"login":"pvanheus","id":4154788,"avatar_url":"https://avatars.githubusercontent.com/u/4154788?v=3","gravatar_id":"","url":"https://api.github.com/users/pvanheus","html_url":"https://github.com/pvanheus","followers_url":"https://api.github.com/users/pvanheus/followers","following_url":"https://api.github.com/users/pvanheus/following{/other_user}","gists_url":"https://api.github.com/users/pvanheus/gists{/gist_id}","starred_url":"https://api.github.com/users/pvanheus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pvanheus/subscriptions","organizations_url":"https://api.github.com/users/pvanheus/orgs","repos_url":"https://api.github.com/users/pvanheus/repos","events_url":"https://api.github.com/users/pvanheus/events{/privacy}","received_events_url":"https://api.github.com/users/pvanheus/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-06T10:01:31Z","updated_at":"2016-09-22T14:07:27Z","closed_at":"2016-09-22T14:07:27Z","body":"BEAST jobs on our cluster sometimes end up with the same random number seed. This seems to happen when our schedule (SGE) starts multiple replicates of the same job at the same time on the same host. The behaviour might be related to the initialisation of MersenneTwisterFast() using currentTimeMillis().\r\n\r\n(Observed with BEAST 1.8.1 and 1.8.3)"},"comment":{"url":"https://api.github.com/repos/beast-dev/beast-mcmc/issues/comments/248913686","html_url":"https://github.com/beast-dev/beast-mcmc/issues/837#issuecomment-248913686","issue_url":"https://api.github.com/repos/beast-dev/beast-mcmc/issues/837","id":248913686,"user":{"login":"GuyBaele","id":1092968,"avatar_url":"https://avatars.githubusercontent.com/u/1092968?v=3","gravatar_id":"","url":"https://api.github.com/users/GuyBaele","html_url":"https://github.com/GuyBaele","followers_url":"https://api.github.com/users/GuyBaele/followers","following_url":"https://api.github.com/users/GuyBaele/following{/other_user}","gists_url":"https://api.github.com/users/GuyBaele/gists{/gist_id}","starred_url":"https://api.github.com/users/GuyBaele/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GuyBaele/subscriptions","organizations_url":"https://api.github.com/users/GuyBaele/orgs","repos_url":"https://api.github.com/users/GuyBaele/repos","events_url":"https://api.github.com/users/GuyBaele/events{/privacy}","received_events_url":"https://api.github.com/users/GuyBaele/received_events","type":"User","site_admin":false},"created_at":"2016-09-22T14:07:27Z","updated_at":"2016-09-22T14:07:27Z","body":"Correct, but even initialising with nanoTime() for example might now solve this. From the Java documentation of currentTimeMillis(): 'Returns the current time in milliseconds. Note that while the unit of time of the return value is a millisecond, the granularity of the value depends on the underlying operating system and may be larger. For example, many operating systems measure time in units of tens of milliseconds.'\r\n\r\nI typically simply insert a sleep() statement in my Linux job submission script, to ensure that no 2 replicates of a BEAST run end up with the same starting seed. "}}
{"actor":{"display_login":"GuyBaele"}}