Skip to main content
43 events
when toggle format what by license comment
S Oct 11, 2020 at 17:05 history bounty ended Giuseppe
S Oct 11, 2020 at 17:05 history notice removed Giuseppe
S Oct 5, 2020 at 16:11 history bounty started Giuseppe
S Oct 5, 2020 at 16:11 history notice added Giuseppe Reward existing answer
S Oct 5, 2020 at 16:09 history bounty ended Giuseppe
S Oct 5, 2020 at 16:09 history notice removed Giuseppe
S Oct 1, 2020 at 15:09 history bounty started Giuseppe
S Oct 1, 2020 at 15:09 history notice added Giuseppe Reward existing answer
Sep 10, 2020 at 18:30 answer added Greg Martin timeline score: 2
Sep 10, 2020 at 14:41 comment added Giuseppe @null I'm using the terminology that the SSA does, you can take it up with them and I'll change it when they do.
Sep 10, 2020 at 14:37 comment added Giuseppe @GregMartin well, yes, encoding the whole table in the M/F values has been done, and I'm rather regretful of that permissivity, but I stand by my original rules. Do what you want, but it's rather against the spirit of the challenge to encode that much information.
Sep 10, 2020 at 14:33 comment added Giuseppe @thedefault. that's perfectly fine. Would be interested in seeing another approach like we have here.
Sep 10, 2020 at 8:28 comment added Greg Martin When you say "You can specify any two distinct values for M/F", what are the restrictions on "value"? Can a value be an ordered triple of numbers? Can it be a function? Can it be the lists that give the values of the mortality table?
Sep 10, 2020 at 8:09 comment added the default. Mathematica can do MortalityData[<|"Age" -> Quantity[60, "Years"], "Gender" -> "Male"|>, "RemainingLifeExpectancy"].
Sep 10, 2020 at 7:55 comment added qwr @TimPederick your final score will be calculated based on your death date.
Sep 10, 2020 at 7:17 comment added qwr I think you made the input format too flexible. Especially considering the solution that encoded the inputs as in base 1000 the tables for male and female.
Sep 10, 2020 at 5:19 comment added TwilightSparkle Sex? Gender. (15 chars)
Sep 9, 2020 at 14:47 comment added Tim Pederick Misleading title. Why isn't the challenge predicting when I, personally, will die, and then scoring me by my accuracy? :-P
Sep 9, 2020 at 14:37 answer added Dominic van Essen timeline score: 2
Sep 9, 2020 at 14:14 comment added Giuseppe @OlivierDulac the output is the life expectancy rather than the probabilities. The two are often presented together in a life table, but I thought life expectancy was more interesting than probability. I guess this is why long-winded preambles are generally frowned upon. I cleaned it up a bit, is that clearer?
Sep 9, 2020 at 14:13 history edited Giuseppe CC BY-SA 4.0
deleted 130 characters in body
Sep 9, 2020 at 14:08 comment added Olivier Dulac There seems to be a problem either in the first chapter or in the numbers: you say the table shows the probability that a person aged A years will die in the next year and I see that at age A=0 that probability is >70(%?), and goes to <1(%?) when reaching age A=113 ? ... this seems reversed. Did you mean "survive"? (and even then, it seems quite low for the low-to-middle ages...)
Sep 9, 2020 at 14:06 comment added Giuseppe @DarrelHoffman fixed. Thanks.
Sep 9, 2020 at 14:05 history edited Giuseppe CC BY-SA 4.0
deleted 1 character in body
Sep 9, 2020 at 12:58 comment added Darrel Hoffman Nitpick: It should be "real and imaginary parts of a complex number".
Sep 9, 2020 at 10:27 answer added Robin Ryder timeline score: 12
Sep 9, 2020 at 8:55 answer added Dominic van Essen timeline score: 3
Sep 9, 2020 at 7:38 comment added Kaddath Is there a Depressing Golfing Week here like in C&H?
Sep 9, 2020 at 3:36 answer added Dingus timeline score: 7
Sep 9, 2020 at 1:13 history became hot network question
Sep 8, 2020 at 22:49 answer added xash timeline score: 5
Sep 8, 2020 at 21:08 answer added ZaMoC timeline score: 7
Sep 8, 2020 at 20:05 history edited Giuseppe CC BY-SA 4.0
added 4 characters in body
Sep 8, 2020 at 18:26 answer added Arnauld timeline score: 12
Sep 8, 2020 at 18:25 answer added ovs timeline score: 3
Sep 8, 2020 at 18:00 history tweeted twitter.com/StackCodeGolf/status/1303392662108733446
Sep 8, 2020 at 17:55 comment added Giuseppe @user if R hadn't been the LoTM for September, I would have saved it for Halloween.
Sep 8, 2020 at 17:54 comment added Giuseppe @Arnauld that challenge was my inspiration for swapping it from kolmogorov-complexity! Added the note about the score, definitely missed that :-)
Sep 8, 2020 at 17:53 history edited Giuseppe CC BY-SA 4.0
added 47 characters in body
Sep 8, 2020 at 17:34 comment added Arnauld Vaguely related (in the spirit). Pro tip: include a mention that the lowest score wins in bold! :-p
Sep 8, 2020 at 17:30 comment added Razetime I really like the approximation part of this question that throws kolmogorov complexity out the window.
Sep 8, 2020 at 17:24 comment added user This challenge is depressing. Excuse me while I go write my will...
Sep 8, 2020 at 17:11 history asked Giuseppe CC BY-SA 4.0