[logseq-plugin-git:commit] 2025-12-27T19:07:25.270Z
This commit is contained in:
@@ -0,0 +1,243 @@
|
||||
filters:: {"call per posizioni mosaico" true}
|
||||
status:: [[ACCEPTED]]
|
||||
deadline-submission:: [[19-03-2024]]
|
||||
date-start:: [[01-01-2025]]
|
||||
date-end:: [[31-12-2027]]
|
||||
todoist:: [Todoist](https://todoist.com/showTask?id=7288828203)
|
||||
project-type:: [[EU-PROJECT]]
|
||||
external-links:: [MOSAICO - Google Drive](https://drive.google.com/drive/folders/1smtmPfO8AAJTJknzfkMB0_tXIKbDDcqm) [Funding & tenders (europa.eu)](https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/horizon-cl4-2024-digital-emerging-01-22?tenders=false&callIdentifier=HORIZON-CL4-2024-DIGITAL-EMERGING-01) [AI Communities for SE - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/6555c7e7fdd67dc9161ee0d0) [AI Debate for SE - Google Docs](https://docs.google.com/document/d/1tjrjMOls_RiooIv8XtLTwYnMTRK0pTmVUtQrHKeZD2M/edit) [UDA Contribution](https://vps.diruscio.org/nc/s/pxFapNXLNGx2Nfn)
|
||||
full-title::
|
||||
priority:: [[P1]]
|
||||
progress:: {{renderer :todomaster}}
|
||||
|
||||
- ## ACK Text
|
||||
- This work has been funded by the European Union under the Grant Agreement No 101189664 (MOSAICO project). Views and opinions expressed are those of the author(s) only and do not necessarily reflect those of the European Union or the European Health and Digital Executive Agency (HADEA). Neither the European Union nor the granting authority can be held responsible for them.
|
||||
- ## Project Officer
|
||||
- [(21) Gregor Novak | LinkedIn](https://www.linkedin.com/in/novakgregor/?originalSubdomain=be)
|
||||
- [[PROJECTS/MOSAICO/WP2]]
|
||||
- ## Calendar of Consortium Meetings
|
||||
- {:height 302, :width 557}
|
||||
- ## Deliverable QA process
|
||||
- {:height 491, :width 862}
|
||||
- ## Project preparation
|
||||
collapsed:: true
|
||||
- Timeline
|
||||
- From today --> March 7th: last pieces of the materials from partners
|
||||
- From 8th to 14th: Massimo and I work on the consolidation of the proposal
|
||||
- 14th to 17th: review the final version by partners
|
||||
- 18th-19th : submission.
|
||||
- We need then:
|
||||
- DONE I need all the budget templates by wednesday 12.00.
|
||||
- DONE @all: support us with the Expected outcomes, expected impacts and barriers by sending back to me the "section 2.1 template" by next thursday.
|
||||
- #.tabular
|
||||
- ### Meetings
|
||||
- {{query (and (or (property :tags [[PROJECTS/SE-H2020-March-Call]]) (property :tags [[PROJECTS/MOSAICO]])) (block-property :type [[meeting]]))}}
|
||||
query-table:: true
|
||||
query-properties:: [:date :duration]
|
||||
query-sort-by:: date
|
||||
query-sort-desc:: true
|
||||
- ### TASKS
|
||||
- DONE For budget template: please provide me with a first draft for [[01-03-2024]]
|
||||
- DONE Leggere [[2402.02172] CodeAgent: Collaborative Agents for Software Engineering (arxiv.org)](https://arxiv.org/abs/2402.02172)
|
||||
- DONE Leggere [[2307.07924] Communicative Agents for Software Development (arxiv.org)](https://arxiv.org/abs/2307.07924)
|
||||
- DONE Leggere MetaGPT and alike
|
||||
- DONE Leggere [Leonardo Tonetto on LinkedIn: Ideal-ist Spring Proposal Check Event](https://www.linkedin.com/posts/leonardotonetto_ideal-ist-spring-proposal-check-event-activity-7153302779006984193-BfdO/?utm_source=share&utm_medium=member_ios)
|
||||
- DONE For impact template: I need the one for (IMT), UDA, INTRA, IMM, NBG, ECL, F6S, US Collins. + UY (the data section in template impact)
|
||||
- DONE Write WP2 deliverables
|
||||
- DONE Email Julienne
|
||||
- DONE WP leaders 1--> 5: please provide one to two risks + the associated mitigation measures in the "Table 11: Critical risks for implementation and contingency plans (L: Likelihood; S: Severity)"
|
||||
- DONE WP leader 1--> 4 : finalise/ revisit State of the Art section and methodology section.
|
||||
- DONE all: note your possible contribution to the subtables of the different tasks in WP1 to WP 5 included. I added lines for US Collins, Unparallel and eventually Codium AI if they join (and will be the last partner)
|
||||
- **LISTA DI TUTTI I TASK**
|
||||
query-sort-by:: page
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
- {{query (and (or [[PROJECTS/SE-H2020-March-Call]] [[PROJECTS/MOSAICO]]) (task TODO DOING) (not [[GOALS-TODOIST]]))}}
|
||||
query-table:: true
|
||||
query-sort-by:: page
|
||||
query-sort-desc:: false
|
||||
- ### Writing notes and comments
|
||||
collapsed:: true
|
||||
- DONE Deepmark seems to be one of our baselines. Thus it is necessary to have a deep look at it
|
||||
- DONE Leggere [[@Battle of the Wordsmiths: Comparing ChatGPT, GPT-4, Claude, and Bard]]
|
||||
- DONE Leggere [[@Large Language Models for Software Engineering: Survey and Open Problems]]
|
||||
- DONE Leggere [[@An Empirical Study of Pre-Trained Model Reuse in the Hugging Face Deep Learning Model Registry]]
|
||||
- DONE We need to write contents related to the research objective **management of agents communities for SE tasks**
|
||||
- Several works have shown and proposed the adoption of LLMs for different SE tasks
|
||||
- DONE Antonio Garcia-Dominguez (York) 01/02/2024 12:46 • May be worth to check the way search is done in HuggingFace: https://huggingface.co/models
|
||||
- DONE Omogeneizzare l'uso di
|
||||
- solution Agent, mediating agents, etc.
|
||||
- AI assistant vs AI agent
|
||||
-
|
||||
- ### Notes for the sota
|
||||
collapsed:: true
|
||||
- In the realm of software engineering, developers encounter a significant challenge due to the diversity of AI agents available. This diversity spans language models, capabilities, and use cases, requiring developers to navigate through a multitude of options to find the most suitable AI agent for their specific software engineering tasks. The lack of standardized metadata further compounds this challenge, as a comprehensive understanding of the capabilities and limitations of AI agents is crucial for informed decision-making. Without standardized metadata, developers may struggle to assess the appropriateness of an AI agent for their needs. Additionally, users face the issue of inadequate guidance in selecting the most appropriate AI agents for specific software engineering challenges. This lack of guidance can hinder the adoption of optimal solutions. Moreover, the dynamic nature of the AI landscape poses an ongoing challenge, as staying updated on the latest advancements in Large Language Models (LLMs), understanding their evolving capabilities, and assessing their relevance to software tasks require continuous effort. These challenges underscore the importance of establishing standardized information, guidance mechanisms, and up-to-date resources to facilitate effective utilization of AI agents in software engineering endeavors.
|
||||
- ### WP2 notes
|
||||
- **WP2 tasks description**
|
||||
- *Task 2.1 - Definition of a taxonomy of AI agents for SE*: This task will define a comprehensive taxonomy to categorize AI agents based on their functionalities, capabilities, and intended use cases. Thus, the taxonomy will permit to manage and organize AI agents by categorizing them into distinct groups and identifying areas of potential overlap.
|
||||
- *Task 2.2 – Definition of Key Performance Indicators of AI agents for SE*: This task will define KPIs tailored to the goals of the AI agent community management. These KPIs will specifically address the management of potential overlapping functionalities and the evaluation of AI agents against benchmarks. To this end, the task will exploit measurable metrics that provide insights of each managed AI agent, including their performance, and efficiency. The defined KPIs will support a systematic evaluation and monitoring of AI agents within the repository.
|
||||
- *Task 2.3 – Development of a benchmarking framework for AI agents for SE*: This task will develop a benchmarking framework to evaluate managed AI agents. Thus, this task will define performance benchmarks, quality standards, and criteria for assessing the effectiveness of AI agents. This task involves creating a framework that ensures consistency in evaluating different agents, facilitating comparisons, and supporting informed decisions.
|
||||
-
|
||||
- ### Concept slides
|
||||
collapsed:: true
|
||||
- {:height 365, :width 601}
|
||||
- {:height 334, :width 604}
|
||||
- {:height 397, :width 606}
|
||||
- It's a call on fundamental software engineering
|
||||
- We need to be "disruptive"
|
||||
- {:height 418, :width 606}
|
||||
- Similarly to what happend in the past, moving from one single-cloud provider to multi-cloud providers.
|
||||
- {:height 389, :width 609}
|
||||
- The call is 4-6M Euro.
|
||||
- We decided to have weekly meetings on **Thursdays at 12:00**.
|
||||
-
|
||||
- ### Reading notes
|
||||
collapsed:: true
|
||||
- #[[Clip]] [[31-01-2024]] 21:01 [ML Model Registry: The Ultimate Guide](https://neptune.ai/blog/ml-model-registry)
|
||||
Your new and improved cross-functional team is asking you about:
|
||||
|
||||
* Where can we find the best version of this model so we can audit, test, deploy, or reuse it?
|
||||
* How was this model trained?
|
||||
* How can we track the docs for each model to make sure they are compliant and people can know the necessary details about it including the metadata?
|
||||
* How can we review models before they are put to use or even after they have been deployed?
|
||||
* How can we integrate with tools and services that make shipping new projects easier?
|
||||
- This is interesting [[Omnivore/22-11-2023/IngestAI-deepmark- Deepmark AI enables a unique testing environment for langu...]]. It is very much related to our idea of developing a framework to compare different LLMs.
|
||||
background-color:: green
|
||||
- *Deepmark AI empowers Generative AI builders to make informed decisions when choosing among Large Language Models (LLM), enabling seamless assessment of various LLM on your own data, so your AI applications have predictable and reliable performance.* [IngestAI/deepmark](https://github.com/IngestAI/deepmark)
|
||||
collapsed:: true
|
||||
- There’s no available tools (open-source or proprietary) that enable developers to seamlessly make task-specific (intrinsic) assessments on their unique data. #challenges
|
||||
- LangChain and LangSmitm seem to be candidate solutios for this even though they are still in closed beta. #evaluation
|
||||
- Deepmark is proposed as a *benchmarking tool that enables assessment of large language models (LLM) on various extrinsic (task-specific) metrics on your own data*.
|
||||
- it has pre-built integration with leading Generative AI APIs such as GPT-4, Anthropic, GPT-3.5 Turbo, Cohere, AI21, and others.
|
||||
- Two kinds of metrics are employed, i.e., intrinsic and extrinsic
|
||||
-
|
||||
- intrinsic: entropy, perplexity, coherence,
|
||||
- extrinsic: accuracy, latency, cost, etc.
|
||||
- ==These assessment metrics are not exhaustive, and specific applications may have additional or alternative metrics depending on the context and requirements, but some of the task-specific metrics like latency, accuracy, or cost can be considered as the most commonly used.==
|
||||
- We can work on this, by doing something similar we did with CROSSMINER, with the language for specifying quality models. We can think of defining custom quality models for LLMs with a corresponding quality assessment infrastructure. The output of the quality models can be used to annotaed LLMs in the repository. Such annotations are considered when querying the repository to find LLMs that best fit user requirements. #Ideas
|
||||
- **Deepmark AI** offers capabilities for comprehensive assessment of various important GenAI performance metrics, such as:
|
||||
background-color:: green
|
||||
- Question answering accuracy
|
||||
- Text classification accuracy
|
||||
- PII recognition accuracy
|
||||
- Named entity recognition (NER) accuracy
|
||||
- Summarization quality (Relevance)
|
||||
- Sentiment analysis accuracy
|
||||
- Cost analysis
|
||||
- Failure rate
|
||||
- Accuracy
|
||||
- Latency
|
||||
- We could start with such metrics and enable the addition of new ones and their organizations during the definition of custom quality models. #Ideas
|
||||
background-color:: green
|
||||
-
|
||||
- {{query (and "omnivore-note" [[PROJECTS/SE-H2020-March-Call]])}}
|
||||
query-table:: true
|
||||
query-properties:: [:omnivore-note :page]
|
||||
query-sort-by:: page
|
||||
query-sort-desc:: true
|
||||
- {{embed ((651a8a88-9694-4887-9d92-fa2364e9b940))}}
|
||||
- ### Call
|
||||
id:: 652fc20e-c15e-4157-a830-0109db28748a
|
||||
- _1697629060680_0.pdf)
|
||||
- ((652fc39c-87d2-417f-b7a3-29b29f0780a7))
|
||||
-
|
||||
- 
|
||||
- ((652fc30b-7172-4e89-81b8-c4a971ae8d3f))
|
||||
- ((652fc320-a4da-4aba-8d44-c4ec121ae7b2))
|
||||
- {:height 181, :width 714}
|
||||
- ### Example Scenario
|
||||
collapsed:: true
|
||||
- **Title:** From a High-Level Description to a Deployed IoT Smart Home System
|
||||
- **Objective:** To assist developers in creating, analyzing, and maintaining IoT-based smart home applications through an intelligent agent-based environment. In this scenario, the Smart Development Environment provides a comprehensive suite of tools for developers to efficiently create, analyze, and maintain IoT-based smart home applications. The agent-based approach ensures that each aspect of the software engineering process is handled by specialized agents, with the Meta-Agent (MA) coordinating their activities and serving as the primary interface for the developer.
|
||||
-
|
||||
- #### **Artificial Agents Involved (All Powered by LLMs)**
|
||||
- **Specification Agent (SA)**:
|
||||
- **Capabilities**: Derives requirements from high-level descriptions and produces conceptual and architectural models.
|
||||
- **Technologies**: Uses **spaCy** integrated with an **LLM** for enhanced natural language understanding.
|
||||
- **KPIs**: Accuracy of derived requirements, clarity of produced models.
|
||||
- **AgileDevelopment Agent (ADA)**:
|
||||
- **Capabilities**: Supports agile methodologies, sprint planning, and backlog management tailored for IoT.
|
||||
- **Technologies**: Integrates with **JIRA** and uses an **LLM** for task description interpretation and sprint optimization.
|
||||
- **KPIs**: Efficiency in task allocation, sprint completion rate.
|
||||
- **CodeAnalysis Agent (CAA)**:
|
||||
- **Capabilities**: Performs advanced code analysis to ensure best practices for IoT development.
|
||||
- **Technologies**: Uses **SonarQube** with **LLM** insights for deeper code understanding and analysis.
|
||||
- **KPIs**: Depth of code analysis, identification of potential issues.
|
||||
- **FaultPrediction Agent (FPA)**:
|
||||
background-color:: yellow
|
||||
- **Capabilities**: Uses AI to predict potential faults in the system and locate existing ones.
|
||||
- **Technologies**: Leverages **TensorFlow** integrated with **LLM** insights for enriched fault prediction.
|
||||
- **KPIs**: Accuracy of fault prediction, speed of fault location.
|
||||
- **SelfRepair Agent (SRA)**:
|
||||
background-color:: yellow
|
||||
- **Capabilities**: Utilizes AI and data technologies to suggest and implement self-repair mechanisms.
|
||||
- **Technologies**: Uses **AutoML** combined with **LLM** for generating repair algorithms based on natural language descriptions.
|
||||
- **KPIs**: Success rate of repairs, system uptime.
|
||||
- **TestingSupport Agent (TSA)**:
|
||||
- **Capabilities**: Facilitates automated unit and integration testing based on the contracts provided by CPA.
|
||||
- **Technologies**: Uses **JUnit** and **Jenkins** with **LLM** insights for generating test cases based on natural language descriptions.
|
||||
- **KPIs**: Test coverage, detection of contract violations.
|
||||
- **AgentRepository (AR)**:
|
||||
background-color:: purple
|
||||
- **Capabilities**: Stores, categorizes, and provides access to various agents based on requirements.
|
||||
- **Technologies**: Built on **Elasticsearch** with **LLM** for enhanced agent description and retrieval.
|
||||
- **KPIs**: Speed of agent retrieval, accuracy in matching agent capabilities to requirements.
|
||||
- **InputFormatter (IF)**:
|
||||
background-color:: yellow
|
||||
- **Capabilities**: Transforms input data into the expected format for each agent.
|
||||
- **Technologies**: Uses **Apache NiFi** integrated with **LLM** for understanding and transforming complex data formats.
|
||||
- **KPIs**: Accuracy of format transformation, speed of processing.
|
||||
- **Meta-Agent (MA)**:
|
||||
- **Capabilities**: Coordinates with all other agents, manages workflows, and serves as the primary interface for the developer.
|
||||
- **Technologies**: Built on a **Microservices** architecture using **Docker** and **Kubernetes**. Uses **LLM** for coordinating tasks and understanding developer intents.
|
||||
- **KPIs**: Efficiency in task delegation, overall system performance.
|
||||
- #### Process
|
||||
- **Initiating a New IoT Smart Home Project**
|
||||
- A developer provides a high-level description of a smart home feature, e.g., "A system that adjusts room temperature based on occupancy and time of day."
|
||||
- MA queries AR to retrieve SA.
|
||||
- SA derives specific requirements and produces a conceptual model.
|
||||
- MA presents the derived requirements and model to the developer for validation.
|
||||
- **Agile Development Process**
|
||||
- MA retrieves ADA from AR to initiate sprint planning.
|
||||
- ADA breaks down the requirements into user stories and tasks tailored for IoT development.
|
||||
- Throughout the sprint, ADA monitors progress and adjusts the backlog as necessary.
|
||||
- **Code Development and Analysis**:
|
||||
- As the developer writes code, MA retrieves CAA from AR for real-time code analysis.
|
||||
- CAA ensures that the code adheres to best practices for IoT and provides instant feedback.
|
||||
- **Fault Prediction and Location**:
|
||||
- MA retrieves FPA to analyze the system for potential faults.
|
||||
- FPA predicts possible faults and pinpoints any existing ones, alerting the developer.
|
||||
- **Self-Repair Mechanisms**:
|
||||
- If a fault is detected, MA queries AR for SRA.
|
||||
- SRA suggests repair mechanisms and, with developer approval, implements them.
|
||||
- #### Description
|
||||
- A developer aims to create a new IoT-based smart home application but lacks the intricate knowledge of IoT system design and wants our agents to assist in the process.
|
||||
- The developer starts by providing a high-level description, such as "A system that adjusts room temperature based on the number of people in the room and the time of day."
|
||||
-
|
||||
- A first set of **Specification Agents (SA)** translate this description into a technical model, capturing key concepts like "Occupancy Sensor," "Clock Module," and "Temperature Controller." A meta-agent, designed to oversee and harmonize the outputs of individual agents, meticulously reviews the models generated by each agent. It identifies and addresses any discrepancies or ambiguities that arise. For instance, while one agent might interpret "adjusts room temperature" as a simple increase or decrease in degrees, another might perceive it as a dynamic calibration based on external factors like outside temperature or humidity. To ensure the most accurate interpretation and alignment with the developer's intent, the meta-agent, when faced with such conflicting interpretations, initiates a dialogue with the developer, seeking clarification or confirmation to refine the model accurately.
|
||||
-
|
||||
- A second set of design-generation agents, including the **AgileDevelopment Agent (ADA)** and the **CodeAnalysis Agent (CAA)**, spring into action once the initial requirements are set. The ADA, with its integration with JIRA and LLM-enhanced understanding, starts by breaking down the technical model into potential system architectures, considering factors like scalability, modularity, and IoT-specific constraints. It proposes various architectural blueprints, each optimized for different aspects of the smart home environment.
|
||||
- Simultaneously, the CodeAnalysis Agent (CAA) focuses on potential code structures and algorithms that would fit the chosen architecture. Drawing from a vast database of best practices and leveraging SonarQube's capabilities, the CAA suggests efficient and secure code snippets, ensuring the software's robustness from the get-go. This phase is highly interactive, with each agent presenting a series of alternative designs, architectures, and code structures to the developer in a cyclical manner. The developer reviews these options, selecting elements they find most fitting, and provides feedback on areas of improvement or specific preferences. This feedback loop is crucial: all agents have access to the developer's choices and comments, enabling them to refine their subsequent proposals based on this real-time input. They learn from each other's suggestions, often blending elements from multiple proposals to create a more optimized solution.
|
||||
- This phase exploits the collaborative nature of the agents. Instead of competing or working in isolation, they operate more like a cohesive team, each contributing its expertise and building upon the others' strengths. There's no singular meta-agent directing this symphony; instead, the agents synchronize through shared data and developer feedback, ensuring the end result is a harmonized blend of their collective intelligence.
|
||||
-
|
||||
- The code development activity is done in synergy with the testing one by making use of the TestingSupport Agent (TSA). The TSA, leveraging its integration with JUnit and Jenkins, ensures that the system undergoes rigorous testing. It checks for functional correctness, performance benchmarks, and integration stability, all tailored for the IoT environment.
|
||||
-
|
||||
- With the green light from TSA, the last step of the process is the deployment phase,which employs a CI/CD infrastructure, automating the process of deploying the system configurations, code, and any necessary firmware updates to the target IoT devices. In this phase, the developer is presented with a selection of specialized agents, each with its unique strengths, compatibility metrics, and cost structures. After evaluating factors like the agent's track record in deploying similar systems, compatibility with the target IoT devices, and the overall cost-effectiveness, the developer selects the most suitable agent for deployment.
|
||||
-
|
||||
- ### Readings
|
||||
- {{query (and (property :labels [[PROJECTS/SE-H2020-March-Call]]) (not (property :is-archived "10")))}}
|
||||
query-sort-by:: date-saved
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
query-properties:: [:page :site :date-saved]
|
||||
- 
|
||||
- [Home / X (twitter.com)](https://twitter.com/aserebrenik/status/1735231168151236809/photo/1)
|
||||
-
|
||||
- ## Readings
|
||||
- [Models | Model Openness Tool](https://mot.isitopen.ai/)
|
||||
- Interesting to see to complete the characteristics definition of the MOSAICO repository
|
||||
- In particular, at the following link [Evaluate model | Model Openness Tool](https://mot.isitopen.ai/model/evaluate) there is a form to evaluate a model being created/uploaded. The fields of such a form are very much related to the MOSAICO repository.
|
||||
- ## [[Resources]]
|
||||
- [MOSAICO Project planning.xlsx](https://imtatlantiquefr.sharepoint.com/:x:/r/sites/MOSAICO/_layouts/15/Doc.aspx?sourcedoc=%7BB19128F1-2547-452A-9A77-43255E8933AA%7D&file=MOSAICO%20Project%20planning.xlsx&action=default&mobileredirect=true) - Deliverable Reviewers
|
||||
- Innovation Management Log - https://imtatlantiquefr.sharepoint.com/:x:/r/sites/MOSAICO/_layouts/15/Doc.aspx?sourcedoc=%7BE4A9B8DF-6C18-42E8-81F1-9961EAC76933%7D&file=(MOSAICO)%20Innovation%20Management%20Log_v1.xlsx&action=default&mobileredirect=true
|
||||
- [Data management log.xlsx](https://imtatlantiquefr.sharepoint.com/:x:/r/sites/MOSAICO/_layouts/15/Doc.aspx?sourcedoc=%7B9B8967C9-090E-4E19-AB28-4F664431BE86%7D&file=Data%20management%20log.xlsx&action=default&mobileredirect=true)
|
||||
@@ -0,0 +1 @@
|
||||
- {{renderer :todoistsync_qvdaezva}}
|
||||
@@ -0,0 +1,10 @@
|
||||
- [la Repubblica - News in tempo reale - Le notizie e i video di politica, cronaca, economia, sport](http://www.repubblica.it)
|
||||
site:: www.repubblica.it
|
||||
author::
|
||||
date-saved:: [[23-12-2025]]
|
||||
published-at::
|
||||
id-wallabag:: 1
|
||||
publishedby::
|
||||
- ### Highlights
|
||||
- i Repu
|
||||
Note: test
|
||||
@@ -1,62 +0,0 @@
|
||||
- [[Software ecosystem book chapter]]
|
||||
- Lavorare su sezione presentazione processo
|
||||
-  #ReadingNotes
|
||||
- Machine Learning is a method to find a relationship between different sets of values by utilizing ==statistical models== and ==algorithms==.
|
||||
- ((631f19cb-c451-4e9b-bb59-1d22d7bac8b2))
|
||||
- ((631f1a34-3f81-4a1b-9fcb-29b8d39c020e))
|
||||
- ((631f1aa1-6e38-4cb4-a283-150b6fac9e58))
|
||||
- [ML courses, videos, and websites](https://todoist.com/showTask?id=6165927353)
|
||||
id:: 631f2025-9cad-413a-8fcf-c1c78bd68635
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
people:: #people/alfonso
|
||||
areas:: [[Software ecosystem book chapter]]
|
||||
date:: [[12-09-2022]]
|
||||
duration-minutes:: 73
|
||||
- **MDE for [[Digital Twin]]** ([Schloss Dagstuhl : Seminar Homepage](https://www.dagstuhl.de/en/program/calendar/semhp/?semnr=22362)) [[Ideas]]
|
||||
- Lavoro di Andreas che ha fatto qualche survey
|
||||
- ci sono diverse componenti tra cui quella prescrittiva
|
||||
- Anomaly detection
|
||||
- Predictive maintenance
|
||||
- Dataset disponibili?
|
||||
- Petrobras ha messo disponibile dei #dataset
|
||||
- [UCI Machine Learning Repository: 3W dataset Data Set](https://archive.ics.uci.edu/ml/datasets/3W+dataset)
|
||||
- [ricardovvargas/3w_dataset: The first realistic and public dataset with rare undesirable real events in oil wells. (github.com)](https://github.com/ricardovvargas/3w_dataset)
|
||||
- [[@A realistic and public dataset with rare undesirable real events in oil wells]]
|
||||
- **Da vedere**
|
||||
- [Machine learning and transport simulations for groundwater anomaly detection - ScienceDirect (cineca.it)](https://www-sciencedirect-com.univaq.clas.cineca.it/science/article/pii/S0377042720302739?via%3Dihub)
|
||||
- [Imminence Monitoring of Critical Events: A Representation Learning Approach | Proceedings of the 2021 International Conference on Management of Data (cineca.it)](https://dl-acm-org.univaq.clas.cineca.it/doi/10.1145/3448016.3452804)
|
||||
- Disponibilità di simulatori
|
||||
- Ventilatore meccanico
|
||||
- Domini consolidati
|
||||
- Manufatturiero dove hai una controparte fisica / meccanica
|
||||
- Sistemi umani (es. medicina di precisione, agricoltura di precisione)
|
||||
- **Aggiornamento book chapter**
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Alfonso. Ha detto che se lo vedrà per Venerdi 16 Settembre
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #people/vittorio #people/traini #people/riccardo #people/imran
|
||||
areas::
|
||||
date:: [[12-09-2022]]
|
||||
duration-minutes:: 60
|
||||
- Benchmarking process
|
||||
- 4 different steps
|
||||
- *Identify code segment*
|
||||
- Recommender systems for recommending parts of software systems that should be benchmarked
|
||||
- Mixing static and dynamic analysis
|
||||
- Related work
|
||||
- AutoJMH (2016)
|
||||
- J23jmh (2022)
|
||||
- *Wrap code into payload*
|
||||
- remove code smells (of the code we want to benchmark)
|
||||
- Smells that affect the performance
|
||||
- We need to be cautious on this because we might introduce some bias or in general, affect the behaviour of the original system
|
||||
- Dead code identification
|
||||
- [...]
|
||||
- *Execution large # of times*
|
||||
- Reduce time to execute tests
|
||||
- **Ideas**
|
||||
- Identify features (static or dynamic) of existing projects that can underpin the recommender system
|
||||
- The goal is to recommend code locations that need to be benchmarked via [[JMH]]
|
||||
- [projects.csv](../assets/projects_1663000066246_0.csv)
|
||||
@@ -1,62 +0,0 @@
|
||||
- [[Software ecosystem book chapter]]
|
||||
- Lavorare su sezione presentazione processo
|
||||
-  #ReadingNotes
|
||||
- Machine Learning is a method to find a relationship between different sets of values by utilizing ==statistical models== and ==algorithms==.
|
||||
- ((631f19cb-c451-4e9b-bb59-1d22d7bac8b2))
|
||||
- ((631f1a34-3f81-4a1b-9fcb-29b8d39c020e))
|
||||
- ((631f1aa1-6e38-4cb4-a283-150b6fac9e58))
|
||||
- [ML courses, videos, and websites](https://todoist.com/showTask?id=6165927353)
|
||||
id:: 631f2025-9cad-413a-8fcf-c1c78bd68635
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
people:: #people/alfonso
|
||||
areas:: [[Software ecosystem book chapter]]
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 73
|
||||
- **MDE for [[Digital Twin]]** ([Schloss Dagstuhl : Seminar Homepage](https://www.dagstuhl.de/en/program/calendar/semhp/?semnr=22362)) [[Ideas]]
|
||||
- Lavoro di Andreas che ha fatto qualche survey
|
||||
- ci sono diverse componenti tra cui quella prescrittiva
|
||||
- Anomaly detection
|
||||
- Predictive maintenance
|
||||
- Dataset disponibili?
|
||||
- Petrobras ha messo disponibile dei #dataset
|
||||
- [UCI Machine Learning Repository: 3W dataset Data Set](https://archive.ics.uci.edu/ml/datasets/3W+dataset)
|
||||
- [ricardovvargas/3w_dataset: The first realistic and public dataset with rare undesirable real events in oil wells. (github.com)](https://github.com/ricardovvargas/3w_dataset)
|
||||
- [[@A realistic and public dataset with rare undesirable real events in oil wells]]
|
||||
- **Da vedere**
|
||||
- [Machine learning and transport simulations for groundwater anomaly detection - ScienceDirect (cineca.it)](https://www-sciencedirect-com.univaq.clas.cineca.it/science/article/pii/S0377042720302739?via%3Dihub)
|
||||
- [Imminence Monitoring of Critical Events: A Representation Learning Approach | Proceedings of the 2021 International Conference on Management of Data (cineca.it)](https://dl-acm-org.univaq.clas.cineca.it/doi/10.1145/3448016.3452804)
|
||||
- Disponibilità di simulatori
|
||||
- Ventilatore meccanico
|
||||
- Domini consolidati
|
||||
- Manufatturiero dove hai una controparte fisica / meccanica
|
||||
- Sistemi umani (es. medicina di precisione, agricoltura di precisione)
|
||||
- **Aggiornamento book chapter**
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Alfonso. Ha detto che se lo vedrà per Venerdi 16 Settembre
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #people/vittorio #people/traini #people/riccardo #people/imran
|
||||
areas::
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 60
|
||||
- Benchmarking process
|
||||
- 4 different steps
|
||||
- *Identify code segment*
|
||||
- Recommender systems for recommending parts of software systems that should be benchmarked
|
||||
- Mixing static and dynamic analysis
|
||||
- Related work
|
||||
- AutoJMH (2016)
|
||||
- J23jmh (2022)
|
||||
- *Wrap code into payload*
|
||||
- remove code smells (of the code we want to benchmark)
|
||||
- Smells that affect the performance
|
||||
- We need to be cautious on this because we might introduce some bias or in general, affect the behaviour of the original system
|
||||
- Dead code identification
|
||||
- [...]
|
||||
- *Execution large # of times*
|
||||
- Reduce time to execute tests
|
||||
- **Ideas**
|
||||
- Identify features (static or dynamic) of existing projects that can underpin the recommender system
|
||||
- The goal is to recommend code locations that need to be benchmarked via [[JMH]]
|
||||
- [projects.csv](../assets/projects_1663000066246_0.csv)
|
||||
@@ -1,62 +0,0 @@
|
||||
- [[Software ecosystem book chapter]]
|
||||
- Lavorare su sezione presentazione processo
|
||||
-  #ReadingNotes
|
||||
- Machine Learning is a method to find a relationship between different sets of values by utilizing ==statistical models== and ==algorithms==.
|
||||
- ((631f19cb-c451-4e9b-bb59-1d22d7bac8b2))
|
||||
- ((631f1a34-3f81-4a1b-9fcb-29b8d39c020e))
|
||||
- ((631f1aa1-6e38-4cb4-a283-150b6fac9e58))
|
||||
- [ML courses, videos, and websites](https://todoist.com/showTask?id=6165927353)
|
||||
id:: 631f2025-9cad-413a-8fcf-c1c78bd68635
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
people:: #people/alfonso
|
||||
areas:: [[Software ecosystem book chapter]]
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 73
|
||||
- **MDE for [[Digital Twin]]** ([Schloss Dagstuhl : Seminar Homepage](https://www.dagstuhl.de/en/program/calendar/semhp/?semnr=22362)) [[Ideas]]
|
||||
- Lavoro di Andreas che ha fatto qualche survey
|
||||
- ci sono diverse componenti tra cui quella prescrittiva
|
||||
- Anomaly detection
|
||||
- Predictive maintenance
|
||||
- Dataset disponibili?
|
||||
- Petrobras ha messo disponibile dei #dataset
|
||||
- [UCI Machine Learning Repository: 3W dataset Data Set](https://archive.ics.uci.edu/ml/datasets/3W+dataset)
|
||||
- [ricardovvargas/3w_dataset: The first realistic and public dataset with rare undesirable real events in oil wells. (github.com)](https://github.com/ricardovvargas/3w_dataset)
|
||||
- [[@A realistic and public dataset with rare undesirable real events in oil wells]]
|
||||
- **Da vedere**
|
||||
- [Machine learning and transport simulations for groundwater anomaly detection - ScienceDirect (cineca.it)](https://www-sciencedirect-com.univaq.clas.cineca.it/science/article/pii/S0377042720302739?via%3Dihub)
|
||||
- [Imminence Monitoring of Critical Events: A Representation Learning Approach | Proceedings of the 2021 International Conference on Management of Data (cineca.it)](https://dl-acm-org.univaq.clas.cineca.it/doi/10.1145/3448016.3452804)
|
||||
- Disponibilità di simulatori
|
||||
- Ventilatore meccanico
|
||||
- Domini consolidati
|
||||
- Manufatturiero dove hai una controparte fisica / meccanica
|
||||
- Sistemi umani (es. medicina di precisione, agricoltura di precisione)
|
||||
- **Aggiornamento book chapter**
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Alfonso. Ha detto che se lo vedrà per Venerdi 16 Settembre
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #people/vittorio #people/traini #people/riccardo #people/imran
|
||||
areas::
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 60
|
||||
- Benchmarking process
|
||||
- 4 different steps
|
||||
- *Identify code segment*
|
||||
- Recommender systems for recommending parts of software systems that should be benchmarked
|
||||
- Mixing static and dynamic analysis
|
||||
- Related work
|
||||
- AutoJMH (2016)
|
||||
- J23jmh (2022)
|
||||
- *Wrap code into payload*
|
||||
- remove code smells (of the code we want to benchmark)
|
||||
- Smells that affect the performance
|
||||
- We need to be cautious on this because we might introduce some bias or in general, affect the behaviour of the original system
|
||||
- Dead code identification
|
||||
- [...]
|
||||
- *Execution large # of times*
|
||||
- Reduce time to execute tests
|
||||
- **Ideas**
|
||||
- Identify features (static or dynamic) of existing projects that can underpin the recommender system
|
||||
- The goal is to recommend code locations that need to be benchmarked via [[JMH]]
|
||||
- [projects.csv](../assets/projects_1663000066246_0.csv)
|
||||
@@ -1,62 +0,0 @@
|
||||
- [[Software ecosystem book chapter]]
|
||||
- Lavorare su sezione presentazione processo
|
||||
-  #ReadingNotes
|
||||
- Machine Learning is a method to find a relationship between different sets of values by utilizing ==statistical models== and ==algorithms==.
|
||||
- ((631f19cb-c451-4e9b-bb59-1d22d7bac8b2))
|
||||
- ((631f1a34-3f81-4a1b-9fcb-29b8d39c020e))
|
||||
- ((631f1aa1-6e38-4cb4-a283-150b6fac9e58))
|
||||
- [ML courses, videos, and websites](https://todoist.com/showTask?id=6165927353)
|
||||
id:: 631f2025-9cad-413a-8fcf-c1c78bd68635
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
people:: #people/alfonso
|
||||
tags:: [[Software ecosystem book chapter]]
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 73
|
||||
- **MDE for [[Digital Twin]]** ([Schloss Dagstuhl : Seminar Homepage](https://www.dagstuhl.de/en/program/calendar/semhp/?semnr=22362)) [[Ideas]]
|
||||
- Lavoro di Andreas che ha fatto qualche survey
|
||||
- ci sono diverse componenti tra cui quella prescrittiva
|
||||
- Anomaly detection
|
||||
- Predictive maintenance
|
||||
- Dataset disponibili?
|
||||
- Petrobras ha messo disponibile dei #dataset
|
||||
- [UCI Machine Learning Repository: 3W dataset Data Set](https://archive.ics.uci.edu/ml/datasets/3W+dataset)
|
||||
- [ricardovvargas/3w_dataset: The first realistic and public dataset with rare undesirable real events in oil wells. (github.com)](https://github.com/ricardovvargas/3w_dataset)
|
||||
- [[@A realistic and public dataset with rare undesirable real events in oil wells]]
|
||||
- **Da vedere**
|
||||
- [Machine learning and transport simulations for groundwater anomaly detection - ScienceDirect (cineca.it)](https://www-sciencedirect-com.univaq.clas.cineca.it/science/article/pii/S0377042720302739?via%3Dihub)
|
||||
- [Imminence Monitoring of Critical Events: A Representation Learning Approach | Proceedings of the 2021 International Conference on Management of Data (cineca.it)](https://dl-acm-org.univaq.clas.cineca.it/doi/10.1145/3448016.3452804)
|
||||
- Disponibilità di simulatori
|
||||
- Ventilatore meccanico
|
||||
- Domini consolidati
|
||||
- Manufatturiero dove hai una controparte fisica / meccanica
|
||||
- Sistemi umani (es. medicina di precisione, agricoltura di precisione)
|
||||
- **Aggiornamento book chapter**
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Alfonso. Ha detto che se lo vedrà per Venerdi 16 Settembre
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #people/vittorio #people/traini #people/riccardo #people/imran
|
||||
areas::
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 60
|
||||
- Benchmarking process
|
||||
- 4 different steps
|
||||
- *Identify code segment*
|
||||
- Recommender systems for recommending parts of software systems that should be benchmarked
|
||||
- Mixing static and dynamic analysis
|
||||
- Related work
|
||||
- AutoJMH (2016)
|
||||
- J23jmh (2022)
|
||||
- *Wrap code into payload*
|
||||
- remove code smells (of the code we want to benchmark)
|
||||
- Smells that affect the performance
|
||||
- We need to be cautious on this because we might introduce some bias or in general, affect the behaviour of the original system
|
||||
- Dead code identification
|
||||
- [...]
|
||||
- *Execution large # of times*
|
||||
- Reduce time to execute tests
|
||||
- **Ideas**
|
||||
- Identify features (static or dynamic) of existing projects that can underpin the recommender system
|
||||
- The goal is to recommend code locations that need to be benchmarked via [[JMH]]
|
||||
- [projects.csv](../assets/projects_1663000066246_0.csv)
|
||||
@@ -1,62 +0,0 @@
|
||||
- [[Software ecosystem book chapter]]
|
||||
- Lavorare su sezione presentazione processo
|
||||
-  #Highlights
|
||||
- Machine Learning is a method to find a relationship between different sets of values by utilizing ==statistical models== and ==algorithms==.
|
||||
- ((631f19cb-c451-4e9b-bb59-1d22d7bac8b2))
|
||||
- ((631f1a34-3f81-4a1b-9fcb-29b8d39c020e))
|
||||
- ((631f1aa1-6e38-4cb4-a283-150b6fac9e58))
|
||||
- [ML courses, videos, and websites](https://todoist.com/showTask?id=6165927353)
|
||||
id:: 631f2025-9cad-413a-8fcf-c1c78bd68635
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
people:: #people/alfonso
|
||||
tags:: [[Software ecosystem book chapter]]
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 73
|
||||
- **MDE for [[Digital Twin]]** ([Schloss Dagstuhl : Seminar Homepage](https://www.dagstuhl.de/en/program/calendar/semhp/?semnr=22362)) [[Ideas]]
|
||||
- Lavoro di Andreas che ha fatto qualche survey
|
||||
- ci sono diverse componenti tra cui quella prescrittiva
|
||||
- Anomaly detection
|
||||
- Predictive maintenance
|
||||
- Dataset disponibili?
|
||||
- Petrobras ha messo disponibile dei #dataset
|
||||
- [UCI Machine Learning Repository: 3W dataset Data Set](https://archive.ics.uci.edu/ml/datasets/3W+dataset)
|
||||
- [ricardovvargas/3w_dataset: The first realistic and public dataset with rare undesirable real events in oil wells. (github.com)](https://github.com/ricardovvargas/3w_dataset)
|
||||
- [[@A realistic and public dataset with rare undesirable real events in oil wells]]
|
||||
- **Da vedere**
|
||||
- [Machine learning and transport simulations for groundwater anomaly detection - ScienceDirect (cineca.it)](https://www-sciencedirect-com.univaq.clas.cineca.it/science/article/pii/S0377042720302739?via%3Dihub)
|
||||
- [Imminence Monitoring of Critical Events: A Representation Learning Approach | Proceedings of the 2021 International Conference on Management of Data (cineca.it)](https://dl-acm-org.univaq.clas.cineca.it/doi/10.1145/3448016.3452804)
|
||||
- Disponibilità di simulatori
|
||||
- Ventilatore meccanico
|
||||
- Domini consolidati
|
||||
- Manufatturiero dove hai una controparte fisica / meccanica
|
||||
- Sistemi umani (es. medicina di precisione, agricoltura di precisione)
|
||||
- **Aggiornamento book chapter**
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Alfonso. Ha detto che se lo vedrà per Venerdi 16 Settembre
|
||||
- type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #people/vittorio #people/traini #people/riccardo #people/imran
|
||||
areas::
|
||||
date:: [[12-09-2022]]
|
||||
duration-min:: 60
|
||||
- Benchmarking process
|
||||
- 4 different steps
|
||||
- *Identify code segment*
|
||||
- Recommender systems for recommending parts of software systems that should be benchmarked
|
||||
- Mixing static and dynamic analysis
|
||||
- Related work
|
||||
- AutoJMH (2016)
|
||||
- J23jmh (2022)
|
||||
- *Wrap code into payload*
|
||||
- remove code smells (of the code we want to benchmark)
|
||||
- Smells that affect the performance
|
||||
- We need to be cautious on this because we might introduce some bias or in general, affect the behaviour of the original system
|
||||
- Dead code identification
|
||||
- [...]
|
||||
- *Execution large # of times*
|
||||
- Reduce time to execute tests
|
||||
- **Ideas**
|
||||
- Identify features (static or dynamic) of existing projects that can underpin the recommender system
|
||||
- The goal is to recommend code locations that need to be benchmarked via [[JMH]]
|
||||
- [projects.csv](../assets/projects_1663000066246_0.csv)
|
||||
@@ -1,8 +0,0 @@
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people::
|
||||
areas::
|
||||
date:: [[04-10-2022]] - 12:02
|
||||
|
||||
-
|
||||
@@ -1,18 +0,0 @@
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #comunicazioneUnivaq #people/alfonso
|
||||
areas::
|
||||
date:: [[04-10-2022]] - 12:02
|
||||
|
||||
- [Documento per Massimo Prosperorocco](https://todoist.com/showTask?id=6231715349)
|
||||
- Storia del gruppo, quando nasce, quali sono le *aree*, *prospettive condivise*, dove vogliamo andare
|
||||
- Elencare le cose fatte (sintetico)
|
||||
- Congressi organizzati, etc.
|
||||
- Non esploso nei minimi dettagli
|
||||
- Deve essere funzionale alla storia che vogliamo ricostruire e raccontare
|
||||
- Identificare gli elementi che accomunano le varie aree
|
||||
- Il documento deve essere un documento interno, per chiarezza nostra e nei confronti dell'ufficio immagine di Atene
|
||||
- [ACM Transactions on Interactive Intelligent Systems (scimagojr.com)](https://www.scimagojr.com/journalsearch.php?q=21100301601&tip=sid&clean=0)
|
||||
|
||||
-
|
||||
@@ -1,18 +0,0 @@
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags::
|
||||
people:: #comunicazioneUnivaq #people/alfonso
|
||||
areas::
|
||||
date:: [[04-10-2022]] - 12:02
|
||||
|
||||
- [Documento per Massimo Prosperorocco](https://todoist.com/showTask?id=6231715349)
|
||||
- Storia del gruppo, quando nasce, quali sono le *aree*, *prospettive condivise*, dove vogliamo andare
|
||||
- Elencare le cose fatte (sintetico)
|
||||
- Congressi organizzati, etc.
|
||||
- Non esploso nei minimi dettagli
|
||||
- Deve essere funzionale alla storia che vogliamo ricostruire e raccontare
|
||||
- Identificare gli elementi che accomunano le varie aree
|
||||
- Il documento deve essere un documento interno, per chiarezza nostra e nei confronti dell'ufficio immagine di Atene
|
||||
- [ACM Transactions on Interactive Intelligent Systems (scimagojr.com)](https://www.scimagojr.com/journalsearch.php?q=21100301601&tip=sid&clean=0)
|
||||
|
||||
-
|
||||
@@ -1,87 +0,0 @@
|
||||
## Notes
|
||||
- ## 🤝Meetings
|
||||
- Internal EMELIOT update
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PROJECTS/PRIN-EMELIOT]]
|
||||
people:: [[people/claudio]] [[people/giordano]] [[people/AntiniscaDiMarco]]
|
||||
date:: [[15-01-2024]] - 17:05
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- 
|
||||
- 
|
||||
- Ho dato come suggerimento quello di aggiungere una motivazione del perche' ha senso predirre. Quanto e' il costo che vado a risparmiare?
|
||||
- Antinisca ha suggerito anche usare MANILA in questa fase.
|
||||
- Usando MANILA si conosce a priori la variabile sensibile.
|
||||
- Sarebbe carino anche usare la libreria python per misurare il consumo di energia in Joule
|
||||
- 
|
||||
- 
|
||||
- *A* e' la variabile sensibile.
|
||||
- Metriche calcolability direttamente sul dataset iniziale.
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
-
|
||||
- Brainstorming with Phuong
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[BRAINSTORMING]]
|
||||
people:: [[people/PhuongNguyen]]
|
||||
date:: [[15-01-2024]] - 11:00
|
||||
duration::
|
||||
collapsed:: true
|
||||
- We had a quick update about the different activities.
|
||||
- DONE Phuong has been 3 weeks in Vietnam and started a collaboration with [[people/Le-Duc-Anh]] and [[people/Bui-Thi-Mai-Anh]], they started the paper [[PAPERS/EASE2024-SO-TITLE-GENERATION]]
|
||||
background-color:: green
|
||||
- We have been talking about the [[PAPERS/GITSUMMARIZATION]] paper. A user study is needed. The idea is extending [[PAPERS/EASE2023-GitSum]] with a user study and submit to a journal (maybe [[IST]])??
|
||||
background-color:: green
|
||||
- Concerning the recently rejected [[PAPERS/DEEPMIG-JSS-RESUBMISSION]] paper. Phuong proposed to resubmit it to [[IST]] without major changes.
|
||||
background-color:: green
|
||||
- Phuong mentioned a possible work to extend our [[EMSE]] paper on recsys with the goal of writing a follow-up work with extensions related to the use of deep learning approaches. I said that we need to carefully check what we could do more than the recent survey papers from David Lo and Mark Harman.
|
||||
- DOING We talked about the [[PAPERS/SSTD-LLMS]] paper and recaped the tasks that were decided during the [[12-01-2024]] meeting.
|
||||
background-color:: green
|
||||
- Finally, we talked about [[PAPERS/Code-Comments-Coherence]]. Phuong mentioned that the student involved in the paper had some personal issues. He will try to recover the paper.
|
||||
- Finally, we talked abou the paper with Rick Kazman (on Technical Dept). Phuong will push on this after the urgent things we currently have.
|
||||
-
|
||||
- Riunione organizzativa Open Days e PNRR
|
||||
type:: [[meeting]]
|
||||
title:: Riunuione organizzativa Open Days e PNRR
|
||||
external-links::
|
||||
tags:: [[SERVICES/ORIENTAMENTO]] [[SERVICES/ORIENTAMENTO/PNRR Orientamento 2026]]
|
||||
people::
|
||||
date:: [[15-01-2024]] - 13:40
|
||||
file-odg::
|
||||
duration::
|
||||
collapsed:: true
|
||||
- L'Ateneo dovrebbe ricevere circa 370kEuro per quanto fatto l'anno scorso per il progetto PNRR Orientamento 2026
|
||||
- Le scuole stanno mandando richieste. L'ultima e' del D'Annunzio di Pescara (Liceo Classico) per il 31 Gennaio. In alternativa, viene proposto il 24 Gennaio per il 31 Gennaio c'e' un altro evento.
|
||||
- Vedere documento [Attività Orientamento 2023-24 - Google Sheets](https://docs.google.com/spreadsheets/d/1rLW6sK6QPHlE7NP5PXhb8cIvXI8CRCh9RN5JDD0GBwY/edit#gid=0)
|
||||
- Per gli [[OpenDays]] si riproporrà il programma dell'anno scorso.
|
||||
- A Coppito, aule di diversa capienza
|
||||
- Gara per Brochure
|
||||
- Rollup (due per dipartimento)
|
||||
- Numero di Bruchure (ridurre a 5000 dei vari dipartimenti, 5000 generali, 1000 lingua inglese, da ridurre il numero di cartelline)
|
||||
-
|
||||
- ### From other pages
|
||||
- {{query (and [[15-01-2024]] (property :type "meeting") (not [[15-01-2024]]))}}
|
||||
query-table:: true
|
||||
-
|
||||
- ## 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[15-01-2024]]) (property :date-start [[15-01-2024]]) (property :date-submitted [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
- ## ⤴️Omnivore readings
|
||||
- {{query (and (property :source [[Omnivore]]) (or (property :deadline [[15-01-2024]]) (property :date-saved [[15-01-2024]]) (property :date-archived [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:labels :state :full-title]
|
||||
@@ -1,87 +0,0 @@
|
||||
## Notes
|
||||
- ## 🤝Meetings
|
||||
- Internal EMELIOT update
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PROJECTS/PRIN-EMELIOT]]
|
||||
people:: [[people/claudio]] [[people/giordano]] [[people/AntiniscaDiMarco]]
|
||||
date:: [[15-01-2024]] - 17:05
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- 
|
||||
- 
|
||||
- Ho dato come suggerimento quello di aggiungere una motivazione del perche' ha senso predirre. Quanto e' il costo che vado a risparmiare?
|
||||
- Antinisca ha suggerito anche usare MANILA in questa fase.
|
||||
- Usando MANILA si conosce a priori la variabile sensibile.
|
||||
- Sarebbe carino anche usare la libreria python per misurare il consumo di energia in Joule
|
||||
- 
|
||||
- 
|
||||
- *A* e' la variabile sensibile.
|
||||
- Metriche calcolability direttamente sul dataset iniziale.
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
-
|
||||
- Brainstorming with Phuong
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[BRAINSTORMING]]
|
||||
people:: [[people/PhuongNguyen]]
|
||||
date:: [[15-01-2024]] - 11:00
|
||||
duration::
|
||||
collapsed:: true
|
||||
- We had a quick update about the different activities.
|
||||
- DONE Phuong has been 3 weeks in Vietnam and started a collaboration with [[people/Le-Duc-Anh]] and [[people/Bui-Thi-Mai-Anh]], they started the paper [[PAPERS/EASE2024-SO-TITLE-GENERATION]]
|
||||
background-color:: green
|
||||
- We have been talking about the [[PAPERS/GITSUMMARIZATION]] paper. A user study is needed. The idea is extending [[PAPERS/EASE2023-GitSum]] with a user study and submit to a journal (maybe [[IST]])??
|
||||
background-color:: green
|
||||
- DONE Concerning the recently rejected [[PAPERS/DEEPMIG-JSS-RESUBMISSION]] paper. Phuong proposed to resubmit it to [[IST]] without major changes.
|
||||
background-color:: green
|
||||
- Phuong mentioned a possible work to extend our [[EMSE]] paper on recsys with the goal of writing a follow-up work with extensions related to the use of deep learning approaches. I said that we need to carefully check what we could do more than the recent survey papers from David Lo and Mark Harman.
|
||||
- DOING We talked about the [[PAPERS/SSTD-LLMS]] paper and recaped the tasks that were decided during the [[12-01-2024]] meeting.
|
||||
background-color:: green
|
||||
- DOING Finally, we talked about [[PAPERS/Code_Comments_Coherence]]. Phuong mentioned that the student involved in the paper had some personal issues. He will try to recover the paper.
|
||||
- Finally, we talked abou the paper with Rick Kazman (on Technical Dept). Phuong will push on this after the urgent things we currently have.
|
||||
-
|
||||
- Riunione organizzativa Open Days e PNRR
|
||||
type:: [[meeting]]
|
||||
title:: Riunuione organizzativa Open Days e PNRR
|
||||
external-links::
|
||||
tags:: [[SERVICES/ORIENTAMENTO]] [[SERVICES/ORIENTAMENTO/PNRR Orientamento 2026]]
|
||||
people::
|
||||
date:: [[15-01-2024]] - 13:40
|
||||
file-odg::
|
||||
duration::
|
||||
collapsed:: true
|
||||
- L'Ateneo dovrebbe ricevere circa 370kEuro per quanto fatto l'anno scorso per il progetto PNRR Orientamento 2026
|
||||
- Le scuole stanno mandando richieste. L'ultima e' del D'Annunzio di Pescara (Liceo Classico) per il 31 Gennaio. In alternativa, viene proposto il 24 Gennaio per il 31 Gennaio c'e' un altro evento.
|
||||
- Vedere documento [Attività Orientamento 2023-24 - Google Sheets](https://docs.google.com/spreadsheets/d/1rLW6sK6QPHlE7NP5PXhb8cIvXI8CRCh9RN5JDD0GBwY/edit#gid=0)
|
||||
- Per gli [[OpenDays]] si riproporrà il programma dell'anno scorso.
|
||||
- A Coppito, aule di diversa capienza
|
||||
- Gara per Brochure
|
||||
- Rollup (due per dipartimento)
|
||||
- Numero di Bruchure (ridurre a 5000 dei vari dipartimenti, 5000 generali, 1000 lingua inglese, da ridurre il numero di cartelline)
|
||||
-
|
||||
- ### From other pages
|
||||
- {{query (and [[15-01-2024]] (property :type "meeting") (not [[15-01-2024]]))}}
|
||||
query-table:: true
|
||||
-
|
||||
- ## 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[15-01-2024]]) (property :date-start [[15-01-2024]]) (property :date-submitted [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
- ## ⤴️Omnivore readings
|
||||
- {{query (and (property :source [[Omnivore]]) (or (property :deadline [[15-01-2024]]) (property :date-saved [[15-01-2024]]) (property :date-archived [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:labels :state :full-title]
|
||||
@@ -1,87 +0,0 @@
|
||||
## Notes
|
||||
- ## 🤝Meetings
|
||||
- Internal EMELIOT update
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PROJECTS/PRIN-EMELIOT]]
|
||||
people:: [[people/claudio]] [[people/giordano]] [[people/AntiniscaDiMarco]]
|
||||
date:: [[15-01-2024]] - 17:05
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- 
|
||||
- 
|
||||
- Ho dato come suggerimento quello di aggiungere una motivazione del perche' ha senso predirre. Quanto e' il costo che vado a risparmiare?
|
||||
- Antinisca ha suggerito anche usare MANILA in questa fase.
|
||||
- Usando MANILA si conosce a priori la variabile sensibile.
|
||||
- Sarebbe carino anche usare la libreria python per misurare il consumo di energia in Joule
|
||||
- 
|
||||
- 
|
||||
- *A* e' la variabile sensibile.
|
||||
- Metriche calcolability direttamente sul dataset iniziale.
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
-
|
||||
- Brainstorming with Phuong
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[BRAINSTORMING]]
|
||||
people:: [[people/PhuongNguyen]]
|
||||
date:: [[15-01-2024]] - 11:00
|
||||
duration::
|
||||
collapsed:: true
|
||||
- We had a quick update about the different activities.
|
||||
- DONE Phuong has been 3 weeks in Vietnam and started a collaboration with [[people/Le-Duc-Anh]] and [[people/Bui-Thi-Mai-Anh]], they started the paper [[PAPERS/EASE2024-SO-TITLE-GENERATION]]
|
||||
background-color:: green
|
||||
- We have been talking about the [[PAPERS/GITSUMMARIZATION]] paper. A user study is needed. The idea is extending [[PAPERS/EASE2023-GitSum]] with a user study and submit to a journal (maybe [[IST]])??
|
||||
background-color:: green
|
||||
- DONE Concerning the recently rejected [[PAPERS/DEEPMIG-JSS-RESUBMISSION]] paper. Phuong proposed to resubmit it to [[IST]] without major changes.
|
||||
background-color:: green
|
||||
- Phuong mentioned a possible work to extend our [[EMSE]] paper on recsys with the goal of writing a follow-up work with extensions related to the use of deep learning approaches. I said that we need to carefully check what we could do more than the recent survey papers from David Lo and Mark Harman.
|
||||
- DOING We talked about the [[PAPERS/SSTD-LLMS]] paper and recaped the tasks that were decided during the [[12-01-2024]] meeting.
|
||||
background-color:: green
|
||||
- DOING Finally, we talked about [[PAPERS/Code_Comments_Coherence]]. Phuong mentioned that the student involved in the paper had some personal issues. He will try to recover the paper.
|
||||
- Finally, we talked abou the paper with Rick Kazman (on Technical Dept). Phuong will push on this after the urgent things we currently have.
|
||||
-
|
||||
- Riunione organizzativa Open Days e PNRR
|
||||
type:: [[meeting]]
|
||||
title:: Riunuione organizzativa Open Days e PNRR
|
||||
external-links::
|
||||
tags:: [[SERVICES/ORIENTAMENTO]] [[SERVICES/ORIENTAMENTO/PNRR Orientamento 2026]]
|
||||
people::
|
||||
date:: [[15-01-2024]] - 13:40
|
||||
file-odg::
|
||||
duration::
|
||||
collapsed:: true
|
||||
- L'Ateneo dovrebbe ricevere circa 370kEuro per quanto fatto l'anno scorso per il progetto PNRR Orientamento 2026
|
||||
- Le scuole stanno mandando richieste. L'ultima e' del D'Annunzio di Pescara (Liceo Classico) per il 31 Gennaio. In alternativa, viene proposto il 24 Gennaio per il 31 Gennaio c'e' un altro evento.
|
||||
- Vedere documento [Attività Orientamento 2023-24 - Google Sheets](https://docs.google.com/spreadsheets/d/1rLW6sK6QPHlE7NP5PXhb8cIvXI8CRCh9RN5JDD0GBwY/edit#gid=0)
|
||||
- Per gli [[OpenDays]] si riproporrà il programma dell'anno scorso.
|
||||
- A Coppito, aule di diversa capienza
|
||||
- Gara per Brochure
|
||||
- Rollup (due per dipartimento)
|
||||
- Numero di Bruchure (ridurre a 5000 dei vari dipartimenti, 5000 generali, 1000 lingua inglese, da ridurre il numero di cartelline)
|
||||
-
|
||||
- ### From other pages
|
||||
- {{query (and [[15-01-2024]] (property :type "meeting") (not [[15-01-2024]]))}}
|
||||
query-table:: true
|
||||
-
|
||||
- ## 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[15-01-2024]]) (property :date-start [[15-01-2024]]) (property :date-submitted [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
- ## ⤴️Omnivore readings
|
||||
- {{query (and (property :source [[Omnivore]]) (or (property :deadline [[15-01-2024]]) (property :date-saved [[15-01-2024]]) (property :date-archived [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:labels :state :full-title]
|
||||
@@ -1,91 +0,0 @@
|
||||
-
|
||||
- ## Notes
|
||||
- ## 🤝Meetings
|
||||
- Internal EMELIOT update
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PROJECTS/PRIN-EMELIOT]]
|
||||
people:: [[people/claudio]] [[people/giordano]] [[people/AntiniscaDiMarco]]
|
||||
date:: [[15-01-2024]] - 17:05
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- 
|
||||
- 
|
||||
- Ho dato come suggerimento quello di aggiungere una motivazione del perche' ha senso predirre. Quanto e' il costo che vado a risparmiare?
|
||||
- Antinisca ha suggerito anche usare MANILA in questa fase.
|
||||
- Usando MANILA si conosce a priori la variabile sensibile.
|
||||
- Sarebbe carino anche usare la libreria python per misurare il consumo di energia in Joule
|
||||
- 
|
||||
- 
|
||||
- *A* e' la variabile sensibile.
|
||||
- Metriche calcolability direttamente sul dataset iniziale.
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
-
|
||||
- Brainstorming with Phuong
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[BRAINSTORMING]]
|
||||
people:: [[people/PhuongNguyen]]
|
||||
date:: [[15-01-2024]] - 11:00
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- We had a quick update about the different activities.
|
||||
- DONE Phuong has been 3 weeks in Vietnam and started a collaboration with [[people/Le-Duc-Anh]] and [[people/Bui-Thi-Mai-Anh]], they started the paper [[PAPERS/EASE2024-SO-TITLE-GENERATION]]
|
||||
background-color:: green
|
||||
- We have been talking about the [[PAPERS/GITSUMMARIZATION]] paper. A user study is needed. The idea is extending [[PAPERS/EASE2023-GitSum]] with a user study and submit to a journal (maybe [[IST]])??
|
||||
background-color:: green
|
||||
- [Human evaluation.xlsx (sharepoint.com)](https://husteduvn-my.sharepoint.com/:x:/g/personal/anh_buithimai_hust_edu_vn/EV_vfGCZMFlOmI3-PoSI05EBQkeeKgxHGtSpg7i9F-YRug?rtime=SXfp51FV3Eg)
|
||||
- DONE Concerning the recently rejected [[PAPERS/DEEPMIG-JSS-RESUBMISSION]] paper. Phuong proposed to resubmit it to [[IST]] without major changes.
|
||||
background-color:: green
|
||||
- Phuong mentioned a possible work to extend our [[EMSE]] paper on recsys with the goal of writing a follow-up work with extensions related to the use of deep learning approaches. I said that we need to carefully check what we could do more than the recent survey papers from David Lo and Mark Harman.
|
||||
background-color:: green
|
||||
- DOING We talked about the [[PAPERS/SSTD-LLMS]] paper and recaped the tasks that were decided during the [[12-01-2024]] meeting.
|
||||
background-color:: green
|
||||
- DOING Finally, we talked about [[PAPERS/EASE2024-Co3D]] . Phuong mentioned that the student involved in the paper had some personal issues. He will try to recover the paper.
|
||||
- Finally, we talked abou the paper with Rick Kazman (on Technical Dept). Phuong will push on this after the urgent things we currently have.
|
||||
-
|
||||
- Riunione organizzativa Open Days e PNRR
|
||||
type:: [[meeting]]
|
||||
title:: Riunuione organizzativa Open Days e PNRR
|
||||
external-links::
|
||||
tags:: [[SERVICES/ORIENTAMENTO]] [[SERVICES/ORIENTAMENTO/PNRR Orientamento 2026]]
|
||||
people::
|
||||
date:: [[15-01-2024]] - 13:40
|
||||
file-odg::
|
||||
file-verbale:: [Verbale commissione orientamento DATA 15 01 2024 REV (2).doc](../assets/Verbale_commissione_orientamento_DATA_15_01_2024_REV_(2)_1713523392509_0.doc)
|
||||
duration::
|
||||
- L'Ateneo dovrebbe ricevere circa 370kEuro per quanto fatto l'anno scorso per il progetto PNRR Orientamento 2026
|
||||
- Le scuole stanno mandando richieste. L'ultima e' del D'Annunzio di Pescara (Liceo Classico) per il 31 Gennaio. In alternativa, viene proposto il 24 Gennaio per il 31 Gennaio c'e' un altro evento.
|
||||
- Vedere documento [Attività Orientamento 2023-24 - Google Sheets](https://docs.google.com/spreadsheets/d/1rLW6sK6QPHlE7NP5PXhb8cIvXI8CRCh9RN5JDD0GBwY/edit#gid=0)
|
||||
- Per gli [[OpenDays]] si riproporrà il programma dell'anno scorso.
|
||||
- A Coppito, aule di diversa capienza
|
||||
- Gara per Brochure
|
||||
- Rollup (due per dipartimento)
|
||||
- Numero di Bruchure (ridurre a 5000 dei vari dipartimenti, 5000 generali, 1000 lingua inglese, da ridurre il numero di cartelline)
|
||||
-
|
||||
- ### From other pages
|
||||
- {{query (and [[15-01-2024]] (property :type "meeting") (not [[15-01-2024]]))}}
|
||||
query-table:: true
|
||||
-
|
||||
- ## 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[15-01-2024]]) (property :date-start [[15-01-2024]]) (property :date-submitted [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
- ## ⤴️Omnivore readings
|
||||
- {{query (and (property :source [[Omnivore]]) (or (property :deadline [[15-01-2024]]) (property :date-saved [[15-01-2024]]) (property :date-archived [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:labels :state :full-title]
|
||||
@@ -1,95 +0,0 @@
|
||||
-
|
||||
- ## Notes
|
||||
- ## 🤝Meetings
|
||||
- Internal EMELIOT update
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PROJECTS/PRIN-EMELIOT]]
|
||||
people:: [[people/claudio]] [[people/giordano]] [[people/AntiniscaDiMarco]]
|
||||
date:: [[15-01-2024]] - 17:05
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- 
|
||||
- 
|
||||
- Ho dato come suggerimento quello di aggiungere una motivazione del perche' ha senso predirre. Quanto e' il costo che vado a risparmiare?
|
||||
- Antinisca ha suggerito anche usare MANILA in questa fase.
|
||||
- Usando MANILA si conosce a priori la variabile sensibile.
|
||||
- Sarebbe carino anche usare la libreria python per misurare il consumo di energia in Joule
|
||||
- 
|
||||
- 
|
||||
- *A* e' la variabile sensibile.
|
||||
- Metriche calcolability direttamente sul dataset iniziale.
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
-
|
||||
- Brainstorming with Phuong
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[BRAINSTORMING]]
|
||||
people:: [[people/PhuongNguyen]]
|
||||
date:: [[15-01-2024]] - 11:00
|
||||
duration::
|
||||
collapsed:: true
|
||||
-
|
||||
- We had a quick update about the different activities.
|
||||
- DONE Phuong has been 3 weeks in Vietnam and started a collaboration with [[people/Le-Duc-Anh]] and [[people/Bui-Thi-Mai-Anh]], they started the paper [[PAPERS/EASE2024-SO-TITLE-GENERATION]]
|
||||
background-color:: green
|
||||
- We have been talking about the [[PAPERS/GITSUMMARIZATION]] paper. A user study is needed. The idea is extending [[PAPERS/EASE2023-GitSum]] with a user study and submit to a journal (maybe [[IST]])??
|
||||
background-color:: green
|
||||
- [Human evaluation.xlsx (sharepoint.com)](https://husteduvn-my.sharepoint.com/:x:/g/personal/anh_buithimai_hust_edu_vn/EV_vfGCZMFlOmI3-PoSI05EBQkeeKgxHGtSpg7i9F-YRug?rtime=SXfp51FV3Eg)
|
||||
- DONE Concerning the recently rejected [[PAPERS/DEEPMIG-JSS-RESUBMISSION]] paper. Phuong proposed to resubmit it to [[IST]] without major changes.
|
||||
background-color:: green
|
||||
- Phuong mentioned a possible work to extend our [[EMSE]] paper on recsys with the goal of writing a follow-up work with extensions related to the use of deep learning approaches. I said that we need to carefully check what we could do more than the recent survey papers from David Lo and Mark Harman.
|
||||
background-color:: green
|
||||
- DOING We talked about the [[PAPERS/SSTD-LLMS]] paper and recaped the tasks that were decided during the [[12-01-2024]] meeting.
|
||||
background-color:: green
|
||||
- DONE Finally, we talked about [[PAPERS/EASE2024-Co3D]] . Phuong mentioned that the student involved in the paper had some personal issues. He will try to recover the paper.
|
||||
id:: 65c8d43c-9e5e-455f-9c48-cb6d035417fc
|
||||
- DOING Finally, we talked abou the paper with Rick Kazman (on Technical Dept). Phuong will push on this after the urgent things we currently have.
|
||||
:LOGBOOK:
|
||||
CLOCK: [2025-05-21 Wed 09:04:50]
|
||||
:END:
|
||||
-
|
||||
- Riunione organizzativa Open Days e PNRR
|
||||
type:: [[meeting]]
|
||||
title:: Riunuione organizzativa Open Days e PNRR
|
||||
external-links::
|
||||
tags:: [[SERVICES/ORIENTAMENTO]] [[SERVICES/ORIENTAMENTO/PNRR Orientamento 2026]]
|
||||
people::
|
||||
date:: [[15-01-2024]] - 13:40
|
||||
file-odg::
|
||||
file-verbale:: [Verbale commissione orientamento DATA 15 01 2024 REV (2).doc](../assets/Verbale_commissione_orientamento_DATA_15_01_2024_REV_(2)_1713523392509_0.doc)
|
||||
duration::
|
||||
- L'Ateneo dovrebbe ricevere circa 370kEuro per quanto fatto l'anno scorso per il progetto PNRR Orientamento 2026
|
||||
- Le scuole stanno mandando richieste. L'ultima e' del D'Annunzio di Pescara (Liceo Classico) per il 31 Gennaio. In alternativa, viene proposto il 24 Gennaio per il 31 Gennaio c'e' un altro evento.
|
||||
- Vedere documento [Attività Orientamento 2023-24 - Google Sheets](https://docs.google.com/spreadsheets/d/1rLW6sK6QPHlE7NP5PXhb8cIvXI8CRCh9RN5JDD0GBwY/edit#gid=0)
|
||||
- Per gli [[OpenDays]] si riproporrà il programma dell'anno scorso.
|
||||
- A Coppito, aule di diversa capienza
|
||||
- Gara per Brochure
|
||||
- Rollup (due per dipartimento)
|
||||
- Numero di Bruchure (ridurre a 5000 dei vari dipartimenti, 5000 generali, 1000 lingua inglese, da ridurre il numero di cartelline)
|
||||
-
|
||||
- ### From other pages
|
||||
- {{query (and [[15-01-2024]] (property :type "meeting") (not [[15-01-2024]]))}}
|
||||
query-table:: true
|
||||
-
|
||||
- ## 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end [[15-01-2024]]) (property :date-start [[15-01-2024]]) (property :date-submitted [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
- ## ⤴️Omnivore readings
|
||||
- {{query (and (property :source [[Omnivore]]) (or (property :deadline [[15-01-2024]]) (property :date-saved [[15-01-2024]]) (property :date-archived [[15-01-2024]])))}}
|
||||
query-table:: true
|
||||
query-properties:: [:labels :state :full-title]
|
||||
@@ -1,363 +0,0 @@
|
||||
{:meta/version 1
|
||||
|
||||
;; Currently, we support either "Markdown" or "Org".
|
||||
;; This can overwrite your global preference so that
|
||||
;; maybe your personal preferred format is Org but you'd
|
||||
;; need to use Markdown for some projects.
|
||||
;; :preferred-format ""
|
||||
|
||||
;; Preferred workflow style.
|
||||
;; Value is either ":now" for NOW/LATER style,
|
||||
;; or ":todo" for TODO/DOING style.
|
||||
:preferred-workflow :todo
|
||||
|
||||
;; The app will ignore those directories or files.
|
||||
;; E.g. :hidden ["/archived" "/test.md" "../assets/archived"]
|
||||
:hidden []
|
||||
|
||||
;; When creating the new journal page, the app will use your template if there is one.
|
||||
;; You only need to input your template name here.
|
||||
:default-templates
|
||||
{:journals "JOURNAL-TEMPLATE"}
|
||||
|
||||
;; Set a custom date format for journal page title
|
||||
;; Example:
|
||||
;; :journal/page-title-format "EEE, do MMM yyyy"
|
||||
|
||||
;; Whether to enable hover on tooltip preview feature
|
||||
;; Default is true, you can also toggle this via setting page
|
||||
:ui/enable-tooltip? true
|
||||
|
||||
;; Show brackets around page references
|
||||
;; :ui/show-brackets? true
|
||||
|
||||
;; Enable showing the body of blocks when referencing them.
|
||||
:ui/show-full-blocks? true
|
||||
|
||||
;; Expand block references automatically when zoom-in
|
||||
:ui/auto-expand-block-refs? true
|
||||
|
||||
;; Enable Block timestamp
|
||||
:feature/enable-block-timestamps? false
|
||||
|
||||
;; Enable remove accents when searching.
|
||||
;; After toggle this option, please remember to rebuild your search index by press (cmd+c cmd+s).
|
||||
:feature/enable-search-remove-accents? true
|
||||
|
||||
;; Enable journals
|
||||
;; :feature/enable-journals? true
|
||||
|
||||
;; Enable flashcards
|
||||
;; :feature/enable-flashcards? true
|
||||
|
||||
;; Enable Whiteboards
|
||||
;; :feature/enable-whiteboards? true
|
||||
|
||||
;; Disable the built-in Scheduled tasks and deadlines query
|
||||
:feature/disable-scheduled-and-deadline-query? false
|
||||
|
||||
;; Specify the number of days in the future to display in the
|
||||
;; scheduled tasks and deadlines query, with a default value of 7 which
|
||||
;; displays tasks for the next 7 days.
|
||||
;; Example usage:
|
||||
;; Display all scheduled and deadline blocks for the next 14 days
|
||||
:scheduled/future-days 7
|
||||
|
||||
;; Specify the date on which the week starts.
|
||||
;; Goes from 0 to 6 (Monday to Sunday), default to 6
|
||||
:start-of-week 0
|
||||
|
||||
;; Specify a custom CSS import
|
||||
;; This option take precedence over your local `logseq/custom.css` file
|
||||
;; You may find a list of awesome logseq themes here:
|
||||
;; https://github.com/logseq/awesome-logseq#css-themes
|
||||
;; Example:
|
||||
;; :custom-css-url "@import url('https://cdn.jsdelivr.net/gh/dracula/logseq@master/custom.css');"
|
||||
|
||||
;; Specify a custom js import
|
||||
;; This option take precedence over your local `logseq/custom.js` file
|
||||
;; :custom-js-url ""
|
||||
|
||||
;; Set a custom Arweave gateway
|
||||
;; Default gateway: https://arweave.net
|
||||
;; :arweave/gateway ""
|
||||
|
||||
;; Set Bullet indentation when exporting
|
||||
;; default option: tab
|
||||
;; Possible options for `:export/bullet-indentation` are
|
||||
;; 1. `:eight-spaces` as eight spaces
|
||||
;; 2. `:four-spaces` as four spaces
|
||||
;; 3. `:two-spaces` as two spaces
|
||||
;; :export/bullet-indentation :tab
|
||||
|
||||
;; When :all-pages-public? true, export repo would export all pages within that repo.
|
||||
;; Regardless of whether you've set any page to public or not.
|
||||
;; Example:
|
||||
;; :publishing/all-pages-public? true
|
||||
|
||||
;; Specify default home page and sidebar status for Logseq
|
||||
;; If not specified, Logseq default opens journals page on startup
|
||||
;; value for `:page` is name of page
|
||||
;; Possible options for `:sidebar` are
|
||||
;; 1. `"Contents"` to open up `Contents` in sidebar by default
|
||||
;; 2. `page name` to open up some page in sidebar
|
||||
;; 3. Or multiple pages in an array ["Contents" "Page A" "Page B"]
|
||||
;; If `:sidebar` is not set, sidebar will be hidden
|
||||
;; Example:
|
||||
;; 1. Setup page "Changelog" as home page and "Contents" in sidebar
|
||||
;; :default-home {:page "Changelog", :sidebar "Contents"}
|
||||
;; 2. Setup page "Jun 3rd, 2021" as home page without sidebar
|
||||
;; :default-home {:page "Jun 3rd, 2021"}
|
||||
;; 3. Setup page "home" as home page with multiple pages in sidebar
|
||||
;; :default-home {:page "home" :sidebar ["page a" "page b"]}
|
||||
|
||||
;; Tell logseq to use a specific folder in the repo as a default location for notes
|
||||
;; if not specified, notes are stored in `pages` directory
|
||||
;; :pages-directory "your-directory"
|
||||
|
||||
;; Tell logseq to use a specific folder in the repo as a default location for journals
|
||||
;; if not specified, journals are stored in `journals` directory
|
||||
;; :journals-directory "your-directory"
|
||||
|
||||
;; Set this to true will convert
|
||||
;; `[[Grant Ideas]]` to `[[file:./grant_ideas.org][Grant Ideas]]` for org-mode
|
||||
;; For more, see https://github.com/logseq/logseq/issues/672
|
||||
;; :org-mode/insert-file-link? true
|
||||
|
||||
;; Setup custom shortcuts under `:shortcuts` key
|
||||
;; Syntax:
|
||||
;; 1. `+` means keys pressing simultaneously. eg: `ctrl+shift+a`
|
||||
;; 2. ` ` empty space between keys represents key chords. eg: `t s` means press `t` followed by `s`
|
||||
;; 3. `mod` means `Ctrl` for Windows/Linux and `Command` for Mac
|
||||
;; 4. use `false` to disable particular shortcut
|
||||
;; 5. you can define multiple bindings for one action, eg `["ctrl+j" "down"]`
|
||||
;; full list of configurable shortcuts are available below:
|
||||
;; https://github.com/logseq/logseq/blob/master/src/main/frontend/modules/shortcut/config.cljs
|
||||
;; Example:
|
||||
;; :shortcuts
|
||||
;; {:editor/new-block "enter"
|
||||
;; :editor/new-line "shift+enter"
|
||||
;; :editor/insert-link "mod+shift+k"
|
||||
;; :editor/highlight false
|
||||
;; :ui/toggle-settings "t s"
|
||||
;; :editor/up ["ctrl+k" "up"]
|
||||
;; :editor/down ["ctrl+j" "down"]
|
||||
;; :editor/left ["ctrl+h" "left"]
|
||||
;; :editor/right ["ctrl+l" "right"]}
|
||||
:shortcuts {}
|
||||
|
||||
;; By default, pressing `Enter` in the document mode will create a new line.
|
||||
;; Set this to `true` so that it's the same behaviour as the usual outliner mode.
|
||||
:shortcut/doc-mode-enter-for-new-block? false
|
||||
|
||||
;; Block content larger than `block/content-max-length` will not be searchable
|
||||
;; or editable for performance.
|
||||
:block/content-max-length 10000
|
||||
|
||||
;; Whether to show command doc on hover
|
||||
:ui/show-command-doc? true
|
||||
|
||||
;; Whether to show empty bullets for non-document mode (the default mode)
|
||||
:ui/show-empty-bullets? false
|
||||
|
||||
;; Pre-defined :view function to use with advanced queries
|
||||
:query/views
|
||||
{:pprint
|
||||
(fn [r] [:pre.code (pprint r)])}
|
||||
|
||||
;; Pre-defined :result-transform function for use with advanced queries
|
||||
:query/result-transforms
|
||||
{:sort-by-priority
|
||||
(fn [result] (sort-by (fn [h] (get h :block/priority "Z")) result))}
|
||||
|
||||
;; The app will show those queries in today's journal page,
|
||||
;; the "NOW" query asks the tasks which need to be finished "now",
|
||||
;; the "NEXT" query asks the future tasks.
|
||||
:default-queries
|
||||
{:journals
|
||||
[{:title "🔨 NOW"
|
||||
:query [:find (pull ?h [*])
|
||||
:in $ ?start ?today
|
||||
:where
|
||||
[?h :block/marker ?marker]
|
||||
[(contains? #{"NOW" "DOING"} ?marker)]
|
||||
[?h :block/page ?p]
|
||||
[?p :block/journal? true]
|
||||
[?p :block/journal-day ?d]
|
||||
[(>= ?d ?start)]
|
||||
[(<= ?d ?today)]]
|
||||
:inputs [:14d :today]
|
||||
:result-transform (fn [result]
|
||||
(sort-by (fn [h]
|
||||
(get h :block/priority "Z")) result))
|
||||
:group-by-page? false
|
||||
:collapsed? true}
|
||||
{:title "📅 NEXT"
|
||||
:query [:find (pull ?h [*])
|
||||
:in $ ?start ?next
|
||||
:where
|
||||
[?h :block/marker ?marker]
|
||||
[(contains? #{"NOW" "LATER" "TODO"} ?marker)]
|
||||
[?h :block/page ?p]
|
||||
[?p :block/journal? true]
|
||||
[?p :block/journal-day ?d]
|
||||
[(> ?d ?start)]
|
||||
[(< ?d ?next)]]
|
||||
:inputs [:today :7d-after]
|
||||
:group-by-page? false
|
||||
:collapsed? true}
|
||||
{:title "Reviews"
|
||||
|
||||
}]}
|
||||
|
||||
;; Add your own commands to slash menu to speedup.
|
||||
;; E.g.
|
||||
;; :commands
|
||||
;; [
|
||||
;; ["js" "Javascript"]
|
||||
;; ["md" "Markdown"]
|
||||
;; ]
|
||||
:commands
|
||||
[]
|
||||
|
||||
;; By default, a block can only be collapsed if it has some children.
|
||||
;; `:outliner/block-title-collapse-enabled? true` enables a block with a title
|
||||
;; (multiple lines) can be collapsed too. For example:
|
||||
;; - block title
|
||||
;; block content
|
||||
:outliner/block-title-collapse-enabled? true
|
||||
|
||||
;; Macros replace texts and will make you more productive.
|
||||
;; For example:
|
||||
;; Change the :macros value below to:
|
||||
;; {"poem" "Rose is $1, violet's $2. Life's ordered: Org assists you."}
|
||||
;; input "{{poem red,blue}}"
|
||||
;; becomes
|
||||
;; Rose is red, violet's blue. Life's ordered: Org assists you.
|
||||
:macros {}
|
||||
|
||||
;; The default level to be opened for the linked references.
|
||||
;; For example, if we have some example blocks like this:
|
||||
;; - a [[page]] (level 1)
|
||||
;; - b (level 2)
|
||||
;; - c (level 3)
|
||||
;; - d (level 4)
|
||||
;;
|
||||
;; With the default value of level 2, `b` will be collapsed.
|
||||
;; If we set the level's value to 3, `b` will be opened and `c` will be collapsed.
|
||||
:ref/default-open-blocks-level 1
|
||||
|
||||
:ref/linked-references-collapsed-threshold 0
|
||||
|
||||
;; Favorites to list on the left sidebar
|
||||
:favorites ["Writing Challenges" "inbox" "todoist-logseqed" "planner" "desktop" "diario" "brainstorming" "reviews" "services/phdict" "cv empower" "projects" "services/dottorato" "papers" "teaching" "books" "todoist-dashboard" "consigliodisim" "services/placement" "ideas"]
|
||||
|
||||
;; any number between 0 and 1 (the greater it is the faster the changes of the next-interval of card reviews) (default 0.5)
|
||||
;; :srs/learning-fraction 0.5
|
||||
|
||||
;; the initial interval after the first successful review of a card (default 4)
|
||||
;; :srs/initial-interval 4
|
||||
|
||||
;; hide specific properties for blocks
|
||||
;; E.g. :block-hidden-properties #{:created-at :updated-at}
|
||||
;; :block-hidden-properties #{}
|
||||
;; :block-hidden-properties #{:todoistid }
|
||||
|
||||
|
||||
;; Enable all your properties to have corresponding pages
|
||||
:property-pages/enabled? true
|
||||
|
||||
;; Properties to exclude from having property pages
|
||||
;; E.g.:property-pages/excludelist #{:duration :author}
|
||||
;; :property-pages/excludelist
|
||||
|
||||
;; By default, property value separated by commas will not be treated as
|
||||
;; page references. You can add properties to enable it.
|
||||
;; E.g. :property/separated-by-commas #{:alias :tags}
|
||||
;; :property/separated-by-commas #{}
|
||||
|
||||
;; Properties that are ignored when parsing property values for references
|
||||
;; :ignored-page-references-keywords #{:author :startup}
|
||||
|
||||
;; logbook setup
|
||||
;; :logbook/settings
|
||||
;; {:with-second-support? false ;limit logbook to minutes, seconds will be eliminated
|
||||
;; :enabled-in-all-blocks true ;display logbook in all blocks after timetracking
|
||||
;; :enabled-in-timestamped-blocks false ;don't display logbook at all
|
||||
;; }
|
||||
|
||||
;; Mobile photo uploading setup
|
||||
;; :mobile/photo
|
||||
;; {:allow-editing? true
|
||||
;; :quality 80}
|
||||
|
||||
;; Mobile features options
|
||||
;; Gestures
|
||||
;; :mobile
|
||||
;; {:gestures/disabled-in-block-with-tags ["kanban"]}
|
||||
|
||||
;; Extra CodeMirror options
|
||||
;; See https://codemirror.net/5/doc/manual.html#config for possible options
|
||||
;; :editor/extra-codemirror-options {:keyMap "emacs" :lineWrapping true}
|
||||
|
||||
;; Enable logical outdenting
|
||||
;; :editor/logical-outdenting? true
|
||||
|
||||
;; When both text and a file are in the clipboard, paste the file
|
||||
;; :editor/preferred-pasting-file? true
|
||||
|
||||
;; Quick capture templates for receiving contents from other apps.
|
||||
;; Each template contains three elements {time}, {text} and {url}, which can be auto-expanded
|
||||
;; by received contents from other apps. Note: the {} cannot be omitted.
|
||||
;; - {time}: capture time
|
||||
;; - {date}: capture date using current date format, use `[[{date}]]` to get a page reference
|
||||
;; - {text}: text that users selected before sharing.
|
||||
;; - {url}: url or assets path for media files stored in Logseq.
|
||||
;; You can also reorder them, or even only use one or two of them in the template.
|
||||
;; You can also insert or format any text in the template as shown in the following examples.
|
||||
;; :quick-capture-templates
|
||||
;; {:text "[[quick capture]] **{time}**: {text} from {url}"
|
||||
;; :media "[[quick capture]] **{time}**: {url}"}
|
||||
|
||||
;; Quick capture options
|
||||
;; :quick-capture-options {:insert-today? false :redirect-page? false :default-page "my page"}
|
||||
|
||||
;; File sync options
|
||||
;; Ignore these files when syncing, regexp is supported.
|
||||
;; :file-sync/ignore-files []
|
||||
|
||||
;; dwim (do what I mean) for Enter key when editing.
|
||||
;; Context-awareness of Enter key makes editing more easily
|
||||
; :dwim/settings {
|
||||
; :admonition&src? true
|
||||
; :markup? false
|
||||
; :block-ref? true
|
||||
; :page-ref? true
|
||||
; :properties? true
|
||||
; :list? true
|
||||
; }
|
||||
|
||||
;; Decide the way to escape the special characters in the page title.
|
||||
;; Warning:
|
||||
;; This is a dangerous operation. If you want to change the setting,
|
||||
;; should access the setting `Filename format` and follow the instructions.
|
||||
;; Or you have to rename all the affected files manually then re-index on all
|
||||
;; clients after the files are synced. Wrong handling may cause page titles
|
||||
;; containing special characters to be messy.
|
||||
;; Available values:
|
||||
;; :file/name-format :triple-lowbar
|
||||
;; ;use triple underscore `___` for slash `/` in page title
|
||||
;; ;use Percent-encoding for other invalid characters
|
||||
:file/name-format :triple-lowbar
|
||||
:journal/page-title-format "dd-MM-yyyy"
|
||||
:ui/show-brackets? true
|
||||
:zotero/settings-v2 {"default" {:extra-tags "#zotero", :zotero-data-directory "C:/Users/david/Zotero", :zotero-linked-attachment-base-directory "C:/Users/david/Zotero", :type-id "1039502", :type :user, :notes-block-text "### Notes", :page-insert-prefix "@", :include-notes? true, :attachments-block-text "### Attachments"}}
|
||||
:editor/logical-outdenting? false
|
||||
:feature/enable-timetracking? true
|
||||
:feature/enable-whiteboards? false
|
||||
:editor/preferred-pasting-file? true
|
||||
|
||||
;; specify the format of the filename for journal files
|
||||
;; :journal/file-name-format "yyyy_MM_dd"
|
||||
:editor/extra-codemirror-options {:theme "gruvbox-dark"}
|
||||
}
|
||||
@@ -1,363 +0,0 @@
|
||||
{:meta/version 1
|
||||
|
||||
;; Currently, we support either "Markdown" or "Org".
|
||||
;; This can overwrite your global preference so that
|
||||
;; maybe your personal preferred format is Org but you'd
|
||||
;; need to use Markdown for some projects.
|
||||
;; :preferred-format ""
|
||||
|
||||
;; Preferred workflow style.
|
||||
;; Value is either ":now" for NOW/LATER style,
|
||||
;; or ":todo" for TODO/DOING style.
|
||||
:preferred-workflow :todo
|
||||
|
||||
;; The app will ignore those directories or files.
|
||||
;; E.g. :hidden ["/archived" "/test.md" "../assets/archived"]
|
||||
:hidden []
|
||||
|
||||
;; When creating the new journal page, the app will use your template if there is one.
|
||||
;; You only need to input your template name here.
|
||||
:default-templates
|
||||
{:journals "JOURNAL-TEMPLATE"}
|
||||
|
||||
;; Set a custom date format for journal page title
|
||||
;; Example:
|
||||
;; :journal/page-title-format "EEE, do MMM yyyy"
|
||||
|
||||
;; Whether to enable hover on tooltip preview feature
|
||||
;; Default is true, you can also toggle this via setting page
|
||||
:ui/enable-tooltip? true
|
||||
|
||||
;; Show brackets around page references
|
||||
;; :ui/show-brackets? true
|
||||
|
||||
;; Enable showing the body of blocks when referencing them.
|
||||
:ui/show-full-blocks? true
|
||||
|
||||
;; Expand block references automatically when zoom-in
|
||||
:ui/auto-expand-block-refs? true
|
||||
|
||||
;; Enable Block timestamp
|
||||
:feature/enable-block-timestamps? false
|
||||
|
||||
;; Enable remove accents when searching.
|
||||
;; After toggle this option, please remember to rebuild your search index by press (cmd+c cmd+s).
|
||||
:feature/enable-search-remove-accents? true
|
||||
|
||||
;; Enable journals
|
||||
;; :feature/enable-journals? true
|
||||
|
||||
;; Enable flashcards
|
||||
;; :feature/enable-flashcards? true
|
||||
|
||||
;; Enable Whiteboards
|
||||
;; :feature/enable-whiteboards? true
|
||||
|
||||
;; Disable the built-in Scheduled tasks and deadlines query
|
||||
:feature/disable-scheduled-and-deadline-query? false
|
||||
|
||||
;; Specify the number of days in the future to display in the
|
||||
;; scheduled tasks and deadlines query, with a default value of 7 which
|
||||
;; displays tasks for the next 7 days.
|
||||
;; Example usage:
|
||||
;; Display all scheduled and deadline blocks for the next 14 days
|
||||
:scheduled/future-days 7
|
||||
|
||||
;; Specify the date on which the week starts.
|
||||
;; Goes from 0 to 6 (Monday to Sunday), default to 6
|
||||
:start-of-week 0
|
||||
|
||||
;; Specify a custom CSS import
|
||||
;; This option take precedence over your local `logseq/custom.css` file
|
||||
;; You may find a list of awesome logseq themes here:
|
||||
;; https://github.com/logseq/awesome-logseq#css-themes
|
||||
;; Example:
|
||||
;; :custom-css-url "@import url('https://cdn.jsdelivr.net/gh/dracula/logseq@master/custom.css');"
|
||||
|
||||
;; Specify a custom js import
|
||||
;; This option take precedence over your local `logseq/custom.js` file
|
||||
;; :custom-js-url ""
|
||||
|
||||
;; Set a custom Arweave gateway
|
||||
;; Default gateway: https://arweave.net
|
||||
;; :arweave/gateway ""
|
||||
|
||||
;; Set Bullet indentation when exporting
|
||||
;; default option: tab
|
||||
;; Possible options for `:export/bullet-indentation` are
|
||||
;; 1. `:eight-spaces` as eight spaces
|
||||
;; 2. `:four-spaces` as four spaces
|
||||
;; 3. `:two-spaces` as two spaces
|
||||
;; :export/bullet-indentation :tab
|
||||
|
||||
;; When :all-pages-public? true, export repo would export all pages within that repo.
|
||||
;; Regardless of whether you've set any page to public or not.
|
||||
;; Example:
|
||||
;; :publishing/all-pages-public? true
|
||||
|
||||
;; Specify default home page and sidebar status for Logseq
|
||||
;; If not specified, Logseq default opens journals page on startup
|
||||
;; value for `:page` is name of page
|
||||
;; Possible options for `:sidebar` are
|
||||
;; 1. `"Contents"` to open up `Contents` in sidebar by default
|
||||
;; 2. `page name` to open up some page in sidebar
|
||||
;; 3. Or multiple pages in an array ["Contents" "Page A" "Page B"]
|
||||
;; If `:sidebar` is not set, sidebar will be hidden
|
||||
;; Example:
|
||||
;; 1. Setup page "Changelog" as home page and "Contents" in sidebar
|
||||
;; :default-home {:page "Changelog", :sidebar "Contents"}
|
||||
;; 2. Setup page "Jun 3rd, 2021" as home page without sidebar
|
||||
;; :default-home {:page "Jun 3rd, 2021"}
|
||||
;; 3. Setup page "home" as home page with multiple pages in sidebar
|
||||
;; :default-home {:page "home" :sidebar ["page a" "page b"]}
|
||||
|
||||
;; Tell logseq to use a specific folder in the repo as a default location for notes
|
||||
;; if not specified, notes are stored in `pages` directory
|
||||
;; :pages-directory "your-directory"
|
||||
|
||||
;; Tell logseq to use a specific folder in the repo as a default location for journals
|
||||
;; if not specified, journals are stored in `journals` directory
|
||||
;; :journals-directory "your-directory"
|
||||
|
||||
;; Set this to true will convert
|
||||
;; `[[Grant Ideas]]` to `[[file:./grant_ideas.org][Grant Ideas]]` for org-mode
|
||||
;; For more, see https://github.com/logseq/logseq/issues/672
|
||||
;; :org-mode/insert-file-link? true
|
||||
|
||||
;; Setup custom shortcuts under `:shortcuts` key
|
||||
;; Syntax:
|
||||
;; 1. `+` means keys pressing simultaneously. eg: `ctrl+shift+a`
|
||||
;; 2. ` ` empty space between keys represents key chords. eg: `t s` means press `t` followed by `s`
|
||||
;; 3. `mod` means `Ctrl` for Windows/Linux and `Command` for Mac
|
||||
;; 4. use `false` to disable particular shortcut
|
||||
;; 5. you can define multiple bindings for one action, eg `["ctrl+j" "down"]`
|
||||
;; full list of configurable shortcuts are available below:
|
||||
;; https://github.com/logseq/logseq/blob/master/src/main/frontend/modules/shortcut/config.cljs
|
||||
;; Example:
|
||||
;; :shortcuts
|
||||
;; {:editor/new-block "enter"
|
||||
;; :editor/new-line "shift+enter"
|
||||
;; :editor/insert-link "mod+shift+k"
|
||||
;; :editor/highlight false
|
||||
;; :ui/toggle-settings "t s"
|
||||
;; :editor/up ["ctrl+k" "up"]
|
||||
;; :editor/down ["ctrl+j" "down"]
|
||||
;; :editor/left ["ctrl+h" "left"]
|
||||
;; :editor/right ["ctrl+l" "right"]}
|
||||
:shortcuts {}
|
||||
|
||||
;; By default, pressing `Enter` in the document mode will create a new line.
|
||||
;; Set this to `true` so that it's the same behaviour as the usual outliner mode.
|
||||
:shortcut/doc-mode-enter-for-new-block? false
|
||||
|
||||
;; Block content larger than `block/content-max-length` will not be searchable
|
||||
;; or editable for performance.
|
||||
:block/content-max-length 10000
|
||||
|
||||
;; Whether to show command doc on hover
|
||||
:ui/show-command-doc? true
|
||||
|
||||
;; Whether to show empty bullets for non-document mode (the default mode)
|
||||
:ui/show-empty-bullets? false
|
||||
|
||||
;; Pre-defined :view function to use with advanced queries
|
||||
:query/views
|
||||
{:pprint
|
||||
(fn [r] [:pre.code (pprint r)])}
|
||||
|
||||
;; Pre-defined :result-transform function for use with advanced queries
|
||||
:query/result-transforms
|
||||
{:sort-by-priority
|
||||
(fn [result] (sort-by (fn [h] (get h :block/priority "Z")) result))}
|
||||
|
||||
;; The app will show those queries in today's journal page,
|
||||
;; the "NOW" query asks the tasks which need to be finished "now",
|
||||
;; the "NEXT" query asks the future tasks.
|
||||
:default-queries
|
||||
{:journals
|
||||
[{:title "🔨 NOW"
|
||||
:query [:find (pull ?h [*])
|
||||
:in $ ?start ?today
|
||||
:where
|
||||
[?h :block/marker ?marker]
|
||||
[(contains? #{"NOW" "DOING"} ?marker)]
|
||||
[?h :block/page ?p]
|
||||
[?p :block/journal? true]
|
||||
[?p :block/journal-day ?d]
|
||||
[(>= ?d ?start)]
|
||||
[(<= ?d ?today)]]
|
||||
:inputs [:14d :today]
|
||||
:result-transform (fn [result]
|
||||
(sort-by (fn [h]
|
||||
(get h :block/priority "Z")) result))
|
||||
:group-by-page? false
|
||||
:collapsed? true}
|
||||
{:title "📅 NEXT"
|
||||
:query [:find (pull ?h [*])
|
||||
:in $ ?start ?next
|
||||
:where
|
||||
[?h :block/marker ?marker]
|
||||
[(contains? #{"NOW" "LATER" "TODO"} ?marker)]
|
||||
[?h :block/page ?p]
|
||||
[?p :block/journal? true]
|
||||
[?p :block/journal-day ?d]
|
||||
[(> ?d ?start)]
|
||||
[(< ?d ?next)]]
|
||||
:inputs [:today :7d-after]
|
||||
:group-by-page? false
|
||||
:collapsed? true}
|
||||
{:title "Reviews"
|
||||
|
||||
}]}
|
||||
|
||||
;; Add your own commands to slash menu to speedup.
|
||||
;; E.g.
|
||||
;; :commands
|
||||
;; [
|
||||
;; ["js" "Javascript"]
|
||||
;; ["md" "Markdown"]
|
||||
;; ]
|
||||
:commands
|
||||
[]
|
||||
|
||||
;; By default, a block can only be collapsed if it has some children.
|
||||
;; `:outliner/block-title-collapse-enabled? true` enables a block with a title
|
||||
;; (multiple lines) can be collapsed too. For example:
|
||||
;; - block title
|
||||
;; block content
|
||||
:outliner/block-title-collapse-enabled? true
|
||||
|
||||
;; Macros replace texts and will make you more productive.
|
||||
;; For example:
|
||||
;; Change the :macros value below to:
|
||||
;; {"poem" "Rose is $1, violet's $2. Life's ordered: Org assists you."}
|
||||
;; input "{{poem red,blue}}"
|
||||
;; becomes
|
||||
;; Rose is red, violet's blue. Life's ordered: Org assists you.
|
||||
:macros {}
|
||||
|
||||
;; The default level to be opened for the linked references.
|
||||
;; For example, if we have some example blocks like this:
|
||||
;; - a [[page]] (level 1)
|
||||
;; - b (level 2)
|
||||
;; - c (level 3)
|
||||
;; - d (level 4)
|
||||
;;
|
||||
;; With the default value of level 2, `b` will be collapsed.
|
||||
;; If we set the level's value to 3, `b` will be opened and `c` will be collapsed.
|
||||
:ref/default-open-blocks-level 1
|
||||
|
||||
:ref/linked-references-collapsed-threshold 0
|
||||
|
||||
;; Favorites to list on the left sidebar
|
||||
:favorites ["writing challenges" "inbox" "todoist-logseqed" "planner" "desktop" "diario" "brainstorming" "reviews" "services/phdict" "cv empower" "projects" "services/dottorato" "papers" "teaching" "books" "todoist-dashboard" "consigliodisim" "services/placement" "ideas"]
|
||||
|
||||
;; any number between 0 and 1 (the greater it is the faster the changes of the next-interval of card reviews) (default 0.5)
|
||||
;; :srs/learning-fraction 0.5
|
||||
|
||||
;; the initial interval after the first successful review of a card (default 4)
|
||||
;; :srs/initial-interval 4
|
||||
|
||||
;; hide specific properties for blocks
|
||||
;; E.g. :block-hidden-properties #{:created-at :updated-at}
|
||||
;; :block-hidden-properties #{}
|
||||
;; :block-hidden-properties #{:todoistid }
|
||||
|
||||
|
||||
;; Enable all your properties to have corresponding pages
|
||||
:property-pages/enabled? true
|
||||
|
||||
;; Properties to exclude from having property pages
|
||||
;; E.g.:property-pages/excludelist #{:duration :author}
|
||||
;; :property-pages/excludelist
|
||||
|
||||
;; By default, property value separated by commas will not be treated as
|
||||
;; page references. You can add properties to enable it.
|
||||
;; E.g. :property/separated-by-commas #{:alias :tags}
|
||||
;; :property/separated-by-commas #{}
|
||||
|
||||
;; Properties that are ignored when parsing property values for references
|
||||
;; :ignored-page-references-keywords #{:author :startup}
|
||||
|
||||
;; logbook setup
|
||||
;; :logbook/settings
|
||||
;; {:with-second-support? false ;limit logbook to minutes, seconds will be eliminated
|
||||
;; :enabled-in-all-blocks true ;display logbook in all blocks after timetracking
|
||||
;; :enabled-in-timestamped-blocks false ;don't display logbook at all
|
||||
;; }
|
||||
|
||||
;; Mobile photo uploading setup
|
||||
;; :mobile/photo
|
||||
;; {:allow-editing? true
|
||||
;; :quality 80}
|
||||
|
||||
;; Mobile features options
|
||||
;; Gestures
|
||||
;; :mobile
|
||||
;; {:gestures/disabled-in-block-with-tags ["kanban"]}
|
||||
|
||||
;; Extra CodeMirror options
|
||||
;; See https://codemirror.net/5/doc/manual.html#config for possible options
|
||||
;; :editor/extra-codemirror-options {:keyMap "emacs" :lineWrapping true}
|
||||
|
||||
;; Enable logical outdenting
|
||||
;; :editor/logical-outdenting? true
|
||||
|
||||
;; When both text and a file are in the clipboard, paste the file
|
||||
;; :editor/preferred-pasting-file? true
|
||||
|
||||
;; Quick capture templates for receiving contents from other apps.
|
||||
;; Each template contains three elements {time}, {text} and {url}, which can be auto-expanded
|
||||
;; by received contents from other apps. Note: the {} cannot be omitted.
|
||||
;; - {time}: capture time
|
||||
;; - {date}: capture date using current date format, use `[[{date}]]` to get a page reference
|
||||
;; - {text}: text that users selected before sharing.
|
||||
;; - {url}: url or assets path for media files stored in Logseq.
|
||||
;; You can also reorder them, or even only use one or two of them in the template.
|
||||
;; You can also insert or format any text in the template as shown in the following examples.
|
||||
;; :quick-capture-templates
|
||||
;; {:text "[[quick capture]] **{time}**: {text} from {url}"
|
||||
;; :media "[[quick capture]] **{time}**: {url}"}
|
||||
|
||||
;; Quick capture options
|
||||
;; :quick-capture-options {:insert-today? false :redirect-page? false :default-page "my page"}
|
||||
|
||||
;; File sync options
|
||||
;; Ignore these files when syncing, regexp is supported.
|
||||
;; :file-sync/ignore-files []
|
||||
|
||||
;; dwim (do what I mean) for Enter key when editing.
|
||||
;; Context-awareness of Enter key makes editing more easily
|
||||
; :dwim/settings {
|
||||
; :admonition&src? true
|
||||
; :markup? false
|
||||
; :block-ref? true
|
||||
; :page-ref? true
|
||||
; :properties? true
|
||||
; :list? true
|
||||
; }
|
||||
|
||||
;; Decide the way to escape the special characters in the page title.
|
||||
;; Warning:
|
||||
;; This is a dangerous operation. If you want to change the setting,
|
||||
;; should access the setting `Filename format` and follow the instructions.
|
||||
;; Or you have to rename all the affected files manually then re-index on all
|
||||
;; clients after the files are synced. Wrong handling may cause page titles
|
||||
;; containing special characters to be messy.
|
||||
;; Available values:
|
||||
;; :file/name-format :triple-lowbar
|
||||
;; ;use triple underscore `___` for slash `/` in page title
|
||||
;; ;use Percent-encoding for other invalid characters
|
||||
:file/name-format :triple-lowbar
|
||||
:journal/page-title-format "dd-MM-yyyy"
|
||||
:ui/show-brackets? true
|
||||
:zotero/settings-v2 {"default" {:extra-tags "#zotero", :zotero-data-directory "C:/Users/david/Zotero", :zotero-linked-attachment-base-directory "C:/Users/david/Zotero", :type-id "1039502", :type :user, :notes-block-text "### Notes", :page-insert-prefix "@", :include-notes? true, :attachments-block-text "### Attachments"}}
|
||||
:editor/logical-outdenting? false
|
||||
:feature/enable-timetracking? true
|
||||
:feature/enable-whiteboards? false
|
||||
:editor/preferred-pasting-file? true
|
||||
|
||||
;; specify the format of the filename for journal files
|
||||
;; :journal/file-name-format "yyyy_MM_dd"
|
||||
:editor/extra-codemirror-options {:theme "gruvbox-dark"}
|
||||
}
|
||||
@@ -1,363 +0,0 @@
|
||||
{:meta/version 1
|
||||
|
||||
;; Currently, we support either "Markdown" or "Org".
|
||||
;; This can overwrite your global preference so that
|
||||
;; maybe your personal preferred format is Org but you'd
|
||||
;; need to use Markdown for some projects.
|
||||
;; :preferred-format ""
|
||||
|
||||
;; Preferred workflow style.
|
||||
;; Value is either ":now" for NOW/LATER style,
|
||||
;; or ":todo" for TODO/DOING style.
|
||||
:preferred-workflow :todo
|
||||
|
||||
;; The app will ignore those directories or files.
|
||||
;; E.g. :hidden ["/archived" "/test.md" "../assets/archived"]
|
||||
:hidden []
|
||||
|
||||
;; When creating the new journal page, the app will use your template if there is one.
|
||||
;; You only need to input your template name here.
|
||||
:default-templates
|
||||
{:journals "JOURNAL-TEMPLATE"}
|
||||
|
||||
;; Set a custom date format for journal page title
|
||||
;; Example:
|
||||
;; :journal/page-title-format "EEE, do MMM yyyy"
|
||||
|
||||
;; Whether to enable hover on tooltip preview feature
|
||||
;; Default is true, you can also toggle this via setting page
|
||||
:ui/enable-tooltip? false
|
||||
|
||||
;; Show brackets around page references
|
||||
;; :ui/show-brackets? true
|
||||
|
||||
;; Enable showing the body of blocks when referencing them.
|
||||
:ui/show-full-blocks? true
|
||||
|
||||
;; Expand block references automatically when zoom-in
|
||||
:ui/auto-expand-block-refs? false
|
||||
|
||||
;; Enable Block timestamp
|
||||
:feature/enable-block-timestamps? false
|
||||
|
||||
;; Enable remove accents when searching.
|
||||
;; After toggle this option, please remember to rebuild your search index by press (cmd+c cmd+s).
|
||||
:feature/enable-search-remove-accents? true
|
||||
|
||||
;; Enable journals
|
||||
;; :feature/enable-journals? true
|
||||
|
||||
;; Enable flashcards
|
||||
;; :feature/enable-flashcards? true
|
||||
|
||||
;; Enable Whiteboards
|
||||
;; :feature/enable-whiteboards? true
|
||||
|
||||
;; Disable the built-in Scheduled tasks and deadlines query
|
||||
:feature/disable-scheduled-and-deadline-query? false
|
||||
|
||||
;; Specify the number of days in the future to display in the
|
||||
;; scheduled tasks and deadlines query, with a default value of 7 which
|
||||
;; displays tasks for the next 7 days.
|
||||
;; Example usage:
|
||||
;; Display all scheduled and deadline blocks for the next 14 days
|
||||
:scheduled/future-days 7
|
||||
|
||||
;; Specify the date on which the week starts.
|
||||
;; Goes from 0 to 6 (Monday to Sunday), default to 6
|
||||
:start-of-week 6
|
||||
|
||||
;; Specify a custom CSS import
|
||||
;; This option take precedence over your local `logseq/custom.css` file
|
||||
;; You may find a list of awesome logseq themes here:
|
||||
;; https://github.com/logseq/awesome-logseq#css-themes
|
||||
;; Example:
|
||||
;; :custom-css-url "@import url('https://cdn.jsdelivr.net/gh/dracula/logseq@master/custom.css');"
|
||||
|
||||
;; Specify a custom js import
|
||||
;; This option take precedence over your local `logseq/custom.js` file
|
||||
;; :custom-js-url ""
|
||||
|
||||
;; Set a custom Arweave gateway
|
||||
;; Default gateway: https://arweave.net
|
||||
;; :arweave/gateway ""
|
||||
|
||||
;; Set Bullet indentation when exporting
|
||||
;; default option: tab
|
||||
;; Possible options for `:export/bullet-indentation` are
|
||||
;; 1. `:eight-spaces` as eight spaces
|
||||
;; 2. `:four-spaces` as four spaces
|
||||
;; 3. `:two-spaces` as two spaces
|
||||
;; :export/bullet-indentation :tab
|
||||
|
||||
;; When :all-pages-public? true, export repo would export all pages within that repo.
|
||||
;; Regardless of whether you've set any page to public or not.
|
||||
;; Example:
|
||||
;; :publishing/all-pages-public? true
|
||||
|
||||
;; Specify default home page and sidebar status for Logseq
|
||||
;; If not specified, Logseq default opens journals page on startup
|
||||
;; value for `:page` is name of page
|
||||
;; Possible options for `:sidebar` are
|
||||
;; 1. `"Contents"` to open up `Contents` in sidebar by default
|
||||
;; 2. `page name` to open up some page in sidebar
|
||||
;; 3. Or multiple pages in an array ["Contents" "Page A" "Page B"]
|
||||
;; If `:sidebar` is not set, sidebar will be hidden
|
||||
;; Example:
|
||||
;; 1. Setup page "Changelog" as home page and "Contents" in sidebar
|
||||
;; :default-home {:page "Changelog", :sidebar "Contents"}
|
||||
;; 2. Setup page "Jun 3rd, 2021" as home page without sidebar
|
||||
;; :default-home {:page "Jun 3rd, 2021"}
|
||||
;; 3. Setup page "home" as home page with multiple pages in sidebar
|
||||
;; :default-home {:page "home" :sidebar ["page a" "page b"]}
|
||||
|
||||
;; Tell logseq to use a specific folder in the repo as a default location for notes
|
||||
;; if not specified, notes are stored in `pages` directory
|
||||
;; :pages-directory "your-directory"
|
||||
|
||||
;; Tell logseq to use a specific folder in the repo as a default location for journals
|
||||
;; if not specified, journals are stored in `journals` directory
|
||||
;; :journals-directory "your-directory"
|
||||
|
||||
;; Set this to true will convert
|
||||
;; `[[Grant Ideas]]` to `[[file:./grant_ideas.org][Grant Ideas]]` for org-mode
|
||||
;; For more, see https://github.com/logseq/logseq/issues/672
|
||||
;; :org-mode/insert-file-link? true
|
||||
|
||||
;; Setup custom shortcuts under `:shortcuts` key
|
||||
;; Syntax:
|
||||
;; 1. `+` means keys pressing simultaneously. eg: `ctrl+shift+a`
|
||||
;; 2. ` ` empty space between keys represents key chords. eg: `t s` means press `t` followed by `s`
|
||||
;; 3. `mod` means `Ctrl` for Windows/Linux and `Command` for Mac
|
||||
;; 4. use `false` to disable particular shortcut
|
||||
;; 5. you can define multiple bindings for one action, eg `["ctrl+j" "down"]`
|
||||
;; full list of configurable shortcuts are available below:
|
||||
;; https://github.com/logseq/logseq/blob/master/src/main/frontend/modules/shortcut/config.cljs
|
||||
;; Example:
|
||||
;; :shortcuts
|
||||
;; {:editor/new-block "enter"
|
||||
;; :editor/new-line "shift+enter"
|
||||
;; :editor/insert-link "mod+shift+k"
|
||||
;; :editor/highlight false
|
||||
;; :ui/toggle-settings "t s"
|
||||
;; :editor/up ["ctrl+k" "up"]
|
||||
;; :editor/down ["ctrl+j" "down"]
|
||||
;; :editor/left ["ctrl+h" "left"]
|
||||
;; :editor/right ["ctrl+l" "right"]}
|
||||
:shortcuts {}
|
||||
|
||||
;; By default, pressing `Enter` in the document mode will create a new line.
|
||||
;; Set this to `true` so that it's the same behaviour as the usual outliner mode.
|
||||
:shortcut/doc-mode-enter-for-new-block? false
|
||||
|
||||
;; Block content larger than `block/content-max-length` will not be searchable
|
||||
;; or editable for performance.
|
||||
:block/content-max-length 10000
|
||||
|
||||
;; Whether to show command doc on hover
|
||||
:ui/show-command-doc? true
|
||||
|
||||
;; Whether to show empty bullets for non-document mode (the default mode)
|
||||
:ui/show-empty-bullets? false
|
||||
|
||||
;; Pre-defined :view function to use with advanced queries
|
||||
:query/views
|
||||
{:pprint
|
||||
(fn [r] [:pre.code (pprint r)])}
|
||||
|
||||
;; Pre-defined :result-transform function for use with advanced queries
|
||||
:query/result-transforms
|
||||
{:sort-by-priority
|
||||
(fn [result] (sort-by (fn [h] (get h :block/priority "Z")) result))}
|
||||
|
||||
;; The app will show those queries in today's journal page,
|
||||
;; the "NOW" query asks the tasks which need to be finished "now",
|
||||
;; the "NEXT" query asks the future tasks.
|
||||
:default-queries
|
||||
{:journals
|
||||
[{:title "🔨 NOW"
|
||||
:query [:find (pull ?h [*])
|
||||
:in $ ?start ?today
|
||||
:where
|
||||
[?h :block/marker ?marker]
|
||||
[(contains? #{"NOW" "DOING"} ?marker)]
|
||||
[?h :block/page ?p]
|
||||
[?p :block/journal? true]
|
||||
[?p :block/journal-day ?d]
|
||||
[(>= ?d ?start)]
|
||||
[(<= ?d ?today)]]
|
||||
:inputs [:14d :today]
|
||||
:result-transform (fn [result]
|
||||
(sort-by (fn [h]
|
||||
(get h :block/priority "Z")) result))
|
||||
:group-by-page? false
|
||||
:collapsed? true}
|
||||
{:title "📅 NEXT"
|
||||
:query [:find (pull ?h [*])
|
||||
:in $ ?start ?next
|
||||
:where
|
||||
[?h :block/marker ?marker]
|
||||
[(contains? #{"NOW" "LATER" "TODO"} ?marker)]
|
||||
[?h :block/page ?p]
|
||||
[?p :block/journal? true]
|
||||
[?p :block/journal-day ?d]
|
||||
[(> ?d ?start)]
|
||||
[(< ?d ?next)]]
|
||||
:inputs [:today :7d-after]
|
||||
:group-by-page? false
|
||||
:collapsed? true}
|
||||
{:title "Reviews"
|
||||
|
||||
}]}
|
||||
|
||||
;; Add your own commands to slash menu to speedup.
|
||||
;; E.g.
|
||||
;; :commands
|
||||
;; [
|
||||
;; ["js" "Javascript"]
|
||||
;; ["md" "Markdown"]
|
||||
;; ]
|
||||
:commands
|
||||
[]
|
||||
|
||||
;; By default, a block can only be collapsed if it has some children.
|
||||
;; `:outliner/block-title-collapse-enabled? true` enables a block with a title
|
||||
;; (multiple lines) can be collapsed too. For example:
|
||||
;; - block title
|
||||
;; block content
|
||||
:outliner/block-title-collapse-enabled? true
|
||||
|
||||
;; Macros replace texts and will make you more productive.
|
||||
;; For example:
|
||||
;; Change the :macros value below to:
|
||||
;; {"poem" "Rose is $1, violet's $2. Life's ordered: Org assists you."}
|
||||
;; input "{{poem red,blue}}"
|
||||
;; becomes
|
||||
;; Rose is red, violet's blue. Life's ordered: Org assists you.
|
||||
:macros {}
|
||||
|
||||
;; The default level to be opened for the linked references.
|
||||
;; For example, if we have some example blocks like this:
|
||||
;; - a [[page]] (level 1)
|
||||
;; - b (level 2)
|
||||
;; - c (level 3)
|
||||
;; - d (level 4)
|
||||
;;
|
||||
;; With the default value of level 2, `b` will be collapsed.
|
||||
;; If we set the level's value to 3, `b` will be opened and `c` will be collapsed.
|
||||
:ref/default-open-blocks-level 1
|
||||
|
||||
:ref/linked-references-collapsed-threshold 0
|
||||
|
||||
;; Favorites to list on the left sidebar
|
||||
:favorites ["inbox" "todoist-logseqed" "planner" "desktop" "diario" "brainstorming" "reviews" "services/phdict" "cv empower" "projects" "services/dottorato" "papers" "teaching" "books" "todoist-dashboard" "consigliodisim" "services/placement" "ideas"]
|
||||
|
||||
;; any number between 0 and 1 (the greater it is the faster the changes of the next-interval of card reviews) (default 0.5)
|
||||
;; :srs/learning-fraction 0.5
|
||||
|
||||
;; the initial interval after the first successful review of a card (default 4)
|
||||
;; :srs/initial-interval 4
|
||||
|
||||
;; hide specific properties for blocks
|
||||
;; E.g. :block-hidden-properties #{:created-at :updated-at}
|
||||
;; :block-hidden-properties #{}
|
||||
:block-hidden-properties #{:todoistid }
|
||||
|
||||
|
||||
;; Enable all your properties to have corresponding pages
|
||||
:property-pages/enabled? true
|
||||
|
||||
;; Properties to exclude from having property pages
|
||||
;; E.g.:property-pages/excludelist #{:duration :author}
|
||||
;; :property-pages/excludelist
|
||||
|
||||
;; By default, property value separated by commas will not be treated as
|
||||
;; page references. You can add properties to enable it.
|
||||
;; E.g. :property/separated-by-commas #{:alias :tags}
|
||||
;; :property/separated-by-commas #{}
|
||||
|
||||
;; Properties that are ignored when parsing property values for references
|
||||
;; :ignored-page-references-keywords #{:author :startup}
|
||||
|
||||
;; logbook setup
|
||||
;; :logbook/settings
|
||||
;; {:with-second-support? false ;limit logbook to minutes, seconds will be eliminated
|
||||
;; :enabled-in-all-blocks true ;display logbook in all blocks after timetracking
|
||||
;; :enabled-in-timestamped-blocks false ;don't display logbook at all
|
||||
;; }
|
||||
|
||||
;; Mobile photo uploading setup
|
||||
;; :mobile/photo
|
||||
;; {:allow-editing? true
|
||||
;; :quality 80}
|
||||
|
||||
;; Mobile features options
|
||||
;; Gestures
|
||||
;; :mobile
|
||||
;; {:gestures/disabled-in-block-with-tags ["kanban"]}
|
||||
|
||||
;; Extra CodeMirror options
|
||||
;; See https://codemirror.net/5/doc/manual.html#config for possible options
|
||||
;; :editor/extra-codemirror-options {:keyMap "emacs" :lineWrapping true}
|
||||
|
||||
;; Enable logical outdenting
|
||||
;; :editor/logical-outdenting? true
|
||||
|
||||
;; When both text and a file are in the clipboard, paste the file
|
||||
;; :editor/preferred-pasting-file? true
|
||||
|
||||
;; Quick capture templates for receiving contents from other apps.
|
||||
;; Each template contains three elements {time}, {text} and {url}, which can be auto-expanded
|
||||
;; by received contents from other apps. Note: the {} cannot be omitted.
|
||||
;; - {time}: capture time
|
||||
;; - {date}: capture date using current date format, use `[[{date}]]` to get a page reference
|
||||
;; - {text}: text that users selected before sharing.
|
||||
;; - {url}: url or assets path for media files stored in Logseq.
|
||||
;; You can also reorder them, or even only use one or two of them in the template.
|
||||
;; You can also insert or format any text in the template as shown in the following examples.
|
||||
;; :quick-capture-templates
|
||||
;; {:text "[[quick capture]] **{time}**: {text} from {url}"
|
||||
;; :media "[[quick capture]] **{time}**: {url}"}
|
||||
|
||||
;; Quick capture options
|
||||
;; :quick-capture-options {:insert-today? false :redirect-page? false :default-page "my page"}
|
||||
|
||||
;; File sync options
|
||||
;; Ignore these files when syncing, regexp is supported.
|
||||
;; :file-sync/ignore-files []
|
||||
|
||||
;; dwim (do what I mean) for Enter key when editing.
|
||||
;; Context-awareness of Enter key makes editing more easily
|
||||
; :dwim/settings {
|
||||
; :admonition&src? true
|
||||
; :markup? false
|
||||
; :block-ref? true
|
||||
; :page-ref? true
|
||||
; :properties? true
|
||||
; :list? true
|
||||
; }
|
||||
|
||||
;; Decide the way to escape the special characters in the page title.
|
||||
;; Warning:
|
||||
;; This is a dangerous operation. If you want to change the setting,
|
||||
;; should access the setting `Filename format` and follow the instructions.
|
||||
;; Or you have to rename all the affected files manually then re-index on all
|
||||
;; clients after the files are synced. Wrong handling may cause page titles
|
||||
;; containing special characters to be messy.
|
||||
;; Available values:
|
||||
;; :file/name-format :triple-lowbar
|
||||
;; ;use triple underscore `___` for slash `/` in page title
|
||||
;; ;use Percent-encoding for other invalid characters
|
||||
:file/name-format :triple-lowbar
|
||||
:journal/page-title-format "dd-MM-yyyy"
|
||||
:ui/show-brackets? false
|
||||
:zotero/settings-v2 {"default" {:extra-tags "#zotero", :zotero-data-directory "C:/Users/david/Zotero", :zotero-linked-attachment-base-directory "C:/Users/david/Zotero", :type-id "1039502", :type :user, :notes-block-text "### Notes", :page-insert-prefix "@", :include-notes? true, :attachments-block-text "### Attachments"}}
|
||||
:editor/logical-outdenting? false
|
||||
:feature/enable-timetracking? true
|
||||
:feature/enable-whiteboards? false
|
||||
:editor/preferred-pasting-file? true
|
||||
|
||||
;; specify the format of the filename for journal files
|
||||
;; :journal/file-name-format "yyyy_MM_dd"
|
||||
:editor/extra-codemirror-options {:theme "gruvbox-dark"}
|
||||
}
|
||||
@@ -1,17 +0,0 @@
|
||||
div.block-properties > div:has(div:empty) {
|
||||
display: none;
|
||||
}
|
||||
|
||||
a.page-ref[data-ref="alias" i] {
|
||||
font-size: 0;
|
||||
}
|
||||
|
||||
a.page-ref[data-ref="alias" i]::before {
|
||||
font-family: 'Material Icons';
|
||||
content: "content_copy";
|
||||
visibility: visible;
|
||||
display: inline-block;
|
||||
font-size: initial;
|
||||
vertical-align: top;
|
||||
color: rgb(83, 83, 83);
|
||||
}
|
||||
@@ -1,3 +0,0 @@
|
||||
div.block-properties > div:has(div:empty) {
|
||||
display: none;
|
||||
}
|
||||
@@ -1,58 +0,0 @@
|
||||
@import url('https://fonts.googleapis.com/css2?family=Mulish&display=swap');
|
||||
|
||||
/* === Font Settings === */
|
||||
html, body {
|
||||
font-family: 'Mulish', sans-serif !important;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
:root {
|
||||
--ls-font-family: 'Mulish', sans-serif;
|
||||
--ls-page-text-size: 16px;
|
||||
--ls-ui-font-family: system-ui;
|
||||
--ls-ui-font-size: 14px;
|
||||
}
|
||||
|
||||
/* === Backgrounds === */
|
||||
:root {
|
||||
--ls-left-sidebar-background: #2E3234;
|
||||
--ls-right-sidebar-background: #FBFBFB;
|
||||
--ls-main-background: #FBFBFB;
|
||||
--ls-secondary-background: #F7F7F7;
|
||||
--ls-tertiary-background: #FFFFFF;
|
||||
|
||||
--ls-page-properties-background-color: #F7F7F7;
|
||||
--ls-block-properties-background-color: #F7F7F7;
|
||||
}
|
||||
|
||||
/* === Text === */
|
||||
:root {
|
||||
--ls-primary-text-color: #2E3234;
|
||||
--ls-title-text-color: #2E3234;
|
||||
--ls-link-text-color: #CF4444;
|
||||
--ls-link-text-hover-color: #CF4444;
|
||||
--ls-external-link-color: #CF4444;
|
||||
--ls-tag-text-color: #FFFFFF;
|
||||
--ls-tag-background-color: #A3A3A3;
|
||||
|
||||
--ls-head-text-color: #2E3234;
|
||||
--ls-bold-text-color: #2E3234;
|
||||
--ls-italic-text-color: #2E3234;
|
||||
}
|
||||
|
||||
/* === Sidebar === */
|
||||
#left-sidebar {
|
||||
background-color: #2E3234 !important;
|
||||
color: #CFCFCF !important;
|
||||
}
|
||||
#left-sidebar .header {
|
||||
color: #CFCFCF;
|
||||
}
|
||||
#left-sidebar .logo {
|
||||
color: #CF4444 !important;
|
||||
}
|
||||
|
||||
/* === Headers (H1–H6) === */
|
||||
h1, h2, h3, h4, h5, h6 {
|
||||
color: #2E3234 !important;
|
||||
}
|
||||
@@ -1,30 +0,0 @@
|
||||
- icon::🔥
|
||||
- #+BEGIN_PINNED
|
||||
This is a space where new technologies / ideas are explored. This is the starting point with links to notes presenting ideas that are matured while reading technical documents.
|
||||
#+END_PINNED
|
||||
- ## Documentazione tecnica
|
||||
- [[OpenAI examples]]
|
||||
- [debanjandhar12/logseq-anki-sync: An logseq to anki syncing plugin. (github.com)](https://github.com/debanjandhar12/logseq-anki-sync)
|
||||
- [[PYTHON]]
|
||||
- ## Reading
|
||||
- [[Omnivore]]
|
||||
- [[ReadingNotes]]
|
||||
- [[@A Survey of Large Language Models]]
|
||||
- [[Highlights]]
|
||||
- [[STAR]]
|
||||
- ## Some [[thoughts]]
|
||||
- I need to make some practice with ML models, DL ones and also with LLMs. Deeply understanding their difference is also necessary!
|
||||
- Concepts to be further understood:
|
||||
- Batch size
|
||||
- Epoc
|
||||
- Concerning hyper-parameter values:
|
||||
- learning rate (e.g., $5 \times 10^{-5}$)
|
||||
- Optimizer (e.g., AdamW)
|
||||
- Scheduler (e.g., linear decay)
|
||||
- Concerning [[pretrainedmodels]] relevant concepts are early stopping, with checkpoints saved every epoch, a delta of 0.005, and a patience of 5
|
||||
- I need to do some hands-on sessions to understand technical details.
|
||||
- As general comments for doing so, maybe I could schedule a couple of hours on Saturday or Sunday with a dedicated session for exploring new technologies and to gain insights from them.
|
||||
- Following the previous point, I think it is important to schedule also writing sessions when I can push myself beyond my confort zone concerning my writing capabilities. I need to improve them, both in English and Italian.
|
||||
- I could spend one hour per night on reading and writing, forgetting about University duties and thus just focusing on such empowering sessions dedicated to make practice on writing in general.
|
||||
- The previous suggestion is a good one. However, I have to finish at least the work related to the PhD admission of the students of the XL cycle, the pending reviews, and the TESORO paper.
|
||||
- I could define the requirements of a simple application to be developed from my side.
|
||||
@@ -1,28 +0,0 @@
|
||||
icon:: 💪
|
||||
|
||||
-
|
||||
- #+BEGIN_PINNED
|
||||
This is a space where new technologies / ideas are explored. This is the starting point with links to notes presenting ideas that are matured while reading technical documents.
|
||||
#+END_PINNED
|
||||
- ## Documentazione tecnica
|
||||
- [[OpenAI examples]]
|
||||
- [debanjandhar12/logseq-anki-sync: An logseq to anki syncing plugin. (github.com)](https://github.com/debanjandhar12/logseq-anki-sync)
|
||||
- [[PYTHON]]
|
||||
- ## Reading
|
||||
- [[Omnivore]]
|
||||
- [[ReadingNotes]]
|
||||
- [[Highlights]]
|
||||
- [[STAR]]
|
||||
- ## Some Thoughts
|
||||
- I need to make some practice with ML models, DL ones and also with LLMs. Deeply understanding their difference is also necessary!
|
||||
- Concepts to be further understood:
|
||||
- Batch size
|
||||
- Epoc
|
||||
- Concerning hyper-parameter values:
|
||||
- learning rate (e.g., $5 \times 10^{-5}$)
|
||||
- Optimizer (e.g., AdamW)
|
||||
- Scheduler (e.g., linear decay)
|
||||
- I need to do some hands-on sessions to understand technical details.
|
||||
- As general comments for doing so, maybe I could schedule a couple of hours on Saturday or Sunday with a dedicated session for exploring new technologies and to gain insights from them.
|
||||
- Following the previous point, I think it is important to schedule also writing sessions when I can push myself beyond my confort zone concerning my writing capabilities. I need to improve them, both in English and Italian.
|
||||
- I could spend one hour per night on reading and writing, forgetting about University duties and thus just focusing on such empowering sessions dedicated to make practice on writing in general.
|
||||
@@ -1,28 +0,0 @@
|
||||
icon:: 💪
|
||||
|
||||
-
|
||||
- #+BEGIN_PINNED
|
||||
This is a space where new technologies / ideas are explored. This is the starting point with links to notes presenting ideas that are matured while reading technical documents.
|
||||
#+END_PINNED
|
||||
- ## Documentazione tecnica
|
||||
- [[OpenAI examples]]
|
||||
- [debanjandhar12/logseq-anki-sync: An logseq to anki syncing plugin. (github.com)](https://github.com/debanjandhar12/logseq-anki-sync)
|
||||
- [[PYTHON]]
|
||||
- ## Reading
|
||||
- [[Omnivore]]
|
||||
- [[ReadingNotes]]
|
||||
- [[Highlights]]
|
||||
- [[STAR]]
|
||||
- ## Some Thoughts
|
||||
- I need to make some practice with ML models, DL ones and also with LLMs. Deeply understanding their difference is also necessary!
|
||||
- Concepts to be further understood:
|
||||
- Batch size
|
||||
- Epoc
|
||||
- Concerning hyper-parameter values:
|
||||
- learning rate (e.g., $5 \times 10^{-5}$)
|
||||
- Optimizer (e.g., AdamW)
|
||||
- Scheduler (e.g., linear decay)
|
||||
- I need to do some hands-on sessions to understand technical details.
|
||||
- As general comments for doing so, maybe I could schedule a couple of hours on Saturday or Sunday with a dedicated session for exploring new technologies and to gain insights from them.
|
||||
- Following the previous point, I think it is important to schedule also writing sessions when I can push myself beyond my confort zone concerning my writing capabilities. I need to improve them, both in English and Italian.
|
||||
- I could spend one hour per night on reading and writing, forgetting about University duties and thus just focusing on such empowering sessions dedicated to make practice on writing in general.
|
||||
@@ -1,36 +0,0 @@
|
||||
tags:: #todoist-task [[PROJECTS/MOSAICO]]
|
||||
progress:: {{renderer :todomaster}}
|
||||
|
||||
- DONE Studiare [[@Regolamento per il conferimento di contratti di ricerca]]
|
||||
id:: 6839cd22-cd1c-4541-bea1-50c655611104
|
||||
:LOGBOOK:
|
||||
CLOCK: [2025-05-30 Fri 18:04:12]--[2025-05-30 Fri 18:04:13] => 00:00:01
|
||||
:END:
|
||||
- ((6839d240-e828-4ebd-861e-2f97e1adb987))
|
||||
- ### **Stima dei costi**
|
||||
|
||||
| Voce | Importo (€) |
|
||||
| ---- | ---- | ---- |
|
||||
| Compenso lordo ricercatore | 36.000,00 |
|
||||
| Oneri previdenziali e assistenziali a carico ente | 10.800,00 |
|
||||
| IRAP (8,5% stimato) | 3.200,00 |
|
||||
| **Totale annuo lordo omnicomprensivo** | **50.000,00** |
|
||||
- Due anni ((6839d6ee-b985-41b9-8edf-5180e3fd947c))
|
||||
- DONE Cercare bandi di contratti già banditi
|
||||
id:: 6839ce19-2f24-43d2-a1ab-b615a34bd92f
|
||||
:LOGBOOK:
|
||||
CLOCK: [2025-05-30 Fri 18:00:10]--[2025-05-30 Fri 18:00:11] => 00:00:01
|
||||
:END:
|
||||
- |PDF | Data | Oggetto|
|
||||
| | [[17-04-2025]] | Bando|
|
||||
| | [[28-04-2025]] | Ammissione candidati|
|
||||
| | [[28-04-2025]] | Nomina commissione dal Rettore su Delibera del MESVA|
|
||||
| | [[05-05-2025]] | Verbale preliminare|
|
||||
| | [[09/05/2025]] | Valutazione titoli|
|
||||
| | [[12-05-2025]] | Orale|
|
||||
| | [[13-05-2025]] | Approvazione atti e graduatoria|
|
||||
- TODO Vedere CFP di altri contratti di ricerca banditi da altre università
|
||||
- [All. 1_Decreto DG 140-2025_Bando 2_2025_Contratti di ricerca_1.1-signed.pdf](https://www.inrim.it/sites/default/files/2025-05/All.%201_Decreto%20DG%20140-2025_Bando%202_2025_Contratti%20di%20ricerca_1.1-signed.pdf)
|
||||
- Qui il compenso annuale loro e' di euro 38986.47
|
||||
- [Bando MUR PNRR - 4 CdR_EN.pdf](file:///C:/Users/david/Nextcloud/WIN/Downloads/Bando%20MUR%20PNRR%20-%204%20CdR_EN.pdf)
|
||||
- TODO Fare scouting
|
||||
@@ -1,27 +0,0 @@
|
||||
icon:: 🖥️
|
||||
progress:: {{renderer :todomaster}}
|
||||
title:: DESKTOP
|
||||
|
||||
- #+BEGIN_QUOTE
|
||||
⛅️ This [[page]] is just for flushing [[Notes]] about things that need to be done.
|
||||
#+END_QUOTE
|
||||
- {{embed [[Inbox]]}}
|
||||
- ## Ideas
|
||||
- {{query (or [[Ideas]] (property :tags [[Ideas]]))}}
|
||||
query-table:: true
|
||||
query-properties:: [:block :page]
|
||||
- ## AGENDA FOR TODAY
|
||||
collapsed:: true
|
||||
- {{renderer agenda, task-list}}
|
||||
- {{embed ((648f2e59-50c8-4173-9cc0-71512dead48d))}}
|
||||
- ## TODOs from this page
|
||||
query-sort-by:: priority
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
query-properties:: [:block :priority]
|
||||
- {{query (and (task DOING TODO) (or (page [[DESKTOP]]) [[Inbox]] ))}}
|
||||
- ## [[PAPERS]]
|
||||
- {{embed ((648b062b-c129-40a4-ace1-2364698a8736))}}
|
||||
-
|
||||
-
|
||||
-
|
||||
@@ -1,27 +0,0 @@
|
||||
icon:: 🖥️
|
||||
progress:: {{renderer :todomaster}}
|
||||
title:: DESKTOP
|
||||
|
||||
- #+BEGIN_QUOTE
|
||||
⛅️ This [[page]] is just for flushing [[Notes]] about things that need to be done.
|
||||
#+END_QUOTE
|
||||
- {{embed [[Inbox]]}}
|
||||
- ## Ideas
|
||||
- {{query (or [[Ideas]] (property :tags [[Ideas]]))}}
|
||||
query-table:: true
|
||||
query-properties:: [:block :page]
|
||||
- ## AGENDA FOR TODAY
|
||||
collapsed:: true
|
||||
- {{renderer agenda, task-list}}
|
||||
- {{embed ((648f2e59-50c8-4173-9cc0-71512dead48d))}}
|
||||
- ## TODOs from this page
|
||||
query-sort-by:: priority
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
query-properties:: [:block :priority]
|
||||
- {{query (and (task DOING TODO) (or (page [[DESKTOP]]) [[Inbox]] ))}}
|
||||
- ## [[PAPERS]]
|
||||
- {{embed ((648b062b-c129-40a4-ace1-2364698a8736))}}
|
||||
-
|
||||
-
|
||||
-
|
||||
@@ -1,20 +0,0 @@
|
||||
icon:: 🖥️
|
||||
progress:: {{renderer :todomaster}}
|
||||
title:: DESKTOP
|
||||
|
||||
- #+BEGIN_QUOTE
|
||||
⛅️ This page is just for flushing Notes about things that must be done.
|
||||
#+END_QUOTE
|
||||
- #.tabular
|
||||
- **Inbox**
|
||||
- {{embed [[Inbox]]}}
|
||||
- **[[REVIEWS]] DOING**
|
||||
- {{embed ((648f2e59-50c8-4173-9cc0-71512dead48d))}}
|
||||
- **[[PAPERS]]**
|
||||
- {{embed ((648b062b-c129-40a4-ace1-2364698a8736))}}
|
||||
- **Active [[PROJECTS]]**
|
||||
- {{embed ((65c8d46f-2067-4e99-9d92-e54d5f04180a))}}
|
||||
- **[[Ideas]]**
|
||||
- {{query (or [[Ideas]] (property :tags [[Ideas]]))}}
|
||||
query-table:: true
|
||||
query-properties:: [:block :page]
|
||||
@@ -1,90 +0,0 @@
|
||||
icon:: ✅
|
||||
|
||||
- ### [[2025/05]]
|
||||
- ✔️ [[May 26th, 2025]] *22:39* ((68341e4c-22c0-498c-8b18-bf3c03b3f7ea))
|
||||
- ✔️ [[26-05-2025]] *22:52* ((6673db98-f12a-4d48-b1ec-281082dfec1f))
|
||||
- ✔️ [[27-05-2025]] *16:18* ((6831929a-bb3a-4d1e-a0ab-5dd96aedb5a1))
|
||||
- ✔️ [[28-05-2025]] *09:22* ((68342adf-7c9d-4937-8d81-7ce37d084360))
|
||||
- ✔️ [[28-05-2025]] *09:23* ((6836208c-160c-483a-b6fe-939605fbb4fc))
|
||||
- ✔️ [[28-05-2025]] *12:40* ((683620bb-651c-44a0-8fd0-4e5e835a9090))
|
||||
- ✔️ [[28-05-2025]] *12:44* ((683620b6-4510-470b-90ef-d8ec1122471c))
|
||||
- ✔️ [[28-05-2025]] *12:44* ((683620b6-ca0a-4855-846c-952d9add8ef5))
|
||||
- ✔️ [[29-05-2025]] *12:57* ((68372640-5f76-4640-8b49-7d79dc1e8c7a))
|
||||
- ✔️ [[30-05-2025]] *11:19* ((683952a8-5c44-4441-8f3f-bbfb8797674f))
|
||||
- ✔️ [[30-05-2025]] *18:00* ((6839ce19-2f24-43d2-a1ab-b615a34bd92f))
|
||||
- ✔️ [[30-05-2025]] *18:04* ((6839cd22-cd1c-4541-bea1-50c655611104))
|
||||
- ✔️ [[30-05-2025]] *21:28* ((68362092-aafa-44b6-83b2-8f4a163dd2a0))
|
||||
- ✔️ [[10-05-2025]] *22:52* ((66ed695f-a60d-473d-8855-ec948f4a8bf8))
|
||||
- ✔️ [[10-05-2025]] *22:56* ((66ed6960-90a9-44e0-842f-61c071f4b607))
|
||||
- ✔️ [[10-05-2025]] *23:05* ((93b5aeab-7030-401b-b111-f27673af6d28))
|
||||
- ✔️ [[10-05-2025]] *23:06* ((681fbf91-62b7-49bc-bf11-aad4d56a6f83))
|
||||
- ✔️ [[10-05-2025]] *23:07* :LOGBOOK:
|
||||
CLOCK: [2025-05-10 Sat 23:07:09]--[2025-05-10 Sat 23:07:11] => 00:00:02
|
||||
:END:
|
||||
- ✔️ [[May 21st, 2025]] *09:04* ((65c8d43c-9e5e-455f-9c48-cb6d035417fc))
|
||||
- ✔️ [[May 24th, 2025]] *19:02* ((6831961e-c3a3-4890-99ae-ffda429333c8))
|
||||
- ✔️ [[May 24th, 2025]] *20:47* ((6659d0ed-b485-4423-9c75-a8f5d715b31f))
|
||||
- ✔️ [[May 24th, 2025]] *22:02* ((6832257a-63a4-4c89-8353-25f0e94caa51))
|
||||
- ✔️ [[May 24th, 2025]] *22:02* ((6832257a-4373-4560-a7e2-79fba9f4c9e6))
|
||||
- ✔️ [[May 24th, 2025]] *22:02* ((682ecc99-b356-4086-9ff8-4e4736018009))
|
||||
- ✔️ [[May 25th, 2025]] *15:49* ((66e80dfd-0f7c-4020-aa87-906662c9eebd))
|
||||
- ✔️ [[May 25th, 2025]] *19:26* ((6832257a-f98d-4f5e-850c-ddf8ffd0b5fb))
|
||||
- ✔️ [[May 25th, 2025]] *19:26* ((6832257a-85cb-46bd-9018-855f59070a41))
|
||||
- ✔️ [[May 25th, 2025]] *19:27* ((68331e69-7914-4696-8f2e-9ff4e9878686))
|
||||
- ✔️ [[May 25th, 2025]] *19:29* ((6832257a-7e7e-4ed8-abf8-dd88c6643863))
|
||||
- ✔️ [[May 25th, 2025]] *19:30* ((6832257a-cbb8-4881-ab20-bebcda629999))
|
||||
- ✔️ [[May 25th, 2025]] *19:31* ((6832257a-eea4-45f9-ab9f-98dbc36328cf))
|
||||
- ✔️ [[May 25th, 2025]] *22:49* ((65c8d46e-6599-4319-9683-4f86396c7e29))
|
||||
- ✔️ [[May 25th, 2025]] *22:49* ((65c8d45b-9775-4e19-88ed-c5d1895df182))
|
||||
- ✔️ [[May 26th, 2025]] *11:19* ((68342adf-8309-40bf-a38e-5dab74b7a5ea))
|
||||
- ✔️ [[May 26th, 2025]] *11:20* ((68342adf-0b33-4470-aae1-a3741a2d5432))
|
||||
- ✔️ [[May 26th, 2025]] *11:22* ((68342adf-7c9d-4937-8d81-7ce37d084360))
|
||||
- ✔️ [[May 26th, 2025]] *13:23* ((68342adf-daa1-480c-813c-48be1ba86b71))
|
||||
- ✔️ [[May 26th, 2025]] *13:31* ((68342adf-3362-4bb4-9082-f6050f8cf63c))
|
||||
- ✔️ [[May 26th, 2025]] *13:45* ((6834435e-3184-483a-a02c-271995950996))
|
||||
- ✔️ [[May 26th, 2025]] *13:45* ((6834435d-21d2-492c-aac2-21053aba25e1))
|
||||
- ✔️ [[May 26th, 2025]] *13:47* ((68342adf-d123-444d-b7a2-c4bedd4042dd))
|
||||
- ✔️ [[May 26th, 2025]] *14:11* ((68342adf-ecdc-4812-ad4f-d5240a2d5fa9))
|
||||
- ✔️ [[May 26th, 2025]] *15:19* ((68344d8e-d83d-4c7c-b4aa-56ad71f53ddf))
|
||||
- ✔️ [[May 26th, 2025]] *20:22* ((683481be-df12-4c94-a56b-fbf9712c96e4))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((6831933e-7f38-436a-91f0-abf1292e15a2))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((68319354-327c-48d4-a6f8-47c04409e98a))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((68331a74-24ed-48d3-9a7f-df9101d3ef5f))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((683481c8-e3cd-462a-8a93-4d19b7e3db3e))
|
||||
- ✔️ [[May 26th, 2025]] *22:11* ((6831991d-62c9-4091-b3e9-af451051d642))
|
||||
- ✔️ [[May 26th, 2025]] *22:16* ((65c8d477-cade-4b0b-a8b4-2756a6b98e6e))
|
||||
- ✔️ [[May 26th, 2025]] *22:16* ((65c8d477-2c6c-4548-9e72-09cee84bec35))
|
||||
- ✔️ [[May 26th, 2025]] *22:17* ((65c8d455-6e80-4f1e-b650-813a243b696c))
|
||||
- ✔️ [[May 26th, 2025]] *22:18* ((65f2aaa6-64f6-42e8-8b2c-2a22f8538b30))
|
||||
- ✔️ [[May 26th, 2025]] *22:18* ((65f2aaa6-690e-4bdc-962a-7c0ddf212f11))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((668e3747-dff2-4f1a-84b2-1d75cbd83aa1))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((668e3747-62ba-4218-8d0e-57effaa7f795))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((6673db54-3eb8-48ba-a840-cbe1ba29b2ff))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((6673db1d-f835-4eb5-9182-9e4a56a85e18))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((6673db98-f12a-4d48-b1ec-281082dfec1f))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((666d40df-e520-45bc-be26-dd4af89767e5))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((65d89628-a424-4291-ad37-c95ed68c7fdd))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c9f0a4-861b-4f8e-9738-9e19488e259d))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43b-046c-4682-a958-a14787d04e22))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43c-3e62-4a44-aaf8-ad1f7b0e15c4))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43c-b2de-4ad6-9282-e2d67a0cb6b9))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43d-0487-4c5e-a8ae-cae113812690))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43d-09c9-416b-a127-a865e0fd3b08))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43d-2358-46ad-acf0-3396607b2ace))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((660178c2-5901-423e-976a-dba8a52916c5))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65d8963d-149e-44b2-a70d-9cee907047ad))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c8d477-b5c3-45c1-986d-9daf3563a1d1))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65d8963d-5b6c-48da-bd21-21e3ffe41570))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c8d45b-545c-4ca4-acc3-b35ef663757f))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c8d45b-3974-4a0e-ac6e-7dbc798340ab))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c35633-d1fd-4840-a6bc-ee79a2db5ffa))
|
||||
- ✔️ [[May 26th, 2025]] *22:22* ((65c8d45b-1a21-40d2-9003-5b9c13d08e01))
|
||||
- ✔️ [[May 26th, 2025]] *22:22* ((65d8963d-f00b-44a0-97c3-10f5510ab44e))
|
||||
- ✔️ [[May 26th, 2025]] *22:22* ((683432dd-8909-4466-b7ec-c4861aaf2fe0))
|
||||
- ✔️ [[May 26th, 2025]] *22:23* ((65c8d46f-f70f-4d0f-9fce-14c2ab11ab68))
|
||||
- ✔️ [[May 26th, 2025]] *22:23* Coprire anche aspetti di collaborative modeling
|
||||
- ### [[2025/06]]
|
||||
- ✔️ [[02-06-2025]] *23:42* ((6836208c-cf9d-4d40-9f87-db1045f739e1))
|
||||
- ✔️ [[03-06-2025]] *16:05* ((683f0108-c7ac-41ae-a6bd-b9c02829e6fc))
|
||||
- ✔️ [[03-06-2025]] *16:07* ((683ee6f2-7304-4ea7-8000-46b4106b3ef5))
|
||||
- ✔️ [[03-06-2025]] *21:54* ((683620b6-dd45-402c-80d5-0eb8facf914d))
|
||||
@@ -1,91 +0,0 @@
|
||||
icon:: ✅
|
||||
|
||||
- ### [[2025/05]]
|
||||
- ✔️ [[May 26th, 2025]] *22:39* ((68341e4c-22c0-498c-8b18-bf3c03b3f7ea))
|
||||
- ✔️ [[26-05-2025]] *22:52* ((6673db98-f12a-4d48-b1ec-281082dfec1f))
|
||||
- ✔️ [[27-05-2025]] *16:18* ((6831929a-bb3a-4d1e-a0ab-5dd96aedb5a1))
|
||||
- ✔️ [[28-05-2025]] *09:22* ((68342adf-7c9d-4937-8d81-7ce37d084360))
|
||||
- ✔️ [[28-05-2025]] *09:23* ((6836208c-160c-483a-b6fe-939605fbb4fc))
|
||||
- ✔️ [[28-05-2025]] *12:40* ((683620bb-651c-44a0-8fd0-4e5e835a9090))
|
||||
- ✔️ [[28-05-2025]] *12:44* ((683620b6-4510-470b-90ef-d8ec1122471c))
|
||||
- ✔️ [[28-05-2025]] *12:44* ((683620b6-ca0a-4855-846c-952d9add8ef5))
|
||||
- ✔️ [[29-05-2025]] *12:57* ((68372640-5f76-4640-8b49-7d79dc1e8c7a))
|
||||
- ✔️ [[30-05-2025]] *11:19* ((683952a8-5c44-4441-8f3f-bbfb8797674f))
|
||||
- ✔️ [[30-05-2025]] *18:00* ((6839ce19-2f24-43d2-a1ab-b615a34bd92f))
|
||||
- ✔️ [[30-05-2025]] *18:04* ((6839cd22-cd1c-4541-bea1-50c655611104))
|
||||
- ✔️ [[30-05-2025]] *21:28* ((68362092-aafa-44b6-83b2-8f4a163dd2a0))
|
||||
- ✔️ [[10-05-2025]] *22:52* ((66ed695f-a60d-473d-8855-ec948f4a8bf8))
|
||||
- ✔️ [[10-05-2025]] *22:56* ((66ed6960-90a9-44e0-842f-61c071f4b607))
|
||||
- ✔️ [[10-05-2025]] *23:05* ((93b5aeab-7030-401b-b111-f27673af6d28))
|
||||
- ✔️ [[10-05-2025]] *23:06* ((681fbf91-62b7-49bc-bf11-aad4d56a6f83))
|
||||
- ✔️ [[10-05-2025]] *23:07* :LOGBOOK:
|
||||
CLOCK: [2025-05-10 Sat 23:07:09]--[2025-05-10 Sat 23:07:11] => 00:00:02
|
||||
:END:
|
||||
- ✔️ [[May 21st, 2025]] *09:04* ((65c8d43c-9e5e-455f-9c48-cb6d035417fc))
|
||||
- ✔️ [[May 24th, 2025]] *19:02* ((6831961e-c3a3-4890-99ae-ffda429333c8))
|
||||
- ✔️ [[May 24th, 2025]] *20:47* ((6659d0ed-b485-4423-9c75-a8f5d715b31f))
|
||||
- ✔️ [[May 24th, 2025]] *22:02* ((6832257a-63a4-4c89-8353-25f0e94caa51))
|
||||
- ✔️ [[May 24th, 2025]] *22:02* ((6832257a-4373-4560-a7e2-79fba9f4c9e6))
|
||||
- ✔️ [[May 24th, 2025]] *22:02* ((682ecc99-b356-4086-9ff8-4e4736018009))
|
||||
- ✔️ [[May 25th, 2025]] *15:49* ((66e80dfd-0f7c-4020-aa87-906662c9eebd))
|
||||
- ✔️ [[May 25th, 2025]] *19:26* ((6832257a-f98d-4f5e-850c-ddf8ffd0b5fb))
|
||||
- ✔️ [[May 25th, 2025]] *19:26* ((6832257a-85cb-46bd-9018-855f59070a41))
|
||||
- ✔️ [[May 25th, 2025]] *19:27* ((68331e69-7914-4696-8f2e-9ff4e9878686))
|
||||
- ✔️ [[May 25th, 2025]] *19:29* ((6832257a-7e7e-4ed8-abf8-dd88c6643863))
|
||||
- ✔️ [[May 25th, 2025]] *19:30* ((6832257a-cbb8-4881-ab20-bebcda629999))
|
||||
- ✔️ [[May 25th, 2025]] *19:31* ((6832257a-eea4-45f9-ab9f-98dbc36328cf))
|
||||
- ✔️ [[May 25th, 2025]] *22:49* ((65c8d46e-6599-4319-9683-4f86396c7e29))
|
||||
- ✔️ [[May 25th, 2025]] *22:49* ((65c8d45b-9775-4e19-88ed-c5d1895df182))
|
||||
- ✔️ [[May 26th, 2025]] *11:19* ((68342adf-8309-40bf-a38e-5dab74b7a5ea))
|
||||
- ✔️ [[May 26th, 2025]] *11:20* ((68342adf-0b33-4470-aae1-a3741a2d5432))
|
||||
- ✔️ [[May 26th, 2025]] *11:22* ((68342adf-7c9d-4937-8d81-7ce37d084360))
|
||||
- ✔️ [[May 26th, 2025]] *13:23* ((68342adf-daa1-480c-813c-48be1ba86b71))
|
||||
- ✔️ [[May 26th, 2025]] *13:31* ((68342adf-3362-4bb4-9082-f6050f8cf63c))
|
||||
- ✔️ [[May 26th, 2025]] *13:45* ((6834435e-3184-483a-a02c-271995950996))
|
||||
- ✔️ [[May 26th, 2025]] *13:45* ((6834435d-21d2-492c-aac2-21053aba25e1))
|
||||
- ✔️ [[May 26th, 2025]] *13:47* ((68342adf-d123-444d-b7a2-c4bedd4042dd))
|
||||
- ✔️ [[May 26th, 2025]] *14:11* ((68342adf-ecdc-4812-ad4f-d5240a2d5fa9))
|
||||
- ✔️ [[May 26th, 2025]] *15:19* ((68344d8e-d83d-4c7c-b4aa-56ad71f53ddf))
|
||||
- ✔️ [[May 26th, 2025]] *20:22* ((683481be-df12-4c94-a56b-fbf9712c96e4))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((6831933e-7f38-436a-91f0-abf1292e15a2))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((68319354-327c-48d4-a6f8-47c04409e98a))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((68331a74-24ed-48d3-9a7f-df9101d3ef5f))
|
||||
- ✔️ [[May 26th, 2025]] *21:58* ((683481c8-e3cd-462a-8a93-4d19b7e3db3e))
|
||||
- ✔️ [[May 26th, 2025]] *22:11* ((6831991d-62c9-4091-b3e9-af451051d642))
|
||||
- ✔️ [[May 26th, 2025]] *22:16* ((65c8d477-cade-4b0b-a8b4-2756a6b98e6e))
|
||||
- ✔️ [[May 26th, 2025]] *22:16* ((65c8d477-2c6c-4548-9e72-09cee84bec35))
|
||||
- ✔️ [[May 26th, 2025]] *22:17* ((65c8d455-6e80-4f1e-b650-813a243b696c))
|
||||
- ✔️ [[May 26th, 2025]] *22:18* ((65f2aaa6-64f6-42e8-8b2c-2a22f8538b30))
|
||||
- ✔️ [[May 26th, 2025]] *22:18* ((65f2aaa6-690e-4bdc-962a-7c0ddf212f11))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((668e3747-dff2-4f1a-84b2-1d75cbd83aa1))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((668e3747-62ba-4218-8d0e-57effaa7f795))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((6673db54-3eb8-48ba-a840-cbe1ba29b2ff))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((6673db1d-f835-4eb5-9182-9e4a56a85e18))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((6673db98-f12a-4d48-b1ec-281082dfec1f))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((666d40df-e520-45bc-be26-dd4af89767e5))
|
||||
- ✔️ [[May 26th, 2025]] *22:19* ((65d89628-a424-4291-ad37-c95ed68c7fdd))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c9f0a4-861b-4f8e-9738-9e19488e259d))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43b-046c-4682-a958-a14787d04e22))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43c-3e62-4a44-aaf8-ad1f7b0e15c4))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43c-b2de-4ad6-9282-e2d67a0cb6b9))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43d-0487-4c5e-a8ae-cae113812690))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43d-09c9-416b-a127-a865e0fd3b08))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((65c8d43d-2358-46ad-acf0-3396607b2ace))
|
||||
- ✔️ [[May 26th, 2025]] *22:20* ((660178c2-5901-423e-976a-dba8a52916c5))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65d8963d-149e-44b2-a70d-9cee907047ad))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c8d477-b5c3-45c1-986d-9daf3563a1d1))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65d8963d-5b6c-48da-bd21-21e3ffe41570))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c8d45b-545c-4ca4-acc3-b35ef663757f))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c8d45b-3974-4a0e-ac6e-7dbc798340ab))
|
||||
- ✔️ [[May 26th, 2025]] *22:21* ((65c35633-d1fd-4840-a6bc-ee79a2db5ffa))
|
||||
- ✔️ [[May 26th, 2025]] *22:22* ((65c8d45b-1a21-40d2-9003-5b9c13d08e01))
|
||||
- ✔️ [[May 26th, 2025]] *22:22* ((65d8963d-f00b-44a0-97c3-10f5510ab44e))
|
||||
- ✔️ [[May 26th, 2025]] *22:22* ((683432dd-8909-4466-b7ec-c4861aaf2fe0))
|
||||
- ✔️ [[May 26th, 2025]] *22:23* ((65c8d46f-f70f-4d0f-9fce-14c2ab11ab68))
|
||||
- ✔️ [[May 26th, 2025]] *22:23* Coprire anche aspetti di collaborative modeling
|
||||
- ### [[2025/06]]
|
||||
- ✔️ [[02-06-2025]] *23:42* ((6836208c-cf9d-4d40-9f87-db1045f739e1))
|
||||
- ✔️ [[03-06-2025]] *16:05* ((683f0108-c7ac-41ae-a6bd-b9c02829e6fc))
|
||||
- ✔️ [[03-06-2025]] *16:07* ((683ee6f2-7304-4ea7-8000-46b4106b3ef5))
|
||||
- ✔️ [[03-06-2025]] *21:54* ((683620b6-dd45-402c-80d5-0eb8facf914d))
|
||||
- ✔️ [[04-06-2025]] *11:29* ((5b54cf10-4738-44a1-b930-fcff797d0b75))
|
||||
@@ -1,6 +0,0 @@
|
||||
- [[people/ValerioCrescia]]
|
||||
titolo-tesi:: A LiveSycn extension to integrate an event-driven architecture in Apache Syncope
|
||||
struttura:: [[company/Tirasa]]
|
||||
deadline-titolo:: [[18-01-2023]]
|
||||
deadline-tesi:: [[02-03-2023]]
|
||||
-
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
tags:: #meeting
|
||||
date:: 2021-01-22
|
||||
time:: 10:46
|
||||
people:: #people/alfonso #people/apurv
|
||||
|
||||
- Presentation of the SOSYM paper about about BPMN vs Low-code
|
||||
- Problem with section 5.4 concerning the usability
|
||||
- We decided to model a workflow in BPMN and then use this as a reference workflow to show the characteristics of all the analyzed LCDPs
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
tags:: #meeting
|
||||
date:: 2021-01-22
|
||||
time:: 10:46
|
||||
people:: #people/alfonso #people/apurv
|
||||
|
||||
- Presentation of the SOSYM paper about about BPMN vs Low-code
|
||||
- Problem with section 5.4 concerning the usability
|
||||
- We decided to model a workflow in BPMN and then use this as a reference workflow to show the characteristics of all the analyzed LCDPs
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
tags:: #meeting
|
||||
date:: 2021-01-22
|
||||
time:: 10:46
|
||||
people:: #people/alfonso #people/apurv
|
||||
|
||||
- Presentation of the SOSYM paper about about BPMN vs Low-code
|
||||
- Problem with section 5.4 concerning the usability
|
||||
- We decided to model a workflow in BPMN and then use this as a reference workflow to show the characteristics of all the analyzed LCDPs
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
tags:: #meeting
|
||||
date:: 2021-01-22
|
||||
time:: 10:46
|
||||
people:: #people/alfonso #people/apurv
|
||||
|
||||
- Presentation of the SOSYM paper about about BPMN vs Low-code
|
||||
- Problem with section 5.4 concerning the usability
|
||||
- We decided to model a workflow in BPMN and then use this as a reference workflow to show the characteristics of all the analyzed LCDPs
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
type:: #meeting
|
||||
date:: 2021-01-22
|
||||
time:: 10:46
|
||||
people:: #people/alfonso #people/apurv
|
||||
|
||||
- Presentation of the SOSYM paper about about BPMN vs Low-code
|
||||
- Problem with section 5.4 concerning the usability
|
||||
- We decided to model a workflow in BPMN and then use this as a reference workflow to show the characteristics of all the analyzed LCDPs
|
||||
@@ -1,37 +0,0 @@
|
||||
icon:: ⤴️
|
||||
|
||||
- ## ⭐️STARRED ITEMS
|
||||
- query-sort-by:: page
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
collapsed:: true
|
||||
#+BEGIN_QUERY
|
||||
{:title "NOTES"
|
||||
:query
|
||||
[:find (pull ?b [*] )
|
||||
:where
|
||||
[?b :block/page ?p]
|
||||
[?p :block/name ?p-name]
|
||||
[?b :block/content ?c]
|
||||
[(clojure.string/includes? ?c "#STAR")]
|
||||
[(clojure.string/includes? ?p-name "omnivore")]
|
||||
]
|
||||
:collapsed? true}
|
||||
#+END_QUERY
|
||||
- ARTICLES
|
||||
- {{query (and (property source "Omnivore") [[STAR]])}}
|
||||
query-table:: true
|
||||
query-properties:: [:block :site :labels :author]
|
||||
- ## DA LEGGERE 🔎
|
||||
query-table:: true
|
||||
- {{query (and (property source "Omnivore") (not (property :is-archived "10")) (not (page [[Highlights]])))}}
|
||||
query-sort-by:: date-saved
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
query-properties:: [:block :labels :site :date-saved :author]
|
||||
- ## ARCHIVED 📓
|
||||
- {{query (and [[Omnivore]] (property :is-archived "10")) }}
|
||||
query-table:: true
|
||||
query-properties:: [:block :site :labels :date-published :date-archived :author]
|
||||
query-sort-by:: date-archived
|
||||
query-sort-desc:: false
|
||||
-11
@@ -1,11 +0,0 @@
|
||||
## 🔖 Articles
|
||||
- [Generative AI: A new Gold Rush for software engineering innovation | VentureBeat](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215)
|
||||
collapsed:: true
|
||||
site:: [VentureBeat](https://venturebeat.com/ai/generative-ai-a-new-gold-rush-for-software-engineering-innovation)
|
||||
author:: Ashish Kakran, Thomvest Ventures
|
||||
labels:: [[P1]] [[generativeAI]]
|
||||
date-saved:: [[14-08-2023]]
|
||||
date-published:: [[06-08-2023]]
|
||||
date-archived:: [[]]
|
||||
is-archived::
|
||||
source:: [[Omnivore]]
|
||||
-59
@@ -1,59 +0,0 @@
|
||||
type:: [[journalPaper]]
|
||||
external-sources::
|
||||
todoist:: https://todoist.com/showTask?id=6509420504
|
||||
year:: 2023
|
||||
status:: [[DOING]]
|
||||
venue:: [[SOSYM]]
|
||||
priority:: [[P1]]
|
||||
|
||||
- Bisogna descrivere un processo tipico di benchmarking.
|
||||
- A tale scopo bisogna guardare [microsoft/CodeXGLUE: CodeXGLUE (github.com)](https://github.com/microsoft/CodeXGLUE)
|
||||
- microsoft/CodeXGLUE: CodeXGLUEmicrosoft/CodeXGLUE: CodeXGLUE - https://github.com/microsoft/CodeXGLUE -
|
||||
- 23.9 million professional developers in 2019, and the population is expected to reach 28.7 million in 2024
|
||||
- Microsoft offers the most complete toolchain for developers, bringing together the best of GitHub, Visual Studio, and Microsoft Azure to help developers to go from idea to code and code to cloud.
|
||||
- **Recent years have seen a surge of applying of statistical models, including neural nets, to code intelligence tasks**
|
||||
- However, the area of code intelligence lacks a benchmark suite that covers a wide range of tasks.
|
||||
- **CodeXGLUE, a benchmark dataset and open challenge for code intelligence.**
|
||||
- collection of code intelligence tasks and a platform for model evaluation and comparison.
|
||||
-
|
||||
- The questions / points to elaborate are as follows:
|
||||
- the need of benchmarking when applying ML tools when automating some process
|
||||
- how typical benchmarking processes look like
|
||||
- what are the issues when benchmarking ML tools
|
||||
-
|
||||
- Initial draft on notes:
|
||||
% Benchmarking ML Tools: Why and How
|
||||
- Machine learning (ML) is a rapidly evolving field that offers many benefits for various domains and applications. However, choosing the right ML tool for a specific task can be challenging, as there are many factors to consider, such as data capacity, training speed, inference speed, and model precision. Therefore, benchmarking ML tools is a crucial step to evaluate their performance and suitability for different scenarios.
|
||||
- Benchmarking is the practice of comparing tools based on some key performance indicators (KPIs) that reflect their strengths and weaknesses. Benchmarking can help users make informed decisions about which tool to use, as well as identify areas for improvement and optimization. However, benchmarking ML tools is not a straightforward process, as it involves many steps and challenges.
|
||||
|
||||
In this blog post, we will elaborate on:
|
||||
- The need of benchmarking when applying ML tools when automating some process
|
||||
- How typical benchmarking processes look like
|
||||
- What are the issues when benchmarking ML tools
|
||||
|
||||
The need of benchmarking when applying ML tools when automating some process
|
||||
|
||||
ML tools are often used to automate some process that involves data analysis, prediction, or classification. For example, ML tools can be used to automate image recognition, sentiment analysis, fraud detection, or recommendation systems. However, not all ML tools are equally effective or efficient for these tasks. Some tools may have higher accuracy, but lower speed; some tools may handle large datasets better than others; some tools may have more features or functionalities than others.
|
||||
|
||||
Therefore, benchmarking ML tools is necessary to measure their performance and compare them against each other or against some baseline. Benchmarking can help users select the best tool for their specific needs and goals, as well as optimize their workflow and resource allocation. Benchmarking can also help developers improve their tools by identifying bottlenecks and gaps in performance.
|
||||
|
||||
How typical benchmarking processes look like
|
||||
|
||||
A typical benchmarking process consists of the following steps:
|
||||
- Define the ==objective and scope of the benchmarking==. What is the purpose of the benchmarking? What are the criteria and metrics to evaluate the performance? What are the tools to compare?
|
||||
- Choose a ==reference dataset and a reference model==. The dataset should be relevant and representative of the task at hand. The model should be appropriate and consistent for the chosen tools.
|
||||
- Choose a ==reference computer and a reference training strategy==. The computer should have sufficient hardware and software specifications to run the tools. The training strategy should include parameters such as loss function, optimization algorithm, and stopping criterion.
|
||||
- Run the tools on the dataset using the model and the training strategy. ==Record the results== and metrics for each tool.
|
||||
- ==Analyze and compare the results==. Use visualizations and statistics to summarize and interpret the results. Identify the strengths and weaknesses of each tool.
|
||||
-
|
||||
- What are the issues when benchmarking ML tools
|
||||
- Benchmarking ML tools is not without challenges. Some of the common issues are:
|
||||
- The ==lack of standardization and reproducibility==. Different tools may have different implementations, configurations, or versions that affect their performance. Moreover, different datasets, models, or training strategies may also introduce variability and inconsistency in the results. Therefore, it is important to ensure that the benchmarking is fair and reliable by using standardized and reproducible methods.
|
||||
- The ==trade-off between complexity and simplicity==. Some tools may have more features or functionalities than others, which can make them more powerful or flexible, but also more complex or difficult to use. On the other hand, some tools may be simpler or easier to use, but also more limited or constrained in their capabilities. Therefore, it is important to balance between complexity and simplicity when choosing or evaluating a tool.
|
||||
- The ==trade-off between accuracy and efficiency==. Some tools may have higher accuracy or precision than others, but also lower speed or scalability. On the other hand, some tools may be faster or more scalable than others, but also less accurate or precise. Therefore, it is important to balance between accuracy and efficiency when choosing or evaluating a tool.
|
||||
- Conclusion
|
||||
- Benchmarking ML tools is an essential step to assess their performance and suitability for different tasks and applications. However, benchmarking ML tools is not a simple process, as it involves many steps and challenges. In this blog post, we have elaborated on why benchmarking is needed when applying ML tools when automating some process; how typical benchmarking processes look like; and what are the issues when benchmarking ML tools.
|
||||
- [[RelatedWork]]
|
||||
- [[@Benchmarking Machine Learning Solutions in Production]]
|
||||
- [[@PMLB: a large benchmark suite for machine learning evaluation and comparison]]
|
||||
-
|
||||
-59
@@ -1,59 +0,0 @@
|
||||
type:: [[journalPaper]]
|
||||
external-sources::
|
||||
todoist:: https://todoist.com/showTask?id=6509420504
|
||||
year:: 2023
|
||||
status:: [[DOING]]
|
||||
venue:: [[SOSYM]]
|
||||
priority:: [[P1]]
|
||||
|
||||
- Bisogna descrivere un processo tipico di benchmarking.
|
||||
- A tale scopo bisogna guardare [microsoft/CodeXGLUE: CodeXGLUE (github.com)](https://github.com/microsoft/CodeXGLUE)
|
||||
- microsoft/CodeXGLUE: CodeXGLUEmicrosoft/CodeXGLUE: CodeXGLUE - https://github.com/microsoft/CodeXGLUE -
|
||||
- 23.9 million professional developers in 2019, and the population is expected to reach 28.7 million in 2024
|
||||
- Microsoft offers the most complete toolchain for developers, bringing together the best of GitHub, Visual Studio, and Microsoft Azure to help developers to go from idea to code and code to cloud.
|
||||
- **Recent years have seen a surge of applying of statistical models, including neural nets, to code intelligence tasks**
|
||||
- However, the area of code intelligence lacks a benchmark suite that covers a wide range of tasks.
|
||||
- **CodeXGLUE, a benchmark dataset and open challenge for code intelligence.**
|
||||
- collection of code intelligence tasks and a platform for model evaluation and comparison.
|
||||
-
|
||||
- The questions / points to elaborate are as follows:
|
||||
- the need of benchmarking when applying ML tools when automating some process
|
||||
- how typical benchmarking processes look like
|
||||
- what are the issues when benchmarking ML tools
|
||||
-
|
||||
- Initial draft on notes:
|
||||
% Benchmarking ML Tools: Why and How
|
||||
- Machine learning (ML) is a rapidly evolving field that offers many benefits for various domains and applications. However, choosing the right ML tool for a specific task can be challenging, as there are many factors to consider, such as data capacity, training speed, inference speed, and model precision. Therefore, benchmarking ML tools is a crucial step to evaluate their performance and suitability for different scenarios.
|
||||
- Benchmarking is the practice of comparing tools based on some key performance indicators (KPIs) that reflect their strengths and weaknesses. Benchmarking can help users make informed decisions about which tool to use, as well as identify areas for improvement and optimization. However, benchmarking ML tools is not a straightforward process, as it involves many steps and challenges.
|
||||
|
||||
In this blog post, we will elaborate on:
|
||||
- The need of benchmarking when applying ML tools when automating some process
|
||||
- How typical benchmarking processes look like
|
||||
- What are the issues when benchmarking ML tools
|
||||
|
||||
The need of benchmarking when applying ML tools when automating some process
|
||||
|
||||
ML tools are often used to automate some process that involves data analysis, prediction, or classification. For example, ML tools can be used to automate image recognition, sentiment analysis, fraud detection, or recommendation systems. However, not all ML tools are equally effective or efficient for these tasks. Some tools may have higher accuracy, but lower speed; some tools may handle large datasets better than others; some tools may have more features or functionalities than others.
|
||||
|
||||
Therefore, benchmarking ML tools is necessary to measure their performance and compare them against each other or against some baseline. Benchmarking can help users select the best tool for their specific needs and goals, as well as optimize their workflow and resource allocation. Benchmarking can also help developers improve their tools by identifying bottlenecks and gaps in performance.
|
||||
|
||||
How typical benchmarking processes look like
|
||||
|
||||
A typical benchmarking process consists of the following steps:
|
||||
- Define the ==objective and scope of the benchmarking==. What is the purpose of the benchmarking? What are the criteria and metrics to evaluate the performance? What are the tools to compare?
|
||||
- Choose a ==reference dataset and a reference model==. The dataset should be relevant and representative of the task at hand. The model should be appropriate and consistent for the chosen tools.
|
||||
- Choose a ==reference computer and a reference training strategy==. The computer should have sufficient hardware and software specifications to run the tools. The training strategy should include parameters such as loss function, optimization algorithm, and stopping criterion.
|
||||
- Run the tools on the dataset using the model and the training strategy. ==Record the results== and metrics for each tool.
|
||||
- ==Analyze and compare the results==. Use visualizations and statistics to summarize and interpret the results. Identify the strengths and weaknesses of each tool.
|
||||
-
|
||||
- What are the issues when benchmarking ML tools
|
||||
- Benchmarking ML tools is not without challenges. Some of the common issues are:
|
||||
- The ==lack of standardization and reproducibility==. Different tools may have different implementations, configurations, or versions that affect their performance. Moreover, different datasets, models, or training strategies may also introduce variability and inconsistency in the results. Therefore, it is important to ensure that the benchmarking is fair and reliable by using standardized and reproducible methods.
|
||||
- The ==trade-off between complexity and simplicity==. Some tools may have more features or functionalities than others, which can make them more powerful or flexible, but also more complex or difficult to use. On the other hand, some tools may be simpler or easier to use, but also more limited or constrained in their capabilities. Therefore, it is important to balance between complexity and simplicity when choosing or evaluating a tool.
|
||||
- The ==trade-off between accuracy and efficiency==. Some tools may have higher accuracy or precision than others, but also lower speed or scalability. On the other hand, some tools may be faster or more scalable than others, but also less accurate or precise. Therefore, it is important to balance between accuracy and efficiency when choosing or evaluating a tool.
|
||||
- Conclusion
|
||||
- Benchmarking ML tools is an essential step to assess their performance and suitability for different tasks and applications. However, benchmarking ML tools is not a simple process, as it involves many steps and challenges. In this blog post, we have elaborated on why benchmarking is needed when applying ML tools when automating some process; how typical benchmarking processes look like; and what are the issues when benchmarking ML tools.
|
||||
- [[RelatedWork]]
|
||||
- [[@Benchmarking Machine Learning Solutions in Production]]
|
||||
- [[@PMLB: a large benchmark suite for machine learning evaluation and comparison]]
|
||||
-
|
||||
-97
@@ -1,97 +0,0 @@
|
||||
type:: [[journalPaper]]
|
||||
external-sources::
|
||||
todoist:: https://todoist.com/showTask?id=6509420504
|
||||
year:: 2023
|
||||
deadline:: [[12-05-2023]]
|
||||
status:: [[DOING]]
|
||||
venue:: [[SOSYM]]
|
||||
priority:: [[P1]]
|
||||
|
||||
- ## TODOs
|
||||
- DONE Vedere sezione 3
|
||||
completed:: [[09-05-2023]]
|
||||
- DONE Finalizzare descizione architettura
|
||||
completed:: [[11-05-2023]]
|
||||
- DONE GUardare lo spreadsheet di Jesus
|
||||
completed:: [[11-05-2023]]
|
||||
- Finalizzare fig 3
|
||||
- DONE Rivedere parte iniziale sez 4
|
||||
completed:: [[09-05-2023]]
|
||||
- DONE Scrivere Conclusioni
|
||||
completed:: [[09-05-2023]]
|
||||
- [[10-05-2023]]
|
||||
- DONE Rivedere Intro
|
||||
completed:: [[10-05-2023]]
|
||||
- DONE Scrivere [[Abstract]]
|
||||
completed:: [[10-05-2023]]
|
||||
- [[12-05-2023]]
|
||||
- DONE Rivedere sezione 5
|
||||
completed:: [[12-05-2023]]
|
||||
- DONE [[people/riccardo]] rivede la sezione related [[WORK]]
|
||||
completed:: [[12-05-2023]]
|
||||
- DONE Rivedere sezione 3
|
||||
completed:: [[12-05-2023]]
|
||||
- TODO Lettura completa
|
||||
- DONE Fare figura componenti da inserire in sezione 3
|
||||
completed:: [[02-05-2023]]
|
||||
- DONE Rivedere parte scritta da Riccardo
|
||||
completed:: [[02-05-2023]]
|
||||
- DONE Listare challenges a fine sezione [[2]]
|
||||
completed:: [[02-05-2023]]
|
||||
-
|
||||
- [[Ideas]]
|
||||
- We could propose a tool demo [[paper]] at MODELS
|
||||
- [MODELS 2023 - Tools and Demonstrations - MODELS 2023 (researchr.org)](https://conf.researchr.org/track/models-2023/models-2023-tools-and-demonstrations)
|
||||
- We could even organize an informal hackathon to extend the catalogue
|
||||
-
|
||||
- Bisogna descrivere un processo tipico di benchmarking.
|
||||
- A tale scopo bisogna guardare [microsoft/CodeXGLUE: CodeXGLUE (github.com)](https://github.com/microsoft/CodeXGLUE)
|
||||
- microsoft/CodeXGLUE: CodeXGLUEmicrosoft/CodeXGLUE: CodeXGLUE - https://github.com/microsoft/CodeXGLUE -
|
||||
- 23.9 million professional developers in 2019, and the population is expected to reach 28.7 million in 2024
|
||||
- Microsoft offers the most complete toolchain for developers, bringing together the best of GitHub, Visual Studio, and Microsoft Azure to help developers to go from idea to code and code to cloud.
|
||||
- **Recent years have seen a surge of applying of statistical models, including neural nets, to code intelligence tasks**
|
||||
- However, the area of code intelligence lacks a benchmark suite that covers a wide range of tasks.
|
||||
- **CodeXGLUE, a benchmark dataset and open challenge for code intelligence.**
|
||||
- collection of code intelligence tasks and a platform for model evaluation and comparison.
|
||||
-
|
||||
- The questions / points to elaborate are as follows:
|
||||
- the need of benchmarking when applying ML tools when automating some process
|
||||
- how typical benchmarking processes look like
|
||||
- what are the issues when benchmarking ML tools
|
||||
-
|
||||
- Initial draft on notes:
|
||||
% Benchmarking ML Tools: Why and How
|
||||
- Machine learning (ML) is a rapidly evolving field that offers many benefits for various domains and applications. However, choosing the right ML tool for a specific task can be challenging, as there are many factors to consider, such as data capacity, training speed, inference speed, and model precision. Therefore, benchmarking ML tools is a crucial step to evaluate their performance and suitability for different scenarios.
|
||||
- Benchmarking is the practice of comparing tools based on some key performance indicators (KPIs) that reflect their strengths and weaknesses. Benchmarking can help users make informed decisions about which tool to use, as well as identify areas for improvement and optimization. However, benchmarking ML tools is not a straightforward process, as it involves many steps and challenges.
|
||||
|
||||
In this blog post, we will elaborate on:
|
||||
- The need of benchmarking when applying ML tools when automating some process
|
||||
- How typical benchmarking processes look like
|
||||
- What are the issues when benchmarking ML tools
|
||||
|
||||
The need of benchmarking when applying ML tools when automating some process
|
||||
|
||||
ML tools are often used to automate some process that involves data analysis, prediction, or classification. For example, ML tools can be used to automate image recognition, sentiment analysis, fraud detection, or recommendation systems. However, not all ML tools are equally effective or efficient for these tasks. Some tools may have higher accuracy, but lower speed; some tools may handle large datasets better than others; some tools may have more features or functionalities than others.
|
||||
|
||||
Therefore, benchmarking ML tools is necessary to measure their performance and compare them against each other or against some baseline. Benchmarking can help users select the best tool for their specific needs and goals, as well as optimize their workflow and resource allocation. Benchmarking can also help developers improve their tools by identifying bottlenecks and gaps in performance.
|
||||
|
||||
How typical benchmarking processes look like
|
||||
|
||||
A typical benchmarking process consists of the following steps:
|
||||
- Define the ==objective and scope of the benchmarking==. What is the purpose of the benchmarking? What are the criteria and metrics to evaluate the performance? What are the tools to compare?
|
||||
- Choose a ==reference dataset and a reference model==. The dataset should be relevant and representative of the task at hand. The model should be appropriate and consistent for the chosen tools.
|
||||
- Choose a ==reference computer and a reference training strategy==. The computer should have sufficient hardware and software specifications to run the tools. The training strategy should include parameters such as loss function, optimization algorithm, and stopping criterion.
|
||||
- Run the tools on the dataset using the model and the training strategy. ==Record the results== and metrics for each tool.
|
||||
- ==Analyze and compare the results==. Use visualizations and statistics to summarize and interpret the results. Identify the strengths and weaknesses of each tool.
|
||||
-
|
||||
- What are the issues when benchmarking ML tools
|
||||
- Benchmarking ML tools is not without challenges. Some of the common issues are:
|
||||
- The ==lack of standardization and reproducibility==. Different tools may have different implementations, configurations, or versions that affect their performance. Moreover, different datasets, models, or training strategies may also introduce variability and inconsistency in the results. Therefore, it is important to ensure that the benchmarking is fair and reliable by using standardized and reproducible methods.
|
||||
- The ==trade-off between complexity and simplicity==. Some tools may have more features or functionalities than others, which can make them more powerful or flexible, but also more complex or difficult to use. On the other hand, some tools may be simpler or easier to use, but also more limited or constrained in their capabilities. Therefore, it is important to balance between complexity and simplicity when choosing or evaluating a tool.
|
||||
- The ==trade-off between accuracy and efficiency==. Some tools may have higher accuracy or precision than others, but also lower speed or scalability. On the other hand, some tools may be faster or more scalable than others, but also less accurate or precise. Therefore, it is important to balance between accuracy and efficiency when choosing or evaluating a tool.
|
||||
- Conclusion
|
||||
- Benchmarking ML tools is an essential step to assess their performance and suitability for different tasks and applications. However, benchmarking ML tools is not a simple process, as it involves many steps and challenges. In this blog post, we have elaborated on why benchmarking is needed when applying ML tools when automating some process; how typical benchmarking processes look like; and what are the issues when benchmarking ML tools.
|
||||
- Machine learning (ML) is a fast-growing field with many applications in various domains and areas including MDE. Selecting the appropriate ML tool for a particular task can be difficult, as different ML tools may have different strengths and weaknesses. In this [[paper]], we presented the \modelxglue framework, which we have designed to facilitate benchmarking ML [[MODELS]] specifically created to address MDE tasks. The framework has been designed to be able to manage different datasets, metrics, and execution environments. The aim is to automate benchmarking processess [[by]] simplifying comparisong processess [[by]] limiting the burden related to the installation and management of the different artifacts that are typically involved. A catalogue of already available benchmarks has been presented and its execution has been presented.
|
||||
- [[RelatedWork]]
|
||||
- [[@Benchmarking Machine Learning Solutions in Production]]
|
||||
- [[@PMLB: a large benchmark suite for machine learning evaluation and comparison]]
|
||||
-97
@@ -1,97 +0,0 @@
|
||||
type:: [[journalPaper]]
|
||||
external-sources::
|
||||
todoist:: https://todoist.com/showTask?id=6509420504
|
||||
year:: 2023
|
||||
deadline:: [[12-05-2023]]
|
||||
status:: [[DOING]]
|
||||
venue:: [[SOSYM]]
|
||||
priority:: [[P1]]
|
||||
|
||||
- ## TODOs
|
||||
- DONE Vedere sezione 3
|
||||
completed:: [[09-05-2023]]
|
||||
- DONE Finalizzare descizione architettura
|
||||
completed:: [[11-05-2023]]
|
||||
- DONE GUardare lo spreadsheet di Jesus
|
||||
completed:: [[11-05-2023]]
|
||||
- Finalizzare fig 3
|
||||
- DONE Rivedere parte iniziale sez 4
|
||||
completed:: [[09-05-2023]]
|
||||
- DONE Scrivere Conclusioni
|
||||
completed:: [[09-05-2023]]
|
||||
- [[10-05-2023]]
|
||||
- DONE Rivedere Intro
|
||||
completed:: [[10-05-2023]]
|
||||
- DONE Scrivere [[Abstract]]
|
||||
completed:: [[10-05-2023]]
|
||||
- [[12-05-2023]]
|
||||
- DONE Rivedere sezione 5
|
||||
completed:: [[12-05-2023]]
|
||||
- DONE [[people/riccardo]] rivede la sezione related [[WORK]]
|
||||
completed:: [[12-05-2023]]
|
||||
- DONE Rivedere sezione 3
|
||||
completed:: [[12-05-2023]]
|
||||
- TODO Lettura completa
|
||||
- DONE Fare figura componenti da inserire in sezione 3
|
||||
completed:: [[02-05-2023]]
|
||||
- DONE Rivedere parte scritta da Riccardo
|
||||
completed:: [[02-05-2023]]
|
||||
- DONE Listare challenges a fine sezione [[2]]
|
||||
completed:: [[02-05-2023]]
|
||||
-
|
||||
- [[Ideas]]
|
||||
- We could propose a tool demo [[paper]] at MODELS
|
||||
- [MODELS 2023 - Tools and Demonstrations - MODELS 2023 (researchr.org)](https://conf.researchr.org/track/models-2023/models-2023-tools-and-demonstrations)
|
||||
- We could even organize an informal hackathon to extend the catalogue
|
||||
-
|
||||
- Bisogna descrivere un processo tipico di benchmarking.
|
||||
- A tale scopo bisogna guardare [microsoft/CodeXGLUE: CodeXGLUE (github.com)](https://github.com/microsoft/CodeXGLUE)
|
||||
- microsoft/CodeXGLUE: CodeXGLUEmicrosoft/CodeXGLUE: CodeXGLUE - https://github.com/microsoft/CodeXGLUE -
|
||||
- 23.9 million professional developers in 2019, and the population is expected to reach 28.7 million in 2024
|
||||
- Microsoft offers the most complete toolchain for developers, bringing together the best of GitHub, Visual Studio, and Microsoft Azure to help developers to go from idea to code and code to cloud.
|
||||
- **Recent years have seen a surge of applying of statistical models, including neural nets, to code intelligence tasks**
|
||||
- However, the area of code intelligence lacks a benchmark suite that covers a wide range of tasks.
|
||||
- **CodeXGLUE, a benchmark dataset and open challenge for code intelligence.**
|
||||
- collection of code intelligence tasks and a platform for model evaluation and comparison.
|
||||
-
|
||||
- The questions / points to elaborate are as follows:
|
||||
- the need of benchmarking when applying ML tools when automating some process
|
||||
- how typical benchmarking processes look like
|
||||
- what are the issues when benchmarking ML tools
|
||||
-
|
||||
- Initial draft on notes:
|
||||
% Benchmarking ML Tools: Why and How
|
||||
- Machine learning (ML) is a rapidly evolving field that offers many benefits for various domains and applications. However, choosing the right ML tool for a specific task can be challenging, as there are many factors to consider, such as data capacity, training speed, inference speed, and model precision. Therefore, benchmarking ML tools is a crucial step to evaluate their performance and suitability for different scenarios.
|
||||
- Benchmarking is the practice of comparing tools based on some key performance indicators (KPIs) that reflect their strengths and weaknesses. Benchmarking can help users make informed decisions about which tool to use, as well as identify areas for improvement and optimization. However, benchmarking ML tools is not a straightforward process, as it involves many steps and challenges.
|
||||
|
||||
In this blog post, we will elaborate on:
|
||||
- The need of benchmarking when applying ML tools when automating some process
|
||||
- How typical benchmarking processes look like
|
||||
- What are the issues when benchmarking ML tools
|
||||
|
||||
The need of benchmarking when applying ML tools when automating some process
|
||||
|
||||
ML tools are often used to automate some process that involves data analysis, prediction, or classification. For example, ML tools can be used to automate image recognition, sentiment analysis, fraud detection, or recommendation systems. However, not all ML tools are equally effective or efficient for these tasks. Some tools may have higher accuracy, but lower speed; some tools may handle large datasets better than others; some tools may have more features or functionalities than others.
|
||||
|
||||
Therefore, benchmarking ML tools is necessary to measure their performance and compare them against each other or against some baseline. Benchmarking can help users select the best tool for their specific needs and goals, as well as optimize their workflow and resource allocation. Benchmarking can also help developers improve their tools by identifying bottlenecks and gaps in performance.
|
||||
|
||||
How typical benchmarking processes look like
|
||||
|
||||
A typical benchmarking process consists of the following steps:
|
||||
- Define the ==objective and scope of the benchmarking==. What is the purpose of the benchmarking? What are the criteria and metrics to evaluate the performance? What are the tools to compare?
|
||||
- Choose a ==reference dataset and a reference model==. The dataset should be relevant and representative of the task at hand. The model should be appropriate and consistent for the chosen tools.
|
||||
- Choose a ==reference computer and a reference training strategy==. The computer should have sufficient hardware and software specifications to run the tools. The training strategy should include parameters such as loss function, optimization algorithm, and stopping criterion.
|
||||
- Run the tools on the dataset using the model and the training strategy. ==Record the results== and metrics for each tool.
|
||||
- ==Analyze and compare the results==. Use visualizations and statistics to summarize and interpret the results. Identify the strengths and weaknesses of each tool.
|
||||
-
|
||||
- What are the issues when benchmarking ML tools
|
||||
- Benchmarking ML tools is not without challenges. Some of the common issues are:
|
||||
- The ==lack of standardization and reproducibility==. Different tools may have different implementations, configurations, or versions that affect their performance. Moreover, different datasets, models, or training strategies may also introduce variability and inconsistency in the results. Therefore, it is important to ensure that the benchmarking is fair and reliable by using standardized and reproducible methods.
|
||||
- The ==trade-off between complexity and simplicity==. Some tools may have more features or functionalities than others, which can make them more powerful or flexible, but also more complex or difficult to use. On the other hand, some tools may be simpler or easier to use, but also more limited or constrained in their capabilities. Therefore, it is important to balance between complexity and simplicity when choosing or evaluating a tool.
|
||||
- The ==trade-off between accuracy and efficiency==. Some tools may have higher accuracy or precision than others, but also lower speed or scalability. On the other hand, some tools may be faster or more scalable than others, but also less accurate or precise. Therefore, it is important to balance between accuracy and efficiency when choosing or evaluating a tool.
|
||||
- Conclusion
|
||||
- Benchmarking ML tools is an essential step to assess their performance and suitability for different tasks and applications. However, benchmarking ML tools is not a simple process, as it involves many steps and challenges. In this blog post, we have elaborated on why benchmarking is needed when applying ML tools when automating some process; how typical benchmarking processes look like; and what are the issues when benchmarking ML tools.
|
||||
- Machine learning (ML) is a fast-growing field with many applications in various domains and areas including MDE. Selecting the appropriate ML tool for a particular task can be difficult, as different ML tools may have different strengths and weaknesses. In this [[paper]], we presented the \modelxglue framework, which we have designed to facilitate benchmarking ML [[MODELS]] specifically created to address MDE tasks. The framework has been designed to be able to manage different datasets, metrics, and execution environments. The aim is to automate benchmarking processess [[by]] simplifying comparisong processess [[by]] limiting the burden related to the installation and management of the different artifacts that are typically involved. A catalogue of already available benchmarks has been presented and its execution has been presented.
|
||||
- [[RelatedWork]]
|
||||
- [[@Benchmarking Machine Learning Solutions in Production]]
|
||||
- [[@PMLB: a large benchmark suite for machine learning evaluation and comparison]]
|
||||
-37
@@ -1,37 +0,0 @@
|
||||
type:: [[bookchapter]]
|
||||
external-links::
|
||||
todoist:: https://todoist.com/showTask?id=5492418790
|
||||
year:: 2023
|
||||
date-start:: [[05-09-2022]]
|
||||
people:: [[people/alfonso]] [[people/phuong]]
|
||||
status:: [[ACCEPTED]]
|
||||
|
||||
- **30 #PAPERS MERGED WITH 20 MANUALLY SELECTED**
|
||||
- 4 duplicati quindi 30 + 16 => 46 (to be further filtered)
|
||||
- **Interesting related / reference #paper to consider**
|
||||
- [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]]
|
||||
- [[@Niggemann201221]]
|
||||
- Per descrivere il processo di selezione dei paper
|
||||
- [[@Adversarial Attacks to API Recommender Systems: Time to Wake Up and Smell the Coffee?]]
|
||||
- [[@Handbook on Artificial Intelligence-Empowered Applied Software Engineering: VOL.1: Novel Methodologies to Engineering Smart Software Systems]]
|
||||
- [[@Collaborative Model-Driven Software Engineering: A Classification Framework and a Research Map]]
|
||||
- id:: #{"{" "}"}
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PAPERS]]
|
||||
people:: #people/phuong
|
||||
tags::
|
||||
status:: [[DONE]]
|
||||
date:: [[05-09-2022]]
|
||||
- [Book chapter - reference #PAPERS.xlsx - Google Sheets](https://docs.google.com/spreadsheets/d/1UaDD4eSJQ0OZIcv3qXr7BMKhPqMzOMS7/edit#gid=940972288)
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Phuong
|
||||
- Phuong lavora su sezione 2 e forse 4 (mentre legge lavoro related)
|
||||
- Io lavoro su
|
||||
- [sezione 4](https://todoist.com/showTask?id=6146932471)
|
||||
id:: 631f0934-8108-4d13-89f5-62a0d262eb69
|
||||
- DONE [Descrizione del processo/protocollo usato per collezionare e labellare i lavori](https://todoist.com/showTask?id=6146932848)
|
||||
completed:: [[01-05-2023]]
|
||||
- Vista che considera anche il tipo di artefatto (modello, metamodello, etc.)
|
||||
- Discorso anche qualitativo
|
||||
- LSTM sottoutilizzato???
|
||||
-
|
||||
-37
@@ -1,37 +0,0 @@
|
||||
type:: [[Bookchapter]]
|
||||
external-links::
|
||||
todoist:: https://todoist.com/showTask?id=5492418790
|
||||
year:: 2023
|
||||
date-start:: [[05-09-2022]]
|
||||
people:: [[people/alfonso]] [[people/PhuongNguyen]]
|
||||
status:: [[ACCEPTED]]
|
||||
|
||||
- **30 #PAPERS MERGED WITH 20 MANUALLY SELECTED**
|
||||
- 4 duplicati quindi 30 + 16 => 46 (to be further filtered)
|
||||
- **Interesting related / reference #paper to consider**
|
||||
- [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]]
|
||||
- [[@Niggemann201221]]
|
||||
- Per descrivere il processo di selezione dei paper
|
||||
- [[@Adversarial Attacks to API Recommender Systems: Time to Wake Up and Smell the Coffee?]]
|
||||
- [[@Handbook on Artificial Intelligence-Empowered Applied Software Engineering: VOL.1: Novel Methodologies to Engineering Smart Software Systems]]
|
||||
- [[@Collaborative Model-Driven Software Engineering: A Classification Framework and a Research Map]]
|
||||
- id:: #{"{" "}"}
|
||||
type:: [[meeting]]
|
||||
external-links::
|
||||
tags:: [[PAPERS]]
|
||||
people:: #people/PhuongNguyen
|
||||
tags::
|
||||
status:: [[DONE]]
|
||||
date:: [[05-09-2022]]
|
||||
- [Book chapter - reference #PAPERS.xlsx - Google Sheets](https://docs.google.com/spreadsheets/d/1UaDD4eSJQ0OZIcv3qXr7BMKhPqMzOMS7/edit#gid=940972288)
|
||||
- Condiviso il paper [[@AI-driven streamlined modeling: experiences and lessons learned from multiple domains]] con Phuong
|
||||
- Phuong lavora su sezione 2 e forse 4 (mentre legge lavoro related)
|
||||
- Io lavoro su
|
||||
- [sezione 4](https://todoist.com/showTask?id=6146932471)
|
||||
id:: 631f0934-8108-4d13-89f5-62a0d262eb69
|
||||
- DONE [Descrizione del processo/protocollo usato per collezionare e labellare i lavori](https://todoist.com/showTask?id=6146932848)
|
||||
date-submitted:: [[01-05-2023]]
|
||||
- Vista che considera anche il tipo di artefatto (modello, metamodello, etc.)
|
||||
- Discorso anche qualitativo
|
||||
- LSTM sottoutilizzato???
|
||||
-
|
||||
@@ -1,39 +0,0 @@
|
||||
status:: [[Active]]
|
||||
date-start:: [[01-06-2022]]
|
||||
date-end:: [[31-05-2025]]
|
||||
project-type:: [[PRIN]]
|
||||
todoist:: https://app.todoist.com/app/project/projects-prin-emeliot-6HVW7R4C59Hxrx8R
|
||||
|
||||
- [[PROJECTS/PRIN-EMELIOT/STUDENTS-EXPERIMENT]]
|
||||
-
|
||||
- Prenotata Sala del Senato, Palazzo Camponeschi
|
||||
- Allora l'8 dalle 12:30 fino alle 19:00, mentre per il 9 direi dalle 9:00 fino alle 14:30. Comunque stiamo predisponendo l'agenda in questi giorni, vi faremo sapere se ci saranno modifiche da fare alla prenotazione.
|
||||
- Chiedere a Leonardo dove siamo
|
||||
- Integrazione lavoro Felicien + MODNESS
|
||||
- Quindi fare checkpoint
|
||||
-
|
||||
-
|
||||
- ## [[ADMIN]]
|
||||
- 
|
||||
- Quindi
|
||||
- ```calc
|
||||
5/3
|
||||
```
|
||||
-
|
||||
- 1.7 mesi l'uomo l'anno
|
||||
- ```calc
|
||||
1720/12
|
||||
144*1.7
|
||||
245/12
|
||||
```
|
||||
- Quindi 245 ore l'anno, circa 20.5 ore al mese.
|
||||
-
|
||||
-
|
||||
- ## Meetings
|
||||
- {{query (property :tags [[PROJECTS/PRIN-EMELIOT]])}}
|
||||
query-sort-by:: date
|
||||
query-table:: true
|
||||
query-sort-desc:: true
|
||||
query-properties:: [:page :date :isconsortium :people :location]
|
||||
-
|
||||
-
|
||||
@@ -1,39 +0,0 @@
|
||||
status:: [[Active]]
|
||||
date-start:: [[01-06-2022]]
|
||||
date-end:: [[31-05-2025]]
|
||||
project-type:: [[PRIN]]
|
||||
todoist:: https://app.todoist.com/app/project/projects-prin-emeliot-6HVW7R4C59Hxrx8R
|
||||
|
||||
- [[PROJECTS/PRIN-EMELIOT/STUDENTS-EXPERIMENT]]
|
||||
-
|
||||
- Prenotata Sala del Senato, Palazzo Camponeschi
|
||||
- Allora l'8 dalle 12:30 fino alle 19:00, mentre per il 9 direi dalle 9:00 fino alle 14:30. Comunque stiamo predisponendo l'agenda in questi giorni, vi faremo sapere se ci saranno modifiche da fare alla prenotazione.
|
||||
- Chiedere a Leonardo dove siamo
|
||||
- Integrazione lavoro Felicien + MODNESS
|
||||
- Quindi fare checkpoint
|
||||
-
|
||||
-
|
||||
- ## [[ADMIN]]
|
||||
- 
|
||||
- Quindi
|
||||
- ```calc
|
||||
5/3
|
||||
```
|
||||
-
|
||||
- 1.7 mesi l'uomo l'anno
|
||||
- ```calc
|
||||
1720/12
|
||||
144*1.7
|
||||
245/12
|
||||
```
|
||||
- Quindi 245 ore l'anno, circa 20.5 ore al mese.
|
||||
-
|
||||
-
|
||||
- ## Meetings
|
||||
- {{query (property :tags [[PROJECTS/PRIN-EMELIOT]])}}
|
||||
query-sort-by:: date
|
||||
query-table:: true
|
||||
query-sort-desc:: true
|
||||
query-properties:: [:page :date :isconsortium :people :location]
|
||||
-
|
||||
-
|
||||
@@ -1,46 +0,0 @@
|
||||
icon:: 📝
|
||||
todoist:: https://todoist.com/app/project/2181518404
|
||||
progress:: {{renderer :todomaster}}
|
||||
|
||||
- ## ⛑️ WORKING
|
||||
id:: 656bb92d-99b8-4f8c-8498-d79698ff9dc8
|
||||
- {{query (and (namespace [[PAPERS]]) (not (page-property :status [[IDLE]])) (not (page-property :status [[ACCEPTED]])) (not (page-property :status [[REVISED]] )) (not (page-property :status [[DISMISSED]])) (not (page-property :status [[SUBMITTED]])) (not (page-property :status [[REJECTED]])) (page-property :year))}}
|
||||
query-sort-by:: priority
|
||||
query-sort-desc:: false
|
||||
query-properties:: [:priority :venue :page :deadline-submission :deadline-abstract]
|
||||
id:: 648b062b-c129-40a4-ace1-2364698a8736
|
||||
- ### ☑️ TODOs grouped by paper
|
||||
- {{query (and (or (task TODO) (task DOING)) (namespace [[papers]]))}}
|
||||
query-table:: true
|
||||
query-sort-by:: page
|
||||
query-sort-desc:: false
|
||||
- ### [From Todoist](https://todoist.com/home)
|
||||
collapsed:: true
|
||||
- {{query (and (task DOING TODO) (page [[GOALS-TODOIST]]) "PAPERS/")}}
|
||||
query-table:: true
|
||||
query-properties:: [:block :todoist-desc :todoist-id]
|
||||
query-sort-by:: block
|
||||
query-sort-desc:: true
|
||||
-
|
||||
-
|
||||
- ## [[SUBMITTED]]
|
||||
- {{query (and (namespace [[papers]]) (page-property :status [[SUBMITTED]] ) )}}
|
||||
query-properties:: [:type :year :venue :full-title :date-submitted]
|
||||
query-sort-by:: year
|
||||
query-sort-desc:: true
|
||||
-
|
||||
- ## [[ACCEPTED]]
|
||||
- {{query (and (namespace [[papers]]) (page-property :status [[ACCEPTED]]) (page-property :year "2024"))}}
|
||||
query-properties:: [:page :year :venue :todoist :type]
|
||||
query-sort-by:: venue
|
||||
query-sort-desc:: true
|
||||
- ## [[REJECTED]]
|
||||
collapsed:: true
|
||||
- {{query (and (namespace [[papers]]) (page-property :status [[REJECTED]]) (page-property :year "2024"))}}
|
||||
query-properties:: [:page :type :full-title :year :venue]
|
||||
- ## [[IDLE]]
|
||||
collapsed:: true
|
||||
- {{query (and (namespace [[papers]]) (page-property :status [[IDLE]] ) )}}
|
||||
- ## Acknowledgments
|
||||
- All the numerical simulations/evaluations have been realized on the Linux HPC cluster Caliban of the High-Performance Computing Laboratory of the Department of Information Engineering, Computer Science and Mathematics (DISIM) at the University of L'Aquila. This work has been partially supported by the EMELIOT national research project, which has been funded by the MUR under the PRIN 2020 program (Contract 2020W3A5FY). The work has also been partially supported by the European Union--NextGenerationEU through the Italian Ministry of University and Research, Projects PRIN 2022 PNRR \emph{``FRINGE: context-aware FaiRness engineerING in complex software systEms''} grant n. P2022553SL. We acknowledge the Italian ``PRIN 2022'' project TRex-SE: \emph{``Trustworthy Recommenders for Software Engineers,''} grant n. 2022LKJWHC.
|
||||
-
|
||||
@@ -1,41 +0,0 @@
|
||||
icon:: 📅
|
||||
|
||||
- [[GOALS-TODOIST]]
|
||||
- **WEEK BLOCKING (First Semester)**
|
||||
id:: 650b4d6e-0015-446a-bc62-629af3621638
|
||||
- |**Monday**|**Tuesday**|**Wednesday**|**Thursday**|**Friday**|**Saturday**|
|
||||
|--|--|--|--|--|--|
|
||||
|[[Teaching]]|[[Teaching]]|[[Papers]]|[[Papers]]|[[Teaching]]|[[CV Empower]]|
|
||||
||[[Reviews]]| [Mentoring](onenote:https://d.docs.live.net/a33324427a144a54/Documenti/CROSSMINER/MEETINGS/Internal%20Meetings.one#section-id={98E19AF8-5A76-4F4A-B1FE-AE643744BAE7}&end) ([visualizzazione Web](https://onedrive.live.com/view.aspx?resid=A33324427A144A54%211622&id=documents&wd=target%28MEETINGS%2FInternal%20Meetings.one%7C98E19AF8-5A76-4F4A-B1FE-AE643744BAE7%2F%29)) |[[Projects]]|[[Reviews]]||
|
||||
|||[[Projects]]|[[CV Empower]]|||
|
||||
- **WEEK BLOCHING (Second Semester)**
|
||||
- One hour per day needs to be employed to read material stored in [[Omnivore]] otherwise the list just grows without any actions to reduce it.
|
||||
-
|
||||
-
|
||||
- Migliorare le **lezioni** magistrale?
|
||||
- DONE Rivedere **funding** di Riccardo e Claudio
|
||||
- Claudio mi sembra piu' urgente
|
||||
- Da fare entro fine anno altrimenti si entra nella nuova normativa (contratti di ricerca con costi molto piu alti)
|
||||
- [[2021-02-04-1205-BUDGET]]
|
||||
-
|
||||
- [[BRAINSTORMING]] per nuovi lavori / nuove direzioni di ricerca
|
||||
- Vedi proposta progetto EU non accettata #PROJECTS/PODIUM
|
||||
- Forse qui [Funding & tenders (europa.eu)](https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/horizon-cl4-2022-digital-emerging-02-05;callCode=null;freeTextSearchKeyword=;matchWholeText=true;typeCodes=;statusCodes=31094502;programmePeriod=2021%20-%202027;programCcm2Id=43108390;programDivisionCode=43120193;focusAreaCode=null;destination=43650717;mission=null;geographicalZonesCode=null;programmeDivisionProspect=null;startDateLte=null;startDateGte=null;crossCuttingPriorityCode=AI;cpvCode=null;performanceOfDelivery=null;sortQuery=sortStatus;orderBy=asc;onlyTenders=false;topicListKey=topicSearchTablePageState)
|
||||
-
|
||||
- DONE Organizzare attività di **placement** di Ateneo
|
||||
- Il problema principale e' l'ufficio
|
||||
-
|
||||
- Lavorare quindi su [[CV Empower]]
|
||||
- Capire come risolvere i problemi di **espressione** / comunicazione
|
||||
- Leggere documentazione tecnica
|
||||
- Letture di cultura generale
|
||||
-
|
||||
- [[Lavori Ristrutturazione]]
|
||||
-
|
||||
- QUINDI #4monthplan
|
||||
- DONE [[PAPERS]]
|
||||
- DONE [[TEACHING]]
|
||||
- DONE Sistemare rendicontazione contratti [[PROJECTS/PRIN-EMELIOT]]
|
||||
- DONE Conferenza MODELS
|
||||
- DONE Gestire Special-Issue SCP
|
||||
-
|
||||
@@ -1,41 +0,0 @@
|
||||
icon:: 📅
|
||||
|
||||
- [[GOALS-TODOIST]]
|
||||
- **WEEK BLOCKING (First Semester)**
|
||||
id:: 650b4d6e-0015-446a-bc62-629af3621638
|
||||
- |**Monday**|**Tuesday**|**Wednesday**|**Thursday**|**Friday**|**Saturday**|
|
||||
|--|--|--|--|--|--|
|
||||
|[[Teaching]]|[[Teaching]]|[[Papers]]|[[Papers]]|[[Teaching]]|[[CV Empower]]|
|
||||
||[[Reviews]]| [Mentoring](onenote:https://d.docs.live.net/a33324427a144a54/Documenti/CROSSMINER/MEETINGS/Internal%20Meetings.one#section-id={98E19AF8-5A76-4F4A-B1FE-AE643744BAE7}&end) ([visualizzazione Web](https://onedrive.live.com/view.aspx?resid=A33324427A144A54%211622&id=documents&wd=target%28MEETINGS%2FInternal%20Meetings.one%7C98E19AF8-5A76-4F4A-B1FE-AE643744BAE7%2F%29)) |[[Projects]]|[[Reviews]]||
|
||||
|||[[Projects]]|[[CV Empower]]|||
|
||||
- **WEEK BLOCHING (Second Semester)**
|
||||
- One hour per day needs to be employed to read material stored in [[Omnivore]] otherwise the list just grows without any actions to reduce it.
|
||||
-
|
||||
-
|
||||
- Migliorare le **lezioni** magistrale?
|
||||
- DONE Rivedere **funding** di Riccardo e Claudio
|
||||
- Claudio mi sembra piu' urgente
|
||||
- Da fare entro fine anno altrimenti si entra nella nuova normativa (contratti di ricerca con costi molto piu alti)
|
||||
- [[2021-02-04-1205-BUDGET]]
|
||||
-
|
||||
- [[BRAINSTORMING]] per nuovi lavori / nuove direzioni di ricerca
|
||||
- Vedi proposta progetto EU non accettata #PROJECTS/PODIUM
|
||||
- Forse qui [Funding & tenders (europa.eu)](https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/horizon-cl4-2022-digital-emerging-02-05;callCode=null;freeTextSearchKeyword=;matchWholeText=true;typeCodes=;statusCodes=31094502;programmePeriod=2021%20-%202027;programCcm2Id=43108390;programDivisionCode=43120193;focusAreaCode=null;destination=43650717;mission=null;geographicalZonesCode=null;programmeDivisionProspect=null;startDateLte=null;startDateGte=null;crossCuttingPriorityCode=AI;cpvCode=null;performanceOfDelivery=null;sortQuery=sortStatus;orderBy=asc;onlyTenders=false;topicListKey=topicSearchTablePageState)
|
||||
-
|
||||
- DONE Organizzare attività di **placement** di Ateneo
|
||||
- Il problema principale e' l'ufficio
|
||||
-
|
||||
- Lavorare quindi su [[CV Empower]]
|
||||
- Capire come risolvere i problemi di **espressione** / comunicazione
|
||||
- Leggere documentazione tecnica
|
||||
- Letture di cultura generale
|
||||
-
|
||||
- [[Lavori Ristrutturazione]]
|
||||
-
|
||||
- QUINDI #4monthplan
|
||||
- DONE [[PAPERS]]
|
||||
- DONE [[TEACHING]]
|
||||
- DONE Sistemare rendicontazione contratti [[PROJECTS/PRIN-EMELIOT]]
|
||||
- DONE Conferenza MODELS
|
||||
- DONE Gestire Special-Issue SCP
|
||||
-
|
||||
@@ -1,88 +0,0 @@
|
||||
icon:: 📜
|
||||
|
||||
-
|
||||
- # COLOR SCHEMA
|
||||
id:: 634184dc-a3c1-4816-8b77-af9e091bcc64
|
||||
- Green -> Everything is ok, it is just to help the reading
|
||||
background-color:: green
|
||||
- ==Yellow -> Something is not clear. Probably a question is raised. Need for clarification==
|
||||
background-color:: yellow
|
||||
- Red -> Typos, unreadable sentence
|
||||
background-color:: red
|
||||
- Purple -> Key sentence / aspect in the document.
|
||||
background-color:: purple
|
||||
- [[@Uncovering Library Features from Incomplete Information on Stack Overflow]]
|
||||
- ## REVIEWS - DOING
|
||||
query-sort-by:: year
|
||||
query-table:: true
|
||||
query-sort-desc:: false
|
||||
query-properties:: [:year :venue :deadline :full-title :page :parent :todoist]
|
||||
id:: 648f2e59-50c8-4173-9cc0-71512dead48d
|
||||
{{query (and (property :status [[DOING]]) (or (property :type [[REVIEWS]]) (property :type [[REVIEWS/PhDThesis]]) (property :type [[REVIEWS/PROJECTS]])) (not [[templates]]))}}
|
||||
- ## REVIEWS - DONE
|
||||
query-table:: true
|
||||
query-properties:: [:year :venue :full-title :date-submitted]
|
||||
query-sort-by:: date-submitted
|
||||
query-sort-desc:: true
|
||||
collapsed:: true
|
||||
{{query (and (property :status [[DONE]]) (property :type [[REVIEWS]]) (not [[templates]]))}}
|
||||
- ## OTHER REVIEWS
|
||||
collapsed:: true
|
||||
- DONE [[JSSOFTWARE-D-22-00977_reviewer.pdf]]
|
||||
- DONE [[IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems]]
|
||||
- DONE [[TTC-2023]]
|
||||
- DONE [[Software Evolutionary Architecture: Automated Planning for Functional Changes]]
|
||||
date-submitted:: [[01-05-2023]]
|
||||
- DONE [[TOSEM-2023-0032_Proof_hi]]
|
||||
- DONE [[JSME-23-0044]]
|
||||
- DONE [[JSSOFTWARE-D-22-00977_R1_reviewer]]
|
||||
- DONE [[SCICO-D-22-00337_R1]]
|
||||
- DONE [[JOT-507-Article Text-1015-1-4-20230214]]
|
||||
- SATTOSE 2023
|
||||
- DONE [[SATToSE_2023_paper_1]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_2]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_3]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_5]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- ## 2022
|
||||
- ### Papers
|
||||
- #### Conferences
|
||||
id:: 63061068-2bf3-4551-82cd-08565392d81f
|
||||
**KARS2022**: [[@Recommending scholarly articles to monitor COVID-19 trends in social media based on low-cost topic modeling]]
|
||||
**ASE2022 Artifact Evaluation** [[@CrystalBLEU: Precisely and Efficiently Measuring the Similarity of Code]]
|
||||
**EMSE 2022** [[EMSE_SelectingThird-party Libraries_The_Data_Scientist_s_Perspective]]
|
||||
**ICSE 2023**
|
||||
- DONE [[ICSE2023-REVIEW-1237]]
|
||||
- DONE [[ICSE2023-REVIEW-1237-METAREVIEW]]
|
||||
- DONE [[ICSE2023-REVIEW-685]]
|
||||
- DONE [[ICSE2023-REVIEW-2055]]
|
||||
- DONE [[Qualitative Clustering of Software Repositories Based on Software Metrics]]
|
||||
((63568355-e57b-4a93-b804-5717bca6402b))
|
||||
- DONE [[ICSE2023-REVIEW-1123]]
|
||||
- [[icse2023-review-1123-metareview]]
|
||||
- DONE [[ICSE2023-REVIEW-1528]]
|
||||
collapsed:: true
|
||||
[[01-11-2022]]
|
||||
- DONE [[ICSE2023-REVIEW-9]] **L**
|
||||
collapsed:: true
|
||||
DONE [[ICSE2023-REVIEW-9-METAREVIEW]]
|
||||
DONE [[ICSE2023-REBUTTAL]]
|
||||
**ROSE 2023**
|
||||
[[ROSE2023]]
|
||||
**ICSE2023**
|
||||
DONE [[ICSE2023-Poster-6]]
|
||||
-
|
||||
- #### Journals
|
||||
- DONE [[COLA-D-22-00029_reviewer]]
|
||||
- **Tom Mens Book Chapter**
|
||||
- DONE [[REVIEWS-Mining Analyzing and Evolving Data-intensive Software Ecosystems]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- ### Projects
|
||||
- DONE [[10-12-SFI-Ireland]]
|
||||
- ### PhD Thesis
|
||||
- DONE [[GSSI PhD Thesis proposal review]]
|
||||
- DONE [[Maxime_Gobert-NAMUR-Cleve]]
|
||||
- DONE [[Antonio Mastropaolo Student of Gabriele Bavota]]
|
||||
@@ -1,85 +0,0 @@
|
||||
icon:: 📜
|
||||
|
||||
- # COLOR SCHEMA
|
||||
id:: 634184dc-a3c1-4816-8b77-af9e091bcc64
|
||||
- Green -> Everything is ok, it is just to help the reading
|
||||
background-color:: green
|
||||
- ==Yellow -> Something is not clear. Probably a question is raised. Need for clarification==
|
||||
background-color:: yellow
|
||||
- Red -> Typos, unreadable sentence
|
||||
background-color:: red
|
||||
- Purple -> Key sentence / aspect in the document.
|
||||
background-color:: purple
|
||||
- ## REVIEWS - DOING
|
||||
query-table:: true
|
||||
query-properties:: [:page :parent :year :venue :deadline-submission :full-title :deadline]
|
||||
query-sort-by:: venue
|
||||
query-sort-desc:: false
|
||||
{{query (and (property :status [[DOING]]) (or (property :type [[REVIEWS]]) (property :type [[REVIEWS/PhDThesis]]) (property :type [[REVIEWS/PROJECTS]])) (not [[templates]]))}}
|
||||
- ## REVIEWS - DONE
|
||||
query-table:: true
|
||||
query-properties:: [:year :venue :full-title :date-submitted]
|
||||
query-sort-by:: venue
|
||||
query-sort-desc:: true
|
||||
{{query (and (property :status [[DONE]]) (property :type [[REVIEWS]]) (not [[templates]]))}}
|
||||
- ## OTHER REVIEWS
|
||||
- DONE [[JSSOFTWARE-D-22-00977_reviewer.pdf]]
|
||||
- DONE [[IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems]]
|
||||
- DONE [[TTC-2023]]
|
||||
- DONE [[Software Evolutionary Architecture: Automated Planning for Functional Changes]]
|
||||
date-submitted:: [[01-05-2023]]
|
||||
- DONE [[TOSEM-2023-0032_Proof_hi]]
|
||||
- DONE [[JSME-23-0044]]
|
||||
- DONE [[JSSOFTWARE-D-22-00977_R1_reviewer]]
|
||||
- DONE [[SCICO-D-22-00337_R1]]
|
||||
- DONE [[JOT-507-Article Text-1015-1-4-20230214]]
|
||||
- SATTOSE 2023
|
||||
collapsed:: true
|
||||
- DONE [[SATToSE_2023_paper_1]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_2]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_3]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_5]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- ## 2022
|
||||
collapsed:: true
|
||||
- ### Papers
|
||||
- #### Conferences
|
||||
id:: 63061068-2bf3-4551-82cd-08565392d81f
|
||||
**KARS2022**: [[@Recommending scholarly articles to monitor COVID-19 trends in social media based on low-cost topic modeling]]
|
||||
**ASE2022 Artifact Evaluation** [[CrystalBLEU: Precisely and Efficiently Measuring the Similarity of Code]]
|
||||
**EMSE 2022** [[EMSE_SelectingThird-party Libraries_The_Data_Scientist_s_Perspective]]
|
||||
**ICSE 2023**
|
||||
- DONE [[ICSE2023-REVIEW-1237]]
|
||||
- DONE [[ICSE2023-REVIEW-1237-METAREVIEW]]
|
||||
- DONE [[ICSE2023-REVIEW-685]]
|
||||
- DONE [[ICSE2023-REVIEW-2055]]
|
||||
- DONE [[Qualitative Clustering of Software Repositories Based on Software Metrics]]
|
||||
((63568355-e57b-4a93-b804-5717bca6402b))
|
||||
- DONE [[ICSE2023-REVIEW-1123]]
|
||||
- [[icse2023-review-1123-metareview]]
|
||||
- DONE [[ICSE2023-REVIEW-1528]]
|
||||
collapsed:: true
|
||||
[[01-11-2022]]
|
||||
- DONE [[ICSE2023-REVIEW-9]] **L**
|
||||
collapsed:: true
|
||||
DONE [[ICSE2023-REVIEW-9-METAREVIEW]]
|
||||
DONE [[ICSE2023-REBUTTAL]]
|
||||
**ROSE 2023**
|
||||
[[ROSE2023]]
|
||||
**ICSE2023**
|
||||
DONE [[ICSE2023-Poster-6]]
|
||||
-
|
||||
- #### Journals
|
||||
- DONE [[COLA-D-22-00029_reviewer]]
|
||||
- **Tom Mens Book Chapter**
|
||||
- DONE [[REVIEWS-Mining Analyzing and Evolving Data-intensive Software Ecosystems]]
|
||||
date-submitted:: [[04-05-2023]]
|
||||
- ### Projects
|
||||
- DONE [[10-12-SFI-Ireland]]
|
||||
- ### PhD Thesis
|
||||
- DONE [[GSSI PhD Thesis proposal review]]
|
||||
- DONE [[Maxime_Gobert-NAMUR-Cleve]]
|
||||
- DONE [[Antonio Mastropaolo Student of Gabriele Bavota]]
|
||||
@@ -1,86 +0,0 @@
|
||||
icon:: 📜
|
||||
|
||||
- # COLOR SCHEMA
|
||||
id:: 634184dc-a3c1-4816-8b77-af9e091bcc64
|
||||
- [[#green]]==Green -> Everything is ok, it is just to help the reading==
|
||||
- ==Yellow -> Something is not clear. Probably a question is raised. Need for clarification==
|
||||
- [[#red]]==Red -> Typos, unreadable sentence==
|
||||
- Purple -> Key sentence / aspect in the document.
|
||||
background-color:: purple
|
||||
- ## REVIEWS - DOING
|
||||
- {{query (and (property :status [[DOING]]) (or (property :type [[REVIEWS]]) (property :type [[REVIEWS/PhDThesis]]) (property :type [[REVIEWS/PROJECTS]])) (not [[templates]]))}}
|
||||
query-sort-desc:: false
|
||||
query-table:: true
|
||||
query-properties:: [:full-title :deadline :year :venue :page]
|
||||
id:: 9c4a3fe4-9941-4bdd-a55b-b4c76c54d685
|
||||
- ## REVIEWS - DONE
|
||||
collapsed:: true
|
||||
- {{query (and (property :status [[DONE]]) (property :type [[REVIEWS]]) (not [[templates]]))}}
|
||||
query-sort-by:: year
|
||||
query-properties:: [:year :venue :full-title :date-submitted]
|
||||
query-sort-desc:: true
|
||||
query-table:: true
|
||||
- ## OTHER REVIEWS
|
||||
collapsed:: true
|
||||
- DONE [[JSSOFTWARE-D-22-00977_reviewer.pdf]]
|
||||
- DONE [[IoTMoF: A Requirements-Driven Modelling Framework for Adaptive IoT Systems]]
|
||||
- DONE [[TTC-2023]]
|
||||
- DONE [[Software Evolutionary Architecture: Automated Planning for Functional Changes]]
|
||||
- date-submitted:: [[01-05-2023]]
|
||||
- DONE [[TOSEM-2023-0032_Proof_hi]]
|
||||
- DONE [[JSME-23-0044]]
|
||||
- DONE [[JSSOFTWARE-D-22-00977_R1_reviewer]]
|
||||
- DONE [[SCICO-D-22-00337_R1]]
|
||||
- DONE [[JOT-507-Article Text-1015-1-4-20230214]]
|
||||
- SATTOSE 2023
|
||||
collapsed:: true
|
||||
- DONE [[SATToSE_2023_paper_1]]
|
||||
- date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_2]]
|
||||
- date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_3]]
|
||||
- date-submitted:: [[04-05-2023]]
|
||||
- DONE [[SATToSE_2023_paper_5]]
|
||||
- date-submitted:: [[04-05-2023]]
|
||||
- ## 2022
|
||||
collapsed:: true
|
||||
-
|
||||
- ### Papers
|
||||
- #### Conferences
|
||||
id:: 63061068-2bf3-4551-82cd-08565392d81f
|
||||
- **KARS2022**: [[@Recommending scholarly articles to monitor COVID-19 trends in social media based on low-cost topic modeling]]
|
||||
- **ASE2022 Artifact Evaluation** [[CrystalBLEU: Precisely and Efficiently Measuring the Similarity of Code]]
|
||||
- **EMSE 2022** [[EMSE_SelectingThird-party Libraries_The_Data_Scientist_s_Perspective]]
|
||||
- **ICSE 2023**
|
||||
- DONE [[ICSE2023-REVIEW-1237]]
|
||||
- DONE [[ICSE2023-REVIEW-1237-METAREVIEW]]
|
||||
- DONE [[ICSE2023-REVIEW-685]]
|
||||
- DONE [[ICSE2023-REVIEW-2055]]
|
||||
- DONE [[Qualitative Clustering of Software Repositories Based on Software Metrics]]
|
||||
- ((63568355-e57b-4a93-b804-5717bca6402b))
|
||||
- DONE [[ICSE2023-REVIEW-1123]]
|
||||
- [[icse2023-review-1123-metareview]]
|
||||
- DONE [[ICSE2023-REVIEW-1528]]
|
||||
collapsed:: true
|
||||
-
|
||||
- [[01-11-2022]]
|
||||
- - DONE [[ICSE2023-REVIEW-9]] **L**
|
||||
- collapsed:: true
|
||||
- DONE [[ICSE2023-REVIEW-9-METAREVIEW]]
|
||||
- DONE [[ICSE2023-REBUTTAL]]
|
||||
- **ROSE 2023**
|
||||
- [[ROSE2023]]
|
||||
- **ICSE2023**
|
||||
- DONE [[ICSE2023-Poster-6]]
|
||||
- -
|
||||
- - #### Journals
|
||||
- DONE [[COLA-D-22-00029_reviewer]]
|
||||
- **Tom Mens Book Chapter**
|
||||
- - DONE [[REVIEWS-Mining Analyzing and Evolving Data-intensive Software Ecosystems]]
|
||||
- date-submitted:: [[04-05-2023]]
|
||||
- ### Projects
|
||||
- - DONE [[10-12-SFI-Ireland]]
|
||||
- ### PhD Thesis
|
||||
- DONE [[GSSI PhD Thesis proposal review]]
|
||||
- DONE [[Maxime_Gobert-NAMUR-Cleve]]
|
||||
- DONE [[Antonio Mastropaolo Student of Gabriele Bavota]]
|
||||
@@ -1,50 +0,0 @@
|
||||
icon:: 👨🏫
|
||||
|
||||
- **ORARIO 2022/2023**
|
||||
|
||||
|ORA|LUNEDI|MARTEDI|MERCOLEDI|GIOVEDI|VENERDI|
|
||||
|--|--|--|--|--|--|
|
||||
|9:30 - 11:30|SE4IOT (from 10:30)|||||
|
||||
|11:30 - 13:30|SE4IOT||||S3S (11:30-13:30)|
|
||||
|14:30 - 16:30|SE4AS|SE4AS||| SE4IOT|
|
||||
|17:00 - 19:00||S3F||||
|
||||
- _S3F - Scienze dell'educazione e della formazione_ (L39)
|
||||
- _DQ0570 - Multimedialità per le scienze sociali e dell'educazione - 6 cfu- 36 ore -** _(obbligatorio)_
|
||||
- martedì 17.00-19.00 (Davide) - aula 2A
|
||||
- Venerdì 11:30-13:30 (Monica) - aula 2A
|
||||
- [[Lezioni fatte]]
|
||||
- |Data | Contentuto|
|
||||
|11/10/2022 | Intro|
|
||||
|18/10/2022 | Intro / CMS|
|
||||
|25/10/2022| Non fatta per via di MODELS |
|
||||
|8/11/2022 | CMS / Wordpress su mio sito Web|
|
||||
|15/11/2022 | No per via sessione fuori corso|
|
||||
|22/11/2022 |Installazione MAMP|
|
||||
|29/11/2022 | Installazione MAMP |
|
||||
|06/12/2022 | Installazione MAMP |
|
||||
|13/12/2022 | Crezione nuove pagine, Immagini, Galleria immagini, Integrazione con PayPal, Modifica template, Chiesto di vedere da sole la creazione di form di registrazione guardando la video lezione messa a disposizione|
|
||||
|20/12/2022 | Fatta lezione a 4-5 studentesse fatti tutti i plugin incluso SMTP|
|
||||
|10/01/2022 | Fatta ultima lezione ad una decina di studentesse. Rivisto un po tutto quanto.|
|
||||
-
|
||||
-
|
||||
- _S3S - Scienze del servizio sociale_ (L19)
|
||||
- **DQ0520 -** **Multimedialità e informatica per le scienze sociali - 8 cfu - 48 ore** - (opzionale)
|
||||
- Lunedì 15:00-17:00 (Marco) - aula 4C (25 posti)
|
||||
- giovedì 08.30-10.30 (Monica)- aula 3B (43posti)
|
||||
- Venerdì 11:30 - 13:30 (Davide)- aula 4C
|
||||
- [[Lezioni fatte]]
|
||||
- TODO |Data | Contentuto|
|
||||
|14/10/2022 |Nessuno in aula (per via di un tirocinio)|
|
||||
|21/10/2022 |Intro|
|
||||
|28/10/2022 | Non fatta per via della Conferenza MODELS 2022|
|
||||
|4/11/2022| Intro|
|
||||
|11/11/2022 |CMS / Wordpress|
|
||||
|18/11/2022 |No perche' non c'era nessuno per via di un tirocinio|
|
||||
|25/11/2022 | Fatta lezione facendo cominciare ad installare i software sulle macchine delle studentesse|
|
||||
|2/12/2022 |No perche' non c'era nessuno per via di un tirocinio|
|
||||
| 9/12/2022| No perche' hanno chiesto di fare ponte|
|
||||
|16/12/2022| No perche' non c'era nessuno |
|
||||
|13/01/2022| Fatta ultima lezione. Due studentesse in aula.|
|
||||
-
|
||||
- [[Ideas]]
|
||||
- Bisogna raffinare un pochino i requisiti del progetto #TEACHING/SE4AS
|
||||
@@ -1,53 +0,0 @@
|
||||
- {{embed [[Inbox]]}}
|
||||
- {{embed [[BRAINSTORMING]]}}
|
||||
query-properties:: [:page :updated-at]
|
||||
query-sort-by:: updated-at
|
||||
query-sort-desc:: true
|
||||
#+BEGIN_QUERY
|
||||
{:title [:h2 "Recent changes"]
|
||||
:query [:find (pull ?b [* {:block/_parent ...}])
|
||||
:in $ ?end
|
||||
:where
|
||||
[?b :block/updated-at ?v]
|
||||
[(- ?end 86400000 ) ?period]
|
||||
[(>= ?v ?period)]
|
||||
[(< ?v ?end)]
|
||||
]
|
||||
:inputs [:end-of-today-ms]
|
||||
}
|
||||
#+END_QUERY
|
||||
|
||||
- {{embed ((6481f453-50b6-4442-8ec6-b9e43aed9b3e))}}
|
||||
- <iframe src="https://indify.co/widgets/live/clock/eaVjMwEPyamrxNI3tqoR" style="width: 100%; height: 220px"></iframe>
|
||||
id:: 644bb986-2554-46ff-b8bd-859586cd10b9
|
||||
- <iframe src="https://indify.co/widgets/live/weather/s14YWaczVaA9fraNV8YR" style="width: 100%; height: 520px"></iframe>
|
||||
- ## Areas of focus
|
||||
- [[WORK]]
|
||||
- [[PAPERS]]
|
||||
- [[REVIEWS]]
|
||||
- [[SERVICES]]
|
||||
- [[SERVICES/PLACEMENT-ATENEO]]
|
||||
- [[SERVICES/ORIENTAMENTO]]
|
||||
- [[SERVICES/ORIENTAMENTO/CADINFORMATICA]]
|
||||
- [[SERVICES/DOTTORATO]]
|
||||
- #TEACHING **(132 ore)**
|
||||
- {{namespace [[TEACHING]] }}
|
||||
- #TEACHING/SE4AS - DISIM - 48 ore
|
||||
- #TEACHING/SE4IOT - DISIM - 48 ore
|
||||
- #TEACHING/DSU-S3F - **DQ0570 - Multimedialità per le scienze sociali e d****ell'educazione - 6 cfu- 36 ore - ***(obbligatorio)* - S3F *-Scienze dell'educazione e della formazione*
|
||||
collapsed:: true
|
||||
- prof.ssa Nesi 3cfu - 18 ore
|
||||
prof. Di Ruscio 3cfu- 18 ore
|
||||
- #TEACHING/DSU-S3S **DQ0520 - **** Multimedialità e informatica per le scienze sociali - 8 cfu - 48 ore** - *(opzionale)* - **S3S - Scienze del servizio sociale**
|
||||
collapsed:: true
|
||||
- prof. Autili 2 cfu -12 ore
|
||||
prof.ssa Nesi 3cfu - 18 ore
|
||||
prof. Di Ruscio 3cfu - 18 ore
|
||||
- #MENTORING
|
||||
- #Projects
|
||||
- #PERSONAL
|
||||
- #PERSONAL/CASA
|
||||
- [[Lavori Ristrutturazione]]
|
||||
- #PERSONAL/HEALTH
|
||||
- #PERSONAL/FAMILY
|
||||
-
|
||||
@@ -1,148 +0,0 @@
|
||||
template:: JOURNAL-TEMPLATE
|
||||
|
||||
- #.tabular
|
||||
- ### 🗒️Notes
|
||||
- 
|
||||
- ### 📜Reviews
|
||||
- {{query (and [[REVIEWS]] (or (property :date-end <%today%>) (property :date-start <%today%>) (property :date-submitted <%today%>)))}}
|
||||
query-table:: true
|
||||
query-properties:: [:file :year :venue :deadline]
|
||||
-
|
||||
- type:: [[JournalPaper]], [[conferencepaper]], [[WorkshopPaper]], [[Bookchapter]]
|
||||
template:: PAPERS
|
||||
date:: <%today%> - <%time%>
|
||||
full-title::
|
||||
external-links::
|
||||
todoist::
|
||||
year::
|
||||
date-start::
|
||||
status:: [[DOING]], [[DONE]], [[SUBMITTED]], [[REJECTED]] [[UNDER-REVISION]]
|
||||
venue::
|
||||
priority:: [[P1]] [[P2]] [[P3]] [[P4]]
|
||||
parent::
|
||||
leader::
|
||||
todoist::
|
||||
progress:: {{renderer :todomaster}}
|
||||
- #.tabular
|
||||
- ## MEETINGS
|
||||
- {{query (and <%current page%> (block-property :type [[meeting]]) (not (page <%current page%>)))}}
|
||||
- query-table:: true
|
||||
- ## READINGS
|
||||
- #+BEGIN_QUERY
|
||||
{:title "Related readings in Omnivore"
|
||||
:query [:find (pull ?b [*] )
|
||||
:in $ ?current-page
|
||||
:where
|
||||
[?b :block/page ?p]
|
||||
[?p :block/name ?p-name]
|
||||
[?b :block/content ?c]
|
||||
[(clojure.string/includes? ?c ?current-page)]
|
||||
[(clojure.string/includes? ?p-name "omnivore")]
|
||||
]
|
||||
:inputs [:current-page]}
|
||||
#+END_QUERY
|
||||
-
|
||||
- ## TASKs
|
||||
-
|
||||
- ## ❓️ QUESTIONS TO ANSWER
|
||||
{{query (and [[question]]<%current page%>)}}
|
||||
- ## [[PAPERS/NOTES]]
|
||||
-
|
||||
- type:: [[weblink]]
|
||||
template:: WEBLINK
|
||||
source::
|
||||
tags:: [[readingnotes]]
|
||||
date:: <%today%> - <%time%>
|
||||
- type:: [[CAD]]
|
||||
template:: CAD
|
||||
corso:: [[Ingegneria Informatica]], [[Informatica]], [[TEACHING/DSU-S3S]], [[TEACHING/DSU-S3F]]
|
||||
|
||||
date:: <%today%> - <%time%>
|
||||
- type:: [[REVIEWS]]
|
||||
tags::
|
||||
year::
|
||||
venue::
|
||||
template:: REVIEW
|
||||
full-title::
|
||||
date-start:: <%today%> - <%time%>
|
||||
date-submitted::
|
||||
external-links::
|
||||
status:: [[DOING]]
|
||||
deadline-submission::
|
||||
file::
|
||||
parent::
|
||||
todoist::
|
||||
collapsed:: true
|
||||
- ### [[Highlights]]
|
||||
- ### [[Comments]]
|
||||
- #.tabular
|
||||
- - ### Paper summary
|
||||
-
|
||||
- - ### Strengths
|
||||
- +
|
||||
- - ### Weaknesses
|
||||
- -
|
||||
- - ### Detailed comments for authors
|
||||
- Novelty:
|
||||
- Rigor:
|
||||
- Relevance:
|
||||
- Verifiability & transparency:
|
||||
- Presentation:
|
||||
- Detailed comments:
|
||||
- ### [[REVIEWS/Notes]]
|
||||
- ### YELLOW CONCERNS
|
||||
background-color:: yellow
|
||||
- {{query (and [[ffd400]] <%current page%> )}}
|
||||
collapsed:: true
|
||||
- ### ❓️Questions
|
||||
- {{query (and [[question]] <%current page%> )[[question]]}}
|
||||
query-table:: true
|
||||
query-properties:: [:block]
|
||||
- type:: [[Contact]]
|
||||
page-type:: [[people]]
|
||||
date:: <%today%> - <%time%>
|
||||
template:: CONTACT
|
||||
name::
|
||||
struttura::
|
||||
email::
|
||||
- type:: [[meeting]]
|
||||
template:: ConsiglioDisim
|
||||
external-links::
|
||||
tags:: [[SERVICES/ConsiglioDisim]] [[Convocazioni]]
|
||||
date:: <%today%> - <%time%>
|
||||
duration-min::
|
||||
file-brogliaccio::
|
||||
file-odg::
|
||||
- type:: [[meeting]]
|
||||
template:: MEETING
|
||||
external-links::
|
||||
tags::
|
||||
people::
|
||||
date:: <%today%> - <%time%>
|
||||
duration::
|
||||
- template:: VENUE
|
||||
date:: <%today%> - <%time%>
|
||||
full-title::
|
||||
link::
|
||||
type:: [[JOURNAL]] [[CONFERENCE]] [[WORKSHOP]]
|
||||
ranking-link::
|
||||
- template:: QUERY-QUESTIONS
|
||||
template-including-parent:: false
|
||||
- ### Questions
|
||||
- {{query (and [[question]] <%current page%> )[[question]]}}
|
||||
- template:: QUERY-IDEAS
|
||||
template-including-parent:: false
|
||||
- ### Ideas
|
||||
- {{query (and [[Ideas]] <%current page%>)}}
|
||||
- template:: QUERY-TASKS
|
||||
template-including-parent:: false
|
||||
- ### TASKS
|
||||
- {{query (and <%current page%> (task TODO DOING) (not [[GOALS-TODOIST]]))}}
|
||||
- template:: BOOX-NOTES
|
||||
- 
|
||||
- template:: PHD-task
|
||||
- tags:: [[SERVICES/PHDICT]] #todoist-task
|
||||
- {{query (and <%current page%> (task TODO DOING) (not [[GOALS-TODOIST]]))}}
|
||||
query-table:: true
|
||||
query-properties:: [:block :page]
|
||||
- ---
|
||||
+1
-1
@@ -250,7 +250,7 @@
|
||||
:ref/linked-references-collapsed-threshold 0
|
||||
|
||||
;; Favorites to list on the left sidebar
|
||||
:favorites ["desktop" "inbox" "todoist-logseqed" "planner" "diario" "brainstorming" "reviews" "services/phdict" "cv empower" "projects" "services/dottorato" "papers" "teaching" "books" "todoist-dashboard" "consigliodisim" "services/placement" "writing challenges" "ideas"]
|
||||
:favorites ["KaraKeep-Highlights" "planner" "call per posizioni mosaico" "desktop" "inbox" "todoist-logseqed" "diario" "brainstorming" "reviews" "services/phdict" "cv empower" "projects" "services/dottorato" "papers" "teaching" "books" "todoist-dashboard" "consigliodisim" "services/placement" "writing challenges" "clip" "ideas"]
|
||||
|
||||
;; any number between 0 and 1 (the greater it is the faster the changes of the next-interval of card reviews) (default 0.5)
|
||||
;; :srs/learning-fraction 0.5
|
||||
|
||||
+4
-1
@@ -1 +1,4 @@
|
||||
|
||||
:root {
|
||||
--ls-main-content-max-width: 90%;
|
||||
--ls-main-content-max-width-wide: 95%;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user