[logseq-plugin-git:commit] 2026-01-29T11:16:10.274Z
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
icon:: ✏️
|
||||
generation_time:: [[2026-01-29]] T10:00:25Z
|
||||
generation_time:: [[2026-01-29]] T11:00:25Z
|
||||
|
||||
- # **TODOs and IDEAs**
|
||||
- {{query (and [[TODO]] [[KaraKeep-Highlights]] (or [[Ideas]] [[KaraKeep-Highlights]]))}}
|
||||
|
||||
@@ -54,17 +54,17 @@
|
||||
todoist-status:: ✅
|
||||
- [[2026-01-29]] SE4IOT Final Project Update - Team 7
|
||||
todoist-id:: [6frhPXP6xcPW7gF8](https://todoist.com/showTask?id=6frhPXP6xcPW7gF8)
|
||||
todoist-project:: #Inbox
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-01-29
|
||||
todoist-desc:: From: meteharun.akcay@student.univaq.it Received: 2026-01-29T10:13:50Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAii1IdqAAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, here's a summary of the email content, followed by actionable task recommendations: **Summary of Email Content:** The email is a follow-up to a feedback discussion regarding a Smarthouse project. It details the following: * **Implemented Updates:** The code has been updated and is available in the GitHub repository at `https://github.com/phuc-tr/smarthouse`. * **Changes Summarized:** * Room profiles are now configurable within the simulator/config.yaml. * A .env file has been added for the required environment variables. * Altering the alerting logic is now possible without Node-RED changes. * **Request for Review:** The author requests review and feedback on the updated code. * **Actionable Task Recommendation:** The author suggests reviewing the changes and notifying them about any further adjustments needed. **Actionable Task Recommendations (Todoist Task Creation):** 1. **Create a Task:** "Review Smarthouse Project Updates - GitHub" 2. **Assign Priority:** High (As this is a follow-up and requires verification) 3. **Due Date:** Ideally, within 24-48 hours (to allow for review and testing) 4. **Include Details:** Add: “Investigate the .env file configuration. Confirm the environment variable loading mechanism is working as expected." 5. **Consider:** "Check if any further configuration changes are needed in the YAML configuration files." Let me know if you'd like me to refine this further! --- Dear Professor, Following your feedback on our Smarthouse project, we implemented the requested improvements. The updated version is now available in our GitHub repository: [GitHub - phuc-tr/smarthouse](https://github.com/phuc-tr/smarthouse) The changes are summarized below: *
|
||||
todoist-status:: ◼️
|
||||
- [[2026-01-29]] [Ciao Prof,For our team IoT exam on 13th February 2 pm is fine, but for Autonomous can we take exam on 17th February 11:30 am instead since we already have another exam on 18th February](https://teams.microsoft.com/l/message/19:754a431125ac4ec0a155dd5146ee451b@thread.v2/1769681470587?context=%7B%22contextType%22:%22chat%22%7D)
|
||||
todoist-id:: [6frhMFhPQgMPjfcg](https://todoist.com/showTask?id=6frhMFhPQgMPjfcg)
|
||||
todoist-project:: #Inbox
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-01-29
|
||||
todoist-status:: ◼️
|
||||
- [[2026-01-29]] [Buongiorno professore, io ho problemi di autorizzazione nel vedere i l’excel sul teams](https://teams.microsoft.com/l/message/19:4f63fced-a9df-4e41-92c8-1629a26533b0_c2787b22-cc39-410e-a383-56cbdb9b69c9@unq.gbl.spaces/1769681590771?context=%7B%22contextType%22:%22chat%22%7D)
|
||||
todoist-id:: [6frhMGP7gJXx7r8g](https://todoist.com/showTask?id=6frhMGP7gJXx7r8g)
|
||||
todoist-project:: #Inbox
|
||||
todoist-project:: #👨🏫 Teaching
|
||||
todoist-due:: 2026-01-29
|
||||
todoist-status:: ◼️
|
||||
@@ -245,13 +245,6 @@
|
||||
todoist-desc:: From: lolaburgueno@uma.es
|
||||
todoist-labels:: #goal #logseqed
|
||||
todoist-status:: ◼️
|
||||
- [[2026-01-31]] 🧠 Manage EASE 2026 Leading Reviewer Submission Review Process
|
||||
todoist-id:: [6frGf8cR7g3RFwMg](https://todoist.com/showTask?id=6frGf8cR7g3RFwMg)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
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
|
||||
|
||||
@@ -26,7 +26,7 @@
|
||||
todoist-project:: #🎓 Services-PHDICT
|
||||
todoist-due:: 2026-02-02
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-02]] 🧠 Review and Complete Paper Assignments for EASE 2026 Research Papers Track
|
||||
- [[2026-02-02]] 🧠 EASE 2026 Research Papers Track
|
||||
todoist-id:: [6frFf4WCxMV283m6](https://todoist.com/showTask?id=6frFf4WCxMV283m6)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-due:: 2026-02-02
|
||||
@@ -96,4 +96,11 @@
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-due:: 2026-02-02
|
||||
todoist-desc:: From: onbehalfof@manuscriptcentral.com Received: 2026-01-08T15:15:16Z ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAiVbuR5AAA%3D&exvsurl=1&viewmodel=ReadMessageItem) --- Okay, here's a summary of the email, formatted as a task description with actionable steps: **Task: Review Manuscript - 'Evaluating Incompatible Third-party Library API Usage in LLM-based Code Completion'** **Objective:** To thoroughly review the provided manuscript titled "Evaluating Incompatible Third-party Library API Usage in LLM-based Code Completion" submitted to *Transactions on Software Engineering and Methodology*. **Instructions:** 1. **Locate Manuscript:** Access the manuscript at: * [ScholarOne Manuscripts](https://mc.manuscriptcentral.com/tosem?URL_MASK=f8e067daf3c948909c391290bf2da5b7) * Alternatively, access the manuscript through the system at: [http://mc.manuscriptcentral.com/tosem (in the reviewer center)] 2. **System Login & Paper Download:** Follow the instructions to log in to the system and download the manuscript. 3. **Review and Identify Missing Literature:** * Identify any relevant literature that is missing from the reference list. * For each relevant paper: * Collect the names of all authors. * Retrieve the paper title. * Retrieve the journal/book title where the paper was published. * Find the year of publication. * Obtain the URL link to the paper. * Justify why this source is relevant – highlight a key aspect or contribution. 4. **Report Generation:** Create a report summarizing your findings, including the bibliographic information of the relevant literature. 5. **Report Formatting:** Use the provided template for report formatting. **Deliverable:** A completed report containing the collected bibliographic information and justification for the identified literature. **Notes:** The primary focus is on verifying the accuracy and completeness of the manuscript's bibliographic information and identifying potential missing sources of literature. Ensure the report highlights key findings and is well-organized. --- 08-Jan-2026 Dear Dr. Di Ruscio, Thank you for agreeing to review the following paper submitted for possible publication to Transactions on Software Engineering and Methodology: Evaluating Incompatible Third-party Library API Usage in LLM-based Co
|
||||
todoist-status:: ◼️
|
||||
- [[2026-02-02]] 🧠 Manage EASE 2026 Leading Reviewer Submission Review Process
|
||||
todoist-id:: [6frGf8cR7g3RFwMg](https://todoist.com/showTask?id=6frGf8cR7g3RFwMg)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-due:: 2026-02-02
|
||||
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:: ◼️
|
||||
@@ -2711,4 +2711,20 @@
|
||||
- [[No due date]] (30) Colin Atkinson, Mattias Ulbrich, Romain Pascual and Erik Burger. Endotrophic Models: Formalizing Inter-Model Consistency and Semantic Overlap
|
||||
todoist-id:: [6frhCMrvj87rRx9c](https://todoist.com/showTask?id=6frhCMrvj87rRx9c)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-status:: ◼️
|
||||
- [[No due date]] (62) A Universal Textual Merge Strategy Based on Tokens for Version Control Systems
|
||||
todoist-id:: [6frhcRq97mVMVM5c](https://todoist.com/showTask?id=6frhcRq97mVMVM5c)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-status:: ◼️
|
||||
- [[No due date]] (108) STLGT: A Scalable Trace-Based Linear Graph Transformer for Tail Latency Prediction in Microservices
|
||||
todoist-id:: [6frhcRm7Vxxm8GRc](https://todoist.com/showTask?id=6frhcRm7Vxxm8GRc)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-status:: ◼️
|
||||
- [[No due date]] (118) Sustainability of Open Source Machine Learning Robustness Assessment Tools: A Repository Mining Study
|
||||
todoist-id:: [6frhcRp7xXmhMcVc](https://todoist.com/showTask?id=6frhcRp7xXmhMcVc)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-status:: ◼️
|
||||
- [[No due date]] (184) Exploring Creativity in Human–Human-LLM Collaborative Software Design
|
||||
todoist-id:: [6frhcRrgvQ7rh596](https://todoist.com/showTask?id=6frhcRrgvQ7rh596)
|
||||
todoist-project:: #📜 REVIEWS
|
||||
todoist-status:: ◼️
|
||||
Reference in New Issue
Block a user