-
Notifications
You must be signed in to change notification settings - Fork 5
added why.md for the environments #23
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
base: main
Are you sure you want to change the base?
Conversation
bastoica
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused as why you added a new WHY.md for arteval_bench. Is this simply the existing file or did you make any edits? Thanks!
|
Hi @bastoica sorry for the confusion the arteval benchmark file is same, it is error from my side that it looks like a new file in commit, but it is the same |
Signed-off-by: Yogesh <yogeshsingla481@gmail.com>
|
sounds good, thanks @yogesh1801 |
|
@tareknaser can you help review if the new WHY.md make sense to you? |
|
@Qian-Cheng-nju can you help review if the new WHY.md of SysMoBench works for you? Welcome any comments. |
Updated the number of systems and their types in the benchmark description.
We recently added the ringbuffer module from Asterinas and ZooKeeper, so I updated the description of the number and types of systems. Everything looks good to me now. Thank you very much for such a detailed document! |
Description
This PR addresses Issue #22 by adding dedicated WHY.md files to each benchmark directory and linking them from the root README. These files explain why each benchmark matters and how it fits into the broader vision of system intelligence, following the pattern established in PR #21.
Changes
Testing
Checklist