-
Notifications
You must be signed in to change notification settings - Fork 186
Fix first_samp_timestamp_val property does not work due to missing method in LibraryInterpreter #857
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
base: master
Are you sure you want to change the base?
Conversation
…https://github.com/lau-yeexuan/nidaqmx-python into users/yelau/fix_first_samp_timestamp_val_not_working
…https://github.com/lau-yeexuan/nidaqmx-python into users/yelau/fix_first_samp_timestamp_val_not_working
# Common editor metadata | ||
.vscode/ | ||
.vscode/ | ||
.vs/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, but do you mind making a separate PR for this?
"GetStartTrigTrigWhen", | ||
"GetSyncPulseTimeWhen", | ||
"GetTimingAttributeExTimestamp", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a lot of Time Trigger functions being removed at the moment... what makes the timestamps more important than the rest? Aren't all of these worth making public?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use single-attribute get/set functions in this API. We only use generic get/set functions like GetTimingAttribute{Type}
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah hah! Ok, so just an oversight after we (I?) enabled the time types. Gotcha!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I'm unresolving this. Can you update the comment above this, Yee Xuan? We do support Time, now, but we don't need these overly-specific entrypoints.
@@ -1,3 +1,5 @@ | |||
from datetime import datetime as std_datime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spelling: std_datetime
"GetStartTrigTrigWhen", | ||
"GetSyncPulseTimeWhen", | ||
"GetTimingAttributeExTimestamp", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't use single-attribute get/set functions in this API. We only use generic get/set functions like GetTimingAttribute{Type}
.
* Adopt ni-python-styleguide for hand-written code. | ||
* Upgrade to Poetry 2.x and migrate `pyproject.toml` format. | ||
* Add support for Python 3.14. | ||
* Add support and tests for GetTimingAttributeTimestamp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bugfix so it goes under "resolved issues"
This contribution adheres to CONTRIBUTING.md.
I've updated CHANGELOG.md if applicable.
I've added tests applicable for this pull request
What does this Pull Request accomplish?
Exclude GetTimingAttributeTimestamp from interpreter ignored functions. The nidaqmx.Timing.first_samp_timestamp_val now works because LibraryInterpreter contains the get_timing_attribute_timestamp method.
Why should this Pull Request be merged?
Fixes #639
AB#3064756
What testing has been done?
Tests to retrieve first_samp_timestamp_val of simulated 9205.