Parameterized segmentation of virtual Image

[Machriam]

Sometimes it is not easily visible, what has changed between images leading the descriptor values to change.

I want an Option to calculate and Show the segmentation of a virtual Image

This feature would pair well with parameterized segmentation, stored along the phototourtrips in a jsonb format. The following parameters would be useful after solving #226:

1. HSL High and Low values for segmentation
2. Repeat amount of Opening
3. Toggling Otsu-Thresholding

The segmentation parameters should be used based on the last defined parameter from the trips - analogue to the IR-alignment

Usability Fixes

• The gateway server sometimes crashes/hangs during scrolling through virtual images
• Empty images are displayed sometimes
• I want an option to remove the currently selected image from the filter

[github-actions[bot]]

Changes of Pull Request #234

Commit messages for #229

• cc8492a8561208e392adeec71993e42ea6265bb5 Segmentation parameters can now be dynamically adjusted and the result is displayed instantly
• 41a6eea1cae5a1c07bbaef4bcd2291b3a463389f segmentations can now be stored. Additionally added a converter to always store and serve json data on the backend in utc format
• d99f7235e3b6ecf9a675ea4a31d8837bcbd56a5c simplification for photo summary worker
• 36578aafff30d2cc6058d2aadfb4b3b8b5a9fa65 We need to store the milliseconds aswell else selection of individual datapoints is impossible in the plant summary for high res photo tours
• 703905ee23a276580f3a1d1f0f9ec2de5c27d322 added a sample pipe implementation, but it does not expose the extended properties
• 2d09c8d62ef2709dccd42f6c7d616b82ba6eeada Reverting of wrong scaffolding because of local identity setting

[github-actions[bot]]

Changes of Pull Request #235

Commit messages for #229

• 0b9d5fa40808cfd2f2086a94c88901a1b788cde9 removed all simple object type extensions from the project to the pipe function. The pipe functions automatically gives access to the corresponding wrapper type with extension methods. This has the advantage to not pollute the prototype namespace
• e7d01a59db16d304a77061b7b782ff4064b4bfc1 added try method to pipe functions aswell
• 6678df63134f49be691f7c09a594e680d2e97bfb moved remaining prototype extensions to the pipe function
• 0261327d198cba689272ddaed4899dd093bcd8ef added an easier sort extension to pipe methods, which is able to sort only, when toArray or collect is called
• 2e15b7af9f9c46382e5a945192e5ac4f96ad4fe2 Segmentation changes are now indicated in the diagram
• 390be76deabfbe6137007f2443a139ba6468ce48 when input numbers are initially selected, each of them calls the updatevirtualimage function. This is now prohibited by registering the cache key on the dashboard client instance, such that the call is terminated, if the cache key was already registered. A registered cache key means, that there is already a call to the backend running
• 04989f0540009f609ec532ec5a252a62e9d54792 segmentation parameters are now properly updated between graph and selection
• 752281c0078847a7c6dd2af19bd88bb52dd527b9 Merge branch '229-parameterized-segmentation-of-image' of https://github.com/Machriam/PlantMonitor into 229-parameterized-segmentation-of-image

[github-actions[bot]]

Changes of Pull Request #236

Commit messages for #229

• 9855c61c993308df9e8c18281e00d3768bfc45ca apply functions call now implicitely the toarray function to apply the sorting
• 717dcf52640601213924648baf6b01ebaf4a6be6 the corresponding segmentation is now always displayed upon image change. A segmentation can be removed by setting the segmentation on the starting point to default. Segmentation options are properly updated on each update

[github-actions[bot]]

Changes of Pull Request #237

Commit messages for #229

• efefdead87bc7feb8460a15a9c288ec2ba9d9085 the trip with the least distance to the sent time is now associated with the custom segmentation. Somehow the precision might differ

[github-actions[bot]]

Changes of Pull Request #238

Commit messages for #229

• 2a0e265ce48d72360f89203c2a1aa7e15c4b3daf photo tour summary can now be recalculated without creating virtual images from scratch. Existing segmentation paramaters are only highlighted, when there is an exact json match
• 8b0a0d157fb7198ca65318f899720a7aeaae236d much better ui with saving and restoring of segmentations as a new feature. Existing segmentations are now displayed with more room
• 6b284b3cbaec7efad5629a0fa62116fe46e71653 segmentation lines are not duplicated anymore and reach now properly from top to bottom

[github-actions[bot]]

Changes of Pull Request #239

Commit messages for #229

• ed5e95f188aa8111484c4abd05b1f3e2ad00e8b9 Segmentation values can now be locked. This means the user can decide, whether he wants to see the actual segmentation or the currently selected segmentation upon image change