Skip to content

fixed tg4x and tested now works #692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

fixed tg4x and tested now works #692

wants to merge 2 commits into from

Conversation

daysgobye
Copy link
Collaborator

No description provided.

@daysgobye daysgobye added the bug Something isn't working label Feb 5, 2023
Comment on lines +33 to +85
coord_mapping = [
0,
1,
2,
3,
4,
5,
6,
28,
29,
30,
31,
33,
7,
8,
9,
10,
11,
12,
13,
35,
36,
37,
38,
39,
14,
15,
16,
17,
18,
19,
20,
42,
43,
44,
46,
21,
22,
23,
25,
26,
50,
51,
52,
53,
]
# all keys
# coord_mapping = [
# 0 ,1 ,2 ,3 ,4 ,5 ,6 ,28,29,30,31,32,33,
# 7 ,8 ,9 ,10,11,12,13,35,36,37,38,39,
# 14,15,16,17,18,19,20,42,43,44,45,46,
# 21,22,23,25,26,50,51,52,53
# ]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the past people have put

# flake8: noqa
# fmt: off

into their kb.py files to disable linting for coord_mapping and format it the way it is in the comment. We can tell the linter to make an exception in general, just like we do for main.py (implemented in #710).

@regicidalplutophage
Copy link
Member

This PR has been closed due to removal of the master branch, which has been inactive for over a year. The default branch is main. If reopening a PR that were closed in this cleanup, please rebase it against main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants