25-02425 Detailed Specifications ARTIQ Zynq batching.docx
DOCX document 22 KB Posted
- Attached to
- ARTIQ Zynq Batching and Ndscan Federal contract opportunity
- Solicitation number
- NB688000-25-02425
About this file
This document is a detailed specification for the National Institute of Standards and Technology (NIST) seeking commercial product development for ARTIQ Zynq event batching and ndscan compatibility. The technical requirements include implementing RTIO event batching for Zynq-based core devices, developing a new context manager for RTIO event transmission, and integrating modifications to enable ndscan package use without patching ARTIQ. Specifically, the specifications mandate increased RTIO event throughput, a new "with batch" context in ARTIQ-Python, and full integration into the main ARTIQ GitHub repository.
The sources sought announcement is a market research tool to identify potential vendors, with a potential small business set-aside if at least two qualified small businesses are found. The procurement is categorized under NAICS code 334516 (Analytical Laboratory Instrument Manufacturing) with a small business size standard of 1,000 employees. Interested businesses are requested to submit four-page electronic capability statements to Angela Hitt via email, including company details, manufacturing origin, product specifications, lead times, and relevant experience. The solicitation is not a formal Request for Proposals and does not commit the government to an immediate contract award.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 25-02425 Requirements and Specifications ARTIQ zynq batching.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Detailed specifications for Ion Storage Group ARTIQ Zynq event batching and ndscan compatibility requisition. Terminology is as defined in the linked GitHub repositories listed below and their associated code and documentation.
Specifications for ARTIQ Zynq event batching
1. Must implement the capability of RTIO event batching for all Zynq-based core devices for ARTIQ (Kasli SoC and ZC706). The event batching means collecting a buffer of RTIO events from the kernel and transmitting them as a batch from the hard processor to the RTIO engine in the FPGA fabric.
2. The batching must result in an increased average sustained RTIO event throughput rate from the hard processor to the RTIO engine in the FPGA fabric relative to that achievable in ARTIQ 8.0.
3. Must develop a new context manager (such as “with batch”) to be added to ARTIQ-Python for the user to enable RTIO event batching as described above in relevant kernel sections.
4. All RTIO events within a “with batch” context will be transmitted from hard processor to the RTIO engine in the FPGA fabric as a batch, upon closing of the “with batch” context, or through an explicit method that calls for the transmission of all the currently enqueued batched events without leaving the “with batch” context.
5. All of the above functionalities must be integrated into the main ARTIQ repository at https://github.com/m-labs/artiq, must be included in the next ARTIQ release after their satisfactory completion and testing, and must be usable for ARTIQ installations made through any standard ARTIQ installation channel (not requiring ARTIQ to be built from source).
Specifications for ndscan integration
1. Must implement all necessary modifications to ARTIQ to enable the use of the ndscan package at https://github.com/OxfordIonTrapGroup/ndscan without patching ARTIQ.
2. Implementation must work for NAC-3 ARTIQ compiler.
3. All of the above functionalities must be integrated into the main ARTIQ repository at https://github.com/m-labs/artiq, must be included in the next ARTIQ release after their satisfactory completion and testing, and must be usable for ARTIQ installations made through any standard ARTIQ installation channel (not requiring ARTIQ to be built from source).
File details come from the government source that posted it. Updated .