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
Comments
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. |
@touryan should I close the issue? |
yes
…On Sun, Sep 29, 2019 at 9:11 PM Nima Bigdely-Shamlo < ***@***.***> wrote:
@touryan <https://github.com/touryan> should I close the issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4?email_source=notifications&email_token=AAJCJOWHISJLLBPU46O2MN3QMFN5JA5CNFSM4IMNPHOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD74GHPQ#issuecomment-536372158>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJCJOQLOCEIRDYQVSEWJQDQMFN5JANCNFSM4IMNPHOA>
.
|
This has been addressed in HED-3G with the Task-property/Task-effect-evidence section of the hierarchy. |
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
The text was updated successfully, but these errors were encountered: