Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log Used Soft- and Hardware and Wall-Clock Time #24

Open
3 tasks
fsschneider opened this issue Feb 19, 2020 · 0 comments
Open
3 tasks

Log Used Soft- and Hardware and Wall-Clock Time #24

fsschneider opened this issue Feb 19, 2020 · 0 comments
Assignees
Labels
⚗️ Other: Good First Issue Good issue to try out for newcomers 👷 Status: In Progress Issue is being worked on ✨ Type: Feature Request New feature or request

Comments

@fsschneider
Copy link
Owner

  • Runners should also log the wall-clock time for logged values. We can extract the aforementioned time to achieve a target error in the post-processing step.
  • For completeness, and as DeepOBS is still being developed, it would be good to track version and hardware information in the same .json file (e.g. torch, torchvision, deepobs, tensorflow versions + hardware info)

To Do

We will do the following steps for version 1.2.0:

  • Add logging of wall-clock time.
  • Add logging of used software.
  • Add logging of used hardware.
@fsschneider fsschneider added ✨ Type: Feature Request New feature or request 👷 Status: In Progress Issue is being worked on ⚗️ Other: Good First Issue Good issue to try out for newcomers labels Feb 19, 2020
@fsschneider fsschneider added this to the 📦 Version 1.2.0 milestone Feb 19, 2020
@fsschneider fsschneider self-assigned this Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚗️ Other: Good First Issue Good issue to try out for newcomers 👷 Status: In Progress Issue is being worked on ✨ Type: Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant