-
Notifications
You must be signed in to change notification settings - Fork 259
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
Clarify if hardware type is equal to hardware requirements in the specification #1121
Comments
Interesting! My understanding is that "hardware type" times the "hours" gives an approximation for the total amount of compute, which is a very interesting figure to report. What do you think is important to cover in the "hardware requirements" field? cc @davanstrien for insight. |
Looking at schema.org (which is often used as a reference to describe many resources in the web). They have:
If you clarify somewhere in the doc that you are only referring that the hardware recorded is the GPU type, and that "hardware type" times the "hours" is the approx time of compute (i.e., RAM, DISK are not addressed), that would really help a lot. Thanks in advance! |
I think @EziOzoani and @meg-huggingface are probably the best people to answer this. |
Thank you so much for noticing this issue, @dgarijo !
The updated template is here: |
Thanks! Closing the issue then |
changes to differentiate between the different uses of hardware This is Part 2 of the updates to address [this issue](huggingface#1121)
Is your feature request related to a problem? Please describe.
We are reviewing the model card specification in order to adopt it. However,
Hardware Type
andhardware requirements
have the same keyhardware
. We believe these entries are not the same, as I can require 2 GB of RAM and 2 H100 GPUs for running a model, but the the hardware_type is justGPU H100
. Can you please clarify the intended use in the current documentation? (for hardware requirements there is no definition)Describe the solution you'd like
Clarify if
hardware_type
andhardware requirements
are mapped to the same keyhardware
Thanks!
The text was updated successfully, but these errors were encountered: