Anonymous | Login | Signup for a new account | 2025-05-09 05:23 EDT | ![]() |
My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0000426 | JANA | Feature Request | public | 2014-12-03 06:18 | 2015-06-09 16:15 | ||||
Reporter | davidl | ||||||||
Assigned To | davidl | ||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Summary | 0000426: Add event barrier | ||||||||
Description | There are situations where special events are encountered in the data stream that may affect how the events following it are analyzed. These include EPICS events and sync events. In order to ensure that all subsequent events see the effects of the special event, but no previous ones still being processed do, a barrier mechanism is needed. The barrier should be callable from the JEventSource::GetEvent() method and should let the event buffer drain completely before continuing. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
![]() |
|
(0000642) davidl (administrator) 2015-06-09 16:15 |
This was implemented in revision 2337 and will appear in JANA 0.7.3. If an event source calls: event.SetSequential() in its GetEvent method than the event is flagged to be run sequentially. A unit test called "event_barrier" was created to test the mechanism and it appears to work. |
![]() |
|||
Date Modified | Username | Field | Change |
2014-12-03 06:18 | davidl | New Issue | |
2014-12-03 06:19 | davidl | Status | new => assigned |
2014-12-03 06:19 | davidl | Assigned To | => davidl |
2015-06-09 16:15 | davidl | Note Added: 0000642 | |
2015-06-09 16:15 | davidl | Status | assigned => resolved |
2015-06-09 16:15 | davidl | Resolution | open => fixed |
Copyright © 2000 - 2025 MantisBT Team |