atlas_developer_directory

Files

• atlas_release - ATLAS release version, e.g. 10.0.1.
• jo.py - User job options.
• workarea - File specifying the developer's directory (see below).
• output_content - describes the output to be saved--see atlas_job_options.

The workarea can be in one of two forms: Either a full path to a local directory or a DIAL file URL (file:..., gsiftp:..., lfn:..., etc.). In the former case, the directory is the build area and is required to have a subdirectory InstallArea. In the latter case, the file must be a gzipped tar archive of such a directory.

The directory form will only work if the directory is accessible from the worker nodes, i.e. typically if the job is run at the same site where directory resides. Changes in that area are immediately visible to any running jobs and so typically the directory should not be modified while jobs are running or pending.

The URL form will typically be more broadly accessible and can be used when jobs are run a remote sites. The base name of the URL should be changed any time the directory is changed and the archive is recreated. Otherwise there may be uncertainty as to whether jobs are using the latest version or a cached copy of an earlier version.

Applications are allowed to rebuild (i.e. compile and link) the URL form but the present (January 2006) application atlasdev does not do this and so jobs can be expected to fail if the worker platform differs from that of the build machine.

The previous version of this interface has been renamed to atlas_developer_directory-jun05. Previous to January 2006, only the directory form of workarea was supported.