NAME

SYNOPSIS

DESCRIPTION

The chunk-name-format command specifies the format to be used when naming newly created chunks. The short format is:

<prefix>-<chunk-num>

The long format is:

<prefix>-<chunk-num>*d<dc>*<impasse-type>*<dc-chunk-num>

where:

<prefix>

is a user-definable prefix string; <prefix> defaults to "chunk" when unspecified by the user;

<chunk-num>

is 1 for the first chunk created, 2 for the second chunk created, and so on.

<dc>

is the number of the decision cycle in which the chunk was formed;

<impasse-type>

is [tie | conflict | cfailure | snochange | opnochange]

<dc-chunk-num>

is the number of the chunk within that specific decision cycle.

Notes:

1

The <prefix> string may not contain the '*' character. (The chunk-name-format command enforces this constraint.) The '*' character marks the ending of the number of the chunk, and chunk numbers are examined during production loading to allow a starting chunk number to be identified automatically.

2

<impasse-type> is the impasse of the lowest goal that has a result generated by this chunk.

OPTIONS

-short

When generating chunk names, use the short format. (See the DESCRIPTION section for details.)

-long

When generating chunk names, use the long format. (See the DESCRIPTION section for details.) This is the default format for Soar.

-prefix [<prefix>]

When generating chunk names, use the string <prefix>. <prefix> is initially "chunk". When <prefix> is unspecified, return the current <prefix>.

-count [<chunk-num>]

Set chunk counter to <chunk-num>. <chunk-num> cannot be reset to a number lower than the smallest chunk number of any loaded chunk. When <chunk-num> is unspecified, return the current <chunk-num>.

EXAMPLES

chunk-name-format -short -prefix "chunk" -count 0

To cause chunks to be named according to the "old" scheme.

chunk-name-format -prefix "new-chunk"

To begin naming a new sequence of chunks.

chunk-name-format -count 1000

To begin numbering a new sequence of chunks at 1000.

chunk-name-format -count

To retrieve the next <chunk-num> that will be used to form a chunk name.