| 324 | | Another script in the {{{/tools}}} directory can be used to probe errors more thoroughly. Chip, camera, warp, stack, diff, magic and destreak are currently supported, as well as the use of multiple labels (all use LIKE so wildcards work). You can also search by a specific fault code, or limit the query. The script categorises errors for entries at the specified stage and with the provided label. The output is the appropriate id and component, the machine it was run on, and the particular problem (e.g., a file that failed to be found, otherwise the resolved name of the processing log), all grouped into categories. With such a list, it's easy to identify patterns, e.g., a few warps are failing because of a single corrupt camera mask file; or machine X can't read files on machine Y. For example, using the same label as above: |
| | 324 | Another script in the {{{/tools}}} directory can be used to probe errors more thoroughly for a particular stage and label. The chip, camera, warp, stack, diff, magic and destreak stages are currently supported, as well as the use of multiple labels (wildcards are allowed). You can also search by a specific fault code (see table below), or limit the query. The output is the appropriate id and component, the machine it was run on, and the particular problem (e.g., a file that failed to be found, otherwise the resolved name of the processing log), all grouped into categories. With such a list, it's easy to identify patterns, e.g., a few warps are failing because of a single corrupt camera mask file, or machine 'X' can't read files on machine 'Y'. For example, using the same label as above: |
