ChimeraTK / ChimeraTK/ControlSystemAdapter-DoocsAdapter
Bug in IFFF history
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 1
- Avg merge
- 23h 29m
- Merged PRs (30d)
- 1
Description
DOOCS IFFF history complains about faulty timestamp.
Here is a snippet from diagnostic server log;
2020-07-06T10:58:00 LA_fill_hist <DETUNING_PARAMS.HIST/C8.M4.A6.L3> block <1427>, ERROR first excluded record's wrong timestamp is <1594025701> sec, <773> msec *
2020-07-06T10:58:00 LA_fill_hist <DETUNING_PARAMS.HIST/C8.M4.A6.L3> block <1427>, ERROR - <1> records with wrong timestamp excluded, starting at record <214> - written records <1999> *
2020-07-06T10:58:01 LA_fill_hist <DETUNING_PARAMS.HIST/C3.M3.A6.L3> block <1430>, ERROR first excluded record's wrong timestamp is <1594025701> sec, <773> msec *
2020-07-06T10:58:01 LA_fill_hist <DETUNING_PARAMS.HIST/C3.M3.A6.L3> block <1430>, ERROR - <1> records with wrong timestamp excluded, starting at record <200> - written records <1999> *
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the DOOCS IFFF history handling around LA_fill_hist and the DETUNING_PARAMS.HIST records shown in the diagnostic log. Reproduce the faulty-timestamp exclusion using the reported timestamp and record numbers, then identify the cause and verify that valid history records are no longer rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100