make printable
all trendPlotter config files
trendPlotter tool
trendPlotter operations
qc1Plotter web interface
navigation bars can be created by webNavBar
|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.eso.org/~qc/tqs/config_tp_spec.html
Дата изменения: Thu Jan 8 20:07:59 2015 Дата индексирования: Sun Apr 10 00:49:39 2016 Кодировка: Поисковые слова: m 63 |
Common Trending and QC tools:
|
| tqs = Trending and Quality Control System |
| make printable |
new: | see also: |
|
|
all trendPlotter config files navigation bars can be created by webNavBar |
|
There is the option for using a non-standard tool configuration instead of config.trendPlotter. That special configuration gives much more flexibility for the design of the output, but because of that is not intended for reports on the HC site. A typical application of special configuration is the WISQ web site.
A non-standard tool configuration is called like follows:
trendPlotter -c <non-standard_config> -r <report> -f
There is no rule about its name.
Its content is the same as that of the standard configuration file (which you check out here), plus it has some additional keys which are not configurable in standard HC reports.
| Section 1: additional general parameters | ||
| WIDTH |
600 | non-standard width of HTML table in px (standard value is 950 pixels) |
| HEADER | /observing/dfo/quality/WISQ/HEALTH/header_WISQ.html | non-standard header page |
| VNAVBAR | /observing/dfo/quality/WISQ/HEALTH/navbar_WISQ.html | non-standard vertical navigation bar |
| PLOT_LABEL | Workflow_information_system_for_QC | non-standard plot label |
| PRODUCT_SECTION | NO | optional; display the product section (default: YES) |
| INFO_SECTION | NO | optional; display the INFO section (HELP | USERS-GUIDE | MORE) (default: YES) |
| HISTORY_SECTION | YES | optional; display the horizontal navbar (default: YES) |
| SCORE_FLAG | NO | NO: no link to "scores&comments" included (default: YES) |
| HISTO_FLAG | NO | NO: no link to "history" offered (default: YES) |
| EDIT_FLAG | NO | NO: no 'edit' button for "Report news" (e.g. since they don't comply with DATE convention) |
| EDIT_PERMA | YES | YES: comment is permanent (validity check turned off) |
| DATE_RANGE | YES | NO: switch off "last_90_days", "QC_data_range: ... " |
| DATE_RNG_LABEL | Data_range_for_ZP | non-standard text for DATE_RANGE (default: "QC_data_range") ; all '_' will be replaced by blanks |
If you use a non-standard tool configuration file, you should mark the report configuration file(s) with the special key CONFIG_TYPE (value is NON_STANDARD). Check out here.
Furthermore some standard configuration keys can be filled in a non-standard way. For instance, the standard value for QC_URL is
http://www.eso.org/observing/dfo/quality/GIRAFFE/reports
while for WISQ reports it becomes
http://www.eso.org/observing/dfo/quality/WISQ .
Find here a sketch of the impact of these configuration keys [click to enlarge]:
