[From Rick Marken (2018.02.12.2130 PDT)]
Bruce Abbott (2018.02.12.1100 EST)--
Â
BA: Although I have no doubt that one can control sequences and programs, I doubt that we do very much of either.Â
 RM: The demo is designed only to show what it means to control a sequence and a program perception. I think the question of how much we actually control such variables can be answered only by research. But I see that Erling made a pretty good observation about how much you were controlling for sequences in your post. I suspect people control sequence perceptions far more than you think!
BA: To control a sequence implies (a) knowing what the sequence is, (b) recognizing deviations from the sequence, and (c) having a means of correcting the deviations.
RM: Exactly. You have to be able to perceive that a sequence is in progress; you have to have a reference for the desired state of the sequence; the reference, of course, defines what constitutes a deviation from the sequence. And you must be able to act to keep the sequence perception in the desired state, protected from disturbances which would "push" the sequence away from its reference state. In the demo, the means (actions) that keep the sequence in the desired state is very simple; a press of the space bar.
Â
 BA: At the very least, the sequence reference specifies what to perceive at any given step in the sequence;
RM: This is not how it's conceived of in PCT. I recommend (to everyone) that they read the section of B:CP on control of sequences (pp. 139-146 in the 2nd edition). On p. 139 Bill notes that, according to the model, "the perceptual signal emitted by a fifth order [sequence perception] input function will not be a sequence, but will stand for the presence of a particular sequence" and perceptual signal "...must be a one-dimensional signal if unambiguous control is to be achieved...". This means that, as in all control systems in the PCT model, the reference signal for a sequence perception is a one-dimensional signal that that specifies the magnitude of the one-dimensional perceptual signal whose magnitude indicates the degree to which a particular sequence is occurring.Â
Â
BA: actions are initiated to carry out the step, resulting in a perception that either matches or does not match the reference for control of the perception associated with that step. The sequence-reference sets the reference for the next step, and so on until all steps in the sequence have been carried out.
RM: This is not the way a sequence control system works in PCT. But that's irrelevant to my demo, which demonstrates the fact of control of a sequence and the fact that what is controlled when you control a sequence is not a sequences of actions that produce the sequence but a perception of the sequence that is a consequence of those actions (which are not necessarily a sequence, as in the demo)  combined (as usual) with effects produced by the environment (disturbances); in the demo these disturbances are the program statements that produce the display of the shapes of different sizes and colors. >
Â
BA: For example, typing the word “catâ€? entails having a reference for the sequence c – a – t. To type †“cat,â€? the sequence controller sets a reference for a lower-level controller to perceive typing the “c,â€? then “a,â€? then “t.â€? Typing the “câ€? involves several levels of control that may themselves involve sequence-control, i.e., placing the fingers on the keyboard, moving a finger over the “câ€? key, then pressing and releasing the key, and then (for a touch typist) moving that finger back to the “homeâ€? position on the keyboard. These hand and finger movements are carried out by even lower level controllers.
Â
BA: The sequence controller may not wait for tactile or visual feedback to confirm that the “c� has been typed before initiating the typing of the “a.�  Once a mistake has been made, by the time the sequence controller receives the feedback it is too late for on-the-fly correction. I’m a fairly good touch typist but when I make a mistake I’ve usually typed a number of additional letters before becoming aware of it (the tactile perception is wrong). Error correction in sequence control usually involves interrupting the sequence to make the correction before continuing, and sometimes involves starting the sequence over again.
RM: This is all correct. I think it would be great if you could create a system that controls a perception of sequence in this way. Â >
Â
BA: In the example just given, the sequence to be produced is known in advance and one can compare the perception of that sequence to its reference sequence. As in typing or playing music, there is a known pattern to be reproduced. (The pattern may include more than just the sequence of letters or notes, but also patterned variations in the speeds of execution, intensity of the perceptions, etc.) We can learn to control sequences. But I believe that most examples in which a sequence of activities is carried out do not involve pre-specified sequence references and therefore are not examples of sequence control. The same may be said of program control.
RM: That may be. It's certainly easy to find examples of behaviors that look like intended (controlled) sequences or programs that are not. For example, a person will move the mouse in a back and forth sequence of motions to protect the cursor from a sine wave disturbance in a compensatory tracking task; so the person is producing a sequence of movements but it is not produced intentionally (controlled). And compensatory tracking itself can look like a program of actions of the form " if cursor moving left, move mouse to right; if cursor moving right move mouse left; if cursor is stationary, don't move mouse". These are more examples of behavioral illusions, where the side effects of control are seen as emitted (caused) outputs; that is, they are seen as what the person is "doing", when they are not.>
Â
BA: In program control, there is a prespecified “programâ€? to be carried out – a program rreference that specifies what is to be done at each step,
RM: No, the reference for a program specifies what is to be perceived; behavior is the control of perception, remember. My demo shows what it means to control a program perception, without having to do anything other than to perceive the fact that the program is "happening"; when the program perception stops happening all you have to do is press the bar to get it to keep happening again. The maintenance of programs in real life typically requires a great deal more than just pressing a bar; but that's why, in real life, it often looks like a program is a process of emitting a contingent sequence of actions-- another behavioral illusion. My demo pares things down so that it's easier to see that carrying out a program is the control of input (perception) not the emission of output.
BA: including alternatives whose execution depends on current perceptions: If this perception, then do that, else do this other thing. Certainly we can learn what should be perceived at each step, what alternatives if any are available at that step, and whether what should be perceived is being perceived. But I’m doubtful that we do much of this.Â
RM:Â I don't know why you think this. We even have a phase we use when we see that a program is not being controlled correctly: "get with the program". I think the control of program perceptions is very common in people and other creatures; but, again, how prevalent it is is a matter for research. I'm just trying to make sure that the PCT concept of sequential and programmatic behavior as the control of sequence and program perceptions, respectively, is understood.
BA: Instead, we have a goal to achieve and string together activities on the fly that (we hope) will move us closer to achieving that goal, based on prior experience and what options appear to be available to us at the time. After we have achieved the goal and look back on how it was accomplished, it may appear that we were executing a pre-planned program, but most of the time we just did what occurred to us at the time, step by step.Â
Â
BA: Most of what we do is improvisation, not programmed execution.
RM: All of what we do is control! Some of what we do is building control systems through trial and error, a process called reorganization (which can look like "improvisation"). None of what people do is programed execution; it's control of perceptions, some of which are program perceptions.
 >
 BA: Comments?
RM: You got 'em. Â
Best
···
Â
Bruce A.Â
--
Richard S. MarkenÂ
"Perfection is achieved not when you have nothing more to add, but when you
have nothing left to take away.�
                --Antoine de Saint-Exupery