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
Reversion of many steps (3-5) from the history can result in incorrect cluster labels. Observed with long recordings, eg. 2-3 hours recordings of 384 channels.
For about 20% of revert operations, some or all of the reverted steps are not removed from the history as displayed in the "History" pull down menu. This can be true even though the steps were correctly executed-- i.e. the cluster labels are correct. After saving the sort and re-starting manual curation, the history displayed is correct. (confirmed with JRCLUST v4.0.1 "Edward" (c584685)).
On recordings of any length, annotations are not handled correctly when reverting. Annotations remain "stuck" at the cluster assignment at the start of the revision, and don't get updated as the cluster labels change due to reverting merges and splits. (confirmed with JRCLUST v4.0.1 "Edward" (c584685)).
The text was updated successfully, but these errors were encountered:
Reversion of many steps (3-5) from the history can result in incorrect cluster labels. Observed with long recordings, eg. 2-3 hours recordings of 384 channels.
For about 20% of revert operations, some or all of the reverted steps are not removed from the history as displayed in the "History" pull down menu. This can be true even though the steps were correctly executed-- i.e. the cluster labels are correct. After saving the sort and re-starting manual curation, the history displayed is correct. (confirmed with JRCLUST v4.0.1 "Edward" (c584685)).
On recordings of any length, annotations are not handled correctly when reverting. Annotations remain "stuck" at the cluster assignment at the start of the revision, and don't get updated as the cluster labels change due to reverting merges and splits. (confirmed with JRCLUST v4.0.1 "Edward" (c584685)).
The text was updated successfully, but these errors were encountered: