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.

Sign up for GitHub

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

Jump to bottom

rsi_hw_iface: decide whether AXISCORRMON object should be kept #72

Open
gavanderhoorn opened this issue Sep 3, 2016 · 1 comment
Open

rsi_hw_iface: decide whether AXISCORRMON object should be kept #72

gavanderhoorn opened this issue Sep 3, 2016 · 1 comment
Labels
question

Comments

@gavanderhoorn
Copy link
Member

From #54 (comment):

I am uncertain if the AXISCORRMON object is really needed and should be removed.
@gavanderhoorn gavanderhoorn mentioned this issue Sep 3, 2016
Merged
@BrettHemes
Copy link
Member

I think we can remove this all together, as it is redundant to the limits currently set within the AXISCORR object and we don't have any external axes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gavanderhoorn @BrettHemes