da.tasks

This changes the execution mode such that the priority is increased when the current day is the first one of various intervals. That is, this executes at the specified priority when this is not the first day of something. It will execute at the priority plus 1000 when this is the first day of the week (defined as Saturday), plus 2000 when it is the first weekend of the month, and plus 3000 when it is the fist weekend of the year. When the priority is not set it defaults to 3000 when this option is used.

This option causes all tasks to be executed in detached processes. This allows for better isolation in the event of failure or other problems.

This is the maximum priority level of tasks to execute. Priority zero tasks are run every time data is processed. Priority 1000 is run "near real time" (generally every ten minutes). Priority 2000 is run "frequently" (generally hourly). Priority 3000 is run less frequently (generally daily). Priority 4000 is run on a more differed basis (generally weekly). Priority 5000 is run on a response time irrelevant basis (generally monthly). Priority 6000 is run on an even lower time basis (generally yearly).

Default: 0

This option only accepts integers greater than or equal to 0.

If set then no progress output is displayed and any confirmation prompts are bypassed.

Default: Disabled

This argument is used to specify the station used to look up variables that do not include a station as part of an archive read specification. The station is the three letter GAW station code of the location, such as BND. The argument accepts multiple stations specified as regular expressions and separated by : or ; or ,. For example BND,MLO and (BND|MLO) are two ways of selecting both the BND and MLO stations.

The special value allstations may also be specified to select all stations.

This will run all tasks that are flagged as immediate. Normally this is not required as it is run automatically by the data archive modifier.

This will run all tasks of weekly or higher frequency.