{"action":"closed","issue":{"url":"https://api.github.com/repos/worldpopulation/population.io-api/issues/10","labels_url":"https://api.github.com/repos/worldpopulation/population.io-api/issues/10/labels{/name}","comments_url":"https://api.github.com/repos/worldpopulation/population.io-api/issues/10/comments","events_url":"https://api.github.com/repos/worldpopulation/population.io-api/issues/10/events","html_url":"https://github.com/worldpopulation/population.io-api/issues/10","id":34884841,"number":10,"title":"What are the exact date boundaries of the various statistical functions?","user":{"login":"hheimbuerger","id":159414,"avatar_url":"https://avatars.githubusercontent.com/u/159414?v=3","gravatar_id":"","url":"https://api.github.com/users/hheimbuerger","html_url":"https://github.com/hheimbuerger","followers_url":"https://api.github.com/users/hheimbuerger/followers","following_url":"https://api.github.com/users/hheimbuerger/following{/other_user}","gists_url":"https://api.github.com/users/hheimbuerger/gists{/gist_id}","starred_url":"https://api.github.com/users/hheimbuerger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hheimbuerger/subscriptions","organizations_url":"https://api.github.com/users/hheimbuerger/orgs","repos_url":"https://api.github.com/users/hheimbuerger/repos","events_url":"https://api.github.com/users/hheimbuerger/events{/privacy}","received_events_url":"https://api.github.com/users/hheimbuerger/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/worldpopulation/population.io-api/labels/help%20wanted","name":"help wanted","color":"159818"},{"url":"https://api.github.com/repos/worldpopulation/population.io-api/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":{"login":"kcsamir","id":7687584,"avatar_url":"https://avatars.githubusercontent.com/u/7687584?v=3","gravatar_id":"","url":"https://api.github.com/users/kcsamir","html_url":"https://github.com/kcsamir","followers_url":"https://api.github.com/users/kcsamir/followers","following_url":"https://api.github.com/users/kcsamir/following{/other_user}","gists_url":"https://api.github.com/users/kcsamir/gists{/gist_id}","starred_url":"https://api.github.com/users/kcsamir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kcsamir/subscriptions","organizations_url":"https://api.github.com/users/kcsamir/orgs","repos_url":"https://api.github.com/users/kcsamir/repos","events_url":"https://api.github.com/users/kcsamir/events{/privacy}","received_events_url":"https://api.github.com/users/kcsamir/received_events","type":"User","site_admin":false},"milestone":null,"comments":9,"created_at":"2014-06-03T17:21:58Z","updated_at":"2015-12-04T08:54:56Z","closed_at":"2015-12-04T08:54:56Z","body":"@kcsamir @joeyklee Can you help me define the exact range of valid inputs into the statistical functions? I will then only let those through on the API level and reject all others with decent error messages.\r\n\r\nBased on my own experiments, here's what I've come up with so far:\r\n\r\n##### yourRANKbyAge(), yourRANKbyDate(), yourRANKToday()\r\n\r\n* The DoB has to be 1914-06-27 or past. Before that and I get NaN ranks. (Why such a weird cutoff point?)\r\n* The DoB has to be equal to or before today's date. Past that and I get NaN ranks.\r\n* The calculation date has to be equal to or past 1950-01-01. For 1949-12-31 or before I get a `dfitpack.error`.\r\n* The calculation date has to be equal to or be past the DoB. Otherwise I get `dfitpack.error`s again.\r\n* The difference between the DoB and the calculation date must be at most 36501 days. If it's 36502 days, I get a NaN rank again. As an example, the pair of 1925-06-04 and 2025-05-11 still works, but 2025-05-12 does not. (Strangely, in the R implementation, 2025-05-10 still works and 2025-05-11 already does not.)\r\n\r\n##### yourRANKTomorrow()\r\n\r\nI haven't worked on this yet. Can you give me some insight, or shall I experimentally determine the boundaries?\r\n\r\n##### rem_le()\r\n\r\nSame here."}}