You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello again.
Sorry for the recent deluge of questions.
I am currently using SS1 version of SAVI to collect some dataset based on the oracle actions.
For each trajectory, I am also interested in knowing which scene / room the agent is current moving in.
To this end, I inspected the envs object created with the constuct_envs() function as in ppo_trainer.py, and came up with the following function to recover the scene id of a given environment:
defget_env_scene_id(envs, env_idx):
# NOTE: might be different if using other wrapper like SYNC_ENV or VecEnvreturnenvs.workers[env_idx]._env._env.current_episode.scene_id.split("/")[3]
# return envs.workers[env_idx]._env._env._task._sim._current_scene.strip("data/scene_datasets/mp3d").split("/")[0]
However, when collection a few trajectories (around a 100), then plotting their top_down_map, the same scene id will sometime have different maps:
For example, there is the scene PX4nDJXEHrG which has give me two different maps, as per the screenshot below:
Or the scene E9uDoFAP3SH that also exhibits two different maps:
Would really appreciate if there was a more reliable method to recover the scene id from the running simulation.
Thanks a lot for your time.
The text was updated successfully, but these errors were encountered:
Hello again.
Sorry for the recent deluge of questions.
I am currently using SS1 version of SAVI to collect some dataset based on the oracle actions.
For each trajectory, I am also interested in knowing which scene / room the agent is current moving in.
To this end, I inspected the
envs
object created with theconstuct_envs()
function as inppo_trainer.py
, and came up with the following function to recover the scene id of a given environment:However, when collection a few trajectories (around a 100), then plotting their top_down_map, the same scene id will sometime have different maps:
For example, there is the scene
![image](https://private-user-images.githubusercontent.com/21224272/241965469-abb42cef-ca0e-4ba1-af37-66497c05e6a1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU0OTE1MTMsIm5iZiI6MTcyNTQ5MTIxMywicGF0aCI6Ii8yMTIyNDI3Mi8yNDE5NjU0NjktYWJiNDJjZWYtY2EwZS00YmExLWFmMzctNjY0OTdjMDVlNmExLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA0VDIzMDY1M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA4ODNlZWZmY2Q2NjNjNWFmYzVlMGNlNWE0OTMyMDA1NjVkOTIxODNjNzE5ZDVlNGE1MGZkZjEwOTI4YmNlNTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ncnZrF2dfCxRrUyNpbjZOF6HgxdhHm0We2f7ezizNLw)
PX4nDJXEHrG
which has give me two different maps, as per the screenshot below:Or the scene
![image](https://private-user-images.githubusercontent.com/21224272/241965850-02f7194d-83c5-47ce-8265-953bbfe22dd6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU0OTE1MTMsIm5iZiI6MTcyNTQ5MTIxMywicGF0aCI6Ii8yMTIyNDI3Mi8yNDE5NjU4NTAtMDJmNzE5NGQtODNjNS00N2NlLTgyNjUtOTUzYmJmZTIyZGQ2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTA0VDIzMDY1M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWRkNDU2MmQxNGQ5NTk2YWVlOTNiZTI4ZGRmNDA3OThkMjc1NTY3YjNiOTU0NGY3NGIyYjM5MGVmODBiY2NlMTQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.lupLKKQTnUk4Von2JGDG2QNxD4QyX3nJjlMncRQw7xM)
E9uDoFAP3SH
that also exhibits two different maps:Would really appreciate if there was a more reliable method to recover the scene id from the running simulation.
Thanks a lot for your time.
The text was updated successfully, but these errors were encountered: