- 30 Jul, 2015 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 29 Jul, 2015 11 commits
-
-
Tomasz Wlostowski authored
Signed-off-by: Tomasz Wlostowski <Tomasz.Wlostowski@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Actually, they are still together in the same structure but on the application output we separate them to make it clear Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 21 Jul, 2015 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 17 Jul, 2015 3 commits
-
-
Federico Vaga authored
Instead of going to the next available trigger (i + 1), what we have to to do is going to the next available trigger for a given channel Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
A trigger can be assigned, on output, to different channel. So, when we look for a trigger ID we must specify on which channel and not just getting the first one assigned. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 16 Jul, 2015 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 15 Jul, 2015 5 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 14 Jul, 2015 1 commit
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 10 Jul, 2015 6 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 09 Jul, 2015 2 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 08 Jul, 2015 2 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 02 Jul, 2015 1 commit
-
-
Federico Vaga authored
"premature optimization is the root of all evil" The hash implementation was buggy. Difficult to understand because it includes also a memory allocator. My humble opinion is that we do not need such optimization for a very limited entries set (128). I replaced the hash table with an ordered by trigger-id array. Ordered because with an optimization you can use a binary search to retrieve in few step the correct trigger. NOTE: a draft of the binary search algorithm is there but not tested, that's way is inactive code. Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 01 Jul, 2015 4 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
- 30 Jun, 2015 2 commits
-
-
Federico Vaga authored
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-
Federico Vaga authored
The behavior was not clear because it was overwriting the same values. From the real-time application we were sending both a trigger and, if any, its condition (which is a trigger itself). On library side we were reading both: the condition (if any) and than the trigger. But when the user was interested in just the trigger we were overwriting the condition. So with this patch we send (RT) and receive (lib) only what we requested Signed-off-by: Federico Vaga <federico.vaga@cern.ch>
-