After using CTAGGER to tag event type, the tags appeared in EEG.event.usertags and EEG.etc.tags as one long string without any comma-separation. When trying to extract epochs using tags, the whole tag string must be specified and thus individual tags can’t be used.
The issue was replicated in both Linux Fedora and Windows 10 Home edition. However, macOS didn’t seem to have such issue. Tagging through excel workflow also didn’t seem to have the issue.
After tracing the bug in the Linux computer, it seems that the issue is with the JSON string created by CTAGGER before passing to tagMap to parse. In the “tags” array, each tag string is enclosed by an extra pair of square brackets, making it an array or arrays. After removing the extra square brackets, creating fieldMap using the new JSON, and tagging the dataset with the new fieldMap, the problem appeared to be fixed.
After using CTAGGER to tag event type, the tags appeared in EEG.event.usertags and EEG.etc.tags as one long string without any comma-separation. When trying to extract epochs using tags, the whole tag string must be specified and thus individual tags can’t be used. The issue was replicated in both Linux Fedora and Windows 10 Home edition. However, macOS didn’t seem to have such issue. Tagging through excel workflow also didn’t seem to have the issue.
After tracing the bug in the Linux computer, it seems that the issue is with the JSON string created by CTAGGER before passing to tagMap to parse. In the “tags” array, each tag string is enclosed by an extra pair of square brackets, making it an array or arrays. After removing the extra square brackets, creating fieldMap using the new JSON, and tagging the dataset with the new fieldMap, the problem appeared to be fixed.
Screenshots and JSON file are attached in zip file. CTAGGERBugReport.zip