SET_AUTO_APPEND_DATABASE

This command is for the DATABASE_RETRIEVAL (TDB) module.

Enforce an automatic action that appends thermodynamic data from a chosen database regarding the system to the data you already have about the system from the current database (that is, the default database or the database last chosen with SWITCH_DATABASE or APPEND_DATABASE).

This is useful to simultaneously retrieve both thermodynamic and mobility data for a defined system when performing a DICTRA module simulation.

This command should be used before defining a system (with the commands DEFINE_ELEMENTS, DEFINE_SPECIES, or DEFINE_SYSTEM) and retrieving the data with the GET_DATA command from the primary switched database.

Syntax	set_auto_append_database
Prompt	Database name /XYZ/: <Additional database name>
Option	Additional database name The name of an existing database or a User database that corresponds to the automatically-appending database.

It works in a way that is similar to the APPEND_DATABASE<database-name> command sequence, but only the phases that are also available in the primary switched database are appended. There is no possibility to manually list, reject and/or restore any phase that is available in the appending database. When retrieving data with GET_DATA afterwards, all the phases that exist in the appending database but not in the primary switched database are automatically rejected. The prompt is kept as for the primary switched database, TDB_XYZ: (where XYZ stands for the name of the primary switched database) until the execution of GET_DATA.

Therefore, to selectively append more phases from a secondary database to a system that is defined and retrieved from a primary switched database, then APPEND_DATABASE and sequential commands (such as DATABASE_INFORMATION, DEFINE_SYSTEM, DEFINE_ELEMENT, DEFINE_SPECIES, LIST_SYSTEM, REJECT, RESTORE and GET_DATA) should be used instead, before this command.

Although it is impossible to manually list, reject and restore any phase from the appending database, the DATA module automatically ignores all the phases that do not exist in both the primary switched database and the appending database, and append the data for the phases (that are also available in the primary switched database) from the appending database, as informed on screen when executing GET_DATA afterwards.