Min-Cut on Agglomerate Graph

[fm3]

Min-cut on agglomerate graph.

URL of deployed dev instance (used for testing):

• https://agglomerategraphmincut.webknossos.xyz

Steps to test:

• activate the Proofreading tool on an annotation with agglomerate mapping
• select a source node, right-click on a target node and "Perform Min-Cut between these Nodes"

Backend

• new route POST /volume/:tracingId/agglomerateGraphMinCut expects positions of two nodes between which to calculate the min-cut.
• sample request on an editable mapping on the test-agglomerate-file dataset:

POST http://localhost:9000/tracings/volume/827b9540-a45c-4c9a-965a-dafd193ab21a/agglomerateGraphMinCut?token=secretSampleUserToken
Body: {"segmentPosition1":[77, 77, 39],"segmentPosition2":[77, 73, 80],"mag":[1,1,1],"agglomerateId":1,"editableMappingId":"1a2ed917-39f1-4d52-8ece-b6e98fb3ec49"}

• returned [{"segmentId1":1,"segmentId2":3,"position1":[77,77,39],"position2":[77,73,80]},{"segmentId1":1,"segmentId2":49,"position1":[77,77,39],"position2":[87,100,70]},{"segmentId1":1,"segmentId2":56,"position1":[77,77,39],"position2":[80,149,94]},{"segmentId1":1,"segmentId2":58,"position1":[77,77,39],"position2":[91,107,76]},{"segmentId1":1,"segmentId2":63,"position1":[77,77,39],"position2":[83,64,59]},{"segmentId1":1,"segmentId2":76,"position1":[77,77,39],"position2":[105,101,62]},{"segmentId1":1,"segmentId2":82,"position1":[77,77,39],"position2":[96,89,66]},{"segmentId1":1,"segmentId2":88,"position1":[77,77,39],"position2":[104,53,51]},{"segmentId1":3,"segmentId2":34,"position1":[77,73,80],"position2":[62,122,87]}]

Issues:

• fixes Min-cut for super voxel graphs #6265

---

• Updated (unreleased) changelog
• Needs datastore update after deployment
• Ready for review

[philippotto]

awesome! didn't test, yet, but the code itself already looks very good. still, I've left some feedback :)

[philippotto]

testing went really well 👍 unfortunately, i could only test it on https://agglomerategraphmincut.webknossos.xyz/datasets/sample_organization/test-agglomerate-file/view and not on a big segmentation, but splitting was really fun 👍

[jstriebel]

Nice, backend mostly LGTM, just left one comment 👍

[jstriebel]

Is there anything else we should be aware of? E.g. are the actions applied in the order intended? Can the frontend now also send multiple actions in one group?

[fm3]

I’d say this should work as is. For this particular update group, the order should actually not matter, as it deletes all the edges of the cut.
Multiple actions in one group is exactly what is now possible. It still has to be one group.

[philippotto]

great, frontend looks good 👍