wiki:DC3SymLinkStagePolicyDesign
Last modified 10 years ago Last modified on 04/03/2009 12:08:23 PM

DC3 SymLinkStage Policy Design

updated: Feb 11, 2009

SymLinkStage Policy File Components

  1. AdditionalData: "visitId=triggerIpdpEvent.visitid"
    • type: string array
    • description: allows clipboard values to be given names to be used as parameters in pathnames. Form is <name>=<clipboardKey>.
  2. RunMode:
    • type: string
    • allowed values: "preprocess", "process", "postprocess"
    • description: specifies when the symbolic links should be created.
  3. Links
    • type: policy
    • description: symbolic links to create. Define one Links Policy for each symbolic link you wish to create.
    • components:
      1. sourcePath:
        • type: string
        • description: path of the source file. Can include %(...) parameters which will be filled in by the stage using the "AdditionalData" values. Built in %(...) operands include:
          • %(input), %(output), %(scratch), %(update), %(work) directories
          • %(dbUrl) database URL
          • %(runId), %(sliceId), %(universeSize) pipeline parameters
      2. destPath:
        • type: string
        • description: path of the destination file. Can include %(...) parameters which will be filled in by the stage using the "AdditionalData" values. Built in %(...) operands include:
          • %(input), %(output), %(scratch), %(update), %(work)
          • %(dbUrl)
          • %(runId), %(sliceId), %(universeSize)

Sample SymLinkStage Policy File

AdditionalData: "exposureId=triggerVisitEvent.exposureId"
RunMode: "preprocess"
Links: {
        sourcePath: "/lsst/images/D4/%(exposureId)"
        destPath: "/share/lsst9/DC3root/%(runId)/input/%(exposureId)
}