Two lists of configurations are maintained by fmstudio: the 'Plan config' list and the 'Database config' list.
The latter list ('Database config') is meant as a repository of useful configurations. It is typically stored in a file with the same name base as the scene file but ending in '.conf' instead of '.iv'. It is read right after starting the fmstudio and written back to the same file when the program exits normally. (Use the '-db' option, see , to specify a different file name.)
In contrast, 'Plan config' contains a task, and possibly further configurations that define an entire plan (that is, a solved task). (Use a sequence of indices at the command line, see , to fill this list at start-up of fmstudio.) A 'task' is defined as an arbitrary sequence of collision-free, so-called 'key-configurations'. A 'plan' contains additional (non-key) configurations such that connecting two successive configurations by straight line segments yields a collision-free path. The planner tries to insert proper non-key configurations into a task to turn it into a plan.
Thus, 'Database config' is a conglomeration, most likely without significant order of the configurations, and is automatically saved at proper exit of fmstudio. In contrast, the order of the configurations in 'Plan config' does matter. 'Plan config' can be seen as something like the 'working memory' of fmstudio and needs to be saved explicitly if desired (see below). Both lists can be edited by the user. To this end, each list has a pointer associated with it that indicates the current position, similarly to a cursor position, in its list. The status output in the shell window shows the sizes ('plan-total' and 'db-total') of both lists and the respective current 'cursor' positions 'plan-curr' and 'db-curr':
Plan config : <plan-curr>/<plan-total> * - not planned yet Database config : <db-curr>/<db-total> (database file: <filename>)
An asterisk '*' in the 'Plan config' line shows if the configuration at the 'plan-curr' position in 'Plan config' is a key configuration (only key-configurations are considered when the planner is run; this allows re-starting the planner several times in a row on the same task). The key status flag can be changed by the user (see below). Furthermore, the 'Plan config' line indicates the planner status.
Similarly, the 'Database config' line shows the current position in the 'Database config' list and the total number of stored configurations. It also shows the name of the file from which the database was read at program start and to which it will be written back when the program exits normally.
The following keyboard commands can be used to edit and perform other operations on these two lists: