\nGeneral meaning
\nEgocentrism is the inability to differentiate between self and others.
\n
![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F636669%2F722d9e9efe7e8d9ccc6741bd9b5e7c6c%2F220px-Egocentrism1.Musfica.png?generation=1599625587272191&alt=media\")
\nImage from wikipedia
Kindly may I know the reason behind the prefix dataset name with \"ego\" by the Lyft team? any specific context here?
\nGeneral meaning
\nEgocentrism is the inability to differentiate between self and others.
\n
\nImage from wikipedia
Kindly may I know the reason behind the prefix dataset name with \"ego\" by the Lyft team? any specific context here?
\nGeneral meaning
\nEgocentrism is the inability to differentiate between self and others.
\n
\nImage from wikipedia
\"ego\" describes the Automated Vehicle (AV) with the sensor suite. All other vehicles are \"agents\" are perceived by this AV.
\nThus, the position/yaw etc. values for \"ego\" are much more precise.
@ilu000 Thanks for the response. Your clarification made me to get another question. Even an ego vehicle can be an agent with respect to another ego vehicles. is my understanding right?
", "rawMarkdown": "ilu000 Thanks for the response. Your clarification made me to get another question. Even an ego vehicle can be an agent with respect to another ego vehicles. is my understanding right?", "votes": null }, { "id": "1004089", "postDate": "09/09/2020 12:58:17", "content": "Technically, yes. Everything around the AV is considered an agent from our perception stack. This means that if another AV was around collecting data at the same time, it will be regarded as yet another agent by the first AV
", "rawMarkdown": "Technically, yes. Everything around the AV is considered an agent from our perception stack. This means that if another AV was around collecting data at the same time, it will be regarded as yet another agent by the first AV", "votes": null }, { "id": "1004171", "postDate": "09/09/2020 14:07:56", "content": "@lucabergamini Thank you. Make Sense!
", "rawMarkdown": "lucabergamini Thank you. Make Sense!", "votes": null }, { "id": "1004185", "postDate": "09/09/2020 14:16:42", "content": "But still, I am trying to understand yaw angle, transformations, perturbation, etc by looking at l5kit code
", "rawMarkdown": "But still, I am trying to understand yaw angle, transformations, perturbation, etc by looking at l5kit code", "votes": null }, { "id": "1004213", "postDate": "09/09/2020 14:39:23", "content": "About yawl angle, lk5kit etc. all is explained in this kernel https://www.kaggle.com/corochann/lyft-deep-into-the-l5kit-library . It also explains all about ego and agents
", "rawMarkdown": "About yawl angle, lk5kit etc. all is explained in this kernel https://www.kaggle.com/corochann/lyft-deep-into-the-l5kit-library . It also explains all about ego and agents", "votes": null } ], "comments": [ { "id": 1003761, "author_name": "ilu000", "author_url": "", "post_date": "09/09/2020 08:19:36", "content": "\"ego\" describes the Automated Vehicle (AV) with the sensor suite. All other vehicles are \"agents\" are perceived by this AV.
\nThus, the position/yaw etc. values for \"ego\" are much more precise.
@ilu000 Thanks for the response. Your clarification made me to get another question. Even an ego vehicle can be an agent with respect to another ego vehicles. is my understanding right?
", "votes": null, "replies": [] }, { "id": 1004089, "author_name": "lucabergamini", "author_url": "", "post_date": "09/09/2020 12:58:17", "content": "Technically, yes. Everything around the AV is considered an agent from our perception stack. This means that if another AV was around collecting data at the same time, it will be regarded as yet another agent by the first AV
", "votes": null, "replies": [] }, { "id": 1004171, "author_name": "pallaviroyal", "author_url": "", "post_date": "09/09/2020 14:07:56", "content": "@lucabergamini Thank you. Make Sense!
", "votes": null, "replies": [] }, { "id": 1004185, "author_name": "pallaviroyal", "author_url": "", "post_date": "09/09/2020 14:16:42", "content": "But still, I am trying to understand yaw angle, transformations, perturbation, etc by looking at l5kit code
", "votes": null, "replies": [] }, { "id": 1004213, "author_name": "mclikmb4", "author_url": "", "post_date": "09/09/2020 14:39:23", "content": "About yawl angle, lk5kit etc. all is explained in this kernel https://www.kaggle.com/corochann/lyft-deep-into-the-l5kit-library . It also explains all about ego and agents
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "1003530": "Kindly may I know the reason behind the prefix dataset name with \"ego\" by the Lyft team? any specific context here?\nGeneral meaning \nEgocentrism is the inability to differentiate between self and others.\n\nImage from wikipedia", "1003761": "\"ego\" describes the Automated Vehicle (AV) with the sensor suite. All other vehicles are \"agents\" are perceived by this AV.\nThus, the position/yaw etc. values for \"ego\" are much more precise.", "1003972": "ilu000 Thanks for the response. Your clarification made me to get another question. Even an ego vehicle can be an agent with respect to another ego vehicles. is my understanding right?", "1004089": "Technically, yes. Everything around the AV is considered an agent from our perception stack. This means that if another AV was around collecting data at the same time, it will be regarded as yet another agent by the first AV", "1004171": "lucabergamini Thank you. Make Sense!", "1004185": "But still, I am trying to understand yaw angle, transformations, perturbation, etc by looking at l5kit code", "1004213": "About yawl angle, lk5kit etc. all is explained in this kernel https://www.kaggle.com/corochann/lyft-deep-into-the-l5kit-library . It also explains all about ego and agents" }, "source": "meta" }