You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using multiple PMTInfo tables to construct a detector, there seems to be a weird dependence on the "index" of the table that causes some sets of the ptms to not register hits at all. No discernible pattern has been found so far. A possible solution would be to force the multiple pmtinfo sets to merge internally and be assigned a new fixed name -- though this could cause trouble for the regex-based generators.
The text was updated successfully, but these errors were encountered:
When using multiple PMTInfo tables to construct a detector, there seems to be a weird dependence on the "index" of the table that causes some sets of the ptms to not register hits at all. No discernible pattern has been found so far. A possible solution would be to force the multiple pmtinfo sets to merge internally and be assigned a new fixed name -- though this could cause trouble for the regex-based generators.
The text was updated successfully, but these errors were encountered: