[WIP] eventify: removed HierarchyLevels and Listener<> from event_dispatcher #14

Member
No description provided.
In the FMSolvr, the concurrent implementation of FMM passes,
defines tasks at the octree node granularity,
that is applying an FMM operator for one node defines one task.

This explains why template specializations of CallbackImpl<>
for P2M_Task, M2M_Task, M2L_Task, L2L_Task and L2P_Task
were ignoring the HierarchyLevels parameter.

Moreover, the sequential implementation of FMM passes,
which does not utilize / depend on the Eventify tasking system,
defines tasks at the coarsest possible granularity,
that is executing an FMM pass defines one task,
which shows that LVL and ALL HierarchyLevels are not used.

To summarize,
Hierarchy-Levels are a misnomer for Task-Granularities and
the FMSolvr currently does *not* support varying granularity of tasks.


The only place where the LVL HierarchyLevel was used
was the the EventDispatcher unit-test,
which was checking whether filtering of HierarchyLevels worked correctly.

The EventDispatcher unit-test was making sure that nothing is executed
in the case, where triggered HierarchyLevel does not match
the configured HierarchyLevel (aka Quantity) - LVL doesn't match BOX.

Since HierarchyLevel was removed from the EventListenerContainer::dispatch<>(),
no filtering by HierarchyLevel / Quantity is being done,
thus the EventDispatcher unit-test doesn't have a semantic sense anymore.
i.kabadshow merged commit b9fc3de1c7 into WIP/parallelization/intra-node/lgpl21+minimize 2021-05-27 20:32:25 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ATML-CAP/fmsolvr#14
No description provided.