Skip to content
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

Rule: No Full Z-Retraction Before Travel #6

Open
marks-res opened this issue Dec 8, 2023 · 0 comments
Open

Rule: No Full Z-Retraction Before Travel #6

marks-res opened this issue Dec 8, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@marks-res
Copy link
Member

marks-res commented Dec 8, 2023

Feature Request

Rule Name Category Description
no-full-z-retraction-before-travel Logical Error When optimizing method speed, a programmer may often disable retracting all the way to Z-max because they’ve deemed it safe in the current deck layout. However, when updating a method, the deck may change and this movement can get overlooked. By forcing an explicit comment in the code describing reasoning for the original safe motion path, it is easier to spot and take into account when modifying the code to avoid potential crashes.
@marks-res marks-res added the enhancement New feature or request label Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant