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

Should "n/a" be allowed in the onset column of events.tsv #1943

Open
VisLab opened this issue Oct 4, 2024 · 0 comments
Open

Should "n/a" be allowed in the onset column of events.tsv #1943

VisLab opened this issue Oct 4, 2024 · 0 comments

Comments

@VisLab
Copy link
Member

VisLab commented Oct 4, 2024

The current description of onset in Task events says that the onset column may have 0, positive and negative values. It does not explicitly say it does not allow "n/a", although I believe that somewhere in the past that was in the spec. The current description of duration explicitly says that it can be "n/a" and what that means.

My question is --- is "n/a" really allowed in the onset column. If so, what does it mean and how are tools required to handle it?

This should be made explicit in the specification and in the schema.

This issue is related to issue #1938 and to issue hed-standard/hed-python#1026.

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