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
After Merging any candidates within a Cluster, the Surf User is taken out of the "Streaks" UI to the "One Cluster Per ID" UI
Streaks
User is taken to the "One Cluster Per ID" UI after clicking on Merge
Note:
The merge still takes place when clicking "Merge" within the Streaks UI
In the following picture, the chosen rows (from Image 1) all have the same ID, signifying the merge was successfully done
To replicate:
Click Merge from Streaks UI
Filter -> Candidate = /ERAMANATHAN/ after being taken to "One Cluster Per ID" UI
Since we know the merge does take place, the bug is not critical
Current Turnaround:
Run the Streaks algorithm multiple times and merge within multiple clusters at once, instead of one cluster at a time
Proposed Solution:
The user is kept within Streaks UI after clicking Merge
The text was updated successfully, but these errors were encountered:
ananay95
changed the title
SURF - Streaks algorithm 'merge' resets Surf to one cluster per id
SURF - Merging rows in Streaks UI unexpectedly takes user to One-Cluster-Per-ID UI
Oct 8, 2022
Dataset Used: Test_Tamil_Nadu.csv
To replicate Bug -
Settings used:
Column for IDs -> 'Candidate'
Columns to show during merge -> All
Within a cluster, sort by -> Year
Clustering algorithm -> Streaks
Streak Column -> Assembly_No
Streak Length -> 5
Max. Holes in Streak -> 1
Secondary Column -> Constituency_Name
After Merging any candidates within a Cluster, the Surf User is taken out of the "Streaks" UI to the "One Cluster Per ID" UI
Streaks

User is taken to the "One Cluster Per ID" UI after clicking on Merge

Note:
The merge still takes place when clicking "Merge" within the Streaks UI
In the following picture, the chosen rows (from Image 1) all have the same ID, signifying the merge was successfully done
To replicate:
Since we know the merge does take place, the bug is not critical
Current Turnaround:
Run the Streaks algorithm multiple times and merge within multiple clusters at once, instead of one cluster at a time
Proposed Solution:
The user is kept within Streaks UI after clicking Merge
The text was updated successfully, but these errors were encountered: