Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/6.5.0/doc/odfcheck/node15.html
Дата изменения: Tue Aug 16 07:09:27 2005 Дата индексирования: Sat Dec 22 11:03:40 2007 Кодировка: Поисковые слова: п п п п п п п п п |
Parameter | Mand | Type | Default | Constraints |
skippreliminaries | no | bool | no | |
If set odfcheck
will assume that the user has already run
cifbuild
and odfingest, and that the relevant
environment variables have been set. Otherwise cifbuild
and
odfingest
will be run. The resulting CIF will have a name
like RRRR_XXXXXXXXXX.cif, where RRRR_XXXXXXXXXX is the
revolution/observation identifier for the current ODF.
| ||||
checkattitude | no | bool | yes | |
If set odfcheck
will run the attitude diagnostics on the
current ODF.
| ||||
allowedbadattitudefraction | no | real | 65 | [0,100] |
When running the attitude diagnostics odfcheck
will issue a
warning if the attitude is more than
allowedbadattitudefraction% of the time more than nrms
r.m.s. away from the median.
| ||||
nrms | no | real | 3 | |
If the attitude diagnostic is being run, then the fraction of the
time that the attitude differs more than nrms from the
median pointing will be calculated.
| ||||
allowedtimecorrelationfraction | no | real | 65 | [0,100] |
When running the time correlation diagnostic odfcheck
will issue a
warning if more than
allowedtimecorrelationfraction% of the available data points
need to be discarded in order to reach a good fit. | ||||
checktimecorrelation | no | bool | yes | |
If set odfcheck
will run the time correlation diagnostics on the
current ODF.
| ||||
tcpinterval | no | real | 35 | |
If the time correlation diagnostic is being run, time packets
differing more than tcpinterval seconds from each other
will be considered in estimating the statistical loss of telemetry.
| ||||
checktelemetry | no | bool | yes | |
If set odfcheck
will run the telemetry loss diagnostics on the
current ODF.
| ||||
allowedtelemetrylossfraction | no | real | 5 | [0,100] |
When running the telemetry loss diagnostic odfcheck
will issue a
warning if the estimated telemetry loss is larger than
allowedtelemetrylossfraction%. | ||||
checkcountingmode | no | bool | yes | |
If set odfcheck
will run the EPIC counting mode diagnostics on the
current ODF.
| ||||
checkminimumpnenergy | no | bool | yes | |
If set odfcheck
will run the PN minimum energy diagnostics on the
current ODF.
| ||||
checkompriorityfieldacquisition | no | bool | yes | |
If set odfcheck
will run the OM priority field acquisition diagnostics on the
current ODF.
| ||||
checkhkgti | no | bool | yes | |
If set odfcheck
will run the housekeeping GTI diagnostics on the
current ODF.
| ||||
checkmostemperature | no | bool | yes | |
If set odfcheck
will check if the EMOS cameras mean
temperature during the science exposures was above the thresholds
given with m1temperature and m2temperature.
| ||||
m1temperature | no | real | 33 | |
If the corresponfing diagnostics is activated odfcheck
will
use this value as the minimum mean temperature for the EMOS1 camera.
| ||||
m2temperature | no | real | 30 | |
If the corresponfing diagnostics is activated odfcheck
will
use this value as the minimum mean temperature for the EMOS2 camera.
| ||||
checkpnenergy | no | bool | yes | |
If set odfcheck
will
check if the energy of every event in the PN science files is above
a threshold. The latter is calculated from the housekeeping. | ||||
checksascompliance | no | bool | yes | |
If set odfcheck
will check that every FITS file in the ODF
can be read with the SAS.
| ||||
Parameter | Mand | Type | Default | Constraints |