markusdreyer / delegation-sequencing Goto Github PK

If a task (T2) has a precedence restriction to task (T1), and T1 does not exist, then T2 should be dropped. This implicitly means that any tasks that has a precedence restriction to T2 should also be dropped.

Current behaviour is that the task is included, regardless if the tasks precedence restriction is present in the result set. See example below showing task T2 in the result set, even though T2 has a precedence restriction to T1, which does not exist.

It should not be possible to generate models with roles from agents other than the agents assigned to the task. E.g.
The following task, should only be assigned to members of the 1st Attack Engine Crew with the Firetruck Driver role.

The current behaviour is that all agents with the Firetruck Driver role, regardless of team, is considered. This also leads to a side effect where the same task occurs multiple times in a model, with the only difference being different agents.

Example:

In the example above, both lukas and peter has the Firetruck Driver role assignment, but only lukas should be considered, as peter does not belong to the assigned team. See taxonomy table below of the agents and role assignments:

See attached GIF of the issue:

To reproduce:

1. Visit https://delegation-sequencing.azurewebsites.net/
2. Select the Hamar Scenario from the Procedures in the left side menu
3. Select the Hamar taxonomy from the taxonomy dropdown
4. Click the GENERATE ACTION CARDS button

ASP will ignore tasks that are unsolvable instead of returning unsatisfiable. An example of this is if you delete an agent that is required for a task, then the task is ignored.

To reproduce:

1. Visit https://delegation-sequencing.azurewebsites.net/
2. Navigate to the second page of the default procedure (EA fire)
3. Take note of the "Travel of ladder tower crew to 911 address" task and its role and agent restrictions.
4. Click the GENERATE ACTION CARDS button
5. See that the "Travel of ladder tower crew to 911 address" task is missing from the model.

This happens because the task has the driver role assignment restriction, as well as the lt_crew agent restriction.

Looking at the Land fire incidents taxonomy in the left side menu, we see that lt_crew has no agents with the driver role assignment.

Instead of ignoring the task, ASP should return UNSATISFIABLE.