OpenLLM-France/wikimedia huggingface dataset:
# Speech-Language Pathology/Stuttering/Practice Word Lists

These 357 words include every combination of consonant and vowel in the English language.

#### Word List 1

able
baby
chainsaw
dateline
famous
gatepost
halo
jaywalk
cable
label
mailbag
nadir
pacer
rabies
saber
shapeless
table
they
vacant
weightless
whale
zany

#### Word List 2

abbey (a monastery)
baboon
dancer
famine
gadget
hacksaw
jasmine
cabin
ladder
macro
knapsack
package
rabbit
saddle
shadow
tactile
than
thankful
vanish
wacky

#### Word List 3

achoo
baa
cha-cha
father
hah
calf
launch
macho
pasta

#### Word List 4

alarm
balloon
macaw
patrol
salon
taboo

#### Word List 5

eager
beachfront
cheap
dealer
feature
geese
healer
genius
kiwi
legion
meager
kneecap
peaceful
react
cease-fire
sheepdog
teak
thee
theme
V-eight
weasel
wheel
yeast
zeal

#### Word List 6

any
bedtime
checkbook
dentist
felon
guest
health
gentle
kettle
leather
meadow
nephew
peck
redwood
self-talk
shepherd
ten-speed
them
theft
vent
wealthy
whether
yell
zest

#### Word List 7

aisle
byte
child
diamond
fiber
guide
height
jive
cayenne
lion
micro
knife
pie
rhino
cyclist
shiner
thyme
thy
thigh
vibrant
wildcat
whitefish
yipe
xylan (plant substance)

#### Word List 8

image
bemoan
chipmunk
divide
fishbowl
gift-wrap
hitchhike
ginger
kibbutz
lily
midcourse
nimble
picture
rebel
system
shiftless
ticket
this
thicket
vicar
wizard
whimsy
yip
zigzag

#### Word List 9

oaken
boastful
choke
domain
focus
ghost
hoagie (sandwich)
joke
coleslaw
locust
motion
noble
pollster
romance
soapstone
chauffer
toaster
those
thole (endure)
vogue
woven
yolk
zonal

#### Word List 10

otter
bobcat
chocolate
docile
foggy
goblin
hobby
jogger
cobbler
lobster
model
knockout
pocket
robin
soccer
shocker
toddler
volley
waffle
whopper
yacht

#### Word List 11

alder
bald
chalk
daughter
fallen
gauntlet
hallmark
jaunt
caller
laundry
mossy
gnaw
pause
raucous
salted
shawl
talking
thoughtful
vault
walker
yawn

#### Word List 12

oil
boil
choice
doily (small napkin)
foible
goiter
hoist
join
coin
loin
moist
noise
poignant
royal
soil
toil
voice
yoicks (cry to encourage foxhounds)

#### Word List 13

ouster
bough
chow
downbeat (conductor's downstroke on first beat of a measure)
foul
gauss (measure of magnetism)
hound
jounce (bounce, jolt)
couch
loud
mountain
noun
pouch
round
sow
shout
tout (extravagant praise)
thou
thousand
vouch
wound (as in string, not as in injury)
yowl (cry of distress)
zounds (a mild oath)

#### Word List 14

oops (mild surprise or apology)
boomer
chew
deuce
food
goober (peanut)
hoop
juice
coolant
lunar
moon
nougat
poodle
rupee
sewage
shoe
tomb
woo
whoosh
U-boat
zoo

#### Word List 15

butte
deuce
feudal
gewgaw (showy trifle, bauble)
hewn
coupon
mule
neutral
pewter
tuba
view
whew

#### Word List 16

oomph
butcher
football
good
hoof
cookbook
lookout
nook
pudding
roof
soot
shook
took
wolf
whoops

#### Word List 17

onion
bubble
chubby
doesn't
fungus
govern
hovel
judge
color
love
money
knuckle
pump
rough
someday
shutter
touchdown
thus
thumbnail
vulgar
once
what
youngster
* Next chapter: Recommended Books
* Back to Table of Contents
# Programming with ooc/Installing

ooc code is compiled to C using rock
The rock github page contains a list of high-level dependencies and more detail for UNIX and Windows.

## Installing in Ubuntu Linux
#### Boehm GC (optional)

1. Download the Boehm GC from here.
2. Configure, compile and install

#### rock

3. Download and compile rock
The first time you compile ooc source with rock will take a little longer than subsequent builds because of the nature of the compilation to C99 followed by compilation of C process. In the .libs directory - that is created wherever you call rock - the compiler will produce not only C code for your ooc but also produce the C code for the language constructs used by your code under .libs/ooc/sdk. Future compiles (especially those that do not use additional language features or parts of the sdk) will be significantly more spritely. Enjoy!
# Project+

This textbook is intended to teach fundamental project management skills for the Project+ certification offered by CompTIA, the Computing Technology Industry Association, a non-profit, vendor-neutral trade association. Project+ shows that one has the knowledge needed to manage projects. It provides validation of fundamental project management skills. The certification covers the life cycle of a project from initiation and planning through execution, acceptance, support and closure.
There are no prerequisites, and candidates are not required to submit an application or complete additional hours of continuing education.

## Contents

Project+ divides project management into the following distinct phases:
* Initiating
* Planning
* Executing
* Controlling and Monitoring
* Closing

## Further reading

* Project Management
# Programming with ooc/Interfaces
## Introduction

One of the strong points of ooc is the descriptive way C libraries can be interfaced with. These interfaces can be as low-level as a list of extern functions or 'high-level' by wrapping function calls and data within ooc classes or complex covers.

## Building an interface

In the discussion that follows we are going to build up a basic interface to the libYAML (http://pyyaml.org/wiki/LibYAML) library. There is an existing interface by nddrylliog here which we will use as a reference too.
Most of our work will involve reading the library header file (http://svn.pyyaml.org/libyaml/branches/stable/include/yaml.h) and deciding how we intend to use the contents therein. To interface with the C library we will need it to be present on our system. We will also want to create a file hierarchy for our new interface.

### Setup

In this section we will make the C library accessible to our new ooc interface and create the file hierarchy for that interface.

#### libYAML
##### System-wide install

Installing (making available) the C library is system dependent. The following steps will work for users of Ubuntu:

##### Local install

Another option (that is really beyond the scope of this book) is to keep libraries within a user account and control the paths where the C compiler searches for libraries and headers. An example setup that uses ~/local as a prefix could be:
To make use of this kind of setup you will need to set the relevant environment variables in the relevant user rc file:

#### ooc

To make use of libraries in ooc the convention is to set the environment variable OOC_LIBS. Inkeeping with the local setup discussed above this can be a path accessible only to this user:
Since we are building an ooc library ourselves the file hierarchy belongs inside OOC_LIBS. More details on the structure of a library and the associated use file are available in the ooc documentation. For our purposes we will have something like :

### Interfacing

The first step is to create a use file that describes how our ooc library is laid out and what setting it needs to compile to ooc programs that want to use it. A basic setup is the following :
For the purposes of this discussion we are going to do all of the interface creation inside source/YAML.ooc in our file hierarchy above. Because we want this file to include the settings we established above we include the line
at the top of this file.

#### Constants

Wonder of wonders libYAML does not seem to define any constants! But just-in-case the library you are interfacing with does include constants your interfaces should look something like this (C code above in bold, ooc below):

#### Functions

Interfacing with C header means coming into contact with many of the quirky parts of the C pre-processor and the tricks developers use to cross platforms and programming paradigms. libYAML uses the macro YAML_DECLARE to provide interoperability with WIN32. For our purposes we will simply expand: #define YAML_DECLARE(type) type which makes the following declarations equivalent:
# Project+/Closing
## Project Close Out Phase
### Closing

* process of gaining formal acceptance for the results of a project or phase.
* bringing project or phase to an orderly end.
* archiving of project information and post-project review.

### Output

* project archives
* formal acceptance documentation
* project review
* team member evaluations
* lessons learned report = last deliverable

### Formal Acceptance Of The Project By The Customers

* first step in close out phase
* a goals of the close out phase?
* formal acceptance documentation should be prepared
* PM should document customer acceptance

### Project Review

* necessary task in preparation of the Close Out phase
* asses and evaluate each phases of the project
* asses and evaluate the overall project performance
* a way to learn from the experience and continuously improve project performance

### Project Archives

* leave clear and complete documentation of the project

### Lessons Learned Report

* PM may need to study from previous projects

### Project Audit

* formal review of project progress and results
* did project achieve benefits as planned
* was work accomplished according to plan
# Scriptapedia/Parameterized Relationship between Two Variables (VISCONS)
## {Name of Script}

{Brief description of context and purpose of script}

### Status:

{Status of script, e.g., best practice, promising practice, or under development}

### Primary nature of group task:

{Divergent, Convergent, Presentation, Evaluation}

### Time:

Preparation time: {time to prepare} minutes Time required during session: {time required during the session} minutes Follow-up time: {time required for follow-up work} minutes

### Materials needed:

* {first item needed}
* {second item needed}
* {third item needed}

### Inputs:

{Inputs required from other scripts}

### Outputs:

{outputs produced by this script}

### Roles:

* {first role needed}
* {second role needed}
* {third role needed}

### Steps:

* Step 1
* Step 2
** Substep 1
** Substep 2
* Step 3

### Evaluation Criteria:

{How would one know that this the script is working?}

### Authors:

{Who created the script, e.g., the small group exercise (not the person who documented the script).}}

### History:

{What is the history of the script?}

### Revisions:

{What revisions have made to the script over the years}

### References:

{Full references to literature cited in the documentation of the literature}

### Notes:

{Any notes on variations or tips for using the script}
# Scriptapedia/Preface

The idea of documenting group model building (GMB) scripts started Andersen and Richardson's (1997) call to make group model building more science than art through better documentation and sharing of scripts.

## References

Richardson, G.P & Andersen, D.F. 1997. Scripts for Group Model Building. System Dynamics Review, 13(2).
# Scriptapedia/Parameterized Relationship between Two Variables
## <Name of Script>

<Brief description of context and purpose of script>

### Status:

<Status of script, e.g., best practice, promising practice, or under development>

### Primary nature of group task:

<Divergent, Convergent, Presentation, Evaluation>

### Time:

Preparation time: <time to prepare> minutes Time required during session: <time required during the session> minutes Follow-up time: <time required for follow-up work> minutes

### Materials needed:

* <first item needed>
* <second item needed>
* <third item needed>

### Inputs:

<Inputs required from other scripts>

### Outputs:

<outputs produced by this script>

### Roles:

* <first role needed>
* <second role needed>
* <third role needed>

### Steps:

* Step 1
* Step 2
** Substep 1
** Substep 2
* Step 3

### Evaluation Criteria:

<How would one know that this the script is working?>

### Authors:

<Who created the script, e.g., the small group exercise (not the person who documented the script).>

### History:

<What is the history of the script?>

### Revisions:

<What revisions have made to the script over the years>

### References:

<Full references to literature cited in the documentation of the literature>

### Notes:

<Any notes on variations or tips for using the script>
# Scriptapedia/Presenting the Reference Mode
## Presenting the Reference Mode

The purpose of this script is to propose and develop consensus on a reference mode after dynamics have been described by participants.

### Status:

Best practice

### Primary nature of group task:

Presentation

### Time:

Preparation time: 10 minutes
Time required during session: 30 minutes
Follow-up time: 0 minutes

### Materials needed:

White or black board or flip chart with markers (or chalk) for drawing one or more reference modes

### Inputs:

Dynamics identified from previous activity (e.g., graphs over time)

### Outputs:

Reference modes

### Roles:

* Modeler to introduce the concept of a reference mode and propose a reference mode for discussion
* Facilitator to manage the conversation

### Steps:

* Prior to the exercise (e.g., during a break), the team meets to review the dynamics that have been identified during the previous session, and then identifies one more more dynamics as candidates for reference modes.
* The modeler then introduces the reference mode and presents one or more behavior over time graphs as the reference modes.
* The facilitator then asks participants if this is correct or we should be focusing on something else.
* As participants clarify their understanding of what a reference mode is and what is should be, the modeler redraws the reference mode.
* The facilitator ends the exercise when participants have reached consensus.

### Evaluation Criteria:

* A reference mode has been identified.
* There is an initial consensus on what the dynamic problem is.

### Authors:

David Andersen and George Richardson

### History:

Identifying a reference mode is a common activity. This script was based on a version of identifying a reference mode in Luna-Reyes et al. 2006.

### Revisions:

None

### References:

Luna-Reyes, L. F., Martinez-Moyano, I. J., Pardo, T. A., Cresswell, A. M., Andersen, D. F., & Richardson, G. P. (2006). Anatomy of a group model-building intervention: Building dynamic theory from case study research. System Dynamics Review, 22(4), 291-320.

### Notes:

This exercise may reproduce or reinforce group power dynamics. As a way to reduce that possibility, taking time to allow all participants to speak can be a platform for open communication between individuals and subgroups.
If the group is not coming to a consensus you can either extend the session to be longer or wrap up the session summarizing the key ideas participants have been discussing, making sure as a facilitator that everyone feels included. The facilitator and modeler can be the best reference mode to move forward with based on what was discussed on the group model building session or take the ideas back to the core modeling team and may determine to have another session with participants, depending on the problem.
# Scriptapedia/Reflector Feedback
## Reflector Feedback

This script is used to summarize dynamic insights and stories told by the group. It also allows for clarification of fuzzy ideas and helps capture additional information about structure that is needed to formulate the model.

### Status:

Best practices

### Primary nature of group task:

Convergent

### Time

Preparation time: 20 minutes
Time required during session: 15 minutes
Follow-up time: 0 minutes

### Materials

* Chalk/whiteboard markers
* Flip chart/whiteboard
* Data projector

### Inputs:

* Prioritized list of variables
* Behavior over time graphs (reference modes)

### Outputs:

None

### Roles

* Reflector with expertise in system dynamics

### Steps

* The reflector presents a series of diagrams created during the group discussion.
** Diagrams will either be drawn on a whiteboard or modeled in Vensim.
* The diagram is presented in the simplest form. More complex versions with additional variables are progressively revealed on top of the first diagram. As the reflector reveals each iteration of the model, he/she presents the story behind the diagram.
* The reflector may add variables to the diagram at the group’s request.

### Evaluation Criteria:

* Unclear ideas have been clarified
* The group has a better sense of the variables and causal relations needed to complete a model

### Author

George Richardson

### History

First documented by Annaliese Calhoun in 2010; based on Luna-Reyes et al. (2006).

### Revisions

None

### References

Luna-Reyes, L. F., Martinez-Moyano, I. J., Pardo, T. A., Cresswell, A. M., Andersen, D. F., & Richardson, G. P. (2006). Anatomy of a group model-building intervention: Building dynamic theory from case study research. System Dynamics Review, 22(4), 291-320.

### Notes

Although the script is designed to be a presentation, listening to the group and using the pen and the eraser continue to be important during the process.
# Scriptapedia/Readings in System Dynamics
## Introductory Texts on System Dynamics
### Books

* Hovmand, P. (2014). Community Based System Dynamics. New York, NY: Springer.
* Meadows, D. H., & Wright, D. (2008). Thinking in systems: A primer. White River Junction, Vt: Chelsea Green Pub.
* Sterman, J. D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. Irwin McGraw-Hill.
* Morecroft, J. D. W. (2015). Strategic Modeling and Business Dynamics: A Feedback Systems Approach. John Wiley and Sons.
* Ford, Andrew. (1999). Modeling the Environment: An Introduction to System Dynamics Modeling of Environmental Systems. Island Press.
* Maani, K. E., & Robert Y. C. (2000). Systems Thinking and Modeling: Understanding Change and Complexity. Available from Pegasus Communications
* Warren, K. (2002). Competitive Strategy Dynamics. John Wiley and Sons.

### Classic texts

* Forrester, J. W. (1961). Industrial Dynamics. Massachusetts Institute of Technology Press.
* Richardson, G. P., & Pugh III, A. I. (1981). Introduction to system dynamics modeling with DYNAMO. Productivity Press Inc.
* Roberts, N., Andersen, D. F., Deal, R. M., Garet, M. S., & Shaffer, W. A. (1983). Introduction to computer simulation: the system dynamics approach. Addison-Wesley Publishing Company.

## Journal Articles

* Andersen, D. F., Richardson, G. P., & Vennix, J. A. (1997). Group model building: adding more science to the craft.
* Black, L. J. (2016). From Situated Action to Model Abstraction—and Back Again. http://www.systemdynamics.org/conferences/2016/proceed/papers/P1451.pdf
* Meadows, D. (1999). Leverage points. Places to Intervene in a System.
* Richardson, G. P. (1994). Systems thinkers, systems thinking. System Dynamics Review, 10(2‐3), 95-99.
* Richardson, G. P. (2011). Reflections on the foundations of system dynamics. System Dynamics Review, 27(3), 219-243.
Category: Scriptapedia
# The Devonshire Manuscript/Deme as ye list vppon goode cause

* ←Wyll ye se / What Wonderous love hathe wrought || width="200" align="right" | I am as I am and so wil I be→
* The Devonshire Manuscript facsimile 84v
f. [84v] 1 Deme as ye list vppon goode cause 2 I maye and think of this or that 3 but what or whye my self best knowes 4 wherebye I think and fere not 5 but thereunto I maye well think 6 the doubtefull sentence of this clause 7 I wolde yt ware not as I think 8 I wolde I thought yt ware not 9 ffor if I thought yt ware not soo. 10 though yt ware so yt grevid me not 11 vnto my thought yt ware as tho 12 I harkenid tho I here not 13 at that I see . I cannot wynk 14 nor from{_o} mye thought so let it goo. 15 I wolde yt ware not as I think 16 I wolde I thought yt ware not 17 Lo how my thought might make me free 18 of that perch$^a$unce yt nedith$^1$ nott 19 perchaunce no doubte the drede I see 20 I shrink at that I bere not 21 but in my harte this wo$^r$de shall sink 22 vnto the proffe maye better bee 23 I wolde yt ware not & amp; as I think 24 I wolde I thought yt ware not 25 Yf yt be not shewe no cause whye 26 I shulde so think / than care I not 27 for I shall soo myself applie / 28 to bee that I apere not 29 that is as one that[[The Devonshire Manuscript/Appendix_I:_Paleographic_Features|{{th}+t+}]] shall not shrink 30 to be yo$^r$ owne vntill I dye / 31 and if yt be not as I think 32 lyke wyse to think yt is not fs

## Notes & Glosses

1. In "nedith," h overwrites t.

## Commentary

Attributed to Sir Thomas Wyatt, this poem was entered by H8. Rebholz notes, however, that the poem contains no external evidence for this attribution. The speaker engages in a psychological reflection on the nature of perception and reality. “I am as I am and so wil I be” (85r), located on the next page, expresses a similar theme.

#### Works Cited

* ↑ R.A. Rebholz, ed. Sir Thomas Wyatt: The Complete Poems. London: Penguin, 1978. 247-48.
* ↑ ibid., 509.
# The Devonshire Manuscript/Detailed Hand List Hand 12

Detailed Hand Lists :
| Hand 1 | Hand 7 | Hand 13 |
| Hand 1.1 | Hand 7.1 | Hand MS |
| Hand 2 | Hand 8 | Hand MD |
| Hand 3 | Hand 9 | Hand MF |
| Hand 4 | Hand 10 | Hand TH1 |
| Hand 5 | Hand 11 | Hand TH2 |
| Hand 6 | Hand 12 | Hand HS |

## Hand Tables
### Miniscules

* a
* b
* c
* d
* e
* f
* g
* h
* k
* m
* n
* o
* r
* s
* t
* u
* w
* y

### Digraphs, Brevigraphs, Symbols, and Extended Examples

* ff
* fr
* ll
* oo
* st
* th
# The Devonshire Manuscript/Detailed Hand List Hand 4

Detailed Hand Lists :
| Hand 1 | Hand 7 | Hand 13 |
| Hand 1.1 | Hand 7.1 | Hand MS |
| Hand 2 | Hand 8 | Hand MD |
| Hand 3 | Hand 9 | Hand MF |
| Hand 4 | Hand 10 | Hand TH1 |
| Hand 5 | Hand 11 | Hand TH2 |
| Hand 6 | Hand 12 | Hand HS |

## Hand Tables
### Majiscules

* A
* B
* E
* F
* H
* I
* M
* O
* R
* S
* T
* V
* W
* Y

### Miniscules

* a
* b
* c
* d
* e
* f
* g
* h
* i
* k
* l
* m
* n
* o
* p
* q
* r
* s
* t
* u
* v
* w
* y

### Digraphs, Brevigraphs, Symbols, and Extended Examples

* cc
* ch
* de
* des
* er
* es
* eu+er
* ff
* ke
* kes
* ll
* nn
* or
* pre
* re
* ser
* sh
* sl
* ss
* st
* th
* that
* the
* there
* this
* tt
* uer
* Wh
* with
* Yff
* your
# The Devonshire Manuscript/Detailed Hand List Hand 11

Detailed Hand Lists :
| Hand 1 | Hand 7 | Hand 13 |
| Hand 1.1 | Hand 7.1 | Hand MS |
| Hand 2 | Hand 8 | Hand MD |
| Hand 3 | Hand 9 | Hand MF |
| Hand 4 | Hand 10 | Hand TH1 |
| Hand 5 | Hand 11 | Hand TH2 |
| Hand 6 | Hand 12 | Hand HS |

## Hand Tables
### Majiscules

* H
* I
* S
* Y

### Miniscules

* a
* b
* c
* d
* e
* g
* h
* i
* l
* m
* n
* o
* p
* n
* s
* t
* u
* w
* y

### Digraphs, Brevigraphs, Symbols, and Extended Examples

* es
* ff
* ll
* ons
* re
* ss
* th
* that
* tt
* with
# The Devonshire Manuscript/Detailed Hand List Hand 3

Detailed Hand Lists :
| Hand 1 | Hand 7 | Hand 13 |
| Hand 1.1 | Hand 7.1 | Hand MS |
| Hand 2 | Hand 8 | Hand MD |
| Hand 3 | Hand 9 | Hand MF |
| Hand 4 | Hand 10 | Hand TH1 |
| Hand 5 | Hand 11 | Hand TH2 |
| Hand 6 | Hand 12 | Hand HS |

## Hand Tables
### Majiscules

* A
* E
* H
* I
* L
* M
* R
* S
* T
* W

### Miniscules

* a
* b
* c
* d
* e
* f
* g
* h
* i
* k
* l
* m
* n
* o
* p
* q
* r
* s
* t
* u
* v
* w
* y

### Digraphs, Brevigraphs, Symbols, and Extended Examples

* burning
* ff
* fy
* ll
* n macron
* oo
* pp
* quod
* re
* st
* th
* thou
* tt
* with
# The Devonshire Manuscript/Detailed Hand List Hand 1

Detailed Hand Lists :
| Hand 1 | Hand 7 | Hand 13 |
| Hand 1.1 | Hand 7.1 | Hand MS |
| Hand 2 | Hand 8 | Hand MD |
| Hand 3 | Hand 9 | Hand MF |
| Hand 4 | Hand 10 | Hand TH1 |
| Hand 5 | Hand 11 | Hand TH2 |
| Hand 6 | Hand 12 | Hand HS |

## Hand Tables
### Majiscules

* A
* B
* D
* I
* M
* O
* T
* W

### Miniscules

* a
* b
* c
* d
* e
* f
* g
* h
* i
* k
* l
* m
* n
* o
* p
* q
* r
* s
* t
* u
* v
* w
* x
* y

### Digraphs, Brevigraphs, Symbols, and Extended Examples

* cc
* ces
* ff
* ll
* ne
* re
* redresse
* rr
* sh
* ss
* st
* tt
* ty
* with
* your
* yv
# The Devonshire Manuscript/Detailed Hand List Hand 10

Detailed Hand Lists :
| Hand 1 | Hand 7 | Hand 13 |
| Hand 1.1 | Hand 7.1 | Hand MS |
| Hand 2 | Hand 8 | Hand MD |
| Hand 3 | Hand 9 | Hand MF |
| Hand 4 | Hand 10 | Hand TH1 |
| Hand 5 | Hand 11 | Hand TH2 |
| Hand 6 | Hand 12 | Hand HS |

## Hand Tables
### Majiscules

* B
* H
* I
* M
* N
* R
* S

### Miniscules

* a
* b
* d
* e
* f
* g
* h
* i
* k
* l
* m
* n
* o
* p
* r
* s
* t
* u
* v
* w
* y

### Digraphs, Brevigraphs, Symbols, and Extended Examples

* ll
* per
* sh
* th