Philipp Otto

> @philippotto I’ve done that now, please give it a try! The new params are called `segmentId1`, `segmentId2`, `segmentId` Awesome, thanks, I'll give it a try. > I assume that...

> Furthermore, throughout the codebase we have the name agglomerateId and mappedSegmentId for the exact same data / object / think. The same goes for segmentId and umappedSegmentId (if I...

> I think it was in the mesh_saga.ts where Chunck refers to a mesh of an unmapped segment while the file calls the underlying segment something like unmappedSegment. Imo it...

@MichaelBuessemeyer Thank you for your thorough testing and feedback :+1: I incorporated most of your feedback, fixed the hiccups you noticed and did some performance optimizations. Please have another look...

> When I select the Split from all neighboring segments action, I get a A precomputed mesh could not be loaded for this segment. More information was printed to the...

Thanks for the repro steps :pray: Indeed, it happens quite frequently on the dev instance for me, too. @fm3 The error is coming from the back-end (the front-end might still...

> When I select the Split from all neighboring segments action, I get a A precomputed mesh could not be loaded for this segment. More information was printed to the...

> During checking your changes I found a little bug in them: Argh, you are right. TypeScript should have caught this, too, but didn't :cry: Maybe because a function can...

> raw yaml input does the back-end support this already? > info about training bbox sizes what exactly are the expected sizes? then, I could put them in the modal....

I think, the PR is ready for a first round of review :) We haven't added a changelog entry, yet. Maybe we should defer this until the features are available...