Open Ashwitaa opened 2 years ago
Which criterion did you use for group observation and segmentation?
I used the current version of py-eddy-tracker to generate the network file and thus same criterion to group observations and segments…
which value for window and overlap with which option : minimal area or union?
I used: WINDOW size 10 and minimum overlap area of 20%
I missed to mention one thing-- The other networks have the full time series of the merging and splitting events but, this particular trajectory has an issue in its last 117 observation (which counts for 43 days) and the last 117 observations got overwritten by the first 43 days
Hi Antione,
I have adapted the latest version and followed the recommendation in issue https://github.com/AntSimi/py-eddy-tracker/issues/183 but still the problem remains the same! We only see the segmentation of the first few days (which is not true because I have monitored manually how this particular eddy is like in its whole lifetime).
Further, this is not the only case where the segmentation looks slightly strange. I have also seen a few other examples with slightly similar issues.
Could you please help me with understanding the issue?
Hi Antione,
I have a issue regarding the segments including next_obs and previous_obs in the network file. I have selected a network (Figure 01) and I wanted to see the merging and spiltting with the timeseries (Figure 02 and zoomed in Figure 03) but the figure only show the details of the 1st 43 days and we don't see the merging or splitting event occuring in the later stage of the choosen network! Could you please help me to understand why it is so?
Many Thanks…