« first day (2279 days earlier)      last day (672 days later) » 

Aiden Chow
Aiden Chow
01:01
@MarkReed so u r basically saying to round up to the next number if the intersection happens in the middle of a day? but that still runs into the issue of 28/2 * 13 = 182 and 33/2 * 11 = 181.5, as they both round up to 182 and thus would count as a double critical day.
i think the way to fix this is to only restrict the intersections counted if they are exactly on an integer, not in between days. but then the 379.5 would have to be changed back to 759 while leaving everything else the same
so it would be 322 759 462 and 10626
 
2 hours later…
LdBeth
LdBeth
03:25
me decides to only adhere to the\ old problem description.
 
5 hours later…
Aiden Chow
Aiden Chow
08:38
@LdBeth yea but i mean there are a few minor flaws in this problem, that cant be denied
 
5 hours later…
Mark Reed
Mark Reed
13:24
@AidenChow No, you still only count a double critical day when both cycles hit exactly the same number – even if that number is something .5 instead of a whole number. The rounding only kicks in when reporting the date of the crossover: if it's halfway between days, you count it as the later day.
So there's no double critical on day 182 because 181.5 ≠ 182. But since both cycles meet at exactly 379.5, there is a double critical on day 380.
At least, that's what I got when I added the 379.5 to my list of moduli. The details of the rounding don't matter, just the fact that you still only count criticals on exact multiples of the co-period, even when that includes a fraction.
 
5 hours later…
Aiden Chow
Aiden Chow
18:06
@MarkReed but if u read the problem statement closely it never said it had to intersect at the exact same point, just that it had to intersect on the same day
if u think about it that way then isnt 115 and 115.5 technically on the same day?
 
2 hours later…
Mark Reed
Mark Reed
19:50
It's biorhythms. They operate at the level of whole days. Any attempt to generalize to sub-day resolution will require providing time of birth (with time zone, or preconverted to UTC), and no matter how you approach it, you have a different and more complicated problem. Lacking such data, the only way you can be sure if two day counts are on the same day is if they are in fact the same number.
 
1 hour later…
Aiden Chow
Aiden Chow
20:56
@MarkReed that’s kinda my point. The problem don’t give enough info to completely rule out this interpretation and anyways, the problem doesn’t specify that u have to round up to the next day of the intersection occurs in between days
I think a simple fix would be to specify that the intersections have to occur on the same time, not only the same day
then for any intersections that occur in between days, specify that it’ll have to be rounded up (or down, doesn’t matter too much)
 
2 hours later…
LdBeth
LdBeth
22:37
Just boosted the ≢euro makeChange 200 to less than 1 sec!

« first day (2279 days earlier)      last day (672 days later) »