Skip to content

Fix metrics setter#21

Merged
tomonorman merged 3 commits intomainfrom
fix-metrics-setter
Feb 24, 2026
Merged

Fix metrics setter#21
tomonorman merged 3 commits intomainfrom
fix-metrics-setter

Conversation

@tomonorman
Copy link
Copy Markdown
Contributor

I dont believe there is a good way to have the artefacts.yaml look for the tmp dir (of the run) where metrics.json was being placed beforehand. This PR just changes the location of where metrics are being placed to the root of the repo. As a result shows up properly on the project page in dashboard.

Screenshot from 2026-02-24 14-33-31

Also updated the readme with a clarification of why artefacts is not part of the uv environment (psutil discrepancy, where isaac is using quite an old version)

@tomonorman tomonorman requested review from azazdeaz and fabid February 24, 2026 05:39
Copy link
Copy Markdown
Member

@azazdeaz azazdeaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@tomonorman tomonorman merged commit c0e10a6 into main Feb 24, 2026
1 check passed
@tomonorman tomonorman deleted the fix-metrics-setter branch February 24, 2026 09:27
Copy link
Copy Markdown

@fabid fabid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you. Does it mean we should consider updating the artefacts.yaml spec/ CLI to better support the ARTEFACTS_UPLOAD_DIR, especially since we want to deprecated ros topic based metrics

@tomonorman
Copy link
Copy Markdown
Contributor Author

Indeed. A simple one could just be allowing environment variables in the yaml file. I attempted but didnt have any luck.
We could also default to looking the DIR for a metrics.json so no key in yaml would be necessary, unless user is putting it somewhere else / naming it something else

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants