We have 500 image pairs (+ masks) that we could be using to supplement our Unity dataset.
The question is now whether this data is similar enough to the Unity dataset to be used in the same domain, or whether it warrants a separate domain.
I feel that given the utter heterogeneity of our real dataset (Mapillary dashcam vs. GSV data vs. user data), it's ok to have a certain amount of heterogeneity in the simulated data too. But this needs to be tested, either by plotting the distribution of Unity vs. WD2 (e.g. embedding them using Inception?) or doing some ablation studies to see how it can complement the Unity data.
We have 500 image pairs (+ masks) that we could be using to supplement our Unity dataset.
The question is now whether this data is similar enough to the Unity dataset to be used in the same domain, or whether it warrants a separate domain.
I feel that given the utter heterogeneity of our real dataset (Mapillary dashcam vs. GSV data vs. user data), it's ok to have a certain amount of heterogeneity in the simulated data too. But this needs to be tested, either by plotting the distribution of Unity vs. WD2 (e.g. embedding them using Inception?) or doing some ablation studies to see how it can complement the Unity data.