Fixing issue with finding #208
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update Score from develop only pre-release changed
VisLab
reviewed
Jun 20, 2024
| *** Rare-prevalence <nowiki>{hedId=HED_0042232} [Less than 1 percent. (Source: Beniczky ea 2017, Table 6, Table 8).]</nowiki> | ||
| *** Occasional-prevalence <nowiki>{hedId=HED_0042233} [1 to 9 percent. (Source: Beniczky ea 2017, Table 6, Table 8)]</nowiki> | ||
| *** Frequent-prevalence <nowiki>{hedId=HED_0042234} [10 to 49 percent. (Source: Beniczky ea 2017, Table 6, Table 8)]</nowiki> | ||
| *** Abundant-prevalence <nowiki>{hedId=HED_0042235} [50 to 89 percent. (Source: Beniczky ea 2017, Table 6, Table 8)]</nowiki> | ||
| *** Continuous-prevalence <nowiki>{hedId=HED_0042236} [Greater than 90 percent. (Source: Beniczky ea 2017, Table 6, Table 8)]</nowiki> | ||
| * Posterior-dominant-rhythm-property <nowiki>{suggestedTag=Finding-frequency, suggestedTag=Finding-amplitude, hedId=HED_0042237} [Posterior dominant rhythm is the most often scored EEG feature in clinical practice. Therefore, there are specific terms that can be chosen for characterizing the PDR. Note that frequency and amplitude can be further described to be symmetrical or assymetrical. (Source: Beniczky ea 2017, Section 6, Table 4.)]</nowiki> | ||
| * Posterior-dominant-rhythm-property <nowiki>{suggestedTag=Feature-frequency, suggestedTag=Feature-amplitude, hedId=HED_0042237} [Posterior dominant rhythm is the most often scored EEG feature in clinical practice. Therefore, there are specific terms that can be chosen for characterizing the PDR. Note that frequency and amplitude can be further described to be symmetrical or assymetrical. (Source: Beniczky ea 2017, Section 6, Table 4.)]</nowiki> |
There was a problem hiding this comment.
Please check the assymetrical spelling as per codespell. Thx
VisLab
approved these changes
Jun 20, 2024
There was a problem hiding this comment.
This looks good. I think the Finding-property --> Feature-property was particularly important as it will allow those properties to be more transparently applied across the annotations.
There are commas in the epilogue that need to be removed. It might just be the line with the initials.
|
This is superceded by PR #220 which was merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replacing 'finding' with 'feature' in SCORE.