NVIDIA / NVIDIA/simready-foundation

question/clarification on data/types for aif compute rack

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
88
Forks
18
PR merge metrics
No merged PRs in 30d

Description

Some questions on the specification, which define

aif:spec:requiredAirFlowRate | float3_array | m³/s | Required air flow rate curve [Inlet Temp (°C), Flow]
aif:spec:requiredLiquidFlowRate | float3_array | LPM | Required liquid flow rate curve [Inlet Temp (°C), Flow (L/s), Flow (LPM)]

requiredAirFlowRate is specified as float3_array - this appears to contain multiple sub-typed values. The description only lists two values, Inlet Temp (C) and Flow.

requiredLiquidFlowRate desribes three values, temp(C), FLow (L/s) and Flow (LPM).

Three questions

  1. On the former (air), I assume the second value Flow has units m^3/s? It isnt detailed in the specification (see above)
  2. What is the third value in this float3 {inlettemp, flow, ???}, name and units?
  3. On the latter (liquid), what's the difference between the 2nd and 3rd values - Flow(L/s) and Flow (LPM*)

*LPM as an acronym can mean many things - Lines Per Minute (printers) for example :) L/min appears to be the accepted way of writing Litres/min (fluid volume flow). Is it the case that value 2 (Flow) is L/s (litres per second) and the third is Flow in L/min?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or code entry point is identified. Start by locating the AIF compute-rack specification and verifying the float3_array definitions and units with the specification owners; done means the three questions have authoritative answers and the specification is clarified where needed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.