Skip to content

Commit

Permalink
clarify 10.6 is about timing within a trial/word
Browse files Browse the repository at this point in the history
  • Loading branch information
yukomunakata authored Dec 11, 2024
1 parent 2b2b54b commit 1720349
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions ch10/dyslexia/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ You will see the activation flow through the network, and it should settle into

* Use the VCR `Time` buttons at the bottom right of the `Network` to review the settling dynamics over time.

* Continue to `Step Trial` through a few more words, paying particular attention to the timing of when the Phonological layer gets active relative to the Semantic one (you can always review to see this more clearly). Then, do `Run` to test the remainder of the inputs.
* Continue to `Step Trial` through a few more words, paying particular attention to the timing of when the Phonological layer gets active relative to the Semantic one within a trial (you can always review to see this more clearly). Then, do `Run` to test the remainder of the inputs.

> **Question 10.6:** Do you think the initial phonological activation is caused by the "direct" input via orthography or the "indirect" input via semantics? Did you see any cases where the initial phonological pattern is subsequently altered when the later input arrives? Provide an example word where this happened.
> **Question 10.6:** Do you think the initial phonological activation for each word is caused by the "direct" input via orthography or the "indirect" input via semantics? Did you see any cases where the initial phonological pattern is subsequently altered when the later input arrives? Provide an example word where this happened.
* Click on the `Test Trial Plot` tab to see a record of the network's performance on the full set of words. It should only make one "Other" error for the word "flag", which it pronounces as "flaw".

Expand Down

0 comments on commit 1720349

Please sign in to comment.