Closed nehalmamgain closed 2 years ago
Hey Tyler!
We chose to have GenericMetadata because metadata is something that can change over time due to our interest (tags our data scientists are interested in for AL/auto-labeling) and the heterogeneity of sensors. We'd much rather that metadata exist as key, value pairs than have field numbers which could possibly be a pain to maintain backward-compatibility with over time.
Hi Kuan! Thanks for your comments!
I imagine it's some other Parallel Domain dataset (I don't know which - maybe James or Quincy could tell) that uses the messages currently on this repository under metadata.proto. Those metadata are not at all used in another dataset of interest we have (for lane lines). Let me share specifically what the metadata looks like with you and Tyler over Slack.
@tk-woven
Do we anticipate changing the schema so often that this feature does not suit our needs?
Unfortunately, yes. There are a lot of tags in our initial request (which PD cannot render right now and we have an even more detailed one (~200) for the real dataset). As PD's assets mature, the metadata can definitely grow into more fine-grained options.
Sorry, continuing the discussion on Slack to discuss specifics, since this is public repo 🙂
@kuanleetri Yes, as per the schema we agreed upon on Slack, I will take that to PD. Thank you! Waiting on Quincy's comments for any further changes.
This change is![Reviewable](https://reviewable.io/review_button.svg)