-d mark items as deleted
-u "undelete" deleted items
-cc ccode set condition code
One situation in which logpoke can come to the rescue occurs when the
experimenter forgets to change the condition code while running. If it
is possible to determine which events comprise the erroneous entries in
the log file (using logexam), logpoke can be used to remedy the error.
Assume, for example, that events with item numbers (ordinal positions)
between 4627 and 4935 (inclusive) should have been under condition code
3. This can be fixed with:
logpoke logfile 4627 4935 -cc 3
Another common use of logpoke is to delete events which could not be deleted
while running. If one wished to delete items 33 through 254 (inclusive),
one could use logpoke thus:
logpoke logfile 33 254 -d
Note that the wise experimenter makes a backup copy of the logfile before
using logpoke, in case a slip of the finger occurs....