Reply To: Programming
@_madness_
Normally I would smile and let it pass but I have to take issue with you
to come to some understanding.
In post #98171 you state:
@ByteInBits, your MD5 sum is for the NEXT permutation. By my example, you should start with 1 and not 0.
This make you incorrect with the entry number!!
(standard practice doese not start at 1, and you never stated the deviation)
With PARI function numtoperm()
The numbering used is the standard lexicographic ordering, starting at 0.
Thus
numtoperm(26,0)
= [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26]
The entry number you gave was 390304790967593360819076481
and the PARI function
numtoperm(26,390304790967593360819076481) gives
[26, 5, 2, 18, 1, 19, 4, 15, 14, 20, 6, 12, 25, 13, 21, 3, 8, 7, 9, 10, 11, 16, 17, 22, 24, 23]
And those numbers referencing the alphabet positions produce the the following
ZEBRASDONTFLYMUCHGIJKPQVXW
and MD5 of ZEBRASDONTFLYMUCHGIJKPQVXW is
F09C437C737F2B836B1EC48A5056148E which is what I gave.
The PARI inverse function permtonum
permtonum([26, 5, 2, 18, 1, 19, 4, 15, 14, 20, 6, 12, 25, 13, 21, 3, 8, 7, 9, 10, 11, 16, 17, 22, 24, 23])
= 390304790967593360819076481
confirms the entry number
So are you saying that the PARI-gp’s inbuilt functions are at fault?!
Anyone else care to comment in this matter?