Autoload

The "autoload" feature allows an alternative data input to scream in the form of GCF files.

It is not always possible to get a direct serial connection from an instrument to Scream, and the intermediate link may operate on files only. In this case, the autoload feature continuously checks a specified directory for GCF, and will load them as if they are a real-time data source.

Scream checks for files in "autoload" directory, which is a sub-directory from the location of the Scream executable. For example, if, on windows, Scream is located in "c:\program files\guralp systems\scream\", then the autoload directory would be "c:\program files\guralp systems\scream\autoload".

When Scream has loaded the data for a file found in this directory, it will delete the file. If you wish to keep the incoming data files, you should copy the files into the autoload directory from somewhere else. Note that Scream will record the data in the same way as any other data stream, so it should not be necessary to keep the temporary input files.

If a file cannot be deleted, Scream will remember to ignore the file for the rest of the 'session' (until terminated). It is not recommended to use this feature in normal operation - the 'remembered' list would grow indefinitely, and eventually use up all the computer's memory. This feature can, however, be used to pre-load a known set of data every time Scream starts up. To do this, simply mark the GCF files in the autoload directory as read-only. On startup, Scream will read them, attempt to delete them, fail, and ignore them for the rest of the session.

Examples of automated systems which could supply the files are FTP and email systems.