HHC 2018 Programming Contests

[Gerson W. Barbosa]

(09-30-2018 08:47 PM)3298 Wrote:  Your first example yields the same result on my program. P: -100, E: 62, I: 100.
The second one yields "Invalid Date". Kind of understandable 'cause I've yet to see a calendar with 28 or more months in a year.
Adjusted for my value of system flag 42, the program works and outputs a date that matches after being similarly adjusted. P: -100, E: 100, I: -54.
Actually, that exact date was my first test case too. High-Five!

I’m using mm/dd/yyyy format (but my program doesn’t depend on the date format, only dates should be entered accordingly).

Now 419 bytes, #EF6Eh.

1.011905 -> 10.102018
{-.99766872413 .623489809462 .998867339316 }

9.282018 -> 11.302018
{-.997668769192 1. -.54064081743}

2.271963 -> 9.292018
{-.99768769852 .623489808919 .99886733949}

No awe from the judge though, I fear :-)

Also, my last example doesn’t agree with Didier’s because I may have misinterpreted the concept of “Extrema date”. I have considered only (-1, 1) or (1, -1), but not (1, 1) and (-1, -1) pairs. I am probably wrong.

P.S.: Quoting again from the rules;

Quote:Once in a while, two cycles hit 100 and/or -100 simultaneously, as you can see on Day 63 above. Let’s call this an “Extrema Date”.

It’s clear from above that the pairs (1, 1) abd (-1, -1) should also be considered. My failure for not thoroughly reading the instructions. By fixing that the program should certainly grow larger than 485 bytes. There’s only one hour left, so I’ll let it as is. Anyway, it was fun to try.