Skip to content

Add Trajectory Visualizer v.20#18

Open
bhavul wants to merge 1 commit intofacebookresearch:mainfrom
bhavul:patch-2
Open

Add Trajectory Visualizer v.20#18
bhavul wants to merge 1 commit intofacebookresearch:mainfrom
bhavul:patch-2

Conversation

@bhavul
Copy link
Copy Markdown
Contributor

@bhavul bhavul commented May 16, 2025

Many upgrades - categorisation, search, filters, raw logs available, slurm logs dynamically available if present.

  1. tasks are categorised in side panel
  2. filters available for model and task type
  3. raw logs also present in a collapsible container to check
  4. every trajectory has a proper URL, so you can share direct URL with someone
  5. search box — where you can search any substring of the run name.
  6. Slurm logs available if slurm output and error files were present in the trajectory DIR. Otherwise they're skipped.
  7. Different trajectories have different URLs now, so you can easily share a particular trajectory link with someone.

Tested via : streamlit run demo/trajectory_visualizer.py -- --trajectory_dir ./trajectories/bhavul/ on devserver.

496508881_665098449742952_8240494688657101130_n
496511619_1747213486228709_7436414439405224347_n
494572391_1747651125849212_6764779885767853126_n
496509799_682945974469344_4504116092854572672_n

Many upgrades - categorisation, search, filters, raw logs available, slurm logs dynamically available if present
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Meta Open Source bot. label May 16, 2025
@deepakn97
Copy link
Copy Markdown
Contributor

Screenshot 2025-05-19 at 3 54 24 PM
The thought process is rendered outside the block. Should fix this.

@deepakn97
Copy link
Copy Markdown
Contributor

The test command and the files changed don't match. It is mentioned that the changes were tested using demo/trajectory_visualizer.py, however the changes are in demo/demo.py.
These two files serve different purposes. Demo is meant to be a automated demo where the users don't have to click through the next step and previous step buttons and should be used when making a demo video etc. Whereas trajectory visualizer is supposed to be used for stepping through the actions and thought process of the agent by a user.

Not sure what is the intended change here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants