-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Produce fits files for some incomplete packet sequences #370
Comments
for the start we should go for a manual trigger: start the pipeline CLI with a param and for a given set of RIDs
|
So this small script check for incomplete package sequences and running it in all of our science data give the following
21-6-20 (RPD)None 21-6-21 (CPD)
solo_LB_stix-21-6-21_0000000000-9999999999_V02_2305117159-57036.fits -113 False False False 21-6-22 (SCPD)None 21-6-23 (VIS)None 21-6-24 (SPEC)
solo_LB_stix-21-6-24_0000000000-9999999999_V02_2110280058-49980.fits -16 False False False 21-6-30 (QL LC)** Seems like nothing before FSW change from stand along to seq ** 21-6-31 (QL BK)** Seems like nothing before FSW change from stand along to seq ** 21-6-32 (QL SPEC)** Seems like nothing before FSW change from stand along to seq ** 21-6-33 (QL VAR)** Seems like nothing before FSW change from stand along to seq ** 21-6-34 (QL Flare Flag)** Seems like nothing before FSW change from stand along to seq ** 21-6-42 (Aspect)
solo_LB_stix-21-6-42_0000000000-9999999999_V02_2310110180-00000.fits -13 False False False |
There are ~40 requests which have incomplete packet sequence some of these are interesting events so need to investigate if we can make fits file for some/all of them.
The text was updated successfully, but these errors were encountered: