Hi Dave,

Yup. My "envelope" gave 8 days as an estimate, so I think you're right, thanks!

Just 'cos I mentioned it before: I think that the predictor is a potential source of difficulty because different places use different formats for run time. Your own ranking page says "42 years 41 days" and the WCG pages give "42:041:14:15:49", but in your reply you gave fractional years. If someone uses cut'n'paste to enter runtime it would be great if you could recognise and parse all these formats, otherwise it might be better to expressly ask for input in a specific format to make your life easier.

Once again, many thanks for a great tool Dave!

You can now enter decimal years for the predictor. If I get chance at some point I'll do the somewhat more difficult task of parsing a years/days string.

Good Afternoon All



Wow - I never thought that Mamajuanauk would be toppled. Congratulations reduk onwards and upwards.

Nice to see a fight at the top of the table -- well done reduk!

And Dave, just to say that the green appeared on cue, as you predicted.

As to the predictor, thanks for getting decimals to work, but may I make a different suggestion? It seems that you're parsing out the number of years entered and ignoring what follows (until, maybe, you start to parse out more), but you're displaying the entire user entered string in the answer. If you were to echo only the (possible fractional) years that you actually used in the calculation, then it would be obvious that you have dropped the rest and the user could decide whether or not to put the fraction in themselves. [Just a thought to make it better for the user for minimal effort on your part.]

I'm sorry, I wasn't clear enough. And, yes, you are processing any decimal fraction of a year.

But if I enter e.g. "42 years 41" days or "42:041:14:15:49" then you respond with, e.g. "With the current production rate 42:041:14:15:49 years of run time for the team will be achieved in 2 days."

If you responded with merely "With the current production rate 42 years of run time for the team will be achieved in 2 days." then it would be clear that the rest (":041:14:15:49") had been ignored. That would tell me that maybe I need to work out the decimal fraction myself.

Is that clearer? I'm just trying to help the user without giving you the task of parsing more complicated strings, though it would be great to have that ability ...