...
| No Format |
|---|
http://www.example.com/d.zip |
If the alias translation results in a URL, then the previous algorithm is used to look up the conditions.
The value after translation need not be a URL or file. It can be a detector tag.
In the following case, the value of a will be resolved to d.
| No Format |
|---|
a: b b: c c: d |
The d name will still need to be resolved using the conditions lookup algorithm.
...
The alias file is stored at one or more of the following locationspaths.
- The LCSim work directory in the user home directory.
No Format ~/.lcsim/alias.properties - Within the lcsim.jar file at the following path.
No Format org/lcsim/detector/alias.properties - At a URL on the LCSim website.
No Format http://www.lcsim.org/detectors/alias.properties
Your custom aliases belong at
...
as this is likely the only place to which you'll have write access, and your own aliases should be kept separate from the common ones.
Conditions Lookup
Conditions information Once the recursive names are resolved, conditions information for a detector tag is retrieved as follows.
- If the tag value is a URL with a protocol of file:, the local file (zip format) or directory path specified is assumed to contain the conditions.
- If the name tag value is a zip file at a remote URL, an attempt is made to download the file from that location, unless the zip file is already in the local cache (~/.lcsim/cache). In this case, the local copy is used instead.
In the case of an alias, once the final detector name is determined, the algorithm searches for a directory or zip file with the same name as the tag in the following "canonical" locations:
...