Generate variant JSONs and device_db files? #141

Closed
opened 2024-07-09 11:11:13 +08:00 by esavkin · 1 comment
Contributor

I think this would pave the way to the more user-friendly AFWS management, where customers can change their variants configurations without helpdesk.

As an immediate benefit, this can potentially ease the assembly and helpdesk processes, and would help store more complete information about systems shipped.

I think this would pave the way to the more user-friendly AFWS management, where customers can change their variants configurations without helpdesk. As an immediate benefit, this can potentially ease the assembly and helpdesk processes, and would help store more complete information about systems shipped.
Owner

Having a common JSON format makes some sense, though there is information like shipping that shouldn't be in the device JSON.
The device database can be generated from artiq using artiq_ddb_template, which works in user shells since ARTIQ-8, and there is no point making a web interface to it.

Having a common JSON format makes some sense, though there is information like shipping that shouldn't be in the device JSON. The device database can be generated from artiq using artiq_ddb_template, which works in user shells since ARTIQ-8, and there is no point making a web interface to it.
sb10q closed this issue 2025-03-14 12:17:59 +08:00
Sign in to join this conversation.
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: M-Labs/web2019#141