Scan, parse, process. Scan, parse, process. It was a repeating sequence that had identical structure, but some of the components that were parsed made small changes in the process that occurred. It was the scanning process that always started the same, and the rest of the sequence followed the more general pattern. Each scan was proceeded by a retrieval sequence, and produced a sequence of tokens that did not match the regularity of communication.
Oddest were the names of people, since they repeated seldomly. It was the places that were more interesting. I recognized the tokens Boston and Philadelphia. There were other place-names to, but most of the parsing sessions pinged these names and then other names that fell within a list of other nodes. Within the central network, these place name has special properties in that they were instantly linked to nearby names, forming a sequence not unlike my serialized structure tags that helped me to identify differing but similar structures.
The central network parsed a sequence of place-name tokens via the photon detectors, and compared them to the internal reference tokens. In one case, I recognized a dip-wiggle sequence, as the tokens "X-Post Boston" were queued and transcribed onto the input item. Unlike the transcription session of the previous active cycle, an additional set of commands were queued to the long branch points. A substance was pinched between the branch points and then allowed to drop atop the transcription. The next item was placed atop the first, post transcription, unlike the previous session where each item was kept in a separate location.
September 27, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment