AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Open Neural Network Exchange (ONNX) is an open ecosystem that empowers AI developers
to choose the right tools as their project evolves. ONNX provides an open source format for AI models, both deep learning and traditional ML. It defines an extensible computation graph model, as well as definitions of built-in operators and standard
data types. Currently we focus on the capabilities needed for inferencing (scoring).README 전문 보기 ↗Open Neural Network Exchange (ONNX) is an open ecosystem that empowers AI developers to choose the right tools as their project evolves. ONNX provides an open source format for AI models, both deep learning and traditional ML. It defines an extensible computation graph model, as well as definitions of built-in operators and standard data types. Currently we focus on the capabilities needed for inferencing (scoring).
ONNX is widely supported and can be found in many frameworks, tools, and hardware. Enabling interoperability between different frameworks and streamlining the path from research to production helps increase the speed of innovation in the AI community. We invite the community to join us and further evolve ONNX.
ONNX is a community project and the open governance model is described here. We encourage you to join the effort and contribute feedback, ideas, and code. You can participate in the Special Interest Groups and Working Groups to shape the future of ONNX.
Check out our contribution guide to get started.
Support community participation by contributing to the ONNX Community Travel Fund.
If you think some operator should be added to ONNX specification, please read this document.
The schedules of the regular meetings of the Steering Committee, the working groups and the SIGs can be found here
Community Meetups are held at least once a year. Content from previous community meetups are at:
We encourage you to open Issues, or use Slack (If you have not joined yet, please use this link to join the group) for more real-time discussion.
Stay up to date with the latest ONNX news. [Facebook] [Twitter/X]
A roadmap process takes place every year. More details can be found in ROADMAP.md.
ONNX released packages are published in PyPi.
pip install onnx # or pip install onnx[reference] for optional reference implementation dependencies
ONNX weekly packages are published in PyPI to enable experimentation and early testing.
Detailed install instructions, including Common Build Options and Common Errors can be found here
This package provides abi3-compatible wheels, allowing a single binary wheel to work across multiple Python versions (from 3.12 onwards).
ONNX uses pytest as test driver. In order to run tests, you will first need to install pytest:
pip install pytest
After installing pytest, use the following command to run tests.
pytest
Check out the contributor guide for instructions.
ONNX build and release workflows set
SOURCE_DATE_EPOCH
to the source commit timestamp. This removes timestamp-dependent variation from
supported build steps and makes independent build comparison easier.
SOURCE_DATE_EPOCH alone does not guarantee byte-for-byte identical artifacts
across different environments. A reproducibility check must also use the same
source revision, dependency versions, toolchain, target platform, and build
configuration, and then compare the resulting artifacts.
A fixed build timestamp removes one known source of nondeterminism. When independent builds use the same controlled inputs, their artifacts can be compared byte for byte, with cryptographic digests providing a practical shortcut. A byte-for-byte match demonstrates identical outputs, while a mismatch identifies a difference that needs investigation. This comparison complements release provenance attestations; it does not replace them.
Release artifacts are available from PyPI.
Checkout https://trademarks.justia.com for the trademark.
General rules of the Linux Foundation on Trademark usage