Add segger (Draft) #43
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a first draft for adding Segger. There are current issues that can't be solved (spatialdata and segger dependency issue and cuda error when running on cpu)
Two main issues:
segment) we run into a cuda issue (tested in dockercontainer on Mac M3), note that the training worked fine. Related issue: CUDA error when running predictions without GPU EliHei2/segger_dev#126"qv"column, see here Data sample save does not produce files EliHei2/segger_dev#125). However, there aredaskundnumpyversion dependency conflicts betweenseggerandspatialdata(see here Spatialdata and dask Comatibility EliHei2/segger_dev#123).Environment
config.vsh.yamlgives the ideal solution (for future updated version of thedanielunyi42/segger_devcontainer), however currently this doesn't work (see CUDA error when running predictions without GPU EliHei2/segger_dev#126 (comment)). Besides the docker container build that I posted there you also need to install:Other
How to proceed