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

Validation of Behavior Configuration Files #146

Open
jmdelahanty opened this issue Dec 20, 2022 · 0 comments
Open

Validation of Behavior Configuration Files #146

jmdelahanty opened this issue Dec 20, 2022 · 0 comments

Comments

@jmdelahanty
Copy link
Contributor

Given the #126 issue was most likely the result of accidentally using milliseconds instead of seconds, there should be something that can validate whether or not values in the file make sense.

On a related note, the use of different units of measurement (seconds vs milliseconds) within the same file is probably a bad move since that can definitely be confusing. The reason that was done was explicitly because, at the time, it felt confusing to have to convert to milliseconds for values that were always and would conceivably always be in seconds. For example, an ITI would be pretty odd if it was 1.530 seconds. On the other hand, a USDelay could conceivably be within millisecond ranges less than 1 second or some other interval.

I don't know what is best. But should be considered for any future projects/configurations of things...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant