What to do when encountering Invalid value for search tag?

For a number of years, we require users to identify in which search category their Condor jobs belong to. To specify it, please add an line into your submit file specifying accounting_group.

After update to Debian buster (2020)

We simplified the overall structure of tags and made some significant changes to reduce the possiblity to “cheat” by creating new tags for each job (which would always start with the best effective user priority).

Thus, you need to put the following into your submit file:

accounting_group = CATEGORY.PRIORITY.DESCRIPTION

with

CATEGORY
being one of admin, boinc, burst, cbc, cw, gamma, radio, seti

If your jobs do not match any of the categories, please talk to us and we will find a solution.

The next part of the tag is relative priority you assign to the job submission, the associated words and priority factors are

PRIORITY
imp(10), prod(100), test(1000), dev(100000) and back(10000000)

Here, lower numbers imply higher importance and thus more resources will be allocated for lower priority factors. Obviously, if everyone ranked their jobs as imp (important) ones, this factor would become irrelevant, thus, please do not!

Finally, please find a short description for your job (say at most 10-15 characters without a dot), thus something like these lines should work:

  • accounting_group = cbc.test.o1-bns
  • accounting_group = radio.prod.arcibo_follow_up
  • accounting_group = cw.imp.eah_postprocessing

TL;DR

If you are familiar with Perl compatible regular expressions, each tag must match

/^(admin|boinc|burst|cbc|cw|gamma|radio|seti)\.(back|dev|imp|prod|test)\.[a-zA-Z0-9_-]+$/

Tag reduction

For the effective user priority calculation during job submission the accounting_group string is being changed to just become PRIORTY.USERNAME@atlas.local (for example visible via condor_userprio) to keep the priority list short and simple.

Before update to Debian buster

For LVC users, the list of valid tags can be found under /etc/condor/accounting/valid_tags. In the hopefully rare case of no matching tag, please contact the LDG accounting team or us to find a solution.

For users from other collaborations we have pre-defined tags of the form:

NAME.TYPE.DESCRIPTION

with

NAME
best match of aei, et, glasgow, lisa
TYPE
best match of dev, prod, sim
DESCRIPTION
any description matching the regular expression [a-zA-Z0-9_.-]+

This means your submit file must contain a line like

accounting_group = NAME.TYPE.DESCRIPTION

Please be considerate what you use in there!