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

Why is *Delay(theta-dt/2, ...) better? #169

Open
arvoelke opened this issue Mar 15, 2019 · 1 comment
Open

Why is *Delay(theta-dt/2, ...) better? #169

arvoelke opened this issue Mar 15, 2019 · 1 comment
Labels
research Research is required to make progress

Comments

@arvoelke
Copy link
Owner

Both PadeDelay(theta-dt/2, ...) and LegendreDelay(theta-dt/2, ...) better-approximate the delay line of theta. But this is only significant/visible at large values of dt and q. This may have something to do fundamentally with the use of [q-1/q]-order approximants, which removes the passthrough.
@arvoelke arvoelke added the research Research is required to make progress label Mar 15, 2019
@arvoelke arvoelke changed the title Why is *Delay(theta-dt/2, ...)? Why is *Delay(theta-dt/2, ...) better? Mar 15, 2019
@arvoelke arvoelke mentioned this issue Mar 16, 2019
Open
@arvoelke
Copy link
Owner Author

May also be connected to the use of ZOH: dt/2 is the mid-point within the interval over which the step is held constant.

@arvoelke arvoelke mentioned this issue Aug 30, 2020
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
research Research is required to make progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arvoelke