On my machine, I receive a nullpointer exception in processManager.ProcessComparator.compare, tested with multiple protocol files. Indicating there is at least one process manager incorrectly saved to the output XML. Inspection of the outputfile reveals that departure and arrival process both have an empty node without attributes, this is likely where the issue originates.
On my machine, I receive a nullpointer exception in processManager.ProcessComparator.compare, tested with multiple protocol files. Indicating there is at least one process manager incorrectly saved to the output XML. Inspection of the outputfile reveals that departure and arrival process both have an empty node without attributes, this is likely where the issue originates.
<arrivalProcesses /> <departureProcesses />