Incorrect critical path computation after filtering
The critical path computation seems to have an unwanted influence of filtering. Consider the following Gantt chart: When applying critical path analysis (Use of specified dependencies: NONE, Use default epsilon) on it, the following Gantt chart is shown:
If one applies a filter to remove claims with names A1 and A2 and then applies critical path analysis again, the following Gantt chart is shown: Now only three claims are considered critical, which is incorrect.
The following ETF file was used for this example.trace.etf