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
By loading the agglomerate skeletons and deleting/merging edges by interacting with the skeleton nodes. The visible segmentation will update appropriately.
By activating a segment with the proofreading tool and then doing a split/merge with the context menu on another segment position (without using skeletons). Here, the agglomerate skeletons won’t update automatically currently.
In the second case, it would make sense to also update the skeletons. Either delete and refetch them or do the appropriate semantic operation (delete/create edges) in the front-end.
Todos:
get affected skeleton (e.g., by tree name since we know what to expect as long as the user didn't rename it). E.g., this source code: ¹
find edges to delete or remove given the agglomerate positions. in the min-cut case for example, these are easily available. in other cases (such as merge), the back-end probably needs to send the agglomerate positions back
ensure that the naming of the trees stays intact
disallow renaming of agglomerate trees. or alternatively, store the agglomerate ID as metadata in the tree.
// findTreeByName already exists but can be changed like this:exportfunctionfindTreeByName(trees: TreeMap,treeName: string,type?: TreeType|null|undefined,): Tree|undefined{return_.values(trees).find((tree: Tree)=>tree.name===treeName&&(type==null||tree.type===type),);}exportfunctiongetExistingAgglomerateTree(skeletonTracing: SkeletonTracing,agglomerateId: number,mappingName: string,){// todo: this won't work as soon as the user renames the tree. store the original agglomerateId// in the tree?constexpectedName=getTreeNameForAgglomerateSkeleton(agglomerateId,mappingName);returnfindTreeByName(skeletonTracing.trees,expectedName,"AGGLOMERATE");}// within the proofreading sagas:constskeleton=yield*select((state)=>state.tracing.skeleton);consttree=clickedTree||(skeleton!=null
? getExistingAgglomerateTree(skeleton,sourceAgglomerateId,editableMappingId)
: null);
The text was updated successfully, but these errors were encountered:
Detailed Description
There are two ways to do volume proofreading:
In the second case, it would make sense to also update the skeletons. Either delete and refetch them or do the appropriate semantic operation (delete/create edges) in the front-end.
Todos:
merge
), the back-end probably needs to send the agglomerate positions backThe text was updated successfully, but these errors were encountered: