diff --git a/.github/meeting-notes-template.rst b/.github/meeting-notes-template.rst index 4cc1998..d8d33da 100644 --- a/.github/meeting-notes-template.rst +++ b/.github/meeting-notes-template.rst @@ -1,28 +1,28 @@ Meeting title -============= +=============== Date: YYYY-MM-DD Attendees ---------- +----------- Agenda ------- +-------- Discussion ----------- +------------ Decisions ---------- +----------- Record approved decisions separately from proposals and open questions. Actions -------- +--------- For each action, record the agreed owner, next step and target date or issue. Materials and recording ----------------------- +------------------------- Add presentation links and recording access details. Update the meeting index. diff --git a/.github/scripts/check_document_structure.py b/.github/scripts/check_document_structure.py new file mode 100644 index 0000000..d7d637f --- /dev/null +++ b/.github/scripts/check_document_structure.py @@ -0,0 +1,49 @@ +"""Validate RST rendering and coverage of dated records in sibling indexes.""" +import io +from pathlib import Path +import re +import sys +from docutils import nodes +from docutils.core import publish_doctree + + +def check(root): + errors = [] + retired = re.compile( + r'https?://(?:spec\.oneapi\.(?:com|io)|oneapi-spec\.uxlfoundation\.org)' + r'|https?://(?:github\.com|uxlfoundation\.github\.io)/[^\s<>]*' + r'(?:oneapi-spec(?:[/#?]|\b)|spec-working-group)' + r'|specification\s+working\s+group', re.IGNORECASE) + for path in root.rglob('*'): + if path.suffix not in {'.md', '.rst'} or '.git' in path.relative_to(root).parts: + continue + for number, line in enumerate(path.read_text(encoding='utf-8').splitlines(), 1): + if retired.search(line): + errors.append(f'{path.relative_to(root)}:{number}: retired specification reference; use the UXL dynamic specification') + for path in sorted(root.rglob('*.rst')): + if '.git' in path.relative_to(root).parts: + continue + source = path.read_text(encoding='utf-8') + tree = publish_doctree(source, settings_overrides={ + 'halt_level': 6, 'report_level': 5, 'warning_stream': io.StringIO(), + 'raw_enabled': False, 'file_insertion_enabled': False, + }) + for message in tree.findall(nodes.system_message): + if message['level'] >= 2: + errors.append(f'{path.relative_to(root)}:{message.get("line", "?")}: {message.astext()}') + if re.match(r'\d{4}-\d', path.name): + index = path.parent / 'README.rst' + if index.exists(): + # Match actual inline links, not incidental mentions of the filename. + links = re.findall(r'<([^<>\n]+)>`_{1,2}', index.read_text(encoding='utf-8')) + if path.name not in links: + errors.append(f'{path.relative_to(root)}: missing from {index.relative_to(root)}') + return errors + + +if __name__ == '__main__': + errors = check(Path.cwd()) + for error in errors: + print(error) + print(f'Document structure: {len(errors)} error(s).') + sys.exit(bool(errors)) diff --git a/.github/scripts/test_document_structure.py b/.github/scripts/test_document_structure.py new file mode 100644 index 0000000..f7a647c --- /dev/null +++ b/.github/scripts/test_document_structure.py @@ -0,0 +1,38 @@ +from pathlib import Path +import tempfile +import unittest +from check_document_structure import check + + +class StructureChecks(unittest.TestCase): + def test_retired_destination_and_current_specification(self): + with tempfile.TemporaryDirectory() as directory: + root = Path(directory) + page = root / 'README.md' + page.write_text('[Spec](https://github.com/uxlfoundation/oneAPI-spec)\n', encoding='utf-8') + self.assertTrue(any('retired specification' in e for e in check(root))) + page.write_text('[Spec](https://uxlfoundation.org/specifications/oneapi/technical-overview/)\n', encoding='utf-8') + self.assertEqual(check(root), []) + + def test_malformed_heading(self): + with tempfile.TemporaryDirectory() as directory: + root = Path(directory) + (root / 'README.rst').write_text('Long heading\n==========\n', encoding='utf-8') + self.assertTrue(check(root)) + + def test_wrong_existing_record_does_not_cover_omitted_record(self): + with tempfile.TemporaryDirectory() as directory: + root = Path(directory) + for date in ['2024-09-05', '2024-09-19']: + (root / f'{date}.rst').write_text('Meeting\n=======\n', encoding='utf-8') + index = root / 'README.rst' + index.write_text('`September 5 <2024-09-05.rst>`__\n\n' + '`September 19 <2024-09-05.rst>`__\n', encoding='utf-8') + self.assertTrue(any('2024-09-19.rst: missing' in e for e in check(root))) + index.write_text('`September 5 <2024-09-05.rst>`__\n\n' + '`September 19 <2024-09-19.rst>`__\n', encoding='utf-8') + self.assertEqual(check(root), []) + + +if __name__ == '__main__': + unittest.main() diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 6051795..c058e8e 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -14,7 +14,11 @@ jobs: - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4 with: persist-credentials: false - - name: Test link checker + - name: Install documentation parser + run: python3 -m pip install docutils==0.19 + - name: Test documentation checks run: python3 -m unittest discover -s .github/scripts -p 'test_*.py' - name: Check local links run: python3 .github/scripts/check_local_links.py + - name: Check document structure + run: python3 .github/scripts/check_document_structure.py diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1b83213..fb6b000 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -42,3 +42,8 @@ a new license or change governance or contribution terms. Ask foundation operations to confirm applicable terms before importing third-party material. Report security vulnerabilities through the affected project's private reporting channel or security policy, rather than posting details in a public issue. + +For rendering and meeting-index checks, install `docutils==0.19` and run +`python .github/scripts/check_document_structure.py`. The check reports malformed +reStructuredText and dated records missing from sibling indexes. External URLs +and cross-document section anchors still require review. diff --git a/PROJECTS.md b/PROJECTS.md index 32113ac..7094c7b 100644 --- a/PROJECTS.md +++ b/PROJECTS.md @@ -4,7 +4,7 @@ Six core libraries provide building blocks for accelerated computing. Choose by the work you need to do, then use the project's documentation for installation, examples and supported platforms. -[Foundation home](README.md) · [Working Group](https://github.com/uxlfoundation/open-source-working-group) · [oneAPI specification](https://uxlfoundation.org/specifications/oneapi/technical-overview/) +[Foundation home](README.md) · [Working Group](https://github.com/uxlfoundation/open-source-working-group) · [Dynamic oneAPI specification](https://uxlfoundation.org/specifications/oneapi/technical-overview/) ## Choose a library diff --git a/README.md b/README.md index 656879e..c6de5f7 100644 --- a/README.md +++ b/README.md @@ -64,7 +64,7 @@ are available for [Image](image/README.rst) and | --- | --- | | [Foundation charter](doc/uxl-foundation-charter.rst) | Mission, projects and participation | | [Steering Committee](steering-committee/README.rst) | Governance and published meeting minutes | -| [oneAPI specification](https://uxlfoundation.org/specifications/oneapi/technical-overview/) | Dynamic specification and links to current project documentation | +| [Dynamic oneAPI specification](https://uxlfoundation.org/specifications/oneapi/technical-overview/) | Dynamic specification and links to current project documentation | | [Community operations](doc/README.rst) | Meeting guidance, GitHub, Slack and web hosting | | [Status report archive](monthly-status/) | Dated foundation updates | diff --git a/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst b/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst index 7be2fbe..1f41f87 100644 --- a/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst +++ b/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst @@ -3,22 +3,22 @@ AI Special Interest Group Meeting Notes ========================================= 2024-03-14 -========== +============ -Attendees +Attendees * Nikolay Petrov (Intel) * Darshan Patel (Fujitsu) -* Daniel Holmes +* Daniel Holmes * Abhishek Nair (Fujitsu) * Mourad Gouicem (Intel) -* Shashank Sangu +* Shashank Sangu * Giovanni Grandi (Codasip s.r.o.) -* Jose Fonseca +* Jose Fonseca * Deeksha Goplani (Fujitsu) * Rumpf Mr * Mehdi Goli (Codeplay) -* John Melonakos +* John Melonakos * Alison Richards (Intel) * Balas, DorotheeX Marie Clotilde * Chandan Sharma (Fujitsu) @@ -30,15 +30,15 @@ Attendees * Peter Robertson (Codasip s.r.o.) * Ronan Keryell (AMD) * Ruyman Reyes Castro (Codeplay) -* Sasank Chilamkurthy +* Sasank Chilamkurthy * Dave Murray (Imagination Technologies) * Jianhui Li (Intel) -* Kevan Ahmadi +* Kevan Ahmadi * Roman Zhukov (Intel) * Rod Burns (Codeplay) * Chao Chen (Intel) * Nishant Prabhu (Fujitsu) -* Stephen Porter +* Stephen Porter * Robert Cohn (Intel) * Divya Kota (Accenture) * Charles Tuke (Imagination Technologies) @@ -46,27 +46,28 @@ Attendees * Md. Abdullah Shahneous Bari (Intel) * Masahiro Doteguchi (Fujitsu) * Penporn Koanantakool (Google) -Agenda - - + +Agenda - + * Enabling oneDAL on ARM target Chandan Sharma (`slides `__) * oneDNN overview and update Mourad Gouicem (`slides `__) -* Discussion (motivation, expectation, future topics) +* Discussion (motivation, expectation, future topics) + +Question: Fujitsu extended oneDAL to use OpenBLAS library to enable ARM target. oneDAL uses private MKL interface. Will oneDAL use public MKL interface? +Will MKL be open source? -Question: Fujitsu extended oneDAL to use OpenBLAS library to enable ARM target. oneDAL uses private MKL interface. Will oneDAL use public MKL interface? -Will MKL be open source? +Answer: oneDAL uses MKL interface as it needs to use the SYCL interface. oneDAL plans to use oneMKL interface and MKL can be its backend math library. There is no plan to open source MKL. -Answer: oneDAL uses MKL interface as it needs to use the SYCL interface. oneDAL plans to use oneMKL interface and MKL can be its backend math library. There is no plan to open source MKL. +Question: What is the reason of using OpenBlas, not ARM compute library (ACL)? -Question: What is the reason of using OpenBlas, not ARM compute library (ACL)? - -Answer: Fujisu choose OpenBlas because OpenBlas is more “Open”. +Answer: Fujisu choose OpenBlas because OpenBlas is more “Open”. -Answer: I am Christopher Rumph and part of UXL steering committee as ARM representative. ARM compute library is open source project, but not run as “open governance” model. I can help discuss with ARM colleagues to enable you on what you try to achieve. Potentially ACL could be oneMKL’s backend. +Answer: I am Christopher Rumph and part of UXL steering committee as ARM representative. ARM compute library is open source project, but not run as “open governance” model. I can help discuss with ARM colleagues to enable you on what you try to achieve. Potentially ACL could be oneMKL’s backend. -Question: Is oneDNN Graph API stable and officially supported? +Question: Is oneDNN Graph API stable and officially supported? -Answer: Yes. oneDNN Graph is an official feature of oneDNN. oneDNN Graph API is stable API, and there is an official backend using oneDNN primitives. The oneDNN Graph compiler backend is an experimental feature. +Answer: Yes. oneDNN Graph is an official feature of oneDNN. oneDNN Graph API is stable API, and there is an official backend using oneDNN primitives. The oneDNN Graph compiler backend is an experimental feature. -Question: What does it take to optimize oneDNN to other targets? +Question: What does it take to optimize oneDNN to other targets? Answer: There are three levels. The first approach is to map the API to external library (e.g. ARM backend relies on ACL, Nvidia backend relies on cuDNN/cuBLAS, ...), the second one is to add C++/SYCL implementations with targeted optimizations (e.g. RISC-V RVV optimized Matmul), and the third one is to add jitting capabilites and jit kernel generators (e.g. x64 support contributed by Intel and SVE support contributed by Fujitsu). diff --git a/ai-and-scientific-computing/2025-12-19-UXL-AI-SIG.rst b/ai-and-scientific-computing/2025-12-19-UXL-AI-SIG.rst index 2341707..293d41c 100644 --- a/ai-and-scientific-computing/2025-12-19-UXL-AI-SIG.rst +++ b/ai-and-scientific-computing/2025-12-19-UXL-AI-SIG.rst @@ -3,7 +3,7 @@ ========================================= 2025-12-19 -========= +============ Attendees * Biagio COSENZA (University of Salerno) @@ -22,15 +22,15 @@ Attendees * Alison Richards (Intel Corporation) * En Shao (University of Chinese Academy of Sciences) -====== +======== Agenda -====== +======== **NVIDIA GPU Adaptation for SYCL-MLIR**, **Boyuan Bao**, Beijing Institute of Open Source Chip, (`slides `__) Background and Motivation -========================= +=========================== - **SYCL-MLIR** is an MLIR-based compiler infrastructure for SYCL and heterogeneous programming, designed to keep host code and device kernels in the same MLIR @@ -43,10 +43,10 @@ Background and Motivation later shelved internally and is no longer actively maintained. Technical Contributions -======================= +========================= NVIDIA Built-in Variable Adaptation ------------------------------------ +------------------------------------- - The generated LLVM IR contained references to SPIR-V built-in variables (e.g., thread and block IDs, execution parameters). @@ -62,7 +62,7 @@ NVIDIA Built-in Variable Adaptation while providing a cleaner abstraction. Kernel Entry Point Handling ---------------------------- +----------------------------- - Kernel attributes were added to ensure that backend compilation pipelines correctly identify kernel entry points. @@ -70,7 +70,7 @@ Kernel Entry Point Handling device kernels. Pipeline Integration --------------------- +---------------------- - The current compilation flow is not yet fully unified: - Front-end: SYCL source is lowered to MLIR/LLVM using existing front-end tooling (e.g., cgeist-based flow). @@ -79,7 +79,7 @@ Pipeline Integration stages, enabling generation of executable binaries for NVIDIA GPUs. Results and Validation -===================== +======================== - Correctness was validated using **SYCLBench** and **PolyBench** test suites. - Most benchmarks executed successfully on NVIDIA GPUs. @@ -87,23 +87,23 @@ Results and Validation The focus was on functional correctness and backend enablement. Q&A and Strategic Discussion -============================ +============================== Performance Evaluation ----------------------- +------------------------ - **Ettore Tiotto** noted that performance comparison against a baseline (without SYCL-MLIR translation) would be a natural next step. - The presenters confirmed that performance analysis has not yet been performed. Future Backend Support ----------------------- +------------------------ - The team plans to explore additional backends, including **AMD GPUs**. - It was noted that the AMD path should be similar, using ROCDL-based lowering. Maintenance and Upstreaming Strategy ------------------------------------- +-------------------------------------- - The team asked whether to contribute the NVIDIA backend through Intel’s existing repository or via UXL processes. @@ -112,7 +112,7 @@ Maintenance and Upstreaming Strategy - Forking removes reliance on Intel-internal CI infrastructure and enables independent CI coverage across a broader hardware ecosystem. Front-end Considerations ------------------------- +-------------------------- - **Whitney** asked whether replacing the current front-end (cgeist) with a more standardized MLIR-based front-end such as CIR (Clang IR) was being considered. @@ -122,7 +122,7 @@ Front-end Considerations prototyping or long-term productization. UXL Foundation Process for Adding a Repository ----------------------------------------------- +------------------------------------------------ - **Penporn Koanantakool (Google)** and **Alison Richards (Intel)** explained that proposals for hosting a repository under the UXL Foundation should be brought @@ -132,7 +132,7 @@ UXL Foundation Process for Adding a Repository in determining whether a project is suitable to be hosted under UXL. Announcements -============= +=============== - **UXL Foundation Members Meeting** - Date: **January 15** diff --git a/ai-and-scientific-computing/2026-3-5-UXL-AI-SIG.rst b/ai-and-scientific-computing/2026-3-5-UXL-AI-SIG.rst index a5fb7fa..0c95d20 100644 --- a/ai-and-scientific-computing/2026-3-5-UXL-AI-SIG.rst +++ b/ai-and-scientific-computing/2026-3-5-UXL-AI-SIG.rst @@ -3,7 +3,7 @@ ========================================= 2026-03-05 -========= +============ Attendees @@ -20,75 +20,75 @@ Attendees * Alison Richards (Intel Corporation) * Dmitry Zarukin (Intel Corporation) -====== +======== Agenda -====== +======== -**oneDNN Updates: Async Threadpool, Grouped GEMM, and MXFP/NVFP**, +**oneDNN Updates: Async Threadpool, Grouped GEMM, and MXFP/NVFP**, **Dmitry Zarukin**, Intel Corporation, (`slides `__) Summary -======= +========= RISC-V Enablement ------------------ +------------------- -- Growing community contributions with initial optimized kernels and maintainers onboard -- Current support focuses on floating-point inference workloads -- Validation relies on contributor-provided testing (no official CI yet) +- Growing community contributions with initial optimized kernels and maintainers onboard +- Current support focuses on floating-point inference workloads +- Validation relies on contributor-provided testing (no official CI yet) Quantization Enhancements (INT & Low-Precision FP) --------------------------------------------------- +---------------------------------------------------- -- Expanded support for INT4/INT8 weight compression with flexible scales and zero-points -- Introduced grouped and 2D quantization schemes to balance accuracy and memory efficiency -- Added MXFP4/MXFP8/NVFP4 formats with dynamic scaling computed at runtime -- Quantization parameters handled separately from tensor buffers (no native “quantized tensor” abstraction) +- Expanded support for INT4/INT8 weight compression with flexible scales and zero-points +- Introduced grouped and 2D quantization schemes to balance accuracy and memory efficiency +- Added MXFP4/MXFP8/NVFP4 formats with dynamic scaling computed at runtime +- Quantization parameters handled separately from tensor buffers (no native “quantized tensor” abstraction) Async Threadpool Runtime ------------------------- +-------------------------- -- New asynchronous execution model (inspired by XLA) decouples task submission from execution -- Improves parallel efficiency by allowing host thread to continue scheduling work -- Requires significant internal changes (lifetime management, lambda capture semantics, memory safety) -- Currently supported on x86 backend; other backends require non-trivial adaptation -- Expected performance improvement ~10% (framework-level gains can be higher) +- New asynchronous execution model (inspired by XLA) decouples task submission from execution +- Improves parallel efficiency by allowing host thread to continue scheduling work +- Requires significant internal changes (lifetime management, lambda capture semantics, memory safety) +- Currently supported on x86 backend; other backends require non-trivial adaptation +- Expected performance improvement ~10% (framework-level gains can be higher) Grouped GEMM / Mixture-of-Experts (MoE) ---------------------------------------- +----------------------------------------- -- Introduced batched/grouped GEMM to support MoE workloads efficiently -- Uses new memory descriptors for sparse/condensed activations -- Enables multiple GEMMs within a single kernel submission -- Targeted for upcoming oneDNN release (v3.2), with primary focus on GPU backend +- Introduced batched/grouped GEMM to support MoE workloads efficiently +- Uses new memory descriptors for sparse/condensed activations +- Enables multiple GEMMs within a single kernel submission +- Targeted for upcoming oneDNN release (v3.2), with primary focus on GPU backend Host-side Scalars ------------------ +------------------- -- Introduced lightweight scalar handling without device memory allocation -- Reduces overhead for small models and scalar-heavy operations (e.g., scales, zero-points) -- Integrated into selected primitives (e.g., SDPA, dropout) +- Introduced lightweight scalar handling without device memory allocation +- Reduces overhead for small models and scalar-heavy operations (e.g., scales, zero-points) +- Integrated into selected primitives (e.g., SDPA, dropout) Discussion Highlights -===================== +======================= -- RISC-V ecosystem maturity and lack of standardized CI/testing -- Trade-offs in quantization accuracy vs. performance and memory -- Async runtime benefits vs. complexity for non-x86 backends -- API usability concerns (e.g., backend detection for async runtime support) -- Interest in performance data for new FP formats and async execution +- RISC-V ecosystem maturity and lack of standardized CI/testing +- Trade-offs in quantization accuracy vs. performance and memory +- Async runtime benefits vs. complexity for non-x86 backends +- API usability concerns (e.g., backend detection for async runtime support) +- Interest in performance data for new FP formats and async execution Action Items / Follow-ups -========================= +=========================== -- Track RISC-V CI and broader ecosystem validation -- Evaluate async threadpool integration across non-x86 backends -- Monitor MXFP/NVFP adoption and performance data -- Follow up on grouped GEMM / MoE integration in frameworks -- Potential deep-dive session on async runtime internals \ No newline at end of file +- Track RISC-V CI and broader ecosystem validation +- Evaluate async threadpool integration across non-x86 backends +- Monitor MXFP/NVFP adoption and performance data +- Follow up on grouped GEMM / MoE integration in frameworks +- Potential deep-dive session on async runtime internals diff --git a/ai-and-scientific-computing/2026-4-23-UXL-AI-and-Scientific-Computing-SIG.rst b/ai-and-scientific-computing/2026-4-23-UXL-AI-and-Scientific-Computing-SIG.rst index 33f4333..5b054b3 100644 --- a/ai-and-scientific-computing/2026-4-23-UXL-AI-and-Scientific-Computing-SIG.rst +++ b/ai-and-scientific-computing/2026-4-23-UXL-AI-and-Scientific-Computing-SIG.rst @@ -3,7 +3,7 @@ =================================================================== 2026-04-23 -========== +============ Attendees @@ -110,16 +110,16 @@ Recording Link **Watch to explore how AI is shaping the future of simulation, modeling, and engineering innovation** (`Recording Link `__) -====== +======== Agenda -====== +======== **About AI & Scientific Computing SIG by Chairs (Penporn and Priyanka)** -**When AI Meets Engineering Design: Constraining Its Creativity for Smarter Vehicle Aerodynamics Design (Prof. Makoto Tsubokura, Kobe University and RIKEN, Japan)**, +**When AI Meets Engineering Design: Constraining Its Creativity for Smarter Vehicle Aerodynamics Design (Prof. Makoto Tsubokura, Kobe University and RIKEN, Japan)**, Summary -======= +========= Overview ----------------- @@ -130,7 +130,7 @@ Overview - This design space utilizes three techniques: parameterized geometry, Principal Component Analysis (PCA), and latent space editing. He covered topics on development of AI surface models and multi-objective optimization to controlled shape refinement. About AI & Scientific Computing SIG ------------------ +------------------------------------- - Priyanka and Penporn hosted the meeting, explaining purpose and vision for AI and Scientific Computing SIG. - They welcomed all AI SIG members and new attendees, explaining that while the focus has been on AI topics for the past few years, interest in scientific computing applications is growing. @@ -138,7 +138,7 @@ About AI & Scientific Computing SIG - Guest speaker Prof. Makoto Tsubokura was introduced to discuss the impact of AI on engineering design. When AI Meets Engineering Design - Talk by Prof. Makoto Tsubokura ------------------ +------------------------------------------------------------------- Title: When AI Meets Engineering Design: Constraining Its Creativity for Smarter Vehicle Aerodynamics Design @@ -154,7 +154,7 @@ Abstract - By projecting these vehicles into the parameter space and applying principal component analysis, we identify a lower dimensional subspace representing stylistically plausible designs. Optimization within this subspace achieves a better balance between aerodynamic performance and design realism. Discussion Highlights ------------------ +----------------------- - Prof. Tsubokura explained on usage of CFD softwares to significantly reduce pre-processing time for vehicle exterior designs, enabling the AI to handle large volumes of data. - Participants asked questions regarding evaluation of Tesla Cybertruck, the balance between performance and style, programming frameworks that were used, and computational resource requirements, to which Prof. Tsubokura provided detailed responses. diff --git a/ai-and-scientific-computing/README.rst b/ai-and-scientific-computing/README.rst index e7a6d0a..a10514c 100644 --- a/ai-and-scientific-computing/README.rst +++ b/ai-and-scientific-computing/README.rst @@ -1,26 +1,31 @@ -============================================ UXL Foundation AI & Scientific Computing SIG -============================================ +============================================== -🚀 Introducing UXL AI & Scientific Computing SIG: Expanding into AI for Science +The SIG connects AI and scientific-computing communities with UXL project +developers. Its scope includes scientific frameworks, AI for Science, +simulation and modelling on heterogeneous computing platforms. - The UXL Foundation is excited to announce that the AI Special Interest Group (SIG) is evolving into the AI & Scientific Computing SIG, expanding its scope to include scientific frameworks and AI for Science. -This evolution reflects the growing convergence of AI-driven methods and scientific computing workflows, enabling innovation across simulation, modelling, and data-driven discovery on modern heterogeneous computing platforms. - This SIG, led by Google, Fujitsu, and Intel, will focus on: -• Driving technical discussions and knowledge sharing on AI frameworks and Scientific Computing, with UXL software serving as the foundation for scientific frameworks and applications. -• Acting as a bridge between scientific R&D communities and developers to foster collaboration and innovation -• Host regular meetings to share community proposals, case studies, technical advancements, challenges, and contributions, and provide feedback and requirements to guide UXL component development -• Identifying common patterns and requirements in scientific computing and aligning them with AI Surrogate Models & Frameworks +Topics include: -👥 The AI & Scientific Computing SIG is led by Chairs Penporn Koanantakool (Google) and Priyanka Sharma (Fujitsu), along with Co-Chairs Jian Hui Li (Intel) and Ragesh Hajela (Fujitsu). +* Technical discussions, case studies and requirements for UXL libraries. +* Shared patterns across scientific applications and AI surrogate models. +* Community proposals, implementation challenges and contributions. -Archived meeting notes from oneAPI AI Tab meetings held under the oneAPI +Chairs: Penporn Koanantakool (Google) and Priyanka Sharma (Fujitsu). +Co-chairs: Jian Hui Li (Intel) and Ragesh Hajela (Fujitsu). + +Find invitations and discussion through the +`UXL mailing lists `__. +See the `project directory <../PROJECTS.md>`__ for library documentation +and the `foundation home <../README.md>`__ for participation routes. + +Archived meeting notes from oneAPI AI Tab meetings held under the oneAPI Community Forum can be found `here`_ .. _here: https://github.com/oneapi-src/oneAPI-tab/tree/main/ai Meeting notes -============= +=============== * `2026-06-25 <2026-6-25-UXL-AI-and-Scientific-Computing-SIG.rst>`__ * `2026-04-23 <2026-4-23-UXL-AI-and-Scientific-Computing-SIG.rst>`__ diff --git a/doc/2025-UXL-Goals-Objectives.rst b/doc/2025-UXL-Goals-Objectives.rst index d2bb753..a1b4863 100644 --- a/doc/2025-UXL-Goals-Objectives.rst +++ b/doc/2025-UXL-Goals-Objectives.rst @@ -1,11 +1,17 @@ -============================================ +============================================== UXL Foundation Goals and Objectives for 2025 -============================================ +============================================== + +.. note:: + + Historical 2025 record. This page does not announce current programs, + deadlines or commitments. See the `foundation home <../README.md>`__ + for current participation routes. Introduction -============ +============== -The UXL Foundation Steering Committee has agreed some objectives for 2025. +The UXL Foundation Steering Committee has agreed some objectives for 2025. This page records the objectives and targets, these will be monitored and measured through the year. +-------------------------+----------------------------------------+-------------------------------------------+ diff --git a/doc/GSOC2025.rst b/doc/GSOC2025.rst index 1d08fdd..fb59860 100644 --- a/doc/GSOC2025.rst +++ b/doc/GSOC2025.rst @@ -1,11 +1,19 @@ -============================================================================== +================================================================================ UXL Foundation: List of Suggested Projects for the UXL Foundation in GSOC 2025 -============================================================================== +================================================================================ + +.. note:: + + Historical 2025 record. For current APIs, see the + `dynamic specification `__. + This page does not announce current programs, + deadlines or commitments. See the `foundation home <../README.md>`__ + for current participation routes. The UXL Foundation governs a set of predominantly C++ projects that aim to bring vendor neutrality to HPC and AI software development using CPUs, GPUs and other accelerators. These projects are based on the oneAPI specification and open source software and cover a range of domains from AI, Math, ISO Parallel C++ and multi-node GPU systems. -Our overall goal is to build a multi-architecture multi-vendor software ecosystem for all accelerators, +Our overall goal is to build a multi-architecture multi-vendor software ecosystem for all accelerators, unify the heterogeneous compute ecosystem around open standards and build on and expand open-source projects for accelerated computing. This page contains proposed projects for GSOC 2025 have been provided by different UXL Foundation projects. @@ -14,10 +22,10 @@ You can join our Slack workspace and channels to discuss any of these ideas, or Each project under the UXL Foundation has their own Slack channel. `oneMath`_ -========== +============ -The oneMath project is a library that develops a standards based API for a range of math operators so that developers can call the -same API and target multiple CPUs and GPUs from different vendors. For GSOC there are opportunities to implement new functionality for the oneMath project +The oneMath project is a library that develops a standards based API for a range of math operators so that developers can call the +same API and target multiple CPUs and GPUs from different vendors. For GSOC there are opportunities to implement new functionality for the oneMath project to enable the library to support new operators and backends for different processor architectures. Potential mentors for the projects are maintainers of the oneMath project including Romain Biessy and Maria Kraynyuk. @@ -25,7 +33,7 @@ Potential mentors for the projects are maintainers of the oneMath project includ The following are projects that have been proposed by oneMath. Implement New Math Operators for different CPU and GPU targets --------------------------------------------------------------- +---------------------------------------------------------------- **Random Number Generation (RNG)** @@ -43,7 +51,7 @@ The development work will require implementing the bindings for these RNG routin We expect each implementation might take 90-175 hours but this depends since the learnings from integrating the first operator can be taken into the others. Add open source backends for LAPACK and DFT -------------------------------------------- +--------------------------------------------- **LAPACK** oneMath has been adding open source implementations for the different math domains it supports and we would like to see another added for LAPACK for x86 and aarch CPUs. @@ -57,9 +65,9 @@ The project would be to add an open-source CPU backend to the DFT domain for one This project is expected to take 90 hours, and requires tests to also be implemented for this new target and backend. `oneDAL`_ -========= +=========== -oneAPI Data Analytics Library (oneDAL) is a powerful machine learning library that helps you accelerate +oneAPI Data Analytics Library (oneDAL) is a powerful machine learning library that helps you accelerate big data analysis at all stages: preprocessing, transformation, analysis, modeling, validation, and decision making. Potential mentors for the projects include oneDAL maintainers Ian Faust and Sergey Yakovlev. @@ -67,11 +75,11 @@ Potential mentors for the projects include oneDAL maintainers Ian Faust and Serg The project has produced their own list of ideas on `the oneDAL GitHub`_. `oneCCL`_ -========= +=========== The following project is being proposed by the oneCCL project. -oneAPI Collective Communications Library (oneCCL) provides an efficient implementation -of communication patterns used in deep learning on multi-node archtiectures such as research +oneAPI Collective Communications Library (oneCCL) provides an efficient implementation +of communication patterns used in deep learning on multi-node archtiectures such as research clusters. Potential mentor for the projects is oneCCL maintainer Maria Garzaran and other engineers from the project will be available. diff --git a/doc/Meetings.rst b/doc/Meetings.rst index 0a4f443..d090757 100644 --- a/doc/Meetings.rst +++ b/doc/Meetings.rst @@ -1,9 +1,9 @@ -============ +============== UXL Meetings -============ +============== Attending a Meeting -=================== +===================== Meetings are hosted in Zoom. @@ -19,7 +19,7 @@ Group specific pages in lists.uxlfoundation.org Hosting a Meeting -================= +=================== Linux foundation infrastructure to support meeting hosts: @@ -29,7 +29,7 @@ Linux foundation infrastructure to support meeting hosts: Sending a Meeting Announcement ------------------------------- +-------------------------------- Publish an agenda in advance of the meeting. This is a good practice for several reasons: @@ -43,7 +43,7 @@ Include the meeting date, time zone, agenda topics and the calendar link. Coordinate calendar or host changes with the group chairs or foundation operations. Recording a Meeting -------------------- +--------------------- There are many benefits to recording a meeting @@ -60,28 +60,20 @@ attendees that it is being recorded. Recordings may require membership and an openprofile account; do not assume that every recording is publicly accessible. Do not include private information in a public meeting record. -There are two ways to record a meeting: - -* Automatically record the meeting. This is the simplest way to record a - meeting. The recording will be available after the meeting ends in `My - Meetings`_. +Before the meeting: -* Manually record the meeting. Manual recording will give you more control - over the recording. In practice, I have found this very difficult and do not - recommend the option. +* Confirm the host, recording arrangements and backup host. +* Check recording access settings and tell attendees about recording. +* Assign a note taker to capture decisions and agreed actions. - * You will forget to record - * You need to provide a key to authenticate as meeting host and then turn on - recording. It is a distraction. - * If the regular host is not present, the person covering will not remember - to record, or not have the key, or not know how to use the key to record. - * Automatic and manual recordings are available in different places. I have - not found the manual recording after the meeting ends. +After the meeting, confirm that the recording is available to its intended +audience through `My Meetings`_. If it is missing, ask the host or foundation +operations to check the recording before publishing an access link. Publishing Meeting Minutes --------------------------- +---------------------------- -Use the meeting-notes template linked from CONTRIBUTING.md. Save new notes with +Use the meeting-notes template linked from `Contributing <../CONTRIBUTING.md>`__. Save new notes with a YYYY-MM-DD filename in the relevant group directory and add them to its index. Include decisions, action owners, presentation links and recording access details. Submit a pull request for review by the relevant group chairs before publication. diff --git a/doc/README.rst b/doc/README.rst index d66807a..1b6d363 100644 --- a/doc/README.rst +++ b/doc/README.rst @@ -1,29 +1,33 @@ -================================ -UXL Infrastructure Documentation -================================ - -Documentation related to infrastructure for UXL. - -`UXL Foundation Charter`_ - Outlines the foundation projects and how to contribute -`UXL Goals 2025`_ - Historical goals for 2025; not a statement of current-year commitments -`UXL GitHub`_ - GitHub Actions, repositories and organizations -`UXL Slack`_ - Managing Slack channels -`Web Hosting`_ - Hosting project web sites -`Meetings`_ - Attending, hosting and publishing meeting records -`Get Started`_ - How to get started with the UXL Foundation projects - -.. _`UXL Foundation Charter` : uxl-foundation-charter.rst -.. _`UXL Goals 2025` : 2025-UXL-Goals-Objectives.rst -.. _`UXL GitHub`: uxl-github.rst -.. _`UXL Slack`: uxl-slack.rst -.. _`Web Hosting`: web-hosting.rst -.. _`Get Started`: get-started.rst - -.. _`Meetings`: Meetings.rst +Foundation documentation +========================== + +Participation +--------------- + +* `Choose a library <../PROJECTS.md>`__: repositories and documentation. +* `Contribute <../CONTRIBUTING.md>`__: issues, changes and meeting records. +* `Meetings `__: attending, hosting and publishing notes. + +Governance and records +------------------------ + +* `Foundation charter `__: published foundation context. +* `Steering Committee <../steering-committee/README.rst>`__: meeting records. + +Community operations +---------------------- + +* `GitHub `__: repositories, access and CI references. +* `Slack `__: channels and notifications. +* `Web hosting `__: documentation publishing and domain requests. + +Historical programs and reports +--------------------------------- + +* `2025 objectives <2025-UXL-Goals-Objectives.rst>`__. +* `GSoC 2025 project ideas `__. +* `Foundation status reports <../monthly-status/README.md>`__. + +These archives do not announce current programs or commitments. + +`Foundation home <../README.md>`__ diff --git a/doc/uxl-foundation-charter.rst b/doc/uxl-foundation-charter.rst index 016a5ce..13c74dd 100644 --- a/doc/uxl-foundation-charter.rst +++ b/doc/uxl-foundation-charter.rst @@ -1,29 +1,37 @@ -====================== +======================== UXL Foundation Charter -====================== +======================== + +.. note:: + + This document preserves the foundation's published charter and project + context. For current interfaces, supported platforms and requirements, + consult the `project directory <../PROJECTS.md>`__ and + `dynamic specification `__. Project descriptions below + may reflect the period in which this document was written. Introduction -============ - -The landscape of computing has changed, and increasingly architectures are -heterogeneous, consisting of multiple types of processors from different -vendors. The top supercomputers are now dominated by architectures that -predominantly use GPUs. Data centres and embedded/edge systems are integrating -CPUs and GPUs from multiple vendors alongside specialised processors for -domains such as AI. This change has reached all industry verticals from +============== + +The landscape of computing has changed, and increasingly architectures are +heterogeneous, consisting of multiple types of processors from different +vendors. The top supercomputers are now dominated by architectures that +predominantly use GPUs. Data centres and embedded/edge systems are integrating +CPUs and GPUs from multiple vendors alongside specialised processors for +domains such as AI. This change has reached all industry verticals from finance and healthcare through to autonomous vehicles and manufacturing. -What this means is that there is a growing demand for software acceleration -using architectures that consist of different types of accelerators from +What this means is that there is a growing demand for software acceleration +using architectures that consist of different types of accelerators from multiple vendors. -Multiple types of processors are used to accelerate various software applications, -in particular for AI. Large data centres and clusters are increasingly using -large numbers of GPUs to accelerate data intensive workloads including those used +Multiple types of processors are used to accelerate various software applications, +in particular for AI. Large data centres and clusters are increasingly using +large numbers of GPUs to accelerate data intensive workloads including those used in AI. -A survey done by Evans Data in 2024 found that more than half of developers are -now designing software to account for processor specifics across multiple hardware -architectures including CPUs, GPUs or accelerators*. +A survey done by Evans Data in 2024 found that more than half of developers are +now designing software to account for processor specifics across multiple hardware +architectures including CPUs, GPUs or accelerators*. +----------------------------------------+---------------------------------------+ | .. figure:: images/cpu-gpu-npu-ai.png | .. figure:: images/cpu-gpu.png | @@ -36,143 +44,144 @@ architectures including CPUs, GPUs or accelerators*. +----------------------------------------+---------------------------------------+ The Challenge -============= - -The emergence of heterogeneous architectures poses two main challenges for +=============== + +The emergence of heterogeneous architectures poses two main challenges for software developers: -1. Easily developing software that can be used with different architectures +1. Easily developing software that can be used with different architectures and vendors of accelerators such as GPUs and AI processors 2. Achieving good levels of performance across architectures and vendors The UXL Foundation -================== - +==================== + The goals of the `UXL Foundation`_ aim to address these challenges by: -- Building a multi-architecture multi-vendor software ecosystem for all +- Building a multi-architecture multi-vendor software ecosystem for all accelerators. - Unifying the heterogeneous compute ecosystem around open standards. - Enabling collaboration around open-source projects for accelerated computing. -The UXL Foundation enables developers to write source code once and -deploy it across accelerators, regardless of vendor, by facilitating -collaboration between organisations designing the latest processors and +The UXL Foundation enables developers to write source code once and +deploy it across accelerators, regardless of vendor, by facilitating +collaboration between organisations designing the latest processors and software developers building the latest innovative solutions. -We create the environment required for cross-industry participation -on the specification and open source projects that are governed by the UXL -Foundation. This is achieved by adopting best practices for open source +We create the environment required for cross-industry participation +on the specification and open source projects that are governed by the UXL +Foundation. This is achieved by adopting best practices for open source development and providing the structure for open discussion and decision making. -The UXL Foundation is part of the Linux Foundation and is founded on the +The UXL Foundation is part of the Linux Foundation and is founded on the principles of open governance, as outlined in the UXL `GitHub repository`_. UXL Foundation Projects -======================= +========================= -Initially a set of C++ projects and specifications were contributed to the UXL -Foundation forming fundamental building blocks that cover accelerated operations +Initially a set of C++ projects and specifications were contributed to the UXL +Foundation forming fundamental building blocks that cover accelerated operations required by most software applications and frameworks. -- For GPU acceleration, the projects use the `SYCL`_ open standard, a programming - model defined by the Khronos Group. SYCL makes it possible to write kernels - that can be executed in parallel using standard C++ code and compiled for a - range of processors. -- For CPU acceleration most projects use `oneTBB`_, an open source framework +- For GPU acceleration, the projects use the `SYCL`_ open standard, a programming + model defined by the Khronos Group. SYCL makes it possible to write kernels + that can be executed in parallel using standard C++ code and compiled for a + range of processors. +- For CPU acceleration most projects use `oneTBB`_, an open source framework that provides multi-threading capabilities. -The `oneAPI specification`_ defines the APIs for these projects. +The `dynamic oneAPI specification`_ describes shared concepts and links to each +project's documentation, the canonical source for current APIs and requirements. -A list of specific areas where the community can contribute to projects is +A list of specific areas where the community can contribute to projects is being added to the project issue trackers under the “Help Wanted” label. -Proposals for significant changes or additions to the projects can be made through -the RFC process, Open Source Working Group, and discussions can be had on the +Proposals for significant changes or additions to the projects can be made through +the RFC process, Open Source Working Group, and discussions can be had on the `Slack`_ channel. -The current work packages are tracked on the `Open Source Working Group GitHub +The current work packages are tracked on the `Open Source Working Group GitHub repository`_. Accelerated Building Blocks -=========================== +============================= .. figure:: images/uxl-foundation-projects.png :scale: 50 % :alt: uxl-projects Open Source Development -======================= - -Making open source code available is not enough to build a sustainable open -source project with many contributors, maintainers and users. An open source -project requires a set of fundamentals that an open source needs, such as -open decision robust build infrastructure in order to be successfully -adopted across the community. The projects have adopted the best practices -for open source development, such as using the OpenSSF security badge, and -the project health is monitored regularly and reviewed by the Working Group +========================= + +Making open source code available is not enough to build a sustainable open +source project with many contributors, maintainers and users. An open source +project requires a set of fundamentals that an open source needs, such as +open decision robust build infrastructure in order to be successfully +adopted across the community. The projects have adopted the best practices +for open source development, such as using the OpenSSF security badge, and +the project health is monitored regularly and reviewed by the Working Group and Steering Committee. Math Domains - The `oneMath`_ project -===================================== +======================================= -The oneAPI specification defines the oneMath API (formerly oneMKL) covering +The oneAPI specification defines the oneMath API (formerly oneMKL) covering BLAS, LAPACK, RNG, DFT and SPARSE math domains. -The open source `oneMKL`_ interfaces project implements the specification, -providing a standard API for these math domains. The project uses industry -standards where available, such as for BLAS, to define the API arguments. The -project integrates with multiple back ends to enable deployment to different +The open source `oneMKL`_ interfaces project implements the specification, +providing a standard API for these math domains. The project uses industry +standards where available, such as for BLAS, to define the API arguments. The +project integrates with multiple back ends to enable deployment to different processors: - Intel oneMKL optimized library for Intel CPU and GPU - Nvidia cuBLAS, cuSOLVER, cuRAND, and cuFFT optimized libraries for Nvidia GPU - AMD rocBLAS, rocSOLVER, rocRAND, and rocFFT optimized libraries for AMD GPU - Open source NETLIB LAPACK library for x86 CPU -- Open source portBLAS and portFFT SYCL code for x86 CPU, AMD GPU, Intel GPU, +- Open source portBLAS and portFFT SYCL code for x86 CPU, AMD GPU, Intel GPU, Nvidia GPU A matrix of targets available and domains is available in the project README. Contributions to the oneMath Project ------------------------------------- +-------------------------------------- Broadening support for processors ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -New backends targeting different processors including new host CPUs such as -RISC-V can be added to the project. Public documentation on how to do -this is available. Pull Requests can be made with additions for integrations -with vendor libraries or open source code. In addition to new backend work, -testing resources for existing processor targets are needed to ensure these can -be treated as supported targets. Alongside this, the community can contribute -to helping make the project easy to install as well as showing what level of -support is available for different processors based on the different math +New backends targeting different processors including new host CPUs such as +RISC-V can be added to the project. Public documentation on how to do +this is available. Pull Requests can be made with additions for integrations +with vendor libraries or open source code. In addition to new backend work, +testing resources for existing processor targets are needed to ensure these can +be treated as supported targets. Alongside this, the community can contribute +to helping make the project easy to install as well as showing what level of +support is available for different processors based on the different math domains. Public Build and CI ^^^^^^^^^^^^^^^^^^^ -There is an ongoing work package to set up sufficient public CI infrastructure -for the projects. This will document how new community managed build -machines can be added and make additional infrastructure available. Please -contact the Open Source Working Group to contribute CI resources for the +There is an ongoing work package to set up sufficient public CI infrastructure +for the projects. This will document how new community managed build +machines can be added and make additional infrastructure available. Please +contact the Open Source Working Group to contribute CI resources for the oneMath project. Open Source Contributions ^^^^^^^^^^^^^^^^^^^^^^^^^ -Some open source implementations of the math domains are available for CPU and -GPU but gaps exist, and the open source implementations could be further -optimized for specific processors. Additionally a documented approach for -how to consistently add new hardware targets for the library would help +Some open source implementations of the math domains are available for CPU and +GPU but gaps exist, and the open source implementations could be further +optimized for specific processors. Additionally a documented approach for +how to consistently add new hardware targets for the library would help the project to cover a broader set of processors. -The project is also seeking code owners and maintainers for some hardware +The project is also seeking code owners and maintainers for some hardware targets. Acceleration for AI Applications and Frameworks - `oneDNN`_ =============================================================== -The oneAPI specification defines the oneDNN API covering convolution, matrix -multiplication, pooling, batch normalization, activation functions, RNN and -LSTM. These are currently the most commonly used operators for AI software, +The oneAPI specification defines the oneDNN API covering convolution, matrix +multiplication, pooling, batch normalization, activation functions, RNN and +LSTM. These are currently the most commonly used operators for AI software, used by frameworks such as TensorFlow and PyTorch. -The open source `oneDNN`_ project implements the specification and provides a +The open source `oneDNN`_ project implements the specification and provides a standard API for commonly used operators on: - Intel GPU @@ -180,173 +189,173 @@ standard API for commonly used operators on: - Nvidia GPU (experimental) - AMD GPU (experimental) -oneDNN is currently used by a variety of AI projects including PyTorch, -TensorFlow, and Paddle Paddle amongst others for software acceleration on a +oneDNN is currently used by a variety of AI projects including PyTorch, +TensorFlow, and Paddle Paddle amongst others for software acceleration on a variety of processors, including both CPUs and GPUs. -The oneDNN project is seeking code owners and maintainers for some hardware +The oneDNN project is seeking code owners and maintainers for some hardware targets, see the `oneDNN Maintainers`_ file for details. -Contributions to expand the processor targets supported by oneDNN, as well as -support to bring the Nvidia and AMD GPU targets out of experimental status are -welcome. Resources for public CI infrastructure are required both to expand -testing of existing target processors and to help bring target processors out -of experimental status (in particular Nvidia and AMD). Join the `Slack`_ -channel to discuss contributions and see the `oneDNN Contributing`_ file for +Contributions to expand the processor targets supported by oneDNN, as well as +support to bring the Nvidia and AMD GPU targets out of experimental status are +welcome. Resources for public CI infrastructure are required both to expand +testing of existing target processors and to help bring target processors out +of experimental status (in particular Nvidia and AMD). Join the `Slack`_ +channel to discuss contributions and see the `oneDNN Contributing`_ file for details. Parallel ISO C++ - `oneDPL`_ -============================ +============================== -Based on the ISO C++ standard definition for parallel routines and algorithms, -the oneAPI specification defines the oneDPL interfaces and execution model to -integrate the SYCL programming model. Developers use a SYCL queue and memory +Based on the ISO C++ standard definition for parallel routines and algorithms, +the oneAPI specification defines the oneDPL interfaces and execution model to +integrate the SYCL programming model. Developers use a SYCL queue and memory management alongside the ISO C++ parallel routines and algorithms. -The open source `oneDPL`_ project implements the specification and uses SYCL code -to provide portability for the project across architectures and vendor processors +The open source `oneDPL`_ project implements the specification and uses SYCL code +to provide portability for the project across architectures and vendor processors including GPUs, FPGAs and CPUs. -Currently the project only lists Intel processors as targets, but since the -code is implemented using SYCL it can be compiled and used with other targets +Currently the project only lists Intel processors as targets, but since the +code is implemented using SYCL it can be compiled and used with other targets supported by the DPC++ compiler such as Nvidia and AMD GPUs. -Contributions to extend the project and/or optimize it for more processor -targets are welcome. Resources for CI infrastructure to cover testing and -building on more target processors are required. Join the `Slack`_ channel to +Contributions to extend the project and/or optimize it for more processor +targets are welcome. Resources for CI infrastructure to cover testing and +building on more target processors are required. Join the `Slack`_ channel to discuss contributions. Accelerated AI Data Analysis – `oneDAL`_ -======================================== +========================================== -The oneAPI specification defines interfaces for oneDAL, used in big data -analysis through optimized data ingestion alongside algorithms. -The open source `oneDAL`_ implementation provides accelerated algorithms used -by machine learning packages such as SciKit Learn. These algorithms can be -executed on CPUs and GPUs through a range of backends, and the project has some +The oneAPI specification defines interfaces for oneDAL, used in big data +analysis through optimized data ingestion alongside algorithms. +The open source `oneDAL`_ implementation provides accelerated algorithms used +by machine learning packages such as SciKit Learn. These algorithms can be +executed on CPUs and GPUs through a range of backends, and the project has some dependencies on oneTBB for CPU multi-threading and Intel oneMKL for BLAS. -The project lists Intel CPUs and GPUs as supported targets however it can -be used with Arm CPUs and work is underway for RISC-V CPUs. The project team -is implementing SYCL kernel code for the algorithms and once available brings +The project lists Intel CPUs and GPUs as supported targets however it can +be used with Arm CPUs and work is underway for RISC-V CPUs. The project team +is implementing SYCL kernel code for the algorithms and once available brings the potential for much broader processor target support. -Contributions to extend the project or optimize it for more processor targets -are welcome. There is also an opportunity to bring more infrastructure for +Contributions to extend the project or optimize it for more processor targets +are welcome. There is also an opportunity to bring more infrastructure for building and testing on more Arm processor targets. Multi-node deep learning – `oneCCL`_ -==================================== - -The oneAPI specification defines interfaces for oneCCL, used to define concepts -and objects that operate on data. This includes operations that the open source -`oneCCL`_ project implements as well as the specification, and provides efficient -communication patterns for deep learning. The specification is designed for use -on systems consisting of multiple nodes where work is distributed and effective -data transfer can help accelerate the software. The project is integrated with -PyTorch and Horovod. Currently the project only lists Intel CPUs and GPU -processors as targets, but there is potential for the project to be used with -other targets. Contributions to bring more processor targets to oneCCL as well +====================================== + +The oneAPI specification defines interfaces for oneCCL, used to define concepts +and objects that operate on data. This includes operations that the open source +`oneCCL`_ project implements as well as the specification, and provides efficient +communication patterns for deep learning. The specification is designed for use +on systems consisting of multiple nodes where work is distributed and effective +data transfer can help accelerate the software. The project is integrated with +PyTorch and Horovod. Currently the project only lists Intel CPUs and GPU +processors as targets, but there is potential for the project to be used with +other targets. Contributions to bring more processor targets to oneCCL as well as resources for public build and CI infrastructure are required. CPU Multi-threading – `oneTBB`_ -=============================== +================================= -The oneAPI specification defines the interfaces for oneTBB which is used for +The oneAPI specification defines the interfaces for oneTBB which is used for multi-threading on CPUs. -The open source `oneTBB`_ project implements the specification and broadly -speaking can be used with any x86 and aarch64 processor, but specific support -is provided for Intel CPUs listed on this page, and community supported +The open source `oneTBB`_ project implements the specification and broadly +speaking can be used with any x86 and aarch64 processor, but specific support +is provided for Intel CPUs listed on this page, and community supported processors are also listed. -Other UXL Foundation projects utilize the oneTBB project to achieve -acceleration on CPU devices, specifically oneDAL, oneDPL and oneDNN. Many -software projects worldwide using oneTBB to accelerate software on CPUs. -Contributions to test a broad range of processor targets with oneTBB are -welcome in the form of CI or build infrastructure. The project does not +Other UXL Foundation projects utilize the oneTBB project to achieve +acceleration on CPU devices, specifically oneDAL, oneDPL and oneDNN. Many +software projects worldwide using oneTBB to accelerate software on CPUs. +Contributions to test a broad range of processor targets with oneTBB are +welcome in the form of CI or build infrastructure. The project does not currently test RISC-V CPUs and some functionality is missing. Hardware Enablement - `oneAPI Construction Kit`_ -================================================ +================================================== -The oneAPI Construction Kit can be used to bring SYCL and oneAPI to new and -specialist accelerators. The oneAPI Construction Kit works enables the CPU -to offload compute-intensive kernels to the custom accelerator. The project +The oneAPI Construction Kit can be used to bring SYCL and oneAPI to new and +specialist accelerators. The oneAPI Construction Kit works enables the CPU +to offload compute-intensive kernels to the custom accelerator. The project includes a reference implementation using RISC-V. The UXL Foundation Work Areas -============================= +=============================== -This section outlines the primary areas where contributors can help support +This section outlines the primary areas where contributors can help support the foundation and its projects in achieving their objectives. Hardware Support ----------------- +------------------ -The UXL projects aim to support a broad range of processors from different -vendors. Each project shows the currently supported hardware in the project -documentation. Contributions can be made to introduce new target processors -and/or to provide build and testing resources for these targets to improve -support. +The UXL projects aim to support a broad range of processors from different +vendors. Each project shows the currently supported hardware in the project +documentation. Contributions can be made to introduce new target processors +and/or to provide build and testing resources for these targets to improve +support. -Potential contributors can contact the project team through the `Slack`_ channel -or `mailing list`_ to discuss with the project maintainers and the community +Potential contributors can contact the project team through the `Slack`_ channel +or `mailing list`_ to discuss with the project maintainers and the community about how they can assist with this work. Distribution ------------- - -The broad distribution of UXL projects across Linux distributions and through -commercial releases such as the Intel oneAPI Base Toolkit relies on robust -testing across hardware, operating systems and driver level software. This -requires infrastructure hosted by the foundation and community members -including processor vendors and Linux distributions. A work package for public -build infrastructure is ongoing and community contributions are welcomed to -this effort. Contact the Open Source Working Group through the `Slack`_ +-------------- + +The broad distribution of UXL projects across Linux distributions and through +commercial releases such as the Intel oneAPI Base Toolkit relies on robust +testing across hardware, operating systems and driver level software. This +requires infrastructure hosted by the foundation and community members +including processor vendors and Linux distributions. A work package for public +build infrastructure is ongoing and community contributions are welcomed to +this effort. Contact the Open Source Working Group through the `Slack`_ Channel or `mailing list`_. Open Source ------------ - -The UXL Foundation is based on the principles of open source software and as -such all projects try to use open source components where possible. For some -projects, such as oneMath, open source code can be contributed to ensure -there is an open source implementation alongside any closed source vendor -libraries. This ensures that developers can use the necessary functionality -they need across targets and have access to fully open source versions of the -projects. Use the `Slack`_ channel or `mailing list`_ to talk about what open source +------------- + +The UXL Foundation is based on the principles of open source software and as +such all projects try to use open source components where possible. For some +projects, such as oneMath, open source code can be contributed to ensure +there is an open source implementation alongside any closed source vendor +libraries. This ensures that developers can use the necessary functionality +they need across targets and have access to fully open source versions of the +projects. Use the `Slack`_ channel or `mailing list`_ to talk about what open source contributions could be made to different projects. Optimisation ------------- +-------------- -The UXL Foundation projects have been optimized for some targets but there is -always room for further code optimization more for different targets. The -projects may have issues for these items, but if not please talk to the +The UXL Foundation projects have been optimized for some targets but there is +always room for further code optimization more for different targets. The +projects may have issues for these items, but if not please talk to the project teams through the `Slack`_ channels or `mailing list`_. Software Integration --------------------- - -The UXL Foundation projects sit low in the software stack providing building -blocks for many other applications, libraries and frameworks. There must be a -level of compatibility and integration for the UXL Foundation projects. -Collaboration with key open source projects is essential. If your project is -working with UXL Foundation projects please share your feedback, issues and -ideas through GitHub or the SIG meetings. Get in touch via the `Slack`_ +---------------------- + +The UXL Foundation projects sit low in the software stack providing building +blocks for many other applications, libraries and frameworks. There must be a +level of compatibility and integration for the UXL Foundation projects. +Collaboration with key open source projects is essential. If your project is +working with UXL Foundation projects please share your feedback, issues and +ideas through GitHub or the SIG meetings. Get in touch via the `Slack`_ channels or `mailing list`_. \* `Evans Data Article on Multiarchitecture Programming`_ .. _`UXL Foundation`: https://www.uxlfoundation.org .. _`sycl`: https://www.khronos.org/sycl/ -.. _`oneTBB`: https://github.com/oneapi-src/oneTBB -.. _`oneMath`: https://github.com/oneapi-src/oneMath -.. _`oneDNN`: https://github.com/oneapi-src/oneDNN -.. _`oneDAL`: https://github.com/oneapi-src/oneDAL -.. _`oneCCL`: https://github.com/oneapi-src/oneCCL -.. _`oneDPL`: https://github.com/oneapi-src/oneDPL +.. _`oneTBB`: https://github.com/uxlfoundation/oneTBB +.. _`oneMath`: https://github.com/uxlfoundation/oneMath +.. _`oneDNN`: https://github.com/uxlfoundation/oneDNN +.. _`oneDAL`: https://github.com/uxlfoundation/oneDAL +.. _`oneCCL`: https://github.com/uxlfoundation/oneCCL +.. _`oneDPL`: https://github.com/uxlfoundation/oneDPL .. _`oneAPI Construction Kit`: https://github.com/uxlfoundation/oneapi-construction-kit .. _`Slack`: http://slack-invite.uxlfoundation.org/ .. _`Open Source Working Group GitHub repository`: https://github.com/uxlfoundation/open-source-working-group -.. _`oneAPI specification`: https://oneapi-spec.uxlfoundation.org/specifications/oneapi/latest/ +.. _`dynamic oneAPI specification`: https://uxlfoundation.org/specifications/oneapi/technical-overview/ .. _`mailing list`: https://lists.uxlfoundation.org .. _`GitHub project board`: https://github.com/orgs/uxlfoundation/projects/5?pane=info -.. _`oneDNN Maintainers`: https://github.com/oneapi-src/oneDNN/blob/main/MAINTAINERS.md -.. _`oneDNN Contributing`: https://github.com/oneapi-src/oneDNN/blob/main/CONTRIBUTING.md +.. _`oneDNN Maintainers`: https://github.com/uxlfoundation/oneDNN/blob/main/MAINTAINERS.md +.. _`oneDNN Contributing`: https://github.com/uxlfoundation/oneDNN/blob/main/CONTRIBUTING.md .. _`GitHub repository`: https://github.com/uxlfoundation/foundation .. _`Evans Data Article on Multiarchitecture Programming`: https://evansdata.com/press/viewRelease.php?pressID=364 diff --git a/doc/uxl-github.rst b/doc/uxl-github.rst index b70b72a..943353d 100644 --- a/doc/uxl-github.rst +++ b/doc/uxl-github.rst @@ -1,75 +1,38 @@ -================= UXL use of GitHub -================= +=================== -This document describes the use of GitHub for the UXL project. +The `uxlfoundation organization `__ hosts +foundation governance, Working Group coordination and individual library projects. +Use the `project directory <../PROJECTS.md>`__ to find the right repository. -uxlfoundation org -================= +Access and ownership +---------------------- -The UXL project is hosted on GitHub under the `uxlfoundation`_ organization. It -contains repos that are not specific to any one open source project. There will -be a small set of ``owners`` for the org. ``@thelinuxfoundation`` is an owner -as backup in case UXL owners are not available. +Use role-based GitHub teams to manage access and route reviews. The foundation's +``sig-leaders`` team and the Working Group's ``open-source-wg-maintainers`` team +are identified in their CODEOWNERS files. Projects retain their own maintainers. -Giving Access to Resources --------------------------- +Request access through the relevant repository maintainers. Include the repository, +the work you need to do and the access required. Organization-level changes need +an organization owner; repository access does not imply organization administration. +See `Contributing <../CONTRIBUTING.md>`__ for documentation review guidance. -Try to use GitHub Teams that are defined by roles. For example, -``@oneapi-spec-maintainers`` are the maintainers for the oneapi spec and have -write access. Using a team-based role instead of directly adding maintainers to -the repo makes it possible to ``@tag`` the team in issues and PRs. +GitHub Actions and runners +---------------------------- -If a role specific team is overkill, but you still want to be able to ``@tag`` -someone in a repo in uxlfoundation org, they can be added to the `UXL Members`_ -team. If you have a role in UXL (e.g. SIG leader), you can be added as a -maintainer of this team. +The Working Group's `CI requirements and reported infrastructure +`__ +is the shared reference for project requirements and infrastructure evidence. -GitHub Actions -============== +Before using a runner, confirm its availability, permitted repositories, labels +and support contact with its owner. A workflow records intended usage; a recent +successful run shows that the configuration worked at that time. Neither +guarantees future capacity. -UXL Foundation projects make use of GitHub Actions for continuous integration -and testing. +The former Intel Max 1550 runner catalogue on this page is historical. The +`August 2025 Working Group record +`__ +describes changes to hardware access and support. Do not use the old catalogue +as a current availability guarantee. It remains accessible in this file's history. -Available Runners ------------------ - -In addition to the `Standard GitHub-hosted runners`_ the UXL Foundation GitHub -organization has several member-hosted test systems available for use: - -Intel Data Center GPU Max 1550 -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -These systems are provided by Intel and maintained by Codeplay Software Ltd. - -The following labels are usable: - -+------------------+------------+-----------+-------------+ -| Label | vCPU | Memory | GPU | -+==================+============+===========+=============+ -| uxl-xlarge | 4 | 16Gi | - | -+------------------+------------+-----------+-------------+ -| uxl-gpu-xlarge | 4 | 16Gi | 1x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-2xlarge | 8 | 32Gi | 2x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-4xlarge | 16 | 64Gi | 1x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-6xlarge | 24 | 96Gi | 2x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-8xlarge | 32 | 128Gi | 1x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-10xlarge | 40 | 160Gi | 2x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-12xlarge | 48 | 192Gi | 4x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-16xlarge | 64 | 256Gi | 1x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-24xlarge | 96 | 384Gi | 4x 1550 GPU | -+------------------+------------+-----------+-------------+ -| uxl-gpu-48xlarge | 170 | 769Gi | 8x 1550 GPU | -+------------------+------------+-----------+-------------+ - -.. _`uxlfoundation`: https://github.com/uxlfoundation -.. _`UXL Members`: https://github.com/orgs/uxlfoundation/teams/uxl-members -.. _`Standard GitHub-hosted runners`: https://docs.github.com/en/enterprise-cloud@latest/actions/writing-workflows/choosing-where-your-workflow-runs/choosing-the-runner-for-a-job#choosing-github-hosted-runners +`Foundation home <../README.md>`__ | `Community operations `__ diff --git a/doc/uxl-slack.rst b/doc/uxl-slack.rst index 94a5a02..a001f25 100644 --- a/doc/uxl-slack.rst +++ b/doc/uxl-slack.rst @@ -1,27 +1,36 @@ -================ -UXL Use of Slack -================ +UXL use of Slack +================== -This document describes the use of Slack for the UXL project. +Slack supports discussion among projects, Special Interest Groups and the +Working Group. Find participation routes on the `foundation home <../README.md>`__. +Use the workspace's channel directory to find a project or group; channel names +may differ from repository names. -Channels -======== +Channels and access +--------------------- -There are channels for each SIG (e.g. ``sig-math``), project (e.g. ``onemkl``), and working group (e.g. ``wg-open-source``). Channels are public unless there is a specific need (e.g. ``steering-committee``, ``security``). +The Working Group uses ``wg-open-source``. Ask group chairs or workspace +administrators about other channels and access. Keep membership-restricted +discussions and credentials in the appropriate private channels. -GitHub Integration -================== +GitHub notifications +---------------------- -It is possible for GitHub Actions to post messages in Slack. This can be useful for notifications of CI failures, new issues, etc. To enable this feature for a channel: +The Working Group's `Slack notification workflow +`__ +notifies its channel when an RFC label is added and when a pull request labelled +``meeting notes`` is merged. -* add `@GitHub Messages` to the channel -* add a GitHub action to your repo. See `Slack Action`_ as an example. -* add ``SLACK_BOT_TOKEN`` to the GitHub secrets for the repo. Get the value - from Robert Cohn +To request a similar integration: -Getting the Token -================= +* Identify the destination channel and the events that should produce messages. +* Coordinate app access with workspace administrators and workflow configuration + with repository maintainers. +* Arrange the repository secret through the administrators. The existing workflow + uses ``SLACK_BOT_TOKEN``; do not publish its value in issues or documentation. +* Check delivery with the administrators and document the support role. -The token is connected with a slack app. You need to be signed in to uxlfoundation workspace to see it, otherwise you will not see the app. +The current app owner and access-request contact are not documented here. +Confirm them with workspace administrators before changing the integration. -.. _`Slack Action`: https://github.com/uxlfoundation/open-source-working-group/blob/main/.github/workflows/slack-pr.yaml +`Community operations `__ diff --git a/doc/web-hosting.rst b/doc/web-hosting.rst index 9764555..7b2035d 100644 --- a/doc/web-hosting.rst +++ b/doc/web-hosting.rst @@ -1,34 +1,40 @@ -=========== -Web Hosting -=========== - -Projects typically need web sites for documentation and other information. - -Providers -========= - -`GitHub Pages`_ - GitHub pages is usually the best solution for web sites that are static - HTML. Many people know how to use it, and it is free. It is also easy to - set up and maintain. They recommend not using it for sites bigger than 1 - Gbyte. You are only allowed static HTML, CSS, and JavaScript files. You - can use Jekyll to generate the site, but you cannot use server-side - languages like PHP. You can use client-side JavaScript to make the site - interactive. You can use a custom domain name, HTTPS, and a custom 404 page. - -.. _`GitHub Pages`: https://pages.github.com/ - -Domain Names -============ - -Most providers make it easy to host a web site in their domain. For example, the oneapi spec uses GitHub pages and can be found at: https://uxlfoundation.github.io/oneAPI-spec/spec/. While this is fine for many projects, some projects may want to have their own domain name. Using your own domain name gives you more flexibility for future changes. For example, GitHub pages uses their `github.io` domain name, the org name, and the repo name. If any of that changes, you will need to update all the links and set up redirects. If you use your own domain name, you can change the hosting provider without changing the domain name. - -Web hosting providers, including GitHub pages, lets you use your own domain name. You can buy a domain name from a domain name registrar, and then set up the DNS to point to the hosting provider. While it is not hard or expensive to do this, you may want to use the uxlfoundation.org domain name: - -* Linux foundation owns and manages the uxlfoundation.org domain name. -* Establishes the foundation as the owner of the project. - -For an example see the `UXL project site`_ which is hosted on GitHub pages but uses the uxlfoundation.org domain name. It is published from the `UXL project site repo`_. - -.. _`UXL project site`: https://uxlfoundation.org/ -.. _`UXL project site repo`: https://github.com/uxlfoundation/uxlfoundation.org +Web hosting +============= + +The `project directory <../PROJECTS.md>`__ links to current documentation sites. +The `dynamic oneAPI specification +`__ is the +current specification entry point. The retired bundled-specification site is +a historical resource. + +Plan a documentation site +--------------------------- + +* Identify the content repository and its maintainers. +* Choose a publishing process that supports the project's documentation tooling. + `GitHub Pages `__ is an option for static sites. +* Document the deployment workflow, publishing permissions and support contact. +* Distinguish release documentation from current development documentation and + preserve stable links between them. + +Domains and changes +--------------------- + +Coordinate requests under ``uxlfoundation.org`` with foundation operations. +Include the hostname, destination, content owner and proposed migration plan. +Domain ownership, DNS administration and content publishing are separate +responsibilities and should each have a confirmed contact. + +When moving a site, inventory existing URLs, arrange redirects where possible, +and verify inbound links and HTTPS after deployment. Moving a repository alone +does not establish that its documentation URLs have been redirected. + +Foundation website +-------------------- + +The `foundation website `__ and +`website source repository `__ +are reference points. Confirm the production publishing process with foundation +operations before proposing deployment or DNS changes. + +`Community operations `__ diff --git a/hardware/README.rst b/hardware/README.rst index 20b30ae..3d7c6b2 100644 --- a/hardware/README.rst +++ b/hardware/README.rst @@ -1,6 +1,6 @@ -=========================== +============================= UXL Foundation Hardware SIG -=========================== +============================= The Hardware SIG hosts discussions and presentations focused on how to enable a broad range of hardware architectures. @@ -8,13 +8,17 @@ how to enable a broad range of hardware architectures. The Hardware SIG is led by `Jeremy Bennett `__ (`Embecosm `__). -Archived meeting notes from meetings held under the oneAPI +For invitations and current meeting information, find the group through the +`UXL mailing lists `__. +See the `project directory <../PROJECTS.md>`__ for current library documentation. + +Archived meeting notes from meetings held under the oneAPI Community Forum can be found `here`_ .. _here: https://github.com/oneapi-src/oneAPI-tab/tree/main/hardware 2025-05-08 Scaling Workloads with a Memory Lake -=============================================== +================================================= Agenda: @@ -22,7 +26,7 @@ Agenda: * Scaling Workloads with a Memory Lake. Dr. Skyler Windh, Micron Scalable Memory Systems Pathfinding. `[Slides] `__ 2025-02-20 Embecosm and University of Southampton Porting to AI Hardware -======================================================================== +========================================================================== Agenda: @@ -31,38 +35,38 @@ Agenda: * Hardware acceleration for PyTorch – a demonstrator. James Betson and Lorinc Boer. University of Southampton, with Embecosm. `[Slides] `__ 2024-06-03 Imagination Technologies Enabling Compute Hardware -============================================================= +=============================================================== `[Meeting Recording] `__ Alex Pim from Imagination Technologies presented their view on the customer's journey through compute, and how they are designing their hardware with a software first approach. Imagination’s view of the customer’s journey through compute - `[slides] `__. - + HW Accel using oneAPI slide: Direct support of SYCL on OpenCL vs oneAPI on OpenCL. -A: - +A: + Q Colin: Reaction from customers so far? A: Positive, like being able to use existing code for algorithms rather than porting, want to understand how this fits into what their currently doing and are investigating SYCL. - + Q: Looked at anything other than OpenCL for implementing SYCL? A: Already had mature OpenCL driver which made that attractive, looking at what to use in the future but no conclusion. - + Q: Why continue looking at other options? A: In Imagination Technology office, part of brief is to look at upcoming technologies, never assume that today’s tech will still be tomorrow’s tech. A: What speed is OpenCL moving in relation to AI, is it moving in the right direction. A: OpenCL works, no issue. - + Q Ronan: Do you have a modern LLVM for your GPU? Often problem supporting UXL is technical debt in LLVM backend. A: Have LLVM, has enabled us to move quickly and get tests working etc. - + Q Ronan: Support USM extension in OpenCL? A: Yes, have initial support for that. Had SVM support so adapted that. Initial block for using SYCLomatic was it used USM a lot. - + Q Colin: What extensions do you support? It feels like it’s not well documented. A: Initially the only thing that didn’t work was USM, could execute simple SYCL immediately. A: Sometimes an error will pop up when building something saying some extension isn’t supported. - + Q Ben: Do you support USM today? Did you implement the Intel USM extension? A: I have access to an internal beta version, not in public support yet. @@ -90,10 +94,10 @@ Attendees: * Ruyman Reyes (Codeplay) * Verena Beckham (Codeplay) * Victor Lomuller (Codeplay) -* Victor Lu +* Victor Lu 2024-02-15 oneAPI Construction Kit and Level Zero 1.9 -===================================================== +======================================================= Agenda: diff --git a/image/README.rst b/image/README.rst index 2b19010..a78a1e9 100644 --- a/image/README.rst +++ b/image/README.rst @@ -1,19 +1,19 @@ -==================================== +====================================== Image SIG - a oneAPI Community Forum -==================================== +====================================== Introduction -============ +============== The Image SIG hosts discussions and presentations for fundamental image processing routines for high-performance computing, engineering, financial, and other applications. -This SIG discusses the oneAPI Image Processing Library (oneIPL). Its goal is -to become an extensive library of ready-to-use, highly optimized image -processing functions. As part of UXL, oneIPL is designed to allow execution -on various computational devices: CPUs, GPUs, and other accelerators. The -functionality is subdivided into several domains: filers, geometry +This SIG discusses the oneAPI Image Processing Library (oneIPL). Its goal is +to become an extensive library of ready-to-use, highly optimized image +processing functions. As part of UXL, oneIPL is designed to allow execution +on various computational devices: CPUs, GPUs, and other accelerators. The +functionality is subdivided into several domains: filters, geometry transformations, and color and type conversions. Its royalty-free APIs help developers: @@ -33,7 +33,7 @@ handling. At times, the open source oneIPL Interfaces project, which implements the oneIPL specification may also be discussed. Purpose of the Group -==================== +====================== The Image Special Interest Group (Image SIG) is committed to the collaborative development, understanding, and promotion of the open standard oneIPL. We aim @@ -52,7 +52,7 @@ image processing in the oneAPI ecosystem. wider oneAPI community. Strategy for Achieving Goals -============================ +============================== To achieve these goals, the following strategic approach will be taken: @@ -88,16 +88,21 @@ library in alignment with the broader goals of the oneAPI ecosystem. We believe in the power of collaborative innovation to drive the future of image processing and look forward to contributing to this journey. ---- +-------- The Image SIG is led by John Melonakos. -Upcoming Meetings -================= +Meeting information +===================== -The next Image SIG will be held on December 14, 2023, from 10am to 11am CST. +The previously announced meeting was December 14, 2023, 10–11am CST. +This is a historical announcement, not an upcoming meeting invitation. +For current participation information, use the +`UXL mailing lists `__. +The scope and plans below describe the group's published remit; a current +meeting schedule is not recorded on this page. -Archived meeting notes from meetings held under the oneAPI +Archived meeting notes from meetings held under the oneAPI Community Forum can be found `here`_ .. _here: https://github.com/oneapi-src/oneAPI-tab/tree/main/image diff --git a/language/README.rst b/language/README.rst index 08fe676..d007050 100644 --- a/language/README.rst +++ b/language/README.rst @@ -1,6 +1,6 @@ -=========================== +============================= UXL Foundation Language SIG -=========================== +============================= The Language SIG hosts discussions and presentations focused on how to integrate a broad range of languages to support oneAPI. @@ -10,18 +10,18 @@ implementations can contribute to the ISO C++ and SYCL specifications managed by ISO and Khronos respectively. The SIG does not discuss the design of SYCL APIs, just general feedback. -The language SIG is led by Biagio Cosenza . +The language SIG is led by Biagio Cosenza . You can sign up for the Language SIG mailing list on this `page `__ to receive updates and call information. Drop an email to the language SIG Chair if you have trouble subscribing to the list. 2026 Language SIG Quarterly Meetings ------------------------------------- +-------------------------------------- The Language SIG currently organizes its activities through quarterly meetings. Depending on the needs, additional meetings may be scheduled to discuss specific topics. -The Language SIG Chair is responsible for organizing the meetings. +The Language SIG Chair is responsible for organizing the meetings. The following are the meeting schedules for 2026: ================ ================================================ @@ -30,29 +30,34 @@ Date Agenda Feb 3, 2026 | oneDPL Overview and Update, Alexey Kukanov (Intel) May 5, 2026 | SYCL Offloading toolchain upstreaming, Yury Plyakhin (Intel) Jul 28, 2026 | TBB is 20!, Michael Voss (Intel) - | oneTBB meets the community, with two short talks: + | oneTBB meets the community, with two short talks: | - oneTBB use in DUNE/Phlex and in High-Energy Physics, Kyle Knoepfel (Fermilab) | - Scaling Drug Discovery via oneTBB, Federico Ficarelli (CINECA) Nov 3, 2026 | tbd ================ ================================================ -Previous Language SIG Meetings +Previous Language SIG Meetings ---------------------------------------- -Hereafter, you will find slides, recordings, and additional materials from the meetings that have already been held. +Hereafter, you will find slides, recordings, and additional materials from the meetings that have already been held. + +:2026-07-28: + | Twenty Years of TBB; oneTBB in high-energy physics and drug discovery + | Michael Voss, Kyle Knoepfel and Federico Ficarelli + | `Event details and presentation recording `__ :2026-02-03: | oneDPL Overview and Update | Alexey Kukanov (Intel) | `slides `__ -:2025-11-04: +:2025-11-04: | dpctl: Portable Data Parallel Extensions for Python | Nikita Grigorian (Intel) | `slides `__ - -:2025-08-05: + +:2025-08-05: | ParaS: Unified Programming Ecosystem for Architectural Portability Across Diverse Computing Needs | H.V. Deepika and A. Bisht (Centre for Development of Advanced Computing, Bengaluru) @@ -61,13 +66,13 @@ Hereafter, you will find slides, recordings, and additional materials from the m | Stefan Werner (Intel) | `recording `__ -:2025-02-04: +:2025-02-04: | SYCL Upstreaming - | Tom Honermann (Intel) + | Tom Honermann (Intel) | `slides `__ `recording `__ -:2024-11-05: +:2024-11-05: | SPIR-V extensions used by DPC++ | Victor Loemuller (Codeplay Software) | `slides `__ @@ -79,7 +84,7 @@ Hereafter, you will find slides, recordings, and additional materials from the m | Diptorup Deb (Intel) | `slides `__ -:2023-11-07: +:2023-11-07: | SYCL-Graphs: A Progress Update | Ewan Crawford, Ben Tracy, Maxime France-Pillois (Codeplay Software), Pablo Reble, Julian Miller (Intel) | `slides `__ @@ -91,7 +96,7 @@ Hereafter, you will find slides, recordings, and additional materials from the m | `slides `__ -Archived meeting notes from meetings held under the oneAPI +Archived meeting notes from meetings held under the oneAPI Community Forum can be found `here`_ .. _here: https://github.com/oneapi-src/oneAPI-tab/tree/main/language diff --git a/math/2024-04-24-UXL-Math-SIG.rst b/math/2024-04-24-UXL-Math-SIG.rst index 1d19d8b..dd374d0 100644 --- a/math/2024-04-24-UXL-Math-SIG.rst +++ b/math/2024-04-24-UXL-Math-SIG.rst @@ -2,6 +2,14 @@ Math Special Interest Group Meeting Notes ========================================= + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + 2024-04-24 ========== @@ -42,7 +50,7 @@ Agenda: New oneMKL sparse specification: -* Lots of help from Gajanan Choudhary and Spencer Patty as well. This is a follow up from a previous Math SIG meeting, where I explained some changes. Specification Pull Request `#522 `__ is in review. Main motivation for all changes was to better align with all of the backends we want to support, and make it easier to transition from existing applications to oneMKL interfaces. +* Lots of help from Gajanan Choudhary and Spencer Patty as well. This is a follow up from a previous Math SIG meeting, where I explained some changes. Specification Pull Request #522 (historical reference) is in review. Main motivation for all changes was to better align with all of the backends we want to support, and make it easier to transition from existing applications to oneMKL interfaces. * We are renaming some operations. * There will be a single function for different types of matrix-vector multiplication; gemv, symv, and trmv will all be replaced by spmv. * Similarly, gemm will become spmm, and trsv will be spsv. @@ -115,7 +123,7 @@ Updates from last meeting: * oneMKL interfaces v0.4 was released * In addition to the #sig-math channel on Slack, there is also a #onemkl channel for discussions on the oneMKL interfaces open source project. * The UXL Open Source Working Group created a checklist to ensure best practices are used in oneMKL interfaces and other open source projects; these tasks will be worked on in the coming months. -* The oneAPI spec repo was moved from https://github.com/oneapi-src/oneAPI-spec to https://github.com/uxlfoundation/oneAPI-spec. +* A specification-hosting migration was reported at this meeting. Current guidance is the `dynamic specification `__. * There are a couple of pull requests that may be of interest (including the one Romain discussed earlier in the meeting), as well as an open issue. * The spec moved to the uxlfoundation org, but the oneMKL interfaces will be moved to a different org? diff --git a/math/2024-10-02-UXL-Math-SIG.rst b/math/2024-10-02-UXL-Math-SIG.rst index ef42d40..0395f0a 100644 --- a/math/2024-10-02-UXL-Math-SIG.rst +++ b/math/2024-10-02-UXL-Math-SIG.rst @@ -2,6 +2,14 @@ Math Special Interest Group Meeting Notes ========================================= + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + 2024-10-02 ========== @@ -112,7 +120,7 @@ Q&A: * Raphael: Yes. * Romain: I don't think this has been a concern for the interface. -* I finalized these changes in a pull request: `#593 `__. +* I finalized these changes in a pull request: #593 (historical reference). * For anyone who might be looking at it, I separated the pull request into 2 main components. There are several aspects of the current specification that could be improved (typos, etc.), which are not strictly related to this proposal. Those are all in the first commit (not content-changing). Second commit covers what we covered here. If you'd prefer two separate PRs, we can do that. * Andrey: Currently these interfaces rely on vectors to pass multiple values around. Are there any plans to add support for std::span from C++20 instead of direct array? diff --git a/math/2025-02-26-UXL-Math-SIG.rst b/math/2025-02-26-UXL-Math-SIG.rst index 42ea228..7407312 100644 --- a/math/2025-02-26-UXL-Math-SIG.rst +++ b/math/2025-02-26-UXL-Math-SIG.rst @@ -2,6 +2,14 @@ Math Special Interest Group Meeting Notes ========================================= + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + 2025-02-26 ========== diff --git a/math/2026-05-13-UXL-Math-SIG.rst b/math/2026-05-13-UXL-Math-SIG.rst index 4c5417b..fa00fa6 100644 --- a/math/2026-05-13-UXL-Math-SIG.rst +++ b/math/2026-05-13-UXL-Math-SIG.rst @@ -2,6 +2,14 @@ Math Special Interest Group Meeting Notes ========================================= + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + 2026-05-13 ========== diff --git a/math/README.rst b/math/README.rst index 380b2da..f615f7e 100644 --- a/math/README.rst +++ b/math/README.rst @@ -1,6 +1,6 @@ -======================= +========================= UXL Foundation Math SIG -======================= +========================= The Math SIG hosts discussions and presentations for fundamental mathematical routines for use in high-performance computing, @@ -14,7 +14,11 @@ or error handling. The Math SIG is led by Sarah Knepper (Intel). -Archived meeting notes from meetings held under the oneAPI +For invitations and current meeting information, find the group through the +`UXL mailing lists `__. +See the `project directory <../PROJECTS.md>`__ for current library documentation. + +Archived meeting notes from meetings held under the oneAPI Community Forum can be found `here`_ .. _here: https://github.com/oneapi-src/oneAPI-tab/tree/main/math diff --git a/monthly-status/README.md b/monthly-status/README.md new file mode 100644 index 0000000..0d354ce --- /dev/null +++ b/monthly-status/README.md @@ -0,0 +1,22 @@ +# Foundation status report archive + +These dated reports preserve updates as published. They are not a current roadmap. + +[Foundation home](../README.md) + +- [UXL-Foundation Status-2025-05]() +- [UXL-Foundation Status-2025-04]() +- [UXL-Foundation Status-2025-03]() +- [UXL-Foundation Status-2025-02]() +- [UXL-Foundation Status-2025-01]() +- [UXL-Foundation Status-2024-11]() +- [UXL-Foundation Status-2024-10]() +- [UXL-Foundation Status-2024-09]() +- [UXL-Foundation Status-2024-08]() +- [UXL-Foundation Status-2024-07]() +- [UXL-Foundation Status-2024-06]() +- [UXL-Foundation Status-2024-05]() +- [UXL-Foundation Status-2024-04]() +- [UXL-Foundation Status-2024-03]() +- [UXL-Foundation Status-2024-01]() +- [UXL-Foundation Status-2023-12]() diff --git a/safety-critical/README.rst b/safety-critical/README.rst index 9d3f3ed..a467a94 100644 --- a/safety-critical/README.rst +++ b/safety-critical/README.rst @@ -1,6 +1,6 @@ -================================== +==================================== UXL Foundation Safety Critical SIG -================================== +==================================== The Safety Critical SIG hosts discussions and presentations on functional safety topics as relating to the UXL specification @@ -8,4 +8,18 @@ and implementation. The aim of the SIG is to enable or accelerate integration of UXL elements into safety critical systems, targeting markets such as automotive and avionics. -The Safety Critical SIG is led by Verena Beckham (Codeplay). \ No newline at end of file +The Safety Critical SIG is led by Verena Beckham (Codeplay). + +Participation and records +--------------------------- + +For current meeting information, find the group through the +`UXL mailing lists `__ and the +`foundation participation guide <../README.md#join-the-community>`__. + +Published meeting notes: + +* `2024-05-29 <2024-05-29-UXL-SC-SIG.rst>`__ +* `2024-02-28 <2024-02-28-UXL-SC-SIG.rst>`__ + +`Foundation home <../README.md>`__ diff --git a/steering-committee/2024-01-11-UXL-Steering-Committee.rst b/steering-committee/2024-01-11-UXL-Steering-Committee.rst index 17be9b0..8cdc230 100644 --- a/steering-committee/2024-01-11-UXL-Steering-Committee.rst +++ b/steering-committee/2024-01-11-UXL-Steering-Committee.rst @@ -2,6 +2,14 @@ UXL Foundation Steering Committee Meeting 11th Jan 2024 ======================================================= + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + Attendees - Rod Burns (Codeplay) Chairperson - Robert Cohn (Intel) @@ -21,8 +29,8 @@ Agenda General ------- -Operational procedures are published as draft with final chance for -review. A release branch has been created `on GitHub `_ +Operational procedures are published as draft with final chance for +review. A release branch has been created `on GitHub `_ and this defines the current operational procedures for the foundation. The members will continue to review and update these when required. @@ -30,16 +38,16 @@ The members will continue to review and update these when required. Working Group Priorities ------------------------ -The groups previously discussed what the priorities should be for the -two working groups - Specification and Open Source. A general +The groups previously discussed what the priorities should be for the +specification and open-source work. A general summary of these was presented and discussed. -The Steering Committee will publish a set of more detailed priorities +The Steering Committee will publish a set of more detailed priorities on the GitHub repository for the Working Groups. -The groups will meet on a regular basis, the intention initially is -for the Open Source Working Group to meet every two weeks, and the -Specification Working Group will decide the frequency when they meet. +The groups will meet on a regular basis, the intention initially is +for open-source discussions to take place every two weeks. The cadence +for specification discussions remained to be decided. **Specification Priorities** @@ -47,12 +55,12 @@ Specification Working Group will decide the frequency when they meet. - Roadmap for releases - Best practices for community feedback on new APIs and designs -The Specification Working Group is planning the migration of the -specification rendered content to GitHub pages from Intel internal +The meeting discussed plans for migration of the +specification rendered content to GitHub pages from Intel internal infrastructure. -The group will also prioritise the alignment of how changes are shared -for review. Some projects have a RFC process and others a variation on +The group will also prioritise the alignment of how changes are shared +for review. Some projects have a RFC process and others a variation on this. A roadmap is already under discussion and will be published in due course. @@ -68,17 +76,17 @@ A roadmap is already under discussion and will be published in due course. Discussion points: -The structure of this group will need to be agreed by the members, it may +The structure of this group will need to be agreed by the members, it may be necessary to split this into multiple sub-groups as well as work packages. -Members can help to bring credits to the foundation for cloud environments -that can be used for build and testing of any of the projects. +Members can help to bring credits to the foundation for cloud environments +that can be used for build and testing of any of the projects. (e.g. AWS, Google Cloud, MS Azure...) -The TensorFlow project provides the ability for commmunity members to hook their -own infrastructure into the project to build and test on specific targets. This -is something we should encourage for UXL projects. For example Intel already has -a set of infrastructure for building and testing. Other members and contributors +The TensorFlow project provides the ability for commmunity members to hook their +own infrastructure into the project to build and test on specific targets. This +is something we should encourage for UXL projects. For example Intel already has +a set of infrastructure for building and testing. Other members and contributors should be able to add their own. diff --git a/steering-committee/2024-06-27-UXL-Steering-Committee.rst b/steering-committee/2024-06-27-UXL-Steering-Committee.rst index 211f668..b03707c 100644 --- a/steering-committee/2024-06-27-UXL-Steering-Committee.rst +++ b/steering-committee/2024-06-27-UXL-Steering-Committee.rst @@ -2,6 +2,14 @@ UXL Foundation Steering Committee Meeting 27 June 2024 ====================================================== + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + Attendees * Rod Burns (Codeplay) Chairperson diff --git a/steering-committee/2024-07-11-UXL-Steering-Committee.rst b/steering-committee/2024-07-11-UXL-Steering-Committee.rst index 5e937e7..25d57d2 100644 --- a/steering-committee/2024-07-11-UXL-Steering-Committee.rst +++ b/steering-committee/2024-07-11-UXL-Steering-Committee.rst @@ -2,6 +2,14 @@ UXL Foundation Steering Committee Meeting 11 July 2024 ====================================================== + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + Attendees * Rod Burns (Codeplay) Chairperson @@ -28,14 +36,14 @@ Level Zero - It was noted that the spec of Level Zero is part of the oneAPI specification (not UXL). The recommended approach would be that OpenCL would be used. There was no opposition to moving Level Zero out of the spec - The SC discussed the question of inviting a project to join the UXL Foundation previously presented. -- Consensus was not previously reached. -- Rod mentioned possible options moving forward: - - A formal vote (requires 75% of votes to carry) +- Consensus was not previously reached. +- Rod mentioned possible options moving forward: + - A formal vote (requires 75% of votes to carry) - The project joins a different open governance organization It was agreed to have deeper offline discussions on how we see this working and what could be different. -Strategy +Strategy ======== Rod mentioned that he had shared the strategy presentation and is looking for feedback. He will share the document again. diff --git a/steering-committee/2024-08-01-UXL-Steering-Committee.rst b/steering-committee/2024-08-01-UXL-Steering-Committee.rst index 5423600..bcce6ee 100644 --- a/steering-committee/2024-08-01-UXL-Steering-Committee.rst +++ b/steering-committee/2024-08-01-UXL-Steering-Committee.rst @@ -2,6 +2,14 @@ UXL Foundation Steering Committee Meeting 1 Aug 2024 ==================================================== + +.. note:: + + Current guidance: the `dynamic oneAPI specification `__ + links to the concepts and project documentation maintained today. These minutes + record the discussion at the meeting date; release plans and API descriptions + below are historical. Obsolete destinations have been updated or removed. + Attendees * Rod Burns (Codeplay) Chairperson diff --git a/steering-committee/2024-08-08-UXL-Steering-Committee.rst b/steering-committee/2024-08-08-UXL-Steering-Committee.rst index 8c55e5c..3175c37 100644 --- a/steering-committee/2024-08-08-UXL-Steering-Committee.rst +++ b/steering-committee/2024-08-08-UXL-Steering-Committee.rst @@ -1,9 +1,9 @@ -====================================================== +========================================================= UXL Foundation Steering Committee Meeting 8 August 2024 -====================================================== +========================================================= Attendees -========= +=========== * Alison Richards, Chair protem (Intel) * Robert Cohn (Intel) * Masahiro Doteguchi (Fujitsu) @@ -19,27 +19,27 @@ Attendees * Melissa Aranzamendez (Linux Foundation) Notes: -====== -- Alison reported that she is chairing the meeting on behalf of Rod, who is on leave this week. - +======== +- Alison reported that she is chairing the meeting on behalf of Rod, who is on leave this week. + oneAPI Dev Summit hosted by UXL Foundation -========================================== +============================================ - Sri presented an update -- Important dates: Call for papers is live Aug 2-Aug 30 (https://sessionize.com/uxldevsummit). Registration to open 9/13. +- Important dates: Call for papers is live Aug 2-Aug 30 (https://sessionize.com/uxldevsummit). Registration to open 9/13. - October 9 - APAC Dev Summit (virtual) - October 10 - NA/EMEA Dev Summit (virtual) - SC Members are requested to submit papers, promote the event, and advertise the CFP - + UXL Foundation Membership Process -================================= +=================================== - Melissa reported on the current membership: 9 Steering Members; 1 General Member in pipeline; 19 Contributor Members, 1 in pipeline UXL Foundation GTM Kit (Tradeshow) -================================== +==================================== - Alison reported on the Marketing Kit which provides resources mainly for Members' marketing teams. UXL Foundation One-Year Anniversary -=================================== +===================================== - We are approaching the UXL Foundation’s one-year UXL anniversary and will be pushing articles and blogs - We have issued a survey to get feedback from the community - We will also be organizing an All Hands Meeting after the DevSummit to engage with the community and go over what we have accomplished and what is the moonshot for our Foundation. diff --git a/steering-committee/2025-01-09-UXL-Steering-Committee.rst b/steering-committee/2025-01-09-UXL-Steering-Committee.rst index 8268411..4bfdc6a 100644 --- a/steering-committee/2025-01-09-UXL-Steering-Committee.rst +++ b/steering-committee/2025-01-09-UXL-Steering-Committee.rst @@ -9,7 +9,7 @@ Attendees * Evgeny Drapkin (GE Healthcare) * Penporn Koanantakool (Google) * John Melonakos (Intel) -* Dave Murray (Imagination) +* Dave Murray (Imagination) * Ramesh Radhakrishnan (Broadcom) * Chris Reed (GE Healthcare) * Priyanka Sharma (Fujitsu Limited) @@ -17,20 +17,20 @@ Attendees * Andrew Wafaa (Arm Limited) * Melissa Aranzamendez (Linux Foundation) -Not present: +Not present: * Rod Burns, Chair (Codeplay). Alison chaired the meeting since Rod was not able to attend. Notes: * Alison went over updates and ongoing items -* 1.4 spec published here: https://oneapi-spec.uxlfoundation.org/ +* Version 1.4 publication was reported at this meeting. Current guidance is the `dynamic specification `__. * 2025 WG and SIG mtg dates are on the calendar, invitations have been sent * There were no concerns from the Steering Committee wrt the 2025 budget -* Members discussed potential F2F meetings in conjunction with: +* Members discussed potential F2F meetings in conjunction with: * embedded world - Mar 11-13, Nuremberg * Open Source Summit North America 2025 - Jun 23-Jun 25, Denver * PyTorch Conference 2025 - Oct 22-23, San Francisco - * SC '25 - Nov 16-21, St. Louis + * SC '25 - Nov 16-21, St. Louis * SC members agreed to continue with the existing meeting cadence, i.e., every other week * The Annual Report has been published and members were asked to distribute it within their organizations diff --git a/steering-committee/README.rst b/steering-committee/README.rst index 41828e5..399841b 100644 --- a/steering-committee/README.rst +++ b/steering-committee/README.rst @@ -1,11 +1,11 @@ -================================= +=================================== UXL Foundation Steering Committee -================================= +=================================== The Steering Committee is formed of representatives from Steering Members of the UXL Foundation. -The committee usually meets every two weeks and is responsible for making decisions about the -overall organization and governance of the foundation. The groups also approves the plans and +The committee usually meets every two weeks and is responsible for making decisions about the +overall organization and governance of the foundation. The committee also approves the plans and outputs from the Working Groups. Minutes from the Steering Committee meetings are made available in this folder. @@ -40,6 +40,8 @@ Minutes from the Steering Committee meetings are made available in this folder. `9th January 2025 <2025-01-09-UXL-Steering-Committee.rst>`_ +`12th December 2024 <2024-12-12-UXL-Steering-Committee.rst>`_ + `5th December 2024 <2024-12-05-UXL-Steering-Committee.rst>`_ `14th November 2024 <2024-11-14-UXL-Steering-Committee.rst>`_ @@ -50,7 +52,9 @@ Minutes from the Steering Committee meetings are made available in this folder. `3rd October 2024 <2024-10-03-UXL-Steering-Committee.rst>`_ -`19th September 2024 <2024-09-05-UXL-Steering-Committee.rst>`_ +`19th September 2024 <2024-09-14-UXL-Steering-Committee.rst>`_ + +The September 19 record retains its original September 14 filename. `5th September 2024 <2024-09-05-UXL-Steering-Committee.rst>`_