You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first three lines are as expected, but, if I understand correctly, lines 4 to 6 should have given 3, 4, and 5, instead of 1, 1, and 2. At least judging by this and similar examples, it looks like the key is first converted to an integer i by replacing it with the first integer that appears in the representation of the key (for example [2,[1,2]] is replaced with 2), and then lie[i] is returned, which is the (i-1)'th element in the flattened underlying data array (indeed in the above example, lie[i] returns i for i=1,...,5).
Desktop:
OS: Ubuntu 22.04
roughpy version 0.1.1
The text was updated successfully, but these errors were encountered:
OK so it seems there is a bug in the conversion from the Python Lie key into indices. For now the only solution I can offer is to index with integers instead:
Notice that we have to start from 1, the integers are being seen as the internal representation of Lie keys and not as indices which is also a bug. This will be fixed later to meet expectations.
It seems that indexing a
Lie
with aLieKey
does not yield the expected result. Example:gives the following output.
The first three lines are as expected, but, if I understand correctly, lines 4 to 6 should have given 3, 4, and 5, instead of 1, 1, and 2. At least judging by this and similar examples, it looks like the
key
is first converted to an integeri
by replacing it with the first integer that appears in the representation of the key (for example[2,[1,2]]
is replaced with2
), and thenlie[i]
is returned, which is the(i-1)
'th element in the flattened underlying data array (indeed in the above example,lie[i]
returnsi
fori=1,...,5
).Desktop:
The text was updated successfully, but these errors were encountered: