Skip to main content
. 2024 Nov 8;15:9669. doi: 10.1038/s41467-024-54067-7

Fig. 9. Copilot of OCTOPUS.

Fig. 9

Copilot of OCTOPUS consists of seven steps for code generation and customization in OCTOPUS. Gray boxes represent the generated codes. a Action generation: Device actions are facilitated through GPT recommendations and a client feedback system. Code generation occurs within the module node and device server. b Task generation: Module tasks are generated through GPT recommendations and the client feedback system. c Action sequence generation: Action sequences for tasks are generated through GPT recommendations and the client feedback system. Before the GPT modeling process begins, the generated tasks and actions are added to the GPT prompt. d Task template and type validation: Task templates and type validations are generated through GPT recommendations and the client feedback system. Before the GPT modeling process begins, the generated tasks are added to the GPT prompt. Code generation takes place in the task generator and action translator. e IP address and port number registration: This step establishes connections with the module node. Code generation occurs in the action executor. f Task registration with long device standby time: Tasks with long device standby times are registered through the client feedback system using the generated tasks. Code generation takes place in the job trigger. g Device registration: New devices are registered in the device status table and masking table for task execution through the client feedback system, using the generated tasks and actions. Code generation takes place in the resource manager.