Generate variant JSONs and device_db files? #141

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

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.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/web2019#141
No description provided.