rest-for-physics / rest-for-physics/rawlib
TRestRawMultiFEMINOSToSignalProcess: first two events are with the same id
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I found that the first two events from TRestRawMultiFEMINOSToSignalProcess are with same id. Don't know if is the file/daq problem or the process's problem.
I download this file: https://github.com/rest-for-physics/rawlib/blob/master/pipeline/data/R01208_Ar2Iso_Background14h_14Vetos_IccubFEC-000.aqs
and type directly in restRoot:
TRestRawMultiFEMINOSToSignalProcess pc;
pc.OpenInputFiles({"R01208_Ar2Iso_Background14h_14Vetos_IccubFEC-000.aqs"});
TRestRun r;
pc.SetRunInfo(&r);
pc.InitProcess()
pc.ProcessEvent(NULL)->GetTimeStamp().GetNanoSec() //293870925
pc.ProcessEvent(NULL)->GetTimeStamp().GetNanoSec() //293870925
pc.ProcessEvent(NULL)->GetTimeStamp().GetNanoSec() //375673055
pc.ProcessEvent(NULL)->GetTimeStamp().GetNanoSec() //317906618
And see the timestamp of the first two events are same. We can also try event id, and see they are same. However, the signal data seems to be different, meaning that the events are not actually same.
TRestRawMultiFEMINOSToSignalProcess pc;
pc.OpenInputFiles({"R01208_Ar2Iso_Background14h_14Vetos_IccubFEC-000.aqs"});
TRestRun r;
pc.SetRunInfo(&r);
pc.InitProcess();
((TRestRawSignalEvent*)pc.ProcessEvent(NULL))->GetSignal(0)->GetData(0) //249
((TRestRawSignalEvent*)pc.ProcessEvent(NULL))->GetSignal(0)->GetData(0) //261
((TRestRawSignalEvent*)pc.ProcessEvent(NULL))->GetSignal(0)->GetData(0) //269
((TRestRawSignalEvent*)pc.ProcessEvent(NULL))->GetSignal(0)->GetData(0) //249
Contributor guide
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
Reproduce the report through TRestRawMultiFEMINOSToSignalProcess using the referenced .aqs file and the shown ProcessEvent calls. Start by inspecting that process's event and ID handling, then compare it with the input data reader to determine whether the duplicate first ID comes from the file or conversion. Done means identifying the source and documenting or correcting the duplicate-ID behavior.
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