Correct handling of COMM_GROUP groups
Currently, COMM_GROUP members are updated by adding the number of members in a previous COMM_LOCATIONS group. This does not work for e.g. history traces generated by https://gitlab.hrz.tu-chemnitz.de/scads.ai/performance-investigations/big-data-trace-from-history, where no COMM_LOCATIONS group exists.