Skip to content

Commit

Permalink
clarify how to read tabs and errors
Browse files Browse the repository at this point in the history
  • Loading branch information
yukomunakata authored Dec 3, 2024
1 parent 19ae076 commit 2312728
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 @@ -38,9 +38,9 @@ You should see that only the direct pathway is activated, but likely it will sti

* Do `Run` to test all items, and look at the `Test Trial Plot` (you can click off all the bars and toggle each one on in turn to see them more clearly). You can see a sum of all the testing results in the `Test Epoch Plot` tab. This records a new row for each Test Run run, along with the lesion and proportion setting.

> **Question 10.7:** How many times did the network with only the direct pathway (SemanticsFull lesion) make a reading mistake overall (you can count the number of 1's in the various error columns, or look at the `Test Epoch Plot` sums, in the last row)? Notice that the network does not produce any blend outputs, indicating that the phonological output closely matched a known word.
> **Question 10.7:** How many times did the network with only the direct pathway (SemanticsFull lesion) make a reading mistake overall? (You can count the number of 1's in the `Test Trial Plot` if you are viewing only the 5 types of errors, or you can look at the `Test Epoch Plot` which shows the counts of different types of errors, and add those for the SemanticsFull Lesion case.) Notice that the network does not produce any blend outputs, indicating that the phonological output closely matched a known word.
Click on the `Test Trial` tab, which shows the table of testing results per trial. For each of the categorized errors (i.e., where `Vis` or `Other` is 1 -- ignore the SSE through Err columns which show raw error), compare the word the network produced (`Phon`) with the input word (`TrialName`). If the produced word is very similar orthographically (and phonologically) to the input word, this is called a *visual* error, because the error is based on the visual properties instead of the semantic properties of the word. The simulation automatically scores errors as visual if the input orthography and the response orthography (determined from the response phonology) overlap by two or more letters. You should see this reflected in the Vis column in the Table.
To understand the different types of errors, click on the `Test Trial` tab, which shows the table of testing results per trial. For each of the categorized errors (i.e., where `Vis` or `Other` is 1; the SSE through Err columns show raw error and can be ignored here), compare the word the network produced (under `Phon`) with the input word (under `TrialName`). If the produced word is very similar orthographically (and phonologically) to the input word, this is called a *visual* error, because the error is based on the visual properties instead of the semantic properties of the word. The simulation automatically scores errors as visual if the input orthography and the response orthography (determined from the response phonology) overlap by two or more letters. You should see this reflected in the Vis column in the Table.

> **Question 10.8:** How many of the semantically lesioned network's errors were visual, broken down by concrete and abstract, and overall?
Expand Down

0 comments on commit 2312728

Please sign in to comment.