ecpi.process.dpco.core.gti_sta module

Good Time Interval: STA

Summary

Functions:

`get_gti`	Return Good Time Interval (GTI)
`get_gti_high_sta`	Return Good Time Interval (GTI) of SAA retrieve from EIC calibration file
`get_gti_no_slew_sta`	Return Good Time Interval (GTI) of STA retrieve in STATUS of ATT_CNV FITS file

Reference

get_gti(flag_sta, att_time)[source]

Return Good Time Interval (GTI)

Parameters

flag_sta – table of flag SAA -> False=out SAA, True in SAA (EXT or DEEP)
att_time – table of times

Returns

array of GTI

Return type

GTI type is numpy array (n,2) gti[x:0] is t_start gti[x:1] is t_stop

get_gti_high_sta(t_orb)[source]

Return Good Time Interval (GTI) of SAA retrieve from EIC calibration file

Parameters

t_att –
t_orb –

get_gti_no_slew_sta(t_att)[source]

Return Good Time Interval (GTI) of STA retrieve in STATUS of ATT_CNV FITS file

For the moment, the final versions of the stability is not known In the reference document SV-GS-NT-DEF the STATUS field is given for taking the pointing status. However in the reference SV-SCPL-IR-270-JPO given by C. Lachaud, there are two values for checking the stability:

Byte n+35 : Slew status ( 0x55 = slewing and 0xAA not slewing ) Byte n+40 : Quality of pointing stability (0x55 general, 0xAA high stability)

A given OBSID is considered as a full stability pointing gti

If no flag between [a, b] in t_orb so the GTI is [a, b+1]

:param t_att:table ATT_CNV :return: dictionary of GTI with key “sta” :rtype: GTI type is numpy array (n,2) gti[x:0] is t_start gti[x:1] is t_stop