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
Also related to #12 if P2 starts to support multiple chains.
Since each algorithm is a generator and builds up occurrences as they find them, if there exists a full occurrence of the pattern but settings['mismatches'] > 0, S2 and W2 will find all combinations of mismatches within it.
e.g. 'ACE' is the pattern, with an identical source 'ACE'. We use S2 or W2 with threshold = 2 rather than 3
then they will find 'AC', 'AE", 'CE', and 'ACE'. This makes using partial matching frustrating with excerpt output, where each occurrence gets its own xml file, since a lot of the results are redundant.
Currently I workaround by finding all occurrences at once and colouring them in one big score (but this defeats the purpose of having generators in the first place). If we want interactive excerpt output in javascript, then this should be fixed
Option 1) is to try to identify related occurrences by tagging them before they're yielded in the algorithm. Option 2) is to process them after being yielded and filter them based on their shared notes.
But the whole point of having multiple chains is to see the combinations of voices that a query can cross through, so I'm a little confused how to fix the redundancy but retain the desired behaviour.
The text was updated successfully, but these errors were encountered:
Also related to #12 if P2 starts to support multiple chains.
Since each algorithm is a generator and builds up occurrences as they find them, if there exists a full occurrence of the pattern but settings['mismatches'] > 0, S2 and W2 will find all combinations of mismatches within it.
e.g. 'ACE' is the pattern, with an identical source 'ACE'. We use S2 or W2 with threshold = 2 rather than 3
then they will find 'AC', 'AE", 'CE', and 'ACE'. This makes using partial matching frustrating with excerpt output, where each occurrence gets its own xml file, since a lot of the results are redundant.
Currently I workaround by finding all occurrences at once and colouring them in one big score (but this defeats the purpose of having generators in the first place). If we want interactive excerpt output in javascript, then this should be fixed
Option 1) is to try to identify related occurrences by tagging them before they're yielded in the algorithm. Option 2) is to process them after being yielded and filter them based on their shared notes.
But the whole point of having multiple chains is to see the combinations of voices that a query can cross through, so I'm a little confused how to fix the redundancy but retain the desired behaviour.
The text was updated successfully, but these errors were encountered: