You are right! 14.0.7.16.3 will fall on this date, if we follow the most accepted and popular correlation between the calendars.

This Kata challenge is completely wrong in its very basic assumptions - explaining nothing.

Still, even if the original thing applied a very different correlation, it's simply impossible to have 20 as a coefficient in the Maya Long Count at all, as their math is based on digits from 0 to 19. Couldn't have a 13 "baktun" (PIK) coefficient in the early 2000's, unless you use another correlation - still, a 20 coefficient makes it invalid anyway.

Haskell translation

I've done some research that leads to me to believe this description of the mayan long calendar is wrong.
13 20 7 16 3 should be 14 0 7 16 3 and it lies on January 6 2415.
The 13 baktun started on December 21 2012

Haskell translation

Quite easy-going kata to figure out and to practice some coding challenges with, funny task.

Hi,

I've tried multiple things and am unable to replicate the issue (in Python).

1. Using print(n) will correctly output the input in the log.
2. Incorrect outputs are displayed verbosely, i.e. n = 86: 86 should equal (1, 101)

Please open another issue with more information if you believe it is still occurring.

Nice kata.
print(n) does not work.
Unable to view inputs on "Attempt" tests.

I believe I have fixed this and added 'closeTo' assertions using expects' in-built methods.

The only errors are logical errors when the gallery width is >= 700.

They're all trivial changes to the code. I'd expect you'd be able to modify this solution for those cases.

Hey, you said that this is the solution? But "setUpGallery" isn't named correctly, the values are rounded, and the Image objects aren't returned as rows.

Can you please provide the updated code where you got the 'floating point error'.

This will prevent me from wasting time trying to recreate your solution and getting it wrong.

The solution's just the link above though...

Could you please send your solution over so I can look into it further? Post it in Discord at "help-author" if that is better.

@theunbeatableant

However, is you solution supposed to give the correct answers? If so, I will implement that now and that should fix everything.

The last row is incorrect.

Although... that might be quite complicated to do with a 2D array of Image objects. If I were to implement fuzzy assertion, then I would appreciate any guidance you could give.

I could implement a 0.001 tolerance on either side of the expected value, that will definitely fix the errors.

However, is you solution supposed to give the correct answers? If so, I will implement that now and that should fix everything.