Multiple copies of the Grid3D class about biotracker_core HOT 5 CLOSED

@nebw @hmoenck

from biotracker_core.

Creating a repository for only one class seems overkill, though it looks like the most safe thing to do. Are there any more common datastructures and functionalities which can be offloaded into one repository for common use? Json settings are the first thing which come to my mind. The settings class appears in many very similar variations in many repositories.

from biotracker_core.

What about embedding it into biotracker_core? Than one only needs to link against the core and can choose what tools to use.. that way we can also provide trackers with the tools. Downside is that the core might get too bloated if we dont take care

from biotracker_core.

biotracker_core should not include any BeesBook-relevant code. My preferred solution would be to only include the Grid3D class in the groundtruthConvert repo. Seems like this the best place to store legacy code. The groundtruthConvert should have a function to automatically convert Grid3Ds to PipelineGrids as well.

from biotracker_core.

The groundtruthConverter seems to be the best place, I agree. It has very few dependencies and few object files to compile. This shouldn't increase to much in the future, so it is a rather lightweight dependency itself.
About the converter function we've been talking. I basically did this in a local project, so I can add this later.

from biotracker_core.