logseq/pages/todoist___2026-01-31.md

• 2026-01-31 Fare rinnovo contratto via Zara todoist-id:: 6fhrmQrx8rwwwWFm todoist-project:: #📗 Personal todoist-due:: 2026-01-31 todoist-status:: ◼️
• 2026-01-31 Lavorare su seminario Unimib che si terrà il 18 febbraio todoist-id:: 6fpJW47vMQxgM9Q3 todoist-project:: #👷 WORK todoist-due:: 2026-01-31 todoist-status:: ◼️
• 2026-01-31 Rivedere Composizione Collegio todoist-id:: 6X4Jp7W4VW84FHqh todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-31 todoist-labels:: #goal todoist-status:: ◼️
• 2026-01-31 Nominare nuovo rappresentante studenti todoist-id:: 6fWVrV7q926WxpGh todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-31 todoist-status:: ◼️
• 2026-01-31 TOOL DEMO TRACK - MODELS 2026 Organizing Committee todoist-id:: 6fQ7HCGxPvcHGHgg todoist-project:: #💺 EditoringChairing todoist-due:: 2026-01-31 todoist-desc:: From: lolaburgueno@uma.es todoist-labels:: #goal #logseqed 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 todoist-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. todoist-id:: 6fqFgJPRQHf9hcGg todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-01-31 todoist-status:: ◼️
• 2026-01-31 SE4IOT Final Project Update - Team 7 todoist-id:: 6frhPXP6xcPW7gF8 todoist-project:: #👨‍🏫 Teaching todoist-due:: 2026-01-31 todoist-desc:: From: meteharun.akcay@student.univaq.it Received: 2026-01-29T10:13:50Z ✉: Web Link --- 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 The changes are summarized below: * todoist-status:: ◼️
• 2026-01-31 Proposta per Univaq On Air - Dottorandi di Ricerca todoist-id:: 6fmfWgpGcX7V285g todoist-project:: #🎓 Services-PHDICT todoist-due:: 2026-01-31 todoist-desc:: Weblink: Outlook Email Content Summary: Proposal for the Univaq podcast to feature a series of interventions by research PhD students across various scientific areas and schools. The initiative aligns with the goal to narrate the life of an important and dynamic academic community. Seeking opinion and coordination for necessary steps from the coordinator of the podcast. No specific deadlines mentioned. todoist-labels:: #ai-generated #ai-generated-main-task todoist-status:: ◼️
• 2026-01-31 Re: FW: FW: Un breve corso su Quantum Computing todoist-id:: 6frj3mGxqcGgmqvg todoist-project:: #Inbox todoist-due:: 2026-01-31 todoist-desc:: Web Link Okay, based solely on the subject line "Re: FW: FW: Un breve corso su Quantum Computing" (A brief course on Quantum Computing), it's highly probable that someone forwarded information about a quantum computing course, and the current email is a response or a directive related to that information. Here's an actionable task description, assuming the most common scenario: the sender wants the recipient to investigate this course further for potential team training or personal development. --- ## Task: Evaluate Quantum Computing Course for Team Training Description: Following up on the forwarded email chain "Un breve corso su Quantum Computing," the goal is to assess the suitability of this brief quantum computing course as a potential training opportunity for the team or relevant individuals. This involves gathering key details, evaluating its content, and determining feasibility. Source Email: * Subject: Re: FW: FW: Un breve corso su Quantum Computing * Likely Sender: [Person who sent the email to you] * Likely Context: The sender has seen information about a quantum computing course and is prompting further investigation. Priority: Medium Due Date: [Suggest a date, e.g., End of next week, 2023-11-24] Assigned To: [Your Name/Recipient of the email] Actions to Accomplish: 1. Locate Original Course Information: * Find the initial email in the thread that contains the details, link, or attachment for "Un breve corso su Quantum Computing." * If the link/information isn't immediately obvious, try searching your inbox for earlier "FW: Un breve corso su Quantum Computing" emails or ask the sender for clarification. 2. Gather Key Course Details: * Curriculum/Topics: What specific quantum computing concepts are covered? * Duration: How long is the course (hours, days, weeks)? * Format: Is it online, in-person, self-paced, live lectures? * Prerequisites: What prior knowledge (e.g., math, programming) is required? * Cost: What is the registration fee? Are there group discounts or organizational rates? * Language: Is the course entirely in Italian, or are there English options/materials? * Instructor(s): Who is teaching it, and what are their qualifications? * Dates/Schedule: When does the course run or when is registration open? 3. Evaluate Suitability for Team/Individuals: * Relevance: Does the course content align with current team projects, future goals, or skill gaps? * Audience: Who on the team would benefit most from this course? (e.g., developers, researchers, project managers). * Level: Is it an introductory, intermediate, or advanced course, and does it match the team's current knowledge level? 4. Assess Logistics & Feasibility: * Time Commitment: Can team members realistically dedicate the necessary time? * Budget: Is the cost within current training budgets? * Availability: Does the course schedule conflict with critical project deadlines or other commitments? 5. Prepare a Summary & Recommendation: * Compile the key findings from steps 2-4 into a concise summary. * Include a recommendation on whether to pursue this course (e.g., recommend for specific individuals, recommend for the whole team, recommend against it, suggest alternatives). * Highlight potential benefits and any significant challenges (cost, time, prerequisites). Expected Outcome: A brief report or email containing the essential details of the quantum computing course, an assessment of its suitability, and a clear recommendation for next steps. todoist-labels:: #outlook365 todoist-status:: ◼️
• 2026-01-31 ECMFA 2026 submission assignment todoist-id:: 6ffWC97GGvHG4qG8 todoist-project:: #📜 REVIEWS todoist-due:: 2026-01-31 todoist-desc:: Web Link Okay, here’s a task description based on the email content "ECMFA 2026 submission assignment," designed to be actionable and clearly outlined: Task Title: Complete ECMFA 2026 Submission – [Specify Document Name/Format - e.g., Final Report, Presentation, etc.] Description: This task requires you to finalize and submit the ECMFA 2026 submission, specifically [State the specific document/deliverable - e.g., the final report, the presentation slides, the data analysis]. This is a crucial step in ensuring the successful completion of the ECMFA 2026 project. Actionable Steps: 1. Review Submission Guidelines: Thoroughly review the official ECMFA 2026 submission guidelines document located at [Insert Link to Document Here – VERY IMPORTANT]. Pay close attention to formatting requirements, data sources, and required elements. 2. Gather Required Data: Collect all necessary data and information as outlined in the guidelines. This may involve [List specific data sources - e.g., accessing the database, reviewing reports, performing specific calculations]. 3. Format and Organize Content: Organize your submission content in a clear, logical, and consistent format. Ensure all sections are properly labeled and aligned. 4. Proofread and Edit: Carefully proofread your entire submission for any grammatical errors, typos, or inconsistencies. Check formatting for consistency. 5. Submit the Submission: Submit the completed document through [Specify Submission Method - e.g., Outlook, SharePoint, designated portal]. 6. [Optional - If applicable] - Submit Feedback: If you have any questions or require clarification on any part of the submission, please send a brief email to [Your Email Address] within 24 hours of submitting. Deadline: [Insert Deadline – Be realistic!] Priority: [High/Medium/Low - Assign a priority level.] Assigned To: [Your Name/Team Name] Notes: If you encounter any roadblocks or require assistance, please don’t hesitate to reach out to [Contact Person/Team for Support - e.g., your supervisor, the ECMFA team]. --- To help me refine this further and make it even more tailored, could you tell me: * What kind of document is this submission for? (Report, presentation, data analysis, etc.?) * Are there any specific guidelines or requirements you want to highlight? (e.g., specific data sources, format requirements, length restrictions?) todoist-labels:: #outlook365 todoist-status:: ◼️