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

How to represent cause and effects? #4

Closed
jiversen opened this issue Aug 16, 2019 · 4 comments
Closed

How to represent cause and effects? #4

jiversen opened this issue Aug 16, 2019 · 4 comments

Comments

@jiversen
Copy link

Hi, using HED for the first time seriously. A couple of questions about how to best encode some ideas. I didn't see anything in the existing tags, or maybe I missed it. Of course I can add whatever, but would like your feedback on the best way to do so.

I have stimulus events and want to include information about the cause of the event (e.g. a subject-specific action type). Something like /Attribute/Cause/xxxx

I have stimulus events that have variable meaning to the participant, and are expected or unexpected. /Attribute/Reaction/xxx or /Attribute/Meaning/xxx

@bigdelys
Copy link
Collaborator

I assume you have already read HED tagging strategy document.

In general, you should use Participant/Effect/ for things that mean something to the participant. You should search there to see if any combination of the existing tags could be used.

For expected, there is Participant/Effect/Cognitive/Expected and you could use Participant/Effect/Cognitive/Oddball for the unexpected one.

@bigdelys
Copy link
Collaborator

@touryan should I close the issue?

@VisLab
Copy link
Member

VisLab commented Sep 30, 2019 via email

@VisLab
Copy link
Member

VisLab commented Jan 4, 2021

This has been addressed in HED-3G with the Task-property/Task-effect-evidence section of the hierarchy.

@VisLab VisLab closed this as completed Jan 4, 2021
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

3 participants