[logseq-plugin-git:commit] 2026-01-29T07:22:37.304Z

2026-01-29 08:22:38 +01:00
parent 286eea752e
commit db5859b0cd
9 changed files with 153 additions and 125 deletions
@@ -251,4 +251,14 @@
  todoist-due:: 2026-01-31
  todoist-desc:: Subject: EASE2026 submission assignment (as leading reviewers) Sender: ease2026@easychair.org Weblink: [Outlook](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAih8lmqAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) Content Summary: You are assigned as the Leading Reviewer for papers (62) and (184) in the EASE 2026 conference. Your role involves facilitating the review process by ensuring review quality, initiating and moderating discussions, and writing a meta-review with a recommendation. Subtasks: 1. Check colleagues' reviews for appropriate and constructive language. Request clarifications through EasyChair comments if issues are found. 2. Initiate the discussion starting February 27th, even if some reviews are still missing. 3. Moderate the discussion to help reach a consensus by March 10th. 4. Write a brief meta-review summarizing the discussion and giving a recommendation (accept/reject) for the Program Chairs. 5. Submit your final recommendations by March 10th, AoE. Deadline: March 10th, AoE Labels: ai-generated-main-task
  todoist-labels:: #ai-generated-main-task
+  todoist-status:: ◼️
+- [[2026-01-31]] [Buongiorno Prof. Dovrei aver concluso il progetto con lo sviluppo dei 4 punti che ci siamo detti sopra durante l'esame. Spiego di seguito: un container per ogni componente: Ogni componente logico (Monitor, Analyzer, Planner, Executor, Knowledge Base) è eseguito in un container Docker dedicato e isolato, garantendo modularità, ognuno con le sue dipendenze. estensibilità rispetto a sensori vs attuatori: ho superato la logica hardcoded come ci eravamo detti in riferimento alla slide 06_Slides-Control-Systems-v2.pdf implementando una gestione basata su Control Loops configurabili. Il sistema ora non conosce a priori le regole, ma istanzia dinamicamente i loop (es. Hydration Loop, Safety Loop) leggendoli dalla configurazione. Questo garantisce la totale estensibilità rispetto a nuovi sensori o nuove regole di adattamento senza ricompilare il codice. configurazione con un container dedicato: ho implementato un container dedicato (config-server) che agisce come Single Source of Truth, iniettando le policy di adattamento e la topologia a runtime. documentazione: È allegato il report PDF strutturato secondo il template fornito, completo di tassonomia dell'adattamento, logica formale e validazione visiva degli scenari tramite Dashboard Grafana.Ho inserito tutto nel repo https://github.com/ocraton/smart-olive-grove](https://teams.microsoft.com/l/message/19:afb6a496-7b16-4b74-8c53-1cd450e586f9_c2787b22-cc39-410e-a383-56cbdb9b69c9@unq.gbl.spaces/1769424079721?context=%7B%22contextType%22:%22chat%22%7D)
+  todoist-id:: [6frVX6QM6Jp4jRw8](https://todoist.com/showTask?id=6frVX6QM6Jp4jRw8)
+  todoist-project:: #👨‍🏫 Teaching
+  todoist-due:: 2026-01-31
+  todoist-status:: ◼️
+- [[2026-01-31]] [Hi Professor, I just wanted to let you know that we have updated everything based on your feedback for the IoT project. The following major changes are now implemented:- The threshold values used for Telegram notifications are now fully dynamic (loaded from the config).- The Grafana dashboards update automatically whenever a new sensor or threshold is added. - All sensor units are now loaded dynamically from the config file.- The main configuration file has been moved to its own `config` directory.](https://teams.microsoft.com/l/message/19:e8e48abcf7934e2b90680ff9c1d56b99@thread.v2/1769154556182?context=%7B%22contextType%22:%22chat%22%7D)
+  todoist-id:: [6fqFgJPRQHf9hcGg](https://todoist.com/showTask?id=6fqFgJPRQHf9hcGg)
+  todoist-project:: #👨‍🏫 Teaching
+  todoist-due:: 2026-01-31
  todoist-status:: ◼️