diff --git a/assets/2022-10-24-AQ_Dottorato_1729074079098_0.edn b/assets/2022-10-24-AQ_Dottorato_1729074079098_0.edn
index a9d2243d..a6a5053f 100644
--- a/assets/2022-10-24-AQ_Dottorato_1729074079098_0.edn
+++ b/assets/2022-10-24-AQ_Dottorato_1729074079098_0.edn
@@ -21,4 +21,4 @@
:page 14},
:content {:text "calendario di attività formative (corsi, seminari, eventi scientifici…)"},
:properties {:color "green"}}],
- :extra {:page 14}}
+ :extra {:page 13}}
diff --git a/assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.edn b/assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.pdf b/assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.pdf
new file mode 100644
index 00000000..c472d90a
Binary files /dev/null and b/assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.pdf differ
diff --git a/assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.edn b/assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.edn
new file mode 100644
index 00000000..c3eb3071
--- /dev/null
+++ b/assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 7}}
diff --git a/assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.pdf b/assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.pdf
new file mode 100644
index 00000000..cf8e30e4
Binary files /dev/null and b/assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.pdf differ
diff --git a/assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.edn b/assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.pdf b/assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.pdf
new file mode 100644
index 00000000..a4ca05ae
Binary files /dev/null and b/assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.pdf differ
diff --git a/assets/22_03_22_Linee_Guida_accreditamento_dottorati_1731926835562_0.edn b/assets/22_03_22_Linee_Guida_accreditamento_dottorati_1731926835562_0.edn
index a69b66da..a0b88a48 100644
--- a/assets/22_03_22_Linee_Guida_accreditamento_dottorati_1731926835562_0.edn
+++ b/assets/22_03_22_Linee_Guida_accreditamento_dottorati_1731926835562_0.edn
@@ -130,4 +130,4 @@
:page 8},
:content {:text "della valorizzazione e disseminazione dei risultati, della proprietà intellettuale e dell'accesso aperto ai dati e ai prodotti della ricerca, dei principi fondamentali di etica, uguaglianza di genere e integrità;"},
:properties {:color "green"}}],
- :extra {:page 1}}
+ :extra {:page 9}}
diff --git a/assets/7-002832007-UNAQCLE-5ca08ba8-2c0b-460a-8ffc-3b4421f18e62-000_1748620314246_0.edn b/assets/7-002832007-UNAQCLE-5ca08ba8-2c0b-460a-8ffc-3b4421f18e62-000_1748620314246_0.edn
index d89c87b9..ab9a38bd 100644
--- a/assets/7-002832007-UNAQCLE-5ca08ba8-2c0b-460a-8ffc-3b4421f18e62-000_1748620314246_0.edn
+++ b/assets/7-002832007-UNAQCLE-5ca08ba8-2c0b-460a-8ffc-3b4421f18e62-000_1748620314246_0.edn
@@ -1 +1 @@
-{:highlights [], :extra {:page 2}}
+{:highlights [], :extra {:page 1}}
diff --git a/assets/ACN_Dottorati_XLI_ciclo_BANDO_24-02-2025_1742225261475_0.edn b/assets/ACN_Dottorati_XLI_ciclo_BANDO_24-02-2025_1742225261475_0.edn
index f55aedae..69bf1f94 100644
--- a/assets/ACN_Dottorati_XLI_ciclo_BANDO_24-02-2025_1742225261475_0.edn
+++ b/assets/ACN_Dottorati_XLI_ciclo_BANDO_24-02-2025_1742225261475_0.edn
@@ -375,4 +375,4 @@
:page 7},
:content {:text "entro e non oltre le ore 18:00 del 26/03/2025"},
:properties {:color "green"}}],
- :extra {:page 5}}
+ :extra {:page 6}}
diff --git a/assets/BRAINSTORMING.edn b/assets/BRAINSTORMING.edn
index 5d9ecfee..6b31acf2 100644
--- a/assets/BRAINSTORMING.edn
+++ b/assets/BRAINSTORMING.edn
@@ -1 +1 @@
-{:highlights [], :extra {:page 3}}
+{:highlights [], :extra {:page 12}}
diff --git a/assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1755685109982_0.pdf b/assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1755685109982_0.pdf
new file mode 100644
index 00000000..578c5ca9
Binary files /dev/null and b/assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1755685109982_0.pdf differ
diff --git a/assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1755685122002_0.pdf b/assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1755685122002_0.pdf
new file mode 100644
index 00000000..578c5ca9
Binary files /dev/null and b/assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1755685122002_0.pdf differ
diff --git a/assets/Calendario_scadenze_Coordinatori_1764006171407_0.edn b/assets/Calendario_scadenze_Coordinatori_1764006171407_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/Calendario_scadenze_Coordinatori_1764006171407_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/Calendario_scadenze_Coordinatori_1764006171407_0.pdf b/assets/Calendario_scadenze_Coordinatori_1764006171407_0.pdf
new file mode 100644
index 00000000..ac15cb72
Binary files /dev/null and b/assets/Calendario_scadenze_Coordinatori_1764006171407_0.pdf differ
diff --git a/assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.edn b/assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.edn
new file mode 100644
index 00000000..5d9ecfee
--- /dev/null
+++ b/assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 3}}
diff --git a/assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.pdf b/assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.pdf
new file mode 100644
index 00000000..47bf07e8
Binary files /dev/null and b/assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.pdf differ
diff --git a/assets/Convocazione-Audizione-2025_1759759982455_0.edn b/assets/Convocazione-Audizione-2025_1759759982455_0.edn
new file mode 100644
index 00000000..5d9ecfee
--- /dev/null
+++ b/assets/Convocazione-Audizione-2025_1759759982455_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 3}}
diff --git a/assets/Convocazione-Audizione-2025_1759759982455_0.pdf b/assets/Convocazione-Audizione-2025_1759759982455_0.pdf
new file mode 100644
index 00000000..e0c696cb
Binary files /dev/null and b/assets/Convocazione-Audizione-2025_1759759982455_0.pdf differ
diff --git a/assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.edn b/assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.edn
new file mode 100644
index 00000000..31ce1173
--- /dev/null
+++ b/assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.edn
@@ -0,0 +1,35 @@
+{:highlights [{:id #uuid "69429a33-8e6f-447d-ac26-253af028914b",
+ :page 1,
+ :position {:bounding {:x1 41.503676891326904,
+ :y1 419.08990478515625,
+ :x2 194.35385084152222,
+ :y2 431.35888671875,
+ :width 580.0000000000001,
+ :height 820.2539810522072},
+ :rects ({:x1 41.503676891326904,
+ :y1 419.08990478515625,
+ :x2 194.35385084152222,
+ :y2 431.35888671875,
+ :width 580.0000000000001,
+ :height 820.2539810522072}),
+ :page 1},
+ :content {:text "5. BILANCIO E CONTABILITÀ"},
+ :properties {:color "green"}}
+ {:id #uuid "69429b19-0a88-450b-ad31-ee8a9bf8884d",
+ :page 1,
+ :position {:bounding {:x1 50.157692447304726,
+ :y1 558.0197409391403,
+ :x2 123.54506732523441,
+ :y2 572.0414084196091,
+ :width 701,
+ :height 991.3759322717193},
+ :rects ({:x1 50.157692447304726,
+ :y1 558.0197409391403,
+ :x2 123.54506732523441,
+ :y2 572.0414084196091,
+ :width 701,
+ :height 991.3759322717193}),
+ :page 1},
+ :content {:text "9. RICERCA"},
+ :properties {:color "green"}}],
+ :extra {:page 1}}
diff --git a/assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.pdf b/assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.pdf
new file mode 100644
index 00000000..cee05ff5
Binary files /dev/null and b/assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.pdf differ
diff --git a/assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.edn b/assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.pdf b/assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.pdf
new file mode 100644
index 00000000..c3f276fd
Binary files /dev/null and b/assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.pdf differ
diff --git a/assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.edn b/assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.edn
new file mode 100644
index 00000000..d89c87b9
--- /dev/null
+++ b/assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 2}}
diff --git a/assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.pdf b/assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.pdf
new file mode 100644
index 00000000..a8511a57
Binary files /dev/null and b/assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.pdf differ
diff --git a/assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.edn b/assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.pdf b/assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.pdf
new file mode 100644
index 00000000..394298bb
Binary files /dev/null and b/assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.pdf differ
diff --git a/assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.edn b/assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.edn
new file mode 100644
index 00000000..b3b08558
--- /dev/null
+++ b/assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.edn
@@ -0,0 +1,167 @@
+{:highlights [{:id #uuid "68ef936d-6021-40e8-993e-c78676f55faf",
+ :page 1,
+ :position {:bounding {:x1 90.22359895706177,
+ :y1 764.4427337646484,
+ :x2 641.4515042304993,
+ :y2 792.1437835693359,
+ :width 701.0000000000001,
+ :height 992.1171843485276},
+ :rects ({:x1 90.22359895706177,
+ :y1 764.4427337646484,
+ :x2 641.4515042304993,
+ :y2 777.5880584716797,
+ :width 701.0000000000001,
+ :height 992.1171843485276}
+ {:x1 90.22359895706177,
+ :y1 778.9984588623047,
+ :x2 180.65003633499146,
+ :y2 792.1437835693359,
+ :width 701.0000000000001,
+ :height 992.1171843485276}),
+ :page 1},
+ :content {:text "Approvazione relazione attività Assegno di Ricerca dott. Claudio Di Sipio – responsabile scientifico prof. Davide Di Ruscio."},
+ :properties {:color "green"}}
+ {:id #uuid "68ef937a-3d89-4739-b4a2-e73c924a79fc",
+ :page 1,
+ :position {:bounding {:x1 90.22359895706177,
+ :y1 793.5678558349609,
+ :x2 641.4515042304993,
+ :y2 821.4058685302734,
+ :width 701.0000000000001,
+ :height 992.1171843485276},
+ :rects ({:x1 90.22359895706177,
+ :y1 793.5678558349609,
+ :x2 641.4515042304993,
+ :y2 806.7131805419922,
+ :width 701.0000000000001,
+ :height 992.1171843485276}
+ {:x1 90.22359895706177,
+ :y1 808.2605438232422,
+ :x2 180.65003633499146,
+ :y2 821.4058685302734,
+ :width 701.0000000000001,
+ :height 992.1171843485276}),
+ :page 1},
+ :content {:text "Approvazione relazione attività Assegno di Ricerca dott. Riccardo Rubei – responsabile scientifico prof. Davide Di Ruscio."},
+ :properties {:color "green"}}
+ {:id #uuid "68ef942a-5b23-422b-8d88-4c49778a16d7",
+ :page 2,
+ :position {:bounding {:x1 90.22359895706177,
+ :y1 473.12278747558594,
+ :x2 648.911648273468,
+ :y2 500.8512420654297,
+ :width 701.0000000000001,
+ :height 992.1171843485276},
+ :rects ({:x1 90.22359895706177,
+ :y1 473.12278747558594,
+ :x2 648.911648273468,
+ :y2 486.2681121826172,
+ :width 701.0000000000001,
+ :height 992.1171843485276}
+ {:x1 90.22359895706177,
+ :y1 487.7058563232422,
+ :x2 149.16775178909302,
+ :y2 500.8512420654297,
+ :width 701.0000000000001,
+ :height 992.1171843485276}),
+ :page 2},
+ :content {:text "Richiesta proroga Borsa di Ricerca dott. Damiano Di Vincenzo – responsabile scientifico prof. Alfonso Pierantonio"},
+ :properties {:color "green"}}
+ {:id #uuid "68ef94d6-f616-4fa4-95ad-754fb3874601",
+ :page 3,
+ :position {:bounding {:x1 90.22359895706177,
+ :y1 590.0752258300781,
+ :x2 635.155056476593,
+ :y2 617.7762756347656,
+ :width 701.0000000000001,
+ :height 992.1171843485276},
+ :rects ({:x1 90.22359895706177,
+ :y1 590.0752258300781,
+ :x2 635.155056476593,
+ :y2 603.2205505371094,
+ :width 701.0000000000001,
+ :height 992.1171843485276}
+ {:x1 90.22359895706177,
+ :y1 604.6309509277344,
+ :x2 121.60425233840942,
+ :y2 617.7762756347656,
+ :width 701.0000000000001,
+ :height 992.1171843485276}),
+ :page 3},
+ :content {:text "Approvazione relazione tecnico-scientifica RTD b) secondo anno (01.10.2024 – 30.09.2025) dott. Juri Di Rocco"},
+ :properties {:color "green"}}
+ {:id #uuid "68ef9735-4af7-4e7e-909d-98d1f1196f19",
+ :page 1,
+ :position {:bounding {:x1 84.6642210483551,
+ :y1 509.95709228515625,
+ :x2 199.25085282325745,
+ :y2 524.8551635742188,
+ :width 807.0000000000001,
+ :height 1142.1377571601452},
+ :rects ({:x1 84.6642210483551,
+ :y1 509.95709228515625,
+ :x2 199.25085282325745,
+ :y2 524.8551635742188,
+ :width 807.0000000000001,
+ :height 1142.1377571601452}),
+ :page 1},
+ :content {:text "COMUNICAZIONI"},
+ :properties {:color "green"}}
+ {:id #uuid "68ef9bb4-c1e9-4a97-85a3-9a80679645ab",
+ :page 1,
+ :position {:bounding {:x1 103.86189103126526,
+ :y1 560.4434356689453,
+ :x2 328.63703751564026,
+ :y2 575.3415069580078,
+ :width 807.0000000000001,
+ :height 1142.1377571601452},
+ :rects ({:x1 103.86189103126526,
+ :y1 560.4434356689453,
+ :x2 328.63703751564026,
+ :y2 575.3415069580078,
+ :width 807.0000000000001,
+ :height 1142.1377571601452}),
+ :page 1},
+ :content {:text "Nomina Commissioni di Dipartimento"},
+ :properties {:color "green"}}
+ {:id #uuid "68ef9c5e-f8c7-45e8-8b2d-8eb38117c8d5",
+ :page 1,
+ :position {:bounding {:x1 103.86189103126526,
+ :y1 577.3680572509766,
+ :x2 738.2478773593903,
+ :y2 609.0401153564453,
+ :width 807.0000000000001,
+ :height 1142.1377571601452},
+ :rects ({:x1 103.86189103126526,
+ :y1 577.3680572509766,
+ :x2 738.2478773593903,
+ :y2 592.2661285400391,
+ :width 807.0000000000001,
+ :height 1142.1377571601452}
+ {:x1 103.86189103126526,
+ :y1 594.1420745849609,
+ :x2 384.1461317539215,
+ :y2 609.0401153564453,
+ :width 807.0000000000001,
+ :height 1142.1377571601452}),
+ :page 1},
+ :content {:text "Nomina Commissione didattica paritetica docenti-studenti DISIM triennio accademico 2025/20262026/2027-2027/2028 – sostituzione membro"},
+ :properties {:color "green"}}
+ {:id #uuid "68ef9cd5-4623-42a3-b5d6-75212323e48b",
+ :page 1,
+ :position {:bounding {:x1 103.86189103126526,
+ :y1 610.9023895263672,
+ :x2 300.34565567970276,
+ :y2 625.8004302978516,
+ :width 807.0000000000001,
+ :height 1142.1377571601452},
+ :rects ({:x1 103.86189103126526,
+ :y1 610.9023895263672,
+ :x2 300.34565567970276,
+ :y2 625.8004302978516,
+ :width 807.0000000000001,
+ :height 1142.1377571601452}),
+ :page 1},
+ :content {:text "Nomina Delegati di Dipartimento"},
+ :properties {:color "green"}}],
+ :extra {:page 3}}
diff --git a/assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.pdf b/assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.pdf
new file mode 100644
index 00000000..98de71e2
Binary files /dev/null and b/assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.pdf differ
diff --git a/assets/Convocazione_candidati_ICT_XXXVII_ciclo_1764598160633_0.pdf b/assets/Convocazione_candidati_ICT_XXXVII_ciclo_1764598160633_0.pdf
new file mode 100644
index 00000000..3773dd4e
Binary files /dev/null and b/assets/Convocazione_candidati_ICT_XXXVII_ciclo_1764598160633_0.pdf differ
diff --git a/assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.edn b/assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.edn
new file mode 100644
index 00000000..62ad2e79
--- /dev/null
+++ b/assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 33}}
diff --git a/assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.pdf b/assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.pdf
new file mode 100644
index 00000000..549f6b34
Binary files /dev/null and b/assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.pdf differ
diff --git a/assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.edn b/assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.edn
new file mode 100644
index 00000000..427d3849
--- /dev/null
+++ b/assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.edn
@@ -0,0 +1,527 @@
+{:highlights [{:id #uuid "68ecf9ce-81bc-471c-94f4-06be923f5ff1",
+ :page 2,
+ :position {:bounding {:x1 108.08391571044922,
+ :y1 294.10417556762695,
+ :x2 243.2882843017578,
+ :y2 312.3615913391113,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 108.08391571044922,
+ :y1 294.10417556762695,
+ :x2 120.72718048095703,
+ :y2 312.3615913391113,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 145.87677001953125,
+ :y1 294.10417556762695,
+ :x2 243.2882843017578,
+ :y2 312.3615913391113,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 2},
+ :content {:text "1 NISAR Fatima"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecf9e5-04a9-4045-99da-a1e3cb737b35",
+ :page 2,
+ :position {:bounding {:x1 108.08391571044922,
+ :y1 319.8927803039551,
+ :x2 282.9935607910156,
+ :y2 338.15019607543945,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 108.08391571044922,
+ :y1 319.8927803039551,
+ :x2 120.72718048095703,
+ :y2 338.15019607543945,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 145.87677001953125,
+ :y1 319.8927803039551,
+ :x2 282.9935607910156,
+ :y2 338.15019607543945,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 2},
+ :content {:text "2 PELLONE Katiuscia"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecf9fd-fe29-4224-9cd8-9014f68fdced",
+ :page 2,
+ :position {:bounding {:x1 108.08391571044922,
+ :y1 345.71562576293945,
+ :x2 265.15765380859375,
+ :y2 363.9730415344238,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 108.08391571044922,
+ :y1 345.71562576293945,
+ :x2 120.72718048095703,
+ :y2 363.9730415344238,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 145.87677001953125,
+ :y1 345.71562576293945,
+ :x2 265.15765380859375,
+ :y2 363.9730415344238,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 2},
+ :content {:text "3 GIONA Valentino"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfa05-7d25-4847-8fab-05a52f7f7f96",
+ :page 2,
+ :position {:bounding {:x1 108.08391571044922,
+ :y1 371.3216438293457,
+ :x2 258.80169677734375,
+ :y2 389.5790596008301,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 108.08391571044922,
+ :y1 371.3216438293457,
+ :x2 120.72718048095703,
+ :y2 389.5790596008301,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 145.87677001953125,
+ :y1 371.3216438293457,
+ :x2 258.80169677734375,
+ :y2 389.5790596008301,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 2},
+ :content {:text "4 COLLI Giordano"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfa0e-4146-47ce-9b9f-225e708dc1cf",
+ :page 2,
+ :position {:bounding {:x1 108.08391571044922,
+ :y1 397.0988349914551,
+ :x2 274.1503601074219,
+ :y2 415.3562812805176,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 108.08391571044922,
+ :y1 397.0988349914551,
+ :x2 120.72718048095703,
+ :y2 415.3562812805176,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 145.87677001953125,
+ :y1 397.0988349914551,
+ :x2 274.1503601074219,
+ :y2 415.3562812805176,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 2},
+ :content {:text "5 GRANDE Federico"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfa16-6986-4f5e-a69b-e793c43b7a61",
+ :page 2,
+ :position {:bounding {:x1 108.08391571044922,
+ :y1 422.87602615356445,
+ :x2 338.464111328125,
+ :y2 441.13347244262695,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 108.08391571044922,
+ :y1 422.87602615356445,
+ :x2 120.72718048095703,
+ :y2 441.13347244262695,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 145.87677001953125,
+ :y1 422.87602615356445,
+ :x2 338.464111328125,
+ :y2 441.13347244262695,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 2},
+ :content {:text "6 RAZA Muhammad Mudassar"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfab2-c50c-4c53-8e7a-9d8ff511c9f7",
+ :page 3,
+ :position {:bounding {:x1 132.4575653076172,
+ :y1 423.2297878265381,
+ :x2 247.10292053222656,
+ :y2 441.48720359802246,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 132.4575653076172,
+ :y1 423.2297878265381,
+ :x2 247.10292053222656,
+ :y2 441.48720359802246,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 3},
+ :content {:text "NANNI Gianluca"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfac2-4348-442e-8e26-fa99e988033f",
+ :page 3,
+ :position {:bounding {:x1 114.62235260009766,
+ :y1 374.14015769958496,
+ :x2 792.75537109375,
+ :y2 411.12282371520996,
+ :width 876.0000000000001,
+ :height 1238.8663575891958},
+ :rects ({:x1 332.41845703125,
+ :y1 374.14015769958496,
+ :x2 792.75537109375,
+ :y2 392.39757347106934,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}
+ {:x1 114.62235260009766,
+ :y1 392.8654079437256,
+ :x2 524.3451614379883,
+ :y2 411.12282371520996,
+ :width 876.0000000000001,
+ :height 1238.8663575891958}),
+ :page 3},
+ :content {:text "Metodologie di progetto a livello sistema per applicazioni real-time embedded su piattaforme parallele eterogenee riconfigurabili”"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfb18-f881-4bfd-bbea-69920b5aa74d",
+ :page 3,
+ :position {:bounding {:x1 111.29037518799305,
+ :y1 624.6547393798828,
+ :x2 243.62242932617664,
+ :y2 639.9909820556641,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 111.29037518799305,
+ :y1 624.6547393798828,
+ :x2 243.62242932617664,
+ :y2 639.9909820556641,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 3},
+ :content {:text "MUGHAL Abdul Basit "},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfb2f-0d34-426c-ac2f-bd8ec548147c",
+ :page 3,
+ :position {:bounding {:x1 111.29037518799305,
+ :y1 738.7750396728516,
+ :x2 297.0883793383837,
+ :y2 754.1112213134766,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 111.29037518799305,
+ :y1 738.7750396728516,
+ :x2 297.0883793383837,
+ :y2 754.1112213134766,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 3},
+ :content {:text "GANESH Venkata Subramaniyan"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfb4e-6d06-407d-8ae4-71387deb5c0d",
+ :page 3,
+ :position {:bounding {:x1 96.30788464844227,
+ :y1 697.6844024658203,
+ :x2 665.9007648974657,
+ :y2 728.7448272705078,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 279.1644367724657,
+ :y1 697.6844024658203,
+ :x2 665.9007648974657,
+ :y2 713.0206451416016,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}
+ {:x1 96.30788464844227,
+ :y1 713.4086456298828,
+ :x2 464.94118542969227,
+ :y2 728.7448272705078,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 3},
+ :content {:text "rogettazione e Sviluppo di Ambienti Intelligenti per la Valorizzazione del Patrimonio Culturale tramite Gamification e Realtà Aumentata"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfb5d-37f6-4fa8-b320-3c2c845af8dd",
+ :page 3,
+ :position {:bounding {:x1 96.30788464844227,
+ :y1 567.6801910400391,
+ :x2 665.832954838872,
+ :y2 614.4647979736328,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 284.67874951660633,
+ :y1 567.6801910400391,
+ :x2 665.6892780810595,
+ :y2 583.0164337158203,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}
+ {:x1 96.30788464844227,
+ :y1 583.4043731689453,
+ :x2 665.832954838872,
+ :y2 598.7406158447266,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}
+ {:x1 96.30788464844227,
+ :y1 599.1286163330078,
+ :x2 209.2446827441454,
+ :y2 614.4647979736328,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 3},
+ :content {:text "Sistema di raccolta e analisi di dati provenienti da un sistema di videosorveglianza di una rete di comuni del cratere del sisma 2009 per la progettazione di un sistema di Smart Urban Living"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfb71-cc6f-4d08-b54d-44b2644e2594",
+ :page 3,
+ :position {:bounding {:x1 111.29037518799305,
+ :y1 892.3541259765625,
+ :x2 215.00704236328602,
+ :y2 907.6903686523438,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 111.29037518799305,
+ :y1 892.3541259765625,
+ :x2 215.00704236328602,
+ :y2 907.6903686523438,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 3},
+ :content {:text "BILAL Hafiz Anas"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfb98-9a60-4033-8b40-90b7abd3194c",
+ :page 3,
+ :position {:bounding {:x1 96.30788464844227,
+ :y1 851.67431640625,
+ :x2 670.5977253466845,
+ :y2 882.7347412109375,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 288.3188557177782,
+ :y1 851.67431640625,
+ :x2 670.5977253466845,
+ :y2 867.0105590820312,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}
+ {:x1 96.30788464844227,
+ :y1 867.3985290527344,
+ :x2 436.68215222656727,
+ :y2 882.7347412109375,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 3},
+ :content {:text "Sistemi Software Agili e Motivazionali per la Mobilità Sostenibile: Microservizi e Gamification al Servizio di Cittadini e Imprese"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfbb6-3b34-4145-86df-c215def56aa7",
+ :page 4,
+ :position {:bounding {:x1 111.29037518799305,
+ :y1 284.73583602905273,
+ :x2 213.03282971680164,
+ :y2 300.072078704834,
+ :width 735.9999999999999,
+ :height 1040.8740173352144},
+ :rects ({:x1 111.29037518799305,
+ :y1 284.73583602905273,
+ :x2 213.03282971680164,
+ :y2 300.072078704834,
+ :width 735.9999999999999,
+ :height 1040.8740173352144}),
+ :page 4},
+ :content {:text "MAAMOOR Rida"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfc10-e7ff-4c7c-a972-75a6c424b785",
+ :page 4,
+ :position {:bounding {:x1 128.8859611004591,
+ :y1 327.30987548828125,
+ :x2 890.8048606365919,
+ :y2 368.811279296875,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 380.76964335143566,
+ :y1 327.30987548828125,
+ :x2 890.8048606365919,
+ :y2 347.7581787109375,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}
+ {:x1 128.8859611004591,
+ :y1 348.36297607421875,
+ :x2 613.1336417645216,
+ :y2 368.811279296875,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "tudio di architetture e protocolli per reti veicolari nell’ambito della mobilità CCAM (Cooperative, Connected and Automated Mobility"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfc29-3506-4656-8847-cb584846ac9b",
+ :page 4,
+ :position {:bounding {:x1 148.93489603698254,
+ :y1 513.0106391906738,
+ :x2 360.3329368084669,
+ :y2 533.4589424133301,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 148.93489603698254,
+ :y1 513.0106391906738,
+ :x2 360.3329368084669,
+ :y2 533.4589424133301,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "MENGISTU Minase Mekete"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfc39-0e6d-4cf6-bb05-e9db606d82a5",
+ :page 4,
+ :position {:bounding {:x1 304.2242942303419,
+ :y1 479.45122146606445,
+ :x2 774.7198386639357,
+ :y2 499.8995246887207,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 304.2242942303419,
+ :y1 479.45122146606445,
+ :x2 774.7198386639357,
+ :y2 499.8995246887207,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "ngegneria del software con sistemi multi-agente basati su LLM"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfc60-f07d-482e-a0b6-b5ac60f864d9",
+ :page 4,
+ :position {:bounding {:x1 93.70619730651379,
+ :y1 840.2519989013672,
+ :x2 891.2891135662794,
+ :y2 881.5480194091797,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 666.2134299725294,
+ :y1 840.2519989013672,
+ :x2 891.2891135662794,
+ :y2 860.7003631591797,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}
+ {:x1 93.70619730651379,
+ :y1 861.0997161865234,
+ :x2 200.71790079772472,
+ :y2 881.5480194091797,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "Machine Learning applicato all’astrofisica"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfc77-a51f-4bce-bac6-886e023990cc",
+ :page 4,
+ :position {:bounding {:x1 148.93489603698254,
+ :y1 894.8531341552734,
+ :x2 313.2153830975294,
+ :y2 915.3014373779297,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 148.93489603698254,
+ :y1 894.8531341552734,
+ :x2 313.2153830975294,
+ :y2 915.3014373779297,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "MUSTAFA Muzzamil"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfca3-81db-4791-8c34-db6a07a5fde4",
+ :page 4,
+ :position {:bounding {:x1 148.93489603698254,
+ :y1 1225.3124313354492,
+ :x2 257.4581504315138,
+ :y2 1245.7606735229492,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 148.93489603698254,
+ :y1 1225.3124313354492,
+ :x2 257.4581504315138,
+ :y2 1245.7606735229492,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "AHMED Ayaz"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfcaf-736d-468a-8894-f144c7a5529b",
+ :page 4,
+ :position {:bounding {:x1 93.70619730651379,
+ :y1 1145.0710983276367,
+ :x2 891.1877952069044,
+ :y2 1186.5609664916992,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 406.5614219158888,
+ :y1 1145.0710983276367,
+ :x2 891.1877952069044,
+ :y2 1165.5193405151367,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}
+ {:x1 93.70619730651379,
+ :y1 1166.1127243041992,
+ :x2 585.7631125897169,
+ :y2 1186.5609664916992,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 4},
+ :content {:text "Generazione e ottimizzazione model-based di scenari di test per sistemi avanzati di assistenza alla guida (ADAS) in co-simulazione"},
+ :properties {:color "blue"}}
+ {:id #uuid "68ecfce3-ef15-450e-8131-d3b3cac77f8d",
+ :page 5,
+ :position {:bounding {:x1 149.53966288268566,
+ :y1 706.2311706542969,
+ :x2 309.6904807537794,
+ :y2 726.6794738769531,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 149.53966288268566,
+ :y1 706.2311706542969,
+ :x2 309.6904807537794,
+ :y2 726.6794738769531,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 5},
+ :content {:text "VEGLIANTE Davide"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfcf9-61d1-431d-97ac-22a7a5736c7a",
+ :page 5,
+ :position {:bounding {:x1 149.53966288268566,
+ :y1 908.3522033691406,
+ :x2 268.1418662518263,
+ :y2 928.8005065917969,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 149.53966288268566,
+ :y1 908.3522033691406,
+ :x2 268.1418662518263,
+ :y2 928.8005065917969,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 5},
+ :content {:text "ZAHRA Tazeen"},
+ :properties {:color "green"}}
+ {:id #uuid "68ecfd12-2d01-4b73-9caf-0da45837c9e2",
+ :page 5,
+ :position {:bounding {:x1 149.53966288268566,
+ :y1 941.9572448730469,
+ :x2 324.02351908385754,
+ :y2 962.4055480957031,
+ :width 985.0000000000002,
+ :height 1393.0175367869383},
+ :rects ({:x1 149.53966288268566,
+ :y1 941.9572448730469,
+ :x2 324.02351908385754,
+ :y2 962.4055480957031,
+ :width 985.0000000000002,
+ :height 1393.0175367869383}),
+ :page 5},
+ :content {:text "SRIVASTAVA Aditya "},
+ :properties {:color "green"}}
+ {:id #uuid "68ed3720-5254-46fc-981a-b6ddc9b19bcf",
+ :page 5,
+ :position {:bounding {:x1 89.56633758544922,
+ :y1 604.5214233398438,
+ :x2 225.02516174316406,
+ :y2 616.7904052734375,
+ :width 590.0000000000001,
+ :height 834.3962910703488},
+ :rects ({:x1 89.56633758544922,
+ :y1 604.5214233398438,
+ :x2 225.02516174316406,
+ :y2 616.7904052734375,
+ :width 590.0000000000001,
+ :height 834.3962910703488}),
+ :page 5},
+ :content {:text "OTHMAN Ali Mohamed Saed"},
+ :properties {:color "green"}}],
+ :extra {:page 4}}
diff --git a/assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.pdf b/assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.pdf
new file mode 100644
index 00000000..f7b7d137
Binary files /dev/null and b/assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.pdf differ
diff --git a/assets/Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.edn b/assets/Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.edn
index ff4aca2c..04f653ec 100644
--- a/assets/Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.edn
+++ b/assets/Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.edn
@@ -945,5 +945,40 @@
:height 1403.3333333333333}),
:page 7},
:content {:text "venti per cento dell’importo della borsa"},
+ :properties {:color "green"}}
+ {:id #uuid "68ab4d45-dcd9-4e6a-a204-2cff1e9989bc",
+ :page 10,
+ :position {:bounding {:x1 70.71249961853027,
+ :y1 167.6500244140625,
+ :x2 431.7045040130615,
+ :y2 219.19378662109375,
+ :width 872.6666666666667,
+ :height 1234.9333333333334},
+ :rects ({:x1 108.25,
+ :y1 167.6500244140625,
+ :x2 427.94659423828125,
+ :y2 181.6500244140625,
+ :width 872.6666666666667,
+ :height 1234.9333333333334}
+ {:x1 70.71249961853027,
+ :y1 180.125,
+ :x2 431.7045040130615,
+ :y2 194.125,
+ :width 872.6666666666667,
+ :height 1234.9333333333334}
+ {:x1 70.71249961853027,
+ :y1 192.60003662109375,
+ :x2 427.9555721282959,
+ :y2 206.60003662109375,
+ :width 872.6666666666667,
+ :height 1234.9333333333334}
+ {:x1 70.71249961853027,
+ :y1 205.19378662109375,
+ :x2 334.5260066986084,
+ :y2 219.19378662109375,
+ :width 872.6666666666667,
+ :height 1234.9333333333334}),
+ :page 10},
+ :content {:text "6. Gli oneri per il finanziamento delle borse di studio di cui al comma 5 possono essere coperti mediante convenzione con soggetti estranei all’amministrazione universitaria, secondo modalità e procedure deliberate dagli organi competenti delle università"},
:properties {:color "green"}}],
- :extra {:page 7}}
+ :extra {:page 1}}
diff --git a/assets/Decreto_Ministeriale_n._630_del_24-04-2024_1714455918933_0.edn b/assets/Decreto_Ministeriale_n._630_del_24-04-2024_1714455918933_0.edn
index 714fa049..7a67a8b8 100644
--- a/assets/Decreto_Ministeriale_n._630_del_24-04-2024_1714455918933_0.edn
+++ b/assets/Decreto_Ministeriale_n._630_del_24-04-2024_1714455918933_0.edn
@@ -188,4 +188,4 @@
:page 24},
:content {:text "concorrenza del costo complessivo della borsa"},
:properties {:color "green"}}],
- :extra {:page 33}}
+ :extra {:page 1}}
diff --git a/assets/Immagine_WhatsApp_2025-09-02_ore_10.57.26_15b51d90_1756803478464_0.jpg b/assets/Immagine_WhatsApp_2025-09-02_ore_10.57.26_15b51d90_1756803478464_0.jpg
new file mode 100644
index 00000000..75b1e4c5
Binary files /dev/null and b/assets/Immagine_WhatsApp_2025-09-02_ore_10.57.26_15b51d90_1756803478464_0.jpg differ
diff --git a/assets/JOURNALING.edn b/assets/JOURNALING.edn
index aac884ab..4e335cc1 100644
--- a/assets/JOURNALING.edn
+++ b/assets/JOURNALING.edn
@@ -1 +1 @@
-{:highlights [], :extra {:page 47}}
+{:highlights [], :extra {:page 54}}
diff --git a/assets/MOSAICO_CM2_GA_and_EB_Meeting_Minutes_1752829106144_0.pdf b/assets/MOSAICO_CM2_GA_and_EB_Meeting_Minutes_1752829106144_0.pdf
new file mode 100644
index 00000000..06a8bd70
Binary files /dev/null and b/assets/MOSAICO_CM2_GA_and_EB_Meeting_Minutes_1752829106144_0.pdf differ
diff --git a/assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.edn b/assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.edn
new file mode 100644
index 00000000..896e579e
--- /dev/null
+++ b/assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.edn
@@ -0,0 +1,143 @@
+{:highlights [{:id #uuid "693160b0-6a69-410b-a49a-a9cf06dd4073",
+ :page 3,
+ :position {:bounding {:x1 150.50959414243698,
+ :y1 678.5369567871094,
+ :x2 447.1889917254448,
+ :y2 696.7943420410156,
+ :width 868.9999999999999,
+ :height 1228.9667405764965},
+ :rects ({:x1 150.50959414243698,
+ :y1 678.5369567871094,
+ :x2 447.1889917254448,
+ :y2 696.7943420410156,
+ :width 868.9999999999999,
+ :height 1228.9667405764965}),
+ :page 3},
+ :content {:text "8. Contratto Prof. Alessandro Neri: Rinnovo;"},
+ :properties {:color "green"}}
+ {:id #uuid "693160c3-b9e7-4673-8216-abeed18301cc",
+ :page 3,
+ :position {:bounding {:x1 176.74322146177292,
+ :y1 477.6026306152344,
+ :x2 370.02026003599167,
+ :y2 495.8600769042969,
+ :width 868.9999999999999,
+ :height 1228.9667405764965},
+ :rects ({:x1 176.74322146177292,
+ :y1 477.6026306152344,
+ :x2 370.02026003599167,
+ :y2 495.8600769042969,
+ :width 868.9999999999999,
+ :height 1228.9667405764965}),
+ :page 3},
+ :content {:text "Comunicazioni del Presidente"},
+ :properties {:color "green"}}
+ {:id #uuid "6931623f-fe44-4f4b-b56a-9ba822711b5a",
+ :page 3,
+ :position {:bounding {:x1 115.31842041015625,
+ :y1 378.9212646484375,
+ :x2 266.68670654296875,
+ :y2 390.6060791015625,
+ :width 567,
+ :height 801.8689780286232},
+ :rects ({:x1 115.31842041015625,
+ :y1 378.9212646484375,
+ :x2 266.68670654296875,
+ :y2 390.6060791015625,
+ :width 567,
+ :height 801.8689780286232}),
+ :page 3},
+ :content {:text "Preconsuntivo 2025 e Budget 2026;"},
+ :properties {:color "green"}}
+ {:id #uuid "69316743-c79e-4200-934d-85d152b86d60",
+ :page 3,
+ :position {:bounding {:x1 152.95152282714844,
+ :y1 519.9826965332031,
+ :x2 302.4813232421875,
+ :y2 535.3188781738281,
+ :width 752.0000000000001,
+ :height 1063.5017133642411},
+ :rects ({:x1 152.95152282714844,
+ :y1 519.9826965332031,
+ :x2 302.4813232421875,
+ :y2 535.3188781738281,
+ :width 752.0000000000001,
+ :height 1063.5017133642411}),
+ :page 3},
+ :content {:text "Piano triennale 2026-2028"},
+ :properties {:color "green"}}
+ {:id #uuid "69316f7e-d361-4907-af0e-82567bdde4d6",
+ :page 3,
+ :position {:bounding {:x1 154.77726018428802,
+ :y1 543.06689453125,
+ :x2 576.4113544225693,
+ :y2 575.508056640625,
+ :width 761.0000000000001,
+ :height 1076.2297923805684},
+ :rects ({:x1 154.77726018428802,
+ :y1 543.06689453125,
+ :x2 576.4113544225693,
+ :y2 558.4031372070312,
+ :width 761.0000000000001,
+ :height 1076.2297923805684}
+ {:x1 154.77726018428802,
+ :y1 560.1718139648438,
+ :x2 252.99356877803802,
+ :y2 575.508056640625,
+ :width 761.0000000000001,
+ :height 1076.2297923805684}),
+ :page 3},
+ :content {:text "Personale: adeguamento livelli, Buoni pasto, MBO, Regolamento Welfare, Destinazione TFR"},
+ :properties {:color "green"}}
+ {:id #uuid "69317290-2997-4b52-b2ad-552b40db9037",
+ :page 3,
+ :position {:bounding {:x1 151.31976318359375,
+ :y1 563.7662963867188,
+ :x2 443.5373229980469,
+ :y2 579.1024780273438,
+ :width 744,
+ :height 1052.1878653497279},
+ :rects ({:x1 151.31976318359375,
+ :y1 563.7662963867188,
+ :x2 443.5373229980469,
+ :y2 579.1024780273438,
+ :width 744,
+ :height 1052.1878653497279}),
+ :page 3},
+ :content {:text "Regolamenti aziendali: Personale, Acquisti, Missioni;"},
+ :properties {:color "green"}}
+ {:id #uuid "693173af-8ba6-4ee8-8968-64ff8bad3023",
+ :page 3,
+ :position {:bounding {:x1 156.61441212892532,
+ :y1 618.3901672363281,
+ :x2 371.8923357129097,
+ :y2 634.4566955566406,
+ :width 770.0000000000001,
+ :height 1088.9578713968958},
+ :rects ({:x1 156.61441212892532,
+ :y1 618.3901672363281,
+ :x2 371.8923357129097,
+ :y2 634.4566955566406,
+ :width 770.0000000000001,
+ :height 1088.9578713968958}),
+ :page 3},
+ :content {:text "Comitato scientifico: nomina membri"},
+ :properties {:color "green"}}
+ {:id #uuid "6931769f-99fd-4d86-bffc-52319c897578",
+ :page 3,
+ :position {:bounding {:x1 133.35902577638626,
+ :y1 653.0222473144531,
+ :x2 355.36969166994095,
+ :y2 669.0887756347656,
+ :width 770.0000000000001,
+ :height 1088.9578713968958},
+ :rects ({:x1 133.35902577638626,
+ :y1 653.0222473144531,
+ :x2 355.36969166994095,
+ :y2 669.0887756347656,
+ :width 770.0000000000001,
+ :height 1088.9578713968958}),
+ :page 3},
+ :content {:text "11. Modello 231/2001: aggiornamenti"},
+ :properties {:color "green"}}],
+ :extra {:page 3}}
diff --git a/assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.pdf b/assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.pdf
new file mode 100644
index 00000000..135c4306
Binary files /dev/null and b/assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.pdf differ
diff --git a/assets/Piano_2026-28_V1_1764843228299_0.pdf b/assets/Piano_2026-28_V1_1764843228299_0.pdf
new file mode 100644
index 00000000..74e1ba20
Binary files /dev/null and b/assets/Piano_2026-28_V1_1764843228299_0.pdf differ
diff --git a/assets/Piano_2026-28_V1_1764843299066_0.edn b/assets/Piano_2026-28_V1_1764843299066_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/Piano_2026-28_V1_1764843299066_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/Piano_2026-28_V1_1764843299066_0.pdf b/assets/Piano_2026-28_V1_1764843299066_0.pdf
new file mode 100644
index 00000000..74e1ba20
Binary files /dev/null and b/assets/Piano_2026-28_V1_1764843299066_0.pdf differ
diff --git a/assets/Punto_11_odg_-_231_1764843308200_0.zip b/assets/Punto_11_odg_-_231_1764843308200_0.zip
new file mode 100644
index 00000000..ad23f3b7
Binary files /dev/null and b/assets/Punto_11_odg_-_231_1764843308200_0.zip differ
diff --git a/assets/REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.edn b/assets/REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.edn
index fad73f2b..f95dbb13 100644
--- a/assets/REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.edn
+++ b/assets/REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.edn
@@ -205,5 +205,141 @@
:height 1403.1999999999998}),
:page 4},
:content {:text "ali contratti di apprendistato sono considerati equivalenti alle borse di dottorato ai fini del computo del numero minimo necessario per l'attivazione del corso"},
- :properties {:color "green"}}],
- :extra {:page 16}}
+ :properties {:color "green"}}
+ {:id #uuid "6901d620-5ee3-4aff-a09d-e806e025badc",
+ :page 14,
+ :position {:bounding {:x1 349.1546325683594,
+ :y1 913.6250305175781,
+ :x2 445.79437255859375,
+ :y2 932.2916870117188,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 349.1546325683594,
+ :y1 913.6250305175781,
+ :x2 445.79437255859375,
+ :y2 932.2916870117188,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text " due valutatori"},
+ :properties {:color "green"}}
+ {:id #uuid "6901d627-8af7-4b0d-ac36-603139ce7039",
+ :page 14,
+ :position {:bounding {:x1 144.8125,
+ :y1 933.4583435058594,
+ :x2 620.4811401367188,
+ :y2 952.1250305175781,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 144.8125,
+ :y1 933.4583435058594,
+ :x2 620.4811401367188,
+ :y2 952.1250305175781,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text "istituzioni di due paesi europei diversi da quello in cui viene discussa"},
+ :properties {:color "green"}}
+ {:id #uuid "6901d637-b077-40c5-86e4-9d08fbad5a7e",
+ :page 14,
+ :position {:bounding {:x1 144.8125,
+ :y1 974.2395935058594,
+ :x2 278.12579345703125,
+ :y2 992.9062805175781,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 144.8125,
+ :y1 974.2395935058594,
+ :x2 278.12579345703125,
+ :y2 992.9062805175781,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text "almeno un membro"},
+ :properties {:color "green"}}
+ {:id #uuid "6901d645-b4ba-445c-b2dc-d963a87efa00",
+ :page 14,
+ :position {:bounding {:x1 231.94122314453125,
+ :y1 994.0625610351562,
+ :x2 386.793701171875,
+ :y2 1012.7292175292969,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 231.94122314453125,
+ :y1 994.0625610351562,
+ :x2 386.793701171875,
+ :y2 1012.7292175292969,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text "paese europeo diverso"},
+ :properties {:color "green"}}
+ {:id #uuid "6901d652-0585-48bb-b3e2-cb038f9818f4",
+ :page 14,
+ :position {:bounding {:x1 452.44989013671875,
+ :y1 1015.2500610351562,
+ :x2 498.04803466796875,
+ :y2 1033.9167175292969,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 452.44989013671875,
+ :y1 1015.2500610351562,
+ :x2 498.04803466796875,
+ :y2 1033.9167175292969,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text "lingua "},
+ :properties {:color "green"}}
+ {:id #uuid "6901d65b-fa58-46ef-b08f-21b0bb3ab7be",
+ :page 14,
+ :position {:bounding {:x1 631.5821533203125,
+ :y1 1056.2188110351562,
+ :x2 828.6912841796875,
+ :y2 1074.885498046875,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 631.5821533203125,
+ :y1 1056.2188110351562,
+ :x2 828.6912841796875,
+ :y2 1074.885498046875,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text " soggiorno di almeno tre mes"},
+ :properties {:color "green"}}
+ {:id #uuid "6901d669-6055-4d90-868d-e9ae1a83a919",
+ :page 14,
+ :position {:bounding {:x1 197.18603515625,
+ :y1 1115.322998046875,
+ :x2 593.1356811523438,
+ :y2 1133.9896240234375,
+ :width 928.0000000000001,
+ :height 1312.4063696835315},
+ :rects ({:x1 197.18603515625,
+ :y1 1115.322998046875,
+ :x2 593.1356811523438,
+ :y2 1133.9896240234375,
+ :width 928.0000000000001,
+ :height 1312.4063696835315}),
+ :page 14},
+ :content {:text "una o più delle condizioni di cui alle lettere a), b) c) e d) "},
+ :properties {:color "green"}}
+ {:id #uuid "6901d687-84a6-4b31-8d15-967b5a2f925e",
+ :page 14,
+ :position {:bounding {:x1 665.3938598632812,
+ :y1 1203.5416870117188,
+ :x2 834.66845703125,
+ :y2 1224.2083740234375,
+ :width 984,
+ :height 1391.6033057851237},
+ :rects ({:x1 665.3938598632812,
+ :y1 1203.5416870117188,
+ :x2 834.66845703125,
+ :y2 1224.2083740234375,
+ :width 984,
+ :height 1391.6033057851237}),
+ :page 14},
+ :content {:text "International Doctorate"},
+ :properties {:color "red"}}],
+ :extra {:page 15}}
diff --git a/assets/RELAZIONE_Nucleo_2024_1759759962335_0.edn b/assets/RELAZIONE_Nucleo_2024_1759759962335_0.edn
new file mode 100644
index 00000000..8014641b
--- /dev/null
+++ b/assets/RELAZIONE_Nucleo_2024_1759759962335_0.edn
@@ -0,0 +1,265 @@
+{:highlights [{:id #uuid "68e3cec4-61ff-41f0-b1c6-5b38b38c2059",
+ :page 97,
+ :position {:bounding {:x1 94.39085388183594,
+ :y1 609.9689331054688,
+ :x2 898.4756927490234,
+ :y2 657.004638671875,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 94.39085388183594,
+ :y1 609.9689331054688,
+ :x2 898.4756927490234,
+ :y2 632.608154296875,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 634.3654174804688,
+ :x2 675.9605560302734,
+ :y2 657.004638671875,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 97},
+ :content {:text "Si ribadisce che le autovalutazioni hanno lo scopo di sviluppare le capacità di auto-percezione e autocritica, nell’ottica di individuare margini di sviluppo e miglioramento"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3cf06-8829-4450-9140-1c09232fa355",
+ :page 33,
+ :position {:bounding {:x1 94.39085388183594,
+ :y1 558.7682800292969,
+ :x2 902.8953399658203,
+ :y2 654.6083221435547,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 94.39085388183594,
+ :y1 558.7682800292969,
+ :x2 902.8953399658203,
+ :y2 584.3286590576172,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 583.1647644042969,
+ :x2 897.2177581787109,
+ :y2 605.803955078125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 607.5726470947266,
+ :x2 898.2147979736328,
+ :y2 630.2118377685547,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 631.9691162109375,
+ :x2 353.9790802001953,
+ :y2 654.6083221435547,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 33},
+ :content {:text "Per la selezione dei CdS, dei Dipartimenti e corsi di dottorato da audire il Nucleo ha proceduto a una preliminare analisi degli indicatori ANVUR per il monitoraggio annuale (con particolare riferimento al set minimo di indicatori della SMA) definendo un programma di audizioni che fosse rappresentativo delle diverse realtà dell’Ateneo. "},
+ :properties {:color "green"}}
+ {:id #uuid "68e3cf51-64c1-44b1-ad53-e8f45b74c99b",
+ :page 46,
+ :position {:bounding {:x1 94.39085388183594,
+ :y1 914.9705352783203,
+ :x2 901.2289886474609,
+ :y2 1059.6034698486328,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 401.9932403564453,
+ :y1 914.9705352783203,
+ :x2 897.8264923095703,
+ :y2 937.6096954345703,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 939.3670196533203,
+ :x2 901.2289886474609,
+ :y2 962.0061798095703,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 963.7634429931641,
+ :x2 897.5047454833984,
+ :y2 986.4026641845703,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 988.1713409423828,
+ :x2 897.4236907958984,
+ :y2 1010.8105621337891,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 1012.5678253173828,
+ :x2 897.8216400146484,
+ :y2 1035.207046508789,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 1036.9643096923828,
+ :x2 485.7360382080078,
+ :y2 1059.6034698486328,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 46},
+ :content {:text " il NdV rileva che l’Ateneo non si accerta che i Dipartimenti e i Corsi di Dottorato di Ricerca definiscano con chiarezza e trasparenza i criteri e le modalità di distribuzione interna delle risorse (economiche, sia per i Dipartimenti e i Dottorati, e di personale per i Dipartimenti) assegnate a sostegno della ricerca (anche dottorale) e della terza missione/impatto sociale, coerentemente con il programma strategico proprio e dell'Ateneo e con le indicazioni dello stesso sull’utilizzazione delle risorse assegnat"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3cf7d-9acb-4bb1-bbf7-14621a0dd805",
+ :page 52,
+ :position {:bounding {:x1 103.39402770996094,
+ :y1 535.3530883789062,
+ :x2 593.4076080322266,
+ :y2 574.7434692382812,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 103.39402770996094,
+ :y1 535.3530883789062,
+ :x2 593.4076080322266,
+ :y2 557.2620239257812,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 103.39402770996094,
+ :y1 555.7557983398438,
+ :x2 255.6396942138672,
+ :y2 574.7434692382812,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 52},
+ :content {:text "Iscritti al primo anno di Corsi di dottorato che hanno conseguito il titolo di accesso in altro Ateneo"},
+ :properties {:color "green"}}
+ {:id #uuid "68fb6fe9-147f-4605-a4d9-2bebe0ae339c",
+ :page 95,
+ :position {:bounding {:x1 0,
+ :y1 1207.3630981445312,
+ :x2 991.9939575195312,
+ :y2 2815.9785766601562,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 178.67018127441406,
+ :y1 1207.3630981445312,
+ :x2 897.1601715087891,
+ :y2 1230.0022583007812,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 0,
+ :y1 1212.3154296875,
+ :x2 991.9939575195312,
+ :y2 1402.9913330078125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 0,
+ :y1 1412.9872436523438,
+ :x2 991.9939575195312,
+ :y2 2815.9785766601562,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 95},
+ :content {:text "La finalità che il NdV vuole conseguire è quella di offrire un contributo al processo di Assicurazione della Qualità nei Corsi dei Dottorato di Ricerca, tale processo ha infatti lo scopo di Relazione annuale 2023 96 identificare e segnalare i punti di forza e debolezza verso cui indirizzare le future azioni e si basa su una lettura indipendente dei documenti, dei processi e dell’opinione di studenti e colleghi"},
+ :properties {:color "green"}}
+ {:id #uuid "68fb6ffa-898c-4f02-90bb-b6bed5be89c3",
+ :page 96,
+ :position {:bounding {:x1 94.39085388183594,
+ :y1 168.1622314453125,
+ :x2 905.6016082763672,
+ :y2 393.4017333984375,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 94.39085388183594,
+ :y1 168.1622314453125,
+ :x2 905.6016082763672,
+ :y2 192.2620849609375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 192.570068359375,
+ :x2 644.8671722412109,
+ :y2 215.2093505859375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 217.970703125,
+ :x2 139.15574645996094,
+ :y2 240.6099853515625,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 217.970703125,
+ :x2 364.8131561279297,
+ :y2 240.6099853515625,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 243.371337890625,
+ :x2 139.15574645996094,
+ :y2 266.0106201171875,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 243.371337890625,
+ :x2 483.9799041748047,
+ :y2 266.0106201171875,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 268.77197265625,
+ :x2 139.15574645996094,
+ :y2 291.4112548828125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 268.77197265625,
+ :x2 395.79881286621094,
+ :y2 291.4112548828125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 294.36669921875,
+ :x2 139.15574645996094,
+ :y2 317.005859375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 294.36669921875,
+ :x2 477.45982360839844,
+ :y2 317.005859375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 319.767333984375,
+ :x2 139.15574645996094,
+ :y2 342.406494140625,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 319.767333984375,
+ :x2 563.2578582763672,
+ :y2 342.406494140625,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 345.3619384765625,
+ :x2 139.15574645996094,
+ :y2 368.0010986328125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 345.3619384765625,
+ :x2 343.36216735839844,
+ :y2 368.0010986328125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 124.39006042480469,
+ :y1 370.7625732421875,
+ :x2 139.15574645996094,
+ :y2 393.4017333984375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 154.38929748535156,
+ :y1 370.7625732421875,
+ :x2 427.88352966308594,
+ :y2 393.4017333984375,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 96},
+ :content {:text "L’audizione del Dottorato si configura come una verifica condivisa tra il Nucleo e il Corso di Dottorato di Ricerca delle informazioni presenti nei documenti dell’AQ, ovvero:• scheda Anagrafe Dottorati• scheda valutazione ANVUR del Dottorato• indagine Almalaurea Dottorati• verbali Collegio docenti (ultimi 24 mesi);• griglia di autovalutazione Ambito D.PHD compilata;• sito web del Dottorato;• altri documenti ritenuti di interess"},
+ :properties {:color "green"}}],
+ :extra {:page 37}}
diff --git a/assets/RELAZIONE_Nucleo_2024_1759759962335_0.pdf b/assets/RELAZIONE_Nucleo_2024_1759759962335_0.pdf
new file mode 100644
index 00000000..0c9c554c
Binary files /dev/null and b/assets/RELAZIONE_Nucleo_2024_1759759962335_0.pdf differ
diff --git a/assets/Radiolabs_2025-1_1766433218681_0.edn b/assets/Radiolabs_2025-1_1766433218681_0.edn
new file mode 100644
index 00000000..512d9205
--- /dev/null
+++ b/assets/Radiolabs_2025-1_1766433218681_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 9}}
diff --git a/assets/Radiolabs_2025-1_1766433218681_0.pdf b/assets/Radiolabs_2025-1_1766433218681_0.pdf
new file mode 100644
index 00000000..62327db9
Binary files /dev/null and b/assets/Radiolabs_2025-1_1766433218681_0.pdf differ
diff --git a/assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006171407_1.docx b/assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006171407_1.docx
new file mode 100644
index 00000000..702e0805
Binary files /dev/null and b/assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006171407_1.docx differ
diff --git a/assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006190602_0.docx b/assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006190602_0.docx
new file mode 100644
index 00000000..702e0805
Binary files /dev/null and b/assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006190602_0.docx differ
diff --git a/assets/Report_Assegno_2025_1760531396007_0.edn b/assets/Report_Assegno_2025_1760531396007_0.edn
new file mode 100644
index 00000000..d89c87b9
--- /dev/null
+++ b/assets/Report_Assegno_2025_1760531396007_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 2}}
diff --git a/assets/Report_Assegno_2025_1760531396007_0.pdf b/assets/Report_Assegno_2025_1760531396007_0.pdf
new file mode 100644
index 00000000..767ef7d5
Binary files /dev/null and b/assets/Report_Assegno_2025_1760531396007_0.pdf differ
diff --git a/assets/Report_Assegno_v3_1760531375357_0.pdf b/assets/Report_Assegno_v3_1760531375357_0.pdf
new file mode 100644
index 00000000..16f3b824
Binary files /dev/null and b/assets/Report_Assegno_v3_1760531375357_0.pdf differ
diff --git a/assets/Report_JURI_RTDB_2025_2026_1760530960125_0.edn b/assets/Report_JURI_RTDB_2025_2026_1760530960125_0.edn
new file mode 100644
index 00000000..6015423c
--- /dev/null
+++ b/assets/Report_JURI_RTDB_2025_2026_1760530960125_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 5}}
diff --git a/assets/Report_JURI_RTDB_2025_2026_1760530960125_0.pdf b/assets/Report_JURI_RTDB_2025_2026_1760530960125_0.pdf
new file mode 100644
index 00000000..d94ad1dd
Binary files /dev/null and b/assets/Report_JURI_RTDB_2025_2026_1760530960125_0.pdf differ
diff --git a/assets/STAF_2024_paper_8_1704401003970_0.edn b/assets/STAF_2024_paper_8_1704401003970_0.edn
index 21a1e090..c6db51ee 100644
--- a/assets/STAF_2024_paper_8_1704401003970_0.edn
+++ b/assets/STAF_2024_paper_8_1704401003970_0.edn
@@ -1912,4 +1912,4 @@
:page 12},
:content {:text "Figure 10 Sequence Diagram of UAV Simulation"},
:properties {:color "yellow"}}],
- :extra {:page 4}}
+ :extra {:page 11}}
diff --git a/assets/SW-2025-10-0161_Proof_hi_1766502869265_0.edn b/assets/SW-2025-10-0161_Proof_hi_1766502869265_0.edn
new file mode 100644
index 00000000..a6dc007e
--- /dev/null
+++ b/assets/SW-2025-10-0161_Proof_hi_1766502869265_0.edn
@@ -0,0 +1,24 @@
+{:highlights [{:id #uuid "694ab342-364a-4c82-a537-695ff0a4bcb3",
+ :page 3,
+ :position {:bounding {:x1 524.1704864501953,
+ :y1 843.7323608398438,
+ :x2 886.1536407470703,
+ :y2 880.5895385742188,
+ :width 1019.9999999999999,
+ :height 1319.9999999999998},
+ :rects ({:x1 822.0919342041016,
+ :y1 843.7323608398438,
+ :x2 886.1536407470703,
+ :y2 860.5291748046875,
+ :width 1019.9999999999999,
+ :height 1319.9999999999998}
+ {:x1 524.1704864501953,
+ :y1 863.7926635742188,
+ :x2 805.2423858642578,
+ :y2 880.5895385742188,
+ :width 1019.9999999999999,
+ :height 1319.9999999999998}),
+ :page 3},
+ :content {:text " (to which an explanation was previously assigned)"},
+ :properties {:color "green"}}],
+ :extra {:page 2}}
diff --git a/assets/SW-2025-10-0161_Proof_hi_1766502869265_0.pdf b/assets/SW-2025-10-0161_Proof_hi_1766502869265_0.pdf
new file mode 100644
index 00000000..8b648df3
Binary files /dev/null and b/assets/SW-2025-10-0161_Proof_hi_1766502869265_0.pdf differ
diff --git a/assets/SW-2025-10-0163_Proof_hi_1766500599608_0.pdf b/assets/SW-2025-10-0163_Proof_hi_1766500599608_0.pdf
new file mode 100644
index 00000000..af4cdd3d
Binary files /dev/null and b/assets/SW-2025-10-0163_Proof_hi_1766500599608_0.pdf differ
diff --git a/assets/SW-2025-10-0163_Proof_hi_1766500604129_0.edn b/assets/SW-2025-10-0163_Proof_hi_1766500604129_0.edn
new file mode 100644
index 00000000..c3eb3071
--- /dev/null
+++ b/assets/SW-2025-10-0163_Proof_hi_1766500604129_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 7}}
diff --git a/assets/SW-2025-10-0163_Proof_hi_1766500604129_0.pdf b/assets/SW-2025-10-0163_Proof_hi_1766500604129_0.pdf
new file mode 100644
index 00000000..af4cdd3d
Binary files /dev/null and b/assets/SW-2025-10-0163_Proof_hi_1766500604129_0.pdf differ
diff --git a/assets/SWEN_RTR_2025_Report-2_1752779890753_0.edn b/assets/SWEN_RTR_2025_Report-2_1752779890753_0.edn
new file mode 100644
index 00000000..d517f46b
--- /dev/null
+++ b/assets/SWEN_RTR_2025_Report-2_1752779890753_0.edn
@@ -0,0 +1,81 @@
+{:highlights [{:id #uuid "68794d08-6e82-479c-a8e4-97e2e2a8a976",
+ :page 2,
+ :position {:bounding {:x1 83.97271143272519,
+ :y1 319.81863021850586,
+ :x2 610.1603640206158,
+ :y2 352.40810775756836,
+ :width 693.9999999999999,
+ :height 981.5138859957398},
+ :rects ({:x1 97.84835230186582,
+ :y1 319.81863021850586,
+ :x2 610.1603640206158,
+ :y2 335.5199851989746,
+ :width 693.9999999999999,
+ :height 981.5138859957398}
+ {:x1 83.97271143272519,
+ :y1 336.7067222595215,
+ :x2 287.3991488106549,
+ :y2 352.40810775756836,
+ :width 693.9999999999999,
+ :height 981.5138859957398}),
+ :page 2},
+ :content {:text "This report synthesizes the content and outcomes of the retreat, drawing from both formal sessions and transcripted discussion"},
+ :properties {:color "green"}}
+ {:id #uuid "68794d6d-38a0-4e39-81b5-394854f8310c",
+ :page 3,
+ :position {:bounding {:x1 83.97271143272519,
+ :y1 210.62213134765625,
+ :x2 608.8175448067486,
+ :y2 243.11465454101562,
+ :width 693.9999999999999,
+ :height 981.5138859957398},
+ :rects ({:x1 163.63141809776425,
+ :y1 210.62213134765625,
+ :x2 608.8175448067486,
+ :y2 226.32351684570312,
+ :width 693.9999999999999,
+ :height 981.5138859957398}
+ {:x1 83.97271143272519,
+ :y1 227.41323852539062,
+ :x2 441.8429506905377,
+ :y2 243.11465454101562,
+ :width 693.9999999999999,
+ :height 981.5138859957398}),
+ :page 3},
+ :content {:text "A proposed timeline set the completion of the first consolidated version by midSeptember 2025, aligning with the start of the academic year."},
+ :properties {:color "green"}}
+ {:id #uuid "68794d9a-c21d-43b0-9256-74395ecb6d3a",
+ :page 3,
+ :position {:bounding {:x1 159.03827844932675,
+ :y1 160.0490951538086,
+ :x2 199.07149683311582,
+ :y2 175.7504653930664,
+ :width 693.9999999999999,
+ :height 981.5138859957398},
+ :rects ({:x1 159.03827844932675,
+ :y1 160.0490951538086,
+ :x2 199.07149683311582,
+ :y2 175.7504653930664,
+ :width 693.9999999999999,
+ :height 981.5138859957398}),
+ :page 3},
+ :content {:text "SWEn "},
+ :properties {:color "red"}}
+ {:id #uuid "68794dc1-c7cd-4c49-8a54-59b7e592c43c",
+ :page 4,
+ :position {:bounding {:x1 192.8428286202252,
+ :y1 102.30429077148438,
+ :x2 242.02236353233457,
+ :y2 118.00567626953125,
+ :width 693.9999999999999,
+ :height 981.5138859957398},
+ :rects ({:x1 192.8428286202252,
+ :y1 102.30429077148438,
+ :x2 242.02236353233457,
+ :y2 118.00567626953125,
+ :width 693.9999999999999,
+ :height 981.5138859957398}),
+ :page 4},
+ :content {:text "SWEn’s "},
+ :properties {:color "red"}}],
+ :extra {:page 9}}
diff --git a/assets/SWEN_RTR_2025_Report-2_1752779890753_0.pdf b/assets/SWEN_RTR_2025_Report-2_1752779890753_0.pdf
new file mode 100644
index 00000000..1281fc88
Binary files /dev/null and b/assets/SWEN_RTR_2025_Report-2_1752779890753_0.pdf differ
diff --git a/assets/SWEN_RTR_2025_Report-3_1752780760755_0.edn b/assets/SWEN_RTR_2025_Report-3_1752780760755_0.edn
new file mode 100644
index 00000000..6015423c
--- /dev/null
+++ b/assets/SWEN_RTR_2025_Report-3_1752780760755_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 5}}
diff --git a/assets/SWEN_RTR_2025_Report-3_1752780760755_0.pdf b/assets/SWEN_RTR_2025_Report-3_1752780760755_0.pdf
new file mode 100644
index 00000000..c4279ce1
Binary files /dev/null and b/assets/SWEN_RTR_2025_Report-3_1752780760755_0.pdf differ
diff --git a/assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.edn b/assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.edn
new file mode 100644
index 00000000..02d98326
--- /dev/null
+++ b/assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.edn
@@ -0,0 +1,120 @@
+{:highlights [{:id #uuid "68e3ccde-2685-4827-b67e-bb0117622f86",
+ :page 3,
+ :position {:bounding {:x1 171.65397095680237,
+ :y1 795.0763244628906,
+ :x2 434.29947876930237,
+ :y2 813.3337707519531,
+ :width 793.6266666666667,
+ :height 1122.6666666666665},
+ :rects ({:x1 171.65397095680237,
+ :y1 795.0763244628906,
+ :x2 434.29947876930237,
+ :y2 813.3337707519531,
+ :width 793.6266666666667,
+ :height 1122.6666666666665}),
+ :page 3},
+ :content {:text "scheda valutazione ANVUR del Dottorato"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3cce5-1215-4d79-b582-64799d63b8e4",
+ :page 3,
+ :position {:bounding {:x1 171.65397095680237,
+ :y1 816.1864929199219,
+ :x2 365.0768072605133,
+ :y2 834.4438781738281,
+ :width 793.6266666666667,
+ :height 1122.6666666666665},
+ :rects ({:x1 171.65397095680237,
+ :y1 816.1864929199219,
+ :x2 365.0768072605133,
+ :y2 834.4438781738281,
+ :width 793.6266666666667,
+ :height 1122.6666666666665}),
+ :page 3},
+ :content {:text "indagine Almalaurea Dottorati"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3ccec-10c5-4e63-9fde-b8cb9befe103",
+ :page 3,
+ :position {:bounding {:x1 171.65397095680237,
+ :y1 837.2966003417969,
+ :x2 421.0591986179352,
+ :y2 855.5540466308594,
+ :width 793.6266666666667,
+ :height 1122.6666666666665},
+ :rects ({:x1 171.65397095680237,
+ :y1 837.2966003417969,
+ :x2 421.0591986179352,
+ :y2 855.5540466308594,
+ :width 793.6266666666667,
+ :height 1122.6666666666665}),
+ :page 3},
+ :content {:text "verbali Collegio docenti (ultimi 24 mesi"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3ccf1-bc03-450b-9602-7c5200b5d4d0",
+ :page 3,
+ :position {:bounding {:x1 171.65397095680237,
+ :y1 858.2926330566406,
+ :x2 494.77616333961487,
+ :y2 876.5500793457031,
+ :width 793.6266666666667,
+ :height 1122.6666666666665},
+ :rects ({:x1 171.65397095680237,
+ :y1 858.2926330566406,
+ :x2 494.77616333961487,
+ :y2 876.5500793457031,
+ :width 793.6266666666667,
+ :height 1122.6666666666665}),
+ :page 3},
+ :content {:text "griglia di autovalutazione Ambito D.PHD compilata"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3ccfa-c890-46a7-a245-333e0ce7a12f",
+ :page 3,
+ :position {:bounding {:x1 171.65397095680237,
+ :y1 879.4028015136719,
+ :x2 315.9797308444977,
+ :y2 897.6601867675781,
+ :width 793.6266666666667,
+ :height 1122.6666666666665},
+ :rects ({:x1 171.65397095680237,
+ :y1 879.4028015136719,
+ :x2 315.9797308444977,
+ :y2 897.6601867675781,
+ :width 793.6266666666667,
+ :height 1122.6666666666665}),
+ :page 3},
+ :content {:text "sito web del Dottorato"},
+ :properties {:color "green"}}
+ {:id #uuid "68e3cd12-1ce4-44e2-83ee-5cb6ffe4ede5",
+ :page 5,
+ :position {:bounding {:x1 494.6276800632477,
+ :y1 450.5360412597656,
+ :x2 595.7950384616852,
+ :y2 468.79345703125,
+ :width 793.6266666666667,
+ :height 1122.6666666666665},
+ :rects ({:x1 494.6276800632477,
+ :y1 450.5360412597656,
+ :x2 595.7950384616852,
+ :y2 468.79345703125,
+ :width 793.6266666666667,
+ :height 1122.6666666666665}),
+ :page 5},
+ :content {:text "Ambito D.PHD"},
+ :properties {:color "green"}}
+ {:id #uuid "6922c6e5-3223-4b1d-83d7-39e6a443f9bc",
+ :page 2,
+ :position {:bounding {:x1 83.18536376953125,
+ :y1 693.1840286254883,
+ :x2 271.18548583984375,
+ :y2 712.4638137817383,
+ :width 872.9893333333334,
+ :height 1234.9333333333334},
+ :rects ({:x1 83.18536376953125,
+ :y1 693.1840286254883,
+ :x2 271.18548583984375,
+ :y2 712.4638137817383,
+ :width 872.9893333333334,
+ :height 1234.9333333333334}),
+ :page 2},
+ :content {:text "Prof. Bruno Moncharmont,"},
+ :properties {:color "green"}}],
+ :extra {:page 2}}
diff --git a/assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.pdf b/assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.pdf
new file mode 100644
index 00000000..9b07f5d3
Binary files /dev/null and b/assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.pdf differ
diff --git a/assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.edn b/assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.edn
new file mode 100644
index 00000000..c187958e
--- /dev/null
+++ b/assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.edn
@@ -0,0 +1,1122 @@
+{:highlights [{:id #uuid "6887884d-9fdf-4135-b06d-65ed75c76950",
+ :page 4,
+ :position {:bounding {:x1 445.67498779296875,
+ :y1 187.58355712890625,
+ :x2 821.523681640625,
+ :y2 225.44488525390625,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 445.67498779296875,
+ :y1 187.58355712890625,
+ :x2 821.523681640625,
+ :y2 205.84097290039062,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 445.67498779296875,
+ :y1 207.18743896484375,
+ :x2 739.6959228515625,
+ :y2 225.44488525390625,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 4},
+ :content {:text "Multi-disciplinary action aimed at supporting the gender equality education in Palestine"},
+ :properties {:color "green"}}
+ {:id #uuid "68878898-b744-41ae-8884-87c76b101040",
+ :page 5,
+ :position {:bounding {:x1 47.1954345703125,
+ :y1 362.04461669921875,
+ :x2 890.1181640625,
+ :y2 424.770263671875,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 371.14385986328125,
+ :y1 362.04461669921875,
+ :x2 889.656494140625,
+ :y2 381.76263427734375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 47.1954345703125,
+ :y1 383.64544677734375,
+ :x2 890.1181640625,
+ :y2 403.3634033203125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 47.1954345703125,
+ :y1 405.05224609375,
+ :x2 561.1268310546875,
+ :y2 424.770263671875,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 5},
+ :content {:text "la promozione della creazione di un sistema di formazione avanzata integrato che possa incidere sulle politiche di sviluppo e di crescita in Palestina, con uno particolare sguardo all’educazione all’uguaglianza di genere"},
+ :properties {:color "green"}}
+ {:id #uuid "688788a1-18c3-48e8-ad14-c655a2aee1ee",
+ :page 5,
+ :position {:bounding {:x1 191.5521240234375,
+ :y1 448.0941162109375,
+ :x2 867.225341796875,
+ :y2 467.8121337890625,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 191.5521240234375,
+ :y1 448.0941162109375,
+ :x2 867.225341796875,
+ :y2 467.8121337890625,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 5},
+ :content {:text " vasta azione di mobilità di docenti italiani e palestinesi e di studenti palestinesi."},
+ :properties {:color "green"}}
+ {:id #uuid "688788c8-e8d1-47c3-b67d-b3a5d212d4a2",
+ :page 5,
+ :position {:bounding {:x1 356.43505859375,
+ :y1 680.1002655029297,
+ :x2 865.0362548828125,
+ :y2 699.8182830810547,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 356.43505859375,
+ :y1 680.1002655029297,
+ :x2 865.0362548828125,
+ :y2 699.8182830810547,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 5},
+ :content {:text " scambio di competenze, conoscenze e buone prassi tra i partners"},
+ :properties {:color "green"}}
+ {:id #uuid "688789c4-2c00-4edb-bccc-dadb610a69b7",
+ :page 5,
+ :position {:bounding {:x1 47.1954345703125,
+ :y1 1142.5834197998047,
+ :x2 749.5345458984375,
+ :y2 1162.3014373779297,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 47.1954345703125,
+ :y1 1142.5834197998047,
+ :x2 749.5345458984375,
+ :y2 1162.3014373779297,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 5},
+ :content {:text "Attività 1.2. Attivazione di posizioni di PhD espressamente destinate a studenti palestinesi"},
+ :properties {:color "green"}}
+ {:id #uuid "688789cb-ce1d-4035-b90e-cc45405f4efb",
+ :page 5,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 617.1007385253906,
+ :x2 889.3908996582031,
+ :y2 658.2141723632812,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 617.1007385253906,
+ :x2 889.3908996582031,
+ :y2 636.8187561035156,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 638.4961547851562,
+ :x2 229.75152587890625,
+ :y2 658.2141723632812,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 5},
+ :content {:text "O.S.1. Promuovere lo scambio di conoscenze e buone prassi al fine di potenziare le competenze delle Università Palestinesi"},
+ :properties {:color "green"}}
+ {:id #uuid "688789e0-2a51-4011-85ac-9669c875f419",
+ :page 6,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 238.8526611328125,
+ :x2 290.38421630859375,
+ :y2 258.5707092285156,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 238.8526611328125,
+ :x2 290.38421630859375,
+ :y2 258.5707092285156,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 6},
+ :content {:text "O.S.2. Education/Formazione"},
+ :properties {:color "green"}}
+ {:id #uuid "688789e5-28b2-4f1f-bd2d-226488786540",
+ :page 6,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 1012.7275695800781,
+ :x2 746.8088684082031,
+ :y2 1032.4455871582031,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 1012.7275695800781,
+ :x2 746.8088684082031,
+ :y2 1032.4455871582031,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 6},
+ :content {:text "Attività 2.3. Attivazione di posizioni di PhD espressamente destinate a studenti Palestinesi"},
+ :properties {:color "green"}}
+ {:id #uuid "68878a05-28ab-4769-8b14-9e281d2c8ca1",
+ :page 8,
+ :position {:bounding {:x1 94.39083862304688,
+ :y1 765.5335369110107,
+ :x2 889.436279296875,
+ :y2 828.2477703094482,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 384.43804931640625,
+ :y1 765.5335369110107,
+ :x2 889.436279296875,
+ :y2 785.2515544891357,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39083862304688,
+ :y1 787.1343669891357,
+ :x2 889.2010192871094,
+ :y2 806.8523845672607,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39083862304688,
+ :y1 808.5297527313232,
+ :x2 211.7681884765625,
+ :y2 828.2477703094482,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 8},
+ :content {:text "promuovere le capacità tecnologiche dei settori industriali e artigianali, garantendo un aumento significativo dell'accesso alle tecnologie dell'informazione e della comunicazione"},
+ :properties {:color "green"}}
+ {:id #uuid "68878a0a-ee6a-4be8-9cb3-b8b4c151ca52",
+ :page 8,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 556.3491497039795,
+ :x2 531.5315551757812,
+ :y2 579.718656539917,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 556.3491497039795,
+ :x2 531.5315551757812,
+ :y2 579.718656539917,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 8},
+ :content {:text "Information and communication technology (ICT"},
+ :properties {:color "green"}}
+ {:id #uuid "68878a2b-6ad1-4916-94d6-0b517999964e",
+ :page 9,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 251.05096435546875,
+ :x2 748.9871826171875,
+ :y2 270.76898193359375,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 251.05096435546875,
+ :x2 748.9871826171875,
+ :y2 270.76898193359375,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 9},
+ :content {:text "Attività 5.2. Attivazione di posizioni di PhD espressamente destinate a studenti palestinesi"},
+ :properties {:color "green"}}
+ {:id #uuid "68878a39-d9c4-48c4-be96-127479b92b8d",
+ :page 9,
+ :position {:bounding {:x1 104.43243408203125,
+ :y1 513.5469360351562,
+ :x2 181.49627685546875,
+ :y2 566.9498901367188,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 117.82879638671875,
+ :y1 513.5469360351562,
+ :x2 168.2987060546875,
+ :y2 530.34375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 104.43243408203125,
+ :y1 531.747314453125,
+ :x2 181.49627685546875,
+ :y2 548.5441284179688,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 120.03109741210938,
+ :y1 550.153076171875,
+ :x2 162.047607421875,
+ :y2 566.9498901367188,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 9},
+ :content {:text "Borse di Dottorato di ricerca"},
+ :properties {:color "green"}}
+ {:id #uuid "68878aa1-5fbc-4d5f-a6fd-ad7d5104090b",
+ :page 10,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 191.052490234375,
+ :x2 890.004150390625,
+ :y2 253.7667236328125,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 193.7391357421875,
+ :y1 191.052490234375,
+ :x2 890.004150390625,
+ :y2 210.7705078125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 212.4478759765625,
+ :x2 889.696533203125,
+ :y2 232.1658935546875,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 234.0487060546875,
+ :x2 77.96710205078125,
+ :y2 253.7667236328125,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 10},
+ :content {:text " rete quattro Atenei italiani e cinque Atenei palestinesi (l’Università degli Studi di Perugia, l’Università Politecnica delle Marche, l’Università degli Studi dell’Aquila e la Scuola Superiore Sant'Anna di Pisa"},
+ :properties {:color "green"}}
+ {:id #uuid "68878aa8-eb37-43b1-b57f-7825e1066334",
+ :page 10,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 234.0487060546875,
+ :x2 890.1746826171875,
+ :y2 275.162109375,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 197.99664306640625,
+ :y1 234.0487060546875,
+ :x2 890.1746826171875,
+ :y2 253.7667236328125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 255.444091796875,
+ :x2 536.195068359375,
+ :y2 275.162109375,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 10},
+ :content {:text " An-Najah National University; l’Al-Quds University, la Palestine Technical University – Kadoorie, Bethlehem University e l’Arab American University"},
+ :properties {:color "blue"}}
+ {:id #uuid "68878ac8-d4bc-4fc6-9213-9ed5d260fe91",
+ :page 10,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 731.894287109375,
+ :x2 890.09326171875,
+ :y2 794.6541748046875,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 546.5586547851562,
+ :y1 731.894287109375,
+ :x2 889.9869384765625,
+ :y2 751.6123046875,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 753.4949951171875,
+ :x2 890.09326171875,
+ :y2 773.2130126953125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 774.9361572265625,
+ :x2 652.9896850585938,
+ :y2 794.6541748046875,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 10},
+ :content {:text " l’educazione in senso ampio e la formazione degli insegnanti, la sensibilizzazione circa i diritti umani, l’implementazione delle scuole di diritto, la ricerca e le attività educative sul diritto comparato, nonché l’innovazione tecnologica."},
+ :properties {:color "green"}}
+ {:id #uuid "68878b16-19d9-414b-9093-1e28a9f37ede",
+ :page 10,
+ :position {:bounding {:x1 47.1954345703125,
+ :y1 1242.7596130371094,
+ :x2 889.739013671875,
+ :y2 1305.4852600097656,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 671.1355590820312,
+ :y1 1242.7596130371094,
+ :x2 889.739013671875,
+ :y2 1262.4776306152344,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 47.1954345703125,
+ :y1 1264.3604431152344,
+ :x2 889.03369140625,
+ :y2 1284.0784606933594,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 47.1954345703125,
+ :y1 1285.7672424316406,
+ :x2 644.1751708984375,
+ :y2 1305.4852600097656,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 10},
+ :content {:text " Education, Government and Civil Society (Legal and judicial development, Human rights, Women’s equality organisations and institutions), Communications and Industry (Information and communication technology"},
+ :properties {:color "blue"}}
+ {:id #uuid "68878b1e-0b73-4e45-8b75-815b01698b62",
+ :page 10,
+ :position {:bounding {:x1 0,
+ :y1 1285.7672424316406,
+ :x2 991.9940185546875,
+ :y2 2815.978485107422,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 668.3128051757812,
+ :y1 1285.7672424316406,
+ :x2 889.9404296875,
+ :y2 1305.4852600097656,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 0,
+ :y1 1412.9872741699219,
+ :x2 991.9940185546875,
+ :y2 2815.978485107422,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 10},
+ :content {:text "ICT, Industrial development,11 Engineering, Technological research and development)"},
+ :properties {:color "blue"}}
+ {:id #uuid "68878b2c-c434-4a11-b458-4989211b2880",
+ :page 11,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 382.8466796875,
+ :x2 890.0364990234375,
+ :y2 445.5609130859375,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 382.8466796875,
+ :x2 890.0364990234375,
+ :y2 402.564697265625,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 404.4473876953125,
+ :x2 889.4765930175781,
+ :y2 424.1654052734375,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 425.8428955078125,
+ :x2 103.30978393554688,
+ :y2 445.5609130859375,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 11},
+ :content {:text "- Verranno attribuite 9 borse di dottorato espressamente riservate a studenti palestinesi altamente motivati a operare nella cooperazione internazionale e a svolgere ricerca nei settori di interesse negli ambiti sopra indicati"},
+ :properties {:color "blue"}}
+ {:id #uuid "68878b48-c2d4-4f27-9752-076c6bfb6d9f",
+ :page 12,
+ :position {:bounding {:x1 94.39083862304688,
+ :y1 726.8963317871094,
+ :x2 890.2325439453125,
+ :y2 832.6524353027344,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 94.39083862304688,
+ :y1 726.8963317871094,
+ :x2 890.2325439453125,
+ :y2 746.6143493652344,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39083862304688,
+ :y1 748.2917175292969,
+ :x2 889.9522705078125,
+ :y2 768.0097351074219,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39083862304688,
+ :y1 769.9267272949219,
+ :x2 889.436279296875,
+ :y2 789.6447448730469,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39083862304688,
+ :y1 791.3335876464844,
+ :x2 889.6700439453125,
+ :y2 811.0516052246094,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39083862304688,
+ :y1 812.9344177246094,
+ :x2 212.2984619140625,
+ :y2 832.6524353027344,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 12},
+ :content {:text "L’intervento ha lo scopo di costruire un’infrastruttura resiliente e promuovere l'innovazione e uno sviluppo industriale e artigianale equo, responsabile e sostenibile. Ha altresì l’obiettivo di potenziare la ricerca scientifica, promuovere le capacità tecnologiche dei settori industriali e artigianali, garantendo un aumento significativo dell'accesso alle tecnologie dell'informazione e della comunicazione"},
+ :properties {:color "green"}}
+ {:id #uuid "688790f6-a019-4418-9cee-d661457baf32",
+ :page 17,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 427.6458740234375,
+ :x2 889.97607421875,
+ :y2 490.4171142578125,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 427.6458740234375,
+ :x2 808.3291015625,
+ :y2 447.3638916015625,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 449.0982666015625,
+ :x2 889.97607421875,
+ :y2 468.8162841796875,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 470.6990966796875,
+ :x2 873.475341796875,
+ :y2 490.4171142578125,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 17},
+ :content {:text "Attività 1.2. Attivazione di posizioni di PhD espressamente destinate a studenti palestinesi.1.2.1 Attivazione di n. 9 borse di dottorato (complessive per i 5 obiettivi specifici) presso le Università Italiane coinvolte nella rete progettuale espressamente destinate a studenti palestinesi nei main topics individuati."},
+ :properties {:color "green"}}
+ {:id #uuid "68879124-c8db-41bc-8409-2a088c52ae37",
+ :page 19,
+ :position {:bounding {:x1 45.392486572265625,
+ :y1 644.0989227294922,
+ :x2 890.0828857421875,
+ :y2 1007.6497039794922,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 45.392486572265625,
+ :y1 644.0989227294922,
+ :x2 537.4885864257812,
+ :y2 663.8168792724609,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 665.4943084716797,
+ :x2 889.6148986816406,
+ :y2 685.2123260498047,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 686.9011077880859,
+ :x2 890.0828857421875,
+ :y2 706.6191253662109,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 708.5019378662109,
+ :x2 433.93194580078125,
+ :y2 728.2199554443359,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 751.4981536865234,
+ :x2 889.5065002441406,
+ :y2 771.2161712646484,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 772.9277801513672,
+ :x2 178.41314697265625,
+ :y2 792.6457977294922,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 815.9354095458984,
+ :x2 889.88671875,
+ :y2 835.6534271240234,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 837.5362396240234,
+ :x2 889.6407775878906,
+ :y2 857.2542572021484,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 858.9316253662109,
+ :x2 341.549560546875,
+ :y2 878.6496429443359,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 901.9279022216797,
+ :x2 889.9644775390625,
+ :y2 921.6458587646484,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 923.5286712646484,
+ :x2 889.5953674316406,
+ :y2 943.2467498779297,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 944.9354705810547,
+ :x2 153.259521484375,
+ :y2 964.6534881591797,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 45.392486572265625,
+ :y1 987.9316864013672,
+ :x2 778.803955078125,
+ :y2 1007.6497039794922,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 19},
+ :content {:text "O.S.5. Communications&Industry/Innovazione tecnologica R.54.1. Lo sviluppo di infrastrutture di qualità, affidabili, sostenibili e resilienti, comprese le infrastrutture regionali e transfrontaliere, per sostenere lo sviluppo economico e il benessere umano, con particolare attenzione alla possibilità di accesso equo per tutti. R.5.2. La creazione di piccole o grandi imprese che favoriscano la resilienza dei giovani e la promozione del lavoro femminile. R.5.3. L’aggiornamento delle infrastrutture e l’ammodernamento delle industrie per renderle sostenibili, con maggiore efficienza delle risorse da utilizzare e una maggiore adozione di tecnologie pulite e rispettose dell'ambiente e dei processi industriali. R.5.4. Il potenziamento della ricerca scientifica, attraverso la promozione delle capacità tecnologiche dei settori industriali, anche incoraggiando l'innovazione e aumentando in modo sostanziale il numero dei lavoratori dei settori ricerca R.5.5. L’aumento significativo dell'accesso alle tecnologie dell'informazione e della comunicazion"},
+ :properties {:color "green"}}
+ {:id #uuid "68879148-1f5d-48e5-beca-ffff96d1e76f",
+ :page 20,
+ :position {:bounding {:x1 50.56689453125,
+ :y1 608.4968872070312,
+ :x2 310.2469482421875,
+ :y2 628.2149658203125,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 50.56689453125,
+ :y1 608.4968872070312,
+ :x2 310.2469482421875,
+ :y2 628.2149658203125,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 20},
+ :content {:text "’Università degli Studi dell’Aquila"},
+ :properties {:color "green"}}
+ {:id #uuid "68879172-c740-45b9-8533-44609dc624b6",
+ :page 32,
+ :position {:bounding {:x1 0,
+ :y1 455.83067321777344,
+ :x2 1402.9913330078125,
+ :y2 1993.9839324951172,
+ :width 1403.1999999999998,
+ :height 992.2},
+ :rects ({:x1 523.4744262695312,
+ :y1 455.83067321777344,
+ :x2 533.630126953125,
+ :y2 474.8184051513672,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 455.83067321777344,
+ :x2 669.8154907226562,
+ :y2 474.8184051513672,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 873.5147705078125,
+ :y1 455.83067321777344,
+ :x2 902.18798828125,
+ :y2 474.8184051513672,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 976.9088134765625,
+ :y1 456.2985382080078,
+ :x2 993.1693115234375,
+ :y2 477.47715759277344,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1157.96533203125,
+ :y1 456.2985382080078,
+ :x2 1174.2144775390625,
+ :y2 477.47715759277344,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 457.02882385253906,
+ :x2 1109.8204345703125,
+ :y2 476.0165252685547,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 457.02882385253906,
+ :x2 1261.124755859375,
+ :y2 476.0165252685547,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 476.2333221435547,
+ :x2 726.9940795898438,
+ :y2 495.22105407714844,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 477.43150329589844,
+ :x2 1069.1597900390625,
+ :y2 496.41917419433594,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 477.43150329589844,
+ :x2 1295.4755859375,
+ :y2 496.41917419433594,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 496.4305877685547,
+ :x2 683.9667358398438,
+ :y2 515.4183197021484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 497.8341522216797,
+ :x2 1071.5384521484375,
+ :y2 516.8218841552734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 497.8341522216797,
+ :x2 1307.1776123046875,
+ :y2 516.8218841552734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 516.8675384521484,
+ :x2 669.77880859375,
+ :y2 535.8552093505859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 518.0656585693359,
+ :x2 1267.023681640625,
+ :y2 537.0533905029297,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 976.9088134765625,
+ :y1 518.7388763427734,
+ :x2 993.1693115234375,
+ :y2 539.9175262451172,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 519.4692230224609,
+ :x2 1083.8585205078125,
+ :y2 538.4568939208984,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 523.4744262695312,
+ :y1 537.2701873779297,
+ :x2 533.630126953125,
+ :y2 556.2579193115234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 537.2701873779297,
+ :x2 724.9818115234375,
+ :y2 556.2579193115234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 873.5147705078125,
+ :y1 537.2701873779297,
+ :x2 902.18798828125,
+ :y2 556.2579193115234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 538.4683074951172,
+ :x2 1249.46142578125,
+ :y2 557.4560394287109,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 539.6664886474609,
+ :x2 1084.966064453125,
+ :y2 558.6541595458984,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 557.6614227294922,
+ :x2 696.956787109375,
+ :y2 576.6491546630859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 558.8709564208984,
+ :x2 1268.7781982421875,
+ :y2 577.8586883544922,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 560.0691375732422,
+ :x2 1091.7423095703125,
+ :y2 579.0568695068359,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 577.8701019287109,
+ :x2 718.512939453125,
+ :y2 596.8578338623047,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 579.2622528076172,
+ :x2 1279.2176513671875,
+ :y2 598.2499847412109,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 580.4717864990234,
+ :x2 1044.6431884765625,
+ :y2 599.4595184326172,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 598.2613372802734,
+ :x2 721.49072265625,
+ :y2 617.2490692138672,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 599.4709320068359,
+ :x2 1259.0018310546875,
+ :y2 618.4586639404297,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 976.9088134765625,
+ :y1 601.3309173583984,
+ :x2 993.1693115234375,
+ :y2 622.5095062255859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 602.0726165771484,
+ :x2 1095.1219482421875,
+ :y2 621.0602874755859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 618.6640472412109,
+ :x2 626.0029907226562,
+ :y2 637.6517181396484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 619.8621673583984,
+ :x2 1298.19921875,
+ :y2 638.8498992919922,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 622.4638519287109,
+ :x2 1060.848388671875,
+ :y2 641.4515838623047,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 523.4744262695312,
+ :y1 639.0666961669922,
+ :x2 533.630126953125,
+ :y2 658.0544281005859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 639.0666961669922,
+ :x2 669.8154907226562,
+ :y2 658.0544281005859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 873.5147705078125,
+ :y1 639.0666961669922,
+ :x2 902.18798828125,
+ :y2 658.0544281005859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 640.2648162841797,
+ :x2 1295.1378173828125,
+ :y2 659.2525482177734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 642.6725311279297,
+ :x2 1073.580810546875,
+ :y2 661.6602630615234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 198.02450561523438,
+ :y1 650.4661712646484,
+ :x2 475.07122802734375,
+ :y2 669.4539031982422,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 659.2639617919922,
+ :x2 726.165283203125,
+ :y2 678.2516937255859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 660.4620819091797,
+ :x2 1243.6650390625,
+ :y2 679.4498138427734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1006.9080810546875,
+ :y1 663.0637664794922,
+ :x2 1057.7767333984375,
+ :y2 682.0514984130859,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 198.02450561523438,
+ :y1 670.8688201904297,
+ :x2 277.1284484863281,
+ :y2 689.8565521240234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 679.6666107177734,
+ :x2 695.3907470703125,
+ :y2 698.6543426513672,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 680.8647918701172,
+ :x2 1284.2310791015625,
+ :y2 699.8524627685547,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 700.0693206787109,
+ :x2 718.1995849609375,
+ :y2 719.0569915771484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 701.2674407958984,
+ :x2 1310.9400634765625,
+ :y2 720.2551727294922,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 720.3121795654297,
+ :x2 720.9702758789062,
+ :y2 739.2999114990234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 721.7157440185547,
+ :x2 1289.626953125,
+ :y2 740.7034759521484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 523.4744262695312,
+ :y1 740.7148895263672,
+ :x2 533.630126953125,
+ :y2 759.7025604248047,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 740.7148895263672,
+ :x2 669.8154907226562,
+ :y2 759.7025604248047,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 873.5147705078125,
+ :y1 740.7148895263672,
+ :x2 902.18798828125,
+ :y2 759.7025604248047,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 741.9130096435547,
+ :x2 1288.214111328125,
+ :y2 760.9007415771484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 761.1175384521484,
+ :x2 717.7815551757812,
+ :y2 780.1052703857422,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 762.3156585693359,
+ :x2 1272.1346435546875,
+ :y2 781.3033905029297,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 781.5201873779297,
+ :x2 682.3221435546875,
+ :y2 800.5079193115234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 782.7183685302734,
+ :x2 1303.3740234375,
+ :y2 801.7060394287109,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 801.7174530029297,
+ :x2 678.5316162109375,
+ :y2 820.7051849365234,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 803.1210174560547,
+ :x2 1221.3316650390625,
+ :y2 822.1087493896484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 822.1201629638672,
+ :x2 693.4124755859375,
+ :y2 841.1078338623047,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1157.96533203125,
+ :y1 823.9800872802734,
+ :x2 1174.2144775390625,
+ :y2 845.1587371826172,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 824.7218475341797,
+ :x2 1270.4808349609375,
+ :y2 843.7095184326172,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 842.5228118896484,
+ :x2 702.2265014648438,
+ :y2 861.5105438232422,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 844.9191131591797,
+ :x2 1294.44287109375,
+ :y2 863.9067840576172,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 1187.964599609375,
+ :y1 865.3217620849609,
+ :x2 1268.811279296875,
+ :y2 884.3094940185547,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 0,
+ :y1 1001.9899139404297,
+ :x2 1402.9913330078125,
+ :y2 1993.9839324951172,
+ :width 1403.1999999999998,
+ :height 992.2}),
+ :page 32},
+ :content {:text "Communications&Industry/Innovazione tecnologica- La percentuale di incremento delle imprese dei settori ad alta e media tecnologia- L’incremento del numero delle piccole o grandi imprese che favoriscono la promozione del lavoro femminile.- La percentuale di incremento dell’adozione di tecnologie pulite e rispettose dell'ambiente e dei processi industriali.- La percentuale di incremento delle risorse finanziarie messe a disposizione per la ricerca scientifica sui settori dell’industria e10%15%10%20%- Determinazioni del piano operativo- Relazioni di valutazione intermedie e finale- Valutazioni a cura del Valuatore Esterno- Sviluppo di infrastrutture di qualità, affidabili, sostenibili e resilienti, comprese le infrastrutture regionali e transfrontaliere, per sostenere lo sviluppo economico e il benessere umano, con particolare attenzione alla possibilità di accesso equo per tutti.- Creazione di piccole o grandi imprese che"},
+ :properties {:color "green"}}
+ {:id #uuid "6887917b-696a-43a6-99e2-f3afb2e36051",
+ :page 33,
+ :position {:bounding {:x1 553.4736328125,
+ :y1 147.18902587890625,
+ :x2 715.2816162109375,
+ :y2 267.9732666015625,
+ :width 1403.1999999999998,
+ :height 992.2},
+ :rects ({:x1 553.4736328125,
+ :y1 147.18902587890625,
+ :x2 707.82373046875,
+ :y2 166.1767578125,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 167.58026123046875,
+ :x2 666.4944458007812,
+ :y2 186.5679931640625,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 187.98297119140625,
+ :x2 715.2816162109375,
+ :y2 206.97064208984375,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 208.3856201171875,
+ :x2 672.3053588867188,
+ :y2 227.37335205078125,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 228.5828857421875,
+ :x2 642.3067626953125,
+ :y2 247.57061767578125,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 553.4736328125,
+ :y1 248.98553466796875,
+ :x2 639.9515991210938,
+ :y2 267.9732666015625,
+ :width 1403.1999999999998,
+ :height 992.2}),
+ :page 33},
+ :content {:text "Il numero dei giovani e delle giovani che accedono ai dottorati di ricerca in materie scientifiche e tecnologiche"},
+ :properties {:color "blue"}}
+ {:id #uuid "6887919d-a485-4913-849a-7f66214f0b8e",
+ :page 36,
+ :position {:bounding {:x1 352.630615234375,
+ :y1 667.2515716552734,
+ :x2 668.12744140625,
+ :y2 793.8211517333984,
+ :width 1403.1999999999998,
+ :height 992.2},
+ :rects ({:x1 352.630615234375,
+ :y1 667.2515716552734,
+ :x2 664.9879760742188,
+ :y2 686.9695892333984,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 352.630615234375,
+ :y1 688.6470184326172,
+ :x2 664.8816528320312,
+ :y2 708.3650360107422,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 352.630615234375,
+ :y1 710.0538177490234,
+ :x2 665.1758422851562,
+ :y2 729.7718353271484,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 352.630615234375,
+ :y1 731.4948577880859,
+ :x2 665.2108764648438,
+ :y2 751.2128753662109,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 352.630615234375,
+ :y1 752.9017181396484,
+ :x2 416.36041259765625,
+ :y2 772.6197357177734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 430.82940673828125,
+ :y1 752.9017181396484,
+ :x2 511.6185302734375,
+ :y2 772.6197357177734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 526.0304565429688,
+ :y1 752.9017181396484,
+ :x2 552.9715576171875,
+ :y2 772.6197357177734,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 567.3948974609375,
+ :y1 754.3622894287109,
+ :x2 668.12744140625,
+ :y2 774.0803070068359,
+ :width 1403.1999999999998,
+ :height 992.2}
+ {:x1 352.630615234375,
+ :y1 774.1031341552734,
+ :x2 423.711669921875,
+ :y2 793.8211517333984,
+ :width 1403.1999999999998,
+ :height 992.2}),
+ :page 36},
+ :content {:text "Attivazione di n. 9 borse di dottorato(complessive per i 5 obiettivi specifici) presso le Università Italiane coinvolte nella rete progettuale espressamente destinate a studenti palestinesi nei main topics individuat"},
+ :properties {:color "green"}}],
+ :extra {:page 6}}
diff --git a/assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.pdf b/assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.pdf
new file mode 100644
index 00000000..bd073c09
Binary files /dev/null and b/assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.pdf differ
diff --git a/assets/blob.edn b/assets/blob.edn
index 484bd94d..ccedc3ea 100644
--- a/assets/blob.edn
+++ b/assets/blob.edn
@@ -44,5 +44,34 @@
:height 1403.1999999999998}),
:page 2},
:content {:text "che l'importo del trattamento retributivo annuo lordo omnicomprensivo è pari al trattamento iniziale spettante al ricercatore confermato a tempo definito. In sede di delibera tale trattamento economico è incrementabile secondo criteri di complessità del progetto di ricerca e comunque entro il trattamento iniziale spettante al ricercatore confermato a tempo pieno. I contratti di ricerca finanziati su fondi esterni di cui al precedente art. 2 comma 2, possono prevedere comunque un trattamento economico superiore, nel caso in cui l’importo sia stabilito dall’ente finanziatore"},
+ :properties {:color "green"}}
+ {:id #uuid "68d5408b-5055-4173-831e-7099bfe4931a",
+ :page 1,
+ :position {:bounding {:x1 94.39085388183594,
+ :y1 643.049072265625,
+ :x2 897.3003997802734,
+ :y2 711.685546875,
+ :width 992.2,
+ :height 1403.1999999999998},
+ :rects ({:x1 94.39085388183594,
+ :y1 643.049072265625,
+ :x2 897.3003997802734,
+ :y2 665.6882934570312,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 666.053466796875,
+ :x2 897.0400238037109,
+ :y2 688.692626953125,
+ :width 992.2,
+ :height 1403.1999999999998}
+ {:x1 94.39085388183594,
+ :y1 689.04638671875,
+ :x2 485.8333282470703,
+ :y2 711.685546875,
+ :width 992.2,
+ :height 1403.1999999999998}),
+ :page 1},
+ :content {:text "2. Nel caso di progetti di ricerca di carattere nazionale, europeo ed internazionale, i contratti di ricerca hanno durata biennale prorogabile fino a un ulteriore anno, in ragione delle specifiche esigenze relative agli obiettivi e alla tipologia del progetto"},
:properties {:color "green"}}],
- :extra {:page 1}}
+ :extra {:page 2}}
diff --git a/assets/blob.php.edn b/assets/blob.php.edn
new file mode 100644
index 00000000..1173e36f
--- /dev/null
+++ b/assets/blob.php.edn
@@ -0,0 +1,209 @@
+{:highlights [{:id #uuid "69297277-2ddf-4104-81a8-83ee8c65a9e2",
+ :page 1,
+ :position {:bounding {:x1 143.4690704345703,
+ :y1 415.7214050292969,
+ :x2 779.8266143798828,
+ :y2 453.9935302734375,
+ :width 871,
+ :height 1231.7952025801249},
+ :rects ({:x1 143.4690704345703,
+ :y1 415.7214050292969,
+ :x2 779.8266143798828,
+ :y2 433.97882080078125,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 435.7361145019531,
+ :x2 589.6850738525391,
+ :y2 453.9935302734375,
+ :width 871,
+ :height 1231.7952025801249}),
+ :page 1},
+ :content {:text "Gli incarichi di ricerca hanno durata minima di un anno e durata massima, compresi eventuali rinnovi o proroghe, di tre anni, anche non continuativi"},
+ :properties {:color "green"}}
+ {:id #uuid "6929728b-7242-4b4d-8808-7f8f3ebfc9ff",
+ :page 1,
+ :position {:bounding {:x1 143.4690704345703,
+ :y1 756.1766052246094,
+ :x2 779.7538604736328,
+ :y2 814.2808532714844,
+ :width 871,
+ :height 1231.7952025801249},
+ :rects ({:x1 143.4690704345703,
+ :y1 756.1766052246094,
+ :x2 779.6075592041016,
+ :y2 774.4340515136719,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 776.1913146972656,
+ :x2 779.7538604736328,
+ :y2 794.4487609863281,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 796.0234069824219,
+ :x2 606.6394805908203,
+ :y2 814.2808532714844,
+ :width 871,
+ :height 1231.7952025801249}),
+ :page 1},
+ :content {:text "Il conferimento di incarichi di ricerca avviene previo espletamento di procedure selettive che assicurano la valutazione comparativa dei candidati mediante esame dei titoli e delle pubblicazioni ed eventuale colloquio a opera di una commissione"},
+ :properties {:color "green"}}
+ {:id #uuid "692972a5-a982-42c6-986c-82044e13290c",
+ :page 1,
+ :position {:bounding {:x1 143.4690704345703,
+ :y1 1015.7057800292969,
+ :x2 780.1571044921875,
+ :y2 1073.8214416503906,
+ :width 871,
+ :height 1231.7952025801249},
+ :rects ({:x1 227.2825927734375,
+ :y1 1015.7057800292969,
+ :x2 780.1571044921875,
+ :y2 1033.9632263183594,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 1035.5493469238281,
+ :x2 779.9406890869141,
+ :y2 1053.8067321777344,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 1055.5640563964844,
+ :x2 280.27899169921875,
+ :y2 1073.8214416503906,
+ :width 871,
+ :height 1231.7952025801249}),
+ :page 1},
+ :content {:text " l’Università può attivare procedure di conferimento diretto, mediante avvisi pubblicati nel proprio sito internet ai fini della raccolta delle manifestazioni di interesse da parte dei candidati."},
+ :properties {:color "green"}}
+ {:id #uuid "692972b0-1a4a-4c28-ad55-ad14d7f33550",
+ :page 1,
+ :position {:bounding {:x1 143.4690704345703,
+ :y1 1075.5672912597656,
+ :x2 780.097412109375,
+ :y2 1133.6715393066406,
+ :width 871,
+ :height 1231.7952025801249},
+ :rects ({:x1 382.87554931640625,
+ :y1 1075.5672912597656,
+ :x2 780.097412109375,
+ :y2 1093.8247375488281,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 1095.3994445800781,
+ :x2 779.9925537109375,
+ :y2 1113.6568298339844,
+ :width 871,
+ :height 1231.7952025801249}
+ {:x1 143.4690704345703,
+ :y1 1115.4141540527344,
+ :x2 198.009521484375,
+ :y2 1133.6715393066406,
+ :width 871,
+ :height 1231.7952025801249}),
+ :page 1},
+ :content {:text "l'incarico di ricerca è conferito direttamente al candidato con un profilo scientifico-professionale ritenuto idoneo allo svolgimento del progetto stesso."},
+ :properties {:color "green"}}
+ {:id #uuid "6929737c-0fb3-4f8c-be41-d8b3020a00ad",
+ :page 2,
+ :position {:bounding {:x1 134.91583156585693,
+ :y1 263.69415283203125,
+ :x2 811.3495168685913,
+ :y2 283.41217041015625,
+ :width 937.0000000000001,
+ :height 1325.134448699859},
+ :rects ({:x1 134.91583156585693,
+ :y1 263.69415283203125,
+ :x2 144.23361110687256,
+ :y2 283.41217041015625,
+ :width 937.0000000000001,
+ :height 1325.134448699859}
+ {:x1 154.33224391937256,
+ :y1 263.69415283203125,
+ :x2 811.3495168685913,
+ :y2 283.41217041015625,
+ :width 937.0000000000001,
+ :height 1325.134448699859}),
+ :page 2},
+ :content {:text ". Incarichi di ricerca finanziati con altre risorse disponibili sul bilancio dei Dipartimenti."},
+ :properties {:color "green"}}
+ {:id #uuid "6929739f-0a0e-4212-9cb5-3d305f007b67",
+ :page 3,
+ :position {:bounding {:x1 0,
+ :y1 1143.9755859375,
+ :x2 936.9934692382812,
+ :y2 2659.9916381835938,
+ :width 937.0000000000001,
+ :height 1325.134448699859},
+ :rects ({:x1 232.331130027771,
+ :y1 1143.9755859375,
+ :x2 839.3591604232788,
+ :y2 1163.693603515625,
+ :width 937.0000000000001,
+ :height 1325.134448699859}
+ {:x1 154.33224391937256,
+ :y1 1165.485107421875,
+ :x2 838.9317312240601,
+ :y2 1185.203125,
+ :width 937.0000000000001,
+ :height 1325.134448699859}
+ {:x1 154.33224391937256,
+ :y1 1187.0174560546875,
+ :x2 838.9347829818726,
+ :y2 1206.7354736328125,
+ :width 937.0000000000001,
+ :height 1325.134448699859}
+ {:x1 154.33224391937256,
+ :y1 1208.3558349609375,
+ :x2 435.40203762054443,
+ :y2 1228.0738525390625,
+ :width 937.0000000000001,
+ :height 1325.134448699859}
+ {:x1 0,
+ :y1 1334.9938354492188,
+ :x2 936.9934692382812,
+ :y2 2659.9916381835938,
+ :width 937.0000000000001,
+ :height 1325.134448699859}),
+ :page 3},
+ :content {:text ", di titolo di laurea magistrale o a ciclo unico o di titolo conseguito all’estero valutato equivalente al solo fine del conferimento dell’incarico di ricerca dalla Commissione giudicatrice da non più di sei anni e di un curriculum idoneo all'assistenza allo svolgimento di attività di ricerca."},
+ :properties {:color "green"}}
+ {:id #uuid "692973b7-5e82-4927-b113-d2a0e73987a5",
+ :page 4,
+ :position {:bounding {:x1 267.59954738616943,
+ :y1 499.8310852050781,
+ :x2 360.34515285491943,
+ :y2 519.5490417480469,
+ :width 937.0000000000001,
+ :height 1325.134448699859},
+ :rects ({:x1 267.59954738616943,
+ :y1 499.8310852050781,
+ :x2 360.34515285491943,
+ :y2 519.5490417480469,
+ :width 937.0000000000001,
+ :height 1325.134448699859}),
+ :page 4},
+ :content {:text " potrà esser"},
+ :properties {:color "green"}}
+ {:id #uuid "692973ea-228f-46b4-8c0f-dc8223c38e5f",
+ :page 5,
+ :position {:bounding {:x1 154.33224391937256,
+ :y1 823.2155914306641,
+ :x2 559.5140676498413,
+ :y2 842.9336090087891,
+ :width 937.0000000000001,
+ :height 1325.134448699859},
+ :rects ({:x1 154.33224391937256,
+ :y1 823.2155914306641,
+ :x2 559.5140676498413,
+ :y2 842.9336090087891,
+ :width 937.0000000000001,
+ :height 1325.134448699859}),
+ :page 5},
+ :content {:text "l’indicazione del trattamento economico complessivo"},
+ :properties {:color "green"}}],
+ :extra {:page 2}}
diff --git a/assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.edn b/assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.edn
new file mode 100644
index 00000000..2a43f0db
--- /dev/null
+++ b/assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 6}}
diff --git a/assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.pdf b/assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.pdf
new file mode 100644
index 00000000..c3c9984c
Binary files /dev/null and b/assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.pdf differ
diff --git a/assets/brogliaccio_seduta_del_20250910_1757508393988_0.edn b/assets/brogliaccio_seduta_del_20250910_1757508393988_0.edn
new file mode 100644
index 00000000..7e01c536
--- /dev/null
+++ b/assets/brogliaccio_seduta_del_20250910_1757508393988_0.edn
@@ -0,0 +1,18 @@
+{:highlights [{:id #uuid "68c1772a-c6e9-420f-a505-a7d8a5ea6fe2",
+ :page 7,
+ :position {:bounding {:x1 383.59128788113594,
+ :y1 420.03472900390625,
+ :x2 624.9676306545734,
+ :y2 438.2921447753906,
+ :width 932,
+ :height 1318.0763293193884},
+ :rects ({:x1 383.59128788113594,
+ :y1 420.03472900390625,
+ :x2 624.9676306545734,
+ :y2 438.2921447753906,
+ :width 932,
+ :height 1318.0763293193884}),
+ :page 7},
+ :content {:text "Gruppo di Riesame di Dipartimento "},
+ :properties {:color "green"}}],
+ :extra {:page 48}}
diff --git a/assets/brogliaccio_seduta_del_20250910_1757508393988_0.pdf b/assets/brogliaccio_seduta_del_20250910_1757508393988_0.pdf
new file mode 100644
index 00000000..d969b972
Binary files /dev/null and b/assets/brogliaccio_seduta_del_20250910_1757508393988_0.pdf differ
diff --git a/assets/brogliaccio_seduta_del_20251015_1760531243507_0.edn b/assets/brogliaccio_seduta_del_20251015_1760531243507_0.edn
new file mode 100644
index 00000000..53b82e51
--- /dev/null
+++ b/assets/brogliaccio_seduta_del_20251015_1760531243507_0.edn
@@ -0,0 +1,59 @@
+{:highlights [{:id #uuid "68efa542-26fa-411a-be99-256bcc532ce6",
+ :page 299,
+ :position {:bounding {:x1 96.11161637306213,
+ :y1 325.1554870605469,
+ :x2 710.8904249668121,
+ :y2 359.7579040527344,
+ :width 806.9999999999999,
+ :height 1141.2957057518738},
+ :rects ({:x1 96.11161637306213,
+ :y1 325.1554870605469,
+ :x2 710.8904249668121,
+ :y2 340.9299011230469,
+ :width 806.9999999999999,
+ :height 1141.2957057518738}
+ {:x1 96.11161637306213,
+ :y1 343.9834899902344,
+ :x2 520.5850355625153,
+ :y2 359.7579040527344,
+ :width 806.9999999999999,
+ :height 1141.2957057518738}),
+ :page 299},
+ :content {:text "Blended Modeling per piattaforme low-code, in quanto introduce un approccio innovativo che supera la tradizionale separazione tra modelli logici e rappresentazioni grafiche"},
+ :properties {:color "green"}}
+ {:id #uuid "68efa560-d65e-42cc-bd5c-c6463280e3f5",
+ :page 299,
+ :position {:bounding {:x1 96.11161637306213,
+ :y1 419.2816467285156,
+ :x2 714.6287977695465,
+ :y2 491.5125427246094,
+ :width 806.9999999999999,
+ :height 1141.2957057518738},
+ :rects ({:x1 409.399427652359,
+ :y1 419.2816467285156,
+ :x2 714.6287977695465,
+ :y2 436.8087463378906,
+ :width 806.9999999999999,
+ :height 1141.2957057518738}
+ {:x1 96.11161637306213,
+ :y1 438.0959167480469,
+ :x2 710.8796827793121,
+ :y2 453.8703308105469,
+ :width 806.9999999999999,
+ :height 1141.2957057518738}
+ {:x1 96.11161637306213,
+ :y1 456.9238586425781,
+ :x2 710.8724501132965,
+ :y2 472.6982727050781,
+ :width 806.9999999999999,
+ :height 1141.2957057518738}
+ {:x1 96.11161637306213,
+ :y1 475.7381286621094,
+ :x2 367.470228433609,
+ :y2 491.5125427246094,
+ :width 806.9999999999999,
+ :height 1141.2957057518738}),
+ :page 299},
+ :content {:text ".Nonostante il lavoro svolto dal dott. Damiano Di Vincenzo abbia soddisfatto in maniera eccellente tutti i requisiti ed i problemi posti, si ritiene che ulteriori sviluppi ed approfondimenti siano necessari in particolare rispetto alle nuove opportunità di sperimentazione che il progetto sta dando luog"},
+ :properties {:color "blue"}}],
+ :extra {:page 604}}
diff --git a/assets/brogliaccio_seduta_del_20251015_1760531243507_0.pdf b/assets/brogliaccio_seduta_del_20251015_1760531243507_0.pdf
new file mode 100644
index 00000000..c9051c9a
Binary files /dev/null and b/assets/brogliaccio_seduta_del_20251015_1760531243507_0.pdf differ
diff --git a/assets/brogliaccio_seduta_del_20251112_1762955181674_0.edn b/assets/brogliaccio_seduta_del_20251112_1762955181674_0.edn
new file mode 100644
index 00000000..c59f7493
--- /dev/null
+++ b/assets/brogliaccio_seduta_del_20251112_1762955181674_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 21}}
diff --git a/assets/brogliaccio_seduta_del_20251112_1762955181674_0.pdf b/assets/brogliaccio_seduta_del_20251112_1762955181674_0.pdf
new file mode 100644
index 00000000..bb1aae9c
Binary files /dev/null and b/assets/brogliaccio_seduta_del_20251112_1762955181674_0.pdf differ
diff --git a/assets/brogliaccio_seduta_del_20251112_1762956046474_0.edn b/assets/brogliaccio_seduta_del_20251112_1762956046474_0.edn
new file mode 100644
index 00000000..396031a7
--- /dev/null
+++ b/assets/brogliaccio_seduta_del_20251112_1762956046474_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 25}}
diff --git a/assets/brogliaccio_seduta_del_20251112_1762956046474_0.pdf b/assets/brogliaccio_seduta_del_20251112_1762956046474_0.pdf
new file mode 100644
index 00000000..059c504d
Binary files /dev/null and b/assets/brogliaccio_seduta_del_20251112_1762956046474_0.pdf differ
diff --git a/assets/icse2023-paper1528_1666905345862_0.edn b/assets/icse2023-paper1528_1666905345862_0.edn
index 9f9795f2..125812b1 100644
--- a/assets/icse2023-paper1528_1666905345862_0.edn
+++ b/assets/icse2023-paper1528_1666905345862_0.edn
@@ -4954,4 +4954,4 @@
:page 10},
:content {:text "lack of guidance for “what” actions should be performed for a given dataset."},
:properties {:color "purple"}}],
- :extra {:page 2}}
+ :extra {:page 7}}
diff --git a/assets/icse2025-paper1580.edn b/assets/icse2025-paper1580.edn
new file mode 100644
index 00000000..6015423c
--- /dev/null
+++ b/assets/icse2025-paper1580.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 5}}
diff --git a/assets/image_1752660986330_0.png b/assets/image_1752660986330_0.png
new file mode 100644
index 00000000..f3eaf91b
Binary files /dev/null and b/assets/image_1752660986330_0.png differ
diff --git a/assets/image_1752661581443_0.png b/assets/image_1752661581443_0.png
new file mode 100644
index 00000000..eb3f89cf
Binary files /dev/null and b/assets/image_1752661581443_0.png differ
diff --git a/assets/image_1752827966114_0.png b/assets/image_1752827966114_0.png
new file mode 100644
index 00000000..c5d65a2c
Binary files /dev/null and b/assets/image_1752827966114_0.png differ
diff --git a/assets/image_1752828011033_0.png b/assets/image_1752828011033_0.png
new file mode 100644
index 00000000..0dd9873f
Binary files /dev/null and b/assets/image_1752828011033_0.png differ
diff --git a/assets/image_1752828052720_0.png b/assets/image_1752828052720_0.png
new file mode 100644
index 00000000..60f1ba70
Binary files /dev/null and b/assets/image_1752828052720_0.png differ
diff --git a/assets/image_1752828256831_0.png b/assets/image_1752828256831_0.png
new file mode 100644
index 00000000..d5be2882
Binary files /dev/null and b/assets/image_1752828256831_0.png differ
diff --git a/assets/image_1752828369008_0.png b/assets/image_1752828369008_0.png
new file mode 100644
index 00000000..16b55e46
Binary files /dev/null and b/assets/image_1752828369008_0.png differ
diff --git a/assets/image_1752828475860_0.png b/assets/image_1752828475860_0.png
new file mode 100644
index 00000000..4ae52ef7
Binary files /dev/null and b/assets/image_1752828475860_0.png differ
diff --git a/assets/image_1752828840318_0.png b/assets/image_1752828840318_0.png
new file mode 100644
index 00000000..ff49e952
Binary files /dev/null and b/assets/image_1752828840318_0.png differ
diff --git a/assets/image_1752828982148_0.png b/assets/image_1752828982148_0.png
new file mode 100644
index 00000000..3f19d78b
Binary files /dev/null and b/assets/image_1752828982148_0.png differ
diff --git a/assets/image_1752829063116_0.png b/assets/image_1752829063116_0.png
new file mode 100644
index 00000000..6c5f3788
Binary files /dev/null and b/assets/image_1752829063116_0.png differ
diff --git a/assets/image_1752829237854_0.png b/assets/image_1752829237854_0.png
new file mode 100644
index 00000000..51d0be43
Binary files /dev/null and b/assets/image_1752829237854_0.png differ
diff --git a/assets/image_1752829327469_0.png b/assets/image_1752829327469_0.png
new file mode 100644
index 00000000..411e434a
Binary files /dev/null and b/assets/image_1752829327469_0.png differ
diff --git a/assets/image_1752829400574_0.png b/assets/image_1752829400574_0.png
new file mode 100644
index 00000000..e5bb3ac4
Binary files /dev/null and b/assets/image_1752829400574_0.png differ
diff --git a/assets/image_1752829494367_0.png b/assets/image_1752829494367_0.png
new file mode 100644
index 00000000..b305122a
Binary files /dev/null and b/assets/image_1752829494367_0.png differ
diff --git a/assets/image_1752829607471_0.png b/assets/image_1752829607471_0.png
new file mode 100644
index 00000000..3a812737
Binary files /dev/null and b/assets/image_1752829607471_0.png differ
diff --git a/assets/image_1752829623019_0.png b/assets/image_1752829623019_0.png
new file mode 100644
index 00000000..f5da8d3a
Binary files /dev/null and b/assets/image_1752829623019_0.png differ
diff --git a/assets/image_1752829746468_0.png b/assets/image_1752829746468_0.png
new file mode 100644
index 00000000..e0536fea
Binary files /dev/null and b/assets/image_1752829746468_0.png differ
diff --git a/assets/image_1752829785723_0.png b/assets/image_1752829785723_0.png
new file mode 100644
index 00000000..3793c3f5
Binary files /dev/null and b/assets/image_1752829785723_0.png differ
diff --git a/assets/image_1752829948938_0.png b/assets/image_1752829948938_0.png
new file mode 100644
index 00000000..db48e63f
Binary files /dev/null and b/assets/image_1752829948938_0.png differ
diff --git a/assets/image_1752830626034_0.png b/assets/image_1752830626034_0.png
new file mode 100644
index 00000000..0bb2875f
Binary files /dev/null and b/assets/image_1752830626034_0.png differ
diff --git a/assets/image_1752830692756_0.png b/assets/image_1752830692756_0.png
new file mode 100644
index 00000000..73cec1fd
Binary files /dev/null and b/assets/image_1752830692756_0.png differ
diff --git a/assets/image_1752844038326_0.png b/assets/image_1752844038326_0.png
new file mode 100644
index 00000000..050e6c26
Binary files /dev/null and b/assets/image_1752844038326_0.png differ
diff --git a/assets/image_1752844166908_0.png b/assets/image_1752844166908_0.png
new file mode 100644
index 00000000..d56d1667
Binary files /dev/null and b/assets/image_1752844166908_0.png differ
diff --git a/assets/image_1752844268908_0.png b/assets/image_1752844268908_0.png
new file mode 100644
index 00000000..fbd9801d
Binary files /dev/null and b/assets/image_1752844268908_0.png differ
diff --git a/assets/image_1753448528510_0.png b/assets/image_1753448528510_0.png
new file mode 100644
index 00000000..c9e72cc3
Binary files /dev/null and b/assets/image_1753448528510_0.png differ
diff --git a/assets/image_1755684013718_0.png b/assets/image_1755684013718_0.png
new file mode 100644
index 00000000..1cf9a3fb
Binary files /dev/null and b/assets/image_1755684013718_0.png differ
diff --git a/assets/image_1755684068048_0.png b/assets/image_1755684068048_0.png
new file mode 100644
index 00000000..eb3f6bdb
Binary files /dev/null and b/assets/image_1755684068048_0.png differ
diff --git a/assets/image_1755872606461_0.png b/assets/image_1755872606461_0.png
new file mode 100644
index 00000000..bc0863d3
Binary files /dev/null and b/assets/image_1755872606461_0.png differ
diff --git a/assets/image_1756730968439_0.png b/assets/image_1756730968439_0.png
new file mode 100644
index 00000000..b854824b
Binary files /dev/null and b/assets/image_1756730968439_0.png differ
diff --git a/assets/image_1756731012893_0.png b/assets/image_1756731012893_0.png
new file mode 100644
index 00000000..be5a333c
Binary files /dev/null and b/assets/image_1756731012893_0.png differ
diff --git a/assets/image_1756731026653_0.png b/assets/image_1756731026653_0.png
new file mode 100644
index 00000000..4704e013
Binary files /dev/null and b/assets/image_1756731026653_0.png differ
diff --git a/assets/image_1756731056004_0.png b/assets/image_1756731056004_0.png
new file mode 100644
index 00000000..a1b206f0
Binary files /dev/null and b/assets/image_1756731056004_0.png differ
diff --git a/assets/image_1756731095891_0.png b/assets/image_1756731095891_0.png
new file mode 100644
index 00000000..3a1108fd
Binary files /dev/null and b/assets/image_1756731095891_0.png differ
diff --git a/assets/image_1756731123130_0.png b/assets/image_1756731123130_0.png
new file mode 100644
index 00000000..8f0ab404
Binary files /dev/null and b/assets/image_1756731123130_0.png differ
diff --git a/assets/image_1756731154361_0.png b/assets/image_1756731154361_0.png
new file mode 100644
index 00000000..ee9953cb
Binary files /dev/null and b/assets/image_1756731154361_0.png differ
diff --git a/assets/image_1756731182852_0.png b/assets/image_1756731182852_0.png
new file mode 100644
index 00000000..6877f0b5
Binary files /dev/null and b/assets/image_1756731182852_0.png differ
diff --git a/assets/image_1756731196350_0.png b/assets/image_1756731196350_0.png
new file mode 100644
index 00000000..7742fec9
Binary files /dev/null and b/assets/image_1756731196350_0.png differ
diff --git a/assets/image_1756731230828_0.png b/assets/image_1756731230828_0.png
new file mode 100644
index 00000000..a9158b02
Binary files /dev/null and b/assets/image_1756731230828_0.png differ
diff --git a/assets/image_1756731260195_0.png b/assets/image_1756731260195_0.png
new file mode 100644
index 00000000..622d0c7c
Binary files /dev/null and b/assets/image_1756731260195_0.png differ
diff --git a/assets/image_1756731270325_0.png b/assets/image_1756731270325_0.png
new file mode 100644
index 00000000..76395b89
Binary files /dev/null and b/assets/image_1756731270325_0.png differ
diff --git a/assets/image_1756731334437_0.png b/assets/image_1756731334437_0.png
new file mode 100644
index 00000000..c7aa3830
Binary files /dev/null and b/assets/image_1756731334437_0.png differ
diff --git a/assets/image_1756731344880_0.png b/assets/image_1756731344880_0.png
new file mode 100644
index 00000000..c9aba79b
Binary files /dev/null and b/assets/image_1756731344880_0.png differ
diff --git a/assets/image_1756731422652_0.png b/assets/image_1756731422652_0.png
new file mode 100644
index 00000000..f63f7cd7
Binary files /dev/null and b/assets/image_1756731422652_0.png differ
diff --git a/assets/image_1756732897643_0.png b/assets/image_1756732897643_0.png
new file mode 100644
index 00000000..ccf2fb47
Binary files /dev/null and b/assets/image_1756732897643_0.png differ
diff --git a/assets/image_1756732911224_0.png b/assets/image_1756732911224_0.png
new file mode 100644
index 00000000..3dfb477a
Binary files /dev/null and b/assets/image_1756732911224_0.png differ
diff --git a/assets/image_1756732979539_0.png b/assets/image_1756732979539_0.png
new file mode 100644
index 00000000..a2e96e8e
Binary files /dev/null and b/assets/image_1756732979539_0.png differ
diff --git a/assets/image_1756732990374_0.png b/assets/image_1756732990374_0.png
new file mode 100644
index 00000000..6eb8ff00
Binary files /dev/null and b/assets/image_1756732990374_0.png differ
diff --git a/assets/image_1756733148910_0.png b/assets/image_1756733148910_0.png
new file mode 100644
index 00000000..ffb82212
Binary files /dev/null and b/assets/image_1756733148910_0.png differ
diff --git a/assets/image_1756733252916_0.png b/assets/image_1756733252916_0.png
new file mode 100644
index 00000000..d133d2b6
Binary files /dev/null and b/assets/image_1756733252916_0.png differ
diff --git a/assets/image_1756733269130_0.png b/assets/image_1756733269130_0.png
new file mode 100644
index 00000000..dd2d903d
Binary files /dev/null and b/assets/image_1756733269130_0.png differ
diff --git a/assets/image_1756733280118_0.png b/assets/image_1756733280118_0.png
new file mode 100644
index 00000000..d63c2336
Binary files /dev/null and b/assets/image_1756733280118_0.png differ
diff --git a/assets/image_1756733286917_0.png b/assets/image_1756733286917_0.png
new file mode 100644
index 00000000..c47a5e6f
Binary files /dev/null and b/assets/image_1756733286917_0.png differ
diff --git a/assets/image_1756733307931_0.png b/assets/image_1756733307931_0.png
new file mode 100644
index 00000000..a1c7d633
Binary files /dev/null and b/assets/image_1756733307931_0.png differ
diff --git a/assets/image_1756733720525_0.png b/assets/image_1756733720525_0.png
new file mode 100644
index 00000000..0b6fbd64
Binary files /dev/null and b/assets/image_1756733720525_0.png differ
diff --git a/assets/image_1758026244401_0.png b/assets/image_1758026244401_0.png
new file mode 100644
index 00000000..3dde835b
Binary files /dev/null and b/assets/image_1758026244401_0.png differ
diff --git a/assets/image_1758026288177_0.png b/assets/image_1758026288177_0.png
new file mode 100644
index 00000000..03bdce74
Binary files /dev/null and b/assets/image_1758026288177_0.png differ
diff --git a/assets/image_1758026357281_0.png b/assets/image_1758026357281_0.png
new file mode 100644
index 00000000..223c9f3c
Binary files /dev/null and b/assets/image_1758026357281_0.png differ
diff --git a/assets/image_1758026397882_0.png b/assets/image_1758026397882_0.png
new file mode 100644
index 00000000..a7722f3e
Binary files /dev/null and b/assets/image_1758026397882_0.png differ
diff --git a/assets/image_1758026438853_0.png b/assets/image_1758026438853_0.png
new file mode 100644
index 00000000..bd4801f1
Binary files /dev/null and b/assets/image_1758026438853_0.png differ
diff --git a/assets/image_1758026508462_0.png b/assets/image_1758026508462_0.png
new file mode 100644
index 00000000..b603660d
Binary files /dev/null and b/assets/image_1758026508462_0.png differ
diff --git a/assets/image_1758027202868_0.png b/assets/image_1758027202868_0.png
new file mode 100644
index 00000000..c3799656
Binary files /dev/null and b/assets/image_1758027202868_0.png differ
diff --git a/assets/image_1758027303873_0.png b/assets/image_1758027303873_0.png
new file mode 100644
index 00000000..c03ddb0d
Binary files /dev/null and b/assets/image_1758027303873_0.png differ
diff --git a/assets/image_1758027563157_0.png b/assets/image_1758027563157_0.png
new file mode 100644
index 00000000..ec579334
Binary files /dev/null and b/assets/image_1758027563157_0.png differ
diff --git a/assets/image_1758027583266_0.png b/assets/image_1758027583266_0.png
new file mode 100644
index 00000000..76f67542
Binary files /dev/null and b/assets/image_1758027583266_0.png differ
diff --git a/assets/image_1758532616529_0.png b/assets/image_1758532616529_0.png
new file mode 100644
index 00000000..3707e02a
Binary files /dev/null and b/assets/image_1758532616529_0.png differ
diff --git a/assets/image_1758532676441_0.png b/assets/image_1758532676441_0.png
new file mode 100644
index 00000000..764fca25
Binary files /dev/null and b/assets/image_1758532676441_0.png differ
diff --git a/assets/image_1758532699845_0.png b/assets/image_1758532699845_0.png
new file mode 100644
index 00000000..a844d4d5
Binary files /dev/null and b/assets/image_1758532699845_0.png differ
diff --git a/assets/image_1758532713577_0.png b/assets/image_1758532713577_0.png
new file mode 100644
index 00000000..e047e609
Binary files /dev/null and b/assets/image_1758532713577_0.png differ
diff --git a/assets/image_1758532732075_0.png b/assets/image_1758532732075_0.png
new file mode 100644
index 00000000..eefe6baf
Binary files /dev/null and b/assets/image_1758532732075_0.png differ
diff --git a/assets/image_1758532757543_0.png b/assets/image_1758532757543_0.png
new file mode 100644
index 00000000..ea68e272
Binary files /dev/null and b/assets/image_1758532757543_0.png differ
diff --git a/assets/image_1758532771354_0.png b/assets/image_1758532771354_0.png
new file mode 100644
index 00000000..15a9315d
Binary files /dev/null and b/assets/image_1758532771354_0.png differ
diff --git a/assets/image_1758532790542_0.png b/assets/image_1758532790542_0.png
new file mode 100644
index 00000000..aa782502
Binary files /dev/null and b/assets/image_1758532790542_0.png differ
diff --git a/assets/image_1758532808914_0.png b/assets/image_1758532808914_0.png
new file mode 100644
index 00000000..1e43b0ef
Binary files /dev/null and b/assets/image_1758532808914_0.png differ
diff --git a/assets/image_1758532828294_0.png b/assets/image_1758532828294_0.png
new file mode 100644
index 00000000..c27e0b75
Binary files /dev/null and b/assets/image_1758532828294_0.png differ
diff --git a/assets/image_1758532848456_0.png b/assets/image_1758532848456_0.png
new file mode 100644
index 00000000..883ea777
Binary files /dev/null and b/assets/image_1758532848456_0.png differ
diff --git a/assets/image_1758532862162_0.png b/assets/image_1758532862162_0.png
new file mode 100644
index 00000000..569c96b0
Binary files /dev/null and b/assets/image_1758532862162_0.png differ
diff --git a/assets/image_1758532883896_0.png b/assets/image_1758532883896_0.png
new file mode 100644
index 00000000..166ac5e4
Binary files /dev/null and b/assets/image_1758532883896_0.png differ
diff --git a/assets/image_1758532903598_0.png b/assets/image_1758532903598_0.png
new file mode 100644
index 00000000..0cc8ef95
Binary files /dev/null and b/assets/image_1758532903598_0.png differ
diff --git a/assets/image_1758532918420_0.png b/assets/image_1758532918420_0.png
new file mode 100644
index 00000000..04d68085
Binary files /dev/null and b/assets/image_1758532918420_0.png differ
diff --git a/assets/image_1758803685302_0.png b/assets/image_1758803685302_0.png
new file mode 100644
index 00000000..5450476b
Binary files /dev/null and b/assets/image_1758803685302_0.png differ
diff --git a/assets/image_1758803719275_0.png b/assets/image_1758803719275_0.png
new file mode 100644
index 00000000..3cb72084
Binary files /dev/null and b/assets/image_1758803719275_0.png differ
diff --git a/assets/image_1758803769932_0.png b/assets/image_1758803769932_0.png
new file mode 100644
index 00000000..a603336d
Binary files /dev/null and b/assets/image_1758803769932_0.png differ
diff --git a/assets/image_1758803879569_0.png b/assets/image_1758803879569_0.png
new file mode 100644
index 00000000..100bac34
Binary files /dev/null and b/assets/image_1758803879569_0.png differ
diff --git a/assets/image_1758806339815_0.png b/assets/image_1758806339815_0.png
new file mode 100644
index 00000000..482f6c0d
Binary files /dev/null and b/assets/image_1758806339815_0.png differ
diff --git a/assets/image_1759652205466_0.png b/assets/image_1759652205466_0.png
new file mode 100644
index 00000000..fecbfdb8
Binary files /dev/null and b/assets/image_1759652205466_0.png differ
diff --git a/assets/image_1760000615546_0.png b/assets/image_1760000615546_0.png
new file mode 100644
index 00000000..da654c52
Binary files /dev/null and b/assets/image_1760000615546_0.png differ
diff --git a/assets/image_1760000637406_0.png b/assets/image_1760000637406_0.png
new file mode 100644
index 00000000..cdcfe7c4
Binary files /dev/null and b/assets/image_1760000637406_0.png differ
diff --git a/assets/image_1760000659290_0.png b/assets/image_1760000659290_0.png
new file mode 100644
index 00000000..7b35caa7
Binary files /dev/null and b/assets/image_1760000659290_0.png differ
diff --git a/assets/image_1760000715434_0.png b/assets/image_1760000715434_0.png
new file mode 100644
index 00000000..a493d5f9
Binary files /dev/null and b/assets/image_1760000715434_0.png differ
diff --git a/assets/image_1760000786784_0.png b/assets/image_1760000786784_0.png
new file mode 100644
index 00000000..c6e9ef17
Binary files /dev/null and b/assets/image_1760000786784_0.png differ
diff --git a/assets/image_1760000825109_0.png b/assets/image_1760000825109_0.png
new file mode 100644
index 00000000..cd1bb0a4
Binary files /dev/null and b/assets/image_1760000825109_0.png differ
diff --git a/assets/image_1760000867730_0.png b/assets/image_1760000867730_0.png
new file mode 100644
index 00000000..a86e8f8e
Binary files /dev/null and b/assets/image_1760000867730_0.png differ
diff --git a/assets/image_1760000928677_0.png b/assets/image_1760000928677_0.png
new file mode 100644
index 00000000..563bcd78
Binary files /dev/null and b/assets/image_1760000928677_0.png differ
diff --git a/assets/image_1760001286821_0.png b/assets/image_1760001286821_0.png
new file mode 100644
index 00000000..a395843e
Binary files /dev/null and b/assets/image_1760001286821_0.png differ
diff --git a/assets/image_1760001419806_0.png b/assets/image_1760001419806_0.png
new file mode 100644
index 00000000..e69de29b
diff --git a/assets/image_1760001632136_0.png b/assets/image_1760001632136_0.png
new file mode 100644
index 00000000..6cbb3624
Binary files /dev/null and b/assets/image_1760001632136_0.png differ
diff --git a/assets/image_1760001669740_0.png b/assets/image_1760001669740_0.png
new file mode 100644
index 00000000..1a092f15
Binary files /dev/null and b/assets/image_1760001669740_0.png differ
diff --git a/assets/image_1760532542241_0.png b/assets/image_1760532542241_0.png
new file mode 100644
index 00000000..fdd13bab
Binary files /dev/null and b/assets/image_1760532542241_0.png differ
diff --git a/assets/image_1760533647217_0.png b/assets/image_1760533647217_0.png
new file mode 100644
index 00000000..094b5b4b
Binary files /dev/null and b/assets/image_1760533647217_0.png differ
diff --git a/assets/image_1760602269662_0.png b/assets/image_1760602269662_0.png
new file mode 100644
index 00000000..c313cf8c
Binary files /dev/null and b/assets/image_1760602269662_0.png differ
diff --git a/assets/image_1760602283258_0.png b/assets/image_1760602283258_0.png
new file mode 100644
index 00000000..5c6945b3
Binary files /dev/null and b/assets/image_1760602283258_0.png differ
diff --git a/assets/image_1760602683549_0.png b/assets/image_1760602683549_0.png
new file mode 100644
index 00000000..c91a26d5
Binary files /dev/null and b/assets/image_1760602683549_0.png differ
diff --git a/assets/image_1760602902943_0.png b/assets/image_1760602902943_0.png
new file mode 100644
index 00000000..4208b67a
Binary files /dev/null and b/assets/image_1760602902943_0.png differ
diff --git a/assets/image_1760602976597_0.png b/assets/image_1760602976597_0.png
new file mode 100644
index 00000000..d3373131
Binary files /dev/null and b/assets/image_1760602976597_0.png differ
diff --git a/assets/image_1760603135329_0.png b/assets/image_1760603135329_0.png
new file mode 100644
index 00000000..87af1b47
Binary files /dev/null and b/assets/image_1760603135329_0.png differ
diff --git a/assets/image_1760603147888_0.png b/assets/image_1760603147888_0.png
new file mode 100644
index 00000000..603437f8
Binary files /dev/null and b/assets/image_1760603147888_0.png differ
diff --git a/assets/image_1760603242308_0.png b/assets/image_1760603242308_0.png
new file mode 100644
index 00000000..9407e892
Binary files /dev/null and b/assets/image_1760603242308_0.png differ
diff --git a/assets/image_1760603377503_0.png b/assets/image_1760603377503_0.png
new file mode 100644
index 00000000..4f19a604
Binary files /dev/null and b/assets/image_1760603377503_0.png differ
diff --git a/assets/image_1760603546831_0.png b/assets/image_1760603546831_0.png
new file mode 100644
index 00000000..e2d6e964
Binary files /dev/null and b/assets/image_1760603546831_0.png differ
diff --git a/assets/image_1760603661216_0.png b/assets/image_1760603661216_0.png
new file mode 100644
index 00000000..e99c9c70
Binary files /dev/null and b/assets/image_1760603661216_0.png differ
diff --git a/assets/image_1760603759028_0.png b/assets/image_1760603759028_0.png
new file mode 100644
index 00000000..6dd8f9fc
Binary files /dev/null and b/assets/image_1760603759028_0.png differ
diff --git a/assets/image_1760603847565_0.png b/assets/image_1760603847565_0.png
new file mode 100644
index 00000000..5294733b
Binary files /dev/null and b/assets/image_1760603847565_0.png differ
diff --git a/assets/image_1760603922086_0.png b/assets/image_1760603922086_0.png
new file mode 100644
index 00000000..52a9a3a6
Binary files /dev/null and b/assets/image_1760603922086_0.png differ
diff --git a/assets/image_1760604140589_0.png b/assets/image_1760604140589_0.png
new file mode 100644
index 00000000..4241b7bb
Binary files /dev/null and b/assets/image_1760604140589_0.png differ
diff --git a/assets/image_1760604710962_0.png b/assets/image_1760604710962_0.png
new file mode 100644
index 00000000..4cf29f13
Binary files /dev/null and b/assets/image_1760604710962_0.png differ
diff --git a/assets/image_1760605500489_0.png b/assets/image_1760605500489_0.png
new file mode 100644
index 00000000..892e3379
Binary files /dev/null and b/assets/image_1760605500489_0.png differ
diff --git a/assets/image_1760605539918_0.png b/assets/image_1760605539918_0.png
new file mode 100644
index 00000000..e19695e9
Binary files /dev/null and b/assets/image_1760605539918_0.png differ
diff --git a/assets/image_1760605571243_0.png b/assets/image_1760605571243_0.png
new file mode 100644
index 00000000..6c318da3
Binary files /dev/null and b/assets/image_1760605571243_0.png differ
diff --git a/assets/image_1760605608630_0.png b/assets/image_1760605608630_0.png
new file mode 100644
index 00000000..6b21c3d2
Binary files /dev/null and b/assets/image_1760605608630_0.png differ
diff --git a/assets/image_1760605717529_0.png b/assets/image_1760605717529_0.png
new file mode 100644
index 00000000..66b9753b
Binary files /dev/null and b/assets/image_1760605717529_0.png differ
diff --git a/assets/image_1760606114709_0.png b/assets/image_1760606114709_0.png
new file mode 100644
index 00000000..3017c859
Binary files /dev/null and b/assets/image_1760606114709_0.png differ
diff --git a/assets/image_1760606607197_0.png b/assets/image_1760606607197_0.png
new file mode 100644
index 00000000..e8cb24f3
Binary files /dev/null and b/assets/image_1760606607197_0.png differ
diff --git a/assets/image_1760606781314_0.png b/assets/image_1760606781314_0.png
new file mode 100644
index 00000000..12342fca
Binary files /dev/null and b/assets/image_1760606781314_0.png differ
diff --git a/assets/image_1760606794032_0.png b/assets/image_1760606794032_0.png
new file mode 100644
index 00000000..cc8d8c71
Binary files /dev/null and b/assets/image_1760606794032_0.png differ
diff --git a/assets/image_1760606914086_0.png b/assets/image_1760606914086_0.png
new file mode 100644
index 00000000..8b1b18bb
Binary files /dev/null and b/assets/image_1760606914086_0.png differ
diff --git a/assets/image_1760606964911_0.png b/assets/image_1760606964911_0.png
new file mode 100644
index 00000000..448985f5
Binary files /dev/null and b/assets/image_1760606964911_0.png differ
diff --git a/assets/image_1760607112050_0.png b/assets/image_1760607112050_0.png
new file mode 100644
index 00000000..073d1b29
Binary files /dev/null and b/assets/image_1760607112050_0.png differ
diff --git a/assets/image_1760607199552_0.png b/assets/image_1760607199552_0.png
new file mode 100644
index 00000000..34d58355
Binary files /dev/null and b/assets/image_1760607199552_0.png differ
diff --git a/assets/image_1760607255126_0.png b/assets/image_1760607255126_0.png
new file mode 100644
index 00000000..9aa80d52
Binary files /dev/null and b/assets/image_1760607255126_0.png differ
diff --git a/assets/image_1760607514814_0.png b/assets/image_1760607514814_0.png
new file mode 100644
index 00000000..e2e9357f
Binary files /dev/null and b/assets/image_1760607514814_0.png differ
diff --git a/assets/image_1760607634129_0.png b/assets/image_1760607634129_0.png
new file mode 100644
index 00000000..385415ce
Binary files /dev/null and b/assets/image_1760607634129_0.png differ
diff --git a/assets/image_1762955000235_0.png b/assets/image_1762955000235_0.png
new file mode 100644
index 00000000..d49b177b
Binary files /dev/null and b/assets/image_1762955000235_0.png differ
diff --git a/assets/image_1762956452631_0.png b/assets/image_1762956452631_0.png
new file mode 100644
index 00000000..3099f80e
Binary files /dev/null and b/assets/image_1762956452631_0.png differ
diff --git a/assets/image_1764006218234_0.png b/assets/image_1764006218234_0.png
new file mode 100644
index 00000000..5c948d8c
Binary files /dev/null and b/assets/image_1764006218234_0.png differ
diff --git a/assets/image_1764006226420_0.png b/assets/image_1764006226420_0.png
new file mode 100644
index 00000000..87f3799c
Binary files /dev/null and b/assets/image_1764006226420_0.png differ
diff --git a/assets/image_1764006262456_0.png b/assets/image_1764006262456_0.png
new file mode 100644
index 00000000..2190bfd8
Binary files /dev/null and b/assets/image_1764006262456_0.png differ
diff --git a/assets/image_1764842919972_0.png b/assets/image_1764842919972_0.png
new file mode 100644
index 00000000..5289f314
Binary files /dev/null and b/assets/image_1764842919972_0.png differ
diff --git a/assets/image_1764844177625_0.png b/assets/image_1764844177625_0.png
new file mode 100644
index 00000000..08d1eca1
Binary files /dev/null and b/assets/image_1764844177625_0.png differ
diff --git a/assets/image_1764844336583_0.png b/assets/image_1764844336583_0.png
new file mode 100644
index 00000000..4557bb67
Binary files /dev/null and b/assets/image_1764844336583_0.png differ
diff --git a/assets/image_1764844677121_0.png b/assets/image_1764844677121_0.png
new file mode 100644
index 00000000..65e43800
Binary files /dev/null and b/assets/image_1764844677121_0.png differ
diff --git a/assets/image_1764844721345_0.png b/assets/image_1764844721345_0.png
new file mode 100644
index 00000000..dbd912ab
Binary files /dev/null and b/assets/image_1764844721345_0.png differ
diff --git a/assets/image_1764844747551_0.png b/assets/image_1764844747551_0.png
new file mode 100644
index 00000000..6bd0d7b4
Binary files /dev/null and b/assets/image_1764844747551_0.png differ
diff --git a/assets/image_1764844817776_0.png b/assets/image_1764844817776_0.png
new file mode 100644
index 00000000..f54e183d
Binary files /dev/null and b/assets/image_1764844817776_0.png differ
diff --git a/assets/image_1764844850256_0.png b/assets/image_1764844850256_0.png
new file mode 100644
index 00000000..6282514b
Binary files /dev/null and b/assets/image_1764844850256_0.png differ
diff --git a/assets/image_1764844905586_0.png b/assets/image_1764844905586_0.png
new file mode 100644
index 00000000..f58f5e6e
Binary files /dev/null and b/assets/image_1764844905586_0.png differ
diff --git a/assets/image_1764844929345_0.png b/assets/image_1764844929345_0.png
new file mode 100644
index 00000000..88c81972
Binary files /dev/null and b/assets/image_1764844929345_0.png differ
diff --git a/assets/image_1764845013240_0.png b/assets/image_1764845013240_0.png
new file mode 100644
index 00000000..d9c40ffa
Binary files /dev/null and b/assets/image_1764845013240_0.png differ
diff --git a/assets/image_1764845095255_0.png b/assets/image_1764845095255_0.png
new file mode 100644
index 00000000..ffd2868f
Binary files /dev/null and b/assets/image_1764845095255_0.png differ
diff --git a/assets/image_1764845121698_0.png b/assets/image_1764845121698_0.png
new file mode 100644
index 00000000..03a82bf9
Binary files /dev/null and b/assets/image_1764845121698_0.png differ
diff --git a/assets/image_1764845200368_0.png b/assets/image_1764845200368_0.png
new file mode 100644
index 00000000..3639b98f
Binary files /dev/null and b/assets/image_1764845200368_0.png differ
diff --git a/assets/image_1764845231695_0.png b/assets/image_1764845231695_0.png
new file mode 100644
index 00000000..dfb50b17
Binary files /dev/null and b/assets/image_1764845231695_0.png differ
diff --git a/assets/image_1764845299053_0.png b/assets/image_1764845299053_0.png
new file mode 100644
index 00000000..901da1e7
Binary files /dev/null and b/assets/image_1764845299053_0.png differ
diff --git a/assets/image_1765365483941_0.png b/assets/image_1765365483941_0.png
new file mode 100644
index 00000000..5f09fdf7
Binary files /dev/null and b/assets/image_1765365483941_0.png differ
diff --git a/assets/image_1765367415246_0.png b/assets/image_1765367415246_0.png
new file mode 100644
index 00000000..8fb7d4bb
Binary files /dev/null and b/assets/image_1765367415246_0.png differ
diff --git a/assets/image_1765472158589_0.png b/assets/image_1765472158589_0.png
new file mode 100644
index 00000000..67787063
Binary files /dev/null and b/assets/image_1765472158589_0.png differ
diff --git a/assets/image_1765472378222_0.png b/assets/image_1765472378222_0.png
new file mode 100644
index 00000000..bc4fb544
Binary files /dev/null and b/assets/image_1765472378222_0.png differ
diff --git a/assets/image_1765879534794_0.png b/assets/image_1765879534794_0.png
new file mode 100644
index 00000000..3aa7cebb
Binary files /dev/null and b/assets/image_1765879534794_0.png differ
diff --git a/assets/image_1765879670317_0.png b/assets/image_1765879670317_0.png
new file mode 100644
index 00000000..2580fff4
Binary files /dev/null and b/assets/image_1765879670317_0.png differ
diff --git a/assets/image_1765879695762_0.png b/assets/image_1765879695762_0.png
new file mode 100644
index 00000000..5387c75c
Binary files /dev/null and b/assets/image_1765879695762_0.png differ
diff --git a/assets/image_1765879801742_0.png b/assets/image_1765879801742_0.png
new file mode 100644
index 00000000..39de38de
Binary files /dev/null and b/assets/image_1765879801742_0.png differ
diff --git a/assets/image_1765879919499_0.png b/assets/image_1765879919499_0.png
new file mode 100644
index 00000000..e6e746c0
Binary files /dev/null and b/assets/image_1765879919499_0.png differ
diff --git a/assets/image_1765880213606_0.png b/assets/image_1765880213606_0.png
new file mode 100644
index 00000000..84d64b1b
Binary files /dev/null and b/assets/image_1765880213606_0.png differ
diff --git a/assets/image_1765880395778_0.png b/assets/image_1765880395778_0.png
new file mode 100644
index 00000000..dec84077
Binary files /dev/null and b/assets/image_1765880395778_0.png differ
diff --git a/assets/image_1765880522726_0.png b/assets/image_1765880522726_0.png
new file mode 100644
index 00000000..19ed1627
Binary files /dev/null and b/assets/image_1765880522726_0.png differ
diff --git a/assets/image_1765880598517_0.png b/assets/image_1765880598517_0.png
new file mode 100644
index 00000000..95f96a69
Binary files /dev/null and b/assets/image_1765880598517_0.png differ
diff --git a/assets/image_1765880733599_0.png b/assets/image_1765880733599_0.png
new file mode 100644
index 00000000..48440981
Binary files /dev/null and b/assets/image_1765880733599_0.png differ
diff --git a/assets/image_1765880798858_0.png b/assets/image_1765880798858_0.png
new file mode 100644
index 00000000..f53b79c2
Binary files /dev/null and b/assets/image_1765880798858_0.png differ
diff --git a/assets/image_1765880877880_0.png b/assets/image_1765880877880_0.png
new file mode 100644
index 00000000..ce26600b
Binary files /dev/null and b/assets/image_1765880877880_0.png differ
diff --git a/assets/image_1765880935796_0.png b/assets/image_1765880935796_0.png
new file mode 100644
index 00000000..746b9cce
Binary files /dev/null and b/assets/image_1765880935796_0.png differ
diff --git a/assets/image_1765881029140_0.png b/assets/image_1765881029140_0.png
new file mode 100644
index 00000000..1689b92c
Binary files /dev/null and b/assets/image_1765881029140_0.png differ
diff --git a/assets/image_1765881090479_0.png b/assets/image_1765881090479_0.png
new file mode 100644
index 00000000..22ef0cf7
Binary files /dev/null and b/assets/image_1765881090479_0.png differ
diff --git a/assets/image_1765881219782_0.png b/assets/image_1765881219782_0.png
new file mode 100644
index 00000000..ce04908b
Binary files /dev/null and b/assets/image_1765881219782_0.png differ
diff --git a/assets/image_1765881372918_0.png b/assets/image_1765881372918_0.png
new file mode 100644
index 00000000..a1ef759e
Binary files /dev/null and b/assets/image_1765881372918_0.png differ
diff --git a/assets/image_1765881408356_0.png b/assets/image_1765881408356_0.png
new file mode 100644
index 00000000..7f4422fc
Binary files /dev/null and b/assets/image_1765881408356_0.png differ
diff --git a/assets/image_1765883532171_0.png b/assets/image_1765883532171_0.png
new file mode 100644
index 00000000..cb462aaa
Binary files /dev/null and b/assets/image_1765883532171_0.png differ
diff --git a/assets/image_1765985835862_0.png b/assets/image_1765985835862_0.png
new file mode 100644
index 00000000..c3091ecd
Binary files /dev/null and b/assets/image_1765985835862_0.png differ
diff --git a/assets/image_1765985883486_0.png b/assets/image_1765985883486_0.png
new file mode 100644
index 00000000..f82d7cf6
Binary files /dev/null and b/assets/image_1765985883486_0.png differ
diff --git a/assets/image_1765987186206_0.png b/assets/image_1765987186206_0.png
new file mode 100644
index 00000000..79315c4a
Binary files /dev/null and b/assets/image_1765987186206_0.png differ
diff --git a/assets/image_1766132783568_0.png b/assets/image_1766132783568_0.png
new file mode 100644
index 00000000..0aeb87bb
Binary files /dev/null and b/assets/image_1766132783568_0.png differ
diff --git a/assets/image_1766132824023_0.png b/assets/image_1766132824023_0.png
new file mode 100644
index 00000000..693883be
Binary files /dev/null and b/assets/image_1766132824023_0.png differ
diff --git a/assets/presentation_1756721524484_0.edn b/assets/presentation_1756721524484_0.edn
new file mode 100644
index 00000000..2d60bfb2
--- /dev/null
+++ b/assets/presentation_1756721524484_0.edn
@@ -0,0 +1,132 @@
+{:highlights [{:id #uuid "68b572ad-6444-494c-8929-43d2665321e6",
+ :page 3,
+ :position {:bounding {:x1 65.48125457763672,
+ :y1 255.13751220703125,
+ :x2 292.67061614990234,
+ :y2 281.9375,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 65.48125457763672,
+ :y1 255.13751220703125,
+ :x2 292.67061614990234,
+ :y2 281.9375,
+ :width 762,
+ :height 428.625}),
+ :page 3},
+ :content {:text "Open weight mode"},
+ :properties {:color "green"}}
+ {:id #uuid "68b572d4-f669-47ca-b942-f3a52b9e0683",
+ :page 3,
+ :position {:bounding {:x1 65.48125457763672,
+ :y1 288.4750061035156,
+ :x2 300.2505111694336,
+ :y2 315.2749938964844,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 65.48125457763672,
+ :y1 288.4750061035156,
+ :x2 300.2505111694336,
+ :y2 315.2749938964844,
+ :width 762,
+ :height 428.625}),
+ :page 3},
+ :content {:text "Open source model"},
+ :properties {:color "green"}}
+ {:id #uuid "68b57311-0b75-4a2a-86a9-b7236e7d2611",
+ :page 3,
+ :position {:bounding {:x1 65.48125457763672,
+ :y1 321.8125,
+ :x2 391.0964584350586,
+ :y2 348.6125183105469,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 65.48125457763672,
+ :y1 321.8125,
+ :x2 391.0964584350586,
+ :y2 348.6125183105469,
+ :width 762,
+ :height 428.625}),
+ :page 3},
+ :content {:text "Reproducible (libre) model"},
+ :properties {:color "green"}}
+ {:id #uuid "68b5737f-d5d0-41fd-bdc5-e574964d08ed",
+ :page 5,
+ :position {:bounding {:x1 173.8312591612339,
+ :y1 38.29376220703125,
+ :x2 742.5937866270542,
+ :y2 408.2749938964844,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 173.8312591612339,
+ :y1 38.29376220703125,
+ :x2 586.2620452940464,
+ :y2 83.49374389648438,
+ :width 762,
+ :height 428.625}
+ {:x1 175.25624695420265,
+ :y1 366.4562683105469,
+ :x2 591.831274420023,
+ :y2 393.2562561035156,
+ :width 762,
+ :height 428.625}
+ {:x1 734.643774420023,
+ :y1 392.2749938964844,
+ :x2 742.5937866270542,
+ :y2 408.2749938964844,
+ :width 762,
+ :height 428.625}),
+ :page 5},
+ :content {:text "Classes of \"openess\" https: //arxiv.org/abs/2403.13784 55"},
+ :properties {:color "green"}}
+ {:id #uuid "68b57a82-c115-4a56-a85b-4241b54bda29",
+ :page 36,
+ :position {:bounding {:x1 85.5562515258789,
+ :y1 128.78125762939453,
+ :x2 395.23746490478516,
+ :y2 173.98126983642578,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 85.5562515258789,
+ :y1 128.78125762939453,
+ :x2 395.23746490478516,
+ :y2 173.98126983642578,
+ :width 762,
+ :height 428.625}),
+ :page 36},
+ :content {:text "Reproducibility in AI research"},
+ :properties {:color "green"}}
+ {:id #uuid "68b57e64-b29f-42ea-9620-be4bbfa7edc2",
+ :page 53,
+ :position {:bounding {:x1 274.1312561035156,
+ :y1 48.4124755859375,
+ :x2 485.97784423828125,
+ :y2 93.61248779296875,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 274.1312561035156,
+ :y1 48.4124755859375,
+ :x2 485.97784423828125,
+ :y2 93.61248779296875,
+ :width 762,
+ :height 428.625}),
+ :page 53},
+ :content {:text "Finetuning"},
+ :properties {:color "green"}}
+ {:id #uuid "68b57fc1-5214-405c-b4f7-58296590c06d",
+ :page 73,
+ :position {:bounding {:x1 258.0625,
+ :y1 77.58123779296875,
+ :x2 502.1412048339844,
+ :y2 122.78125,
+ :width 762,
+ :height 428.625},
+ :rects ({:x1 258.0625,
+ :y1 77.58123779296875,
+ :x2 502.1412048339844,
+ :y2 122.78125,
+ :width 762,
+ :height 428.625}),
+ :page 73},
+ :content {:text "Benchmarks"},
+ :properties {:color "green"}}],
+ :extra {:page 4}}
diff --git a/assets/presentation_1756721524484_0.pdf b/assets/presentation_1756721524484_0.pdf
new file mode 100644
index 00000000..edd7c9cd
Binary files /dev/null and b/assets/presentation_1756721524484_0.pdf differ
diff --git a/assets/rinunciaAssegnoRubei_1760531403155_0.edn b/assets/rinunciaAssegnoRubei_1760531403155_0.edn
new file mode 100644
index 00000000..ab9a38bd
--- /dev/null
+++ b/assets/rinunciaAssegnoRubei_1760531403155_0.edn
@@ -0,0 +1 @@
+{:highlights [], :extra {:page 1}}
diff --git a/assets/rinunciaAssegnoRubei_1760531403155_0.pdf b/assets/rinunciaAssegnoRubei_1760531403155_0.pdf
new file mode 100644
index 00000000..1880bce9
Binary files /dev/null and b/assets/rinunciaAssegnoRubei_1760531403155_0.pdf differ
diff --git a/journals/2022_09_12.md b/journals/2022_09_12.md
index ec006fc5..9ffa7f93 100644
--- a/journals/2022_09_12.md
+++ b/journals/2022_09_12.md
@@ -9,7 +9,7 @@
id:: 631f2025-9cad-413a-8fcf-c1c78bd68635
- type:: [[meeting]]
external-links::
- people:: #people/alfonso
+ people:: #people/AlfonsoPierantonio
tags:: [[PAPERS/Software-ecosystem-book-chapter]]
date:: [[12-09-2022]]
duration-min:: 73
diff --git a/journals/2022_09_13.md b/journals/2022_09_13.md
index bd72e1b7..dfe7874c 100644
--- a/journals/2022_09_13.md
+++ b/journals/2022_09_13.md
@@ -1,6 +1,6 @@
- [[PAPERS/Software-ecosystem-book-chapter]]
- [[Planner]]
-- Parlato con #people/santucci relativamente la questione [[BUDGET]] di TYPHON
+- Parlato con #people/FortunatoSantucci relativamente la questione [[BUDGET]] di TYPHON
- Esame DSU [APPELLO 12/09/2022](onenote:[OneDrive](https://d.docs.live.net/a33324427a144a54/Documenti/Blocco%20appunti%20di%20Davide/Services/DIDATTICA/DSU.one#APPELLO%2012/09/2022§ion-id={340D9109-CB1D-4C0C-A3D8-1E179B9E8E7E}&page-id={6F8FB6F1-97AA-4C5C-9399-5EB6FF204791}&end)) ([visualizzazione Web](https://onedrive.live.com/view.aspx?resid=A33324427A144A54%21464&id=documents&wd=target%28Services%2FDIDATTICA%2FDSU.one%7C340D9109-CB1D-4C0C-A3D8-1E179B9E8E7E%2FAPPELLO%2012%5C%2F09%5C%2F2022%7C6F8FB6F1-97AA-4C5C-9399-5EB6FF204791%2F%29))
- [[Convegno AlmaLaurea sul profilo e condizione occupazionale dei Dottori di Ricerca]]
- [[CAD-IngInf-13-09-2022]]
diff --git a/journals/2022_10_04.md b/journals/2022_10_04.md
index 0c9d9306..41eeceb1 100644
--- a/journals/2022_10_04.md
+++ b/journals/2022_10_04.md
@@ -1,7 +1,7 @@
type:: [[meeting]]
external-links::
tags::
-people:: #comunicazioneUnivaq #people/alfonso
+people:: #comunicazioneUnivaq #people/AlfonsoPierantonio
tags::
date:: [[04-10-2022]] - 12:02
diff --git a/journals/2022_11_17.md b/journals/2022_11_17.md
index 160da12f..c20c8508 100644
--- a/journals/2022_11_17.md
+++ b/journals/2022_11_17.md
@@ -35,7 +35,6 @@
card-last-reviewed:: 2023-10-13T19:06:03.460Z
card-last-score:: 3
id:: 65c8d443-d834-42ba-9375-e3c7a63e9f8f
- collapsed:: true
- ### Descrizione
- L'ordalia è un'antica pratica giuridica, secondo la quale l'innocenza o la colpevolezza dell'accusato venivano determinate sottoponendolo ad una prova dolorosa o a un duello. La determinazione dell'innocenza derivava dal completamento della prova senza subire danni oppure dalla vittoria nel duello. [Wikipedia](https://it.wikipedia.org/wiki/Ordalia)
- ## Kintsugi #card
diff --git a/journals/2022_11_22.md b/journals/2022_11_22.md
index 37adfcac..5314608f 100644
--- a/journals/2022_11_22.md
+++ b/journals/2022_11_22.md
@@ -13,7 +13,7 @@
type:: [[meeting]]
external-links::
tags:: [[SERVICES/ORIENTAMENTO]]
- people:: [[people/henry]] [[people/forlizzi]]
+ people:: [[people/HenryMuccini]] [[people/forlizzi]]
date:: [[22-11-2022]] - 09:00
- Si e' parlato delle attività con il Bafile ed in particolare della lista dei corsi [[PCTO]] da offrire loro
-
diff --git a/journals/2023_01_17.md b/journals/2023_01_17.md
index ec85ed97..3985b735 100644
--- a/journals/2023_01_17.md
+++ b/journals/2023_01_17.md
@@ -1,7 +1,7 @@
type:: [[meeting]]
external-links::
tags:: [[SERVICES/ORIENTAMENTO]] [[school/Bafile]]
-people:: [[people/henry]] [[people/forlizzi]]
+people:: [[people/HenryMuccini]] [[people/forlizzi]]
date:: [[17-01-2023]] - 11:22
- 
\ No newline at end of file
diff --git a/journals/2023_01_24.md b/journals/2023_01_24.md
index eb986420..1d5027d4 100644
--- a/journals/2023_01_24.md
+++ b/journals/2023_01_24.md
@@ -1,7 +1,7 @@
type:: [[meeting]]
external-links::
tags:: [[SERVICES/ORIENTAMENTO]]
-people:: [[people/henry]] [[people/forlizzi]]
+people:: [[people/HenryMuccini]] [[people/forlizzi]]
date:: [[24-01-2023]] - 09:27
- Punto presentazione Bafile schedulata per il [[13-02-2023]]
diff --git a/journals/2023_05_19.md b/journals/2023_05_19.md
index cd47e94c..d96ff465 100644
--- a/journals/2023_05_19.md
+++ b/journals/2023_05_19.md
@@ -37,4 +37,4 @@
Add to that the simple fact that [[people]] working face-to-face in groups have to communicate sequentially -- in general, one person is speaking at a [[time]] -- so there is a dilution of effort. This is true even when activities are structured to have [[people]] [[WORK]] in parallel as much as possible.
- #[[Clip]] [[19-05-2023]] 10:35 [How To Be More Creative - Sunsama Blog](https://www.sunsama.com/blog/how-to-be-more-creative)
id:: 65c8d441-2be6-459a-9127-8d2501f37e0d
- One way to counter this problem -- at least in part -- is to have a group's participants brainstorm on their own, prior to working together. Then, afterward, the group comes together and shares their [[thoughts]], builds on them, comes up with new Ideas, and so on. But that 'coming together' doesn't have to be face-to-face in a [[CONFERENCE]] room. It can be accomplished [[by]] the group sharing each participant's Ideas, questions, and [[thoughts]] asynchronously, with a moderator guiding the process. This may amplify risk-taking in the absence of group social norms and groupthink #card
\ No newline at end of file
+ One way to counter this problem -- at least in part -- is to have a group's participants brainstorm on their own, prior to working together. Then, afterward, the group comes together and shares their [[thoughts]], builds on them, comes up with new Ideas, and so on. But that 'coming together' doesn't have to be face-to-face in a [[CONFERENCE]] room. It can be accomplished [[by]] the group sharing each participant's Ideas, questions, and [[thoughts]] asynchronously, with a moderator guiding the process. This may amplify risk-taking in the absence of group social norms and groupthink
\ No newline at end of file
diff --git a/journals/2023_09_18.md b/journals/2023_09_18.md
index 1a964767..461e2475 100644
--- a/journals/2023_09_18.md
+++ b/journals/2023_09_18.md
@@ -26,7 +26,7 @@ filters:: {"omnivore" false}
- Rimane appeso il corso di *programmazione per dispositivi mobili*
- verrà bandito a breve
- ((65083275-7567-4dc6-a474-73de58cbc822))
- - SESTUSCI - Segreteria studenti Area scientifica - [Ateneo - Segreteria studenti Area scientifica (univaq.it)](https://www.univaq.it/section.php?id=1724) #card
+ - SESTUSCI - Segreteria studenti Area scientifica - [Ateneo - Segreteria studenti Area scientifica (univaq.it)](https://www.univaq.it/section.php?id=1724)
id:: 65c8d43e-6683-4f87-ac05-5849fcbd106e
-
-
diff --git a/journals/2023_10_25.md b/journals/2023_10_25.md
index ae79c31a..fc18415b 100644
--- a/journals/2023_10_25.md
+++ b/journals/2023_10_25.md
@@ -2,7 +2,7 @@
- **Meeting with the MOSAICO consortium**
type:: [[meeting]]
external-links::
- tags:: [[PROJECTS/SE-H2020-March-Call]]
+ tags:: [[PROJECTS/MOSAICO]]
people::
date:: [[25-10-2023]] - 15:00
duration::
diff --git a/journals/2023_11_22.md b/journals/2023_11_22.md
index cdb2ce16..e8e75a5d 100644
--- a/journals/2023_11_22.md
+++ b/journals/2023_11_22.md
@@ -25,7 +25,7 @@
-
- type:: [[meeting]]
external-links::
- tags:: [[PROJECTS/SE-H2020-March-Call]]
+ tags:: [[PROJECTS/MOSAICO]]
people::
date:: [[22-11-2023]] - 15:00
duration::
diff --git a/journals/2024_01_11.md b/journals/2024_01_11.md
index 330d579a..465eb6e0 100644
--- a/journals/2024_01_11.md
+++ b/journals/2024_01_11.md
@@ -4,7 +4,7 @@
- type:: [[meeting]]
external-links::
tags:: [[PAPERS/SOSYM-EXPERT-VOICE-2024-ML-EVOLUTION]]
- people:: [[people/alfonso]] [[people/cicchetti]] [[people/ludovico]]
+ people:: [[people/AlfonsoPierantonio]] [[people/cicchetti]] [[people/ludovico]]
date:: [[11-01-2024]] - 16:10
duration::
- Evoluzioni si fa con questi strumenti che esistono per sviluppare applicazioni data-intensvie?
diff --git a/journals/2024_01_15.md b/journals/2024_01_15.md
index 9fe9b0a5..05c90962 100644
--- a/journals/2024_01_15.md
+++ b/journals/2024_01_15.md
@@ -55,10 +55,11 @@
background-color:: green
- DONE We talked about the [[PAPERS/SSTD-LLMS]] paper and recaped the tasks that were decided during the [[12-01-2024]] meeting.
background-color:: green
+ id:: 68584e7c-bb5f-40fe-876d-21fe8d87565f
- 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
- DONE Finally, we talked abou the paper with Rick Kazman (on Technical Dept). Phuong will push on this after the urgent things we currently have.
-id:: 65c8d43c-b2de-4ad6-9282-e2d67a0cb6b9
+ id:: 65c8d43c-b2de-4ad6-9282-e2d67a0cb6b9
:LOGBOOK:
CLOCK: [2025-05-21 Wed 09:04:50]--[2025-05-26 Mon 22:20:27] => 133:15:37
:END:
diff --git a/journals/2024_01_30.md b/journals/2024_01_30.md
index e09e4967..55e6d9c3 100644
--- a/journals/2024_01_30.md
+++ b/journals/2024_01_30.md
@@ -6,7 +6,7 @@
- type:: [[meeting]]
external-links::
tags::
- people:: [[people/alfonso]] [[people/Vittorio_Cortellessa]] [[people/henry]] [[people/autili]] [[people/DanieleDiPompeo]] [[people/traini]] [[people/TucciMichele]]
+ people:: [[people/AlfonsoPierantonio]] [[people/Vittorio_Cortellessa]] [[people/HenryMuccini]] [[people/autili]] [[people/DanieleDiPompeo]] [[people/traini]] [[people/TucciMichele]]
date:: [[30-01-2024]] - 11:45
duration:: 60
- Bologna capofila
diff --git a/journals/2024_02_07.md b/journals/2024_02_07.md
index 3c050225..cc3b309d 100644
--- a/journals/2024_02_07.md
+++ b/journals/2024_02_07.md
@@ -13,6 +13,12 @@
- ## Vocaboli
- **Lobotomizzato** #card
id:: 65c8d43b-51bb-4b3a-86d8-f03ea15d11a4
+ card-last-interval:: 4
+ card-repeats:: 1
+ card-ease-factor:: 2.36
+ card-next-schedule:: 2025-12-28T09:11:36.108Z
+ card-last-reviewed:: 2025-12-24T09:11:36.108Z
+ card-last-score:: 3
- Soggetto che è stato sottoposto ad intervento di lobotomia
- Lobotomia e' un intervento con il quale vengono recise delle fibre di un lobo cerebrale, tipicamente il lobo prefrontale.
- L'intervento viene effettuato a persone che hanno un atteggiamento antisociale. Comunque e' una pratica proibita.
\ No newline at end of file
diff --git a/journals/2024_03_20.md b/journals/2024_03_20.md
index 4ebedf9b..06ee7cde 100644
--- a/journals/2024_03_20.md
+++ b/journals/2024_03_20.md
@@ -71,13 +71,13 @@
- ## [[Interventi]]
- [[people/Vittorio_Cortellessa]] fa una domanda sugli **spazi**. Con gli GSSI a fianco e' difficile essere competitivo. E' necessario avere un'attenzione forte sugli spazi.
- Parla inoltre del **ruolo di tecnologo** (ingegnere esperto alla francese (questo l'ho pensato io))
- - [[people/alfonso]] interviene su due punti
+ - [[people/AlfonsoPierantonio]] interviene su due punti
- **Informatizzazione forzata che l'ateneo ha subito**. Il processo e' da rivedere per coinvolgere gli stakeholder. Le scelte sono state prese basandosi su politiche di costo
- Quando si fanno le gare di appalto il capitolato non puo' essere solo in capo dell'amministrazione
- **Supporto alle attività dei docenti** (sia come insegnati che come ricercatori)
- Ci sono dipartimenti che hanno piu' di 50 persone a supporto.
- Problema per poi quando si fanno le valutazioni che quindi diventa non fair.
- - [[people/henry]] fa un intervento sull'internazionalizzazione
+ - [[people/HenryMuccini]] fa un intervento sull'internazionalizzazione
- Abbiamo difficoltà perche' l'ateno e dipartimento non hanno realizzato un core sistemico per gestire studenti internazionali
- **Occorre ragionare in termine sistemico**
- [[people/antinisca]]: **riprendere il dialogo con le istituzioni in particolare con il Comune**
@@ -89,7 +89,7 @@
- Privilegiare l'organizzazione, i dati prima delle opinioni
- Rafforza il fatto che **la libera ricerca non deve finire sotto il tappeto**
- Non siamo qui per seguire i trend, possiamo assecondare ma siamo qui anche per anticipare
- - [[people/santucci]]
+ - [[people/FortunatoSantucci]]
- Problema di carattere generale, avvicendamento al Rettorato concluso il mandato di [[people/inverardi]] .
- Problemi organizzativi, operativi che nascono dalle iniziative che sono state create dal dipartimento
- Problemi oggettivi, perche' il dipartimento e' grande, ha diversi corsi di laurea, e' un dipartimento attivo etc.
diff --git a/journals/2024_04_15.md b/journals/2024_04_15.md
index e9a625d5..b730fccf 100644
--- a/journals/2024_04_15.md
+++ b/journals/2024_04_15.md
@@ -2,7 +2,7 @@
- #.tabular
- ### 🗒️Notes
- ![BOOX Notes - [[15-04-2024]]](../assets/../../onyx/TabUltraCPro/Notepad/15-04-2024.pdf)
- tags:: [[people/santucci]] [[people/Vittorio_Cortellessa]] [[SERVICES/PHDICT]] [[meeting]] [[PROJECTS/PRIN-EMELIOT]]
+ tags:: [[people/FortunatoSantucci]] [[people/Vittorio_Cortellessa]] [[SERVICES/PHDICT]] [[meeting]] [[PROJECTS/PRIN-EMELIOT]]
- {:height 375, :width 728}
- [MIUN Main Agreement Cotutelle_v5_version 5 april (1).docx](../assets/MIUN_Main_Agreement_Cotutelle_v5_version_5_april_(1)_1713186077418_0.docx)
-
diff --git a/journals/2024_04_19.md b/journals/2024_04_19.md
index 7c661120..2cd43260 100644
--- a/journals/2024_04_19.md
+++ b/journals/2024_04_19.md
@@ -46,7 +46,7 @@
- type:: [[meeting]]
external-links::
tags:: [[PAPERS/SOSYM-EXPERT-VOICE-2024-ML-EVOLUTION]]
- people:: [[people/cicchetti]] [[people/alfonso]] [[people/ludovico]]
+ people:: [[people/cicchetti]] [[people/AlfonsoPierantonio]] [[people/ludovico]]
date:: [[19-04-2024]] - 15:02
duration::
- [SOSYM EXPERT VOICE - NOTES - Google Docs](https://docs.google.com/document/d/1nNPbd-S-hsPDR4UUhqHBfYR-gG3rNdYTEJyGq7M1Z-Q/edit)
diff --git a/journals/2025_06_19.md b/journals/2025_06_19.md
index 1213e3ef..bd3a5cbf 100644
--- a/journals/2025_06_19.md
+++ b/journals/2025_06_19.md
@@ -15,7 +15,7 @@ progress:: {{renderer :todomaster}}
id:: d4b795f4-21e9-408f-a6c2-3aadc10c3468
-
- DONE SEAA reviews
-id:: 68584e74-0640-44c4-8805-dcadc064aedb
+ id:: 68584e74-0640-44c4-8805-dcadc064aedb
- 🚧Error! Error: HTTP error! status: 422
- 🚧Error! Error: HTTP error! status: 422
- 🚧Error! Error: HTTP error! status: 422
diff --git a/journals/2025_06_20.md b/journals/2025_06_20.md
index ebbfc0cd..00afd675 100644
--- a/journals/2025_06_20.md
+++ b/journals/2025_06_20.md
@@ -17,7 +17,7 @@ boox-notes:: 
- [[people/PhuongNguyen]] working on the [[PAPERS/MOSAICO-Technical-Report]]. Many things to do with the writing
@@ -25,6 +25,7 @@ id:: 6858534b-a36d-412e-9cee-356a6787e0b4
:LOGBOOK:
CLOCK: [2025-06-18 Wed 17:01:15]
:END:
- - TODO Capire cosa fare [[PRIN 2020 - scadenza rendicontazione finale]]
+ - DONE Capire cosa fare [[PRIN 2020 - scadenza rendicontazione finale]]
+id:: 6858534b-8fe7-4b13-8739-b45d7ac5ea75
- ## Notes
-
\ No newline at end of file
diff --git a/journals/2025_06_21.md b/journals/2025_06_21.md
index fab1b722..842e8f0e 100644
--- a/journals/2025_06_21.md
+++ b/journals/2025_06_21.md
@@ -10,7 +10,7 @@ boox-notes:: , quindi l'assemblea verrà indetta in concomitanza al dipartimento.
- PINKAMP
- #### ((686e6893-02f1-49bd-ad98-d3178508df05))
- - Nominato [[people/alfonso]]
+ - Nominato [[people/AlfonsoPierantonio]]
- ((686e6b91-cba3-43c0-9432-03f6543856e3))
- ((686e6ba2-2f74-4396-95e1-fa3eb009c6ae))
\ No newline at end of file
diff --git a/journals/2025_07_13.md b/journals/2025_07_13.md
index f6fa02bb..03e82a77 100644
--- a/journals/2025_07_13.md
+++ b/journals/2025_07_13.md
@@ -4,12 +4,12 @@ boox-notes:: )
- 
- - Dominio ICT e Aerospazio che non da un punto di vista guiridico non è un distretto.
+ - **Dominio ICT e Aerospazio** (era presidiato da [[people/FabioGraziosi]] ) che non da un punto di vista guiridico non è un distretto.
- L'Università dell'Aquila fa pate del DAAB, credo che sia uno degli enti costituenti.
- 
- 
@@ -63,5 +64,14 @@ boox-notes:: 
- 
- 
- - Fortunato ha data disponibilità ad entrae al direttivo del distretto
- - Roberto Carattoli
\ No newline at end of file
+ - [[people/FortunatoSantucci]] ha data disponibilità ad entrare al consiglio direttivo del distretto. La componente di ricerca è rappresentata da
+ - Uni L'Aquila, Chieti Pescara, GSSi
+ - Roberto Carattoli è stato nominato ma non ho capito chi è e cosa fa
+ - 
+ - RadioLabs ha meno di 15 dipendenti, quindi e' una Piccola Imprese e quindi la quota e' di 1000Euro
+ - 
+ - Varie ed eventuali
+ - Il [[01-09-2025]] usciranno i bandi EuropeRail.
+ -
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_07_17.md b/journals/2025_07_17.md
new file mode 100644
index 00000000..8a05c9da
--- /dev/null
+++ b/journals/2025_07_17.md
@@ -0,0 +1,6 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
\ No newline at end of file
diff --git a/journals/2025_07_18.md b/journals/2025_07_18.md
new file mode 100644
index 00000000..d6185dc9
--- /dev/null
+++ b/journals/2025_07_18.md
@@ -0,0 +1,49 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ - [[Rendicontazione EMELIOT]]
+ - PHD
+ - Rispondere mail
+ - Corso Dajana
+ - Review COMLAN
+ - Mentoring
+ - Corsa
+ - Paper Riccardo
+ - ### Notes
+ - **Assemblea Cad Ing. Informatica I4F**
+ - *Consuntivo delle attività svolte nel triennio 2022-2025*
+ collapsed:: true
+ - 
+ - 
+ - {:height 418, :width 857}
+ - 
+ - 
+ - 
+ - 
+ - 
+ - {:height 521, :width 980}
+ - 
+ - 
+ - 
+ - 
+ - 
+ - {:height 523, :width 967}
+ - 
+ - 
+ - 
+ -
+ - *Presentazione delle candidature*
+ collapsed:: true
+ - [[people/SerafinoCicerone]] si candita
+ - 
+ - 
+ - **Weekly Meeting [[SoftwareMiningGroup]]**
+ - Claudio and Juri are preparing the experiments for the [[PAPERS/DSL-FOR-IOT-TESTING]] paper
+ - The rejected IST [[PAPERS/2025-Survey-MOSAICO]] paper will contribute to D3.1 of MOSAICO
+ - The [[PAPERS/2025-Survey-MOSAICO]] background will be included in the [[PAPERS/MOSAICO-Technical-Report]] #PAPERS #todoist-task
+ - The work on [[PAPERS/AUSE-Metagente]] is progressing
+ - TODO Have a look at the paper with Rick [[PAPERS/TOSEM2025-TESORO]]
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_07_23.md b/journals/2025_07_23.md
new file mode 100644
index 00000000..4fd29a8e
--- /dev/null
+++ b/journals/2025_07_23.md
@@ -0,0 +1,14 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ - DONE Finalizzare verbale di ieri
+ :LOGBOOK:
+ CLOCK: [2025-07-23 Wed 15:30:43]--[2025-07-23 Wed 15:30:44] => 00:00:01
+ :END:
+ - Mandare estratto per corso Gullo (Direttore, uprodid)
+ - Mandre estratto per Federico Di Menna
+ -
+ - ### Notes
+ -
\ No newline at end of file
diff --git a/journals/2025_07_30.md b/journals/2025_07_30.md
new file mode 100644
index 00000000..a7ad139e
--- /dev/null
+++ b/journals/2025_07_30.md
@@ -0,0 +1,23 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting con Phuong, Claudio, Juri [[SoftwareMiningGroup]]**
+ tags:: [[meeting]]
+ - Discusso del paper:
+ - [[PAPERS/2025-EMSE-MOSAICO-Experience-Report]]
+ - Ancora molte cose da fare. [[people/PhuongNguyen]] sta facendo una prima passata
+ - [[PAPERS/AUSE-Metagente]]
+ - [[people/PhuongNguyen]] ha un meeting con lo studente per capire come estendere gli esperimenti. Nella versione FSE del paper, METAGENGE e' stato confrontato con GitSum, Llama, GPT4o. Si pensa di intraprendere queste direzioni per estendere il lavoro
+ - Considerare un ulteriore dataset condiviso da Juri su Android
+ - Considerare un altro modell (Mistral)
+ - Ho suggerito anche di investigare diverse configurazioni. Provare ad usare diversi modelli per i diversi task e vedere se si riesce ad avere qualche insights interessante
+ - [[Deliverable D2.1]]
+ - Abbiamo raffinato il modello, ho suggerito di raffinarlo ulteriormente guardando anche i repository che Antonio ci ha suggerito durante [[Missione ROMA Mosaico]]
+id:: 688a33c3-76cc-4772-8f84-9248e6d96027
+ - {{embed ((6863b98d-74e6-435a-8631-c03155c89300))}}
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_08_01.md b/journals/2025_08_01.md
new file mode 100644
index 00000000..ed50f141
--- /dev/null
+++ b/journals/2025_08_01.md
@@ -0,0 +1,10 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting about the [[PAPERS/2026-SANER-PERFORMANCE-BUG-DETECTION]]**
+ tags:: [[meeting]]
+ -
\ No newline at end of file
diff --git a/journals/2025_09_04.md b/journals/2025_09_04.md
new file mode 100644
index 00000000..4395fe6d
--- /dev/null
+++ b/journals/2025_09_04.md
@@ -0,0 +1,16 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting MATTERS [[04-09-2025]]**
+ tags:: [[PROJECTS/SERICS-MATTERS]], [[MEETINGS]]
+ - Relazione scientifica - Deliverable finale su cui stiamo lavorando
+ - Scheda con informazioni amministrative
+ - TODO Chiudere timesheet [[04-09-2025]] #PROJECTS/SERICS-MATTERS #MEETINGS
+ - Rendicontazione dal 10 Novembre al 9 Agosto
+ -
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_09_05.md b/journals/2025_09_05.md
new file mode 100644
index 00000000..16a9f0c4
--- /dev/null
+++ b/journals/2025_09_05.md
@@ -0,0 +1,18 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### **Notes**
+ - **Meeting [[05-09-2025]] [[PAPERS/2026-SANER-Mutation_Analysis_Bias_Symptoms_Salerno]]**
+ - tags:: [[MEETINGS]], [[TODOIST-LOGSEQED]]
+ - Correttezza del dato rispetto al dominio
+ - Immaginiamo di fare uno studio che coinvolga teenagers e che nel nostro dataset abbiamo per ognuno l'età. Potrei applicare operatori che modificano l'età portando fuori dal dominio di interesse le persone che hanno piu' di 18 anni a valle dell'applicazione degli operator.
+ - Correttezza semantica del dataset e definizione quindi degli operatori rispetto al dato
+ - Studiare gli effetti degli operatori sui sintomi
+ - Ci sono operatori che incidono o meno sui sintomi
+ - Aggiungere una RQ per fare doublckech sulla relazione modifica -> sintomo -> bias
+ - Attenzione alle mutazioni semantiche
+ - Attenzione all'ordine degli operatori, come questi vengono selezionati, se sono dipendenti/independenti, etc.
+ - Da vedere?
+ - TODO [Beyond Internal Data: Constructing Complete Datasets for Fairness Testing](https://arxiv.org/pdf/2507.18561)
+ -
\ No newline at end of file
diff --git a/journals/2025_09_06.md b/journals/2025_09_06.md
new file mode 100644
index 00000000..c0785f65
--- /dev/null
+++ b/journals/2025_09_06.md
@@ -0,0 +1,8 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ -
\ No newline at end of file
diff --git a/journals/2025_09_10.md b/journals/2025_09_10.md
new file mode 100644
index 00000000..d881ac0c
--- /dev/null
+++ b/journals/2025_09_10.md
@@ -0,0 +1,17 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Consiglio dipartimento del [[10-09-2025]]**
+ - type:: [[meeting]]
+ external-links::
+ tags:: [[SERVICES/ConsiglioDisim]] [[Convocazioni]]
+ date:: [[10-09-2025]] - 14:44
+ duration-min::
+ file-brogliaccio:: 
+ file-odg:: 
+ - Non e' chiaro ancora il rapport Spese personale/FFO. In base alle prime stime siamo dal 73 al 76%
+ -
\ No newline at end of file
diff --git a/journals/2025_09_12.md b/journals/2025_09_12.md
new file mode 100644
index 00000000..fd9d07f7
--- /dev/null
+++ b/journals/2025_09_12.md
@@ -0,0 +1,9 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ -
+-
\ No newline at end of file
diff --git a/journals/2025_09_15.md b/journals/2025_09_15.md
new file mode 100644
index 00000000..e0435079
--- /dev/null
+++ b/journals/2025_09_15.md
@@ -0,0 +1,11 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Corso
+ - nome
+ - durata in n ore
+ -
\ No newline at end of file
diff --git a/journals/2025_09_16.md b/journals/2025_09_16.md
new file mode 100644
index 00000000..7d08dc25
--- /dev/null
+++ b/journals/2025_09_16.md
@@ -0,0 +1,25 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **[[SWEN]] talk on Semantic transformations vs Iterative repair: handling bugs with LLMs** (Max Hort)
+ - Work with Simula
+ - Detection and fixing vulnerabilities with LLMs
+ - 
+ - Semantic preservig transformations essentially based on variable renaming
+ - {:height 516, :width 808}
+ - 
+ - 
+ - 
+ - 
+ - How do you ensure that the functionalities remain the same? #question
+ - 
+ - 
+ - How do you check if a bug has been fixed during iterations #question
+ - {:height 508, :width 891}
+ -
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_09_25.md b/journals/2025_09_25.md
new file mode 100644
index 00000000..a4a8c819
--- /dev/null
+++ b/journals/2025_09_25.md
@@ -0,0 +1,25 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ - ### Notes
+ - **Meeting [[SoftwareMiningGroup]]**
+ collapsed:: true
+ - type:: [[meeting]]
+ date:: [[25-09-2025]] - 09:57
+ - [[PAPERS/EMELIOT-EXPERIMENT]] : some differences in the way Juri and Claudio are doing the experiments and this can have an impact on timing
+ - [[Deliverable D2.1]] #todoist-task #PROJECTS/MOSAICO
+ - [[Deliverable D3.1]] #todoist-task #PROJECTS/MOSAICO
+ - [[people/Minase]] is working on security issues on Terraform specifications (the master thesis is on this)
+ - [[PAPERS/2026-SANER-RAG-ATTACK]] Phuong and Max about RAG and Attacks (this is more on the defense side)
+ - Vulnerability detection of PyPi packages [[people/umar]]
+ - Suggested this paper [[2508.01451] Think Broad, Act Narrow: CWE Identification with Multi-Agent Large Language Models](https://arxiv.org/abs/2508.01451)
+ - Umar says that there are no baselines for Python, there are for Java
+ -
+ - Meetging with Francisco Martinez Lasaca
+ - 
+ - 
+ - 
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_09_30.md b/journals/2025_09_30.md
new file mode 100644
index 00000000..fb76d7a5
--- /dev/null
+++ b/journals/2025_09_30.md
@@ -0,0 +1,9 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ -
+- TODO offerta
\ No newline at end of file
diff --git a/journals/2025_10_08.md b/journals/2025_10_08.md
new file mode 100644
index 00000000..d22a5c70
--- /dev/null
+++ b/journals/2025_10_08.md
@@ -0,0 +1,26 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Meeting con [[people/FortunatoSantucci]] Francesco e Elena
+ - Overview dei miei due corsi
+ - SE4AS
+ - Intro - MAPE-K
+ - Video CARLA - [SE4AS_Document.pdf](file:///C:/Users/david/git/Progetti_SE4AS/24_25/Autonomous_Project_CARLA/SE4AS_Document.pdf)
+ - EcoTrafficFlowManager - [SE4AS_EcoTrafficFlowManager/SE4AS Project.pdf at main · RobyBobby24/SE4AS_EcoTrafficFlowManager](https://github.com/RobyBobby24/SE4AS_EcoTrafficFlowManager/blob/main/SE4AS%20Project.pdf)
+ - Platooning
+ - SE4IOT
+ - [Documentation_SE4IOT_Smart_Agriculture_Field_Monitoring_System_EN.pdf](file:///C:/Users/david/git/Progetti_SE4IOT/24-25/Smart-Agriculture-Field-Monitoring-System/docs/Documentation_SE4IOT_Smart_Agriculture_Field_Monitoring_System_EN.pdf)
+ - [Project Report.pdf](file:///C:/Users/david/git/Progetti_SE4IOT/24-25/Smart-Cities-AirQualityMonitoring/Project%20Report.pdf)
+ - [WQMS_ProjectDocumentation.pdf](file:///C:/Users/david/git/Progetti_SE4IOT/24-25/SE4IoT_water_distribution_network/WQMS_ProjectDocumentation.pdf)
+ - [F1 tent](https://www.f1tenth.racing/)
+ - Bisogna entrare nei challenge esistenti
+ - Circuiti indoor o outdoor
+ - Autoware - [autowarefoundation/autoware: Autoware - the world's leading open-source software project for autonomous driving](https://github.com/autowarefoundation/autoware)
+ - Progetto P-CAR che eredita casi d'uso
+ - [Jetson AGX Orin for Next-Gen Robotics | NVIDIA](https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-orin/)
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_10_09.md b/journals/2025_10_09.md
new file mode 100644
index 00000000..1a8c33d2
--- /dev/null
+++ b/journals/2025_10_09.md
@@ -0,0 +1,52 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting [[SoftwareMiningGroup]]**
+ -
+ - type:: [[meeting]], [[SoftwareMiningGroup]]
+ external-links::
+ tags::
+ people::
+ date:: [[09-10-2025]] - 09:58
+ duration::
+ - **Presentation from [[people/Minase]]**
+ - Graphical example on IaC is missing in slide 3
+ - Concrete example of misconfiguration
+ - Otherwise people attending will get lost
+ - Same comment for slide 5
+ - It is necessary to show visually the problems and existing solutions that have been proposed so far and give an intuition supporting the methodology in slide 6
+ - Tools like Terrascan or tfsec should be show (again just to give an intuition on how they work on a very illustrative example)
+ - Too much time on slide 7
+ - Illustrative example giving an intuition about slide 8
+ - What's a unique violations in file?
+ - As a general comment you are asking too much from the attendees. This a technical presentation which is ok in a context like the one we have today. But the presentation for the thesis presentation should be less details but more on giving intuitions about the problems and the proposed solutions
+ - Slide 15
+ - Why **Dual Attention Mechanism**?
+ - For instance you talk about *window*, but of what?
+ - **Update [[PAPERS/2025-IEEESOFTWARE-AGENTIC-SI]]**
+ - Claudio is restructuring the paper
+ - **Update [[PAPERS/AUSE-Metagente]]**
+ - Phuong is in touch with students
+ - Juri is also working on this
+ - **Update from [[people/umar]]**
+ - Poster submission on the 20th of October
+ -
+ -
+ - **Call with Francisco**
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ -
+-
\ No newline at end of file
diff --git a/journals/2025_10_14.md b/journals/2025_10_14.md
new file mode 100644
index 00000000..fdc34027
--- /dev/null
+++ b/journals/2025_10_14.md
@@ -0,0 +1,14 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting [[PROJECTS/MOSAICO]] WP leaders**
+ - type:: [[meeting]]
+ tags:: [[PROJECTS/MOSAICO]]
+ date:: [[14-10-2025]] - 14:45
+ - How much logic is on the collaboration vs on the repository
+ - We need to enable the query by semantic search and by Ids
+ - Then we need to filter by means of the different characteristics
\ No newline at end of file
diff --git a/journals/2025_10_15.md b/journals/2025_10_15.md
new file mode 100644
index 00000000..de034e14
--- /dev/null
+++ b/journals/2025_10_15.md
@@ -0,0 +1,66 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ - ### Notes
+ - **Consiglio di Dipartimento [[DISIM]]**
+ type:: [[meeting]]
+ external-links::
+ tags:: [[SERVICES/ConsiglioDisim]] [[Convocazioni]]
+ date:: [[15-10-2025]] - 14:22
+ duration-min::
+ file-brogliaccio:: 
+ file-odg:: 
+ - ((68ef9735-4af7-4e7e-909d-98d1f1196f19))
+ - Variazioni del consiglio di dipartimento
+ collapsed:: true
+ - Rappresentati Personale TA
+ - ...
+ - Rappresentante assegnisti
+ - MARINO PAVONE
+ - [[people/Pomante]] e' Associato dal primo di Ottobre
+ - Daniele Frigioni e' vice-direttore
+ - Immatricolazioni
+ collapsed:: true
+ - 
+ - **RICERCA**
+ - ((68ef936d-6021-40e8-993e-c78676f55faf)) [[people/claudio]]
+ collapsed:: true
+ - 
+ - 
+ - ((68ef937a-3d89-4739-b4a2-e73c924a79fc)) [[people/riccardo]]
+ collapsed:: true
+ - 
+ - 
+ - ((68ef942a-5b23-422b-8d88-4c49778a16d7))
+ - **PERSONALE**
+ - ((68ef94d6-f616-4fa4-95ad-754fb3874601))
+ - Relazione di [[people/juri]]
+ - 
+ - **STRUTTURE ED ORGANI**
+ - ((68ef9bb4-c1e9-4a97-85a3-9a80679645ab))
+ collapsed:: true
+ - Per il consiglio di Novembre saranno pronte le altre commissioni. Oggi nominiamo quella per l'internazionalizzazione
+ - Nesi (coordinatrice)
+ - Stanchieri
+ - Giuli
+ - ...
+ - Gullo - Data Science
+ - Commissione Didattica
+ - Colangeli
+ - Pola
+ - Cicerone
+ - Autili
+ - D'Innocenzo
+ - Di Marco
+ - Della Penna
+ - Antonelli
+ - Marzia Marcocci
+ - Tragno, Pallottini (rappresentati studenti)
+ - ((68ef9c5e-f8c7-45e8-8b2d-8eb38117c8d5))
+ collapsed:: true
+ - 
+ - Al posto di Daniele, Concettina Buccella
+ - ((68ef9cd5-4623-42a3-b5d6-75212323e48b))
+-
\ No newline at end of file
diff --git a/journals/2025_10_16.md b/journals/2025_10_16.md
new file mode 100644
index 00000000..9b4c62e5
--- /dev/null
+++ b/journals/2025_10_16.md
@@ -0,0 +1,55 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ - ### Notes
+ - **Meeting [[SERVICES/RADIOLABS]] with [[company/ESA]]**
+ type:: [[meeting]]
+ external-links::
+ tags:: [[SERVICES/RADIOLABS]] [[PROJECTS/PCAR]]
+ people::
+ date:: [[16-10-2025]] - 10:10
+ duration::
+ - 
+ - 
+ - 
+ - 
+ - 
+ - **WP14 updates from Vincenzo**
+ - 
+ - 
+ - 
+ - FRODDO covers use case on smart intersection
+ - C Roads big project that consider Airports as use case
+ - ANAS Smart Road project
+ - ADS -> Automated Driving System
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - These are the services that will be implemented.
+ - 
+ -
+ - **Meeting [[PROJECTS/MOSAICO]]** WP6/WP7
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - [EBDVF | Data and AI Event](https://european-big-data-value-forum.eu/)
+ - Someone will go there
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ -
\ No newline at end of file
diff --git a/journals/2025_11_12.md b/journals/2025_11_12.md
new file mode 100644
index 00000000..914ce9bd
--- /dev/null
+++ b/journals/2025_11_12.md
@@ -0,0 +1,64 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Consiglio di dipartimento**
+ - type:: [[meeting]]
+ external-links::
+ tags:: [[SERVICES/ConsiglioDisim]] [[Convocazioni]]
+ date:: [[12-11-2025]] - 14:43
+ duration-min::
+ file-brogliaccio::  
+ file-odg:: 
+ - **Comunicazioni**
+ - Situazione immatricolazioni
+ - {:height 559, :width 1035}
+ - Chiusure Ateneo 2026
+ collapsed:: true
+ - 2 Gennaio 2026
+ - 1 Giugno 2026
+ - Dal 10 al 14 Agosto 2026
+ - Dal 28 al 31 Dicembre 2026
+ - **Figure pre-ruolo**
+ id:: 69190e46-c217-4afb-866d-454ef610384a
+ - ***Contratto di ricerca***
+ - Durata biennale e rinnovabili una sola volta per ulteriori due anni
+ - Candidati con dottori di ricerca
+ - Il contrattista svolge esclusivamente attività di ricerca. Incompatibile con qualsiasi altra attività di lavoro (didattica, attività integrative)
+ - Costo minimo 80000 fino ad un massimo 108000
+ - Due annualità di nu ricercatore a tempo definito
+ - Due annualità di un ricercatore a tempo pieno
+ - La procedura e' molto simile a quella del RTD/a (come tempistiche e' molto simile)
+ - I Contratti di ricerca si possono bandire solo su somme disponibili sui nostri progetti
+ - Oltre alla scheda, la segreteria deve fornire dati economici per quanto riguarda lo stato del fondo su cui si va a bandire il bando
+ - Dati chiesti dai revisori dei conti
+ - Operazione che richiede tempo.
+ - La laurea magistrale non deve essere ottenuta da non più di 7 anni dal bando
+ - La modulistica e' disponibile nella sezione FILE dell'allargato
+ - ***Incarichi post-doc***
+ - [[@Incarichi post-doc]]
+ - Durata annuale rinnovabile massimo 3 anni totale
+ - Costo minimo 40000 Euro
+ - Possono participare dottori di ricerca
+ - Possono svolgere attvità di ricerca e collaborazione in attività didattica e di terza missione
+ - Incompatibile con qualsiasi altro contratto di lavoro
+ - La modulistica per richiedere l'incarico non e' stata ancora prodotta
+ - ***Incarico di ricerca***
+ - [[@Incarichi di ricerca]]
+ - [PDF](https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=205&item=file) {{zotero-imported-file 7ZTPLJQC, "blob.php.pdf"}}
+ - Molto simile all'assegno
+ - Durata annuale prorogato al massimo 3 anni
+ - Possono partecipare anche i laureati
+ - Base minima 25000 Euro
+ - Incompatibile con la frequenza di corsi di laurea o dottorato
+ - Scritta dal decreto legge, quindi dal MUR
+ - A livello di gestione del bando e' capo del dipartimento
+ - ALTRA FORMA
+ - Contratto di Collaborazione (detta da Henry)
+ - **Commissioni**
+ - Commissione spazi
+ - 
+ -
\ No newline at end of file
diff --git a/journals/2025_11_25.md b/journals/2025_11_25.md
new file mode 100644
index 00000000..2ae21b0d
--- /dev/null
+++ b/journals/2025_11_25.md
@@ -0,0 +1,15 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Notes
+ - **[[MEETINGS]] with [[Phuong T. Nguyen]]**
+ - Abbiamo parlato del paper di Umar rifiutato a SCICO-D-25-00281 è stato deciso di rimandare il paper migliorando le motivazioni ad Applied Intelligence
+ - Per quanto riguarda il paper JSS (sempre con Umar) probabilmente si sta aspettando la terza review
+ - [Elsevier - track your submission](https://track.authorhub.elsevier.com/?uuid=7da9b2a4-83ff-4c65-9625-2ccb384d28da)
+ - Il paper EMSE con l'analisi fatta per il deliverable D2.1 e' stato mandato ai reviewer dopo un mese circa
+ - Il [[19-12-2025]] dovrebbero arrivare le notifiche dei paper [[SANER]]
+ - Abbiamo parlato di possibili tesi. Ci sono le condizioni per definire due tesi sul topic di benchmarking di MOSAICO
+ - Una piu' concettuale sulla definizione del benchmarking
+ - Una piu' tecnico implementativa che possa andare anche nella direzione di recommender system che dato l'agente da misurare suggerisce il benchmark da usare.
+ -
\ No newline at end of file
diff --git a/journals/2025_11_27.md b/journals/2025_11_27.md
new file mode 100644
index 00000000..7da1aff8
--- /dev/null
+++ b/journals/2025_11_27.md
@@ -0,0 +1,37 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting with [[SoftwareMiningGroup]]**
+ type:: [[meeting]]
+ - Emeliot paper - Completing the evaluation
+ - On the 4 december next call at 9:00
+ - Target is IST journal
+ - The second research question needs to be finalizaed
+ - [[Phuong T. Nguyen]]
+ - Working on the metagente paper
+ - Almost done with all the comments. We can submit by tomorrow
+ - TESORO revision
+ - The student is working on it not in an intensive manner. There are experiments to be done.
+ - Idea of Phuong is checking in LLM have been trained with malicious repositories
+ - Following the flow of memorization
+ - [https://arxiv.org/pdf/2412.13459](https://arxiv.org/pdf/2412.13459)
+ - Involve the student from Vietnam that was involved on the CWE paper
+ - The message of the paper is giving evidence that LLMs are trained with possibly malicious repositories.
+ - Target is FSE 2026
+ - It will be in Canada I guess.
+ - We should also aim for [[ICSME]]
+ - The deadline is on February.
+ - Possibly idea is machine UNlearning!
+ - Remove for instance the code if we notice that it is malicious
+ - Update on [[Benchmarks]] #PROJECTS/MOSAICO #P1
+ - LanguFuese e' rilasciato con licenza MIT
+ - Alcune componenti hanno licenze enterprise. Componenti che in realtà non stiamo utilizzando
+ - Collaborazione con Antonio
+ - MCP *resources* vs *tools* (es calcolatrice per fare la somma) vs *prompt* (?)
+ - Attualmente abbiamo fornito resources
+ - La ricerca semantica sarà il tool
+ -
\ No newline at end of file
diff --git a/journals/2025_11_30.md b/journals/2025_11_30.md
new file mode 100644
index 00000000..c0785f65
--- /dev/null
+++ b/journals/2025_11_30.md
@@ -0,0 +1,8 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ -
\ No newline at end of file
diff --git a/journals/2025_12_01.md b/journals/2025_12_01.md
new file mode 100644
index 00000000..c0785f65
--- /dev/null
+++ b/journals/2025_12_01.md
@@ -0,0 +1,8 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ -
\ No newline at end of file
diff --git a/journals/2025_12_03.md b/journals/2025_12_03.md
new file mode 100644
index 00000000..2f994ac1
--- /dev/null
+++ b/journals/2025_12_03.md
@@ -0,0 +1,33 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - type:: [[meeting]]
+ external-links::
+ tags:: [[SERVICES/ConsiglioDisim]] [[Convocazioni]]
+ date:: [[03-12-2025]] - 15:05
+ duration-min::
+ file-brogliaccio:: 
+ file-odg:: 
+ - **Comunicazioni**
+ - [[people/FortunatoSantucci]] Nominato vice-presidente del **DAB (Distretto Aerospaziale Abruzzese)**
+ - 451.566,00 Euro FFO (25% in piu' rispetto all'anno scorso e al 5% in meno rispetto al 2024)
+ - 82.000,00 Euro ai dottorati
+ - Didattica
+ - Fondi RIA
+ - Altri attività di ricerca
+ - Rinnovo assegni e per bandi nuovi incarichi di ricerca
+ - Al consiglio di gennaio si parlera' della ripartizione dei fondi ria e per gli assegni
+ - Il [[15/12/2025]] votazioni della giunta
+ - si vota dalle 9:00 alle 13:00
+ - Non possiamo avere persone che sono state due volte in Giunta
+ - [[SERVICES/PINKAMP]]
+ - Referenti lato DISIM sono Claudio Arbib (INF), Carmen Scalone (MAT), Dajana Cassioli (ING-INF)
+ - TODO Riempire questionario docenti su UGOV
+ - A febbraio ci saranno molti PRIN 2022 e PRIN 2022 PNRR in scadenza
+ - Dobbiamo essere collaborativi nella rendicontazione
+ - Il prossimo Dipartimento sara il 14 Gennaio alle 14:30. I punti devono essere ricevuti entro il 7 GEnnaio
+ -
\ No newline at end of file
diff --git a/journals/2025_12_04.md b/journals/2025_12_04.md
new file mode 100644
index 00000000..640e76f1
--- /dev/null
+++ b/journals/2025_12_04.md
@@ -0,0 +1,84 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting [[SoftwareMiningGroup]]**
+ type:: [[meeting]]
+ - [[PAPERS/2025-IEEESOFTWARE-AGENTIC-SI]]
+ - [[PAPERS/2024-TESORO]]
+ - We asked an extension. A meeting with the student has been done by Phuong.
+ - Deadline is [[26-12-2025]]
+ - Work on Memorization on Malicious repositories
+ - Work on **machine unlearning**
+ - An overleaf project will be shared by Phuong to submit to FSE (NIER track)
+ - Students are running some experiments
+ - [MDEGroup/SANER26-JF-DeepMig](https://github.com/MDEGroup/SANER26-JF-DeepMig)
+ - Another Journal First paper managed by Amleto on the paper with Fontana
+ - **Meeting [[SERVICES/RADIOLABS]]**
+ type:: [[meeting]]
+ file-odg:: 
+ documents::  [Punto 11 odg - 231.zip](../assets/Punto_11_odg_-_231_1764843308200_0.zip)
+ - 
+ - ((693160c3-b9e7-4673-8216-abeed18301cc))
+ - Lorenzo Greco
+ - Cegeka partecia in Radiolabs
+ - [Cegeka nomina Lorenzo Greco nuovo Amministratore Delegato per l'Italia](https://www.cegeka.com/it/news/cegeka-nomina-lorenzo-greco-nuovo-amministratore-delegato-per-italia)
+ - ((693160b0-6a69-410b-a49a-a9cf06dd4073))
+ - Nel CDA di Febbraio 2025 veniva conferito un incarico al consulente Alessandro Neri per lo svolgimento di attività tecnico scientifiche per il consorso. Compenso di 130000 Euro che era stata parametrato per la rendicontazione su tutti i progetti che coprivano questo costo per il 2025 e quello che stiamo proponendo è rinnovare con lo stesso importo (1300 ore), l'effort in realtà e' superiore a questo, e il budget c'e'.
+ - Approvato all'unanimità
+ - ((6931623f-fe44-4f4b-b56a-9ba822711b5a))
+ collapsed:: true
+ - {:height 434, :width 576}
+ 
+ - Nelle consulenze tecniche abbiamo anche il costo della consulenza Neri
+ - Welfare e MBO sono possibili premi per i dipendenti
+ - In totale ci sono 14 persone arruolate in RadioLabs
+ - In aggiunta ci sono anche altri Ricercatori (non stabilizzati)
+ - In totale abbiamo circa 30 unità
+ - 
+ - 
+ - Il target era 1.4M
+ - 
+ - {:height 362, :width 582}
+ - 
+ - {:height 345, :width 581}
+ - 
+ - 2026
+ - 
+ - 
+ - 
+ - {:height 227, :width 576}
+ - 
+ - 
+ - ((69316743-c79e-4200-934d-85d152b86d60))
+ collapsed:: true
+ - 
+ - In linea con la missione di RadioLabs, concentrato sull tecnologie innovative per i trasporti e veicoli autonomi
+ - TIM - digitalizzazione cantieri stradali
+ - Thales + Leonardo + Airbus - Gruppo Europeo per lo spazio
+ - Il piano è ancorato a tre utilizzatori principali
+ - RFI
+ - Airbus
+ - Hitachi
+ - Abbiamo aperto ad Airbus
+ - Ottima palestra per fare progetti innovaitivi oppure trampolino di lancio per aziende che sono nel consorzio ad agganciare questo piano
+ - Approvato all'unanimità
+ - ((69316f7e-d361-4907-af0e-82567bdde4d6))
+ - Si chiede al consiglio di dare mandato al presidente e al direttore di decidere eventuali MBO per il personale con un tetto massimo di 90.000 Euro. Questa è un'azione che rientra nella politica di far rimanere i dipendenti in RadioLabs
+ - Non perdere forza lavoro.
+ - Lavoro qualificato e avere grande soddisfazione
+ - ((69317290-2997-4b52-b2ad-552b40db9037))
+ - Rivisti i regolamenti della quantificazione di alcuni livelli per esempio regolamento missione (del 2019) che tengono tetti che orami non sono più praticabili
+ - Adeguamento dei livelli ai livelli di mercato
+ - Per gli acquisti è stata snellita la procedura
+ - ((693173af-8ba6-4ee8-8968-64ff8bad3023))
+ - Per ogni consorziato abbiamo almeno 2 membri
+ - Nominare membri comitato scientifico
+ - Organizzare Worskhop su AI / Agenti / Edge interagendo con SImone Gianfranceschi di Intecs
+ - ((6931769f-99fd-4d86-bffc-52319c897578))
+ - Presa d'atto
+ -
+-
\ No newline at end of file
diff --git a/journals/2025_12_05.md b/journals/2025_12_05.md
new file mode 100644
index 00000000..7fdf3588
--- /dev/null
+++ b/journals/2025_12_05.md
@@ -0,0 +1,16 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting WP Leaders [[PROJECTS/MOSAICO]]**
+ type:: [[meeting]]
+ - Cose da dire:
+ - Il lavoro sul banchmarking -> Necessità di collaborare con Jordi per quanto riguarda il Quality Model
+ - We have in mind the definition of the benchmarking specification as done for ModelXGlue
+ - We can share a document describing the work we are doing
+ - Capire come collaborare relativamente per il task 3.2 per il quale L'Aquila e' Leader
+ - A dedicated meeting is needed here
+ -
\ No newline at end of file
diff --git a/journals/2025_12_10.md b/journals/2025_12_10.md
new file mode 100644
index 00000000..48b9cac3
--- /dev/null
+++ b/journals/2025_12_10.md
@@ -0,0 +1,18 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Meeting with [[PROJECTS/MOSAICO]] WP tech members
+ tags:: [[meeting]] [[Benchmarking framework]]
+ - 
+ - Where are benchmarking information available from these filtering mechanism?
+ - Consider that benchmarking information can change
+ - I would even filter with respect to the quality model
+ - Deployment information for the agent should be included in the metadata
+ - Agents can be running on a given url or you might need a url to download the docker-compose file for instance to install it
+ - See the AgentConsumption in the taxonomy
+ - [git - How can I change the commit author for a single commit? - Stack Overflow](https://stackoverflow.com/questions/3042437/how-can-i-change-the-commit-author-for-a-single-commit)
+ - 
\ No newline at end of file
diff --git a/journals/2025_12_11.md b/journals/2025_12_11.md
new file mode 100644
index 00000000..b58a9f94
--- /dev/null
+++ b/journals/2025_12_11.md
@@ -0,0 +1,21 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Evento Conclusivo SERICS Bologna**link:: [La visione dei giovani ricercatori sulle prospettive della cybersecurity](https://eventi.unibo.it/spoke8serics)
+ - **Evento di chiusura dello**** Spoke 8 'Gestione del rischio e governance' del progetto *****Security and Rights in CyberSpace* (SERICS) in attuazione del Partenariato Esteso “Cybersecurity, nuove tecnologie e tutela dei diritti”, nell’ambito del Piano Nazionale di Ripresa e Resilienza:**
+ - **Project**: *Risk management for future cyber-physical ecosystems (EcoCyber)
+ - ***PI**: Michele Colajanni, Università di Bologna
+ - **Project: ***imPROving The rEsilience to Cyberattacks of distributed ICT InfrastrucTures (PROTECT-IT)
+ - ***PI**: Antonio Lioy, Politecnico di Torino
+ -
+ - **Interesting talks**
+ - Rustam Talibzade, UniTo, *On Using LLMs for Vulnerability Classification* - presented at lamps 2025
+ - CTIBench
+ - Gabriele Penzotti, UniPr, *Machine Learning Based Software Vulnerability Assessment*
+ - Virginia Remondino, UniBo, *The role of EU values in the context of the Cyber Resilience Act*
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_12_16.md b/journals/2025_12_16.md
new file mode 100644
index 00000000..50b5bbc4
--- /dev/null
+++ b/journals/2025_12_16.md
@@ -0,0 +1,54 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - #### **Meeting with students Tesfay and Abu dicussing on using MAS to generate README files**
+ type:: [[meeting]]
+ tags:: [[SoftwareMiningGroup]]
+ collapsed:: true
+ - 
+ - 
+ - First of all, what's hight quality README files?
+ - What README files should include? You know that there are deployment instructions, how to use the projects, how to contribute? So the issue that I see is the definition of quality that should be considered to generate high quality README files
+ - 
+ - 
+ - 
+ - 
+ - An issue that I can see is that it is highly probable that README files have been seen by LLMs
+ - [LARCH: Large Language Model-based Automatic Readme Creation with Heuristics](https://arxiv.org/pdf/2308.03099)
+ - 
+ - 
+ - 
+ - What's the validity of the standard README file structure?
+ - 
+ - 
+ - Repository-specific README structure
+ - It means that you need to train by considering different kinds of repositories. What can you say about the representativeness of the analyzed repositories?
+ - Actually you don't know how many kinds of repositories you have, right? What can you say about the completeness of the process?
+ - 
+ - 
+ - 
+ - 
+ - 
+ - Ablation study is also OK but there is the bias issue that I mentioned before that's a critial threats to validity of the overall process.
+ - 
+ - How similar/different are the generated README files with respect to the original README file?
+ - 
+ - **Meeting WP5 [[PROJECTS/MOSAICO]]**
+ type:: [[meeting]]
+ tags:: [[PROJECTS/MOSAICO]]
+ - [Demo from UY](https://imtatlantiquefr.sharepoint.com/:v:/r/sites/MOSAICO/Shared%20Documents/Work%20Packages/WP1/D1.2/20251210%20-%20Mosaico%20Coding%20Extension%20Demo%202.mp4?csf=1&web=1&e=cnoYvM&xsdata=MDV8MDJ8fGUxZmI1NTIzYWZjZjQwN2I2MmEyMDhkZTNjOTRkYTQwfDhmOWI4OGE3M2YzZTRiZTNhYWU0MjAwNmQ0YzQyMzA2fDB8MHw2MzkwMTQ4MDcxNDc2NjgxMzB8VW5rbm93bnxWR1ZoYlhOVFpXTjFjbWwwZVZObGNuWnBZMlY4ZXlKRFFTSTZJbFJsWVcxelgwRlVVRk5sY25acFkyVmZVMUJQVEU5R0lpd2lWaUk2SWpBdU1DNHdNREF3SWl3aVVDSTZJbGRwYmpNeUlpd2lRVTRpT2lKUGRHaGxjaUlzSWxkVUlqb3hNWDA9fDF8TDJOb1lYUnpMekU1T20xbFpYUnBibWRmVG5wVmVWbHRTbTFaYlZsMFRrZFJNMWxUTURCUFZHZDRURmRLYlU1cVdYUk9lbWMxVGpKUk5VNUhUVEpPTWtWNVFIUm9jbVZoWkM1Mk1pOXRaWE56WVdkbGN5OHhOelkxT0Rnek9URXpOVEV6fDM2NTI3ZTZmNjI1MTRjNjVhOWQwMDhkZTNjOTRkYTNmfGRlNjQzOGFiYjY3NzQ0OTg5ODdkZTI2Yzk4MTYyMjg4&sdata=Z3NJS0N0MzdkTFdxWjNhbWhZbmQxSWtoNTNQMlg1Ymp1WXVsWGlmMHVEcz0%3D&ovuser=9df08a7c-31d7-4024-9ba6-5ed5efac1a01%2Cdavide.diruscio%40univaq.it)
+ - {:height 503, :width 848}
+ - Each agent gives back a card to understand how to use it?
+ - https://a2a-protocol.org/v0.3.0/specification/#55-agentcard-object-structure
+ - We use the A2A card to **use** the agent, but we don't need it to **find** or **select** it (it's enough with the MOSAICO repository metadata)
+ - We discussed [MOSAICO_system_architecture_sequence_diagram_v3.drawio](https://imtatlantiquefr.sharepoint.com/:u:/r/sites/MOSAICO/Shared%20Documents/Work%20Packages/WP5/T5.2/System%20Architecture/MOSAICO_system_architecture_sequence_diagram_v3.drawio?csf=1&web=1&e=hvJq9x)
+ - Tutti gli agenti sono un server A2A
+ - Reference and Collaboration sono sia client che server
+ - Supervision and Solution are only server
+ -
+ -
+ -
\ No newline at end of file
diff --git a/journals/2025_12_17.md b/journals/2025_12_17.md
new file mode 100644
index 00000000..013d7869
--- /dev/null
+++ b/journals/2025_12_17.md
@@ -0,0 +1,50 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - **Meeting commissione [[Services/Commissione-Ricerca-DISIM]]**
+ type:: [[meeting]]
+ - 
+ - 
+ - Definire calendario periodico (mercoledì pomeriggio?)
+ - Indicare commissione di Ateneo per l'emissione del bando
+ - Bando deve rimanere a livello di ateneo, consentendo la spesa a 2 anni [[Ideas]]
+ - Anlizzare il report del Nucleo di Valutazione
+ - Verificare la possibilità dei dottorandi ad inserire i dati su IRIS
+ - 
+ - A maggio/giugno arriverà il rapporto ANVUR
+ - Anche l'ANVUR e' in fase di riforma
+ - Forme di coinvolgimento per gli inattivi
+ - Indirizzare le sottomissioni su journal piu' di prestigio
+ - Per il dottorato almeno un lavoro entro i tre anni (conferimento obbligatorio)
+ - Canali su linkedin?
+ - Presidio sui bandi competitivi
+ - Censimento di asset da poter esporre all'esterno
+ - **Incontro con [[people/FortunatoSantucci]] per l'organizzazione dell'evento [[SERVICES/RADIOLABS]] a Gennaio**
+ - Angelucci
+ - Valutar per evento [[SERVICES/RADIOLABS]]
+ - Introduzione AI con Simone Gianfranceschi [[company/Intecs]]
+ - Rabiolabs + ExEmerge + Intecs
+ - Assetto operativo per guidare il lavoro delle persone
+ - University for Peace
+ - Sergio Bellucci
+ - #### **Seduta [[SERVICES/ExEmerge]] [[17-12-2025]]**
+ type:: [[meeting]]
+ file-odg:: 
+ - **Comunicazione**
+ - Fondazione Restart
+ - Intende proeguire le sue attività anche dopo PNRR
+ - Partecipazione alla fondazione 5000 Euro annua + una tantum 15000 Euro
+ - Destino delle fonazioni nate per gestire fondi PNRR
+ - L'anima è il CNIT che è già un consorzio
+ - Restart integra componenti aziendali
+ - Il MIMIT vorrà supportare tali fndazioni
+ - Buttazzo del Sant'anna
+ - [Cyber 4.0](https://www.cyber40.it/) - Normerto parteciperà domani all'assemblea
+ - Cisco accademy
+ - HD Motion (altro progetto a cui partecipiamo)
+ - ((69429a33-8e6f-447d-ac26-253af028914b))
+ - Budget di circa 1600 da spendere tra il 2026-2027-2028
\ No newline at end of file
diff --git a/journals/2025_12_19.md b/journals/2025_12_19.md
new file mode 100644
index 00000000..ebd20e30
--- /dev/null
+++ b/journals/2025_12_19.md
@@ -0,0 +1,11 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Meeting [[PROJECTS/EU-AIM-PRO]]
+ type:: [[meeting]]
+ - 
+ - 
\ No newline at end of file
diff --git a/journals/2025_12_24.md b/journals/2025_12_24.md
new file mode 100644
index 00000000..c7202831
--- /dev/null
+++ b/journals/2025_12_24.md
@@ -0,0 +1,46 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+id:: 1fc8ffcf-8fa6-4a7e-8982-89adc0977d09
+
+ - ### Tasks
+ -
+ - ### Notes
+- [[KaraKeep-Highlights-Summary]]
+- {{renderer :mermaid_00f4ca0a-1de7-44e6-b203-d72ee1a887ea, 3}}
+ - ```mermaid
+ mindmap
+ root((AI Agent Systems & Deployment))
+ Multi-Agent Systems & Handoffs
+ Explicit Prompted Instructions
+ Conditional Edges & Command Objects
+ Fragile Implementations
+ Tension: Flexibility vs Scripted Control
+ Agent Framework Ecosystems
+ LangChain
+ High-Level Rapid Assembly
+ Provider Agnostic Design
+ Middleware for Customization
+ LangGraph
+ Low-Level Fine-Grained Control
+ Production-Grade Long Running Agents
+ Trade-Off: Ease vs Control
+ Open-Source Protocols & Standards
+ MCP Donation to Linux Foundation
+ Challenges: Complexity, Security, Performance
+ Institutional Push for AI Standards
+ Adoption Uncertainty & Ecosystem Impact
+ Tiny AI Models & Edge Deployment
+ Aggressive Quantization Techniques
+ llama.cpp Framework
+ Vision-Language Fusion Models
+ Qwen 3 Series: Low-Power High Performance
+ Enabling AI on Raspberry Pi & Similar
+ Emerging Research Directions
+ Adaptive Agent Handoff & Orchestration
+ Balancing Protocol Standardization & Research Agility
+ Model Compression & Cross-Modal Integration
+ Middleware Design Patterns for Agent Loops
+ Secure, Performant Multi-Agent Protocols
+ ```
+-
\ No newline at end of file
diff --git a/journals/2025_12_27.md b/journals/2025_12_27.md
new file mode 100644
index 00000000..1e600889
--- /dev/null
+++ b/journals/2025_12_27.md
@@ -0,0 +1,8 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: 
+
+ - ### Tasks
+ - id:: bc947c51-c222-46ad-8dc2-0cd30f0be2af
+ - ### Notes
+ -
\ No newline at end of file
diff --git a/pages/PROJECTS___SE-H2020-March-Call.md b/logseq/.recycle/pages_PROJECTS___SE-H2020-March-Call.md
similarity index 97%
rename from pages/PROJECTS___SE-H2020-March-Call.md
rename to logseq/.recycle/pages_PROJECTS___SE-H2020-March-Call.md
index 3f396827..b03a5544 100644
--- a/pages/PROJECTS___SE-H2020-March-Call.md
+++ b/logseq/.recycle/pages_PROJECTS___SE-H2020-March-Call.md
@@ -1,5 +1,5 @@
-alias:: PROJECTS/MOSAICO
-status:: [[SUBMITTED]]
+filters:: {"call per posizioni mosaico" true}
+status:: [[ACCEPTED]]
deadline-submission:: [[19-03-2024]]
date-start:: [[01-01-2025]]
date-end:: [[31-12-2027]]
@@ -10,13 +10,14 @@ 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
- collapsed:: true
- {:height 491, :width 862}
- ## Project preparation
collapsed:: true
@@ -237,5 +238,6 @@ progress:: {{renderer :todomaster}}
- 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)
\ No newline at end of file
diff --git a/pages/SERVICES___PHDICT___TASKS.md b/logseq/.recycle/pages_SERVICES___PHDICT___TASKS.md
similarity index 100%
rename from pages/SERVICES___PHDICT___TASKS.md
rename to logseq/.recycle/pages_SERVICES___PHDICT___TASKS.md
diff --git a/logseq/.recycle/pages_Wallabag.md b/logseq/.recycle/pages_Wallabag.md
new file mode 100644
index 00000000..337a7abf
--- /dev/null
+++ b/logseq/.recycle/pages_Wallabag.md
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_09_12/2022-11-16T20_21_57.370Z.android.md b/logseq/bak/journals/2022_09_12/2022-11-16T20_21_57.370Z.android.md
deleted file mode 100644
index 5fac244e..00000000
--- a/logseq/bak/journals/2022_09_12/2022-11-16T20_21_57.370Z.android.md
+++ /dev/null
@@ -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)
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_09_12/2022-12-09T22_44_10.163Z.android.md b/logseq/bak/journals/2022_09_12/2022-12-09T22_44_10.163Z.android.md
deleted file mode 100644
index 36d62702..00000000
--- a/logseq/bak/journals/2022_09_12/2022-12-09T22_44_10.163Z.android.md
+++ /dev/null
@@ -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)
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_09_12/2022-12-11T09_56_20.122Z.Desktop.md b/logseq/bak/journals/2022_09_12/2022-12-11T09_56_20.122Z.Desktop.md
deleted file mode 100644
index 36d62702..00000000
--- a/logseq/bak/journals/2022_09_12/2022-12-11T09_56_20.122Z.Desktop.md
+++ /dev/null
@@ -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)
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_09_12/2023-02-04T07_51_31.931Z.android.md b/logseq/bak/journals/2022_09_12/2023-02-04T07_51_31.931Z.android.md
deleted file mode 100644
index 57a45c80..00000000
--- a/logseq/bak/journals/2022_09_12/2023-02-04T07_51_31.931Z.android.md
+++ /dev/null
@@ -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)
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_09_12/2023-04-24T21_54_47.314Z.android.md b/logseq/bak/journals/2022_09_12/2023-04-24T21_54_47.314Z.android.md
deleted file mode 100644
index f5f33e80..00000000
--- a/logseq/bak/journals/2022_09_12/2023-04-24T21_54_47.314Z.android.md
+++ /dev/null
@@ -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)
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_10_04/2022-10-04T16_09_12.481Z.android.md b/logseq/bak/journals/2022_10_04/2022-10-04T16_09_12.481Z.android.md
deleted file mode 100644
index 20e91b2e..00000000
--- a/logseq/bak/journals/2022_10_04/2022-10-04T16_09_12.481Z.android.md
+++ /dev/null
@@ -1,8 +0,0 @@
-type:: [[meeting]]
-external-links::
-tags::
-people::
-areas::
-date:: [[04-10-2022]] - 12:02
-
--
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_10_04/2022-10-05T12_37_48.860Z.android.md b/logseq/bak/journals/2022_10_04/2022-10-05T12_37_48.860Z.android.md
deleted file mode 100644
index 846f04f1..00000000
--- a/logseq/bak/journals/2022_10_04/2022-10-05T12_37_48.860Z.android.md
+++ /dev/null
@@ -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)
-
--
\ No newline at end of file
diff --git a/logseq/bak/journals/2022_10_04/2022-10-05T12_41_05.918Z.android.md b/logseq/bak/journals/2022_10_04/2022-10-05T12_41_05.918Z.android.md
deleted file mode 100644
index 846f04f1..00000000
--- a/logseq/bak/journals/2022_10_04/2022-10-05T12_41_05.918Z.android.md
+++ /dev/null
@@ -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)
-
--
\ No newline at end of file
diff --git a/logseq/bak/journals/2024_01_15/2024-02-23T12_57_30.843Z.Desktop.md b/logseq/bak/journals/2024_01_15/2024-02-23T12_57_30.843Z.Desktop.md
deleted file mode 100644
index 3f5c3579..00000000
--- a/logseq/bak/journals/2024_01_15/2024-02-23T12_57_30.843Z.Desktop.md
+++ /dev/null
@@ -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]
\ No newline at end of file
diff --git a/logseq/bak/journals/2024_01_15/2024-03-14T07_01_22.721Z.Desktop.md b/logseq/bak/journals/2024_01_15/2024-03-14T07_01_22.721Z.Desktop.md
deleted file mode 100644
index 78f77b43..00000000
--- a/logseq/bak/journals/2024_01_15/2024-03-14T07_01_22.721Z.Desktop.md
+++ /dev/null
@@ -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]
\ No newline at end of file
diff --git a/logseq/bak/journals/2024_01_15/2024-03-14T07_43_24.319Z.Desktop.md b/logseq/bak/journals/2024_01_15/2024-03-14T07_43_24.319Z.Desktop.md
deleted file mode 100644
index 78f77b43..00000000
--- a/logseq/bak/journals/2024_01_15/2024-03-14T07_43_24.319Z.Desktop.md
+++ /dev/null
@@ -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]
\ No newline at end of file
diff --git a/logseq/bak/journals/2024_01_15/2025-05-22T07_04_54.490Z.Desktop.md b/logseq/bak/journals/2024_01_15/2025-05-22T07_04_54.490Z.Desktop.md
deleted file mode 100644
index 89a5b9b0..00000000
--- a/logseq/bak/journals/2024_01_15/2025-05-22T07_04_54.490Z.Desktop.md
+++ /dev/null
@@ -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]
\ No newline at end of file
diff --git a/logseq/bak/journals/2024_01_15/2025-05-26T20_45_20.201Z.Desktop.md b/logseq/bak/journals/2024_01_15/2025-05-26T20_45_20.201Z.Desktop.md
deleted file mode 100644
index 19f19eb9..00000000
--- a/logseq/bak/journals/2024_01_15/2025-05-26T20_45_20.201Z.Desktop.md
+++ /dev/null
@@ -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]
\ No newline at end of file
diff --git a/logseq/bak/logseq/config/2025-06-04T21_41_34.909Z.Desktop.edn b/logseq/bak/logseq/config/2025-06-04T21_41_34.909Z.Desktop.edn
deleted file mode 100644
index dbf27fb2..00000000
--- a/logseq/bak/logseq/config/2025-06-04T21_41_34.909Z.Desktop.edn
+++ /dev/null
@@ -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"}
- }
diff --git a/logseq/bak/logseq/config/2025-06-04T21_41_42.404Z.Desktop.edn b/logseq/bak/logseq/config/2025-06-04T21_41_42.404Z.Desktop.edn
deleted file mode 100644
index 4a393f10..00000000
--- a/logseq/bak/logseq/config/2025-06-04T21_41_42.404Z.Desktop.edn
+++ /dev/null
@@ -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"}
- }
diff --git a/logseq/bak/logseq/config/2025-06-05T08_02_31.258Z.Desktop.edn b/logseq/bak/logseq/config/2025-06-05T08_02_31.258Z.Desktop.edn
deleted file mode 100644
index cb42f0ce..00000000
--- a/logseq/bak/logseq/config/2025-06-05T08_02_31.258Z.Desktop.edn
+++ /dev/null
@@ -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"}
- }
diff --git a/logseq/bak/logseq/custom/2024-08-06T16_28_45.258Z.Desktop.css b/logseq/bak/logseq/custom/2024-08-06T16_28_45.258Z.Desktop.css
deleted file mode 100644
index a3dd5f5d..00000000
--- a/logseq/bak/logseq/custom/2024-08-06T16_28_45.258Z.Desktop.css
+++ /dev/null
@@ -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);
-}
diff --git a/logseq/bak/logseq/custom/2024-08-06T16_30_38.609Z.Desktop.css b/logseq/bak/logseq/custom/2024-08-06T16_30_38.609Z.Desktop.css
deleted file mode 100644
index 142dfe25..00000000
--- a/logseq/bak/logseq/custom/2024-08-06T16_30_38.609Z.Desktop.css
+++ /dev/null
@@ -1,3 +0,0 @@
-div.block-properties > div:has(div:empty) {
- display: none;
-}
diff --git a/logseq/bak/logseq/custom/2025-05-10T20_29_01.437Z.Desktop.css b/logseq/bak/logseq/custom/2025-05-10T20_29_01.437Z.Desktop.css
deleted file mode 100644
index 7812a5ed..00000000
--- a/logseq/bak/logseq/custom/2025-05-10T20_29_01.437Z.Desktop.css
+++ /dev/null
@@ -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;
-}
diff --git a/logseq/bak/pages/CV Empower/2024-10-26T09_39_49.355Z.Desktop.md b/logseq/bak/pages/CV Empower/2024-10-26T09_39_49.355Z.Desktop.md
deleted file mode 100644
index d6d56cab..00000000
--- a/logseq/bak/pages/CV Empower/2024-10-26T09_39_49.355Z.Desktop.md
+++ /dev/null
@@ -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.
\ No newline at end of file
diff --git a/logseq/bak/pages/CV Empower/2024-10-26T23_27_21.960Z.Desktop.md b/logseq/bak/pages/CV Empower/2024-10-26T23_27_21.960Z.Desktop.md
deleted file mode 100644
index 09e9b2d7..00000000
--- a/logseq/bak/pages/CV Empower/2024-10-26T23_27_21.960Z.Desktop.md
+++ /dev/null
@@ -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.
\ No newline at end of file
diff --git a/logseq/bak/pages/CV Empower/2024-10-29T14_21_12.789Z.Desktop.md b/logseq/bak/pages/CV Empower/2024-10-29T14_21_12.789Z.Desktop.md
deleted file mode 100644
index 09e9b2d7..00000000
--- a/logseq/bak/pages/CV Empower/2024-10-29T14_21_12.789Z.Desktop.md
+++ /dev/null
@@ -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.
\ No newline at end of file
diff --git a/logseq/bak/pages/Call per posizioni MOSAICO/2025-06-03T13_51_39.382Z.android.md b/logseq/bak/pages/Call per posizioni MOSAICO/2025-06-03T13_51_39.382Z.android.md
deleted file mode 100644
index 606379d2..00000000
--- a/logseq/bak/pages/Call per posizioni MOSAICO/2025-06-03T13_51_39.382Z.android.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/DESKTOP/2024-03-14T07_01_22.864Z.Desktop.md b/logseq/bak/pages/DESKTOP/2024-03-14T07_01_22.864Z.Desktop.md
deleted file mode 100644
index c8009e94..00000000
--- a/logseq/bak/pages/DESKTOP/2024-03-14T07_01_22.864Z.Desktop.md
+++ /dev/null
@@ -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))}}
- -
--
--
\ No newline at end of file
diff --git a/logseq/bak/pages/DESKTOP/2024-03-14T07_43_24.439Z.Desktop.md b/logseq/bak/pages/DESKTOP/2024-03-14T07_43_24.439Z.Desktop.md
deleted file mode 100644
index c8009e94..00000000
--- a/logseq/bak/pages/DESKTOP/2024-03-14T07_43_24.439Z.Desktop.md
+++ /dev/null
@@ -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))}}
- -
--
--
\ No newline at end of file
diff --git a/logseq/bak/pages/DESKTOP/2024-05-11T11_07_18.743Z.Desktop.md b/logseq/bak/pages/DESKTOP/2024-05-11T11_07_18.743Z.Desktop.md
deleted file mode 100644
index 831610ef..00000000
--- a/logseq/bak/pages/DESKTOP/2024-05-11T11_07_18.743Z.Desktop.md
+++ /dev/null
@@ -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]
\ No newline at end of file
diff --git a/logseq/bak/pages/DONE/2025-06-04T17_50_30.223Z.android.md b/logseq/bak/pages/DONE/2025-06-04T17_50_30.223Z.android.md
deleted file mode 100644
index db0f9727..00000000
--- a/logseq/bak/pages/DONE/2025-06-04T17_50_30.223Z.android.md
+++ /dev/null
@@ -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))
\ No newline at end of file
diff --git a/logseq/bak/pages/DONE/2025-06-05T08_02_31.324Z.Desktop.md b/logseq/bak/pages/DONE/2025-06-05T08_02_31.324Z.Desktop.md
deleted file mode 100644
index ec9564f6..00000000
--- a/logseq/bak/pages/DONE/2025-06-05T08_02_31.324Z.Desktop.md
+++ /dev/null
@@ -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))
\ No newline at end of file
diff --git a/logseq/bak/pages/MENTORING___TESISTI/2023-02-08T07_23_33.055Z.android.md b/logseq/bak/pages/MENTORING___TESISTI/2023-02-08T07_23_33.055Z.android.md
deleted file mode 100644
index 986377b1..00000000
--- a/logseq/bak/pages/MENTORING___TESISTI/2023-02-08T07_23_33.055Z.android.md
+++ /dev/null
@@ -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]]
--
\ No newline at end of file
diff --git a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-08-24T19_20_14.429Z.Desktop.md b/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-08-24T19_20_14.429Z.Desktop.md
deleted file mode 100644
index 5d19941b..00000000
--- a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-08-24T19_20_14.429Z.Desktop.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-11-25T12_51_42.488Z.Desktop.md b/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-11-25T12_51_42.488Z.Desktop.md
deleted file mode 100644
index 5d19941b..00000000
--- a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-11-25T12_51_42.488Z.Desktop.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-11-30T10_37_16.061Z.Desktop.md b/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-11-30T10_37_16.061Z.Desktop.md
deleted file mode 100644
index 5d19941b..00000000
--- a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-11-30T10_37_16.061Z.Desktop.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-12-03T20_46_07.755Z.android.md b/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-12-03T20_46_07.755Z.android.md
deleted file mode 100644
index 5d19941b..00000000
--- a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-12-03T20_46_07.755Z.android.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-12-09T22_44_12.544Z.android.md b/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-12-09T22_44_12.544Z.android.md
deleted file mode 100644
index 39f12b55..00000000
--- a/logseq/bak/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso/2022-12-09T22_44_12.544Z.android.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/Omnivore/2023-09-17T19_20_26.787Z.Desktop.md b/logseq/bak/pages/Omnivore/2023-09-17T19_20_26.787Z.Desktop.md
deleted file mode 100644
index be314d44..00000000
--- a/logseq/bak/pages/Omnivore/2023-09-17T19_20_26.787Z.Desktop.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat/2023-08-23T08_46_53.496Z.Desktop.md b/logseq/bak/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat/2023-08-23T08_46_53.496Z.Desktop.md
deleted file mode 100644
index ef212d70..00000000
--- a/logseq/bak/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat/2023-08-23T08_46_53.496Z.Desktop.md
+++ /dev/null
@@ -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]]
\ No newline at end of file
diff --git a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-04-26T15_35_15.956Z.Desktop.md b/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-04-26T15_35_15.956Z.Desktop.md
deleted file mode 100644
index dfa79e18..00000000
--- a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-04-26T15_35_15.956Z.Desktop.md
+++ /dev/null
@@ -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]]
--
\ No newline at end of file
diff --git a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-04-26T15_36_08.686Z.android.md b/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-04-26T15_36_08.686Z.android.md
deleted file mode 100644
index dfa79e18..00000000
--- a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-04-26T15_36_08.686Z.android.md
+++ /dev/null
@@ -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]]
--
\ No newline at end of file
diff --git a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-05-12T13_07_23.434Z.Desktop.md b/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-05-12T13_07_23.434Z.Desktop.md
deleted file mode 100644
index f1e69d40..00000000
--- a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-05-12T13_07_23.434Z.Desktop.md
+++ /dev/null
@@ -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]]
\ No newline at end of file
diff --git a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-05-12T13_29_57.610Z.Desktop.md b/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-05-12T13_29_57.610Z.Desktop.md
deleted file mode 100644
index f1e69d40..00000000
--- a/logseq/bak/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING/2023-05-12T13_29_57.610Z.Desktop.md
+++ /dev/null
@@ -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]]
\ No newline at end of file
diff --git a/logseq/bak/pages/PAPERS___Software-ecosystem-book-chapter/2023-08-31T17_26_22.473Z.Desktop.md b/logseq/bak/pages/PAPERS___Software-ecosystem-book-chapter/2023-08-31T17_26_22.473Z.Desktop.md
deleted file mode 100644
index 1b977491..00000000
--- a/logseq/bak/pages/PAPERS___Software-ecosystem-book-chapter/2023-08-31T17_26_22.473Z.Desktop.md
+++ /dev/null
@@ -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???
--
\ No newline at end of file
diff --git a/logseq/bak/pages/PAPERS___Software-ecosystem-book-chapter/2025-06-03T16_41_53.265Z.android.md b/logseq/bak/pages/PAPERS___Software-ecosystem-book-chapter/2025-06-03T16_41_53.265Z.android.md
deleted file mode 100644
index a335707e..00000000
--- a/logseq/bak/pages/PAPERS___Software-ecosystem-book-chapter/2025-06-03T16_41_53.265Z.android.md
+++ /dev/null
@@ -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???
--
\ No newline at end of file
diff --git a/logseq/bak/pages/PROJECTS___PRIN-EMELIOT/2024-07-26T10_00_07.362Z.Desktop.md b/logseq/bak/pages/PROJECTS___PRIN-EMELIOT/2024-07-26T10_00_07.362Z.Desktop.md
deleted file mode 100644
index a09888d1..00000000
--- a/logseq/bak/pages/PROJECTS___PRIN-EMELIOT/2024-07-26T10_00_07.362Z.Desktop.md
+++ /dev/null
@@ -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]
--
--
\ No newline at end of file
diff --git a/logseq/bak/pages/PROJECTS___PRIN-EMELIOT/2024-07-29T07_28_41.401Z.Desktop.md b/logseq/bak/pages/PROJECTS___PRIN-EMELIOT/2024-07-29T07_28_41.401Z.Desktop.md
deleted file mode 100644
index a09888d1..00000000
--- a/logseq/bak/pages/PROJECTS___PRIN-EMELIOT/2024-07-29T07_28_41.401Z.Desktop.md
+++ /dev/null
@@ -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]
--
--
\ No newline at end of file
diff --git a/logseq/bak/pages/Papers/2024-05-30T07_38_08.773Z.Desktop.md b/logseq/bak/pages/Papers/2024-05-30T07_38_08.773Z.Desktop.md
deleted file mode 100644
index b704da74..00000000
--- a/logseq/bak/pages/Papers/2024-05-30T07_38_08.773Z.Desktop.md
+++ /dev/null
@@ -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.
--
\ No newline at end of file
diff --git a/logseq/bak/pages/Planner/2025-05-26T20_45_37.886Z.Desktop.md b/logseq/bak/pages/Planner/2025-05-26T20_45_37.886Z.Desktop.md
deleted file mode 100644
index 6b986294..00000000
--- a/logseq/bak/pages/Planner/2025-05-26T20_45_37.886Z.Desktop.md
+++ /dev/null
@@ -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
- -
\ No newline at end of file
diff --git a/logseq/bak/pages/Planner/2025-05-26T20_52_51.351Z.Desktop.md b/logseq/bak/pages/Planner/2025-05-26T20_52_51.351Z.Desktop.md
deleted file mode 100644
index 6b986294..00000000
--- a/logseq/bak/pages/Planner/2025-05-26T20_52_51.351Z.Desktop.md
+++ /dev/null
@@ -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
- -
\ No newline at end of file
diff --git a/logseq/bak/pages/REVIEWS/2024-03-14T07_43_25.348Z.Desktop.md b/logseq/bak/pages/REVIEWS/2024-03-14T07_43_25.348Z.Desktop.md
deleted file mode 100644
index 5fe5e8c0..00000000
--- a/logseq/bak/pages/REVIEWS/2024-03-14T07_43_25.348Z.Desktop.md
+++ /dev/null
@@ -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]]
\ No newline at end of file
diff --git a/logseq/bak/pages/REVIEWS/2024-05-11T11_07_19.143Z.Desktop.md b/logseq/bak/pages/REVIEWS/2024-05-11T11_07_19.143Z.Desktop.md
deleted file mode 100644
index c9475db7..00000000
--- a/logseq/bak/pages/REVIEWS/2024-05-11T11_07_19.143Z.Desktop.md
+++ /dev/null
@@ -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]]
\ No newline at end of file
diff --git a/logseq/bak/pages/REVIEWS/2024-06-15T07_21_35.165Z.Desktop.md b/logseq/bak/pages/REVIEWS/2024-06-15T07_21_35.165Z.Desktop.md
deleted file mode 100644
index 973303bf..00000000
--- a/logseq/bak/pages/REVIEWS/2024-06-15T07_21_35.165Z.Desktop.md
+++ /dev/null
@@ -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]]
\ No newline at end of file
diff --git a/logseq/bak/pages/Teaching/2023-02-15T15_41_50.202Z.android.md b/logseq/bak/pages/Teaching/2023-02-15T15_41_50.202Z.android.md
deleted file mode 100644
index 0a5f9f3b..00000000
--- a/logseq/bak/pages/Teaching/2023-02-15T15_41_50.202Z.android.md
+++ /dev/null
@@ -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
\ No newline at end of file
diff --git a/logseq/bak/pages/contents/2024-03-01T09_06_02.456Z.Desktop.md b/logseq/bak/pages/contents/2024-03-01T09_06_02.456Z.Desktop.md
deleted file mode 100644
index ab4d6187..00000000
--- a/logseq/bak/pages/contents/2024-03-01T09_06_02.456Z.Desktop.md
+++ /dev/null
@@ -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))}}
--
- id:: 644bb986-2554-46ff-b8bd-859586cd10b9
--
-- ## 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
--
\ No newline at end of file
diff --git a/logseq/bak/pages/templates/2025-05-29T14_43_54.636Z.Desktop.md b/logseq/bak/pages/templates/2025-05-29T14_43_54.636Z.Desktop.md
deleted file mode 100644
index 25d8e327..00000000
--- a/logseq/bak/pages/templates/2025-05-29T14_43_54.636Z.Desktop.md
+++ /dev/null
@@ -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]
- - ---
\ No newline at end of file
diff --git a/logseq/config.edn b/logseq/config.edn
index 71d4f88a..fb73199c 100644
--- a/logseq/config.edn
+++ b/logseq/config.edn
@@ -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
diff --git a/logseq/custom.css b/logseq/custom.css
index 8b137891..adf628dc 100644
--- a/logseq/custom.css
+++ b/logseq/custom.css
@@ -1 +1,4 @@
-
+:root {
+--ls-main-content-max-width: 90%;
+--ls-main-content-max-width-wide: 95%;
+}
diff --git a/pages/@A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems.md b/pages/@A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems.md
new file mode 100644
index 00000000..0d68a215
--- /dev/null
+++ b/pages/@A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems.md
@@ -0,0 +1,133 @@
+tags:: [[#zotero]]
+date:: 2017
+title:: @A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems
+item-type:: [[journalArticle]]
+original-title:: A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems
+language:: en
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/RRJ2HC5J), [Web library](https://www.zotero.org/users/1039502/items/RRJ2HC5J)
+
+- [[Abstract]]
+ - Smart Human-centric Ecosystems (SHEs), such as smart cities, emerge from the interaction among independently-owned systems and humans, who are active components and not mere users of the ecosystems. While smart cities and more generally SHEs are becoming common in our society, their verification remains a critical challenge, as traditional testing methods cannot adequately capture the emergent, adaptive and sometime conflicting behavior arising from human, digital and physical components.
+- ### Attachments
+ - [PDF](zotero://select/library/items/382QWRQF) {{zotero-imported-file 382QWRQF, "2017 - A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (18/09/2025, 00:29:35)
+
+ - “interaction among independently-owned systems and humans, who are active components and not mere users of the ecosystems” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “their verification remains a critical challenge, as traditional testing methods cannot adequately capture the emergent, adaptive and sometime conflicting behavior arising from human, digital and physical components.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #a28ae5
+
+ - “Multi-Agent Architectural approach for digital twins of SHEs” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “Multi-Agent Architecture Digital Twin of San Francisco,” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “virtual systems-of-systems” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #2ea8e5
+
+ - “ultra-large-scale systems” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #2ea8e5
+
+ - “continuous evolution, and the contradicting requirements of the systems in the ecosystem” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “autonomy of the systems that dynamically enter and exit the SHE” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “implicit interactions among human and systems that adapt to evolving human behaviors and scenarios that emerge in the cyber-physical environment” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “intrinsic contradictions that can lead to unavoidable SHE failures even when all systems behave according to their specifications” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “defined a new concept of health, that captures the intuitive concept of quality of SHEs in the absence of precise specifications of the SHE as a whole.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “challenge of verifying such ecosystems remains largely underexplored.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #a28ae5
+
+ - “Failures may still occur, not because of faults within any single component, but due to unforeseen interactions among components that respond and adapt to human behavior in unpredictable ways” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #a28ae5
+
+ - “For example, in a smart city, even if traffic lights, ride-sharing platforms, and public transportation systems are individually tested, their combined response to a spontaneous large-scale event (for instance, an unpredictably large flash mob or an extremely urgent stadium evacuation) may produce emergent congestion patterns that no single component anticipates.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #a28ae5
+
+ - “new verification strategies that support continuous observation, behavioral simulation, adaptive analysis, and predictive reasoning. In this context, the Digital Twin (DT) paradigm offers the foundation technology for modeling and reasoning about the state and evolution of human-centric ecosystems, enabling real-time monitoring, exploratory simulation, and predictive diagnostics [27, 42].” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #a28ae5
+
+ - “DTs with centralized architectures badly adapt to SHEs [7, 33]. The definition of a suitable architectural approach of DTs for SHE is still a largely open problem” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 1) #5fb236
+
+ - “Current DTs architectures model humans as static parameters or passive data providers, rather than as autonomous, adaptive and goal-oriented elements within the SHEs, and largely miss the sociotechnical interactions that are fundamental in SHEs” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #a28ae5
+
+ - “state-of-the-art approaches lack the expressiveness needed to model the complexity of SHEs, ultimately limiting their utility for effective monitoring, analysis and testing” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #e56eee
+
+ - “Multi-agent Architectural approach for Digital Twins” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “MAD, a Multi-agent Architectural approach for Digital Twins that addresses the decentralized, dynamic and heterogeneous nature of SHEs.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “To the best of our knowledge, this is the first concrete architectural solution in which agents form the structural foundation of the DT itself.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “Our approach integrates both human and cyber agents, capable of perceiving their physical counterpart, reasoning about their goals, and acting within a context-aware environment.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #ffd400
+ *Ok, not clear yet what's the novelty with respect to autonomous systems and CPS in general.*
+
+ - “responsiveness, fidelity, adaptability and robustness of MADSF .” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “decentralized, dynamic, and autonomous nature” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “The Data Exchange, Digital Model, Service, and Data Management composite components comprise the DT, while the Smart Human-centric Ecosystem (SHE composite component in the figure) is the actual ecosystem augmented with the DT.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “SHE Smart Human-Centric Ecosystem The cyber-physical systems, the humans and the environment in which they operate are the main parts of the Smart Humancentric Ecosystem to be digitally twinned. A SHE can be formally defined as: SHE = ⟨C, H, E⟩ (1) where (i) C is the set of Cyber-Physical systems, including digital platforms and sensorized infrastructures (for instance, traffic monitoring systems, transport control units, utility platforms of a smart city), (ii) H is the set of Humans, whose behaviors and decisions influence and are influenced by the SHE (for instance, citizens, taxi drivers, and tourists in a smart city), and (iii) E is the Environment, that is, the infrastructural context comprising physical spaces and networks where digital and human entities interact (for instance, roads, pa” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 2) #5fb236
+
+ - “Belief-Desire-Intention (BDI) paradigm [47], where belief represents the agent’s knowledge or perception of the current world state, desire denotes the goals of the agent, and intention defines the plans and strategies to achieve its goals.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 3) #e56eee
+
+ - “MADSF , Multi-agent Architecture Digital Twin of San Francisco, a prototype implementation of a DT that we develop to validate the responsiveness, fidelity, adaptability, and robustness of MAD,” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 4) #ffd400
+ *This sentence is a bit strange. IN Figure 1 you present an architecture, which is an abstract representation of a system consisting of different components. How can you validate properties that refer to the way the architectures is implemented, deployed, etc.? How can you assess the responsiveness of an architecture? What can you say about the robusteness of fidelity of an architecture? Please, clarify and make this concrete!*
+
+ - “since it does not devise any feedback generation toward the physical SHE” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 4) #ffd400
+ *So it means, we are talking about a simplification of Fig 1, because we have monodirectional connections, i.e., from physical to cyber worlds.*
+
+ - “Responsiveness” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 6) #ffd400
+ *But this depends on the implemention and not on the architecture per se. Isn't it?*
+
+ - “RQ2. Fidelity: Does MAD accurately model the behavior of SHE? Rationale: Accurately reflecting the behavior of the SHE is critical for reliable analysis, detection and prediction. Metrics: We assess MAD fidelity by computing both the accuracy and GEH7 values for vehicular traffic flow, passenger pick-ups and drop-offs of MADSF , and compare them with SUMO baseline. RQ3. Adaptability: Does MAD adapt to the evolving nature of SHE? Rationale: As the SHE continuously evolves, maintaining adaptive alignment is essential to keep the DT effective. Metrics: We evaluate the adaptability of MAD in terms of the impact of a new agent entering MADSF both statically on the structure of the DS and dynamically on the responsiveness and fidelity of the DS. RQ4. Robustness: Does MAD sustain increasing or abnormal workload conditions? Rationale: Given the evolving nature of SHE, MAD should remain stable even during unexpected workload peaks to ensure continuous effectiveness and resilience. Metrics: We evaluate the robustness of MAD by measuring how responsiveness and fidelity degrade under anomalously high workload peaks.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 6) #ffd400
+ *I'm confused. Are we discussing the implementation of the architecture? The research questions are about a concrete implemenation!?!?!*
+
+ - “RQ1 Findings: MAD keeps aligned with SHE over time, significantly reducing total execution time compared to real-world constraints. It maintains consistent simulation speed across increasingly long intervals, staying in synchronization with the SHE.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 8) #ffd400
+ *How these findings are related to the architecture shown in Fig 1 and/or to the implementation you have done of it? What are the general aspects that can be applied to other implementations/applications?*
+
+ - “RQ2 Findings: MAD accurately replicates the SHE, with over 99% fidelity for traffic flow, passenger pick-ups and drop-offs, and GEH values are consistently under 5.0 threshold.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 8) #ffd400
+ *Again, this depends on the way you have implemented the prototype. The same comment applies also to the other RQ findings.*
+
+ - “RQ3 Findings: MAD adapts to the evolutions of the agents in the SHE with minimal impact on fidelity and responsiveness.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 8) #ffd400
+
+ - “RQ4 Findings: MAD demonstrates strong robustness under high workload and disruptive scenarios. Responsiveness of MAD remains consistently below real-time threshold, and fidelity remains high across all conditions.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 9) #ffd400
+
+ - “There is a huge literature on Digital Twins in various domains [35]. Here, we overview the most relevant studies on Digital Twins for SHE and multi-agent approaches for DTs. Digital Twins for SHE Some recent conceptual studies explore the requirements for DTs in complex and evolving socio-technical environments [7, 13, 17, 33]. Michael et al. [33] emphasize the need of the DT to co-evolve with the SHE to be relevant. David et al. [13] propose a taxonomy that identifies some critical capabilities for DT evolution, such as, runtime model reconciliation and system reconfiguration. Bonetti et al. [7] focus on the socio-technical nature of SHEs and advocate for model-driven engineering to better integrate human and technological dimensions. Several studies discuss the benefits of DTs for ecosystems in domain-specific applications: healthcare DTs for predictive diagnostics [14], smart grids DTs for fault detection [39], smart buildings DTs for energy optimization [23], smart cities DTs for urban mobility, transportation management, and planning [46]. The current approaches for DTs propose centralized architectures that miss the distinctive characteristics of SHEs as ecosystems that emerge from the sometimes implicit interactions between humans and independently-owned systems. Wang et al. [44] propose a mobility DT that integrates humans, infrastructure, and vehicles, however they model humans merely as traffic data points. Dembski et al. [16] incorporate citizens feedback into participatory urban planning, however they consider humans as external participants. Xu et al. [49] and Irfan et al. [26] design traffic DTs driven by centralized analytics without modeling human interactions. Biagiola et al. [6] focus on testing autonomous vehicles, and exclude human-system dynamics. Michael et al. [33] explicitly address the co-evolution of human and technological systems, yet their work remains at a conceptual level and falls short of delivering practical engineering solutions. Architectural proposals that claim to support ecosystem-wide DTs [8, 29, 30] focus on isolated or domain-specific subsystems, often under centralized control. As a result, current works on DTs for SHEs fall short of supporting new behaviors, conflicting goals, and continuous co-evolution between humans, cyber-systems and environment. Multi-Agent Approaches for DTs Recent research increasingly studies multi-agent modeling as a promising strategy for addressing the engineering challenges of DTs for SHEs. However, the work presented so far remains narrowly scoped and does not adequately address the architectural concerns of SHEs. Current agent-based DT solutions are typically applied to single-domain and well-structured systems. Pretel et al.’s MAS4DT framework [37] provides a rigorous mapping between DTs properties and multi-agent constructs, but it is designed for centralized cyber-physical systems with uniform stakeholders. Hussein and Challenger’s MADTwin [25] approach synchronizes physical and digital agents within a smart warehouse context. While it confirms the operational feasibility of agent-based DT, it does not support the modeling of diverse agent behaviors. Pretel et al.’s systematic review [36] confirms the limitations of both agent-based systems that act as consumers of DT services and agent-based systems in which agents constitute the structural foundation of the DT. We address the limitations of current approaches by proposing MAD, a multi-agent DT architecture that explicitly models both cyber and human entities as agents. MAD agents perceive, reason, and act according to their beliefs and goals, and operate within a shared digital environment that enables decentralized coordination and supports the co-evolution of autonomous components.” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 10) #ffd400
+ *The novelty of your approach is not clear with respecto to what already existing. Moreover, since you are also talking about autonomous systems, it is important to refer peculiar architectural patterns, like the MAPE-K that are completely nelected in the paper.*
+
+ - “We validate MAD with MADSF , a level-2 DT of ride-hailing ecosystems that we instantiate on the city of San Francisco” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 10) #ffd400
+ *When you say "validate" you have actually implemented a DT by following the proposed architecture, and the findings are related to that specific implementations. It is not clear what are the take-away messages or general insights that can be applied to any other potential implementations of the proposed architecture.*
+
+ - “We provide a comprehensive usage guide, data and code to run MADSF in our replication package, along with the experiments’ results.11” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 10) #5fb236
+
+ - “Replication package available at https://anonymous.4open.science/r/sfdigitalshadow” (“A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems”, 2017, p. 10) #5fb236
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ STRENGHTS:
+
+ WEAKNESSES:
+
+ COMMENTS: Organize the notes with respect to the following criteria:
+
+ -
+ `Novelty`
+
+ -
+ `Rigor`
+
+ -
+ `Relevance (of the contribution)`
+
+ -
+ `Verifiability and Transparency`
+
+ -
+ `Presentation`
+
+ And then add a Detailed Comments section to report the notes that contain issues or typos.
+ Can you also formulate three explicit questions by considering the comments above?
\ No newline at end of file
diff --git a/pages/@A kNN-Based Recommender System for Test Case Reuse in Agile Software Development.md b/pages/@A kNN-Based Recommender System for Test Case Reuse in Agile Software Development.md
new file mode 100644
index 00000000..48671a97
--- /dev/null
+++ b/pages/@A kNN-Based Recommender System for Test Case Reuse in Agile Software Development.md
@@ -0,0 +1,345 @@
+tags:: [[#zotero]]
+date:: 2026
+title:: @A kNN-Based Recommender System for Test Case Reuse in Agile Software Development
+item-type:: [[journalArticle]]
+original-title:: A kNN-Based Recommender System for Test Case Reuse in Agile Software Development
+language:: en
+authors:: [[Anonymous Author]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/NUL9BMH7), [Web library](https://www.zotero.org/users/1039502/items/NUL9BMH7)
+
+- [[Abstract]]
+ - Context: Agile testing poses unique challenges, including short development cycles, evolving requirements, and the need to rapidly execute and update test suites. Efficient reuse of test cases can help address these demands, but remains difficult due to fragmented documentation and evolving repositories. Objective: This study proposes a Recommender System (RecSys) to support test case reuse in agile development contexts by leveraging historical user stories and a domain-specific taxonomy. Method: We implemented a K-Nearest Neighbors (KNN)-based RecSys to retrieve user stories similar to a given target and recommend their associated test cases. The algorithm’s transparent logic enables traceable and interpretable recommendations. The evaluation followed a multi-method design: first, an offline experiment with 217 user stories and 1077 test cases from two companies identified the best configuration based on recall, precision, and F-measure. Then, this configuration was applied in an online case study involving two agile projects to assess real-world impact on test reuse and suite completeness. Results: The best offline configuration achieved a recall of 67.5%, precision of 37.8%, and F-measure of 51.0%. In the online phase, 65.09% of the developed test cases aligned with existing assets, and the RecSyS increased the projects’ test suites by 38.78%. Conclusion: These results indicate that our taxonomy-based RecSyS effectively supports test case reuse in agile settings, achieving solid results both offline and in practice. Its transparent logic, minimal infrastructure needs, and alignment with agile workflows make it a lightweight and practical alternative to more complex reuse solutions.
+- ### Attachments
+ - [PDF](zotero://select/library/items/SM9JG55B) {{zotero-imported-file SM9JG55B, "Author - 2026 - A kNN-Based Recommender System for Test Case Reuse in Agile Software Development.pdf"}}
+- ### Notes
+ - # Annotations
+ (18/09/2025, 01:58:43)
+
+ - “Agile testing poses unique challenges, including short development cycles, evolving requirements, and the need to rapidly execute and update test suites.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “Efficient reuse of test cases can help address these demands, but remains difficult due to fragmented documentation and evolving repositories” (Author, 2026, p. 1) #e56eee
+ * *
+
+
+
+ - “This study proposes a Recommender System (RecSys) to support test case reuse in agile development contexts by leveraging historical user stories and a domain-specific taxonomy” (Author, 2026, p. 1) #e56eee
+ * *
+
+
+
+ - “We implemented a K-Nearest Neighbors (KNN)-based RecSys to retrieve user stories similar to a given target and recommend their associated test cases.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “first, an offline experiment with 217 user stories and 1077 test cases from two companies identified the best configuration based on recall, precision, and F-measure.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “this configuration was applied in an online case study involving two agile projects to assess real-world impact on test reuse and suite completeness.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “These results indicate that our taxonomy-based RecSyS effectively supports test case reuse in agile settings, achieving solid results both offline and in practice.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “developers must navigate increasingly complex information spaces—often spending disproportionate time seeking relevant artifacts at the expense of value-generating work” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “Recommender Systems (RecSys) for software engineering have emerged as tools that assist developers with various tasks—ranging from code reuse to effective bug reporting—and aim to reduce cognitive load and improve productivity [” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “reusing validated test cases offers a promising way to improve test coverage and efficiency without increasing effort” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “When organizations accumulate substantial testing knowledge across features or projects, test reuse can reduce redundancy and accelerate software testing.” (Author, 2026, p. 1) #a28ae5
+ * *
+
+
+
+ - “Industrial test repositories often suffer from inconsistent documentation, lack of structure, and frequent changes” (Author, 2026, p. 1) #a28ae5
+ * *
+
+
+
+ - “However, these techniques often require complex infrastructure—semantic models, embeddings, or deep learning pipelines, and typically operate at the code level or support regression testing, rather than proactive reuse at the user story level in agile workflows.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “we developed a RecSys tailored to agile environments, particularly for early sprint planning and user story development.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “The system leverages two underutilized resources: structured taxonomies and historical user stories.” (Author, 2026, p. 1) #5fb236
+ * *
+
+
+
+ - “referred to as offline validation in RecSys” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “First, we used the data from 13 industrial projects from one organization, encompassing 217 user stories and 1077 distinct test cases, to identify the most effective RecSys configuration.” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “in-situ case study in two projects of the same organization to assess the RecSys’s practical impact on agile test case development” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “test cases linked to semantically similar user stories in agile development.” (Author, 2026, p. 2) #e56eee
+ * *
+
+
+
+ - “textual similarity between requirements implies similarity in downstream artifacts (e.g., code and tests).” (Author, 2026, p. 2) #ffd400
+ *This is a crucial assumption that can give place to some threats to validity. It's ok if it is mentioned in that section. *
+
+
+
+ - “Abbas et al. [2] provide empirical support for this assumption. Their study evaluated six NLP models—ranging from lexical to deep learning-based approaches—and found a moderately positive correlation between the similarity of requirements and the similarity of their associated software components” (Author, 2026, p. 2) #a28ae5
+ *That's important. *
+
+
+
+ - “that semantically similar user stories are likely to be associated with reusable test cases.” (Author, 2026, p. 2) #e56eee
+ * *
+
+
+
+ - “This assumption is further supported by broader work in requirements traceability and retrieval [24, 55], which shows that requirements labeled with semantic metadata—such as purpose, stakeholder, or behavior—can be more effectively retrieved. Collectively, these studies justify our design choice to use structured user story similarity as a proxy for identifying reusable test cases.” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “Web Information Systems (WIS)” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “Module, Operation” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “. Each user story can be labeled with one or more such pairs, enabling multi-label classification and more expressive comparisons across stories.” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “Any structured labeling scheme that enables meaningful comparison across requirements, especially with respect to the type of feature involved, can support our approach. This flexibility allows adaptation to other domains or evolving taxonomies.” (Author, 2026, p. 2) #5fb236
+ * *
+
+
+
+ - “These solutions require mature projects with rich defect histories and focus on prioritization rather than early-stage reuse” (Author, 2026, p. 3) #e56eee
+ * *
+
+
+
+ - “LLMs represent a more recent shift from reuse to generation.” (Author, 2026, p. 3) #e56eee
+ * *
+
+
+
+ - “Empirical evaluations show that models like GPT-4 and Gemini can generate high-coverage unit tests given source code and examples” (Author, 2026, p. 3) #5fb236
+ * *
+
+
+
+ - “However, these black-box approaches raise reproducibility and traceability concerns and do not capitalize on validated, existing test assets within an organization.” (Author, 2026, p. 3) #e56eee
+ * *
+
+
+
+ - “We propose a RecSys that classifies User Stories using a validated taxonomy and applies a transparent similarity metric to retrieve reusable test cases, before coding begins.” (Author, 2026, p. 3) #5fb236
+ * *
+
+
+
+ - “The RecSys receives as input a target requirement and produces a list of potential test cases to be reused by testers through the data analysis from previously executed projects or ones under execution.” (Author, 2026, p. 3) #5fb236
+ * *
+
+
+
+ - “we assumed that test cases are requirements-driven and that, if the requirements are similar, the test cases are also similar, following the findings of Abbas et al. [2].” (Author, 2026, p. 3) #5fb236
+ * *
+
+
+
+ - “In particular, we employed the WIS taxonomy proposed by Dilorenzo et al. [15], detailed in Section 2.1. For instance, if we have the set of user stories given by U = {U S1, U S2, · · · , U Sk }, where k is the total number of user stories, and that each U Sk ∈ U are of the type (Authentication, First login), we can infer that they are all similar, even if they have different descriptions.” (Author, 2026, p. 3) #ffd400
+ *This is a strong assumption. Similar user stories have similar tests is strong for me. Even minor variations of code implementing similar user stories can make tests different. It is interesting to see, what's the usage of the recommended tests. Are they used as starting point or as reference implementation to look at while developing the actual test cases? *
+
+
+
+ - “Acceptance Criteria (AC)” (Author, 2026, p. 3) #e56eee
+ * *
+
+
+
+ - “Let f be a utility function that measures the usefulness of a test case t to a user story u, i.e., f : U × T −→ R,” (Author, 2026, p. 3) #e56eee
+ * *
+
+
+
+ - “Recommender: responsible for analyzing characteristics vectors, generated by the data transformer, calculating the similarity between target User Story and retrieved User Stories, and recommending test cases developed for the most similar User Stories ranked by their relevance.” (Author, 2026, p. 3) #5fb236
+ * *
+
+
+
+ - “uses the collaborative filtering based on user attributes [23], and performs the recommendation of test cases from the nearest neighbors, to the target User Story.” (Author, 2026, p. 4) #ffd400
+ * *
+
+
+
+ - “K Nearest Neighbors (KNN) algorithm” (Author, 2026, p. 4) #5fb236
+ * *
+
+
+
+ - “We validated the proposed Recommender System using a multimethod design that combined a retrospective experiment using historical project data (offline validation) and a pilot in situ deployment in industry projects (online validation). This strategy allowed us to examine both the internal performance of the algorithm under controlled conditions and its practical usefulness in real-world agile teams.” (Author, 2026, p. 5) #5fb236
+ *This is important and well motivated. *
+
+
+
+ - “After identifying the best-performing configuration, we proceeded to the online phase, where we deployed the RecSys in two ongoing software projects at an industrial partner.” (Author, 2026, p. 5) #5fb236
+ * *
+
+
+
+ - “We did not include a comparative evaluation with existing test case recommenders such as those proposed by Bera et al.[9] or Ge and Liu[20], as these approaches rely on fundamentally different infrastructures, including structured requirement modeling, collaborative filtering, and knowledge graphs. Our method depends on a domain-specific taxonomy and requires semantic labeling of user stories, making direct comparisons non-trivial and potentially misleading. Furthermore, no benchmark dataset exists that would support a controlled comparison under equivalent conditions. Instead, we focused on assessing the internal effectiveness of our approach through multiple configurations and evaluating its external utility through industrial deployment.” (Author, 2026, p. 5) #ffd400
+ *Ok even though this is a potential bias that needs to be discussed. *
+
+
+
+ - “4.1.1 Training Dataset Definition” (Author, 2026, p. 5) #2ea8e5
+ * *
+
+
+
+ - “The lack of RecSys users (User Stories) and items (test cases) data problem is called User Cold-Start and Item Cold-Start, respectivel” (Author, 2026, p. 5) #5fb236
+ * *
+
+
+
+ - “we collected User Stories data, AC, and test cases from project databases of two software development companies that execute projects with Scrum” (Author, 2026, p. 5) #5fb236
+ * *
+
+
+
+ - “4.1.2 Experiment Design.” (Author, 2026, p. 5) #2ea8e5
+ * *
+
+
+
+ - “support Scrum teams in reusing test cases and enhancing the projects’ test suites.” (Author, 2026, p. 6) #5fb236
+ * *
+
+
+
+ - “RQ” (Author, 2026, p. 6) #ff6666
+ *RQ_on *
+
+
+
+ - “RQon1: To what extent does the test cases recommender increase the test suite completeness for agile projects?” (Author, 2026, p. 6) #ffd400
+ *In contrast to the situation when no support is used? What's the baseline? *
+
+
+
+ - “RQon2: To what extent does the test cases recommender enable the test cases reuse for agile projects?” (Author, 2026, p. 6) #ffd400
+ * *
+
+
+
+ - “RQon1, we wanted to identify whether the test suite resulted from the recommendations and test cases developed by the project testers are more complete than the original test suite,” (Author, 2026, p. 6) #5fb236
+ * *
+
+
+
+ - “RQon2, our goal was to identify if the RecSys provides testers with test cases that they would develop, that is, if it anticipates test cases that would be developed and, thus, allow the tester to reuse them.” (Author, 2026, p. 6) #5fb236
+ * *
+
+
+
+ - “two projects under development from one organization” (Author, 2026, p. 6) #ffd400
+ *Can you say something more on the selected projects and on the organization? (business domain, kinds of projects, etc) *
+
+
+
+ - “hen, we compared the recommended test cases with the ones created by the project’s testers. After RecSys execution, we discussed the results with the project’s testers and classified the test cases as follows:” (Author, 2026, p. 6) #ffd400
+ *This was a qualitative comparison, isn't it? *
+
+
+
+ - “Accepted” (Author, 2026, p. 6) #ffd400
+ *Acepted how? I'm not sure it can be used as it is recommended. I guess some refinements/changes were required, isn't it? *
+
+
+
+ - “a higher number of neighbors, whereas the recall value does not present a significant change.” (Author, 2026, p. 7) #5fb236
+ * *
+
+
+
+ - “he configuration Euclidean distance, K = 3, heuristic = yes outperformed all 59 alternatives (p < 0.05, Nemenyi post-hoc). It achieved 67.5 % recall, 37.8 % precision, and an F2 score of 0.510. This setting is therefore carried forward to the online deployment.” (Author, 2026, p. 7) #5fb236
+ * *
+
+
+
+ - “Additionally, we analyzed the relevance of the accepted test cases, based on the testers’ perception, to identify the tool’s efficiency. Thus, Figure 5 shows the relevance percentages.” (Author, 2026, p. 8) #5fb236
+ * *
+
+
+
+ - “Figure 5: Accepted test cases relevance.” (Author, 2026, p. 8) #ffd400
+ *This is not very good, isn't it? It seems that among the accepted tests, those with low relevance was 47.5% and only 25.4% was considered to be highly relevant... *
+
+
+
+ - “It is worth noting that the percentage of test cases reused is not directly related to the percentage of effort reduction for the development of these reused test cases” (Author, 2026, p. 8) #5fb236
+ * *
+
+
+
+ - “Hence, two-thirds of manually authored tests could have been reused with minor adaptation effort.” (Author, 2026, p. 8) #5fb236
+ * *
+
+
+
+ - “Impact on test reuse and suite completeness. Across 41 User Stories, the RecSys recommended 334 test cases. Of these, 132 matched tests already written by the testers (i.e., reused), and 79 were accepted as new, valuable additions—resulting in a 38.8% increase in the test suite.2 Altogether, approximately 63% of the recommended test cases were considered useful, showing that the system can meaningfully support reuse and enrich coverage with minimal overhead.” (Author, 2026, p. 9) #5fb236
+ * *
+
+
+
+ - “Limitations and failure cases. Despite its benefits, the RecSys was not without limitations. The most common reason for rejection (86% of rejected cases) was incompatibility with implicit or project-specific business rules not captured by the taxonomy. This highlights an important improvement opportunity: augmenting user stories with additional semantic tags or rule-level metadata could help filter out false positives and improve recommendation relevance.” (Author, 2026, p. 9) #5fb236
+ * *
+
+
+
+ - “Applicability and generalization. Although the evaluation was conducted in the context of Web Information Systems, the approach depends primarily on the availability of a domain-specific taxonomy. Substituting this taxonomy for others—tailored to different application domains—requires minimal adaptation effort. Our findings support the broader claim that lightweight, taxonomy-guided kNN-based recommenders can effectively promote early-stage test reuse in agile development, without requiring complex infrastructure or large-scale data.” (Author, 2026, p. 9) #5fb236
+ * *
+
+
+
+ - “7 THREATS TO VALIDITY This section discusses the potential threats to the validity of our study, structured according to the categories proposed by Wohlin et al. [53]. Conclusion Validity. Although the offline dataset contains 217 user stories and 1 077 test cases, some taxonomy categories (e.g., Authentication) are under-represented. When a category appears fewer than K times in a fold, the RecSys cannot identify the required neighbors. We mitigated this by discarding such folds and reporting the effective sample size, but the reduced counts lower statistical power for those categories. Further, we compared 60 algorithm configurations, increasing the risk of Type-I error. We therefore applied the Friedman test followed by a post-hoc Nemenyi procedure and interpreted results at α = 0.05. Nonetheless, borderline-significant differences should be interpreted with caution. Finally, data Normality was rejected by Shapiro–Wilk, justifying non-parametric analysis, but other assumptions (e.g., independence of folds) remain. Cross-validation folds can be correlated if neighboring user stories share many test cases; future work could use nested cross-validation to reduce this risk. Internal Validity.User stories were manually mapped to taxonomy categories by the first author and later double-checked by two co-authors. Disagreements (6 %) were resolved by discussion. Nevertheless, latent bias may persist. A kappa statistic was not calculated; future work will involve independent raters and report inter-rater reliability. Additionally, during the online study, the Scrum team adopted a new test-management plug-in that automatically duplicates certain test cases. We controlled for this by excluding auto-generated duplicates from reuse counts, yet residual confounding is possible. Finally, testers may become more proficient over successive sprints, independently improving reuse. Because the pilot lasted only seven sprints (41 stories) and no time–series analysis was performed, maturation effects cannot be fully ruled out. Construct Validity. We relied on precision, recall, and F-measure (β = 2) for offline evaluation, assuming they correlate with tester utility. However, these metrics do not account for the effort required to inspect false positives or adapt reused tests. Complementary measures such as Mean Reciprocal Rank or time-to-acceptance could provide a richer picture. Further, we evaluated only kNN with six distance functions for viability reasons. Other families of RecSys (e.g., matrix factorization, BERT/LLM embeddings) were not explored. This limits construct coverage; future replications should vary the underlying model. Finally, similarity is computed on binary vectors derived from our taxonomy. If two stories are semantically similar but fall into different categories, similarity is underestimated. Conversely, stories in the same category but semantically dissimilar may inflate similarity. Introducing textual embeddings or hierarchical weights could alleviate this threat. External Validity. Training data came from two Brazilian software vendors; the online pilot ran in one of them. Both organizations develop information systems for web/mobile platforms. Results may differ in safety-critical domains (e.g., avionics) or where test documentation is richer/poorer. Further, uur dataset size (1 077 tests) is modest compared with repositories maintained by large enterprises. kNN’s computational cost is O (nK); additional engineering (e.g., ANN indexing) may be required for million-scale test suites. Additionally, the approach presumes (i) user stories conform to the chosen taxonomy, (ii) each story links to at least K = 3 test cases in the historical repository, and (iii) similar wording or semantics persist across projects. Organizations lacking these conditions may observe lower recall or face a cold-start problem. Finally, both pilot teams already emphasized test automation and collective ownership of test artifacts. In cultures where testers and developers work in silos, the willingness to reuse peer artifacts might differ.” (Author, 2026, p. 10) #ffd400
+ *Overall, I liked the paper. It presents a simple even though effective approach to support the discovery and reuse of testing. The performed experiments are encouraging even though additional investigations need to be n order to support developers in adopting the retrieved test. The efforts required to use the recommended test need to be further investigated. *
\ No newline at end of file
diff --git a/pages/@AI-Assisted Modeling%3A DSL-Driven AI Interactions.md b/pages/@AI-Assisted Modeling%3A DSL-Driven AI Interactions.md
new file mode 100644
index 00000000..e03ed961
--- /dev/null
+++ b/pages/@AI-Assisted Modeling%3A DSL-Driven AI Interactions.md
@@ -0,0 +1,89 @@
+tags:: [[#zotero]]
+title:: @AI-Assisted Modeling: DSL-Driven AI Interactions
+item-type:: [[journalArticle]]
+original-title:: AI-Assisted Modeling: DSL-Driven AI Interactions
+language:: en
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/LNN2PAY5), [Web library](https://www.zotero.org/users/1039502/items/LNN2PAY5)
+
+- [[Abstract]]
+ - AI-assisted programming greatly increases software development performance. We enhance this potential by integrating transparency through domain-specific modeling techniques and providing instantaneous, graphical visualizations that accurately represent the semantics of AI-generated code. This approach facilitates visual inspection and formal verification, such as model checking.
+- ### Attachments
+ - [PDF](https://icse2026-larc.hotcrp.com/doc/icse2026-larc-paper70.pdf) {{zotero-imported-file IJWV5JTZ, "AI-Assisted Modeling DSL-Driven AI Interactions.pdf"}}
+- ### Notes
+ - I’m doing a review for a workshop paper and these are the notes that I took while reading the paper.
+
+ # Annotazioni
+ (7/12/2025, 15:56:09)
+
+ “We enhance this potential by integrating transparency through domain-specific modeling techniques and providing instantaneous, graphical visualizations that accurately represent the semantics of AI-generated code.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “visual inspection and formal verification, such as model checking.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “Visual Studio Code extension for the Lingua Franca language” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “This is achieved by adapting the code generator of the modeling language to produce structured prompt templates that allow LLMs to generate implementation code for dedicated purposes that is automatically integrated in the overall system.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “we enhance AI-assisted programming with domainspecific modeling techniques and providing instantaneous, graphical visualizations that accurately represent the semantics of AIgenerated code as a basis for visual inspection and formal verification, such as model checking.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “AI-assisted programming” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “Conceptually” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “Pragmatically” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “Background” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “it remains difficult to control and steer effectively.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “s. Moreover, classical modeling workflows frequently depend on graphical representations, which are not easily generated by current AI systems” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “We combine” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “(i) state-of-the-art DSL modeling techniques with instantaneous automatic visualizations,” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “(ii) AIassisted programming to enable iterative and interactive support for DSL development.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 1)
+
+ “generating graphical models via AI is more technically demanding” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “we propose increasing the number of observation and interaction points throughout the modeling process” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “They allow modelers to inspect intermediate results, guide refinements, and provide feedbacksupporting more flexible, iterative workflows that move beyond rigid one-shot prompting” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “we decompose the program/model refinement process into distinct stages, allowing for incremental progress and improved controllability during model development” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2) The authors should clarify if the approach is for supporting modeling activities first or code development. In some sentences it seems that the approach is for assisting modeling activities, in some other parts of the paper it seems that the goal of the proposed approach is for supporting the development activities and in parallel a graphical visualization of the code being generated is given. Both directions are indeed important, but it is necessary to be clear on what's the goal of the paper.
+
+ “Contribution” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “visual verification tailored to DSL development” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2) What kind of verification do you support?
+
+ “reliability and controllability” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “Finally, we outline how parts of this extension may themselves be generated via AI in the future, further streamlining the development process.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “approach to AI-assisted modeling,” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “Building on these developments, this work investigates how similar forms of assistance can be applied to domainspecific modeling, with the goal of enabling a more natural and interactive modeling experience” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “Instead of treating model generation as a one-shot task, our approach introduces a dialog-driven workflow that facilitates clarification, program/model refinement, and visual feedback throughout the process.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “The Concept.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 2)
+
+ “Add a reactor named compute that multiplies the input by three and link them both.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 5) That's interesting, int the sense we need a way to define the abstraction of the model and understand the target artifact that will container what the prompt is asking. Here the multiplier function is in the code and not in the model, who decided that?
+
+ What if I change the final model source? Is this considered in the process? This manual intervention should be also used to update the model accordingly.
+
+ “From here create an alternative of the compute reactor that multiplies the input by five.” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 5) Here there is the decision to where the new reactor should be connected to
+
+ “Figure 4:” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 5) It is important to clarify that this is the modeling phase, the "configuration" step is not shown in the example. The settings related to the definition of the Lingua Franca language is important and not shown in the Figure.
+
+ “Listing 2: Current timer definintion in the Lingua Franca grammar” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 6) The efforts required to define the API that is specific for the language at hand is not clear. I gues that for each language, corresponding tools need to be defined. This phases should be more elaborated i the paper in order to substantiate it also with respect to the complexity of the target modeling language.
+
+ “we explored how similar refinement workflows can be extended to the development of domain-specific languages” (“AI-Assisted Modeling: DSL-Driven AI Interactions”, p. 7) The process presented in this paper is more on the modeling phase and not on the modeling language definition.
+
+ Consider that the comments tagged with #5fb236 are just highlights, while those tagged with #e56eee and #a28ae5 are important sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY:
+
+ COMMENTS:
+
+ Please, avoid the typical ChatGPT dash character, and do not write in bullet points,
\ No newline at end of file
diff --git a/pages/@Bridging the gap between industry and academia%3A sustainability in LLM-assisted software engineering.md b/pages/@Bridging the gap between industry and academia%3A sustainability in LLM-assisted software engineering.md
new file mode 100644
index 00000000..cbdcd9be
--- /dev/null
+++ b/pages/@Bridging the gap between industry and academia%3A sustainability in LLM-assisted software engineering.md
@@ -0,0 +1,14 @@
+tags:: [[#zotero]]
+date:: 2026
+title:: @Bridging the gap between industry and academia: sustainability in LLM-assisted software engineering
+item-type:: [[journalArticle]]
+original-title:: Bridging the gap between industry and academia: sustainability in LLM-assisted software engineering
+language:: en
+authors:: [[Maja H Kirkeby]], [[Pepijn de Reus]], [[Ana Oprescu]], [[Kalle Pronk]], [[Qin Zhao]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/LNXBP7BF), [Web library](https://www.zotero.org/users/1039502/items/LNXBP7BF)
+
+- [[Abstract]]
+ - The advent of Large Language Models in software engineering brings both academic research and industry to the cutting edge of uncharted territory, breaking the typical division of roles, and inviting a new type of symbiosis between academia and industry. Drawing on insights from the SILAS workshop, this paper examines sustainability in LLM-assisted software engineering. It identifies key gaps between academic and industrial approaches to methods and metrics, accessibility of systems, and efficiency tradeoffs. We outline key considerations for shaping research agendas that emphasize standardized, outcome-oriented frameworks linking reproducibility with real-world sustainability.
+- ### Attachments
+ - [Bridging the gap between industry and academia: sustainability in LLM-assisted software engineering](https://icse2026-greens.hotcrp.com/doc/icse2026-greens-paper27.pdf) {{zotero-imported-file EQ4SQVBI, "Kirkeby et al. - 2026 - Bridging the gap between industry and academia sustainability in LLM-assisted software engineering.pdf"}}
\ No newline at end of file
diff --git a/pages/@Determining Application Test Results Using Adaptive JSON.md b/pages/@Determining Application Test Results Using Adaptive JSON.md
new file mode 100644
index 00000000..82225e01
--- /dev/null
+++ b/pages/@Determining Application Test Results Using Adaptive JSON.md
@@ -0,0 +1,123 @@
+tags:: [[#zotero]]
+date:: 2026
+title:: @Determining Application Test Results Using Adaptive JSON
+item-type:: [[journalArticle]]
+original-title:: Determining Application Test Results Using Adaptive JSON
+language:: en
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/PIWLIAUZ), [Web library](https://www.zotero.org/users/1039502/items/PIWLIAUZ)
+
+- [[Abstract]]
+ - JSON has become the most popular data exchange format for APIs, especially with the rise of both REST and GraphQL APIs. However, conventional techniques for writing and updating API tests remain laborious and time-consuming. Recent API testing solutions, such as Snapshot Testing and Traffic Mirroring Testing, attempt to address these challenges by leveraging a new data-driven testing method where each JSON API response is compared directly against a baseline. Unlike conventional testing methods, where the expected results and comparison logic are stored together in the test code, this new approach separates them. However, issues such as dynamic data or frequently changing yet irrelevant fields can still cause tests to fail unexpectedly, leading to high maintenance costs. This paper introduces the Adaptive JSON Comparison process, a novel methodology for creating flexible, stable, and maintainable tests for validating JSON API responses. It presents Skeleton JSON, a structural abstraction of the API response, and Adaptive JSON, a hybrid format that selectively combines JSON nodes with Skeleton JSON nodes. The transformation is controlled by a declarative data structure, Adaptation Set, which allows engineers to define precisely which parts of an API response to validate by value and which by structure, while systematically ignoring irrelevant or dynamic sections. Furthermore, a flexible JSON Comparison Filter enables the application of customized comparison logic to specific JSON nodes. We implemented and applied the Adaptive JSON Comparison method to both Snapshot Testing and Traffic Mirroring Testing scenarios. Our evaluation of a suite of APIs at a global e-commerce company demonstrates a marked reduction in spurious test failures and a significant decrease in the manual effort required to maintain test suites. By addressing key challenges in JSON-Driven Testing, our work streamlines quality assurance and makes automated testing more practical and scalable.
+- ### Attachments
+ - [PDF](zotero://select/library/items/8AEAME62) {{zotero-imported-file 8AEAME62, "2026 - Determining Application Test Results Using Adaptive JSON.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (14/09/2025, 17:59:08)
+
+ - “writing and updating API tests” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #a28ae5
+
+ - “Recent API testing solutions, such as Snapshot Testing and Traffic Mirroring Testing, attempt to address these challenges by leveraging a new data-driven testing method where each JSON API response is compared directly against a baseline.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #5fb236
+
+ - “Unlike conventional testing methods, where the expected results and comparison logic are stored together in the test code, this new approach separates them.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #a28ae5
+
+ - “This paper introduces the Adaptive JSON Comparison process, a novel methodology for creating flexible, stable, and maintainable tests for validating JSON API responses.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #a28ae5
+
+ - “Skeleton JSON, a structural abstraction of the API response, and Adaptive JSON, a hybrid format that selectively combines JSON nodes with Skeleton JSON nodes.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #5fb236
+
+ - “Adaptation Set, which allows engineers to define precisely which parts of an API response to validate by value and which by structure, while systematically ignoring irrelevant or dynamic sections” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #a28ae5
+
+ - “In recent years, Representational State Transfer (REST) has become the most popular API style.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #5fb236
+
+ - “JavaScript Object Notation (JSON) has become the most popular data exchange format for APIs.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #5fb236
+
+ - “However, conventional techniques for writing and updating API tests, where the expected API responses and the comparison logic are stored together in the test code, remain laborious and timeconsuming.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #a28ae5
+
+ - “a new data-driven testing (DDT) method, herein referred to as JSON-based data-driven testing (JSON-DDT), which leverages JSON as data sources, has emerged.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #a28ae5
+
+ - “g[” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #ff6666
+ *missing space*
+
+ - “g[” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #ff6666
+ *Missing space. Many occurrences of this problem.*
+
+ - “[14],” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #ffd400
+ *References contains many items from the gray literature even for supporting critical aspects of the paper. Instead of referring medium.com or postman.com posts, I suggest refer instead peer-reviewed papers.*
+
+ - “By separating the test environment settings, the test input parameters, and the expected API responses from the comparison logic, and by making the comparison logic a standard sharable library, a lot of manual steps to write test code are avoided in this new method, therefore makes the tests easy to write and friendly for humans to understand.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #5fb236
+
+ - “However, JSON-DDT has its own limitations and challenges, since the flexibility of using customizable test code to define and compare the expected results is largely reduced.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 1) #ffd400
+ *The mentioned limitation is not evident and properly stressed. Authors introduce that the paper is going to address challenges that are not clear at this very early point of the work.*
+
+ - “is resilient to insignificant changes” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ffd400
+ *What does it mean?*
+
+ - “JSON Schema” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ffd400
+
+ - “distinct advantages for the specific context of automated API testing” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ffd400
+ *Such advantages need to be clarified. For instance, what's new with respect to 10.1016/j.knosys.2016.03.020 and 10.1109/MODELS50736.2021.00033 ?*
+
+ - “Skeleton JSON is designed with simplicity and test automation as its primary goals. It is lightweight,” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ffd400
+ *Ok saying that at Section 2, but I expect to see some validation later in the paper supporting such mentioned strengths of Skeleton JSON.*
+
+ - “An Adaptive JSON object can be: (1) a direct subset of the original JSON; (2) a complete skeleton derived from all or part of the original JSON; or (3), most powerfully, a hybrid containing a selection of both original and skeletonized nodes.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ffd400
+ *Quite vague.*
+
+ - “,” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ff6666
+
+ - “The core principle of Adaptive JSON is selective abstraction. Engineers can choose to preserve the exact values for stable fields while converting volatile or irrelevant fields to their Skeleton JSON type representation.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ffd400
+ *What are the requirement that have driven the definition and development of "Adaptive Json"*
+
+ - “• The price field, which may fluctuate or be irrelevant to a specific test case, is abstracted to its type, "number".” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #5fb236
+
+ - “This targeted approach allows engineers to create robust validation rules that are resilient to insignificant data changes, directly addressing a primary cause of brittleness in automated testing.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #a28ae5
+
+ - “This design separates the testing logic (the consumer) from the core comparison engine (the provider)” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #5fb236
+
+ - “The Adaptive JSON Comparison Provider is the core component, responsible for executing the comparison. It contains two primary internal modules: • Automated Generation: The Adaptive JSON Conversion Module, which takes a raw JSON object and an Adaptation” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 2) #ff6666
+ *This can be removed because it's not updated with respect to the content of Fig. 3. The next paragraph seems to be updated.*
+
+ - “To implement the concepts of Adaptive JSON, we designed a modular system based on a consumer-provider architecture, as illustrated in the teaser Figure 3. This design separates the testing logic” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 3) #ffd400
+ *This is a repetition in the text.*
+
+ - “**Adaptive JSON Comparison Provider**” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 3) #ffd400
+ *The usage of ** ** seems to be related to MD syntax for making the text bold.*
+
+ - “In this paper, we addressed the critical challenge of brittleness in modern data-driven API testing. We identified that naive comparisons of JSON responses in techniques like Snapshot Testing and Traffic Mirroring lead to high maintenance costs due to frequent, spurious failures from dynamic or irrelevant data variations.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 7) #ffd400
+ *This requires to be substantiated with some concrete and motivational example.*
+
+ - “Our core contributions include the concepts of Skeleton JSON and the hybrid Adaptive JSON format, which are controlled by a declarative Adaptation Set. This approach allows engineers to precisely define which parts of an API response to validate by value and which by structure. As demonstrated in our case studies, applying this method to Snapshot Testing and Traffic Mirroring effectively filters out irrelevant data noise, significantly reducing false positives and making these powerful testing techniques more practical and robust in real-world environments.” (“Determining Application Test Results Using Adaptive JSON”, 2026, p. 8) #ffd400
+ *The strenghts of the Skeleton Json and Adaptive JSON is not presented with respect to existing approaches that are able to retrieve JSON schema out JSON documents.
+ The proposed approach is not compared with any API testing techniques.
+
+ THe paper is not always well written. There are repeated text. THe authors can use additional papges to properly present the strenghts and uthe limtiations of the proposed approach.*
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ STRENGHTS:
+
+ WEAKNESSES:
+
+ COMMENTS: Organize the notes with respect to the following criteria:
+
+ -
+ `Novelty`
+
+ -
+ `Rigor`
+
+ -
+ `Relevance (of the contribution)`
+
+ -
+ `Verifiability and Transparency`
+
+ -
+ `Presentation`
+
+ And then add a Detailed Comments section to report the notes that contain issues or typos.
+ Can you also formulate three explicit questions by considering the comments above?
\ No newline at end of file
diff --git a/pages/@Generation of Unit Tests for Test-Driven Development using Large Language Models.md b/pages/@Generation of Unit Tests for Test-Driven Development using Large Language Models.md
new file mode 100644
index 00000000..b6b56432
--- /dev/null
+++ b/pages/@Generation of Unit Tests for Test-Driven Development using Large Language Models.md
@@ -0,0 +1,126 @@
+tags:: [[#zotero]]
+title:: @Generation of Unit Tests for Test-Driven Development using Large Language Models
+item-type:: [[journalArticle]]
+original-title:: Generation of Unit Tests for Test-Driven Development using Large Language Models
+language:: en
+authors:: [[Nathanael Yao]], [[Juergen Dingel]], [[Ali Tizghadam]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/2FPNV3ZR), [Web library](https://www.zotero.org/users/1039502/items/2FPNV3ZR)
+
+- [[Abstract]]
+ - Test-Driven Development (TDD) is a process that has been shown to reduce software defects yet is not always adopted in industrial software. Case studies on industrial teams have shown up to a 50% reduction in defect density when using TDD compared to ad-hoc unit testing. TDD can also reduce the cost of debugging software by finding code defects earlier and can contribute to better software design. In this paper, we present our ongoing work on an approach that uses generative AI to generate unit tests to facilitate test-driven development. Given a high-level goal, the approach generates formalized requirements in the form of a goal model, which is then used to generate unit tests in a test folder. We describe a current prototype implementation and show initial results for example high-level goals provided by our industrial partner.
+- ### Attachments
+ - [PDF](zotero://select/library/items/IU5ZGYX4) {{zotero-imported-file IU5ZGYX4, "Yao et al. - Generation of Unit Tests for Test-Driven Development using Large Language Models.pdf"}}
+- ### Notes
+ - # I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (30/7/2025, 12:06:11)
+
+ - “Test-Driven Development (TDD) is a process that has been shown to reduce software defects yet is not always adopted in industrial software.” (Yao et al., p. 1) #5fb236
+
+ - “50% reduction in defect density when using TDD compared to ad-hoc unit testing.” (Yao et al., p. 1) #5fb236
+
+ - “cost of debugging software by finding code defects earlier and can contribute to better software design.” (Yao et al., p. 1) #5fb236
+
+ - “ongoing work on an approach that uses generative AI to generate unit tests to facilitate test-driven development” (Yao et al., p. 1) #e56eee
+
+ - “goal model,” (Yao et al., p. 1) #a28ae5
+
+ - “which is then used to generate unit tests in a test folder.” (Yao et al., p. 1) #a28ae5
+
+ - “During Test-Driven Development (TDD), developers start by creating a failing test that matches the given goals for the implementation.” (Yao et al., p. 1) #e56eee
+
+ - “When the implementation code is written, developers write the minimum amount of code to pass the unit tests written in the previous step.” (Yao et al., p. 1) #e56eee
+
+ - “Unit tests are a form of software testing that evaluates individual components or functions in isolation to ensure their correctness.” (Yao et al., p. 1) #5fb236
+
+ - “unit tests are often written after the implementation code, using TDD can be more effective in reducing software defects.” (Yao et al., p. 1) #5fb236
+
+ - “However, despite its benefits, a small subset of developers choose to not write tests [2].” (Yao et al., p. 1) #5fb236
+
+ - “Using Large Language Models (LLMs) to generate unit tests offers an approach that may be less time consuming for developers.” (Yao et al., p. 1) #5fb236
+
+ - “use of LLMs for the generation of unit tests from user-given goals to facilitate TDD.” (Yao et al., p. 1) #5fb236
+
+ - “ongoing work on an approach and prototype for the generation of unit tests for TDD.” (Yao et al., p. 1) #a28ae5
+
+ - “many diverse user-given goals, but the development of our prototype was heavily focused on generating unit tests for the network domain” (Yao et al., p. 1) #a28ae5
+
+ - “We did not conduct an extensive evaluation, instead relying on manual checks and feedback from our industry partner.” (Yao et al., p. 1) #ffd400
+ *This is ok for a workshop paper.*
+
+ - “II. UNIT TESTS IN TEST-DRIVEN DEVELOPMENT” (Yao et al., p. 1) #5fb236
+
+ - “During Test-Driven development (TDD), unit tests are created based on requirements for new functionality before any implementation code is written” (Yao et al., p. 1) #5fb236
+
+ - “Red-Green-Refactor: developers write a few failing unit tests (red), then write implementation code to pass the test cases (green) and refactor the code, making sure all the tests still pass (refactor).” (Yao et al., p. 1) #5fb236
+
+ - “Unit tests are added incrementally as new features are added, and all previous unit tests must pass as new unit tests and implementation code are added.” (Yao et al., p. 1) #a28ae5
+
+ - “Moreover, unit tests in TDD can also help reveal issues with the requirements.” (Yao et al., p. 1) #5fb236
+
+ - “The purpose of writing unit tests is to be able to isolate a unit and verify its correctness.” (Yao et al., p. 1) #a28ae5
+
+ - “R1: Given input that identifies the high-level goal g that the user is planning to write implementation code for, the approach and prototype implementation should for any goal g: a) refine the high-level goal g into a set of sub-goals and b) generate unit tests of sufficient quality for goal g using the refined requirements. R2: The approach should represent the requirements in a way that generates good quality unit tests. R3: The approach should work for arbitrary user goals g.” (Yao et al., p. 2) #ffd400
+ *Section 5 that presents the approach is not effective in explaining how these steps work. In particular, it is not clear how the human involvement is managed, how the iterative nature of the process is supported, how human feedback is considered by the subsequent steps of the test driven process.*
+
+ - “Most recent work on test generation uses the implementation code as input. For instance, Amazon Q developer [6] and GitHub Copilot [7] provide a chatbot that allows users to generate unit tests with appropriate mocks for specified methods,” (Yao et al., p. 2) #a28ae5
+
+ - “TESTPILOT, which used the function signature as well as other available information such as documentation and usage examples to generate unit tests with GAI” (Yao et al., p. 2) #5fb236
+
+ - “A previous study found correctness issues in some unit tests generated by ChatGPT but finds that the correct tests are of comparable quality to tests written by developers [3]” (Yao et al., p. 2) #5fb236
+
+ - “Our approach differs from these works as it does not use the implementation code as input and can be used to support TDD.” (Yao et al., p. 2) #5fb236
+
+ - “The MAPE-K loop mechanism has been used to assist in LLM-based goal model generation by continuously adding goals during the loops.” (Yao et al., p. 2) #5fb236
+
+ - “process assigns different roles to the LLM, allowing it to act as different domain experts when performing different tasks within the MAPE-K loop” (Yao et al., p. 2) #5fb236
+
+ - “This also showed promising results, but included steps that required human decision making” (Yao et al., p. 2) #5fb236
+
+ - “GAI has been used as a collaborative tool for developers during TDD showing promising results but requiring developer supervision.” (Yao et al., p. 2) #5fb236
+
+ - “Many techniques are used to try and improve the quality of LLM-generated answer” (Yao et al., p. 2) #5fb236
+
+ - “Our approach is novel, as it allows for few-shot examples of unit tests to be given in our unit test generation step that are aligned with the basic actions selected in the generated goal models.” (Yao et al., p. 2) #e56eee
+
+ - “Our industrial partner tasked us with creating a tool that generates unit tests from user-defined goals.” (Yao et al., p. 2) #5fb236
+
+ - “Generating a goal model skeleton” (Yao et al., p. 2) #2ea8e5
+
+ - “filling in the values in the goal model skeleton using GenAI” (Yao et al., p. 2) #2ea8e5
+
+ - “unit test generation” (Yao et al., p. 2) #2ea8e5
+
+ - “1) Pool of Basic Actions” (Yao et al., p. 2) #2ea8e5
+
+ - “Fig. 1: Algorithm for generating unit tests” (Yao et al., p. 3) #ffd400
+ *I'm not sure this algorithm as presented in the paper is effective in the presentation. I would find an alternative way to present the process that in the end consists of three main steps.*
+
+ - “Fig. 2: Snippet of the pool of basic actions used to build our goal models” (Yao et al., p. 3) #ffd400
+ *Who defines them? Are they domain/application specific?*
+
+ - “It contains two template variables: a goal g representing the user-defined goal” (Yao et al., p. 3) #ffd400
+ *Are goal models written in a specific syntax/format?*
+
+ - “3) Querying the LLM: Next, the LLM is queried using the goal model skeleton prompt and few shot examples to generate a goal model skeleton (line 2 in Figure 1).” (Yao et al., p. 3) #ffd400
+ *This is not clear. The LLM is queried with a goal model skeleton prompt to generate a goal model skeleton. Different parts of the paper are affected by presentation issues that reduce the readability of the work. It is not clear what is general and what is application specific that is valid only for the application at hand and made working with ad-hoc steps.*
+
+ - “validate, get, return” (Yao et al., p. 3) #5fb236
+
+ - “C. Unit Test Generation 1) Few Shot Examples: The list of chosen basic actions generated in the previous step will be used to select example unit tests to aid in unit test generation (line 9 of Figure 1). Each basic action in our pool has a corresponding set of example requirements and unit tests. We tried to include at least two few-shot examples of requirement and unit test pairs for each basic action in our pool. Figure 7 is a snippet of a few-shot example for the ’lookup’ basic action (Jinja2 statements are shown in blue).” (Yao et al., p. 4) #ffd400
+ *This step is not clear neither. First of all it is necessary to clarify that the work is Python specific. Then, it is not clear how unit tests for the basic actions can be "composed" to generate unit tests that are specific for the application at hand. Moreover, what's the granularity of the wanted unit tests?*
+
+ - “However, it struggled with more complex examples and on examples where the high-level goals were less well defined.” (Yao et al., p. 5) #ffd400
+ *This is not surprising to me. I'm really missing in the approach a clear specification of the granularity of the unit tests, what they are supposed to test, etc.*
+
+ - “Our approach takes a high-level goal, refines it into a goal model constructed using a pool of basic actions, and generates unit tests based on the subgoals in the goal model” (Yao et al., p. 5) #5fb236
+
+ - “Despite the mixed results, our approach is novel as it is able to provide few-shot examples of relevant unit tests for many different high-level goals.” (Yao et al., p. 5) #5fb236
+
+ - “Chain-of-thought prompting could be used to attempt to improve the LLMs reasoning capability.” (Yao et al., p. 5) #5fb236
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows: SUMMARY: Just a few sentence to summarize the work COMMENTS: Organize the notes especially those that contain issues or typos. Please do not make an extrause of bullet points. Make the comments fluent without being too verbose
+
+ ######
\ No newline at end of file
diff --git a/pages/@Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices%3A a Technology Acceptance Study.md b/pages/@Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices%3A a Technology Acceptance Study.md
new file mode 100644
index 00000000..c8a370b9
--- /dev/null
+++ b/pages/@Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices%3A a Technology Acceptance Study.md
@@ -0,0 +1,109 @@
+tags:: [[#zotero]]
+date:: 2018
+title:: @Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices: a Technology Acceptance Study
+item-type:: [[journalArticle]]
+original-title:: Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices: a Technology Acceptance Study
+language:: en
+authors:: [[Giuliano M Bonazzi]], [[Jacopo Ammendola]], [[Eduardo M Guerra]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/C3JFD69L), [Web library](https://www.zotero.org/users/1039502/items/C3JFD69L)
+
+- [[Abstract]]
+ - Different from other products, in which the user knows about their energy consumption and can make more sustainable options, in web applications, the user has no control or information regarding how it could be more sustainable. For instance, a specific user might not need the information in a given panel or might choose a lower update rate for a chart or table. To fill this gap, this work aims to propose a graphical user interface model to promote digital sustainability in web applications. The model, named LEAFS, was constructed based on a literature review on digital sustainability, technology acceptance models, and persuasive design theories. An interactive prototype of the model applied in a fictional web application from the finance sector was developed using Figma. In this paper, we present a technology acceptance study with potential users to validate the model, using a structured instrument based on UTAUT 2. The results revealed a good acceptance from the users regarding the possibility of configuring a web application to more sustainable options, and also pointed to some improvement points to be considered before its implementation. As a consequence, this work evaluates an original idea that considers user choices in the implementation of web applications’ sustainability, creating a new dimension to reduce energy consumption.
+- ### Attachments
+ - [PDF](https://icse2026-greens.hotcrp.com/doc/icse2026-greens-paper28.pdf) {{zotero-imported-file 2F7LTX29, "Bonazzi et al. - 2018 - Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices a Techno.pdf"}}
+- ### Notes
+ - # Annotazioni
+ (23/11/2025, 19:15:42)
+
+ “in web applications, the user has no control or information regarding how it could be more sustainable.” (Bonazzi et al., 2018, p. 1)
+
+ “graphical user interface model to promote digital sustainability in web applications.” (Bonazzi et al., 2018, p. 1)
+
+ “In this paper, we present a technology acceptance study with potential users to validate the model, using a structured instrument based on UTAUT 2.” (Bonazzi et al., 2018, p. 1)
+
+ “As a consequence, this work evaluates an original idea that considers user choices in the implementation of web applications’ sustainability, creating a new dimension to reduce energy consumption.” (Bonazzi et al., 2018, p. 1) How is it possible to validate the resulting energy consumption is consistent with the user choices/requirements?
+
+ “The declaration sheds light on the growing negative externalities of digital habits on the environment while also pointing out that digital innovations can enable systemic effects in reducing greenhouse gas emissions [17].” (Bonazzi et al., 2018, p. 1)
+
+ “Green IT” (Bonazzi et al., 2018, p. 1)
+
+ “Although the area has been constantly evolving, a significant body of literature focuses on rethinking software engineering processes and hardware energy efficiency, with emerging but still limited attention to the role of software usage and feature customization by end-users.” (Bonazzi et al., 2018, p. 1)
+
+ “Users naturally have different perceptions, purposes, and skills while using an interface that cannot be fully anticipated.” (Bonazzi et al., 2018, p. 1)
+
+ “enabling more advanced customization options for users to change the behavior of an application would represent a viable strategy to promote sustainability by configuring feature functionality and rearranging interface and functional components.” (Bonazzi et al., 2018, p. 1)
+
+ “propose and evaluate the user acceptance of a pluggable graphical interface model aiming to empower website end users to customize web applications in order to reduce their environmental impact while also enhancing understanding of configurable options and promoting environmental awareness through educational content.” (Bonazzi et al., 2018, p. 1)
+
+ “component that could be plugged into any site with minimal configuration and adjustments to reach a broader public and thus, greater impact.” (Bonazzi et al., 2018, p. 1)
+
+ “Figma” (Bonazzi et al., 2018, p. 1) Figma: The Collaborative Interface Design Tool
+
+ Put a footnote
+
+ “UTAUT 2” (Bonazzi et al., 2018, p. 2) what's that? Please add a reference
+
+ “Based on the answers, we performed a quantitative analysis of the closed-ended question and a qualitative analysis of the open-ended questions.” (Bonazzi et al., 2018, p. 2)
+
+ “Performance Expectancy, Effort Expectancy, and Learning Value.” (Bonazzi et al., 2018, p. 2)
+
+ “difficulties in associating environmental metrics with real-world adherence.” (Bonazzi et al., 2018, p. 2) Yes, that's an important point (see one of my comments above).
+
+ “green software and persuasive interfaces” (Bonazzi et al., 2018, p. 2)
+
+ “proposed graphical interface model;” (Bonazzi et al., 2018, p. 2)
+
+ “research method for the technology acceptance study” (Bonazzi et al., 2018, p. 2)
+
+ “results and findings of the study” (Bonazzi et al., 2018, p. 2)
+
+ “how to measure software energy efficiency” (Bonazzi et al., 2018, p. 2)
+
+ “field is still immature.” (Bonazzi et al., 2018, p. 2)
+
+ “consumes more energy than a system without it.” (Bonazzi et al., 2018, p. 2)
+
+ “reducing energy consumption by allowing users to customize the software based on their usage profile, aiming to reduce the waste generated by unnecessary features.” (Bonazzi et al., 2018, p. 2) That's an interesting proposal. Of course, I see several limitations in its actual implementation, but still it can be interesting!
+
+ “Without their awareness of how to use such resources in a sustainable manner, there will be a significant waste of resources in the usage of such applications.” (Bonazzi et al., 2018, p. 2)
+
+ “The interface proposed in this work has as its main vision to stimulate users’ digital environmental impact awareness and sustainable actions through the mediation of functional and engaging interactions.” (Bonazzi et al., 2018, p. 2)
+
+ “ons. The interface model concept advocates for universal applicability in the web context to achieve influence over the reduction of digital environmental impacts. In this sense, it intends to be flexible enough to provide various implementation alternatives or a strategy framework for developing customization features internally as a means to foster wide adoption by website owners and IT specialists.” (Bonazzi et al., 2018, p. 2) Already said. Sometimes the paper is repetitive.
+
+ “two distinct entities” (Bonazzi et al., 2018, p. 3)
+
+ “fictional website representing a potential model use case” (Bonazzi et al., 2018, p. 3)
+
+ “materialization of the model into an actionable interface” (Bonazzi et al., 2018, p. 3)
+
+ “The impact visualization translates individual results into graphical, real-world metaphors to strengthen their significance” (Bonazzi et al., 2018, p. 3)
+
+ “The last two screens relate to the possibility of alternating between the available profile options and the profile details screen, and to the advanced customization of website features.” (Bonazzi et al., 2018, p. 3) Is this always possible for any web application? I have some doubts about this. How to define profiles? How to check their correctness? (removing some elements of the page, can have some ripple effects with those that instead are intended to be shown).
+
+ “investigate how different factors can influence the intention to use the model by end users as a means to prove its validity and relevance.” (Bonazzi et al., 2018, p. 3)
+
+ “brief presentation video introducing the model and prototype was embedded before the UTAUT2 dimensions section in the questionnaire.” (Bonazzi et al., 2018, p. 3)
+
+ “eight dimensions for acceptance evaluation: Behavioral Intention, Performance Expectancy, Effort Expectancy, Social Influence, Facilitating Conditions, Hedonic Motivation, Learning Value, and Habit and Experience.” (Bonazzi et al., 2018, p. 4)
+
+ “we recreated the video, changing not its content but its format, to make it more interesting to the viewers.” (Bonazzi et al., 2018, p. 4)
+
+ “inductive coding approach.” (Bonazzi et al., 2018, p. 4)
+
+ “The second phase and third phase represented consecutive refinements of both the prototype and its presentation video, carried out in response to feedback gathered in each preceding phase.” (Bonazzi et al., 2018, p. 4)
+
+ “This combination suggests a sample that is both highly educated and mature, factors that may influence their engagement, digital abilities, and professional experience.” (Bonazzi et al., 2018, p. 4)
+
+ “This paper proposed an approach to empower the users of web applications to make configurations that can reduce energy consumption. We created a user interface prototype using Figma and evaluated its acceptance through a technology acceptance study based on UTAUT2.” (Bonazzi et al., 2018, p. 8) I'm wondering to what extent this can be really made general for any kinds of application.
+
+ “showing that this is a promising path for energy saving that can be pursued in the future.” (Bonazzi et al., 2018, p. 8)
+
+ “o the best of our knowledge, no previous work in the literature has explored the participation of users in choices to avoid energy waste before, so the contribution of this work opens a new dimension that can be explored in the implementation of more sustainable web applications.” (Bonazzi et al., 2018, p. 8)
+
+ “. Additionally, some participants expressed uncertainty about the real-world significance of the environmental metrics displayed.” (Bonazzi et al., 2018, p. 8) Exactly, I agree!
+
+ “pluggable web component and integrated into existing web applications to evaluate the required effort for its implementation.” (Bonazzi et al., 2018, p. 8)
+
+ “an experiment with a real application can provide more information regarding user adoption and the potential for energy savings.” (Bonazzi et al., 2018, p. 8)
\ No newline at end of file
diff --git a/pages/@Incarichi di ricerca.md b/pages/@Incarichi di ricerca.md
new file mode 100644
index 00000000..73209390
--- /dev/null
+++ b/pages/@Incarichi di ricerca.md
@@ -0,0 +1,10 @@
+tags:: [[#zotero]]
+title:: @Incarichi di ricerca
+item-type:: [[webpage]]
+access-date:: 2025-11-18T07:32:02Z
+original-title:: Incarichi di ricerca
+url:: https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=205&item=file
+links:: [Local library](zotero://select/library/items/H6XB4AE2), [Web library](https://www.zotero.org/users/1039502/items/H6XB4AE2)
+
+- ### Attachments
+ - [PDF](https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=205&item=file) {{zotero-imported-file 7ZTPLJQC, "blob.php.pdf"}}
\ No newline at end of file
diff --git a/pages/@Incarichi post-doc.md b/pages/@Incarichi post-doc.md
new file mode 100644
index 00000000..72abb595
--- /dev/null
+++ b/pages/@Incarichi post-doc.md
@@ -0,0 +1,10 @@
+tags:: [[#zotero]]
+title:: @Incarichi post-doc
+item-type:: [[webpage]]
+access-date:: 2025-11-18T07:30:48Z
+original-title:: Incarichi post-doc
+url:: https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=203&item=file
+links:: [Local library](zotero://select/library/items/4T5MDQIA), [Web library](https://www.zotero.org/users/1039502/items/4T5MDQIA)
+
+- ### Attachments
+ - [PDF](https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=203&item=file) {{zotero-imported-file 3NYMMVBB, "blob.php.pdf"}}
\ No newline at end of file
diff --git a/pages/@LLM-assisted configuration of model-driven business process families.md b/pages/@LLM-assisted configuration of model-driven business process families.md
new file mode 100644
index 00000000..15a62a8d
--- /dev/null
+++ b/pages/@LLM-assisted configuration of model-driven business process families.md
@@ -0,0 +1,108 @@
+tags:: [[#zotero]]
+title:: @LLM-assisted configuration of model-driven business process families
+item-type:: [[journalArticle]]
+original-title:: LLM-assisted configuration of model-driven business process families
+language:: en
+authors:: [[Daniel Calegari]], [[Andrea Delgado]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/9T42DIJ7), [Web library](https://www.zotero.org/users/1039502/items/9T42DIJ7)
+
+- [[Abstract]]
+ - Business processes often include variations driven by specific business requirements, leading to the concept of a business process family. The management of such families can be streamlined using the Model-Driven Engineering (MDE) approach, which involves defining metamodels to express the process family and applying transformations to support the required management activities, such as the configuration process of a specific process variant. The vast range of potential variants within a BPF introduces several challenges, including the need for mechanisms to assist users in configuring specific process variants. In this article, we explore how an MDE-based business process family management approach could be combined with Large Language Models (LLMs) to define questionnaires that support the configuration of process variants. Although the results are promising and in line with previous findings on the use of LLMs for MDE, several aspects must be considered to bring their application to a reliable industrial environment.
+- ### Attachments
+ - [PDF](zotero://select/library/items/9ZEW774P) {{zotero-imported-file 9ZEW774P, "Calegari e Delgado - LLM-assisted configuration of model-driven business process families.pdf"}}
+- ### Notes
+ - # I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (30/7/2025, 14:43:25)
+
+ - “model-driven business process families” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “specific business requirements, leading to the concept of a business process family” (Calegari general-and Delgado, p. 1) #a28ae5
+
+ - “In this article, we explore how an MDE-based business process family management approach could be combined with Large Language Models (LLMs) to define questionnaires that support the configuration of process variants.” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “This process is configurable, meaning that some elements are variable, and a configuration process must be carried out to derive a process variant.” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “It requires using techniques such as questionnaires [9] to guide users in developing a configuration, which can then be used to generate the variants automatically.” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “This article explores the integration of LLMs within an MDE-based proposal for managing BP families.” (Calegari general-and Delgado, p. 1) #e56eee
+
+ - “The LLM would assist in developing questionnaires for end-users based on the information contained in the BP family model.” (Calegari general-and Delgado, p. 1) #e56eee
+
+ - “These questionnaires are connected to the many configuration options of the BP family.” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “Once a questionnaire is answered, a model transformation utilizes this configuration to generate a specific process instance.” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “Questionnaires are based on an existing proposal from [9], but have been technologically updated and adapted to the MDE-based approach defined in [3].” (Calegari general-and Delgado, p. 1) #ffd400
+ *It is necessary to expand this statement with more details.*
+
+ - “BUSINESS PROCESS FAMILIES MANAGEMENT” (Calegari general-and Delgado, p. 1) #5fb236
+
+ - “a metamodel conceptualizing key elements for BP families” (Calegari general-and Delgado, p. 1) #2ea8e5
+
+ - “a high-level management process supported by the Business Process Family Manager (BPFM) tool” (Calegari general-and Delgado, p. 1) #2ea8e5
+
+ - “Business Process Family Manager (BPFM) tool [12].” (Calegari general-and Delgado, p. 1) #ffd400
+ *The last commit to the tool seems to be done 4 years ago.*
+
+ - “A business process family (BPFamily) groups multiple process variants (ProcessVariant) that share a common base process (BaseProcess) while allowing variations (VariationPoint) on activities, routing nodes, or process fragments. These variation points determine where different variants (Variant) can be applied based on the context (Context), which defines context requirements (ContextRequirement) for variant selection. A specific process variant is derived by defining a configuration (Configuration) that satisfies these requirements.” (Calegari general-and Delgado, p. 2) #ffd400
+ *To make the proposal more convincing and less abstract it is important to give earlier in the paper some illustrative examples of variants related to business process families. Can you make some explanatory examples?*
+
+ - “Figure 1: BP families metamodel (from [3])” (Calegari general-and Delgado, p. 2) #ffd400
+ *The metamodel come from paper [3], another paper from the authors. It is important to stress the novelties of this paper in comparison with what was presented in [3]*
+
+ - “The BPFM tool supports this process by allowing the management of variability approaches that can co-exist within the tool in a homogenized way” (Calegari general-and Delgado, p. 2) #5fb236
+
+ - “Within this approach, BP family languages and configurations must be expressed using metamodels to generate variants using model-to-model transformations, leveraging user-defined configurations.” (Calegari general-and Delgado, p. 2) #5fb236
+
+ - “In [9], the authors propose an approach to capture system variability based on questionnaire models.” (Calegari general-and Delgado, p. 2) #5fb236
+
+ - “The approach depicts variability independently of specific languages through facts representing the space of possible answers to a set of questions.” (Calegari general-and Delgado, p. 2) #5fb236
+
+ - “Questions and facts can be connected through precedence or order dependencies, and facts may have domain” (Calegari general-and Delgado, p. 2) #ffd400
+ *It is important to give some examples of questions to make the presentation concrete and help the reader to grasp the message.*
+
+ - “The configuration process is captured through a series of actions.” (Calegari general-and Delgado, p. 2) #5fb236
+
+ - “C-EPC” (Calegari general-and Delgado, p. 2) #ffd400
+
+ - “The tool not only allows the selection of the most pertinent questions based on the current state of the configuration, but also makes use of a logical expression manipulation application to verify in real-time that the answers comply with the domain constraints, avoiding inconsistent or invalid configurations.” (Calegari general-and Delgado, p. 3) #5fb236
+
+ - “Additionally, its automatic variant generation process is tied to a specific language for BP family modeling” (Calegari general-and Delgado, p. 3) #5fb236
+
+ - “QML for questionnaires” (Calegari general-and Delgado, p. 3) #2ea8e5
+
+ - “DCL for specifying configurations.” (Calegari general-and Delgado, p. 3) #ffd400
+ *What are the configurations that are needed? Can you explain what's the usge of the elements given in the DCL metamodel in Fig. 4.b?*
+
+ - “LLM-ASSISTED GENERATION OF QUESTIONNAIRES” (Calegari general-and Delgado, p. 3) #5fb236
+
+ - “LLM uses it to derive a questionnaire model that conforms to the QML metamodel depicted in Figure 4a.” (Calegari general-and Delgado, p. 3) #5fb236
+
+ - “The prompt is composed of three parts, as detailed in Table I:” (Calegari general-and Delgado, p. 3) #ffd400
+ *I would include illustrative examples for each of the three parts.*
+
+ - “Task Description. A” (Calegari general-and Delgado, p. 3) #2ea8e5
+
+ - “Input Requirements.” (Calegari general-and Delgado, p. 4) #2ea8e5
+
+ - “Output Requirements.” (Calegari general-and Delgado, p. 4) #2ea8e5
+
+ - “(A) to assess the degree to which the LLM could resolve the problem using a zero-shot strategy, without any feedback loop;” (Calegari general-and Delgado, p. 4) #2ea8e5
+
+ - “(B) to compare the results with those of other available LLM solutions and their reasoning capabilities;” (Calegari general-and Delgado, p. 4) #2ea8e5
+
+ - “(C) to determine whether it is possible to improve the results based on a conversational interaction with the LLM, closer to the usual way of working in a real environment with domain experts.” (Calegari general-and Delgado, p. 4) #2ea8e5
+
+ - “A. Zero-shot experiment” (Calegari general-and Delgado, p. 4) #ffd400
+ *This section is verbose and is missing some concrete examples. It's difficult to follow without them.*
+
+ - “Metrics are based on a semantic equivalence between questions, facts, and dependencies of the ground-truth model and the derived ones.” (Calegari general-and Delgado, p. 5) #ffd400
+ *How was the semantic equivalence assessed?*
+
+ - “It presents a method where LLMs assist in generating useroriented questionnaires that support the configuration of process variants based on a metamodel-driven framework.” (Calegari general-and Delgado, p. 10) #ffd400
+ *How are these configurations "consumed"?*
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows: SUMMARY: Just a few sentence to summarize the work COMMENTS: Organize the notes especially those that contain issues or typos. Please do not make an extrause of bullet points. Make the comments fluent without being too verbose
\ No newline at end of file
diff --git a/pages/@Modeling AI-Driven Workflows for Ecosystem Resilience Prediction.md b/pages/@Modeling AI-Driven Workflows for Ecosystem Resilience Prediction.md
new file mode 100644
index 00000000..69567581
--- /dev/null
+++ b/pages/@Modeling AI-Driven Workflows for Ecosystem Resilience Prediction.md
@@ -0,0 +1,439 @@
+tags:: [[#zotero]]
+title:: @Modeling AI-Driven Workflows for Ecosystem Resilience Prediction
+item-type:: [[journalArticle]]
+original-title:: Modeling AI-Driven Workflows for Ecosystem Resilience Prediction
+language:: en
+authors:: [[Tiago Sousa]], [[Nicolas Guelfi]], [[Benoit Ries]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/IWLHMQSC), [Web library](https://www.zotero.org/users/1039502/items/IWLHMQSC)
+
+- [[Abstract]]
+ - Engineering AI-driven workflows to predict ecosystem resilience is increasingly important for responding to rapid environmental change. As climate variability intensifies, leveraging artificial intelligence to support ecological decision-making has become a common approach. However, prevailing approaches to engineering these prediction systems are often ad-hoc and difficult to reproduce, lacking a systematic methodology to ensure coherence between ecological requirements, data, and AI engineered components. To address this gap, this paper introduces a model-driven engineering methodology to support the systematic development of Ecosystem Resilience Prediction Systems (ERPS). We propose an adaptive workflow that formalizes our development process, based on two core metamodels: EcoSys, for structuring the ecological problem domain by defining its measurable properties as resilience indicators, and PredSys, for defining the AI and dataset solution domains. This approach ensures that AI architectures and datasets are co-designed to predict these properties, formally linking them to ecological requirements. The workflow’s flexible design accommodates goal-driven, datadriven, and model-driven entry points. We demonstrate the methodology’s applicability by retrospectively modeling two realworld case studies from the literature: one on forest carbon stock estimation and another on coastal fisheries management.
+- ### Attachments
+ - [PDF](zotero://select/library/items/Y4XBT2Y6) {{zotero-imported-file Y4XBT2Y6, "Sousa et al. - Modeling AI-Driven Workflows for Ecosystem Resilience Prediction.pdf"}}
+- ### Notes
+ - # Annotations
+ (29/7/2025, 15:12:27)
+
+ - “AI-Driven Workflows for Ecosystem Resilience Prediction” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “As climate variability intensifies, leveraging artificial intelligence to support ecological decision-making has become a common approach” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “model-driven engineering methodology to support the systematic development of Ecosystem Resilience Prediction Systems (ERPS).” (Sousa et al., p. 1) #ffd400
+ *What do you mean with ecosystem resilience? *
+
+
+
+ - “This approach ensures that AI architectures and datasets are co-designed to predict these properties, formally linking them to ecological requirements.” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “one on forest carbon stock estimation” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “nother on coastal fisheries management.” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “ecosystem resilience” (Sousa et al., p. 1) #ffd400
+ *natural ecosystems? what? you need to define it early in the paper. *
+
+
+
+ - “While modern ecological monitoring generates vast and heterogeneous datasets from automated sensors and large-scale data acquisition [3], applying advanced AI to this data is essential to enabling the repeatable ecosystem assessments needed to track environmental shifts and inform policy” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “despite the potential of AI, the primary engineering barrier is the overall workflow rather than individual models.” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “This absence of systematic and reproducible workflows slows scientific progress and the development of scalable solutions” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “Ecosystem Resilience Prediction Systems (ERPS)” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “The methodology is founded on two core, formally defined metamodels that structure the problem and solution domains.” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “Ecosystem metamodel (EcoSys” (Sousa et al., p. 1) #2ea8e5
+ * *
+
+
+
+ - “Prediction System metamodel (PredSys)” (Sousa et al., p. 1) #2ea8e5
+ * *
+
+
+
+ - “AI architectures (PredSys-AI) and dataset characteristics (PredSys-Dataset)” (Sousa et al., p. 1) #2ea8e5
+ * *
+
+
+
+ - “workflow that accommodates goal-driven, data-driven, and model-driven design processes” (Sousa et al., p. 1) #2ea8e5
+ * *
+
+
+
+ - “modeling of bidirectional links between ecosystem requirements, data constraints, and AI capabilities” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “coherent” (Sousa et al., p. 1) #ffd400
+ *what do you mean? Data constraints on what? *
+
+
+
+ - “ecosystem science and prediction systems engineering” (Sousa et al., p. 1) #5fb236
+ * *
+
+
+
+ - “A central problem in modern ecosystem science is the transition from creating isolated models to engineering integrated, end-to-end workflows.” (Sousa et al., p. 2) #ffd400
+ *It is necessary to give some explanatory examples early in the paper just to clearly state what's the focus/context of the work. *
+
+
+
+ - “A major concern is ensuring that as AI becomes more powerful, systems remain transparent, accountable, and subject to expert oversight.” (Sousa et al., p. 2) #a28ae5
+ * *
+
+
+
+ - “While this highlevel, strategic perspective calls for a formal, human-driven design process, it does not prescribe a concrete methodology for achieving it, which is a primary motivation for our work.” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “Another key challenge is the automation and standardization of the data-to-model lifecycle.” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “They highlight the need for automation but do not provide a formal design methodology to specify what these automated pipelines should do and why.” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “This gap is further evidenced by the proliferation of specific, applicationoriented workflows, for instance, for monitoring nocturnal insects [12], managing coastal fisheries [13], and assessing algal blooms [14].” (Sousa et al., p. 2) #ffd400
+ *Only at this point you understand that the paper is about natural ecosystems. *
+
+
+
+ - “prediction system” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “This allows for precise structural descriptions but offers less support for specifying the model’s requirements or expected behavior” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “De la Vega et al. [18] present a DSL to automate the transformation of structured data into a format suitable for prediction systems.” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “a posteriori documentation of existing datasets” (Sousa et al., p. 2) #5fb236
+ * *
+
+
+
+ - “few provide the level of detail and guidance needed to model the specific activities, roles, and dependencies involved in engineering prediction systems.” (Sousa et al., p. 2) #a28ae5
+ * *
+
+
+
+ - “tool concept that provides step-by-step support for explicitly modeling ML application integration in BPMN business processes.” (Sousa et al., p. 2) #a28ae5
+ * *
+
+
+
+ - “a DSL to model AI engineering processes, covering the needs for such processes as described in academic and industry proposals” (Sousa et al., p. 2) #e56eee
+ * *
+
+
+
+ - “DSL for modeling ML engineering processes, including activities, their orchestration, roles, resources, and artifacts.” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “Although comprehensive, their approach remains primarily descriptive, supporting the documentation and execution of workflows but lacking mechanisms to enforce consistency between the generated artifacts through verifiable means.” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “In contrast to prior work, we emphasize the formal alignment between problem specification and model design, the derivation of AI and dataset requirements from domain-level concerns, and a prescriptive process model that enforces consistency across artifacts.” (Sousa et al., p. 3) #e56eee
+ * *
+
+
+
+ - “AIdriven workflows for ecosystem resilience prediction.” (Sousa et al., p. 3) #a28ae5
+ * *
+
+
+
+ - “Ecosystem metamodel (EcoSys)” (Sousa et al., p. 3) #2ea8e5
+ * *
+
+
+
+ - “Prediction System metamodel (PredSys)” (Sousa et al., p. 3) #2ea8e5
+ * *
+
+
+
+ - “AI models and datasets.” (Sousa et al., p. 3) #2ea8e5
+ * *
+
+
+
+ - “adaptive model-driven workflow.” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “The section concludes with three detailed scenarios that showcase the adaptability of our approach in real-world contexts.” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “A. Metamodeling Requirements, Data, and AI Components” (Sousa et al., p. 3) #2ea8e5
+ * *
+
+
+
+ - “ERPS” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “Ecosystem metamodel (EcoSys)” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “Prediction System metamodel (PredSys)” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “1) Ecosystem metamodel (EcoSys)” (Sousa et al., p. 3) #2ea8e5
+ * *
+
+
+
+ - “Our ecosystem metamodel (EcoSys), inspired by the DREF framework [5], adapts foundational resilience concepts from software engineering to natural ecosystems (see Figure 1).” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “s :” (Sousa et al., p. 3) #ff6666
+ * *
+
+
+
+ - “Evolution axes define how these entities or the ecosystem health change over an ordered dimension (e.g. time).” (Sousa et al., p. 3) #5fb236
+ * *
+
+
+
+ - “resilience patterns” (Sousa et al., p. 3) #ffd400
+ *you need to give some examples. What do you want predict? *
+
+
+
+ - “2) Prediction System metamodel - AI part” (Sousa et al., p. 4) #2ea8e5
+ * *
+
+
+
+ - “Furthermore, since neural networks contain multiple components in its structure, either in a linear or non-linear order, we define clEdge and clOrdering classes to allow precise specification over the network’s structure composition.” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “This model is associated with a clArchitecture of a recurrent neural network composed of multiple clLayer instances, which are represented as clStructuralComponent elements.” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “The structural composition is further detailed using clEdge and clOrdering to capture the sequential or non-linear arrangement of components.” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “numerical prediction (e.g., surface area in hectares).” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “We define the training of the model with a clTrainingProcess, which relies on a clLossFunction (e.g., mean squared error) to guide optimization, and a clOptimizer (e.g., Adam) to update model parameters.” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “clHyperParameter” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “3) Prediction System metamodel - Dataset part:” (Sousa et al., p. 4) #2ea8e5
+ * *
+
+
+
+ - “Moreover, as data typically requires preprocessing and transformation before being used directly with neural networks, we support the definition of such transformations. Additionally, given that ecosystem data can be very limited for specific tasks, we also support generative transformations for data augmentation purposes.” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “annual surface area observations.” (Sousa et al., p. 4) #5fb236
+ * *
+
+
+
+ - “from high-level goals to a fully specified and generated software product.” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “Intent task” (Sousa et al., p. 5) #a28ae5
+ * *
+
+
+
+ - “Assisted Intent Recognition” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “Observer Elicitation” (Sousa et al., p. 5) #2ea8e5
+ * *
+
+
+
+ - “EcoSys model” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “This model serves as the semantic foundation that informs and constrains all subsequent decisions in the workflow.” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “Acquire and Prepare Data:” (Sousa et al., p. 5) #2ea8e5
+ * *
+
+
+
+ - “validating them against the requirements” (Sousa et al., p. 5) #ffd400
+ *How are data validated against the requirements given in the EcoSys models? *
+
+
+
+ - “Select and Configure AI” (Sousa et al., p. 5) #2ea8e5
+ * *
+
+
+
+ - “To support users who may not have their own datasets or AI models, the workflow is designed to be generic, modular, and interoperable. It may interface with external registries that provide curated and validated artifacts, such as model hubs or open data portals, enabling the integration of existing resources into the design process, even when user-specific artifacts are unavailable. The workflow triggers final system generation once all validated artifacts are available in a shared System State Context (SSC).” (Sousa et al., p. 5) #ffd400
+ *It is necessary to clarify how this model will be used. Is there any running environment to execute the specified models? Are there any code generation steps? Who is the main user of the proposed approach? What are the roles that are involved in the show process? How are they intended to collaborate? *
+
+
+
+ - “This structured approach prevents design mismatches, such as collecting incompatible data or selecting an unsuitable neural network model, by explicitly modeling dependencies between components.” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “Predict the yearly evolution of vegetation surface in Mersch Forest.” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “The ERPS metamodels (EcoSys and PredSys) are interdependent and their consistency must be managed all over the workflow.” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “This explicit representation prevents critical mismatches, such as defining prediction goals that remain unsupported even after preprocessing and augmentation, or selecting AI architectures misaligned with the data’s structure or semantics.” (Sousa et al., p. 5) #5fb236
+ * *
+
+
+
+ - “ResilForest” (Sousa et al., p. 7) #2ea8e5
+ * *
+
+
+
+ - “model introduces vegetation dryness as a key property.” (Sousa et al., p. 7) #5fb236
+ * *
+
+
+
+ - “ffective methodologies should support diverse modeling approaches, enabling not only goal-driven design but also data-driven and technologydriven exploration.” (Sousa et al., p. 7) #5fb236
+ * *
+
+
+
+ - “The workflow is designed to adapt and guide the user from their intent to a complete and consistent ERPS specification” (Sousa et al., p. 7) #5fb236
+ * *
+
+
+
+ - “Observer Elicitation” (Sousa et al., p. 7) #5fb236
+ * *
+
+
+
+ - “Model-Driven” (Sousa et al., p. 8) #ffd400
+ * *
+
+
+
+ - “”What kind of ecosystem resilience properties can I predict with this model?”” (Sousa et al., p. 8) #5fb236
+ * *
+
+
+
+ - “The Classify intent task within the Assisted Intent Recognition pool would classify the intent as to start the Select and Configure AI pool and the workflow execution would be:” (Sousa et al., p. 8) #ffd400
+ *I understand, this needs to be abstract being a workshop paper. However, the paper stays disconnected with the real execution environments and technologies. It is not clear how the presented models and processes are actually used in practice further than the given abstract specifications. *
+
+
+
+ - “2) Prediction System Modeling (PredSys)” (Sousa et al., p. 8) #ffd400
+ *Where are the features of interests are specified? Where the prediction goals are given? *
+
+
+
+ - “By structuring domain knowledge within the EcoSys metamodel, it provides a direct pathway for developing testable and robust predictive systems from established ecological principles.” (Sousa et al., p. 9) #a28ae5
+ *That's interesting and I can agree with this. *
+
+
+
+ - “from highlevel requirements to a fully specified system.” (Sousa et al., p. 10) #ffd400
+ *I'm missing the link with the realy system that will execute what you have specified with the proposed approach. *
\ No newline at end of file
diff --git a/pages/@Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs.md b/pages/@Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs.md
new file mode 100644
index 00000000..6921a2c6
--- /dev/null
+++ b/pages/@Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs.md
@@ -0,0 +1,13 @@
+tags:: [[#zotero]]
+date:: 2018
+title:: @Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs
+item-type:: [[journalArticle]]
+original-title:: Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs
+language:: en
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/5P5PNFFW), [Web library](https://www.zotero.org/users/1039502/items/5P5PNFFW)
+
+- [[Abstract]]
+ - Recently, the emergence of Large Language Models (LLMs) has spurred a surge of research into automated unit test generation, demonstrating impressive performance and reducing manual effort. However, existing LLM-based approaches still suffer from two major limitations: (1) they rely on rule-based context extraction, which fails to capture fine-grained code dependencies, limiting LLMs’ ability to understand program semantics and derive test requirements; (2) they follow rigid, procedural workflows that underutilize the autonomous reasoning potential of LLMs, making it difficult to dynamically adapt testing strategies based on real-time feedback. In this paper, we propose TestAgent, an LLM-based test generation approach that addresses the above limitations by emulating the human testing practice via a multi-agent collaboration mechanism. Particularly, TestAgent designs three specialized agents, i.e., requirement planner, test generator, and test reviewer, to simulate how developers understand, construct, and validate unit tests. Moreover, to unleash the autonomous capabilities of LLMs, we equip TestAgent with a set of tool APIs that can be invoked dynamically by LLMs in an on-demand and adaptive manner. Furthermore, to support repository-level context retrieval and reasoning, TestAgent integrates a repository-aware knowledge graph that provides a structured representation of large-scale codebases and captures fine-grained dependency relations through graph edges. Experimental results show that TestAgent achieves 97.46% execution rate, 92.34% line coverage, 90.24% branch coverage, and 83.69% mutation score on six Java projects, significantly outperforming search-based and LLM-based baselines. We also adapt TestAgent Python projects with 88.85% line coverage and 78.89% branch coverage, demonstrating its generalizability beyond the Java ecosystem. Moreover, the results on three industrial projects and a controlled user study demonstrate the practical applicability and usability of TestAgent in real-world development scenarios.
+- ### Attachments
+ - [PDF](zotero://select/library/items/L3AMMAVS) {{zotero-imported-file L3AMMAVS, "2018 - Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Gr.pdf"}}
\ No newline at end of file
diff --git a/pages/@Recommending Relevant Classes for Infrequent API Classes.md b/pages/@Recommending Relevant Classes for Infrequent API Classes.md
new file mode 100644
index 00000000..02430f97
--- /dev/null
+++ b/pages/@Recommending Relevant Classes for Infrequent API Classes.md
@@ -0,0 +1,275 @@
+tags:: [[#zotero]]
+date:: 2026
+title:: @Recommending Relevant Classes for Infrequent API Classes
+item-type:: [[journalArticle]]
+original-title:: Recommending Relevant Classes for Infrequent API Classes
+language:: en
+authors:: [[Anonymous Author]]
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/9I4Q6XAZ), [Web library](https://www.zotero.org/users/1039502/items/9I4Q6XAZ)
+
+- [[Abstract]]
+ - Although libraries (e.g., J2SE) provide many reusable Application Programming Interfaces (APIs) and are widely used, calling an API class often implements only simple functionalities. As there are many API classes, it is challenging to identify relevant API classes for a given API class. For frequent API classes, various mining approaches, code search engines, and LLMs can help. However, more than 80% of API classes are infrequently called in real projects. The problem is inherent and relevant. If code samples are unavailable or too few, existing approaches are ineffective.
+- ### Attachments
+ - [PDF](zotero://select/library/items/7PARQGX2) {{zotero-imported-file 7PARQGX2, "Author - 2026 - Recommending Relevant Classes for Infrequent API Classes.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (17/09/2025, 11:44:16)
+
+ - “Although libraries (e.g., J2SE) provide many reusable Application Programming Interfaces (APIs) and are widely used, calling an API class often implements only simple functionalities.” (Author, 2026, p. 1) #5fb236
+
+ - “As there are many API classes, it is challenging to identify relevant API classes for a given API class.” (Author, 2026, p. 1) #ffd400
+ *Bad written. Not clear.*
+
+ - “However, more than 80% of API classes are infrequently called in real projects.” (Author, 2026, p. 1) #e56eee
+
+ - “If code samples are unavailable or too few, existing approaches are ineffective.” (Author, 2026, p. 1) #e56eee
+ *We are referring bias issues here.*
+
+ - “APIrel, can predict relevant classes, even if such patterns do not appear in documents or source files.” (Author, 2026, p. 1) #a28ae5
+
+ - “APIrel uses mined patterns as seeds and compares API documents to build labeled data.” (Author, 2026, p. 1) #ffd400
+ *What is mined? When?*
+
+ - “Based on labeled data, APIrel then builds a model by observing the documents of API classes with and without patterns” (Author, 2026, p. 1) #a28ae5
+
+ - “Given the documents of two API classes, our trained model can predict whether they are relevant.” (Author, 2026, p. 1) #ffd400
+ *For what? What kind of documents are given as input?*
+
+ - “As introduced in Section 7,” (Author, 2026, p. 1) #ffd400
+ *It's a too far forward reference.*
+
+ - “inferring from documents” (Author, 2026, p. 1) #2ea8e5
+
+ - “mining from clients.” (Author, 2026, p. 1) #2ea8e5
+
+ - “As specifications define the rules of calling APIs, it is feasible to identify relevant API classes from mined specifications. However, both research lines have inherent limitations” (Author, 2026, p. 1) #ffd400
+
+ - “s.F” (Author, 2026, p. 1) #ff6666
+
+ - “a templates” (Author, 2026, p. 1) #ff6666
+
+ - “For instance, API documents rarely mention relevant API classes, especially when such classes are infrequent.” (Author, 2026, p. 1) #ffd400
+ *Sentences like this require some examples, they are not clear!!*
+
+ - “As a result, the prior approaches are unlikely to infer many relevant infrequent API classes from documents. The limitation is inherent.” (Author, 2026, p. 1) #ffd400
+ *Can you show some explanatory example?*
+
+ - “For instance, researchers use Apriori algorithms to mine the relevant libraries.” (Author, 2026, p. 1) #ffd400
+ *This is not clear.*
+
+ - “They report that only LibSeek [31] can recommend relevant infrequent libraries, but its effectiveness is unsatisfactory. In particular, its precision and recall are only 21.1% and 69.4% in the best scenario, and they drop to 3.1% and 0.9% in the worst scenario.” (Author, 2026, p. 1) #5fb236
+
+ - “95% of API classes are called by less than 10% of clients,” (Author, 2026, p. 1) #a28ae5
+
+ - “hiding 88% of API classes do not affect 75% of clients.” (Author, 2026, p. 1) #a28ae5
+
+ - “As most API classes are infrequent, existing approaches can work for only a small set of frequent API classes.” (Author, 2026, p. 1) #e56eee
+
+ - “APIrel. It is the first approach that infers relevant classes from documents without predefined templates.” (Author, 2026, p. 1) #ffd400
+ *What kind of documents? We are almost at the end of the introduction and this is not clear.*
+
+ - “Although most API classes are infrequent, it is feasible to mine some specifications from clients. We use them as the seeds to infer more rules. Although documents seldom explicitly define rules, e.g., relevant classes, API documentations provide documents for most APIs” (Author, 2026, p. 1) #ffd400
+ *What kind of rules are referring to?*
+
+ - “In our new direction, we mine seen API patterns from source files and use such patterns to label data” (Author, 2026, p. 1) #ffd400
+ *Why is this different from existing approaches?*
+
+ - “predicted relevant API class” (Author, 2026, p. 2) #ffd400
+ *How is the prediction done? What does the prediction, when?*
+
+ - “API” (Author, 2026, p. 2) #ffd400
+
+ - “can train a model to predict unseen patterns based on a small portion of frequent API classes” (Author, 2026, p. 2) #ffd400
+ *This is obscure!*
+
+ - “Given the documents of two API classes, the trained model predicts whether they are relevant.” (Author, 2026, p. 2) #ffd400
+ *For what?*
+
+ - “popular API classes, we conduct a tenfold cross-validation. In each fold, the training set provides API documents and the labels to train a model, and the testing set feeds API documents to the trained model. As the trained model takes only API documents as its input, it works for new API classes without any samples. The f-score values of our prediction vary from 70% to 80%.” (Author, 2026, p. 2) #ffd400
+ *Not clear!*
+
+ - “https://anonymous.4open.science/r/apirel.” (Author, 2026, p. 2) #ffd400
+ *Tried to visit the link but the following message is obtained while trying to access the content:
+ "The requested file is not found."*
+
+ - “2 ILLUSTRATING EXAMPLE” (Author, 2026, p. 2) #ffd400
+ *The paper should be improved by clearly distinguishing the presentation of the problem to be solved and the proposed solution. These are mixed in many parts of the paper, which is not effective in presenting the problem and the limitations of existing approaches. Unfortunately, the motivation part of the paper relies on some examples based on the SearchCode system, which seems is no longer active and online.*
+
+ - “the document of HSSFWorkbook.” (Author, 2026, p. 2) #ffd400
+ *The document?*
+
+ - “From the clients” (Author, 2026, p. 2) #ffd400
+ *What's the client you are referring to?*
+
+ - “HSSFSheet is frequently called with HSSFWorkbook.” (Author, 2026, p. 2) #ffd400
+ *How can you see that from Fig. 1?*
+
+ - ““See Also” titles often ignore many relevant APIs, since it takes too much effort to manually write all of them.” (Author, 2026, p. 2) #5fb236
+
+ - “Many mined relevant classes are not defined in documents” (Author, 2026, p. 2) #a28ae5
+
+ - “Using these instances as its training data, APIrel builds a classification model that can predict unseen API patterns.” (Author, 2026, p. 2) #5fb236
+
+ - “prior approaches” (Author, 2026, p. 2) #ffd400
+ *which one?*
+
+ - “As a comparison, the prior approaches can mine relevant classes only for frequent APIs. In Section 4, we split the labeled instances into ten groups. In each fold, we use nine groups to train our model, and use the remaining group to test our model. We switch the testing group, and test our model for all possible labels. The results show that APIrel achieves around 70% f-score values even if it infers from only documents. APIrel can infe” (Author, 2026, p. 2) #ffd400
+ *This is something related to the evaluation. WHy mentioning here at section 2 of the paper when the details of the approach are not given yet?*
+
+ - “it infers that HSSFBorderFormatting and HSSFWorkbook are relevant” (Author, 2026, p. 2) #ffd400
+ *with respect to what? How relevance is assessed?
+ How is relevance defined?*
+
+ - “SearchCode” (Author, 2026, p. 2) #ffd400
+ *No longer available.*
+
+ - “Although the two API classes are relevant, the prior approaches are unlikely to infer this pattern since its code samples are too few.” (Author, 2026, p. 2) #ffd400
+
+ - “It is infeasible for the prior approaches to mine patterns from only one observation.” (Author, 2026, p. 2) #5fb236
+
+ - “Table 3 s” (Author, 2026, p. 2) #ffd400
+ *It should be Table 1*
+
+ - “To handle the problem, from each code sample of a library, our tool extracts all its called API classes and methods, and removes samples whose called classes or methods are not declared by the latest versions.” (Author, 2026, p. 2) #ffd400
+ *When it extracts? What does it mean?*
+
+ - “A small set of API classes are intensively called by most clients, while most API classes are used by less than 10% of clients. Based on the findings, a learning-based approach can work for only a few critical frequent APIs.” (Author, 2026, p. 3) #5fb236
+
+ - “However, if we use the mined patterns as labels, we can train models that work for many more APIs” (Author, 2026, p. 3) #ffd400
+ *This is not clear!*
+
+ - “Definition 1. The relevant API classes of an API class are classes that can be called together to implement functionalities.” (Author, 2026, p. 3) #ffd400
+ *What does it mean "called together"? What does it mean call a class?*
+
+ - “As infrequent APIs have documents, it is feasible to infer relevant classes for infrequent APIs.” (Author, 2026, p. 3) #ffd400
+ *What does it mean that infrequent APIs have documents? Also the second part of the sentence is not clear to me.*
+
+ - “To infer hidden patterns, we reduce the inference of infrequent relevant API classes into a classification problem. For example, taking the documents of two classes (d1 and d2) as inputs, a solution to our problem is to train a model, f (d1, d2) ⇝ l, that predicts whether d1 and d2 are relevant. After paired API classes are predicted, they can be merged into larger sets” (Author, 2026, p. 3) #ffd400
+ *Paragraphs like this require some explanatory example. It's not clear what do you want to do in practice here.*
+
+ - “As API documents seldom mention relevant classes, it is quite challenging to construct the labels from documents.” (Author, 2026, p. 3) #ffd400
+
+ - “To handle the problem, we use mined patterns as the gold standard, and propose a new research direction that infers unknown knowledge from known knowledge.” (Author, 2026, p. 3) #ffd400
+ *mmmmmm can you give some examples? This is very vague!*
+
+ - “, our tool uses its full name to build the query.” (Author, 2026, p. 3) #ffd400
+ *"Our tool" which tool, when is the query created? How is the tool supposed to be installed/used/....
+
+ The paper requires a serious revision to improve the presentation and the writing in general.*
+
+ - “PPA [19] is a library for analyzing partial code, and we build APIrel on PPA. After the trees are built, APIrel traverses them to collect the called API classes of each method. Our tool collects the full list of API classes for each library. For each method, APIrel extracts its directly dependent API classes (e.g., API classes in cast expressions), and its indirectly dependent API classes (e.g., resolving the types of variables). APIrel merges the two sets of classes to build the used API classes of a method.” (Author, 2026, p. 3) #ffd400
+ *I think some parts of the paper can be reduced to gain some space to be used for presenting some examples to explain technical sentences like these ones.*
+
+ - “Table 2: Our features” (Author, 2026, p. 4) #ffd400
+ *It should be moved to sec 3.*
+
+ - “A transaction database, T DB, is a set of transactions. Given a transaction database T DB, the support of an itemset X , denoted as sup (X ), is the number of transactions in T DB that contain X . An itemset X is a closed itemset, if there exists no itemset X ′ such that (1) X ′ is a proper superset of X , and (2) if a transaction contains X , it also contains X ′.” (Author, 2026, p. 4) #ffd400
+ *Example is needed otherwise this is unreadable.*
+
+ - “itemset contains the API classes that are frequently called in a method.” (Author, 2026, p. 4) #e56eee
+
+ - “APIrel mines that CellStyle, HSSFSheet, and HSSFWorkbook are frequently called in a method. Many API classes are less popular and do not appear in collected source files. As Yen et al. [70] mine frequent itemsets, their approach cannot mine unseen relevant API classes, and their mined API patterns cover only a small set of API classes.” (Author, 2026, p. 4) #ffd400
+ *OK, I can start from this. The rest is still obscure to me. I hope the next sections clarify.*
+
+ - “comparing mined API patterns with API documents (Section 3.3.1), and trains a classification model” (Author, 2026, p. 4) #5fb236
+
+ - “3.3.1 Extracting positive and negative instances” (Author, 2026, p. 4) #2ea8e5
+
+ - “Line 1 builds a dictionary from mined patterns. This dictionary contains all the API classes that appear in SET .” (Author, 2026, p. 4) #ffd400
+ *Can you make some concrete examples by referring to the running motivating example?*
+
+ - “Line 6 checks whether the c1 and c2 classes appear in our dictionary. If one of them does not appear in the dictionary, we conclude that their patterns cannot be observed from the mined API patterns.” (Author, 2026, p. 4) #ffd400
+ *This step requires more elaboration by referring to the motivating example shown in Figure 1.*
+
+ - “Feature 1. The number of overlapped verbs and nouns in class descriptions.” (Author, 2026, p. 4) #2ea8e5
+
+ - “Feature 2. The frequencies of class names.” (Author, 2026, p. 4) #2ea8e5
+
+ - “Feature 3. The distance between two classes in their super types.” (Author, 2026, p. 4) #2ea8e5
+
+ - “Feature 4. The number of overlapped interfaces.” (Author, 2026, p. 4) #2ea8e5
+
+ - “Feature 5. The number of overlapped subclasses.” (Author, 2026, p. 4) #2ea8e5
+
+ - “Feature 6. The number of overlapped references.” (Author, 2026, p. 4) #2ea8e5
+
+ - “Feature 7. The number of fields whose type is the other class.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 8. The links of method parameters.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 9. The number of methods whose return type is the other class.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 10. The frequencies of the other class name in a method description.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 11. The frequencies of the other class name in the thrown exceptions from the methods of a class.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 12. The number of methods that refer to the other class.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 13. The number of methods that are specified in the other class.” (Author, 2026, p. 5) #2ea8e5
+
+ - “Feature 14. The links of constructor parameters.” (Author, 2026, p. 5) #2ea8e5
+
+ - “4 EVALUATION ON CORRECTNESS This section explores the he following RQs: (RQ1) How accurate are our approach (Section 4.3)? (RQ2) What are the key features (Section 4.4)? (RQ3) What is the impact of labels (Section 4.5)?” (Author, 2026, p. 6) #ffd400
+ *The main problem that I had so far with the previous section is about presentation. The paper is not effective in presenting the problems and the solution. Many sentences are unclear and I had to go through them to try catching the meaning or the technical details that should be made explicit by referring for instance to a running example.
+
+ Let's see if the Evaluation improves the situation.....*
+
+ - “API documents in Table 3” (Author, 2026, p. 6) #ffd400
+ *This is not clear. Table 3 list the same labries listed in table 4 and does not include API documents.*
+
+ - “All the libraries are shipped with their API documents.” (Author, 2026, p. 6) #5fb236
+
+ - “The repository of SearchCode has millions of projects. By default, SearchCode retrieves 100 samples per page. Each sample is a source file that calls the queried API. For some popular API classes, it retrieves thousands of pages. As it is impractical to download all samples, we limit the analysis scope of our tool to the top 20 pages, i.e., the top 2,000 samples per API class.” (Author, 2026, p. 6) #ffd400
+ *What's the role of SeachCode in this paragraph*
+
+ - “4.2 No Baseline Statement” (Author, 2026, p. 6) #ffd400
+ *This seems to be an appendix of the related work section, why not merging this with the related work section and move after the introduction by extending with some motivating examples clearly presenting all the different concepts and motivating the paper?*
+
+ - “As introduced in Section 7,” (Author, 2026, p. 6) #ffd400
+ *Since it is referred many times in previous sections, why not moving section 7 after the introduction section.*
+
+ - “The first line of approaches analyzes documents with templates. As documents rarely mention relevant classes, these approaches may not infer many relevant classes. We do not compare with them since the improvement is explicit. The second line of approaches mines relevant classes from clients.” (Author, 2026, p. 6) #ffd400
+ *The distinction between document analysis and clients should make more clear by means of some explanatory examples.*
+
+ - “The accuracy” (Author, 2026, p. 7) #ffd400
+ *it's not clear what this accuracy is about. Is it on the capability of the approach of detecting relevant classes? I think human in the loop should be considered.*
+
+ - “Predicting more complicated infrequent API patterns” (Author, 2026, p. 9) #5fb236
+
+ - “To improve the completeness of API patterns, in this paper, we propose a new direction for inferring infrequent API patterns.” (Author, 2026, p. 10) #5fb236
+
+ - “Our basic idea is to learn a model from API documents and already mined frequent patterns. Mimicking how programmers infer from documents, we proposed APIrel to infer relevant API classes for long-tail and new APIs.” (Author, 2026, p. 10) #5fb236
+
+ - “We evaluated APIrel on five popular libraries. Our results show that our predicted unseen relevant classes are reasonably accurate (fscores around 80%). Based on our positive results, our new direction has the potential to be extended for predicting more complicated API patterns.” (Author, 2026, p. 10) #ffd400
+ *I think it is necessary to revise the evaluation by involving developers!*
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ STRENGHTS:
+
+ WEAKNESSES:
+
+ COMMENTS: Organize the notes with respect to the following criteria:
+
+ -
+ `Novelty`
+
+ -
+ `Rigor`
+
+ -
+ `Relevance (of the contribution)`
+
+ -
+ `Verifiability and Transparency`
+
+ -
+ `Presentation`
+
+ And then add a Detailed Comments section to report the notes that contain issues or typos.
+ Can you also formulate three explicit questions by considering the comments above?
\ No newline at end of file
diff --git a/pages/@SRC-Retrieval%3A Semantic-Based GitHub Repository and Code Retrieval.md b/pages/@SRC-Retrieval%3A Semantic-Based GitHub Repository and Code Retrieval.md
new file mode 100644
index 00000000..b9721cfb
--- /dev/null
+++ b/pages/@SRC-Retrieval%3A Semantic-Based GitHub Repository and Code Retrieval.md
@@ -0,0 +1,243 @@
+tags:: [[#zotero]]
+title:: @SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval
+item-type:: [[document]]
+original-title:: SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval
+links:: [Local library](zotero://select/library/items/NH39F2BD), [Web library](https://www.zotero.org/users/1039502/items/NH39F2BD)
+
+- ### Attachments
+ - [PDF](zotero://select/library/items/MWXK9CXR) {{zotero-imported-file MWXK9CXR, "icse2026-paper3125.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (16/09/2025, 16:05:09)
+
+ - “Semantic-Based” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #5fb236
+
+ - “existing search methods on GitHub and general search engines like Bing often fail to capture the semantic intent behind developers' queries, so the retrieved repositories may not satisfy developers’ requirements.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #a28ae5
+
+ - “Moreover, the search results of current methods are at the repository level rather than at the level of individual code ;iles, making it challenging for beginners to locate speci;ic code implementations.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #ffd400
+ *Do you actually need to do so via existing search engines like Bing when we have the availability of advanced technologies like ChatGPT and Copilot?*
+
+ - “high-level functional requirements and concrete code implementations.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #a28ae5
+
+ - “A transformer-based retrieval model leverages text embeddings to recommend not only relevant repositories but also speci;ic code ;iles aligned with the user’s intended functionalities” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #5fb236
+
+ - “A common use case involves searching for repositories that implement specific functionalities, such as “user authentication” or “data visualization”, to serve as references for their own software projects.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #5fb236
+
+ - “GitHub’s search mainly relies on keyword matching, which often fails to capture the semantic intent behind developers’ queries.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #5fb236
+
+ - “While general-purpose search engines offer alternative solutions [1], they also typically lack a nuanced understanding of the semantic relationship between queries and repositories, often returning broad and imprecise results.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #e56eee
+
+ - “As a result, even when developers find a relevant repository, locating the exact code snippets they need can be difficult, especially for those who are new to programming.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #ffd400
+
+ - “we propose SRC-Retrieval, a GitHub repository and code retrieval method that semantically aligns developers’ functional requirements with relevant repositories and specific code files.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #ffd400
+ *Intersting to see later, what do the author mean with semantic alignment and the corresponding granularity.*
+
+ - “Text embeddings are leveraged to represent both user queries and repositories, as they effectively capture contextual and semantic information and have been widely applied in various tasks such as semantic search, question answering, and document classification” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 1) #a28ae5
+
+ - “code search is an important research topic in software engineering.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #5fb236
+
+ - “Large Language Models (LLMs) may generate code containing hallucinations, which can mislead beginners lacking the expertise to assess correctness. Based on these considerations and supported by our experimental results, we adopt transformer-based encoders for embedding generation.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #a28ae5
+ *This is a good point!*
+
+ - “Unlike existing tools that primarily recommend repositories, our approach identifies specific code files within repositories that directly implement the queried functionality, providing beginners with coding references.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #a28ae5
+
+ - “We propose a semantic retrieval method that aligns user queries with repository functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #ffd400
+ *"repository functionality" is a good point, even though tricky to mange and sustain. I guess it is based on README information, isn't it?
+
+ Let's go ahead with the reading and let's see.*
+
+ - “BERT-based model to link functional requirements to specific code files” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #ffd400
+ *How functional requirements are defined? Are they automatically created from README files? What else? Who create such links?*
+
+ - “To the best of our knowledge, this is the first approach to semantically match user requirement to both repositories and source code files, providing practical references for software development” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #ffd400
+ *I think so, even though the created of the training data is crucial here! Not clear yet how the dataset has been created.*
+
+ - “Experimental results of 3 tasks demonstrate that our method consistently outperforms the baseline methods in metrics such as precision, recall, MRR and repository and code success rate.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #5fb236
+
+ - “open-source software repository retrieval and recommendation” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #2ea8e5
+
+ - “API recommendation” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #2ea8e5
+
+ - “requirementto-code traceability link recovery” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #2ea8e5
+
+ - “their” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 2) #ff6666
+ *the*
+
+ - “While API recommendation provides more fine-grained assistance than repository-level retrieval or recommendation, developers searching for references on implementing specific functionalities often require concrete code examples to understand how these functionalities are implemented in practice.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #ffd400
+ *These two options are not exclusive. API recommendation is still valid even when developers have found a reference GitHub repository.*
+
+ - “This paper solves this problem by proposing a method for recommending specific code files that directly demonstrate the implementations of desired functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #ffd400
+ *See my previous comment. I would smooth this point.*
+
+ - “a technique that automatically refines coarsegrained requirement-to-class traces into method-level links.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #5fb236
+
+ - “On GitHub, issues often contain valuable descriptions of desired functionalities, effectively serving as high-level requirements that developers aim to implement. As such, they are well-suited for application of traceability link recovery techniques.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #5fb236
+
+ - “While existing methods like BTLink and PromptLink focus on linking issues to commits, they fall short of establishing direct connections between issues and the corresponding code files” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #5fb236
+
+ - “In this paper, we propose a novel model that extends existing methods by identifying issues that represent specific functionalities and mapping them directly to relevant code files.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #a28ae5
+
+ - “Then, functionalities are extracted from the README files and issues of the repositories” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #5fb236
+
+ - “Figure 1: The architecture of the GitHub repository and code retrieval method” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 3) #ffd400
+ *The link creation between Issue and code is more intuitive than that between readme and code. The latter seems to be more coarse grained. Not enought details are available to link specific parts of the code base with a functionality description that should be in the readme file.*
+
+ - “collect all other repositories starred by that user.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #ffd400
+
+ - “their starred repositories are likely related to software development as well.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #ffd400
+ *what kind of relation do you expect? What do you want to do with such a relation?*
+
+ - “we apply a filtering criterion that remains only repositories with at least 150 stars. This results in a refined dataset comprising over 180,000 repositories.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #5fb236
+
+ - “we identify and select 40,133 repositories tagged with the top 50 most frequently used topics, ensuring that our dataset reflects both emerging trends and well-established areas within the software development ecosystem.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #5fb236
+
+ - “In this section, we present our approach to extracting functionalities from GitHub repositories.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #5fb236
+
+ - “identify feature request entries,” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #ffd400
+ *So, you considered only closed issues. But in some cases it can be that the issues is closed not because the functionality has been actually implemented, but because it is no longer interesting to implement, or something similar.*
+
+ - “3.2.1 Functionalities in README Files.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #2ea8e5
+
+ - “repository descriptions inherently reflect a repository’s functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #a28ae5
+
+ - “Therefore, we use repository descriptions to identify functionalities in README files.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #ffd400
+ *This step is not clear at all!*
+
+ - “For negative samples, we randomly select sentences from README files that do not match any predefined requirement patterns.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 4) #ffd400
+ *This is also unclear!*
+
+ - “s[” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #ff6666
+ *missing space*
+
+ - “improve the accuracy of functionality extraction from README files, by capturing the semantic relationships between the text and the repository’s intended functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #ffd400
+ *Since readme files and repository descriptions play a key role in the model training phase, does it make sense to impose come constraints on the length or structure of README files and/or repository descriptions?*
+
+ - “After training, the classifier is applied to the candidate sentences, resulting in the extraction of 570,978 functionalities from README files.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #ffd400
+ *To make things clear, it would be great to have a representative example of README file and corresponding text with the retrieved functionalities. Currently such a mapping is vague.*
+
+ - “3.2.2 Functionalities in Issues.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #2ea8e5
+
+ - “2. A feature request issue must be marked as “closed” with the status “completed”. On GitHub, when closing an issue, collaborators can categorize it as “completed”, “not planned” or “duplicate”, with “close as completed” being the default option. In contrast, an open issue indicates that the feature hasn’t yet been implemented in the repository.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #5fb236
+
+ - “In some cases, although an issue may not be explicitly linked to a commit, contributors may confirm that the feature has been accepted by the issue’s comments.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #ffd400
+ *how frequent is this case. How many of this case have you managed during the data preparation phase?*
+
+ - “To automate this verification process, we train a classifier to assess whether a feature request issue has been accepted, based on the comments provided by the contributors. This classifier helps ensure that only genuinely accepted and implemented feature requests are considered as functionalities of the repository.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 5) #ffd400
+ *does it introduce some bias in the data creation phase? I'm not sure about this automation step.*
+
+ - “We fine-tune a BERT-based classifier on this dataset, enabling the model to learn to distinguish between accepted and rejected feature requests.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #5fb236
+
+ - “After training, the classifier is applied to feature request issues that are marked as “closed” with the status “completed”, identifying 350,413 issues as accepted. These accepted issues, along with the 22,270 issues that are directly linked to milestones or commits, are considered as valid functionalities in the repositories. To represent these functionalities, we use the titles of the issues, as they concisely express the main functionality described in the issue.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #ffd400
+ *The creation of the dataset by means of the classifier, can introduce some noise. Have you investigated the effects of not correctly classified issues to the creation phase of the dataset?*
+
+ - “specific code files that are likely to implement those requirements.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #a28ae5
+
+ - “establish direct links between the extracted functionalities and the concrete code files within each repository, which enables developers to not only discover repositories that align with their requirements but also quickly pinpoint the precise code files that serve as useful references for their own implementations” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #5fb236
+
+ - “GitHub issues are more closely related to implementation than README files, as commits that implement features often reference the original issues requesting those features.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #ffd400
+ *It is necessary to add such a clarification early in the paper. In the previous section, README files and issues are considered similar for the sake of functionality characterization of repositories.*
+
+ - “identify connections between feature request issues and the specific code files that implement the requested functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #5fb236
+
+ - “issuecommit pairs” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #5fb236
+
+ - “To construct negative samples, we randomly select commits that do not reference any issue in the positive set.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #5fb236
+
+ - “ce 8” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #ff6666
+
+ - “the classifier is applied to identify issuecommit links within repositories.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #5fb236
+
+ - “However, a single commit may address multiple features, making it inappropriate to assume that all modified code files are relevant to the linked issue.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #e56eee
+
+ - “design a secondary classifier to determine whether a specific code file implements the feature described in a given issue.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 6) #ffd400
+ *Another classifier? Too many and their impact/contribution to the whole process is not discussed at this stage, See my previous comments on the effect of the error propagation through the whole process.*
+
+ - ““You are a data tagger who needs to read a GitHub issue describing a specific feature and a code file to decide whether the code is related to the issue, meaning the code implements (or partially implements) the feature. Use 1 for related and 0 for not” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #a28ae5
+
+ - “e resulting labeled dataset is then used to finetune a BERT-based classifier, further improving the model's ability to accurately link issues to relevant code files.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #ffd400
+ *I would improve figure 4 to make more explicit the different steps including a graphical representation of the process constructing the different datasets.*
+
+ - “source code features of a code file as the concatenation of method names, class names, variable names, and comments found within the code.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #5fb236
+
+ - “For each issue-code pair in the dataset, the issue text and the extracted source code features are concatenated, and the combined sequence is tokenized into individual tokens.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #5fb236
+
+ - “To optimize model performance, we use Cross Entropy as the loss function to train the model, with the Adam optimizer employed for optimization. The learning rate is set to 1 × 10!" to ensure stable and effective convergence. The model is based on the bert-base-uncased varian” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #ffd400
+ *This has been repeated four times. It's better to say once and refer the different steps where such an optimization has been operated.*
+
+ - “After fine-tuning, this model is applied to all issue-code pairs to identify the links between issues and the corresponding code files that implement them. This approach allows us to efficiently establish the relevant connections between issues and the code that addresses them, helping developers quickly locate the most relevant code files for specific functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #ffd400
+ *Repeated.*
+
+ - “We randomly select 1,000 README functionalities from different repositories and pair them with relevant code files from the same repository, resulting in a dataset of 48,107 functionality-code pairs.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #ffd400
+ *The granularity of README files vs functionality vs code is questionable. Not convincing at this stage.*
+
+ - “Use 1 for related and 0 for not.” The model temperature is set to zero.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #5fb236
+
+ - “dataset generated by DeepSeek is then used to fine-tune a BERT model, enhancing its ability to accurately capture the relationships between high-level README functionalities and the code that implements them.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #ffd400
+ *This is not clear. A README file can be linked to several lines of code and potentially to the entire repository. This kind of link is not clear to me.*
+
+ - “For every README functionalitycode file pair in the dataset, the README functionality and the extracted code features are concatenated and tokenized into individual tokens. Following the BERT architecture, special tokens [CLS] and [SEP] are added at the beginning and end of the token sequence, respectively. The tokenized sequence is passed through the encoding layer, and the resulting embeddings are fed into a fully connected layer followed by a sigmoid layer for classification. Cross Entropy is used as the loss function during training, and the Adam optimizer is applied to optimize the model. The learning rate is set to 1 × 10!" to ensure stable and effective convergence. The model is based on the bert-base-uncased variant from Hugging Face and is implemented using PyTorch.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #ffd400
+ *Again, this is repeated many times.*
+
+ - “To enable efficient and accurate search, we use the Software Entity Recognition (SER) model proposed by Nguyen et al. [39] to identify software entities in the extracted functionalities. Additionally, we use Sentence-BERT [40] to generate embeddings for all the functionalities.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #5fb236
+
+ - “We then match the software entities against those in the functionality dataset and calculate the cosine similarity between the query embedding and all functionality embeddings in the database” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 7) #5fb236
+
+ - “This hierarchical fusion approach ensures that the top 20 most relevant functionalities are ranked and returned.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 8) #5fb236
+
+ - “specifying their software requirements, and the tool will retrieve the top 20 related repositories, along with the corresponding code files that implement the requested functionalities for reference” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 8) #a28ae5
+
+ - “This paper presents a GitHub repository and code retrieval method that extracts functionalities from GitHub repositories, establishes links between these functionalities and the corresponding code files, and retrieves repositories and code files based on user queries” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 8) #ffd400
+ *This paragraph is not needed at this stage. You have already said what the paper is about. In any case, you are not presenting a GitHub repository in the end, isn't it?*
+
+ - “RQ1: How effective is our method in extracting functionalities from README files and issues to support the functionality extraction component of the method?” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 8) #ffd400
+ *I'm curious to see the contribution of README files in the overall process. An ablation study would help here. I'm not convinced that README files contribute in a significant manner.*
+
+ - “two baseline models for comparison.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 8) #ffd400
+ *The considered baselins are not appropriate in my opinion. Authors should compare the proposed approach with technologies like Copilot or alike.
+
+ Moreover, it's not clear how the two baselines have been applied and compared with the proposed approach.
+
+ How have you validated that the lines of code that have been retrieved starting for user requests are correctly retrieved and meet the user requirements?*
+
+ - “Keyword-Driven Hierarchical Classification of GitHub Repositories,” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 11) #5fb236
+
+ - “[3] Y. Zhang, D. Lo, P. S. Kochhar, X. Xia, Q. Li, and J. Sun, “Detecting similar repositories on GitHub,” in 2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER), Feb. 2017, pp. 13–23. doi: 10.1109/SANER.2017.7884605.” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 11) #5fb236
+
+ - “Approaching code search for python as a translation retrieval problem with dual encoders,” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 11) #ffd400
+ *This might be a related work to compare with, isn't it?*
+
+ - “Information Retrieval Approaches Applied to Requirements Trace Recovery,” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 11) #5fb236
+
+ - “TraceRefiner: An Automated Technique for Refining Coarse-Grained Requirement-toClass Traces,” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 11) #5fb236
+
+ - “Extracting Requirements Patterns from Software Repositories” (“SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval”, p. 11) #5fb236
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ STRENGHTS:
+
+ WEAKNESSES:
+
+ COMMENTS: Organize the notes with respect to the following criteria:
+
+ -
+ `Novelty`
+
+ -
+ `Rigor`
+
+ -
+ `Relevance (of the contribution)`
+
+ -
+ `Verifiability and Transparency`
+
+ -
+ `Presentation`
+
+ And then add a Detailed Comments section to report the notes that contain issues or typos.
+ Can you also formulate three explicit questions by considering the comments above?
\ No newline at end of file
diff --git a/pages/@Senate%3A Policy-Driven Change Management in Model-Based Systems Engineering.md b/pages/@Senate%3A Policy-Driven Change Management in Model-Based Systems Engineering.md
new file mode 100644
index 00000000..543bb46d
--- /dev/null
+++ b/pages/@Senate%3A Policy-Driven Change Management in Model-Based Systems Engineering.md
@@ -0,0 +1,234 @@
+tags:: [[#zotero]]
+date:: 2017
+title:: @Senate: Policy-Driven Change Management in Model-Based Systems Engineering
+item-type:: [[journalArticle]]
+original-title:: Senate: Policy-Driven Change Management in Model-Based Systems Engineering
+language:: en
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/2G6WZQPU), [Web library](https://www.zotero.org/users/1039502/items/2G6WZQPU)
+
+- [[Abstract]]
+ - Model-Based Systems Engineering uses models for designing and validating complex systems. Different models for large systems are synchronized via transformations, but current Model Management (MoM) approaches lack mechanisms to control or audit changes propagation. Managing such changes is very challenging, especially when the propagated modifications are unauthorized or rejected by downstream teams.
+- ### Attachments
+ - [PDF](zotero://select/library/items/IC97Z8ZT) {{zotero-imported-file IC97Z8ZT, "2017 - Senate Policy-Driven Change Management in Model-Based Systems Engineering.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (17/09/2025, 23:00:37)
+
+ - “current Model Management (MoM) approaches lack mechanisms to control or audit changes propagation.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #e56eee
+
+ - “Managing such changes is very challenging, especially when the propagated modifications are unauthorized or rejected by downstream teams.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #e56eee
+
+ - “This paper introduces Senate, a declarative policy framework for controlling changes propagation in Federated MoM” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “FACE-to-AADL transformations and validate it using representative scenarios such as role-based access control.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “MoM context” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “Safety-critical systems such as those in avionics, automotive applications, medical, robotics, and energy infrastructures, are becoming increasingly complex and resource-intensive to develop.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “issues introduced during earlier stages of development are often only identified during V&V, making them costly and time-consuming to resolve.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “a software mismatch between the tool versions used by different development teams caused design data transfer failure across fuselage sections, leading to wiring harnesses that were too short, which contributed to a two year delivery delay and an estimated extra cost of $6.1B 1.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #e56eee
+
+ - “? ]” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #ff6666
+ *Missing reference*
+
+ - “Model Management (MoM) techniques support global interactions across multiple models [6] and facilitate tasks such as synchronization, V&V, and system-wide analysis, enabling what is often referred to as ‘modeling in the large’. MPM thus plays a key role in enabling and structuring effective MoM techniques.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “On the systems engineering level, often systems integrators define constraints on the overall system that are dispatched to the domain engineers” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “This is a hurdle in implementation of generalized access control in collaborative modeling, which is desired but currently not well-supported by MoM and collaborative modeling environments [9].” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 1) #5fb236
+
+ - “This paper introduces Senate, a declarative policy framework for controlling change propagation that alleviates this problem and provides the foundation for change management in MoM.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #5fb236
+
+ - “All implementations of IMT are realized as a sequence of operations or edits to a model which can be recognized as deltas and reverted by applying the opposite behaviors at the target. Thus, we can separately capture the operations in the source and target models irrespective of their dissimilarities.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #5fb236
+
+ - “Integration” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #2ea8e5
+
+ - “Unification” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #2ea8e5
+
+ - “Federation” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #2ea8e5
+
+ - “Model integration approaches simplify the consistency management by requiring all the models to be built from the union language.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #5fb236
+
+ - “Such union language can be difficult to design based on the various paradigms and semantics used.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #5fb236
+
+ - “Similarly, changes in the formalism for any of the domains requires changes in the formalism and the tooling for all the models.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #a28ae5
+
+ - “Thus, integration approaches improve global operations at the cost of slow or difficult evolution of the formalism.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #a28ae5
+
+ - “Model unification reduces the drawbacks of integration by only requiring the shared information to be modeled in the pivot” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #e56eee
+
+ - “However, this comes at the complexity of maintaining the bidirectional transformations, the pivot model, and their tooling” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 2) #e56eee
+
+ - “Federated Model Management (FMoM) does not require a union or pivot language, and each language can use its tools, which can be independently developed.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #a28ae5
+
+ - “In this paper we focus on FMoM approaches due to the difficult change propagation. However, our approach can also be applied to the multi-pivot unification approaches as a case of FMoM with the pivot models being considered as ordinary models.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #ffd400
+ *Not clear yet the novelty.1*
+
+ - “The FACE metamodel explicitly describes the sub-components of the given software, namely the Portable Components (PCs) and their Platform-Specific Components (PSCs). These components contain their own threads, as well as the data format and connections for inter-component communication” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #5fb236
+
+ - “The mapping relevant to the subset of the language used for this example is shown in Fig. 1” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #5fb236
+
+ - “. The deadlines in the FACE threads can be incompatible with the AADL th” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #5fb236
+
+ - “For timing analysis of an avionics real-time system, the FACE model needs to be converted to an AADL model.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #a28ae5
+
+ - “A software team called FACEDev develops FACE compliant software S. This model is converted into an AADL model M with the communication details added by the AADLDev team, which builds two hardware platforms modeled as A and B that run the software.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #5fb236
+
+ - “Each team is made up of specialists that are allowed to make changes only on their own models.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 3) #5fb236
+
+ - “Incorrect Synchronization Operations.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #2ea8e5
+
+ - “The AADLDev team would like to prevent creation or deletion of systems in their models, unless done by an AADLDev” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #5fb236
+
+ - “Incorrect Thread Deadline in S.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #2ea8e5
+
+ - “Obfuscation and Reviews.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #2ea8e5
+
+ - “Forbidden Patterns.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #2ea8e5
+
+ - “a less constrained formalism such as ecore, where cyclical references are allowed” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #5fb236
+
+ - “Three EObjects, X , Y and Z can create cyclical references such that X references Y , Y references Z and Z references X , forming a cycle. In EMF, the ecore models can be used to generate Java code.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #5fb236
+
+ - “While such constraints could also be specified with a language such as OCL and be part of the validation of the model, instead of waiting for validation, we would like to prevent such patterns from ever being created.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “method to specify what changes are undesirable in order to provide restrictions based on role, element types, specific elements, or patterns of elements.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #ffd400
+ *There are many sync languages and tools. What's the novelty here?*
+
+ - “The propagation of an undesired change to a given model can be considered a failure. As such, we need a method that allows management of the change propagation and makes the FMoM framework robust against such failures in synchronizations.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “RQ1 How to specify policies that can specify change propagation control independent of the transformations?” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “RQ2 How to define change propagation that is robust against rejected changes?” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “RQ3 Can change policies be non-intrusive to the models and transformations used?” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “Section” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #ff6666
+
+ - “change policies and the timeline of their evaluation during change propagation.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #e56eee
+
+ - “how the decisions of change policies interact with change propagation, especially in cases where the change propagation fails.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “Domain-Specific Language (DSL) that is used to specify change policies, including the specification of its inputs and evaluation” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “The systems integrators and domain engineers can create policies in Senate to specify which changes can be directly applied to a model, which changes should stop propagating, and which changes are disallowed.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #a28ae5
+
+ - “The specification and evaluation of a policy on a model is discussed in detail in Section 5.3.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #5fb236
+
+ - “Permit Allow the change to propagate through the model.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 4) #ffd400
+ *To see how propagation is performed. I guess the Permit means apply the transformation to the target model.*
+
+ - “Halt Apply the delta to the current model but do not propagate further.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “However, in the case shown in Fig. 4 the failing node is inaccessible to the original user and thus requires involvement of the integration team for any and all issues” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “Some errors are simple and can be resolved by FACEDev team at S, such as if elements common to FACE and AADL (e.g. Threads) are modified. In this case, the responsibility to fix the error should be delegated back to the FACEDev team by propagating the failure backwards. Thus, if the change is rejected by a downstream node such as A or B, the default behavior is to consider the change to be rejected by M as well.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “If the propagation fails as shown in Fig. 4 the failure back-propagation is stopped at TMA and the change propagates normally to B. The inconsistency can later be fixed by the integration team and the AADLDev team.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “In other cases, S can be impossible to propagate correctly without external modification to M” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “In order to propagate deltas correctly, an IMT requires that the models are consistent before a change.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “However, if the source is reverted without the target, the IMT does not behave correctly.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “Thus, in order to ensure correct propagation, any reverts must be in the reverse direction of propagation and always lead to an intermediate state shown in Fig. 3.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “fine-grained conditions on the operation, changed element, the role of the user making the change, and any patterns such as cycles being found.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 5) #5fb236
+
+ - “The policies are required to be non-intrusive to the model and transformation, thus, we cannot store the access rights within the model itself.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #a28ae5
+
+ - “change policy” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #2ea8e5
+
+ - “role-related access” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #2ea8e5
+
+ - “Policy DSL” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #2ea8e5
+
+ - “Policies have three inputs: The set of deltas, the set of patterns changed, and the set of markers.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #5fb236
+
+ - “Listing 1: EBNF grammar for the Policy DSL” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #ffd400
+ *I don't think the grammar is useful here. It's better to show the language and describe its peculiar parts by means of examples.*
+
+ - “Marker Model” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #2ea8e5
+
+ - “If there are any instances with the action Update in the set cannotUpdate, then the policy is triggered to disallow the change.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #ffd400
+
+ - “Pattern Matching.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #2ea8e5
+
+ - “The PM defines the patterns using VQL, which are then used to identify the changes at the pattern level. pattern parent ( obj : EObject , parentObj : EObject ) { EObject . eContainer ( obj , parentObj ) ; } pattern findCycle ( obj : EObject ) { find parent ∗( obj , obj ) ; / / ∗ is t r a n s i t i v e closure” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #5fb236
+
+ - “Policy Evaluation” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 6) #2ea8e5
+
+ - “Thus, the $input variable is just the set of events that are sourced from this built-in pattern.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “A policy to deny all changes to System Instances except by AADLDev” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #f19837
+
+ - “AADL developers.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #f19837
+
+ - “However, to achieve the global behavior discussed in Section 5.2, the order in which the changes are propagated is important.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “an MoM approach using Senate must construct the Transformation Chain (TC) and provide it to the TC Executor” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “Transformation Chain (TC)” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #a28ae5
+
+ - “If a node does not have any next nodes to be executed due to not existing or a revert or halt, the returned decision is converted to the final result which is a boolean stating success or failure.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “The TC Executor keeps a trace of the execution of MT. When a policy in the TC returns a failure and requires rollback, each previously visited MT in the TC is undone. T” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #ffd400
+
+ - “6 VALIDATION” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #ffd400
+ *This is a very important section, which needs revision. My main concerns is about the lack of details on the granularity of deltas and consequently the granularity of the managed changes. Changes can occur at different levels including packages, classes, and structural features. It is not clear if for instance in case of only some changes of structural features are not allowed, the whole class changes are not propagated. Moreover, there are many works in the MDE community about change propagations, management of model differences, bidirectional transformations, etc. which are completely neglected and that instead should be considered and potentially considered as baseline to show the strenghts and the limitations of the proposed approach. Such limitations have been also mentioned in the short threats to validity section even though the authors have not discussed how they have mitigated them.
+
+ overall even though this is an interesting and relevant work, it requires major revision to properly present the strenghts and liitations with respect to the extensive research on collaborative modeling, model diferences, incremental model transformations, and bidireactional transformations, and change propagations of model differences.*
+
+ - “correctness of the revert handling due to failure cases, and by comparing the behavior of the Senate prototype with the control required by the scenarios in Section 3.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #ffd400
+ *Why showing the correctness of the revert handling to validate the whole approach?*
+
+ - “For ease of experimentation, the MoM framework is simulated by directly providing Senate the requisite Transformation Chain (TC) as an input.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “However, as Senate only depends on recognizing the delta within the models, we could have used any IMT tool to write the transformation. Similarly, batch transformations can be supported by replacing the incremental pattern matcher with a state-based pattern matcher.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “the Senate policy language interpreter only supports propagation control based on pattern recognition.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “failure propagation and failure handling” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “the reverts in the model must be in the reverse direction of propagation, and always stop at an intermediate state.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 7) #5fb236
+
+ - “table” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 8) #ff6666
+
+ - “we show that the final propagation is independent of the order in which the nodes are evaluated.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 8) #ffd400
+ *This is strange and needs to be further elaborated.*
+
+ - “We also show that all the states at which the propagation stops are valid intermediate states in some ordering of the evaluations.” (“Senate: Policy-Driven Change Management in Model-Based Systems Engineering”, 2017, p. 8) #5fb236
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ STRENGHTS:
+
+ WEAKNESSES:
+
+ COMMENTS: Organize the notes with respect to the following criteria:
+
+ -
+ `Novelty`
+
+ -
+ `Rigor`
+
+ -
+ `Relevance (of the contribution)`
+
+ -
+ `Verifiability and Transparency`
+
+ -
+ `Presentation`
+
+ And then add a Detailed Comments section to report the notes that contain issues or typos.
+ Can you also formulate three explicit questions by considering the comments above?
\ No newline at end of file
diff --git a/pages/@TOSEM-2025-0885.md b/pages/@TOSEM-2025-0885.md
new file mode 100644
index 00000000..b7dec573
--- /dev/null
+++ b/pages/@TOSEM-2025-0885.md
@@ -0,0 +1,179 @@
+tags:: [[#zotero]]
+title:: @TOSEM-2025-0885
+item-type:: [[webpage]]
+access-date:: 2025-11-04T21:29:58Z
+original-title:: TOSEM-2025-0885
+url:: https://mc.manuscriptcentral.com/tosem?DOWNLOAD=TRUE&PARAMS=xik_A6HrXFapMx4UPvbFpZJ9Bp5ACAjbXJdr8Tqfj7rfGcRb16MAr5sRcLvKm8uq1i5BLxiFUmZ4tUsb1gnpp7UZSr1qnv6jF4uSH4doDZxpnmVjPXPSJe6oq5tkRc58UdNCqRhqHhxfSeS2exS5FTRbqhGHMLaFJTMkkifhr7VAsSnpHEWH7XSggqbRqZxcnDjBp619F
+links:: [Local library](zotero://select/library/items/DZ4BAU9Y), [Web library](https://www.zotero.org/users/1039502/items/DZ4BAU9Y)
+
+- ### Attachments
+ - [PDF](https://mc.manuscriptcentral.com/tosem?DOWNLOAD=TRUE&PARAMS=xik_A6HrXFapMx4UPvbFpZJ9Bp5ACAjbXJdr8Tqfj7rfGcRb16MAr5sRcLvKm8uq1i5BLxiFUmZ4tUsb1gnpp7UZSr1qnv6jF4uSH4doDZxpnmVjPXPSJe6oq5tkRc58UdNCqRhqHhxfSeS2exS5FTRbqhGHMLaFJTMkkifhr7VAsSnpHEWH7XSggqbRqZxcnDjBp619F) {{zotero-imported-file Y7963XLS, "TOSEM-2025-0885.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotazioni
+ (18/11/2025, 06:59:04)
+
+ “Visual Impairments w” (“TOSEM-2025-0885”, p. 1)
+
+ “visual impairments” (“TOSEM-2025-0885”, p. 2)
+
+ “review on how MDE addresses accessibility for vision impairments.” (“TOSEM-2025-0885”, p. 2)
+
+ “30 primary studies met the inclusion criteria.” (“TOSEM-2025-0885”, p. 2)
+
+ “we report the results of a Systematic Literature Review (SLR) to identify the current state-of-the-art of addressing accessibility needs with MDE based on the concrete example of vision impairments.” (“TOSEM-2025-0885”, p. 3)
+
+ “To give an example from practice: When selecting the menu for lunch or reading a bus schedule, users with low vision or blind users have specific requirements for the technical applications used, e.g., showing larger text sizes and having more contrast for people with low vision or enabling the reading of texts with screen readers for blind users.” (“TOSEM-2025-0885”, p. 3)
+
+ “engineering of socio-technical systems” (“TOSEM-2025-0885”, p. 3)
+
+ “For people with visual impairments, inclusive GUIs facilitate equal access to information, promote independence, and social inclusion.” (“TOSEM-2025-0885”, p. 3)
+
+ “Accessibility as a non-functional requirement, however, is challenging to realize in a software system because its effects are widespread across the entire system” (“TOSEM-2025-0885”, p. 3)
+
+ “On top of MDE [24], low-code development platforms have moved MDE from research to practice, providing methods for supporting additional stakeholder groups [5, 23]. Even though” (“TOSEM-2025-0885”, p. 3)
+
+ “how is it used to improve applications for visually impaired users?” (“TOSEM-2025-0885”, p. 3)
+
+ “arch focused on visual impairments only.” (“TOSEM-2025-0885”, p. 4)
+
+ “The objective of this research is to identify those studies that address a combination of both, or more specifically, the design and implementation of software systems that address the needs of people with visual impairments using MDE methods.” (“TOSEM-2025-0885”, p. 5)
+
+ “evaluation of the capabilities of approaches to capture accessibility (visual impairment) needs,” (“TOSEM-2025-0885”, p. 6) I expect to see some precise definition of visual impairment
+
+ “advantages offered by the model-driven development of accessible software?” (“TOSEM-2025-0885”, p. 6)
+
+ “disadvantages in the context of model-driven development of accessible software?” (“TOSEM-2025-0885”, p. 6)
+
+ “Which trends exist” (“TOSEM-2025-0885”, p. 7)
+
+ “What visual impairments” (“TOSEM-2025-0885”, p. 7)
+
+ “How” (“TOSEM-2025-0885”, p. 7)
+
+ “work” (“TOSEM-2025-0885”, p. 7)
+
+ “How” (“TOSEM-2025-0885”, p. 7)
+
+ “evaluated” (“TOSEM-2025-0885”, p. 7)
+
+ “challenges” (“TOSEM-2025-0885”, p. 7)
+
+ “3.4 Study Selection Procedure” (“TOSEM-2025-0885”, p. 8)
+
+ “The search query was tested and refined with a series of pilot runs” (“TOSEM-2025-0885”, p. 8)
+
+ “Table 1. Quality Assessment (QA) scoring system” (“TOSEM-2025-0885”, p. 9) I guess such quality critiera have been defined by the authors and not inherited from other existing works. In this respect, I would spend just a dedicated paragraph to explain how they have been defined. If a structured process was followed by the authors.
+
+ “Our initial literature search was performed in February 2023 and repeated in January 2024 and we performed an additional forward snowballing in October 2025” (“TOSEM-2025-0885”, p. 9) Mmmm this is suspicious. It means that the paper has been resubmitted several time, nothing wrong. Just saying that it's probable that the paper has been subject of different revisions.
+
+ “Research into MDE approaches that address visual impairment needs started late, trends downward, and has yielded a low output to date.” (“TOSEM-2025-0885”, p. 11) Why is it important to know? The fact the interest around the topic has decreased over the year, what does it mean? Is it an indication of something? is it because the problem is difficult to be addressed with MDE technologies? is it because if completely out of scope for MDE, what else? Having only these numbers is not relevant to me. Some qualitative discussion is needed in my opinion.
+
+ “The impact in the MDE community to date is low. None of the selected studies appeared in a high ranked MDE venue. Generally low citation counts indicate that most of the studies did not create interest beyond a small community of collaborating author.” (“TOSEM-2025-0885”, p. 12) Why? Then? See my previous comment.
+
+ “bstract nature of these keywords indicates that - just like the other 24 studies - these 6 primary studies do not consider the true nature and complexities of visual impairments in detail. Finally only one study (S17) provides basic definitions for common visual impairments” (“TOSEM-2025-0885”, p. 13)
+
+ “The large majority of studies provides generic approaches improving accessibility without studying human-centric aspects of visual impairments in detail. We argue in favor of considering accessibility and in the concrete context of this SLR, visual impairments, as first-class citizens and consider them beyond the technical domain when addressing it.” (“TOSEM-2025-0885”, p. 13)
+
+ “Most primary studies consider different functional roles to represent anticipated users of their MDE-based approach, and identify beneficiaries of improved accessibility. However, they often overlook or briefly address the specific needs of these audiences, neglecting the human and social aspects of socio-technical systems. This shortcoming may hinder understanding of how effectively the tools address accessibility needs or whether they tackle real-world accessibility issues.” (“TOSEM-2025-0885”, p. 14) What's the usage of modeling techniques and tools in the MDE-based approaches that have been analyzed?
+
+ “accessibility challenges” (“TOSEM-2025-0885”, p. 15) What does it mean in practive? What do the author expect by using MDE for deising and impleenting software that mitigate visual impariment issues? it is important to clarify what is the ideal usage of MDE (if any) that authors expected to see.
+
+ “(see Figure 4),” (“TOSEM-2025-0885”, p. 15) This figure is too far, it's page 29, whereas it is referred in the text the first time at page 15.
+
+ “urprisingly, none of the DSLs modeled accessibility aspects explicitly, but rather focused on the basic structure of user interfaces.” (“TOSEM-2025-0885”, p. 19)
+
+ “these solutions are not reusable for other MDE projects as the detailed accessibility requirements, modeling requirements and adaptation rules are provided by giving some examples only.” (“TOSEM-2025-0885”, p. 20) What does it mean reusable solutions for the considered problem that is very specific to the particular case/application/context/user, isn't it?
+
+ “accessibility guidelines should be validated and tested” (“TOSEM-2025-0885”, p. 21) How? What would you exect?
+
+ “Lack of awareness and attention by developers as well as insufficient tools and methods are the most frequently used aspects to motivate research work.” (“TOSEM-2025-0885”, p. 23)
+
+ “Only one [6] of 30 studies took a human-centric approach and motivated the presented research with real-world impact for disadvantaged people.” (“TOSEM-2025-0885”, p. 23)
+
+ “Only one study directly aimed to help disadvantaged users, and just two considered the needs of visually impaired users” (“TOSEM-2025-0885”, p. 23)
+
+ “By creating high-level abstractions of software, these methods provide a comprehensive way to address accessibility requirements while reducing complexity.” (“TOSEM-2025-0885”, p. 23) This is not obvious. We might reduce the development complexity by means of MDE methods. However, the link with accessibility requirements is not direct.
+
+ “The most common are limited evaluation and scope,” (“TOSEM-2025-0885”, p. 25)
+
+ “ack of real-user testing,” (“TOSEM-2025-0885”, p. 25)
+
+ “low applicability to real-world projects.” (“TOSEM-2025-0885”, p. 25)
+
+ “(1) Introducing accessibility:” (“TOSEM-2025-0885”, p. 25)
+
+ “incorporation of accessibility features into the user interface” (“TOSEM-2025-0885”, p. 25)
+
+ “(2) Improving accessibility coverage” (“TOSEM-2025-0885”, p. 25)
+
+ “(3) Technical / maintenance challenges” (“TOSEM-2025-0885”, p. 25)
+
+ “benefits of concepts and methodologies for the model-based development of accessible applications.” (“TOSEM-2025-0885”, p. 25)
+
+ “The large majority of studies focused on open gaps and challenges from the accessibility perspective, not from the MDE perspective. We see this focus as one of the reasons why none of the primary studies were published at main MDE venues” (“TOSEM-2025-0885”, p. 26) I can understand this.
+
+ “analysis of the 30 selected primary studies reveals several shortcomings and areas where further research is needed.” (“TOSEM-2025-0885”, p. 26)
+
+ “While the reviewed studies offer valuable insights and innovative methodologies, certain limitations and ambiguities in their approaches restrict reproducibility and broader applicability to related use cases.” (“TOSEM-2025-0885”, p. 26)
+
+ “By addressing the identified issues and building on existing methodologies, future research can contribute to more robust, transparent, and generalizable solutions.” (“TOSEM-2025-0885”, p. 26) There are many sentences like this that is vague, too abstract and not to the point. Robust with respect what? Whta aspect is requiring transparency?
+
+ “diverse ßhuman” (“TOSEM-2025-0885”, p. 27)
+
+ “Limitation 2: High-level Description of Approaches. A significant number of studies (S4, S10, S15, S18, S20, S21, S28, S27)” (“TOSEM-2025-0885”, p. 27)
+
+ “Limitation 3: Generalisability and Reproducibility of Approaches.” (“TOSEM-2025-0885”, p. 27)
+
+ “Limitation 1: Measuring Achieved Accessibility.” (“TOSEM-2025-0885”, p. 27)
+
+ “Limitation 4: Evaluation with Key Target User Groups.” (“TOSEM-2025-0885”, p. 27)
+
+ “The studies often either discuss the benefits for the user (e.g. enhanced user experience) or the benefits for the developer (e.g. higher efficiency during development).” (“TOSEM-2025-0885”, p. 27)
+
+ “Limitation 5: Lack of MDE Details and Reusability.” (“TOSEM-2025-0885”, p. 27)
+
+ “Evaluate guideline coverage for vision-related needs and include visually impaired participants early in the development” (“TOSEM-2025-0885”, p. 28)
+
+ “Limitation 6: Accessibility as a Prerequisite Competence. T” (“TOSEM-2025-0885”, p. 28)
+
+ “Although the presented approaches include many automation aspects, all of them still rely highly on the developer to provide accessibility expertise” (“TOSEM-2025-0885”, p. 28)
+
+ “automation of accessibility related tasks in the development process” (“TOSEM-2025-0885”, p. 28) What do you mean? It's not clear on how this can be possible, considering that are several impairement situations, cases etc. Addressing all the them automatically by means of some MDE approach is not clear,.
+
+ “Limitation 7: Coverage of Accessibility Needs and Guidelines.” (“TOSEM-2025-0885”, p. 28)
+
+ “Integrate visual impairment requirements with generic requirements.” (“TOSEM-2025-0885”, p. 28)
+
+ “Map visual impairment requirements to commonly used requirements modeling approaches” (“TOSEM-2025-0885”, p. 28)
+
+ “Reuse design models” (“TOSEM-2025-0885”, p. 29) The reuse aspects are mentioned in several parts of the paper, even though it is not clear to what extent this is possible. As mentioned in one of my comments above, applications can be different, in different contexts and different users. What could you reuse? What are the envisioned reusability possibilities?
+
+ “Develop or extend modeling languages to cover needs of visually impaired users.” (“TOSEM-2025-0885”, p. 29)
+
+ “Evaluate and enhance or develop modeling languages to better represent specific accessibility needs, i.e., annotating color-independent interactions, providing alternative modalities, tagging semantic description of UI elements, or dependencies on screen readers, in software design. By adapting and extending existing modeling languages, developers can more effectively articulate and document accessibility requirements within their designs” (“TOSEM-2025-0885”, p. 29)
+
+ “Leverage genAI to create impairment-focused models and represent different levels of vision loss.” (“TOSEM-2025-0885”, p. 29) This comes out of the blue!
+
+ “Provide reusable RTE components that incorporate vision accessibility” (“TOSEM-2025-0885”, p. 30) See my previous comment about reusability.
+
+ “Develop reusable generators and templates incorporating the visually impaired needs.” (“TOSEM-2025-0885”, p. 30) This is very related to one of my previous comment about reusability concerns
+
+ “Create and refine reusable transformation rules for covering sight-related accessibility features by default.” (“TOSEM-2025-0885”, p. 30) Idem, see my previous comment. This is the main concern of this work!
+
+ “While accessibility needs for visually impaired persons are often overlooked in developing socio-technical systems, an MDE approach should provide the needed developer support to incorporate them systematically and consistently throughout the complete application. This study presents a systematic literature review of 30 primary studies on the application of model-driven engineering for visual impairments selected from an initial pool of 447 papers. We have analyzed existing trends regarding timing, output, impact, and nature of the reported approaches, and what visual impairments they address. We investigated the MDE approaches and their development steps and evaluations in detail, and gave an overview of the reported strengths, limitations, gaps, and challenges. Key findings are that most studies to date operate at a high abstraction level, mainly rely on WCAG, and rarely provide reproducible pipelines or working software artifacts.” (“TOSEM-2025-0885”, p. 31)
+
+ “Only a small number of studies provide concrete modeling approaches for accessibility requirements,” (“TOSEM-2025-0885”, p. 31)
+
+ “functioning implementations, and evaluations with visually impaired end users. This limits reuse, hinders independent verification of the results and constrains the impact for practical adoption. Only a few approaches target MDE methods, languages, transformations, code generators, or further tooling as the object of innovation and rather use MDE as an instrument. This might explain why contributions are often rather conceptual, short on implementation details, and underrepresented at core MDE venues. Consequently, the analysis has shown limited research outputs and low visibility. This calls for technically grounded work that treats accessibility as a first-class concern. The applied methods are mixed: While WCAG is used by most of the approaches, and models commonly capture the UI, interactions, and navigation, only five studies consider modeling accessibility requirements (without being specific enough to enable reproduction). Evaluations are sparse: 10 studies have no evaluation, and only 6 conducted user studies, whereas only 3 of them involved visually impaired participants. None provided additional evaluation data packages to support replication of the evaluation. Measuring the achieved accessibility of applications remains challenging, as only using automated checkers is not sufficient and conducting user studies is time-intensive. Using our results, we have sketched some possible research topics in analysis, design, implementation, and testing of accessible applications using MDE. Promising research directions include (i) analysis and design techniques that make accessibility requirements explicit, traceable and verifiable at the model level, (ii) reusable model transformations, code templates, code generators and runtime components that include accessibility, and (iii) testing approaches increasing the level of automation and checking for compliance with accessibility requirements. Exploring the interplay with methods from AI and generative AI provides additional possible research directions. Advancing the field will require publishing more implementation details and replication packages. In summary, the current state-of-the-art demonstrates potential for improving accessibility of software applications with MDE methods. Providing more reusable artefacts on model, template, and code level and transparent evaluations with relevant user groups, the MDE community can improve development methods for accessibility for visual impairments, delivering an important impact on society” (“TOSEM-2025-0885”, p. 32)
+
+ Consider that those that are tagged with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are important sentences.
+
+ Please pay attention to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ COMMENTS: Organize the notes especially those that contain issues or typos.
+
+ Please avoid overstatements and minimize bullet points. The comments have to be fluent, informative.
\ No newline at end of file
diff --git a/pages/@TraceCoder%3A A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code.md b/pages/@TraceCoder%3A A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code.md
new file mode 100644
index 00000000..a1c8c3f8
--- /dev/null
+++ b/pages/@TraceCoder%3A A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code.md
@@ -0,0 +1,214 @@
+tags:: [[#zotero]]
+date:: 2026
+title:: @TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code
+item-type:: [[journalArticle]]
+original-title:: TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code
+language:: en
+library-catalog:: Zotero
+links:: [Local library](zotero://select/library/items/XP7SMW8I), [Web library](https://www.zotero.org/users/1039502/items/XP7SMW8I)
+
+- [[Abstract]]
+ - Large Language Models (LLMs) often generate code with subtle yet critical bugs, particularly for complex tasks. Existing automated methods for repairing LLM-generated code are limited by their reliance on superficial outcomes, such as simple pass/fail results. This “black-box” approach offers little insight into the program’s internal dynamics, hindering precise error localization. Furthermore, the absence of a mechanism to learn from past failures leads to inefficient repair cycles that often repeat the same mistakes. To address these limitations, we introduce TraceCoder, a collaborative multi-agent framework that mimics the observe-analyze-repair process of human experts. The framework first instruments the code with diagnostic print statements to capture fine-grained runtime traces, providing deep visibility into its internal execution. It then conducts causal analysis on these traces to accurately identify the root cause of the error. This process is further enhanced by a novel Historical Lesson Learning Mechanism, which distills insights from prior failed repair attempts to inform subsequent correction strategies and prevent recurrence of similar mistakes. To ensure stable convergence, a Rollback Mechanism enforces that each repair iteration constitutes a strict improvement toward the correct solution. Comprehensive empirical evaluations demonstrate that TraceCoder achieves up to a 34.43% relative improvement in Pass@1 accuracy over state-of-the-art baselines. Ablation studies verify the significance of each system component, with the iterative repair process alone contributing a 65.61% relative gain in accuracy. Furthermore, TraceCoder significantly outperforms leading iterative methods in terms of both accuracy and cost-efficiency.
+- ### Attachments
+ - [PDF](zotero://select/library/items/LU4KFAS8) {{zotero-imported-file LU4KFAS8, "2026 - TraceCoder A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code.pdf"}}
+- ### Notes
+ - I'm reviewing a research paper and I took the following notes:
+
+ # Annotations
+ (17/09/2025, 15:04:04)
+
+ - “A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “Existing automated methods for repairing LLM-generated code are limited by their reliance on superficial outcomes, such as simple pass/fail results” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “the absence of a mechanism to learn from past failures leads to inefficient repair cycles that often repeat the same mistakes.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “TraceCoder, a collaborative multi-agent framework that mimics the observe-analyze-repair process of human experts.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “It then conducts causal analysis on these traces to accurately identify the root cause of the error” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #e56eee
+
+ - “Historical Lesson Learning Mechanism” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “Rollback Mechanism enforces that each repair iteration constitutes a strict improvement toward the correct solution” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #a28ae5
+
+ - “Comprehensive empirical evaluations demonstrate that TraceCoder achieves up to a 34.43% relative improvement in Pass@1 accuracy over state-of-the-art baselines” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “. Despite their impressive capabilities, LLMs often generate code that contains subtle yet critical bugs—particularly in complex or logic-intensive scenarios” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “This challenge has given rise to an emerging research direction focused on the automated repair of LLM-generated code, aiming to improve the reliability, correctness, and usability of LLM-assisted development” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “Recent work in this emerging area has explored diverse strategies for repairing LLM-generated code.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “However, most existing self-correction methods operate as “blackboxes”, relying solely on pass/fail feedback from a test suite. This approach, which lacks insight into the program’s internal execution, suffers from significant limitations.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “To address these challenges, we propose TraceCoder, a multiagent collaborative self-debugging framework that emulates the human debugging process of iterative observation, analysis, and repair.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “TraceCoder decomposes the complex debugging task into three specialized agents to enhance modularity, reliability, and control. Specifically, the Instrumentation Agent captures fine-grained runtime traces by injecting diagnostic statements into the program. The Analysis Agent performs causal reasoning over these traces, guided by a novel Historical Lesson Learning Mechanism (HLLM), which distills insights from past failures to generate effective repair plans. The Repair Agent then translates these plans into concrete code modifications.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #a28ae5
+
+ - “Rollback Mechanism (RM)” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 1) #5fb236
+
+ - “This structured workflow—where the Analysis Agent integrates runtime evidence and historical insights to guide the Repair Agent—establishes a cohesive and interpretable debugging loop with a clear separation of concerns.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #e56eee
+
+ - “Second, it facilitates experienceinformed repair decisions through historical learning, and ensures a robust repair trajectory via integrated rollback and replanning mechanisms.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “We evaluated TraceCoder on several representative datasets, including BigCodeBench and ClassEval, using diverse LLM backends.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “Notably, TraceCoder improves the success rate of repairing LLM-generated code, reduces redundant repair attempts, and enhances cost-efficiency—especially on complex programming tasks where LLMs are most prone to failure.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #e56eee
+
+ - “TraceCoder, a modular, multi-agent framework that emulates the human debugging workflow to enable automated repair of LLM-generated code” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “a novel HLLM that learns from past failures to guide future repairs and avoid repeated mistakes.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “Evaluations show that TraceCoder significantly outperforms SOTA methods, improving repair accuracy from baseline levels by up to 34.43% in relative terms on challenging class-level code generation benchmarks.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “Empirical investigations, such as DevGPT [24], reveal that LLM-generated code is often used for prototyping or conceptual illustration, rather than deployment.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “Despite these advances, postgeneration repair remains underexplored—LLMs frequently produce subtle logic bugs that existing generation pipelines cannot correct.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #5fb236
+
+ - “We address this gap by proposing a trace-driven framework designed to diagnose and repair LLM-generated code.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 2) #a28ae5
+
+ - “Zhang et al. [49] emphasize that despite advances in learning-based repair, runtime-aware introspection and memory-guided strategies remain underexplored.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #a28ae5
+
+ - “However, most methods lack such introspective capabilities and do not systematically incorporate lessons from failed attempts, limiting their effectiveness in complex debugging scenarios.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #e56eee
+
+ - “To address these gaps, we propose a self-debugging approach that combines fine-grained runtime introspection with historical error learning, enabling targeted and repeat-aware code repair” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #5fb236
+
+ - “most MAS frameworks focus on task decomposition and static role allocation, with limited support for integrating dynamic runtime feedback or leveraging historical debugging context” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #5fb236
+
+ - “causal planning with collaborative repair to support runtime-aware, self-corrective debugging” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #5fb236
+
+ - “Instrumentation Agent inserts diagnostic probes to collect runtime traces” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #ffd400
+ *Does it mean that it changes the previously generated code?*
+
+ - “Analysis Agent performs causal reasoning over these traces to localize faults” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #2ea8e5
+
+ - “Repair Agent synthesizes and applies candidate patches.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #2ea8e5
+
+ - “When initial code fails its test suite, the agents are activated and iterate until all tests pass or a termination condition is reached.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #a28ae5
+
+ - “the agent inserts diagnostic print statements into the code to expose internal state transitions and control flow.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #a28ae5
+
+ - “These runtime insights serve as essential evidence for downstream causal analysis by the Analysis Agent.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #a28ae5
+
+ - “resulting instrumented code (Cinst) strictly preserves the original computational semantics but emits context-aware debug logs during execution, providing valuable insights into the program’s dynamic behavior” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #a28ae5
+
+ - “The Instrumentation Agent employs a dedicated prompt to guide the LLM in inserting diagnostic probes.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #ffd400
+ *This is a critical point. Is it sure that the instrumentation agent does not wrongly add statements that change the semantics of the code?*
+
+ - “with strategically placed print statements that reveal execution flow and key variable states” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #ffd400
+ *Only print statements are added then.*
+
+ - “The agent must not modify computational logic, comment out code, or introduce new variables—thus preserving semantic integrity.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 3) #ffd400
+ *This is crucial. How do you ensure that?*
+
+ - “It records the entire output stream during execution and monitors for any runtime errors or uncaught exceptions.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #5fb236
+
+ - “The result is a structured runtime trace that combines test results, debug outputs, and error and exception details.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #a28ae5
+
+ - “This trace is then forwarded to the Analysis Agent as a key input to support subsequent fault diagnosis and repair planning.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #a28ae5
+
+ - “a repair plan for the Repair Agent” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #5fb236
+
+ - “targeted instrumentation suggestions for the next debugging cycle.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #5fb236
+
+ - “Lesson Record (Lrecord). A structured log of all failed repair attempts for the current problem, used to reflect on prior reasoning and avoid repeated mistakes.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #5fb236
+
+ - “Diagnosis and Reflection.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #2ea8e5
+
+ - “Strategy Formulation” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 4) #2ea8e5
+
+ - “This prompt defines the LLM’s role, clarifies the repair objectives, and guides it to reason through the task in a systematic and controlled manner.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “Repair Agent follows a structured three-step workflow:” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #2ea8e5
+
+ - “allowed to make minimal adjustments” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #ffd400
+ *This is also important because it is related to the convergence of the refinement process. How can you define such "minimal" adjustments?*
+
+ - “Repair Agent can be modeled as a function that maps the given context and the repair plan from the Analysis Agent to the final repaired code (Crepaired).” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #e56eee
+
+ - “his process embodies its core responsibility of executing the repair: (Dprob, Cfaulty, Ferror, Prepair) → Crepaired” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “The communication among TraceCoder’s agents follows a structured, sequential pattern, mediated by shared artifacts rather than direct message passing.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #ffd400
+ *So, no dedicated MAS framework has been used. This is important to motivate, because there are dedicated frameworks that take care of the communication and orchestration of agents collaborating to achieve a given goal.*
+
+ - “Analysis Agent integrates” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #ffd400
+ *How agents are orchestrated?*
+
+ - “a detailed repair plan” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “set of instrumentation suggestions to guide the Instrumentation Agent in collecting more targeted traces in subsequent iterations.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #ffd400
+ *Is it always necessary?*
+
+ - “This updated version is re-entered into the testing process, where its success or failure becomes the basis for the next iteration.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “Although the agents maintain independence and do not communicate directly, the flow of artifacts creates an implicit yet effective feedback mechanism: test results indirectly inform the Analysis Agent of the effectiveness of its prior diagnosis.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #ffd400
+
+ - “This sequential, artifactmediated communication model ensures that each agent operates with well-structured, contextually relevant information, avoiding uncoordinated interactions and promoting stable convergence.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #ffd400
+ *Can we be sure about that?*
+
+ - “HLLM, which addresses the limitations of stateless repair by enabling the system to learn from past failures.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “This allows the Analysis Agent to avoid previously ineffective reasoning paths and refine its diagnostic approach across repair cycles.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “Lesson Record.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #2ea8e5
+
+ - “Each time an iterative repair attempt fails to pass all predefined test cases, the system automatically captures key contextual information.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “Lesson Feedback.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #2ea8e5
+
+ - “Before generating a new repair plan, the Analysis Agent prompts the LLM to analyze the Lesson Record, which contains all failure records for the current problem instance.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 5) #5fb236
+
+ - “Lesson-Informed Deliberation and Planning” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 6) #2ea8e5
+
+ - “. By doing so, RM prevents the repair trajectory from deteriorating across iterations and anchors the search process around the best-known solutions.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 6) #5fb236
+
+ - “Key State Recording.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 6) #2ea8e5
+
+ - “Progress Evaluation and Decision-Makin” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 6) #2ea8e5
+
+ - “This section introduces four research questions addressed by TraceCoder and details the experimental setup, including datasets, baselines, evaluation metrics, and implementation details” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 6) #5fb236
+
+ - “RQ1: How effective is TraceCoder in repairing LLM-generated code compared to SOTA automated repair methods?” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 7) #2ea8e5
+
+ - “RQ2: How do TraceCoder’s key hyperparameters affect its repair performance and stability?” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 7) #2ea8e5
+
+ - “RQ3: What is the contribution of each core component to TraceCoder’s overall effectiveness?” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 7) #2ea8e5
+
+ - “RQ4: What are TraceCoder’s API usage characteristics and what are the most frequent failure types during repair?” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 7) #2ea8e5
+
+ - “BigCodeBench offers a diverse set of realistic functionlevel tasks that emphasize complex instruction following and API usage” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 7) #ffd400
+ *Strange sentence. Maybe "following an API usage" ?*
+
+ - “Answer to RQ1: TraceCoder consistently outperforms baseline methods across all benchmarks and model settings. Its advantage is particularly notable on complex benchmarks such as ClassEval and BigCodeBench, where it achieves a relative improvement of up to 34.43% over the strongest baselines.” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 7) #ffd400
+ *Readers are not provided with details to read these numbers in a convincing manner. Can you give some examples to give some hints on the different results provided by the different tools including TraceCoder? Morever, the experiment settings should be better presented. No details are given concerning the problem description, the corresponding source code (if it is a method, a class, a full project) and no details are given concerning the coverage of the generated test cases. With the given descriptions, many questions arise that require further details. Even the application of the baselines is not clear, the same questions about the experimental setup arise.*
+
+ - “This paper presented TraceCoder, a trace-driven, multi-agent framework that emulates expert debugging behavior to automatically repair LLM-generated code. By leveraging runtime instrumentation, coordinated agent collaboration, and iterative refinement, TraceCoder enables precise error diagnosis and targeted correction. Its HLLM prevents redundant failures by reusing past insights, while the RM stabilizes progress by preserving successful intermediate results. Extensive evaluations across multiple benchmarks and foundation models demonstrate TraceCoder’s significant improvements in repair accuracy, particularly on complex tasks. Further analysis highlights its superior efficiency among iterative methods and reveals that the remaining challenge lies in addressing subtle semantic flaws. Future work will explore strategies to improve token efficiency and extend TraceCoder’s language coverage. A key direction is enhancing the HLLM by incorporating structured knowledge representations and task-level learning mechanisms, enabling agents to generalize from prior repair attempts across tasks and domains” (“TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code”, 2026, p. 10) #ffd400
+ *This is a very interesting paper. The presented approach is novel. Themain problem is on RQ1 and on the presentation of how the tool can be used in practice. In particular, the granularity of the problem specification that is given to LLMs to generate source code is not clear. It is not clear also the code that is generated, is it methods, classes, etc. What's the role of test cases in driving the initial code generation?*
+
+ COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows:
+
+ SUMMARY: Just a few sentence to summarize the work
+
+ STRENGHTS:
+
+ WEAKNESSES:
+
+ COMMENTS: Organize the notes with respect to the following criteria:
+
+ -
+ `Novelty`
+
+ -
+ `Rigor`
+
+ -
+ `Relevance (of the contribution)`
+
+ -
+ `Verifiability and Transparency`
+
+ -
+ `Presentation`
+
+ And then add a Detailed Comments section to report the notes that contain issues or typos.
+ Can you also formulate three explicit questions by considering the comments above?
\ No newline at end of file
diff --git a/pages/A Research Assistant Team.md b/pages/A Research Assistant Team.md
new file mode 100644
index 00000000..a47a7f54
--- /dev/null
+++ b/pages/A Research Assistant Team.md
@@ -0,0 +1,12 @@
+- **Use case**: a *“research assistant team”*:
+ - **Researcher** agent → searches the web / literature and gathers info
+ - **Writer** agent → turns notes into a clean answer
+ - **Critic** agent → reviews the draft and tightens it up
+ - **Supervisor** agent → decides which specialist to call and when
+- Setup
+ - ```
+ python -m venv venv
+ .\venv\Scripts\Activate.ps1
+ pip install -U "langchain>=1.0" langchain-openai langchain-community
+ export OPENAI_API_KEY="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"
+ ```
\ No newline at end of file
diff --git a/pages/AVA3.md b/pages/AVA3.md
new file mode 100644
index 00000000..58170c80
--- /dev/null
+++ b/pages/AVA3.md
@@ -0,0 +1,3 @@
+tags:: [[SERVICES/PHDICT]]
+
+- {{embed ((68584ed7-1a9f-42ba-85b0-9cd778066ea7))}}
\ No newline at end of file
diff --git a/pages/Assicurazione della Qualità di Corsi di Studio e di dottorato e Dipartimenti - Audizione del 21 novembre 2025.md b/pages/Assicurazione della Qualità di Corsi di Studio e di dottorato e Dipartimenti - Audizione del 21 novembre 2025.md
new file mode 100644
index 00000000..7b2c015e
--- /dev/null
+++ b/pages/Assicurazione della Qualità di Corsi di Studio e di dottorato e Dipartimenti - Audizione del 21 novembre 2025.md
@@ -0,0 +1,24 @@
+tags:: #todoist-task, [[SERVICES/PHDICT]] , #AVA3
+date:: [[06-10-2025]] - 15:53
+progress:: {{renderer :todomaster}}
+
+ - [[Resources]]
+ - Linee guida e moduli: [https://www.univaq.it/section.php?id=2223](https://www.univaq.it/section.php?id=2223)
+ - 
+ - 
+ - 
+ - ### Tasks
+ - TODO Aggiornare dati su NOTION
+ - DONE Decidere studenti da coinvolgere
+ id:: 68e76ae4-b361-4812-85ba-d7c07be80b1c
+ :LOGBOOK:
+ CLOCK: [2025-11-11 Tue 22:43:35]--[2025-11-11 Tue 22:43:36] => 00:00:01
+ :END:
+ - DONE Aggiornare sito web con dati dal documnto di presentazione
+id:: 69190e77-3111-4845-b9ae-792f9f3382e6
+ - DONE Lavorare su questionario / Allegato
+ id:: 68e76ae4-ab11-47e1-81fc-f2973dab9f1a
+ - DONE Altri documenti?
+ -
+ - ### Notes
+ - [AUDIZIONE NUCLEO DI VALUTAZIONE](onenote:https://d.docs.live.net/a33324427a144a54/Documenti/Blocco%20appunti%20di%20Davide/Services/PHD-ICT.one#AUDIZIONE%20NUCLEO%20DI%20VALUTAZIONE§ion-id={607EE243-9302-4ECB-A218-93C9F0FD3C89}&page-id={21AB324D-4121-420B-94EA-FEDC58AABFD0}&object-id={BB882772-384E-067B-259A-2FB5232CFFA1}&12) ([visualizzazione Web](https://onedrive.live.com/view.aspx?resid=A33324427A144A54%21464&id=documents&wd=target%28Services%2FPHD-ICT.one%7C607EE243-9302-4ECB-A218-93C9F0FD3C89%2FAUDIZIONE%20NUCLEO%20DI%20VALUTAZIONE%7C21AB324D-4121-420B-94EA-FEDC58AABFD0%2F%29&wdpartid=%7b252131B6-EB60-054A-24A3-0383FAEC354A%7d%7b1%7d&wdsectionfileid=A33324427A144A54!1784))
\ No newline at end of file
diff --git a/pages/Assicurazione della qualità dei corsi di Dottorato di Ricerca – AVA3 – Calendario delle scadenze. Presentazione relazione di fine ciclo (RC.PHD).md b/pages/Assicurazione della qualità dei corsi di Dottorato di Ricerca – AVA3 – Calendario delle scadenze. Presentazione relazione di fine ciclo (RC.PHD).md
new file mode 100644
index 00000000..272e03ae
--- /dev/null
+++ b/pages/Assicurazione della qualità dei corsi di Dottorato di Ricerca – AVA3 – Calendario delle scadenze. Presentazione relazione di fine ciclo (RC.PHD).md
@@ -0,0 +1,10 @@
+tags:: #todoist-task, [[SERVICES/PHDICT]], #AVA3
+date:: [[24-11-2025]] - 18:40
+progress:: {{renderer :todomaster}}
+
+ - *"Il calendario delle scadenze per la produzione dei documenti di programmazione, monitoraggio e riesame, viene approvato dal PQA entro il 31 dicembre di ogni anno, su proposta da parte della struttura organizzativa di Ateneo del dottorato (responsabile del settore dottorati, assegni e borse di ricerca), di intesa con le coordinatrici e i coordinatori dei corsi di dottorato e con il referente di Ateneo".*
+ - 
+ - [Relazione Fine Ciclo RC.PHD_2025.docx](../assets/Relazione_Fine_Ciclo_RC.PHD_2025_1764006190602_0.docx)
+ - [Linee Guida AQ Dottorati_marzo 2025 FINALE.pdf](https://www.unitn.it/sites/default/files/2025-05/Linee%20Guida%20AQ%20Dottorati_marzo%202025%20FINALE.pdf?__cf_chl_tk=mV7AQTTxWiMcoc2Xmcr9fZD6Ed8.rjv9e95e_jsVAOk-1764004635-1.0.1.1-pCc2G1KbuZG6ngZqe.qVPvueWoMzTalI5OTdUnrrAhs)
+ - TODO GAQ: Gruppo di Assicurazione della Qualità
+-
\ No newline at end of file
diff --git a/pages/BRAINSTORMING.md b/pages/BRAINSTORMING.md
index 4cee0ba0..78e46f6b 100644
--- a/pages/BRAINSTORMING.md
+++ b/pages/BRAINSTORMING.md
@@ -2,6 +2,8 @@ icon:: 🧠
- 
- [[Writing Challenges]]
+- ## Previsione
+ - Architecting Green and Ethical Quantum Computing-based Agents :-) [[people/HenryMuccini]]
- ## RESEARCH
- Some fortcoming research efforts can be devoted to aspects relatedo to trustworthiness of LLMs in Software Engineering. The recently accepted [[David Lo]] project goes in that direction (see the interview at [[Omnivore/30-11-2023/Realising synergy for bots and engineers - Office of Research]] )
- The paper [[Omnivore/16-12-2023/Breaking the Silence- the Threats of Using LLMs in Software Engineering]] is full of hooks we could consider to define a short and medium term research plan.
diff --git a/pages/Benchmarking framework.md b/pages/Benchmarking framework.md
new file mode 100644
index 00000000..e4d31db2
--- /dev/null
+++ b/pages/Benchmarking framework.md
@@ -0,0 +1 @@
+alias:: [[Benchmarks]]
diff --git a/pages/Benchmarks.md b/pages/Benchmarks.md
new file mode 100644
index 00000000..22fef9a9
--- /dev/null
+++ b/pages/Benchmarks.md
@@ -0,0 +1,6 @@
+tags:: [[PROJECTS/MOSAICO]], [[P1]]
+
+ - In one of the ICSE papers that I reviewed [[ICSE2026-paper1656]] there is this reference to look at:
+ - >[21] René Just, Darioush Jalali, and Michael D. Ernst. 2014. **Defects4j: A Database of Existing Faults to Enable Controlled Testing Studies for Java Programs**. In International Symposium on Software Testing and Analysis, ISSTA ’14, San Jose, CA, USA - July 21 - 26, 2014. ACM, 437–440.
+ - It made me think that when benhmarking AI agents, we need to follow something similar with what we did with Jesus ([ModelXGlue: a benchmarking framework for ML tools in MDE | Software and Systems Modeling](https://link-springer-com.univaq.idm.oclc.org/article/10.1007/s10270-024-01183-z))
+ - In particular, this concept of database of existing subjects to be investigated should be made explicit in the language for specifying benchmarks.
\ No newline at end of file
diff --git a/pages/COLA-D-24-00156.md b/pages/COLA-D-24-00156.md
index 9b60e8c6..a6e58855 100644
--- a/pages/COLA-D-24-00156.md
+++ b/pages/COLA-D-24-00156.md
@@ -13,6 +13,7 @@ parent::
todoist:: https://app.todoist.com/app/task/cola-d-24-00156-6Wxx76rWx3QQ6r88
- ### [[Highlights]]
+ collapsed:: true
- *# Annotazioni *
(6/3/2025, 14:47:58)
diff --git a/pages/CV Empower.md b/pages/CV Empower.md
index 13c73e3a..879cc818 100644
--- a/pages/CV Empower.md
+++ b/pages/CV Empower.md
@@ -5,8 +5,11 @@ icon:: 🔥
#+END_PINNED
- ## [[Writing Challenges]]
- ## [[AI Playground]]
-- [[Agentic AI]]
- -
+ - [[Agentic AI]]
+ - [[Conda and LangChain Playground]]
+ - [[LLMs-from-scratch: Implement a ChatGPT-like LLM in PyTorch from scratch, step by step]]
+ - [[LLM-based Planner]]
+ - [[A Research Assistant Team]]
- ## Documentazione tecnica
- [[OpenAI examples]]
- [debanjandhar12/logseq-anki-sync: An logseq to anki syncing plugin. (github.com)](https://github.com/debanjandhar12/logseq-anki-sync)
diff --git a/pages/Call per posizioni MOSAICO.md b/pages/Call per posizioni MOSAICO.md
index fea02bc9..d47d1491 100644
--- a/pages/Call per posizioni MOSAICO.md
+++ b/pages/Call per posizioni MOSAICO.md
@@ -1,51 +1,62 @@
tags:: #todoist-task [[PROJECTS/MOSAICO]]
+icon:: 🎉
+page-type:: [[PROJECTS/MOSAICO]]
progress:: {{renderer :todomaster}}
- ### TASKS
- {{query (and [[Call per posizioni MOSAICO]] (task TODO DOING) (not [[GOALS-TODOIST]]) (not [[TODOIST-LOGSEQED]]))}}
query-table:: true
-- TODO Preparare documento con lista di espressioni di interesse ricevute
--
-- 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)
-- DOING Fare scouting
- :LOGBOOK:
- CLOCK: [2025-06-14 Sat 11:05:25]
- :END:
-- DONE Fare post linkedin
- :LOGBOOK:
- CLOCK: [2025-06-14 Sat 11:04:58]--[2025-06-14 Sat 11:04:58] => 00:00:00
- CLOCK: [2025-06-14 Sat 11:05:07]--[2025-06-14 Sat 11:05:10] => 00:00:03
- CLOCK: [2025-06-14 Sat 11:05:15]--[2025-06-14 Sat 11:05:16] => 00:00:01
- :END:
- - Anche se generico, chiedere a chi fosse interessato ad un post-doc di approcciarmi via private message of via email.
\ No newline at end of file
+ - TODO Rivedere bene e prendere una decisione in merito a ((69190e46-c217-4afb-866d-454ef610384a))
+ - DONE Preparare documento con lista di espressioni di interesse ricevute
+ id:: 6860e8a1-9d1e-4c28-8936-65e07c1023c4
+ :LOGBOOK:
+ CLOCK: [2025-07-30 Wed 18:01:24]--[2025-07-30 Wed 18:01:25] => 00:00:01
+ :END:
+ - DONE Studiare [[@Regolamento per il conferimento di contratti di ricerca]]
+ id:: 6839cd22-cd1c-4541-bea1-50c655611104
+ collapsed:: true
+ - ((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
+ collapsed:: true
+ :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|
+ - DONE Vedere CFP di altri contratti di ricerca banditi da altre università
+ id:: 68584e9a-3433-49a6-b66e-3f365c4b0713
+ :LOGBOOK:
+ CLOCK: [2025-07-30 Wed 18:01:36]--[2025-11-23 Sun 09:41:27] => 2775:39:51
+ :END:
+ - [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)
+ - DONE Fare scouting
+ id:: 68584e9a-7058-4550-bcde-ecae1dec7e70
+ :LOGBOOK:
+ CLOCK: [2025-06-14 Sat 11:05:25]--[2025-11-23 Sun 09:41:08] => 3886:35:43
+ :END:
+ - DONE Fare post linkedin
+ :LOGBOOK:
+ CLOCK: [2025-06-14 Sat 11:04:58]--[2025-06-14 Sat 11:04:58] => 00:00:00
+ CLOCK: [2025-06-14 Sat 11:05:07]--[2025-06-14 Sat 11:05:10] => 00:00:03
+ CLOCK: [2025-06-14 Sat 11:05:15]--[2025-06-14 Sat 11:05:16] => 00:00:01
+ :END:
+ - Anche se generico, chiedere a chi fosse interessato ad un post-doc di approcciarmi via private message of via email.
\ No newline at end of file
diff --git a/pages/Clip.md b/pages/Clip.md
index 40074b3d..de6b1de3 100644
--- a/pages/Clip.md
+++ b/pages/Clip.md
@@ -1 +1,3 @@
icon:: 📎
+
+-
\ No newline at end of file
diff --git a/pages/Conda and LangChain Playground.md b/pages/Conda and LangChain Playground.md
new file mode 100644
index 00000000..a0b89639
--- /dev/null
+++ b/pages/Conda and LangChain Playground.md
@@ -0,0 +1,39 @@
+- Installation [Installing Miniconda - Anaconda](https://www.anaconda.com/docs/getting-started/miniconda/install#macos-linux-installation:manual-shell-initialization)
+- **LangSmith** is here to support you at every step of your development journey with tools for observability, evaluation, and prompt engineering.
+ - As you start building your agent, you may need to debug unexpected outputs or performance bottlenecks. That’s where **tracing** in LangSmith comes in.
+ - Tracing can help you pinpoint issues and track how each part of your agent contributes to the output. You can also share traces with your team for seamless debugging – here’s [an example](https://track.pstmrk.it/3s/smith.langchain.com%2Fpublic%2F2f75dddd-fa65-4dd1-a9c7-09c11032b267%2Fr/Tpyp/a8W-AQ/AQ/fdde9c53-e164-482b-99dd-eeea3c2a9a20/1/L6vVzrWDEB).
+ - Ready to log your first trace in LangSmith? 🤓 Watch this quick 5-minute video to get started, and follow along with the code [here](https://track.pstmrk.it/3s/github.com%2Fxuro-langchain%2Feli5/Tpyp/a8W-AQ/AQ/fdde9c53-e164-482b-99dd-eeea3c2a9a20/2/OCP0-lehao).
+ - https://track.pstmrk.it/3s/www.youtube.com%2Fwatch%3Fv%3DfA9b4D8IsPQ/Tpyp/a8W-AQ/AQ/fdde9c53-e164-482b-99dd-eeea3c2a9a20/3/9ETeFMFTSD
+ - If you need a hand getting started, our [Quick Start](https://track.pstmrk.it/3s/docs.smith.langchain.com%2Fobservability/Tpyp/a8W-AQ/AQ/fdde9c53-e164-482b-99dd-eeea3c2a9a20/4/1-h5s_hKG0) and [Tracing docs](https://track.pstmrk.it/3s/docs.smith.langchain.com%2Fobservability%2Fhow_to_guides%23tracing-configuration/Tpyp/a8W-AQ/AQ/fdde9c53-e164-482b-99dd-eeea3c2a9a20/5/BFX-Zbfit0#tracing-configuration) have you covered 🥳
+ - Over the next 5 emails in our onboarding series, we’ll dive into LangSmith’s core features and show you how to use them. I’ll be back soon with more on the LangSmith Playground!
+- [[Conda]] is a package and environment manager, originated from Python even though it is language agnostic.
+ - While pip is excellent for managing Python-only packages, Conda can manage dependencies for projects that require non-Python libraries and complex dependency trees
+ - Conda environments can be exported to a YAML file, which permits to recreate the exact same environment, ensuring reproducibility for collaboration and deployment
+ - I think it's a kind of Maven or Gradle framework even though it is not specific to only one language
+ - Conda is a popular choice for data scientists and AI developers
+- Conda can manage different environments [Getting started with conda — conda 25.7.1.dev23 documentation](https://docs.conda.io/projects/conda/en/latest/user-guide/getting-started.html) es
+ - ```
+ conda create -n
+ ```
+- [[Anaconda]] and [[Miniconda]] are software distributions, which means they are collections of pre-built tools specifically designed for data science.
+ - Coda is included in Anaconda and Miniconda
+- Init commands
+ - ```bash
+ source /bin/activate
+ conda init --all
+ conda init --reverse bash
+ ```
+- Then
+ - ```bash
+ conda create -n langchain-book python=3.11
+ ```
+- From VS code I opened a Jupyter notebook of the book and I selected the langchain-book environment.
+- I executed
+ - ```bash
+ pip install -r requirements.txt
+ ```
+- To execute python code outside Jupyter it is necessary to select the correct interpreter
+ - [Python environments in VS Code](https://code.visualstudio.com/docs/python/environments#_manually-specify-an-interpreter)
+ - CTRL+SHIFT P
+ - {:height 867, :width 1154}
+-
\ No newline at end of file
diff --git a/pages/DESKTOP.md b/pages/DESKTOP.md
index 9d2b65e5..9a994341 100644
--- a/pages/DESKTOP.md
+++ b/pages/DESKTOP.md
@@ -5,19 +5,17 @@ title:: DESKTOP
- #+BEGIN_QUOTE
⛅️ This page is just for flushing Notes about things that must be done.
#+END_QUOTE
- -
- ### **WEEK FOCUS**
- Per la settimana del [[09-06-2025]] il focus e' su queste macro attività
- DONE [[Preparazione Intervento PINKAMP]] #todoist-task #SERVICES/PINKAMP
-id:: 68584e9a-9403-4a2a-87b9-70d3260ead58
- - [[Linee guida afferenza Collegio dottorato ICT]] #[[todoist-task SERVICES/PHDICT]]
+ id:: 68584e9a-9403-4a2a-87b9-70d3260ead58
+ - [[Linee guida afferenza Collegio dottorato ICT]] #[[todoist-task]] #[[ SERVICES/PHDICT]]
- [[Aggiornamento uso fondi progetti]] #todoist-task #ADMIN #PROJECTS
- [[Progettazione Offerta Formativa]] #SERVICES/PHDICT #todoist-task
- [[PAPERS/MOSAICO-Technical-Report]] #[[PAPERS]] #[[todoist-task]]
- Questo deve essere il main focus per le prossime settimane.
- #.tabular
- ### **TASKS**
- collapsed:: true
- {{embed [[Tasks]]}}
- ### **BRAINSTORMING**
collapsed:: true
diff --git a/pages/DONE.md b/pages/DONE.md
index 446e1d64..ab43b019 100644
--- a/pages/DONE.md
+++ b/pages/DONE.md
@@ -21,135 +21,268 @@ icon:: ✅
- ✔️ [[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* ((683f0792-8597-4118-9816-7f7e48227b97))
- - ✔️ [[04-06-2025]] *16:43* ((683f0792-8597-4118-9816-7f7e48227b97))
- - ✔️ [[04-06-2025]] *17:08* ((5aecbefd-0816-4ac9-92f7-61d18bdcfa4c))
- - ✔️ [[04-06-2025]] *17:38* ((68405bba-69d5-49a4-b785-d058a3d14a27))
- - ✔️ [[04-06-2025]] *23:40* ((68405baf-941e-4ee8-9e35-96211c54303f))
- - ✔️ [[05-06-2025]] *10:44* ((68414fa8-136d-4af0-b0f0-f91a893374c8))
- - ✔️ [[05-06-2025]] *11:53* ((68414f9a-830f-45a2-bded-93014df5d58e))
- - ✔️ [[05-06-2025]] *16:51* ((68414fa7-671f-43f2-9bca-3a6e0208567e))
- - ✔️ [[05-06-2025]] *23:27* ((683620b6-076a-40c2-a39e-ed6e6b6b38d0))
- - ✔️ [[05-06-2025]] *23:27* ((683620b6-807d-4a7b-833c-08a95c81bc76))
- - ✔️ [[05-06-2025]] *23:30* ((683620b6-4510-470b-90ef-d8ec1122471c))
- - ✔️ [[06-06-2025]] *09:53* ((683e08c8-82e3-4e52-8c5d-16a3c15ba341))
- - ✔️ [[06-06-2025]] *10:05* ((683e08c8-c3b2-4f6b-b62f-fc1cd4c1767b))
- - ✔️ [[06-06-2025]] *10:06* ((68429a60-0890-4c30-894d-75d34710c00d))
- - ✔️ [[06-06-2025]] *13:53* ((6842bc27-d67d-486f-8b13-1d8b1d3616c6))
- - ✔️ [[06-06-2025]] *16:52* ((68429a93-62d6-433e-a867-99b90dd5d32d))
- - ✔️ [[06-06-2025]] *16:52* ((68429a83-f76a-4f2e-93f9-1d56dc1b3b62))
- - ✔️ [[10-06-2025]] *14:39* ((68435147-3695-4233-9c59-30eec6c7bc12))
- - ✔️ [[10-06-2025]] *14:40* ((6843518f-f8a7-4629-b184-1ef230d8c645))
- - ✔️ [[10-06-2025]] *14:42* ((6843518f-b30c-484e-aba0-97ae9328b3f3))
- - ✔️ [[10-06-2025]] *14:43* ((6843518c-4984-4ec8-ac40-c6fba1517d03))
- - ✔️ [[11-06-2025]] *14:24* ((684350a8-08ce-44ba-ac20-7512a49e598d))
- - ✔️ [[18-06-2025]] *13:14* ((685266e9-3b29-401d-a2de-b8aad90054b7))
- - ✔️ [[18-06-2025]] *15:06* ((6852b2bb-9757-4ab4-8661-fdda350c9647))
- - ✔️ [[19-06-2025]] *13:06* ((6852f4e6-5a49-40a5-9807-72cafcb3fbc5))
- - ✔️ [[19-06-2025]] *15:51* ((68540a72-f93d-4413-9b74-79d3e5716758))
- - ✔️ [[19-06-2025]] *16:46* ((6853f169-1d30-4e3e-8bd6-d795d2f01914))
- - ✔️ [[19-06-2025]] *18:57* ((d4b795f4-21e9-408f-a6c2-3aadc10c3468))
- - ✔️ [[20-06-2025]] *11:45* ((6855230d-2cce-40a9-87b4-d99207252a6b))
- - ✔️ [[20-06-2025]] *11:45* ((68552317-3e34-4889-8d03-7671dd9239d7))
- - ✔️ [[20-06-2025]] *11:55* ((6855232a-08da-43da-9147-2012a583dc21))
- - ✔️ [[20-06-2025]] *11:57* ((93ba52d0-ca92-4181-84c3-f85f7ad67810))
- - ✔️ [[20-06-2025]] *12:29* ((68553095-9110-4f54-a545-dd186fa92e2d))
- - ✔️ [[21-06-2025]] *11:11* ((68435168-0fca-49d3-b735-8363d04c92ff))
- - ✔️ [[21-06-2025]] *22:12* ((e7272b30-e96e-4b85-918e-20c89e27647b))
- - ✔️ [[22-06-2025]] *23:25* ((68584e9a-9403-4a2a-87b9-70d3260ead58))
- - ✔️ [[23-06-2025]] *14:44* ((6858534a-5eed-4fdc-ab47-ea1bb731df12))
- - ✔️ [[23-06-2025]] *17:34* ((68597089-bcc4-49a9-8316-fc9b643c01d6))
- - ✔️ [[23-06-2025]] *17:34* ((685970dc-7da2-4c2d-84fe-309f8f827c16))
- - ✔️ [[24-06-2025]] *11:52* ((68597072-81a5-4071-801c-b670f12cd482))
- - ✔️ [[24-06-2025]] *11:52* ((685970ba-924c-46fe-b831-768ba57cfcca))
- - ✔️ [[24-06-2025]] *14:18* ((685a93d1-a8e0-4f42-8a60-8e41eec6c5d6))
- - ✔️ [[24-06-2025]] *18:37* ((68584f65-1fb3-44d5-8df6-eff29bbb2ed1))
- - ✔️ [[25-06-2025]] *23:44* ((68584f65-4d07-49c4-bbe3-3eac2e4c2435))
- - ✔️ [[28-06-2025]] *12:37* ((685f9805-3d35-4797-90e0-4f848ae0fff7))
- - ✔️ [[29-06-2025]] *09:30* ((685e49d2-2419-400e-99ae-66426632b820))
- - ✔️ [[29-06-2025]] *09:31* ((68584f65-059e-497a-b44b-fbe9081c7b12))
- - ✔️ [[29-06-2025]] *15:29* ((c13cae3e-c86c-44b2-9e16-ff89bc12b750))
- - ### [[2025/07]]
- - ✔️ [[02-07-2025]] *12:55* ((6860dc1b-a2e8-449c-b4e9-f8db54775637))
- - ✔️ [[02-07-2025]] *12:56* ((685e499f-4a03-4928-aa8c-ca53263084a5))
- - ✔️ [[02-07-2025]] *12:56* ((6858534a-0896-4252-b629-dd6be7fd6be3))
- - ✔️ [[02-07-2025]] *12:56* ((6858534b-a36d-412e-9cee-356a6787e0b4))
- - ✔️ [[02-07-2025]] *12:56* ((68584e74-0640-44c4-8805-dcadc064aedb))
- - ✔️ [[02-07-2025]] *12:57* ((68584e9f-280a-4a6a-afab-e3a5172e1586))
- - ✔️ [[02-07-2025]] *12:58* ((68584f65-2e7c-411e-ab67-9159bf073567))
- - ✔️ [[02-07-2025]] *12:58* ((68584ec9-3c3f-4ea3-8e31-cb2e6f469bef))
- - ✔️ [[02-07-2025]] *17:29* ((6860dc1b-1039-4aff-a908-74f088f170fd))
- - ✔️ [[13-07-2025]] *09:51* ((9b0b13f5-4a31-4b9a-81cd-ae678dccdd3d))
- - ✔️ [[13-07-2025]] *12:24* ((687351ee-8dbd-4ca4-8ca2-895cfc84715d))
- - ✔️ [[13-07-2025]] *21:36* ((68735256-da89-4baa-9f39-76f60ab77e24))
- - ✔️ [[13-07-2025]] *21:37* ((686e52cd-0003-4306-936b-f4756724680f))
- - ✔️ [[14-07-2025]] *22:08* ((68751c94-e11d-4e71-b78e-fdf51f8f1622))
- - ✔️ [[14-07-2025]] *23:07* ((687351fd-8069-4119-85b6-54f93729bde4))
- - ✔️ [[15-07-2025]] *08:51* ((6875e9a7-eeaa-484c-ae02-c79c27e13344))
\ No newline at end of file
+ - ✔️ [[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* ((683f0792-8597-4118-9816-7f7e48227b97))
+ - ✔️ [[04-06-2025]] *16:43* ((683f0792-8597-4118-9816-7f7e48227b97))
+ - ✔️ [[04-06-2025]] *17:08* ((5aecbefd-0816-4ac9-92f7-61d18bdcfa4c))
+ - ✔️ [[04-06-2025]] *17:38* ((68405bba-69d5-49a4-b785-d058a3d14a27))
+ - ✔️ [[04-06-2025]] *23:40* ((68405baf-941e-4ee8-9e35-96211c54303f))
+ - ✔️ [[05-06-2025]] *10:44* ((68414fa8-136d-4af0-b0f0-f91a893374c8))
+ - ✔️ [[05-06-2025]] *11:53* ((68414f9a-830f-45a2-bded-93014df5d58e))
+ - ✔️ [[05-06-2025]] *16:51* ((68414fa7-671f-43f2-9bca-3a6e0208567e))
+ - ✔️ [[05-06-2025]] *23:27* ((683620b6-076a-40c2-a39e-ed6e6b6b38d0))
+ - ✔️ [[05-06-2025]] *23:27* ((683620b6-807d-4a7b-833c-08a95c81bc76))
+ - ✔️ [[05-06-2025]] *23:30* ((683620b6-4510-470b-90ef-d8ec1122471c))
+ - ✔️ [[06-06-2025]] *09:53* ((683e08c8-82e3-4e52-8c5d-16a3c15ba341))
+ - ✔️ [[06-06-2025]] *10:05* ((683e08c8-c3b2-4f6b-b62f-fc1cd4c1767b))
+ - ✔️ [[06-06-2025]] *10:06* ((68429a60-0890-4c30-894d-75d34710c00d))
+ - ✔️ [[06-06-2025]] *13:53* ((6842bc27-d67d-486f-8b13-1d8b1d3616c6))
+ - ✔️ [[06-06-2025]] *16:52* ((68429a93-62d6-433e-a867-99b90dd5d32d))
+ - ✔️ [[06-06-2025]] *16:52* ((68429a83-f76a-4f2e-93f9-1d56dc1b3b62))
+ - ✔️ [[10-06-2025]] *14:39* ((68435147-3695-4233-9c59-30eec6c7bc12))
+ - ✔️ [[10-06-2025]] *14:40* ((6843518f-f8a7-4629-b184-1ef230d8c645))
+ - ✔️ [[10-06-2025]] *14:42* ((6843518f-b30c-484e-aba0-97ae9328b3f3))
+ - ✔️ [[10-06-2025]] *14:43* ((6843518c-4984-4ec8-ac40-c6fba1517d03))
+ - ✔️ [[11-06-2025]] *14:24* ((684350a8-08ce-44ba-ac20-7512a49e598d))
+ - ✔️ [[18-06-2025]] *13:14* ((685266e9-3b29-401d-a2de-b8aad90054b7))
+ - ✔️ [[18-06-2025]] *15:06* ((6852b2bb-9757-4ab4-8661-fdda350c9647))
+ - ✔️ [[19-06-2025]] *13:06* ((6852f4e6-5a49-40a5-9807-72cafcb3fbc5))
+ - ✔️ [[19-06-2025]] *15:51* ((68540a72-f93d-4413-9b74-79d3e5716758))
+ - ✔️ [[19-06-2025]] *16:46* ((6853f169-1d30-4e3e-8bd6-d795d2f01914))
+ - ✔️ [[19-06-2025]] *18:57* ((d4b795f4-21e9-408f-a6c2-3aadc10c3468))
+ - ✔️ [[20-06-2025]] *11:45* ((6855230d-2cce-40a9-87b4-d99207252a6b))
+ - ✔️ [[20-06-2025]] *11:45* ((68552317-3e34-4889-8d03-7671dd9239d7))
+ - ✔️ [[20-06-2025]] *11:55* ((6855232a-08da-43da-9147-2012a583dc21))
+ - ✔️ [[20-06-2025]] *11:57* ((93ba52d0-ca92-4181-84c3-f85f7ad67810))
+ - ✔️ [[20-06-2025]] *12:29* ((68553095-9110-4f54-a545-dd186fa92e2d))
+ - ✔️ [[21-06-2025]] *11:11* ((68435168-0fca-49d3-b735-8363d04c92ff))
+ - ✔️ [[21-06-2025]] *22:12* ((e7272b30-e96e-4b85-918e-20c89e27647b))
+ - ✔️ [[22-06-2025]] *23:25* ((68584e9a-9403-4a2a-87b9-70d3260ead58))
+ - ✔️ [[23-06-2025]] *14:44* ((6858534a-5eed-4fdc-ab47-ea1bb731df12))
+ - ✔️ [[23-06-2025]] *17:34* ((68597089-bcc4-49a9-8316-fc9b643c01d6))
+ - ✔️ [[23-06-2025]] *17:34* ((685970dc-7da2-4c2d-84fe-309f8f827c16))
+ - ✔️ [[24-06-2025]] *11:52* ((68597072-81a5-4071-801c-b670f12cd482))
+ - ✔️ [[24-06-2025]] *11:52* ((685970ba-924c-46fe-b831-768ba57cfcca))
+ - ✔️ [[24-06-2025]] *14:18* ((685a93d1-a8e0-4f42-8a60-8e41eec6c5d6))
+ - ✔️ [[24-06-2025]] *18:37* ((68584f65-1fb3-44d5-8df6-eff29bbb2ed1))
+ - ✔️ [[25-06-2025]] *23:44* ((68584f65-4d07-49c4-bbe3-3eac2e4c2435))
+ - ✔️ [[28-06-2025]] *12:37* ((685f9805-3d35-4797-90e0-4f848ae0fff7))
+ - ✔️ [[29-06-2025]] *09:30* ((685e49d2-2419-400e-99ae-66426632b820))
+ - ✔️ [[29-06-2025]] *09:31* ((68584f65-059e-497a-b44b-fbe9081c7b12))
+ - ✔️ [[29-06-2025]] *15:29* ((c13cae3e-c86c-44b2-9e16-ff89bc12b750))
+ - ### [[2025/07]]
+ - ✔️ [[02-07-2025]] *12:55* ((6860dc1b-a2e8-449c-b4e9-f8db54775637))
+ - ✔️ [[02-07-2025]] *12:56* ((685e499f-4a03-4928-aa8c-ca53263084a5))
+ - ✔️ [[02-07-2025]] *12:56* ((6858534a-0896-4252-b629-dd6be7fd6be3))
+ - ✔️ [[02-07-2025]] *12:56* ((6858534b-a36d-412e-9cee-356a6787e0b4))
+ - ✔️ [[02-07-2025]] *12:56* ((68584e74-0640-44c4-8805-dcadc064aedb))
+ - ✔️ [[02-07-2025]] *12:57* ((68584e9f-280a-4a6a-afab-e3a5172e1586))
+ - ✔️ [[02-07-2025]] *12:58* ((68584f65-2e7c-411e-ab67-9159bf073567))
+ - ✔️ [[02-07-2025]] *12:58* ((68584ec9-3c3f-4ea3-8e31-cb2e6f469bef))
+ - ✔️ [[02-07-2025]] *17:29* ((6860dc1b-1039-4aff-a908-74f088f170fd))
+ - ✔️ [[13-07-2025]] *09:51* ((9b0b13f5-4a31-4b9a-81cd-ae678dccdd3d))
+ - ✔️ [[13-07-2025]] *12:24* ((687351ee-8dbd-4ca4-8ca2-895cfc84715d))
+ - ✔️ [[13-07-2025]] *21:36* ((68735256-da89-4baa-9f39-76f60ab77e24))
+ - ✔️ [[13-07-2025]] *21:37* ((686e52cd-0003-4306-936b-f4756724680f))
+ - ✔️ [[14-07-2025]] *22:08* ((68751c94-e11d-4e71-b78e-fdf51f8f1622))
+ - ✔️ [[14-07-2025]] *23:07* ((687351fd-8069-4119-85b6-54f93729bde4))
+ - ✔️ [[15-07-2025]] *08:51* ((6875e9a7-eeaa-484c-ae02-c79c27e13344))
+ - ✔️ [[18-07-2025]] *18:13* ((68584e7c-bb5f-40fe-876d-21fe8d87565f))
+ - ✔️ [[19-07-2025]] *12:10* ((686e52d5-3bc5-4420-8cdc-b589ceb2dc04))
+ - ✔️ [[19-07-2025]] *12:15* ((6873c94d-06e6-466f-a125-f321b20c39fb))
+ - ✔️ [[23-07-2025]] *13:29* ((685e49d2-2419-400e-99ae-66426632b820))
+ - ✔️ [[23-07-2025]] *15:30* ((f2b64850-c185-41e8-b5fd-56f2f425379a))
+ - ✔️ [[30-07-2025]] *09:03* ((68874dfe-bd98-41ce-8216-3663c2439bc2))
+ - ✔️ [[30-07-2025]] *17:01* ((688a33c3-76cc-4772-8f84-9248e6d96027))
+ - ✔️ [[30-07-2025]] *18:00* ((6858534b-8fe7-4b13-8739-b45d7ac5ea75))
+ - ✔️ [[30-07-2025]] *18:01* ((6860e8a1-9d1e-4c28-8936-65e07c1023c4))
+ - ### [[2025/08]]
+ - ✔️ [[01-08-2025]] *15:38* ((688cc320-7b06-4594-943f-f302da78f521))
+ - ✔️ [[01-08-2025]] *16:56* ((688b9643-5053-49b9-b9ed-b559e7bf653c))
+ - ✔️ [[07-08-2025]] *09:11* ((6884f13b-60da-48da-abe9-8a522cde5d29))
+ - ✔️ [[07-08-2025]] *15:40* ((68584ec9-a2a1-4685-b559-141f96bb61f2))
+ - ✔️ [[07-08-2025]] *16:13* ((6894a6d1-0613-4b32-ac49-0c3a3fd0753d))
+ - ✔️ [[07-08-2025]] *17:10* ((6894a6a2-bbab-4ec6-bcf4-1821588feb0f))
+ - ✔️ [[08-08-2025]] *12:45* ((6895c9fa-c1e6-4f9b-a4b4-f53c7eefa296))
+ - ✔️ [[08-08-2025]] *15:22* ((68584ea7-8fde-4a5e-9367-f7054ced2f88))
+ - ✔️ [[08-08-2025]] *15:43* ((6895c9da-572c-48e2-8d71-80a61f7e0c81))
+ - ✔️ [[08-08-2025]] *15:53* ((6873c94d-06e6-466f-a125-f321b20c39fb))
+ - ✔️ [[18-08-2025]] *01:35* ((6864fa38-39bb-42b6-94f5-ba9bccfc4f04))
+ - ✔️ [[19-08-2025]] *14:43* ((68960139-341c-40fa-9a35-04c20f74ad14))
+ - ✔️ [[19-08-2025]] *14:45* ((6863b98d-74e6-435a-8631-c03155c89300))
+ - ✔️ [[19-08-2025]] *18:03* ((68653364-55e9-4d49-85e1-0c8a9f186e8e))
+ - ✔️ [[19-08-2025]] *18:04* ((6863a4ff-c366-4708-8009-34f6b34fedbb))
+ - ✔️ [[19-08-2025]] *18:06* ((6863a692-e9b0-4b8f-ba41-a9d4a1043651))
+ - ✔️ [[19-08-2025]] *18:07* ((686503c5-75e8-45ab-9237-aa9eb32c63cc))
+ - ✔️ [[19-08-2025]] *18:08* ((6863a8b5-35d5-492e-a8cf-2549750d9965))
+ - ✔️ [[20-08-2025]] *16:11* ((68960139-c4ea-441c-9d45-89381bddcfb9))
+ - ✔️ [[21-08-2025]] *16:42* ((68960139-1246-4fb7-a933-cc75804483b7))
+ - ✔️ [[25-08-2025]] *16:26* ((68ac6e66-ba4e-41e7-9637-5fe847dfc8ba))
+ - ✔️ [[26-08-2025]] *23:05* ((689467c8-88b1-45b0-b58c-99fa0d0b73a8))
+ - ✔️ [[26-08-2025]] *23:06* ((68960139-bbd3-44c1-a39a-5f0782e5bfad))
+ - ✔️ [[31-08-2025]] *11:47* ((68ac6e54-e572-42f4-8116-625b4d85d757))
+ - ✔️ [[31-08-2025]] *11:52* ((68960139-34fc-4ac4-8745-f8a2bb7cb6e9))
+ - ### [[2025/09]]
+ - ✔️ [[01-09-2025]] *00:04* ((68b4c69b-fa0b-41c1-9633-b87c6cf6ab33))
+ - ✔️ [[01-09-2025]] *00:04* ((68b4c69b-7fdf-4663-89af-ac6df65d88af))
+ - ✔️ [[01-09-2025]] *12:08* ((68b4c69b-4d77-4192-9cff-d9f87cb200f4))
+ - ✔️ [[02-09-2025]] *10:06* ((68946800-a5fe-4f75-af64-8b2509daf7fd))
+ - ✔️ [[02-09-2025]] *10:20* ((68b6a403-1ce2-4fe5-9668-54e32ac0e222))
+ - ✔️ [[02-09-2025]] *11:28* ((68b598e8-992a-433f-b685-5318c5ba0f4d))
+ - ✔️ [[02-09-2025]] *11:29* ((68b57381-292d-4e53-8b79-b0378d3ddcca))
+ - ✔️ [[02-09-2025]] *11:29* ((68b6a86a-0914-4535-b10a-d81519358f6a))
+ - ✔️ [[02-09-2025]] *15:48* ((6895c9da-572c-48e2-8d71-80a61f7e0c81))
+ - ✔️ [[03-09-2025]] *10:30* ((68b6f4f4-a42f-4e0a-a42d-427d478a4423))
+ - ✔️ [[03-09-2025]] *15:05* DONE Regolamento Corsi Dottorato
+ :LOGBOOK:
+ CLOCK: [2025-09-03 Wed 15:05:52]--[2025-09-03 Wed 15:05:52] => 00:00:00
+ :END:
+ - ### [[2025/09]]
+ - ✔️ [[08-09-2025]] *12:58* Check attività formativa
+ :LOGBOOK:
+ CLOCK: [2025-09-08 Mon 12:58:23]--[2025-09-08 Mon 12:58:24] => 00:00:01
+ :END:
+ - ✔️ [[08-09-2025]] *12:58* DONE Scrivere a Alessandro Celi per Portatili
+ :LOGBOOK:
+ CLOCK: [2025-09-08 Mon 12:58:48]--[2025-09-08 Mon 12:58:48] => 00:00:00
+ :END:
+ - ✔️ [[09-09-2025]] *15:02* ((68bfdd58-6374-44fb-a187-ef25e180e2b1))
+ - ✔️ [[09-09-2025]] *15:38* ((68a423d6-ddac-4f6f-b162-51318a682db6))
+ - ✔️ [[15-09-2025]] *13:05* DONE Check studente Giordano
+ - ✔️ [[15-09-2025]] *13:36* DONE **Verbale ultimo collegio**
+ - ✔️ [[20-09-2025]] *16:40* ((68946800-1268-43e8-8971-44b6c0d2ce9c))
+ - ✔️ [[24-09-2025]] *14:57* ((68d3ea95-45ab-43bb-86c6-506a00ca5420))
+ - ✔️ [[24-09-2025]] *16:01* ((68d3ea95-6c8a-40f9-93ff-5d930e6a7174))
+ - ✔️ [[24-09-2025]] *16:01* ((68d3ea95-2936-4efb-8e99-d9282435fff9))
+ - ✔️ [[24-09-2025]] *16:01* ((68d3ea95-f822-42f4-a4f6-6da2d5adfb75))
+ - ✔️ [[25-09-2025]] *11:47* ((68d3ea95-7a33-412c-a9e0-effaf3e484a0))
+ - ✔️ [[25-09-2025]] *11:52* ((68d3ea95-b046-49bf-9509-651f1e88b06e))
+ - ✔️ [[25-09-2025]] *12:42* ((68d3ea95-00ff-47d6-b92f-0243f944f2c0))
+ - ✔️ [[25-09-2025]] *16:38* ((68d3ea95-8858-468b-9c3a-4895f500a9f9))
+ - ✔️ [[26-09-2025]] *11:45* ((68584ec4-baa8-4664-ab02-cb70ee11bad5))
+ - ✔️ [[26-09-2025]] *18:20* ((68d3ea95-f018-4b23-9c51-b0ee94287661))
+ - ✔️ [[28-09-2025]] *17:55* DONE **14:30 - 16:30** - [[TEACHING]] - Pianificazione didattica
+ - ✔️ [[28-09-2025]] *18:41* DONE **16:30 - 17:30** Titolo per talks MODELS e ASE
+ - ✔️ [[28-09-2025]] *18:41* DONE **7:00 - 10:00** : Personal
+ :LOGBOOK:
+ CLOCK: [2025-09-28 Sun 18:41:28]--[2025-09-28 Sun 18:41:28] => 00:00:00
+ :END:
+ - ✔️ [[28-09-2025]] *21:48* DONE **10:00-12:00** - [[Deliverable D2.1]] #todoist-task #PROJECTS/MOSAICO
+ :LOGBOOK:
+ CLOCK: [2025-09-28 Sun 21:48:01]--[2025-09-28 Sun 21:48:02] => 00:00:01
+ :END:
+ - ✔️ [[28-09-2025]] *22:01*
+ - ✔️ [[30-09-2025]] *21:33* ((68584ec9-e757-4b59-adae-09b0616243c2))
+ - ### [[2025/10]]
+ - ✔️ [[02-10-2025]] *11:07* ((68dc3033-9770-4fd0-b2ea-87025e587615))
+ - ✔️ [[02-10-2025]] *14:19* ((68584ec9-a8ef-4798-a441-6ee772d7e22b))
+ - ✔️ [[08-10-2025]] *15:23* ((68df8e5d-3e7c-4377-8a9c-151d1a6f97ae))
+ - ✔️ [[08-10-2025]] *15:23* ((68df8e5d-e7d8-4964-9f1a-765fdd2a28e3))
+ - ✔️ [[13-10-2025]] *21:53* ((68bac2ea-d21f-45cb-b0b0-b7ba4bde8bf8))
+ - ✔️ [[13-10-2025]] *21:54* ((68bac2ea-edb2-4b78-b0eb-182a010233ec))
+ - ✔️ [[19-10-2025]] *14:22* DONE Aggiornare mailing list collegio
+ :LOGBOOK:
+ CLOCK: [2025-10-19 Sun 14:22:27]--[2025-10-19 Sun 14:22:28] => 00:00:01
+ :END:
+ - ✔️ [[19-10-2025]] *15:38* DONE Finalizzare OdG
+ :LOGBOOK:
+ CLOCK: [2025-10-19 Sun 15:38:53]--[2025-10-19 Sun 15:38:53] => 00:00:00
+ :END:
+ - ✔️ [[19-10-2025]] *16:01* DONE Convocare studenti nuovo ciclo
+ - ✔️ [[19-10-2025]] *20:58* DONE Convocazione prossimo collegio
+ :LOGBOOK:
+ CLOCK: [2025-10-19 Sun 20:58:34]--[2025-10-19 Sun 20:58:35] => 00:00:01
+ :END:
+ - ✔️ [[29-10-2025]] *18:30* DONE Questione tabella Excel dottorandi
+ :LOGBOOK:
+ CLOCK: [2025-09-03 Wed 15:05:41]--[2025-10-29 Wed 18:30:23] => 1347:24:42
+ :END:
+ - ### [[2025/11]]
+ - ✔️ [[05-11-2025]] *15:38* ((68e76ae4-ab11-47e1-81fc-f2973dab9f1a))
+ - ✔️ [[11-11-2025]] *22:43* DONE Tania scrive ai titolari dei corsi precedenti chiedendo se vogliono continuare ad erogare il corso come da offerta formativa 24/25 [[people/TaniaDiMascio]]
+ :LOGBOOK:
+ CLOCK: [2025-10-23 Thu 15:17:36]--[2025-11-11 Tue 22:43:15] => 463:25:39
+ :END:
+ - ✔️ [[11-11-2025]] *22:43* ((68e76ae4-b361-4812-85ba-d7c07be80b1c))
+ - ✔️ [[21-11-2025]] *15:23* DONE [[Assicurazione della Qualità di Corsi di Studio e di dottorato e Dipartimenti - Audizione del 21 novembre 2025]] #todoist-task #SERVICES/PHDICT
+ - ✔️ [[21-11-2025]] *16:24* DONE [[Progettazione Offerta Formativa]] #SERVICES/PHDICT #todoist-task
+ :LOGBOOK:
+ CLOCK: [2025-11-21 Fri 16:24:40]--[2025-11-21 Fri 16:24:41] => 00:00:01
+ :END:
+ - ✔️ [[22-11-2025]] *21:36* ((69221dd6-8d69-4210-b1f7-d3afa44ac65b))
+ - ✔️ [[23-11-2025]] *09:38* ((69190e77-3111-4845-b9ae-792f9f3382e6))
+ - ✔️ [[23-11-2025]] *09:41* ((68584e9a-7058-4550-bcde-ecae1dec7e70))
+ - ✔️ [[23-11-2025]] *09:41* ((68584e9a-3433-49a6-b66e-3f365c4b0713))
+ - ✔️ [[Nov 30th, 2025]] *20:50* ((68df8e5d-3f53-4e39-bb5c-c0dbe9368211))
+ - ✔️ [[Nov 30th, 2025]] *20:50* ((68df8e5d-fbdf-4070-ba1e-3a748f11766a))
+ - ### [[2025/12]]
+ - ✔️ [[Dec 9th, 2025]] *14:13* :LOGBOOK:
+ CLOCK: [2025-12-09 Tue 14:12:29]--[2025-12-09 Tue 14:13:07] => 00:00:38
+ :END:
+ - ✔️ [[Dec 16th, 2025]] *09:55* ((6938231c-2456-474f-b723-54a14064632f))
\ No newline at end of file
diff --git a/pages/Deliverable D2.1.md b/pages/Deliverable D2.1.md
new file mode 100644
index 00000000..fcc92542
--- /dev/null
+++ b/pages/Deliverable D2.1.md
@@ -0,0 +1,535 @@
+tags:: #todoist-task, [[PROJECTS/MOSAICO]]
+date:: [[25-08-2025]] - 08:38
+progress:: {{renderer :todomaster}}
+
+- ### References
+ - [Explore models in AI Toolkit](https://code.visualstudio.com/docs/intelligentapps/models)
+ - [AI Toolkit for Visual Studio Code - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-windows-ai-studio.windows-ai-studio)
+ - [Specification - Agent2Agent (A2A) Protocol](https://a2a-protocol.org/latest/specification/#554-agentskill-object)
+ - {{embed ((6863b98d-74e6-435a-8631-c03155c89300))}}
+- ### Tasks
+ - TODO Guardare i TODOs da [[Missione ROMA Mosaico]] #todoist-task #PROJECTS/MOSAICO #meeting
+ - DONE Finalizzare revisione di Section 3 - [[07-08-2025]]
+ id:: 6894a6d1-0613-4b32-ac49-0c3a3fd0753d
+ - DONE Rivedere Section 5 - [[07-08-2025]]
+ id:: 6894a6a2-bbab-4ec6-bcf4-1821588feb0f
+ - DONE Da finalizzare Tabella 4 con lista di marketplace e agent repositories.
+ id:: 68a423d6-ddac-4f6f-b162-51318a682db6
+ :LOGBOOK:
+ CLOCK: [2025-09-09 Tue 15:38:36]--[2025-09-09 Tue 15:38:36] => 00:00:00
+ :END:
+ - DONE Raffinare il metamodello in Section 6 - [[08-08-2025]]
+ id:: 68960139-341c-40fa-9a35-04c20f74ad14
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 14:43:06]--[2025-08-19 Tue 14:43:07] => 00:00:01
+ :END:
+ - DONE Aggiornare il metamodello guardando quanto da Antonio ne suo deliverable di WP1
+ id:: 68960139-34fc-4ac4-8745-f8a2bb7cb6e9
+ - [imtatlantiquefr.sharepoint.com/sites/MOSAICO/Shared Documents/Forms/AllItems.aspx?id=%2Fsites%2FMOSAICO%2FShared Documents%2FWork Packages%2FWP1%2FD1%2E1%2F20250801 draft - only Sections 2 and 3%2Epdf&parent=%2Fsites%2FMOSAICO%2FShared Documents%2FWork Packages%2FWP1%2FD1%2E1](https://imtatlantiquefr.sharepoint.com/sites/MOSAICO/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2FMOSAICO%2FShared%20Documents%2FWork%20Packages%2FWP1%2FD1%2E1%2F20250801%20draft%20%2D%20only%20Sections%202%20and%203%2Epdf&parent=%2Fsites%2FMOSAICO%2FShared%20Documents%2FWork%20Packages%2FWP1%2FD1%2E1)
+ - Da guardare particolarmente e' [Agntcy](https://docs.agntcy.org/#vision)
+ - DONE Inserire in Section 7 una prima bozza dell'architettura del Repository
+ id:: 68960139-bbd3-44c1-a39a-5f0782e5bfad
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 18:09:34]--[2025-08-26 Tue 23:06:08] => 172:56:34
+ :END:
+ - Partire da qualche slide in WP5?
+ - DONE Scrivere le conclusioni
+ id:: 68960139-c4ea-441c-9d45-89381bddcfb9
+ - DONE Lavorare su capitolo 4 a partire dal contenuto del paper EMSE
+ id:: 68960139-1246-4fb7-a933-cc75804483b7
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 18:09:37]--[2025-08-21 Thu 16:42:09] => 46:32:32
+ :END:
+ - DONE Rimuovere dalla bib tutte le occorrenze univaq
+ id:: 68ac6e66-ba4e-41e7-9637-5fe847dfc8ba
+ :LOGBOOK:
+ CLOCK: [2025-08-25 Mon 16:26:24]--[2025-08-25 Mon 16:26:24] => 00:00:00
+ :END:
+ - DONE Ripassata finale prima di mandare ai revisori
+ collapsed:: true
+- ### Notes
+ id:: 689467c8-88b1-45b0-b58c-99fa0d0b73a8
+ - Review di Antonio Garcia (  )
+ - DONE Quick note about the English: I see a lot of "agents monitoring" which should be "agent monitoring", for example. In general, when you have "noun verb-ing", "noun" tends to be singular.
+id:: 68d3ea95-45ab-43bb-86c6-506a00ca5420
+ - DONE Did you not consider LangGraph for Ch3? If so, why? (It's a big player, so this was somewhat surprising - did you run into issues with the license, or did you not consider it as a MAS framework?)
+id:: 68d3ea95-6c8a-40f9-93ff-5d930e6a7174
+ :LOGBOOK:
+ CLOCK: [2025-09-24 Wed 16:01:00]--[2025-09-24 Wed 16:01:02] => 00:00:02
+ :END:
+ - DONE Figure 3 doesn't really explain the notation used.
+id:: 68d3ea95-7a33-412c-a9e0-effaf3e484a0
+ - DONE For FC3.3 (continual evolution), have you considered options like Letta or MemGPT for self-improving agents?
+ - DONE For the METAGENTE study: in the optimisation loop, do you evaluate the new prompt based on how it does across a population of repositories, or is it only against one repository? The latter sounds like it could have a risk of over-fitting.
+id:: 68d3ea95-2936-4efb-8e99-d9282435fff9
+ :LOGBOOK:
+ CLOCK: [2025-09-24 Wed 16:01:22]--[2025-09-24 Wed 16:01:23] => 00:00:01
+ :END:
+ - DONE Figure 13(a) has an odd "5" before "ROUGE-1".
+ - DONE In Section 4.3.4, besides doing the Wilcoxon paired test for statistical significance, I'd also suggest looking at effect sizes. My intuition is that even if the differences are statistically significant, the effect sizes will be very small.
+id:: 68d3ea95-00ff-47d6-b92f-0243f944f2c0
+ - TODO In Figure 9, it feels like each spider chart has its own axis limits. They should all be using the same axis limits, so that the spider charts can be compared to each other.
+ - DONE The report never defines what PTM stands for (used in Ch5).
+id:: 68d3ea95-f822-42f4-a4f6-6da2d5adfb75
+ - DONE Given the talk we attended from Barahona at LLMA4SE 2025 on the various levels of "openness" of LLMs, your discussion of AI Agent List [77] sounds like this marketplace may be oversimplifying things. It may be worth mentioning the need for more nuance in that regard?
+id:: 68d3ea95-8858-468b-9c3a-4895f500a9f9
+ - ((68bac2bb-1db8-41cb-81ed-7ef7f76e1491))
+ - DONE Please take a close look at my comments on Figure 24. I think the metamodel should be expanded in a number of ways. For example, in OpenTelemetry, spans are organised into a tree - this doesn't seem to be reflected in TelemetryRecord.
+id:: 68d3ea95-f018-4b23-9c51-b0ee94287661
+ :LOGBOOK:
+ CLOCK: [2025-09-26 Fri 18:20:20]--[2025-09-26 Fri 18:20:21] => 00:00:01
+ :END:
+ - TODO I also think that Figure 25 needs some improvements: it should stay closer to UML object diagram notation, and it may be best to split it into static parts (about the agents themselves and their relationships) and dynamic parts (about the traces for specific executions of those agents). In fact, I would divide the trace for the separate phases, and I'd suggest expanding further the instantiation (making it more detailed and using all the types in the taxonomy).
+ - TODO For the MOSAICO agent repository architecture: would it make sense to integrate some type of vector database to allow for semantic search over the descriptions of the agents? It's quite likely that we will leave it up to the LLM in the reference agent to invoke your MCP tool for finding the most relevant agents, and that will most likely require semantic search.
+ - DONE Incidentally, I don't think MCP is documented via OpenAPI: MCP is JSON-RPC based rather than REST.
+id:: 68d3ea95-b046-49bf-9509-651f1e88b06e
+ - TODO For telemetry dashboards, you mention Grafana. That's good for metrics, but can it display traces as well, or should we use LangFuse for that?
+ - Da considerare anche il prompt?
+ - {{renderer :mermaid_68668a24-ce43-472e-b787-a53b895f7c75, 3}}
+ collapsed:: true
+ - ```mermaid
+ classDiagram
+ class Agent {
+ id
+ name
+ version
+ owner
+ }
+
+ class Capability {
+ domain
+ taskType
+ supportedLanguages
+ inputFormats
+ outputFormats
+ }
+
+ class PerformanceKPI {
+ accuracy
+ latencyMs
+ resourceConsumption
+ robustnessMetrics
+ }
+
+ class Governance {
+ license
+ dataResidency
+ GDPRCompliance
+ auditTrailAvailable
+ }
+
+ class FairnessEthics {
+ biasDetected
+ fairnessConstraints
+ explanationCapabilities
+ }
+
+ class RuntimeEnvironment {
+ runtime
+ requiredLibraries
+ hardwareAcceleration
+ }
+
+ class Provenance {
+ trainingDataSources
+ modelLineage
+ lastUpdated
+ }
+
+ class ContactInfo {
+ maintainerEmail
+ documentationUrl
+ }
+
+ class AgentRepository {
+ <>
+ }
+
+ Agent --> Capability : has
+ Agent --> PerformanceKPI : provides
+ Agent --> Governance
+ Agent --> FairnessEthics
+ Agent --> RuntimeEnvironment
+ Agent --> Provenance
+ Agent --> ContactInfo
+ AgentRepository --> Agent : manages
+ ```
+ - Agents should be also marked if they keep information or not for IP purposes.
+ -
+- 
+ {{renderer :plantuml_wqrztfdo}}
+ - ```plantuml
+ @startuml
+ ' Enumerations
+ enum FeedbackType {
+ EXPLICIT
+ IMPLICIT
+ }
+
+ enum MemoryType {
+ SHORT_TERM
+ LONG_TERM
+ }
+
+ enum TelemetryOutput {
+ LOG
+ TRACE
+ BAGGAGE
+ }
+
+ ' Core entities
+ class Agent {
+ ID: int
+ name: string
+ modelCard: string
+ messageContent: string
+ hyperparameter: string
+ dependencies: Agent
+ }
+
+ class SolutionAgent {
+ ID: int
+ intentions: string
+ desires: string
+ backStory: string
+ promptType: string
+ role: string
+ }
+
+ class CollaborationAgent {
+ ID: int
+ collaborationPattern: Pattern
+ }
+
+ class SupervisionAgent {
+ ID: int
+ }
+
+ class ConsensusAgent {
+ ID: int
+ }
+
+ class Task {
+ id: int
+ description: string
+ input: string
+ output: string
+ }
+
+ class Tool {
+ ID: int
+ name: string
+ API_key: string
+ }
+
+ class Memory {
+ ID: int
+ type: MemoryType
+ db: string
+ agent: Agent
+ }
+
+ ' Governance and usage
+ class Provider {
+ name: string
+ }
+
+ class Usage {
+ ID: int
+ name: string
+ }
+
+ class Remote {
+ ID: int
+ url: string
+ provider: Provider
+ }
+
+ class Local {
+ ID: int
+ hardwareRequirement: string
+ }
+
+ class A2AProtocol {
+ ID: int
+ }
+
+ ' Evaluation and monitoring
+ class Benchmark {
+ ID: int
+ metadata: string
+ features: string
+ }
+
+ class Metric {
+ ID: int
+ name: string
+ threshold: double
+ }
+
+ class TelemetryData {
+ ID: int
+ tool: TelemetrySource
+ outputFormat: TelemetryOutput
+ }
+
+ class TelemetrySource {
+ ID: int
+ }
+
+ class HumanFeedback {
+ ID: int
+ userID: int
+ feedback: FeedbackType
+ }
+
+ ' Relationships
+ Agent <|-- SolutionAgent
+ Agent <|-- CollaborationAgent
+ Agent <|-- SupervisionAgent
+ Agent <|-- ConsensusAgent
+
+ Agent --> "1..*" Task : accomplishes
+ Agent --> "0..*" Tool : exploits
+ Agent --> "1..*" Memory : has
+ Agent --> "0..*" Benchmark : evaluated by
+ Agent --> "1" Provider : provided by
+ Agent --> "0..*" Usage : uses
+ Agent --> "0..*" A2AProtocol : complies with
+
+ Benchmark --> "1..*" Metric : includes
+ TelemetryData --> Benchmark : collected on
+ TelemetryData --> HumanFeedback : stores
+ HumanFeedback --> Agent : evaluates
+ Usage <|-- Remote
+ Usage <|-- Local
+
+ @enduml
+
+
+ ```
+- 
+ collapsed:: true
+ {{renderer :plantuml_ickelqar}}
+ - ```plantuml
+ @startuml "summarization-teacher-student-example"
+
+ ' ====== STYLE (optional, safe to remove) ======
+ hide methods
+ hide stereotypes
+ skinparam shadowing false
+ skinparam packageStyle rectangle
+ skinparam class {
+ BackgroundColor White
+ BorderColor Black
+ }
+ skinparam object {
+ BackgroundColor White
+ BorderColor Black
+ }
+ skinparam note {
+ BackgroundColor #F9FAFB
+ BorderColor #E5E7EB
+ }
+
+ ' ====== CAPABILITY & PROTOCOL ======
+ object Capability_Summarization as "Capability: Summarization" {
+ id = C-SUMM
+ description = "Generate concise, accurate summaries of technical text"
+ supportedLanguages = "EN, IT"
+ }
+
+ object Proto_TeacherStudent as "InteractionProtocol: Teacher–Student v1" {
+ specUrl = "https://example.org/protos/teacher-student"
+ }
+
+ ' ====== TRAINING PHASE ======
+ package "Training Phase" as Training {
+ object TeacherA as "SupervisionAgent: Teacher A" {
+ ID = A-T1
+ name = "TeacherA"
+ role = "Prompt Explorer"
+ objective = "Generate/critique prompt candidates"
+ }
+
+ object TeacherB as "SupervisionAgent: Teacher B" {
+ ID = A-T2
+ name = "TeacherB"
+ role = "Prompt Critic"
+ objective = "Score and refine prompts"
+ }
+
+ object BenchTrain as "Benchmark: README Summarization (Train)" {
+ ID = B-TRAIN
+ datasetRef = "gh-readme-train"
+ protocolVersion = "1.0"
+ }
+
+ object KPI_Rouge as "PerformanceKPI: ROUGE"
+ object KPI_BERT as "PerformanceKPI: BERTScore"
+ object KPI_Lat as "PerformanceKPI: Latency"
+
+ object M_Rouge1 as "Metric {name=ROUGE-1, unit=score}"
+ object M_RougeL as "Metric {name=ROUGE-L, unit=score}"
+ object M_BERT as "Metric {name=BERTScore, unit=score}"
+ object M_Lat as "Metric {name=Latency, unit=ms}"
+
+ object UsageTrain1 as "AgentUsage: TrainRun#1" {
+ timestamp = 2025-08-05T10:12:00Z
+ durationMs = 8420
+ cost = 0.12
+ }
+
+ object TeleToolTrain as "TelemetryTool: TrainerLogger {format=JSON}"
+ object TeleRecTrain as "TelemetryRecord {kind=TRACE}"
+
+ ' Tools and memory used in training
+ object ToolRetriever as "Tool: DomainRetriever" {
+ authMethod = "API Key"
+ scopes = "read"
+ }
+ object STMem as "Memory {type=SHORT_TERM, scope=AGENT}"
+ object LTMem as "Memory {type=LONG_TERM, scope=SHARED, db=vectorDB}"
+
+ ' Links within training
+ TeacherA --> Capability_Summarization : exposes
+ TeacherB --> Capability_Summarization : exposes
+ TeacherA --> ToolRetriever : exploits
+ TeacherB --> ToolRetriever : exploits
+ TeacherA --> STMem : has
+ TeacherB --> STMem : has
+ TeacherA --> LTMem : has
+ TeacherB --> LTMem : has
+
+ TeacherA --> Proto_TeacherStudent : supports
+ TeacherB --> Proto_TeacherStudent : supports
+
+ BenchTrain --> TeacherA : evaluates
+ BenchTrain --> TeacherB : evaluates
+ BenchTrain --> KPI_Rouge : measures
+ BenchTrain --> KPI_BERT : measures
+ BenchTrain --> KPI_Lat : measures
+ KPI_Rouge --> M_Rouge1 : includes
+ KPI_Rouge --> M_RougeL : includes
+ KPI_BERT --> M_BERT : includes
+ KPI_Lat --> M_Lat : includes
+
+ UsageTrain1 --> TeacherA : agent
+ TeleToolTrain --> UsageTrain1 : collects
+ TeleToolTrain --> TeleRecTrain : produces
+
+ note right of UsageTrain1
+ Prompt candidates explored:
+ - "Summarize in 3 sentences..."
+ - "Provide a factual abstract..."
+ Stored with scores (ROUGE/BERT).
+ end note
+ }
+
+ ' ====== TESTING PHASE ======
+ package "Testing Phase" as Testing {
+ object Student1 as "SolutionAgent: Summarizer-1" {
+ ID = A-S1
+ name = "Summarizer-Abstractive"
+ role = "Apply best prompt"
+ objective = "Produce concise factual summary"
+ }
+
+ object Student2 as "SolutionAgent: Summarizer-2" {
+ ID = A-S2
+ name = "Summarizer-Extractive"
+ role = "Apply best prompt"
+ objective = "Produce concise factual summary"
+ }
+
+ ' Best prompt produced in training (abstracted as context stored in memory)
+ object BestPrompt as "Memory {type=LONG_TERM, scope=SHARED}" {
+ db = "vectorDB: best_prompt_embeddings"
+ }
+
+ object BenchTest as "Benchmark: README Summarization (Test)" {
+ ID = B-TEST
+ datasetRef = "gh-readme-test"
+ protocolVersion = "1.0"
+ }
+
+ object KPI_Rouge_T as "PerformanceKPI: ROUGE"
+ object KPI_Lat_T as "PerformanceKPI: Latency"
+ object M_RougeL_T as "Metric {name=ROUGE-L, unit=score}"
+ object M_Lat_T as "Metric {name=Latency, unit=ms}"
+
+ object UsageTest1 as "AgentUsage: TestRun#S1" {
+ timestamp = 2025-08-12T15:44:00Z
+ durationMs = 5100
+ cost = 0.08
+ }
+ object UsageTest2 as "AgentUsage: TestRun#S2" {
+ timestamp = 2025-08-12T15:45:00Z
+ durationMs = 4300
+ cost = 0.06
+ }
+
+ object TeleToolTest as "TelemetryTool: RuntimeLogger {format=JSON}"
+ object TeleRecTest1 as "TelemetryRecord {kind=LOG}"
+ object TeleRecTest2 as "TelemetryRecord {kind=TRACE}"
+
+ ' Tools used in testing
+ object ToolGlossary as "Tool: TechGlossary" {
+ authMethod = "None"
+ scopes = "public"
+ }
+
+ Student1 --> Capability_Summarization : exposes
+ Student2 --> Capability_Summarization : exposes
+ Student1 --> BestPrompt : has
+ Student2 --> BestPrompt : has
+ Student1 --> ToolGlossary : exploits
+ Student2 --> ToolGlossary : exploits
+ Student1 --> Proto_TeacherStudent : supports
+ Student2 --> Proto_TeacherStudent : supports
+
+ BenchTest --> Student1 : evaluates
+ BenchTest --> Student2 : evaluates
+ BenchTest --> KPI_Rouge_T : measures
+ BenchTest --> KPI_Lat_T : measures
+ KPI_Rouge_T --> M_RougeL_T : includes
+ KPI_Lat_T --> M_Lat_T : includes
+
+ UsageTest1 --> Student1 : agent
+ UsageTest2 --> Student2 : agent
+ TeleToolTest --> UsageTest1 : collects
+ TeleToolTest --> UsageTest2 : collects
+ TeleToolTest --> TeleRecTest1 : produces
+ TeleToolTest --> TeleRecTest2 : produces
+
+ note right of BestPrompt
+ Best prompt selected from training
+ (Teacher–Student protocol):
+ "Summarize in ≤3 sentences, preserve
+ factual references; avoid speculation."
+ end note
+ }
+
+ ' ====== CONSENSUS & GOVERNANCE (applied after testing) ======
+ object Cons as "ConsensusAgent: Summarization-Consensus" {
+ ID = A-C1
+ name = "ConsensusSummarizer"
+ }
+ object Gov as "GovernancePolicy: Accuracy-First" {
+ rules = "Prefer factual consistency over brevity; break ties by ROUGE-L"
+ }
+
+ Cons --> Gov : implements
+ Cons --> Student1 : aggregates candidate
+ Cons --> Student2 : aggregates candidate
+
+ note right of Cons
+ Applies GovernancePolicy across
+ candidate summaries from Student1/2:
+ - Compare ROUGE-L + factuality signals
+ - Select winner under policy rules
+ end note
+
+ @enduml
+
+ ```
\ No newline at end of file
diff --git a/pages/Deliverable D3.1.md b/pages/Deliverable D3.1.md
new file mode 100644
index 00000000..df73f77b
--- /dev/null
+++ b/pages/Deliverable D3.1.md
@@ -0,0 +1,8 @@
+tags:: #todoist-task, [[PROJECTS/MOSAICO]]
+date:: [[25-09-2025]] - 11:17
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ -
+ - ### Notes
+ -
\ No newline at end of file
diff --git a/pages/EditoringChairing___IEEE_Software_SW-2025-10-0161.md b/pages/EditoringChairing___IEEE_Software_SW-2025-10-0161.md
new file mode 100644
index 00000000..804835d1
--- /dev/null
+++ b/pages/EditoringChairing___IEEE_Software_SW-2025-10-0161.md
@@ -0,0 +1,66 @@
+type:: [[REVIEWS]]
+tags:: [[EditoringChairing]]
+year:: 2026
+venue:: [[IEEE SOFTWARE]]
+full-title::
+date-start:: [[23-12-2025]] - 16:08
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: 
+parent::
+todoist:: https://app.todoist.com/app/task/editor-assignment-ieee-software-sw-2025-10-0161-6f5jF5CVMvpVQ49g
+
+ - ### [[Comments]]
+ - FINAL DECISION (MAJOR)
+ - While all three reviewers recommend a minor revision, my assessment is more critical. In my view, the issues raised, particularly those highlighted in my comments, are substantive and require significant changes to the manuscript. Addressing them goes beyond polishing or clarification and calls for a more thorough revision of the paper. For this reason, I recommend a major revision.
+ -
+ - Reviewers find the paper well written and suitable for IEEE Software. However, several issues have been identified that can be summarized as follows:
+ - The user study is small and should be framed as a proof of concept rather than making strong assumptions about reducing development time or cognitive load.
+ - Early in the paper, the authors motivate the work by referring to the need for explainability, especially in the context of AI systems. Unfortunately, the paper lacks a specific, practical AI-based application, weakening its novelty and relevance. It is necessary to delineate the coverage of the pattern by improving the evaluation scenarios.
+ - A clear justification for the use of AOP is also needed. It is necessary to demonstrate how the pattern can be generalized beyond AOP-centric environments and languages.
+ - To summarize, a serious and major revision is needed to make the paper convincing beyond the application of the proposed idea to toy examples that are not representative of complex systems, as claimed at the beginning of the paper.
+ -
+ - Preliminary comment
+ - The three reviewers are largely aligned in judging the paper as **sound, well written, and suitable for IEEE Software**, but they consistently identify a set of **minor yet substantive weaknesses** that need addressing. The main criticality concerns the **evaluation and claims**: the user study is small, affected by ordering bias, and should be framed strictly as a *proof of concept*, avoiding strong claims about development-time reduction or cognitive load. A second recurring issue is **scope and positioning**: although the motivation targets AI-based systems and explainability, the paper lacks a **concrete, realistic AI-based application**, relying instead on generic or dummy scenarios, which weakens both novelty and relevance. Reviewers also ask for a **clearer justification of Aspect-Oriented Programming**, including why it was chosen and how the pattern could generalize beyond AOP-centric environments and languages. Finally, some **clarifications and minor fixes** are needed: better delineation of what the pattern does and does not cover (e.g., where explanations should be placed and based on which criteria), improved description of evaluation scenarios, and small presentation and reproducibility improvements (e.g., archiving supplementary material in a long-term repository). Overall, the issues are coherent, bounded, and addressable with a focused minor revision.
+ - > [[gpt3]]
+ The reviewers find the paper suitable for IEEE Software but point out some minor yet important weaknesses. They highlight concerns about the evaluation and claims made in the paper, suggesting that the user study should be considered a proof of concept rather than making strong assertions about reducing development time or cognitive load. Additionally, they note that the paper lacks a specific, practical AI-based application, weakening its novelty and relevance. Reviewers also seek a clearer justification for the use of Aspect-Oriented Programming and suggest improvements in delineating the pattern's coverage and enhancing evaluation scenarios. Overall, the issues raised are specific and can be addressed through a focused minor revision.
+ -
+ - **R1** / Minor
+ - Paper Summary:
+ This paper presents a design pattern for the integration of explanations using aspect-oriented programming (AOP) with the goal of standardizing and facilitating the development process of explanations, similar to what has been previously done for logging.
+ The authors implement a plugin for Visual Studio Code that supports the implementation of the pattern and preliminarily evaluate it by conducting an experiment involving seven participants. Results of the evaluation reveal benefits in terms of both development time and cognitive load.
+ - Strengths:
+ - The authors investigate a relevant and timely topic, i.e., providing a structural solution to manage explanations.
+ - The paper is very well-written, and it is also very easy to follow and understand.
+ - To present the pattern, the authors rely on the standard design pattern template.
+ - The manuscript comes with a link to a GitLab repo providing a sample implementation of the Explainer design pattern.
+ - I appreciate the presence of the threats to the validity section, where the authors admit as threats both the limited sample size and the ordering bias affecting the evaluation results.
+ - Points to Address:
+ - Due to the admitted threat of ordering bias, I would suggest stressing less the improvement in terms of development time and cognitive load. The evaluation should be viewed primarily as a proof of concept, without making any strong claims about the practical impact of adopting the pattern in real development scenarios.
+ - Since the Aspect-Oriented Programming is not standard in all modern development environments or languages, it would be good to motivate the reason why the authors focused on this paradigm, and the authors must discuss more the feasibility of extending this pattern to be used in different environments/languages.
+ - Overall Summary: This manuscript presents a novel solution to the integration of the explanations issue within complex software systems. While the evaluation is preliminary, the design is sound, and the accompanying tooling makes it a practical contribution for the IEEE Software audience. However, there is a need to work a little bit more on the writing by smoothing the results of the evaluation and by justifying the use of AOP more effectively, as well as explaining how it can be adapted to different environments and languages.
+ - **R2** / Minor
+ - Overall merit
+ - The proposed pattern is well-described and implemented in a Visual Studio Code plugin. However, the presented scenarios are somehow disconnected compared to the original motivation of the paper, i.e., assisting developers for AI-based systems. In this respect, the paper misses a concrete example of an AI-based application and how the proposed design pattern can concretely help developers. In addition, the pilot applications used in the user study are vaguely described. While the proof-of-concept is suitable to showcase a generic usage of the pattern, I strongly recommend authors to present a concrete AI-based application in which the Explainer Pattern can be used.
+ - Novelty
+ - While the proposed pattern can be helpful in practice, the paper does not present a concrete example applied to an actual AI-based project. In addition, existing challenges are not mentioned, and the authors should discuss which benefits the AOP pattern can bring to developers.
+ - Soundness
+ - Although the user study is small, it is adequate as a proof-of-concept. However, the scenario application is not reported, and, by looking in the provided repo, it seems limited to dummy projects. As mentioned, the authors should present a concrete example in an AI-based project, as it is the target domain of the approach. Concerning the evaluation metrics, only the required time is reported, although it might be useful to report how practitioners perceive the usefulness of the generated explanations.
+ - Relevance
+ - This paper proposes a novel design pattern with a minimal tool-based implementation. Therefore, it is relevant to the journal’s aims and scope.
+ - Verifiability
+ - The replication package is available on the GitLab repository, thus fostering the reusage of the tool.
+ - Presentation
+ - The paper is overall well-written and easy to follow.
+ - **R3** / Minor
+ - The paper addresses the scattered nature of code explanations and the need for a unifying structure, a relevant problem. The proposed design pattern is well motivated, follows established pattern description guidelines, and is likely to be actionable for practitioners. The evaluation reports promising initial results.
+ - The evaluation, however, is limited in scope. It considers only the integration of explanations using the pattern, and does not address the retrieval or use of these explanations. In addition, the study is small-scale (7 participants), with most participants being students or trainees, which restricts the extent to which conclusions can be generalized. This is discussed as part of the threats to validity.
+ - While generally clear, some aspects of the pattern description would benefit from further clarification. The pattern description states that explanations are stored "at all points that could be unclear (e.g., when executing a complicated method)", but it remains unclear how complexity is defined or measured. Moreover, since the motivation emphasizes the end-user, it is not obvious whether method complexity is the appropriate criterion for deciding where explanations are needed. If this is intentionally out of scope for the pattern, I would suggest to explicitly state this earlier in the paper to better delineate its scope.
+ - Minor comments:
+ - The supplementary material should be archived in a long-term repository such as Zenodo rather than GitLab
+ - For the feasibility evaluation, either cite the bachelor's thesis explicitly or consider omitting mentioning it
+-
+-
+-
\ No newline at end of file
diff --git a/pages/EditoringChairing___IEEE_Software_SW-2025-10-0163.md b/pages/EditoringChairing___IEEE_Software_SW-2025-10-0163.md
new file mode 100644
index 00000000..406d5bc5
--- /dev/null
+++ b/pages/EditoringChairing___IEEE_Software_SW-2025-10-0163.md
@@ -0,0 +1,124 @@
+type:: [[REVIEWS]]
+tags:: [[💺EditoringChairing]]
+year:: 2025
+venue:: [[IEEE SOFTWARE]]
+full-title::
+date-start:: [[23-12-2025]] - 15:34
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: 
+parent::
+todoist:: https://app.todoist.com/app/task/editor-assignment-ieee-software-sw-2025-10-0163-6f5jF5HM5hW6cPF8
+
+ - ### [[Comments]]
+ - **Final decision**
+ - Reject
+ - Reviewers agree that the paper is about a relevant and interesting problem. However, the paper cannot be accepted because of several issues that can be summarized as follows:
+ - The main message of the paper is not effective because it fails to connect with the existing work on model and DSL evolution, and relies heavily on a specific DSL family. It is unclear whether the specificities of the considered languages can be a source of bias or affect the generalizability of the discussion.
+ - Following the previous point, the lack of novelty makes it challenging to understand the general and broader implications beyond the specific case discussed. The lessons learned section tries to generalize the findings, but it is not convincing.
+ - The evaluation is informal and lacks details. I understand the page constraint plays a role here; however, reviewers identified overstatements without sufficient evidence.
+ - Technical and conceptual issues are identified, including inaccuracies in the MDE tool discussion and insufficient justification for using LLMs over traditional methods in specific tasks.
+ -
+ - **Preliminary comments from those of the reviewers**
+ - Across the three reviews, several converging criticalities emerge. First, the paper’s **positioning and core message are unclear and potentially misleading**: the link to *DSL evolution* is weak, the contribution is tightly bound to a single DSL family (USchema/Athena–Orion), and the paper risks suggesting that probabilistic LLMs can replace well-established, deterministic DSL tooling without adequately discussing limitations, risks, or boundaries. Second, the **novelty and contextualization are insufficient**, with limited engagement with the substantial literature on DSL/model co-evolution and related MDE approaches, making it hard to assess what generalizes beyond this specific experience. Third, the **evaluation is informal and under-specified**: claims are often too strong given the lack of methodological detail, limited scale, absence of analysis of non-determinism, and no clear quantification of effort reduction. Finally, there are **technical and conceptual issues**, including inaccuracies in the discussion of MDE tooling, unclear justification for using LLMs over traditional approaches in some tasks, and missing discussion of key aspects such as data migration, reliability, and broader societal or ecological implications.
+ - > [[gpt3]]
+ The text highlights several key criticisms from three reviews. Firstly, the paper's main message is unclear and may be misleading, as it fails to effectively connect to DSL evolution and relies heavily on a specific DSL family. Secondly, the lack of novelty and context in the paper makes it challenging to understand its broader implications beyond the specific case discussed. Thirdly, the evaluation is deemed informal and lacks specific details, leading to overstatements without sufficient evidence. Lastly, technical and conceptual issues are identified, such as inaccuracies in MDE tool discussion and insufficient justification for using LLMs over traditional methods in certain tasks.
+ - **REVIEWER 1** / REJECT
+ - The paper is generally well-written and sound, and it addresses an interesting and timely topic.
+ It has however a few important problems that hamper my acceptance.
+ - The paper claims to evaluates GPT-4o in DSL evolution (in the title and throughout the paper). I had some difficulties understanding that it actually addresses two (very different) classes of tasks: tasks for DSL users (mainly script generation) and DSL developers (mainly script transformation). The link with DSL evolution is not clear, and feels forced.
+ - While the paper is quite convincing on the tasks for DSL users, I think it is deeply misleading on the tasks for DSL developers. It seems to promote the idea that LLMs should be used to replace traditional DSL tooling like compilers or translators. It completely omits discussing all the drawbacks of such idea. Replacing deterministic translators with probabilistic tools like LLMs would require a much more extensive experimentation. Ecological and societal issues are never mentioned.
+ - As a less critical issue, the paper should better highlight the peculiarities of the two considered DSLs. While on the surface these DSLs seem very similar to other languages (that the LLM "understands" out-of-the-box) I suppose that they have some specific features that need to be taught the LLM. They should be detailed.
+ - Finally, reference [1], that contributes to motivating the paper, is just a very short blog post, and does not contain much evidence of the claim.
+ - In summary, while the topic is interesting, the paper's core message may be misleading to practitioners, and this hampers in my opinion the paper's publication.
+ - **REVIEWER 2** / MAJOR
+ - ----------------------------------------
+ Summary of the submission.
+ ----------------------------------------
+ The paper presents an experience report on using GPT-4o to support the evolution and use of two domain-specific languages from the USchema family: Athena (for database schema specification) and Orion (for schema evolution). The article proposes a four-step prompting strategy to teach the LLM how to generate DSL scripts and translate them to and from various database technologies. Through two validation experiments, the paper reports that GPT-4o produced syntactically correct and semantically valid outputs in nearly all cases, with only minor issues. As such, the paper argues that this approach can reduce the manual effort traditionally required to implement and maintain complex model-to-text transformations. The paper concludes with lessons learned about the strengths and limitations of combining LLMs with DSL engineering.
+ ----------------------------------------
+ Detailed comments
+ ----------------------------------------
+ The paper describes an experience report on the use of large language models to support the evolution of domain-specific languages, focusing on two DSLs within the USchema family. Overall, I found the article quite interesting and divulgative enough to justify a submission to IEEE Software. I appreciated the idea of reporting an experience-driven study to discuss the broader theme of how LLMs can be integrated into DSL engineering workflows. The lessons learned are significant for the community and, more generally, the paper presents insights that are timely and relevant for researchers and practitioners exploring hybrid AI-assisted software development processes. The article effectively reports on the opportunities and challenges of applying LLMs to non-trivial engineering tasks; its form is clear and accessible to a broad audience. So, in this sense, I believe the article is aligned with the objectives of the journal and has the potential to represent a valuable contribution.
+ At the same time, some aspects should be made more explicit or clarified. More specifically, let me report my major concerns in the following - please note that these issues are listed in no particular order of severity.
+ - (1) In the 'Evaluation and Results' section, the article describes the main findings coming from the two validation experiments discussed. While reading this section, I found the claims to be a bit too bold with respect to what is actually reported. In particular, the paper frequently uses expressions such as "complete correctness in all schema transformations" or "full correctness" across multiple target languages. However, the section does not provide enough methodological detail to support such strong claims.
+ - For instance, the paper does not specify (1) how correctness was operationalized (e.g., syntactic vs. semantic correctness criteria, classification of errors, acceptance thresholds); (2) how many test cases were used per transformation direction, nor whether these cases cover the full combinatorial variability of the DSL features; (3) how independence between training examples and evaluation cases was ensured, since few-shot examples may inadvertently encode the exact mapping rules being tested.
+ - I fully understand that these details may have been omitted because of the strict page limitation constraints imposed by the journal. Nonetheless, I would still suggest to briefly summarize the evaluation procedures to better contextualize the reported results. To save some space, the article may consider combining the last two sections (Lessons Learned and Conclusion) together.
+ - (2) As far as I can tell, the DSLs evaluated (Athena and Orion) belong to the same USchema family, which may make generalization easier than for unrelated DSLs. This is basically due to the very nature of the experience, which targets cases addressed in previous research. Yet, a more cautious formulation of the claims would make the contribution stronger. In this sense, I would just ask to more explicitly acknowledge that the experience is limited to cases belonging to the same USchema family and that, for this reason, the considerations reported may not fully generalize to other DSLs.
+ - (3) I appreciated that, in Figure 2, the article reports the prompting and validation strategy. However, some aspects of the prompt strategy are not explicitly discussed. In particular, the article does not address the key concern of LLM non-determinism and how this affects the reliability of the proposed workflow: LLMs can produce different outputs across runs even when using the same prompt, depending on temperature, sampling strategy, and internal stochasticity. As such, the paper should clearly (and briefly) discuss (1) whether the experiments have been conducted in a controlled environment (e.g., by ixing temperature, top-p, or other decoding parameters); (2) whether the reported successful transformations reflect single-run outputs or consistent results across multiple executions; (3) how often incorrect or inconsistent outputs occurred during experimentation, and whether prompt refinements were needed to stabilize behavior. I honestly believe that these details would be essential to assess the overall soundness of the conclusions drawn in the experience report.
+ - (4) Similar considerations may be reported when considering the effort reduction discussion. While the paper convincingly argues that the LLM-based workflow avoids the need to manually implement and maintain M2T transformations, the evidence provided is largely qualitative and does not fully report the magnitude of effort saved. For example, the article reports the lines of code of traditional transformations and the complexity of certain SCO mappings, but it does not quantify the actual prompting effort, the number of iterations required to achieve stable outputs, or the time spent in validation and correction. These aspects should be somehow accounted in the effort analysis, as they are preliminary activities to reach a level where the LLM may actually be exploited.
+ - So, in conclusion, I think the paper represents a nice contribution with effective and timely insights for the research community. The points above are relatively minor, assuming they simply reflect clarifications that were not included in the original manuscript due to space limitations. My recommendation is that the paper undergoes a revision to incorporate these clarifications.
+ - **REVIEWER 3** / Reject
+ - This article reports on an experience using large language models (LLMs) to support the evolution of two domain-specific languages (DSLs), Athena and Orion, by means of a structured prompting strategy. The paper argues that LLMs and DSLs are complementary: LLMs reduce engineering effort, while DSLs provide the formal backbone needed to ensure correctness and maintainability. The topic is timely and relevant for the IEEE Software readership, and the paper is generally well written and easy to follow.
+
+ However, while the paper presents an interesting experience report, several conceptual, methodological, and positioning issues significantly limit the clarity and strength of its contribution. In its current form, the paper lacks adequate contextualization within the literature on model and DSL co-evolution, provides an unclear justification for the use of LLMs over traditional MDE techniques, and presents an evaluation that is informal and insufficiently grounded.
+
+ Strengths
+ The paper addresses a timely topic at the intersection of DSL engineering and LLM-based automation.
+ The experience-based nature of the article aligns well with the IEEE Software audience.
+ The paper is generally readable and written in an accessible style.
+
+ Major Concerns
+ A major limitation of the paper is the lack of contextualization with respect to the extensive body of work on model and DSL co-evolution. The paper frames the contribution mainly as an application of LLMs to DSL evolution. However, it does not sufficiently relate this to existing research on co-evolution between models, metamodels, transformations, and instances.
+ Several recent and closely related works are not discussed, including:
+ Kebaili et al. (2024) [1], which empirically studies the use of LLMs for metamodel and code co-evolution.
+ Zhang et al. (2025) [2], which explicitly investigates LLM support for co-evolution between DSL definitions and instances.
+ Moreover a recent sutdy [3] investigated the usage of LLMs in various MDE tasks.
+ Without positioning the proposed approach with respect to this literature, it remains unclear what is novel beyond applying LLMs to a specific DSL family.
+
+ The paper's contribution is difficult to assess. The study is tightly coupled to a specific DSL family (Athena/Orion) and a specific data modeling context, yet the paper does not clearly articulate:
+ which insights generalize beyond this particular notation,
+ which lessons are specific to the USchema-based DSLs,
+ and how the approach compares to existing DSLs and modeling languages that already support schema evolution and persistence-layer abstractions.
+ There is a substantial body of work on modeling languages and frameworks for persistence, schema evolution, and query adaptation (e.g., Fink et al., 2020) [4] that is not discussed, nor are the differences between those approaches and Athena/Orion clarified.
+
+ The sidebar explaining how DSL generators are built in MDE contains several technical inaccuracies and inconsistencies:
+ Acceleo is presented as an example of a model-to-model (M2M) transformation language, whereas it is primarily a model-to-text (M2T) template-based language.
+ The statement that generators “often consist solely of an M2T transformation when the mapping is not complicated” is misleading; M2T transformations can be highly complex and involve sophisticated mappings.
+ The overall explanation risks confusing non-expert readers and oversimplifying well-known MDE practices.
+
+ I recommend either revising this sidebar substantially for technical accuracy or removing it altogether.
+
+ Box 1 lists several automated tasks (e.g., generating SQL, CQL, or MongoDB schemas from Athena scripts) that correspond to classic M2T transformations. It is not clearly justified why LLMs are preferable to established template-based approaches in these cases. As presented, the use of LLMs sometimes feels like “using a sledgehammer to crack a nut.”
+ The paper would benefit from a clearer discussion of:
+ which tasks genuinely benefit from LLM-based automation,
+ which tasks are already well supported by traditional MDE techniques,
+ and where the boundary lies between the two.
+
+ While the paper introduces a four-step prompting strategy, it does not explain how these steps were identified, nor how each step contributes to the final outcome. The strategy is presented as a design choice rather than as the result of a systematic process.
+ In particular:
+ - There is no analysis of alternative prompting strategies (e.g., few-shot vs. grammar-only, with or without documentation).
+ - The impact of each step on correctness or coverage is not evaluated.
+ - An ablation study would be highly beneficial to understand which components of the strategy are essential.
+ Moreover, it is unclear why the authors used ChatGPT instead of other LLMs (even freely available). This selection should be discussed throughout the paper.
+ Without this, the prompting strategy remains anecdotal rather than principled.
+
+ Although a rigorous evaluation is not mandatory for an IEEE Software article, the evaluation section, as presented, is informal and difficult to interpret:
+ The goals of the two experiments are not clearly defined.
+ The contribution of each experiment to validating the approach is unclear.
+ The reported examples are relatively simple (often fewer than ten entities), making it hard to assess how the approach scales to realistic evolution scenarios.
+ As a result, the evaluation does not convincingly demonstrate the challenges of real-world model and DSL evolution, nor the advantages of the proposed approach in such settings.
+
+ It is unclear whether the approach supports data migration in addition to schema evolution. While Orion generates DDL and DML commands, the paper does not explicitly discuss:
+ whether data consistency is preserved,
+ how data migration is validated,
+ or what guarantees are provided in practice.
+ Given that data migration is a central concern in schema evolution, this omission is significant.
+
+ Minor Comments:
+ The GitHub repository is referenced late in the paper and should be introduced earlier.
+ The repository contents mix English and Spanish examples, which reduces the performance of the training part.
+ Some claims in the text (e.g., the number of entities in examples) appear inconsistent with the repository.
+ Minor editorial issues (dates, phrasing, and references) should be addressed.
+ Overall Recommendation:
+ The paper addresses a relevant topic and reports an interesting practical experience. However, the lack of proper contextualization, unclear contribution, technical inaccuracies, and weak evaluation substantially limit its current impact.
+
+ [1] Z. K. Kebaili, D. E. Khelladi, M. Acher, and O. Barais, “An empirical study on leveraging LLMs for metamodels and code co-evolution,” Journal of Object Technology, vol. 23, no. 3, pp. 1–14, 2024.
+
+ [2] W. Zhang, R. Hebig, and D. Strüber, “Leveraging LLMs to support co-evolution between definitions and instances of textual DSLs,” 2025.
+ [3] Di Rocco, J., Di Ruscio, D., Di Sipio, C. et al. On the use of large language models in model-driven engineering. Softw Syst Model 24, 923–948 (2025). https://doi-org.univaq.idm.oclc.org/10.1007/s10270-025-01263-8
+ [4] J. Fink, M. Gobert, and A. Cleve, “Adapting Queries to Database Schema Changes in Hybrid Polystores,” in Proc. IEEE 20th Int. Working Conf. on Source Code Analysis and Manipulation (SCAM), 2020, pp. 127–131.
+ -
+- 
\ No newline at end of file
diff --git a/pages/GOALS-TODOIST.md b/pages/GOALS-TODOIST.md
index f8c17d41..c6fdc287 100644
--- a/pages/GOALS-TODOIST.md
+++ b/pages/GOALS-TODOIST.md
@@ -26,7 +26,7 @@ progress:: {{renderer :todomaster}}
todoist-desc:: ✉: http://s.diruscio.org/u9fPP
todoist-id:: [7602643924](https://app.todoist.com/app/task/7602643924)
- TODO [[PAPERS/2024-ONTOLOGY-AI]]
- todoist-id:: [7658261760](https://todoist.com/app/task/7658261760)
+ todoist-id:: [7658261760](https://app.todoist.com/app/task/7658261760)
- TODO NIER paper on how our two-level agent architecture
- TODO [#C] [[PAPERS/2024-BiasInRSSEwithLLM]]
todoist-id:: [7688827022](https://todoist.com/app/task/7688827022)
@@ -95,10 +95,10 @@ progress:: {{renderer :todomaster}}
CLOCK: [2025-05-25 Sun 19:29:04]--[2025-05-25 Sun 19:29:05] => 00:00:01
:END:
- TODO Nuova edizione del PinKamp
- todoist-id:: [8644892780](https://app.todoist.com/app/task/8644892780)
todoist-desc:: From: giuseppe.dellapenna@univaq.it
+ todoist-id:: [8644892780](https://app.todoist.com/app/task/8644892780)
- TODO ICSE 2026 Program Committee
-- TODO [[PAPERS/Experience-Report-to-EMSE]]
+-
- DONE [[PAPERS/FSE2025-NIER]]
id:: 68362092-aafa-44b6-83b2-8f4a163dd2a0
- TODO [#C] Dottorato industriale riservato a dipendenti
@@ -107,13 +107,14 @@ progress:: {{renderer :todomaster}}
- TODO Richiesta afferenza al Collegio di Mauro Cappelli, ricercatore all’Enea
- TODO [#C] Vedere per compenso per la De Masi
- TODO [#B] [[PAPERS/Journal-Green-Paper]]
-- TODO [#A] Rivedere Composizione Collegio
+- TODO [#C] Rivedere Composizione Collegio
todoist-id:: [8750396305](https://app.todoist.com/app/task/8750396305)
+ SCHEDULED: <2026-01-12 Mon>
:LOGBOOK:
CLOCK: [2025-06-04 Wed 21:44:39]--[2025-06-04 Wed 23:46:56] => 02:02:17
:END:
- TODO [#C] [[PAPERS/ABSTRACT-ENGINEERING]]
-- TODO [#C] [[PAPERS/TOSEM2025-TESORO]]
+-
- TODO [#B] [R: Scheda XLI ciclo e richieste di afferenza al Collegio](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAHueDXAQAA&exvsurl=1&viewmodel=ReadMessageItem)
- DONE [#B] Informiamo che entro e non oltre il ciascun Coordinatore dovrà caricare sulla piattaforma telematica dedicata: - il verbale del collegio dei docenti con esplicita ammissione all’esame finale; - la copia della tesi finale del dottorando; - il verbale della commissione dell’esame finale.
id:: 68584e9f-280a-4a6a-afab-e3a5172e1586
@@ -128,9 +129,9 @@ progress:: {{renderer :todomaster}}
todoist-desc:: From: noreply-icse2026@hotcrp.com
todoist-id:: [9001461730](https://app.todoist.com/app/task/9001461730)
- TODO Dottorato industriale
- todoist-id:: [9006116046](https://app.todoist.com/app/task/9006116046)
id:: 6823acce-6cc8-4da4-9a2c-5ffacf92e168
- SCHEDULED: <2025-05-22 Thu>
+ todoist-id:: [9006116046](https://app.todoist.com/app/task/9006116046)
+ SCHEDULED: <2025-05-24 Sat>
- DONE [#B] Models Conference 2025
id:: 682ecc99-b356-4086-9ff8-4e4736018009
SCHEDULED✔️ <2025-05-26 Mon>
@@ -151,13 +152,13 @@ progress:: {{renderer :todomaster}}
- DONE [[PAPERS/2025-Survey-MOSAICO]]
id:: 6832257a-63a4-4c89-8353-25f0e94caa51
- TODO [#B] Sinergia con GSSI
-- TODO [#B] SLIDES DI PRESENTAZIONE
+- DONE [#B] SLIDES DI PRESENTAZIONE
todoist-desc:: Con HOWTO etc.
todoist-id:: [9193848277](https://app.todoist.com/app/task/9193848277)
-- TODO [#A] [[MODELS Journal-First-track + 1 more]]
+- DONE [[MODELS Journal-First-track + 1 more]]
todoist-desc:: From: noreply@researchr.org
todoist-id:: [8933176944](https://app.todoist.com/app/task/8933176944)
- SCHEDULED: <2025-07-15 Tue>
+ SCHEDULED: <2025-09-19 Fri>
:LOGBOOK:
CLOCK: [2025-06-04 Wed 21:44:10]--[2025-06-04 Wed 23:46:56] => 02:02:46
:END:
diff --git a/pages/Giornata di presentazione del dottorato.md b/pages/Giornata di presentazione del dottorato.md
new file mode 100644
index 00000000..73ac20a3
--- /dev/null
+++ b/pages/Giornata di presentazione del dottorato.md
@@ -0,0 +1,51 @@
+tags:: #todoist-task, [[SERVICES/PHDICT]]
+page-type:: [[SERVICES/PHDICT]]
+date:: [[26-09-2025]] - 11:14
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ - DONE Preparare slides di presentazione da mostrare ad un evento per tutti gli studenti che andremo ad organizzare per metà Novembre (online?)
+ id:: 68df8e5d-fbdf-4070-ba1e-3a748f11766a
+ - Mail suggerimento VITTORIO
+ - Slides di presentazione del corso con un po' di numeri / analisi
+ - Spiegare funzionamento selezione corsi su esse3
+ - Sezione seminari del sito
+ - Questione preghiera e docoro
+ - Richiesta di missione / disponibilità economica
+ - Gli studenti dovranno caricare il proprio piano entro il 31/01/2025
+ - quelli del primo anno potranno rivedere il piano del secondo e terzo anno e potranno aggiungere anche l'offerta nuova
+ - DONE Trovare location
+ id:: 68df8e5d-3e7c-4377-8a9c-151d1a6f97ae
+ - Aula Seminari Blocco Zero
+ - DONE Individuare una data
+ id:: 68df8e5d-e7d8-4964-9f1a-765fdd2a28e3
+ - DONE Pensare a connessioni da remoto per studenti che ancora non hanno il visto
+ id:: 68df8e5d-3f53-4e39-bb5c-c0dbe9368211
+ :LOGBOOK:
+ CLOCK: [2025-11-30 Sun 20:50:47]--[2025-11-30 Sun 20:50:48] => 00:00:01
+ :END:
+ - DONE Fare una locandina?
+ - ### Notes
+ - Direi un paio di ore con i seguenti interventi
+ - Direttore del Dipartimento / Rettore ???
+ - Coordinatore
+ - Durata del dottorato
+ - Report annuali, cosa e' richiesto
+ - Missioni
+ - Missioni lunghe (maggiorazione del 50%)
+ - Qualche numero anche presi dall'ultimo rapporto
+ - Responsabili del Reference Group
+ - Direi che ogni reference group faccia una sorta di overview dei risultati / ricerche?
+ - Collaborazioni?
+ - Qualche nostro studente
+ - Primo/Secondo anno, Post-doc
+ - Programma di massima:
+ - Inizio ore 10:30
+ - Direttore 5min
+ - Coordinatore / Vice 20min
+ - Responsabili reference groups 20min
+ - Studenti 5min
+ - Q/A 10min
+ - Fine ore 11:30
+ - Collegio 11:30 -> 13:00
+ - Light lunch ore 13:00
\ No newline at end of file
diff --git a/pages/Grafana-handOn.md b/pages/Grafana-handOn.md
new file mode 100644
index 00000000..d2a7b1b1
--- /dev/null
+++ b/pages/Grafana-handOn.md
@@ -0,0 +1,12 @@
+tags:: [[TEACHING/SE4IOT]]
+date:: [[12-12-2025]]
+
+ - Start Grafana
+ - Create a new datasource selecting InfluxDb (Flux)
+ - Create a new dashboard and play with the query from InfluxDB
+ - Show the details of the Forerst Fire Detection
+ - To see the variables, follow the Settings link
+ - 
+ - Add a new variable and see what happens
+ - Discuss the definition of the forest and area varliables
+ - 
\ No newline at end of file
diff --git a/pages/ICSE2026-paper1356.md b/pages/ICSE2026-paper1356.md
new file mode 100644
index 00000000..34c0ebe5
--- /dev/null
+++ b/pages/ICSE2026-paper1356.md
@@ -0,0 +1,35 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: Senate: Policy-Driven Change Management in Model Based Systems Engineering (MBSE)
+date-start:: [[17-09-2025]] - 23:02
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Senate: Policy-Driven Change Management in Model-Based Systems Engineering]]
+parent::
+todoist:: https://app.todoist.com/app/task/1356-senate-policy-driven-change-management-in-model-based-systems-engineering-m-6cVHmvQ33PC6XXV8
+
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - This paper presents Senate, a domain-specific language to specify policies guiding the propagation of model changes in contexts characterized by different and potentially heterogenous models, which are managed by different teams in a collaborative and distributed modeling scenarios. The approach has been validated by discussing its application in a setting characterized by FACE and AADL specifications.
+ - ### Strengths
+ - + Relevant problem in Model Based Software Engineering
+ - + Interesting DSL for specifying governance constraints in collaborative modeling settings
+ - ### Weaknesses
+ - - The novelty of the proposed DSL with respect to existing approaches in change propagation, bidirectional transformations, and model synchronization is not clearly presented.
+ - - Prior work in the MDE community on collaborative modeling, model differencing, incremental synchronization, and consistency management is not considered and only superficially mentioned in the limitation and related work sections of the paper.
+ - The evaluation is underdeveloped: critical details are missing about the granularity of changes (e.g., are structural features handled separately from classes?) and how different levels of model abstraction are affected by policy enforcement.
+ - ### Detailed comments for authors
+ - Novelty: The concept of policy-driven change management in FMoM is potentially novel, but the authors do not discuss Senate with respect to existing synchronization languages or bidirectional transformation frameworks. The DSL for specifying change propagation constraints could be interesting, but the paper does not highlight what makes it unique compared to other policy or transformation languages. Thus, the paper require a major revision to make a clear contribution statement, explicitly clarifying what is new in Senate vs. existing IMT tools, pattern matching systems, or role-based modeling constraints.
+ - Rigor: The policy semantics are underexplained, especially regarding the granularity of collaborative changes: e.g., what happens if a subset of a class’s structural features violates a policy? Does the whole class delta get discarded? Senate DSL should be compared with existing approaches managing the collaborative editing of modeling artifacts.
+ - Relevance: The work is highly relevant to collaborative and federated modeling, particularly in safety-critical domains. However, the relevance of the proposed approach is compromised by the lack of discussion and comparison of Senate with prior work. Without showing how Senate improves over or complements existing tools, it’s difficult to assess practical impact.
+ - Verifiability & transparency: The paper refers to [Anonymized Repository - Anonymous GitHub](https://anonymous.4open.science/r/senate-icse-EDED) which contains the EMF based implementation of the approach. However, no details are given on the performed experiments, successfull cases, encountered limitations, etc.
+ - Presentation: Overall, the paper is well structured, even though it requires major rewriting to improve the readability of the paper by giving concrete examples and experiments by comparing the proposed approach with existing techniques. It is not clear what are the strenghts and the limitations of Senate with respect to existing approaches manageing collaborative modeling.
+ - Questions:
+ - Q1: How does Senate improve over existing synchronization languages and transformation frameworks for managing change propagation across heterogeneous models?
+ - Q2: What is the level of granularity supported by the Senate framework when changes are partially valid (e.g., some attributes allowed, some forbidden within the same class)? How are composite changes handled?
\ No newline at end of file
diff --git a/pages/ICSE2026-paper1656.md b/pages/ICSE2026-paper1656.md
new file mode 100644
index 00000000..46c72e95
--- /dev/null
+++ b/pages/ICSE2026-paper1656.md
@@ -0,0 +1,81 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs
+date-start:: [[09-09-2025]] - 15:31
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Multi-Agent LLM Collaboration for Enhancing Unit Test Generation Using Repository-Aware Knowledge Graphs]]
+parent::
+todoist:: https://app.todoist.com/app/task/1656-multi-agent-llm-collaboration-for-enhancing-unit-test-generation-using-repo-6cVHmvX8F6V23H48
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - The paper presents TestAgent, a multi-agent system (MAS) based on LLMs for the automated unit test generation. The proposed MAS consists of three agents (requirement planner, test generator, reviewer) that collaborate while relying on external tool APIs for executing generated tests, and a knowledge graph that includes fine-grained dependencies of the repository storing the code of the method under analysis. The authors have performed experiments on Java and Python projects, showing that TestAgent outperforms existing approaches under different dimensions.
+ - ### Strengths
+ - + Interesting and effective use of a multi-agent system for a critical software engineering task
+ - + Rich experiments including an ablation study showing the contribution of each agent to the unit test generation process
+ - + Extensive comparison with existing approaches
+ - ### Weaknesses
+ - - Some claims are overstated, especially concerning outperforming all baselines across all metrics (e.g., EvoSuite outperforms TestAgent on some dimensions).
+ - - The multi-agent collaboration protocol is not specified. How agents interact, share state, and resolve conflicts is not well articulated.
+ - - Several terminologies (e.g., “practicality”, “adaptive states”, “real-world industrial projects”) are ambiguous and need better definition
+ - - The mutation process is unclear; more details on fault injection are necessary to validate fairness of the evaluation.
+ - - The scalability of "node-per-line" approach is not discussed
+ - ### Detailed comments for authors
+ - Novelty: The usage of the repository-aware knowledge graph sounds promising, even though it is not clear how agents technical exploit it. Many existing tools can extract AST or dependency graphs out of source code. It is not clear if authors essentially rely on existing graph-construction techniques, or if they had to devise a new one because of some specific requirements that are not elaborated in the text. Nevertheless, the usage of MAS for unit test generation is novel.
+ - Rigor: The evaluation is extensive, covering multiple metrics and configurations (LLMs, baselines, languages). That said, certain evaluation design choices are unclear:
+ - How exactly mutation faults are injected? ([p.7, “Mutation score”])
+ - How were datasets split to mitigate LLM memorization or contamination?
+ - What constitutes a “real-world industrial project”? ([p.6])
+ - “Adaptability” in RQ3 is misleading. In particular, RQ3 does not demonstrate adaptability. What is shown is essentially that TestAgent can be executed with different models, but without clarifying what “robustness” (as mentioned in RQ3) actually means in this context. Could you specify the concrete efforts required to integrate new models? For instance, what operations or modifications were needed in the system to make different LLMs work within TestAgent? While Table 5 compares models on the same tasks and metrics, it does not provide insights into the potential challenges, limitations, or architectural adjustments necessary when switching models.
+ - **Relevance**: The planner–generator–reviewer design, together with tool APIs, is potentially relevant to practitioners. The focus on realistic workflows, integration with external tools, and support for multiple LLMs and languages (Java, Python) enhance applicability.
+ - Verifiability & transparency: A replication package is cited and online. However, key implementation details are missing in the text:
+ - What MAS framework is used?
+ - How are the tools (e.g., check_syntax, calculate_coverage) integrated and invoked autonomously?
+ - What steps are required to plug a new LLM into the system?
+ - Presentation: Overall, the paper is well written. However, I have some suggestions for improvement. In particular, the motivation for the graph should appear earlier. Statements like "substantially outperforms” (pag. 7) should be moderated especially when EvoSuite wins in different cases.
+ - Detailed comments:
+ - page 1 - "captures fine-grained dependency relations through graph edges": How are these dependencies used in practice? Clarify their concrete usage.
+ page 2 - "voting-based diagnostic mechanism": Mechanism unclear; how is voting implemented? Among agents or heuristics?
+ page 3 - "graph serves as … representation": The goal of the graph should be presented earlier.
+ page 3 - "node corresponds to a line of code": Scalability of this design is questionable.
+ page 3 - "Extensive Evaluation … industrial scenarios": What qualifies as “industrial” here? Real companies? Internal repositories?
+ page 4 - "dynamic analysis … adequacy checks…": How do agents access runtime info? Through what interface or protocol?
+ page 5 - "adaptive states": Adaptive in what sense? Not explained.
+ page 5 - "assesses whether current context is sufficient…": Define what “sufficient” means and how it is determined.
+ page 7 - "Mutation score": How is mutation done? What tools or techniques are used? Potential bias?
+ page 7 - "Readability and Usability … aggregated": How is the aggregation done? What weights? Based on what criteria?
+ page 7 - "TestAgent using GPT-4o … two alternative LLMs": Clarify whether only RQ3 used alternative LLMs.
+ page 7 - "substantially outperforms baselines": This should be rephrased. On some metrics, EvoSuite is better.
+ page 8 - "Model Adaptability": The name of the RQ is misleading. This is model portability. What changes are needed to support a new model?
+ page 8 - "data leakage risk": Why is this a concern? What kind of leakage?
+ page 8 - "information is completely unseen": Unverifiable claim unless explicit evidence is given.
+ page 10 - "Taxonomy of Root Causes and Bug Impacts": Could you reflect on how baselines fare in terms of these root causes?
+ page 10 - "private industrial dataset (UTXXX)": Need more details about this dataset. Company? Domain? Lines of code?
+ - Typos / Errors
+ page 3 - "s[": Missing space and typo.
+ page 5 - "n T": Should be “n. T.” or reformulated.
+ page 7 - "Appraoch": Should be “Approach”.
+ page 7 - "97.46%" in bold: Not necessary, especially when it is not the best result.
+ page 8 - "↑": Inconsistent with performance drop. Arrows should point down.
+ - ### Questions
+ - How exactly is the multi-agent collaboration orchestrated? Is there a predefined protocol (e.g., queue-based, blackboard architecture), and which MAS framework (if any) is used to support the coordination, communication, and tool invocation?
+ - What is the novelty and added value of the repository-aware knowledge graph? How does it compare to existing code representation structures used in similar works (e.g., code property graphs, AST-based models)? Can you provide a motivating example early in the paper?
+ - What operations are required to integrate a new LLM model into TestAgent? Does the system abstract away model-specific APIs? What challenges arise when using non-OpenAI models (e.g., context window, latency, inference mode)?
+ - ### [[REVIEWS/Notes]]
+ - ### YELLOW CONCERNS
+ background-color:: yellow
+ collapsed:: true
+ - {{query (and [[ffd400]] [[ICSE2026-paper1656]] )}}
+ collapsed:: true
+ - ### ❓️Questions
+ - {{query (and [[question]] [[ICSE2026-paper1656]] )[[question]]}}
+ query-table:: true
+ query-properties:: [:block]
\ No newline at end of file
diff --git a/pages/ICSE2026-paper2683.md b/pages/ICSE2026-paper2683.md
new file mode 100644
index 00000000..c401b520
--- /dev/null
+++ b/pages/ICSE2026-paper2683.md
@@ -0,0 +1,36 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems
+date-start:: [[18-09-2025]] - 00:31
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@A Multi-Agent Approach for Engineering Digital Twins of Smart Human-Centric Ecosystems]]
+parent::
+todoist:: https://app.todoist.com/app/task/2683-a-multi-agent-approach-for-engineering-digital-twins-of-smart-human-centric-6cVHmvcJVfJcWwhg
+
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - This paper presents MAD, a Multi-Agent Architectural for Digital Twins of Smart Human-centric Ecosystems (SHEs). The main peculiarity of MAD is that it is a decentralized, agent-based architecture that models both cyber and human entities as agents. The architecture has been implemented to simulate a ride-hailing system in San Francisco, and evaluated on responsiveness, fidelity, adaptability, and robustness.
+ - ### Strengths
+ - + The use of Multi-Agent Systems (MAS) to represent both cyber and human entities is interesting
+ - ### Weaknesses
+ - - The distinction between the architecture and its implementation is not sufficiently clear throughout the paper
+ - - It remains ambiguous what generalizable insights are derived from the prototype beyond the specific implementation context (MADSF)
+ - - The novelty with respect to existing work (e.g., MAPE-K, CPS, autonomous systems) is underdeveloped and not convincingly articulated
+ - - The evaluation metrics (e.g., responsiveness, fidelity) are applied to the implementation rather than the architecture, making it unclear whether the results validate MAD as a general architectural solution
+ - ### Detailed comments for authors
+ - Novelty: The contribution claims to be the first concrete architectural solution where agents form the structural foundation of a DT. However, the connection to prior MAS frameworks, CPS architectural patterns (e.g., MAPE-K), and autonomy paradigms is missing. The paper does not clarify whether the innovation lies in the modeling primitives, in the architectural style, or in the instantiation logic of DT components.
+ - Rigor: The research questions (RQ1–RQ4) are framed in terms of implementation-level properties (fidelity, adaptability, etc.), but the paper lacks a principled separation between the architectural design and its concrete realization. Moreover, claims about properties such as robustness and adaptability are derived from simulation results, but the limitations of such evaluations in the generalization of architectural properties are not discussed.
+ - Relevance: The work is highly relevant for domains where decentralized and human-in-the-loop systems interact (e.g., smart cities, urban mobility). However, it is not clear what aspects of the proposed architecture would generalize across different domains or be reusable beyond the specific ride-hailing use case (MADSF).
+ - Verifiability & transparency: A replication package consisting of source code and data is available (https://anonymous.4open.science/r/sfdigitalmirror/README.md). The given repository gives details on how run the code and obtain the results shown in the paper, under different scenarios.
+ - Presentation: The paper is generally clear and well-structured. However, there is a frequent confusion of architectural and implementation concerns (e.g., responsiveness of an architecture, which is implementation-specific). The discussion of results does not distinguish between general findings and implementation-specific behaviors. This is the main issue of the paper, which presents an interesting simulation tool, without drawing research insights that go beyond the implementation of the considered scenario.
+ - QUESTIONS:
+ - Q1: What are the generalizable architectural principles behind MAD that go beyond the specific implementation (MADSF), and how can they be reused or adapted to other SHE scenarios?
+ - Q2: How does MAD relate to existing architectural paradigms in autonomous and self-adaptive systems (e.g., MAPE-K, feedback control loops)?
+ - Q3: What is the specific innovation in MAD’s treatment of human agents compared to previous MAS-based DT architectures that either model humans as data sources or external participants?
\ No newline at end of file
diff --git a/pages/ICSE2026-paper2859.md b/pages/ICSE2026-paper2859.md
new file mode 100644
index 00000000..b1a1e712
--- /dev/null
+++ b/pages/ICSE2026-paper2859.md
@@ -0,0 +1,65 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code
+date-start:: [[17-09-2025]] - 15:05
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@TraceCoder: A Trace-Driven Multi-Agent Framework for Automated Debugging of LLM-Generated Code]]
+parent::
+todoist:: https://app.todoist.com/app/task/2859-trace-coder-a-trace-driven-multi-agent-framework-for-automated-debugging-of-6cVHmvW5WjQw4vmg
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - This paper presents TraceCoder, a multi-agent system to support the automated debugging of source code generated by LLMs. The approach is based on three specialized agents on Instrumentation, Analysis, and Repair. To guide the automated debugging process, the approach makes use of two introduced techniques, ie., Historical Lesson Learning (HLLM) and Rollback Mechanism (RM). They permi to avoid redundant failures. The authors claim significant improvements over state-of-the-art methods, achieving up to 34.43% relative gain in Pass@1 on benchmark datasets.
+ - ### Strengths
+ - + well-motivated and relevant problem
+ - + interesting multi-agent architecture
+ - ### Weaknesses
+ - - Experimental setup lacks detail. The granularity of the initial code generation (method/class/project), the test suite’s role and coverage, and how baselines were configured/applied are insufficiently explained
+ - - No agent orchestration framework is employed or discussed
+ - - Instrumentation phase is critical but underspecified. In particular, semantic-preserving behavior is assumed but not formally verified or tested
+ - ### Detailed comments for authors
+ - Novelty: The paper is about an interesting and novel technique based on MAS to deal with a relevant problem. The proposed combination of runtime tracing, historical error learning, and modular multi-agent design is novel and well-motivated. The paper contributes original ideas such as HLLM and RM in the context of LLM-driven code repair.
+ - Rigor: While the architecture is conceptually solid, key assumptions are not empirically validated, e.g., semantic preservation during instrumentation. Moreover, the experiments related to RQ1 lacks depths. Examples, setup details (class/function/project), and baseline configurations are missing.
+ - Relevance: The work is highly relevant given the increasing reliance on LLMs for code generation and the frequent presence of logic bugs in such code. Debugging automation remains a practical bottleneck in applying LLMs for software engineering at scale.
+ - Verifiability & transparency: Authors provide a link with the implementation of the proposed approach. However, details on the form and source of input prompts, testing strategies/coverage, and baseline configurations are missing.
+ - Presentation: Writing is generally clear, though certain technical claims (e.g., semantic integrity preservation) are not critically assessed. In addition, some terms like “minimal adjustments”, and “strategic print statements” are ambiguous and require proper definitions. Moreover, authors should give details on test cases, e.g., if they play some roles during the initial generation of source code.
+ - Detailed comments:
+ - p.3: “Instrumentation Agent inserts diagnostic probes”
+ Does it mean that it changes the previously generated code? This is a critical point. Clarify whether the instrumentation alters control flow or computational semantics, especially in complex programs.
+ - p.3: “The Instrumentation Agent employs a dedicated prompt…”
+ Is it sure that the instrumentation agent does not wrongly add statements that change the semantics of the code? You should explain how you ensure the correctness of the modified code, and whether any formal guarantees or empirical tests were performed.
+ - p.3: “with strategically placed print statements...” Confirm whether print statements are the only instrumentation method.
+ - p.3: “must not modify logic, comment out code, or introduce new variables” This is crucial. How do you ensure that? How is this enforced at generation time? Please elaborate.
+ - p.5: “allowed to make minimal adjustments”
+ How can you define such "minimal" adjustments? Define what “minimal” means (e.g., token delta, AST edit distance) and how it's enforced across iterations.
+ - p.5: “Communication follows a structured, sequential pattern…”
+ Please discuss why you didn’t use an existing MAS framework, especially when others provide orchestration, coordination, and policy enforcement.
+ - p.5: “instrumentation suggestions in subsequent iterations”
+ Is this always necessary?
+ - p.5: “Agents do not communicate directly...” But how can convergence be guaranteed in this loosely coupled setup?
+ - p.10: Conclusion: Several high-level contributions are claimed. However, the practical usage of the system is hard to infer, especially in terms of granularity of code, role of test cases in initial generation, and setup of generation pipeline.
+ - QUESTIONS:
+ - Q1: How is semantic preservation ensured during the instrumentation process?
+ - Q2: Why was a dedicated MAS framework not used to orchestrate agent interactions and maintain state across iterations?
+ - Can you provide more details about the experimental setup for RQ1? In particular:
+ - What is the granularity of the code used (function, class, full project)?
+ - What is the role of test suites in the initial generation?
+ - How were baselines configured and executed?
+ - How was test case coverage measured and controlled?
+ - ### [[REVIEWS/Notes]]
+ - ### YELLOW CONCERNS
+ background-color:: yellow
+ - {{query (and [[ffd400]] [[ICSE2026-paper2859]] )}}
+ collapsed:: true
+ - ### ❓️Questions
+ - {{query (and [[question]] [[ICSE2026-paper2859]] )[[question]]}}
+ query-table:: true
+ query-properties:: [:block]
\ No newline at end of file
diff --git a/pages/ICSE2026-paper2919.md b/pages/ICSE2026-paper2919.md
new file mode 100644
index 00000000..7be019c3
--- /dev/null
+++ b/pages/ICSE2026-paper2919.md
@@ -0,0 +1,68 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: Recommending Relevant Classes for Infrequent API Classes
+date-start:: [[17-09-2025]] - 11:46
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Recommending Relevant Classes for Infrequent API Classes]]
+parent::
+todoist:: https://app.todoist.com/app/task/2919-recommending-relevant-classes-for-infrequent-api-classes-6cVHmvX54fQVgpV8
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - The paper proposes APIrel, an approach to mitigate bias when recommending API classes, even in the absence of frequent usage patterns in code. APIrel combines mined patterns and document features to train a classifier to predict relationships between infrequently used or new APIs. The paper evaluates APIrel by considering 5 libraries and shows promising results.
+ - ### Strengths
+ - + Relevant long-tail problem in API recommendation, where most APIs are rarely used and thus difficult to relate or recommend
+ - + Interesting attempt to move beyond client-based mining, by relying on API documentations
+ - ### Weaknesses
+ - Presentation is confusing and poorly structured, with forward references, missing definitions, and mixing of problem and solution
+ - The tool is not accessible, making reproducibility and verification impossible.
+ - Evaluation is limited and lacks user studies (e.g., developers' feedback on relevance predictions).
+ - ### Detailed comments for authors
+ - Novelty: The idea of leveraging document-based features rather than usage-based mining for inferring relationships among APIs is interesting and reasonably novel. However, novelty is somewhat undermined by vague distinctions from prior work. The “two lines of research” (document vs. client-based) are repeatedly mentioned but never formally defined with illustrative examples.
+ - Rigor: The technical rigor is compromised by the lack of concrete examples to clarify design choices, assumptions, and implementation steps. Several parts are abstract and theoretical without operational grounding (e.g., the use of “patterns,” “mined rules,” and model training steps).
+ - Relevance: The addressed problem is highly relevant for developers who need better tooling to understand or recommend infrequent APIs. However, the current presentation makes it difficult to assess the actual impact or applicability of the method.
+ - Verifiability & transparency: Broken link to the repository makes it impossible to validate or test the tool. Moreover, it is unclear how the tool is to be used, what the inputs are, or how results are visualized or interpreted. The data collection process (e.g., how patterns are mined or APIs extracted) is not reproducible due to insufficient procedural detail. The fact that SearchCode system is no longer online does not help in this regard.
+ - Presentation: This is the main problem of this paper. The writing is often unclear and the reader is supposed to go trhough the text many times to get the meaning of the presented concepts. The motivation is not well separated from the solution, especially in Section 2. I suggest adding explanatory examples, without them many parts of the paper hare hard to follow. Moreover, firgure and tables are not always correctly references and there are too many forward references. For instance section 7 is mentioned in the introduction.
+ - Detailed comments:
+ - page 1: "As there are many API classes, it is challenging to identify relevant API classes for a given API class." - Sentence is poorly written and redundant. Please rephrase to clearly state what the challenge is: e.g., is the difficulty in discovering dependencies, usage patterns, or semantic relationships?
+ - page 1: "APIrel uses mined patterns as seeds and compares API documents to build labeled data." - What exactly are the “mined patterns”? How are they extracted, from what sources, and at what stage of the process?
+ - page 1: "Given the documents of two API classes, our trained model can predict whether they are relevant." - Please clarify what type of documents are used here (e.g., Javadoc, README, class summaries). This needs to be made explicit.
+ - page 1: "As introduced in Section 7," - This is an overly early forward reference. Consider avoiding such jumps in the introduction. Core ideas should be self-contained in the early sections.
+ - page 1: "For instance, API documents rarely mention relevant API classes, especially when such classes are infrequent." - Statements like this should be supported by concrete examples to make the issue tangible to the reader.
+ - page 1: "For instance, researchers use Apriori algorithms to mine the relevant libraries." - This usage of Apriori is unclear. Specify what is mined, how support is defined, and what the items represent in this context.
+ - page 1: "APIrel. It is the first approach that infers relevant classes from documents without predefined templates." - What kinds of documents are used? This should have been clarified much earlier. The lack of early context makes it difficult to evaluate the novelty.
+ - page 2: "The document of HSSFWorkbook." - Ambiguous phrase. What is meant by "the document"? Please use consistent terminology throughout (e.g., API class description, Javadoc, etc.).
+ - page 2: "From the clients" - Please define what is meant by "clients" in this context. Client projects? Users? Code examples?
+ - page 2: "Table 3" - Typo. Likely meant to reference “Table 1.” Please correct.
+ - page 2: "SearchCode" - This resource appears to be offline. If it’s critical to the example or dataset, either replace it with an active resource or explain how the necessary data was retained.
+ - page 3: "Definition 1. The relevant API classes of an API class are classes that can be called together to implement functionalities." - The phrase “called together” is vague. Please formalize this definition and clarify what is meant by "calling a class."
+ - page 3: "To infer hidden patterns, we reduce the inference of infrequent relevant API classes into a classification problem..." - This paragraph needs a worked-out example to clarify the input/output of the classification function. The formal description is too abstract alone.
+ - page 4: "Line 1 builds a dictionary from mined patterns..." - This would be more understandable if tied to a running example. Refer to specific APIs from the motivating use case to make the logic concrete.
+ - page 4: "Line 6 checks whether the c1 and c2 classes appear in our dictionary..." - Please elaborate on this logic with an example. Without referring back to a real code snippet or API class, it remains abstract.
+ - page 6: "API documents in Table 3" - Table 3 appears to repeat library names listed elsewhere and does not clearly present documents. Please clarify what is meant by "API documents" here.
+ - page 6: "The repository of SearchCode has millions of projects..." - It's unclear how SearchCode contributes to the methodology. Is it used for mining patterns, extracting features, or labeling data?
+ - page 6: "4.2 No Baseline Statement" - This section reads more like an appendix to Related Work. Consider moving it and restructuring Section 2 to present motivation and prior work in a more integrated, example-driven fashion.
+ - page 6: "As introduced in Section 7," - Section 7 is referenced repeatedly and contains important information. Consider moving this section earlier in the paper (e.g., after the introduction).
+ - page 6: "The first line of approaches analyzes documents with templates..." - The distinction between the two families of approaches (document-based and client-based) is referenced frequently. Please clarify this with illustrative examples.
+ - page 7: "The accuracy" - Accuracy of what exactly? Prediction of relevant classes? Clarify what the ground truth is and whether human validation was involved.
+ - page 10: "We evaluated APIrel on five popular libraries..." - Given the subjective nature of what counts as “relevant,” evaluation should involve developers to verify the usefulness of predictions.
+ - Questions
+ - Q1: What exactly are the “documents” used as input by APIrel? Are they structured Javadoc descriptions, source code comments, online documentation, or something else?
+ - Q2: How is “relevance” between two API classes defined and operationalized during model training and evaluation? What constitutes a positive or negative label? Can such labels automatically assessed without any human involvment?
+ - ### [[REVIEWS/Notes]]
+ - ### YELLOW CONCERNS
+ background-color:: yellow
+ - {{query (and [[ffd400]] [[ICSE2026-paper2919]] )}}
+ collapsed:: true
+ - ### ❓️Questions
+ - {{query (and [[question]] [[ICSE2026-paper2919]] )[[question]]}}
+ query-table:: true
+ query-properties:: [:block]
\ No newline at end of file
diff --git a/pages/ICSE2026-paper3125.md b/pages/ICSE2026-paper3125.md
new file mode 100644
index 00000000..e65e64bd
--- /dev/null
+++ b/pages/ICSE2026-paper3125.md
@@ -0,0 +1,48 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval
+date-start:: [[16-09-2025]] - 16:09
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@SRC-Retrieval: Semantic-Based GitHub Repository and Code Retrieval]]
+parent::
+todoist:: https://app.todoist.com/app/task/3125-src-retrieval-semantic-based-git-hub-repository-and-code-retrieval-6cVHmvhGJfhPWjQg
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - The paper presents an approach to retrieving GitHub repositories and specific code files starting from functional requirements given by developers. Functionalities are extracted from README files and GitHub issues, which are about implemented functionalities. The approach has been compared with two different baselines.
+ - ### Strengths
+ - + Interesting and relevant topic
+ - + Linking functionalities with source code is indeed important
+ - ### Weaknesses
+ - Problems in the way dataset was constructed, especially regarding the role of classifiers in labeling large amounts of data, potentially introducing noise and cascading errors
+ - The approach relies heavily on README files for functionality extraction, but the validity and precision of these mappings are questionable.
+ - The evaluation section does not convincingly show that the retrieved code files actually meet user requirements in a semantically meaningful way.
+ - The baselines chosen for comparison appear weak, and the omission of modern tools like GitHub Copilot undermines the credibility of the evaluation.
+ - The presentation is redundant in different parts, especially with repeated technical details on model training.
+ - ### Detailed comments for authors
+ - Novelty: The paper presents a retrieval pipeline that integrates multiple transformers to map functional requirements to GitHub repositories and specific code files. While this integration is interesting, the paper is not convincing with respect to the quality of the obtained results especially in comparison with existing supporting technologies like Copilot. The considered baselines are not appropriate because they do not permit to actually stress the novelty of the proposed approach with respect to existing development assistance tools.
+ - Rigor: The approach heavly rely on multiple trained classifiers, each operating on noisy or weakly supervised data. For instance, the extraction of functionalities from README files lacks solid grounding and examples. The same applies to the issue-to-code linkage process, where the labeling process has been automated without discussing the accuracy of such an automated process. Thus the risk of compounded errors due to the different classifiers that have been used to create the training dataset is not addressed.
+ - Relevance: The paper is highly relevant to software engineering practice, particularly for developers seeking concrete examples of functionality implementations. However, the lack of comparison with widely adopted tools like Copilot reduces the practical significance of the proposed approach.
+ - Verifiability & transparency: How functional requirements are defined and extracted remains ambiguous. The use of classifiers to assess whether a GitHub issue represents a valid functionality or not is prone to mislabeling, and the paper does not provide error analysis or a discussion on its impact. The absence of ablation studies, particularly to separate the contribution of README-derived vs. issue-derived functionalities, is an important omission. Moreover, the evaluation lacks a user-centered validation of whether retrieved code files actually satisfy the intended requirement.
+ - Presentation: The paper is generally readable but suffers from redundancy. Many paragraphs related to the data creation steps are repeated, Some conceptual terms like “semantic alignment” or “repository functionality” are used early on but only vaguely defined.
+ - QUESTIONS:
+ - Q1: How have you quantified the effect of classification errors (e.g., incorrectly labeled issues or README sentences) on the overall retrieval performance?
+ - Q2: What is the actual contribution of README files to the overall retrieval pipeline? Have you considered an ablation study that separates the impact of README-derived vs. issue-derived functionalities?
+ - Q3: Why have you not compared your method against modern tools like GitHub Copilot?
+ - ### [[REVIEWS/Notes]]
+ - ### YELLOW CONCERNS
+ background-color:: yellow
+ - {{query (and [[ffd400]] [[ICSE2026-paper3125]] )}}
+ collapsed:: true
+ - ### ❓️Questions
+ - {{query (and [[question]] [[ICSE2026-paper3125]] )[[question]]}}
+ query-table:: true
+ query-properties:: [:block]
\ No newline at end of file
diff --git a/pages/ICSE2026-paper3485.md b/pages/ICSE2026-paper3485.md
new file mode 100644
index 00000000..ef66ed48
--- /dev/null
+++ b/pages/ICSE2026-paper3485.md
@@ -0,0 +1,39 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: A kNN-Based Recommender System for Test Case Reuse in Agile Development
+date-start:: [[18-09-2025]] - 01:59
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@A kNN-Based Recommender System for Test Case Reuse in Agile Software Development]]
+parent::
+todoist:: https://app.todoist.com/app/task/3485-a-k-nn-based-recommender-system-for-test-case-reuse-in-agile-development-6cVHmvgxqh6VgCcg
+
+ - ### [[Comments]]
+ - #.tabular
+ - ### Paper summary
+ - This paper proposes a KNN-based Recommender System to support the reuse of test cases by leveraging a domain-specific taxonomy and historical user stories. Authors have performed two different experiments. An off-line experiment to identify the configuration that permits to get the achieve the best recommendation performance. The on-line experiment has been performed by using such a configuration with an industrial case study involving two agile projects. Results show promising potential for enhancing test reuse.
+ - ### Strengths
+ - + The paper addresses a relevant and practical problem in agile software testing
+ - + Simple and lightweight solution compared to deep-learning-based alternatives
+ - ### Weaknesses
+ - - The central assumption, that similar user stories lead to reusable test cases, is strong and not critically examined
+ - - The evaluation lacks a proper baseline or comparative study, which limits the assessment of relative performance
+ - ### Detailed comments for authors
+ - Novelty: The idea of test case reuse is not new, but this paper innovates by focusing on early-stage reuse in agile environments and using structured user stories with domain taxonomies. In this respect, I found the paper interesting and I liked the simplificity even though effective simplicity of the proposed solution.
+ - Rigor: The experimental design is solid and includes statistical tests to select the best configuration during the off-line experiments. However, the paper requires revision to address a number of issues as listed below:
+ - The paper is based on the assumption "similar user stories have similar tests". I found this assumption very strong. Minor variations in implementation can lead to very different tests. It is necessary to clarify whether the retrieved tests were used as inspiration or directly reused. Were they used as-is, adapted, or just served as reference?
+ - The relevance of the retrieved test cases is not very high: a large portion of accepted tests were only moderately relevant.
+ - The practical utility of the recommended tests (whether they were reused as-is, adapted, or merely used as inspiration) is not clarified.
+ - A few important details on the context of the online study (e.g., nature of the company, business domain) are missing, which affects external validity.
+ - No mention of effort/time metrics, such as time saved or effort required to adapt reused tests, limits the construct validity.
+ - Relevance: The paper is very relevant to practitioners working in agile contexts. Reuse of test cases could lead to cost and time savings, but the paper does not quantify this aspect as previously pointed out. Moreover, by referring to Fig. 5, the results of the online experiments are not impressive. Nearly half of the accepted tests had low relevance. This needs a more nuanced discussion, especially in the conclusion. Moreover, what does acceptance mean? Were tests reused unchanged? How much effort was required to make them usable?
+ - Verifiability & transparency: The design and implementation of the RecSys are clearly described. However, the supplementary material includes only the dataset used during the experiments. The developed tools are not included. Thus it is not possible to replicate the performed experients.
+ - Presentation: Overall, the paper is well-written, logically organized, and easy to follow despite the issues discussed above.
+ - Questions:
+ - Q1: To what extent can the recommended test cases be reused as-is versus requiring significant adaptation?
+ - Q2: How generalizable is the proposed taxonomy-based RecSys to other domains?
\ No newline at end of file
diff --git a/pages/ICSE2026-paper3924.md b/pages/ICSE2026-paper3924.md
new file mode 100644
index 00000000..d2a5f01a
--- /dev/null
+++ b/pages/ICSE2026-paper3924.md
@@ -0,0 +1,54 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE]]
+full-title:: Determining Application Test Results Using Adaptive JSON
+date-start:: [[14-09-2025]] - 18:01
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Determining Application Test Results Using Adaptive JSON]]
+parent::
+todoist:: https://app.todoist.com/app/task/3924-determining-application-test-results-using-adaptive-json-6cVHmvg3mM8ghg48
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - #.tabular
+ - - ### Paper summary
+ - The paper presents an approach to test JSON-based APIs. The main building blocks of the proposed approach are "Skeleton JSON", "Adaptive JSON", and "Adaptation Sets". By means of these components, engineers can precisely define which parts of an API response have to be validated and how. The application of the approach on two different case studies has been shown.
+ - - ### Strengths
+ - + Relevant problem
+ - + Promising approach based on the declarative "Adaptation Set" mechanism for tuning the testing process
+ - - ### Weaknesses
+ - - The paper is not always well written
+ - - Several parts ar repetitive, vague, or poorly written.
+ - - The writing includes multiple formatting and typographic errors (e.g., Markdown synatx, missing spaces)
+ - - Gray literature is used even critical and motivational parts of the paper that would require peer-reviewed references
+ - - Comparisons with existing techniques (especially other schema-inference-based approaches) are missing or superficial
+ - - The validation of the claimed advantages (e.g., flexibility, maintainability, reduction of brittleness) is not adequately supported by empirical evidence.
+ - - ### Detailed comments for authors
+ - Novelty: The paper does not clearly compare the proposed approach with existing methods that extract or synthesize schemas from JSON payloads. A comparison of the proposed testing mechanism with existing baselines is also missing.
+ - Rigor: The methodology is described conceptually, but formal definitions, measurable properties, and an empirical evaluation are missing. Moreover, claims such as “resilient to insignificant changes” or “lightweight” need quantification or validation to be taken seriously.
+ - Relevance: The paper targets a relevant and timely problem in automated software testing, especially in DevOps and CI/CD pipelines that depend on stable, low-maintenance test suites. However, without a comparative evaluation, the practical significance is not clear.
+ - Verifiability & transparency: There is no mention of tool availability, datasets, or replication packages. The paper should provide a GitHub repository or similar so that readers can downlod tools and related artifacts to play with the proposed approach. Two case studies have been discussed, even though the given details are not enough to replicate them.
+ - Presentation: This is the main issue of the paper. There are redundant sentences, the writing presents the approach only at conceptual level and several formatting errors are present. Many references from non-peer-reviewed sources (e.g., Medium, Postman blogs) are given.
+ - Detailed comments:
+ - p.1: The limitation of JSON-DDT is vaguely mentioned; its impact or relation to the contribution is not evident.
+ - p.2: “resilient to insignificant changes” - This is too vague. Define what constitutes an “insignificant” change.
+ p.2: JSON Schema is mentioned, but no comparative discussion is provided - how does the proposed approach differ from or improve upon it?
+ - p.2: The supposed “distinct advantages” of the technique need to be clarified and situated in the literature (e.g., compare with 10.1016/j.knosys.2016.03.020 and 10.1109/MODELS50736.2021.00033).
+ - p.2: Claim that Skeleton JSON is “lightweight” and suitable for test automation is not supported by any empirical or architectural argument.
+ - p.2: What were the requirements that led to the definition of Adaptive JSON? These are not made explicit.
+ - p.7: The claim about brittleness and spurious failures in Snapshot Testing should be supported by examples or quantitative evidence.
+ - p.8: The authors state that the technique was “demonstrated in case studies” - but there is no real comparison with other approaches, no quantitative results, and no ablation study.
+ - ### [[REVIEWS/Notes]]
+ - ### YELLOW CONCERNS
+ background-color:: yellow
+ - {{query (and [[ffd400]] [[ICSE2026-paper3924]] )}}
+ collapsed:: true
+ - ### ❓️Questions
+ - {{query (and [[question]] [[ICSE2026-paper3924]] )[[question]]}}
+ query-table:: true
+ query-properties:: [:block]
\ No newline at end of file
diff --git a/pages/ICSE_2026_WS_28.md b/pages/ICSE_2026_WS_28.md
new file mode 100644
index 00000000..3a387a7e
--- /dev/null
+++ b/pages/ICSE_2026_WS_28.md
@@ -0,0 +1,21 @@
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE2026-WS]]
+full-title:: Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices: a Technology Acceptance Study
+date-start:: [[23-11-2025]] - 19:27
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Graphical Interface Model for Empowering Web Application Users to Make Sustainable Choices: a Technology Acceptance Study]]
+parent::
+todoist:: https://app.todoist.com/app/task/28-graphical-interface-model-for-empowering-web-application-users-to-make-sustai-6fGCcxFv9QmhxQw6
+
+ - ### [[Comments]]
+ - SUMMARY: The paper proposes a pluggable graphical interface model to enable end-users to customize web applications with the goal of reducing energy consumption and increasing sustainability awareness. A Figma prototype is evaluated through a technology acceptance study based on UTAUT2. The topic is relevant and the idea of involving users in sustainability-oriented customization is interesting, but the paper raises concerns regarding feasibility, generalizability, and the validity of the claimed benefits.
+ - COMMENTS: The paper is about a relevant and timely topic addressing sustainability and user awareness. The idea of involving end-users in sustainability decisions is interesting. The prototype is clearly articulated, and the authors acknowledge key challenges such as immature metrics and difficulties in mapping environmental indicators to real behavior. However, my main concerns are related to the following issues:
+ - The main issue of the paper is that it does not explain how user-driven configuration leads to measurable or validated reductions in energy consumption. The link between customization and actual savings remains speculative.
+ - The generality of the proposed model is unclear. It is doubtful that the approach can be safely applied to arbitrary web applications without breaking layouts, dependencies, or expected behaviours.
+ - The paper suffers from repetition, especially regarding the model’s universality and vision. Some claims of novelty are overstated.
+ - To summarize, the proposed idea is interesting enough to stimulate meaningful discussion, and the prototype and preliminary acceptance study provide a reasonable starting point for future work. I therefore recommend weak accept, mainly for the value of the topic and the potential to enrich the workshop discussion.
\ No newline at end of file
diff --git a/pages/ICSE_2026_WS_GREENS_27.md b/pages/ICSE_2026_WS_GREENS_27.md
new file mode 100644
index 00000000..99a3f54c
--- /dev/null
+++ b/pages/ICSE_2026_WS_GREENS_27.md
@@ -0,0 +1,18 @@
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE2026-WS]]
+full-title:: Bridging the gap between industry and academia: sustainability in LLM-assisted software engineering
+date-start:: [[23-11-2025]] - 16:56
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Bridging the gap between industry and academia: sustainability in LLM-assisted software engineering]]
+parent::
+todoist:: https://app.todoist.com/app/task/27-bridging-the-gap-between-industry-and-academia-sustainability-in-llm-assisted-6fGCcw4wV8fQW9qc
+
+ - ### [[Comments]]
+ - The paper reports on the discussions held during the SILAS (Sustainability in LLM-assisted Software Development) workshop. It highlights sustainability challenges in LLM-based software engineering from both academic and industrial perspectives.
+ - Although the topic is highly relevant and timely, the work suffers from issues in presentation and structure. The discussion is fragmented across the paper, and the narrative lacks a coherent flow. The choice of the three focus areas is not motivated. I suggest reorganizing the discussion section around clearly defined challenges and their corresponding research directions. A dedicated table mapping focus areas, identified challenges, and the research directions considered relevant during the SILAS event would greatly improve clarity.
+ - Despite these structural issues, the paper addresses an important subject and can trigger interesting discussions during the workshop. I recommend revising the organization of the paper as suggested above.
\ No newline at end of file
diff --git a/pages/Invited talk at LLMA4SE Summer School website.md b/pages/Invited talk at LLMA4SE Summer School website.md
new file mode 100644
index 00000000..b865917a
--- /dev/null
+++ b/pages/Invited talk at LLMA4SE Summer School website.md
@@ -0,0 +1,192 @@
+tags:: #todoist-task, [[Talks]], [[WORK]], [[CONFERENCES]]
+date:: [[31-08-2025]] - 11:46
+progress:: {{renderer :todomaster}}
+
+ - ### **Invited talk Tasks**
+ - DONE Raffinare l'introduzione del concetto di agenti AI
+ id:: 68ac6e54-e572-42f4-8116-625b4d85d757
+ collapsed:: true
+ - Creare / trovare una figura che rappresenti i concetti principali graficamente
+ - DONE Rivedere le slides di presentazione dei 5 tipi di agenti
+ - DONE Fare le slide conclusive
+ id:: 68b4c69b-fa0b-41c1-9633-b87c6cf6ab33
+ :LOGBOOK:
+ CLOCK: [2025-09-01 Mon 00:04:03]--[2025-09-01 Mon 00:04:04] => 00:00:01
+ :END:
+ - DONE Ridurre un pochino il numero di slides
+ id:: 68b4c69b-4d77-4192-9cff-d9f87cb200f4
+ - DONE Sistemare le immagini nel summary
+ id:: 68b4c69b-7fdf-4663-89af-ac6df65d88af
+ - Punti da sottolineare:
+ - Challenges related to the adoption of single-agent systems
+ - ### **Notes from the venue**
+ - **Program**: [LLMA4SE 2025 - 1st International Summer School on LLM-based Agents for Software Engineering](https://i3lab.unex.es/summer-school/#agenda)
+ - **Venue**: [Universidad de Extremadura](https://www.unex.es/) - [Caseres](https://es.wikipedia.org/wiki/C%C3%A1ceres)
+ - #### **READINGS**
+ collapsed:: true
+ - {{query (and [[Invited talk at LLMA4SE Summer School website]] [[Reading]]) (not [[GOALS-TODOIST]]) (not [[TODOIST-LOGSEQED]]))}}
+ query-table:: true
+ query-properties:: [:block]
+ - #### **First day of the event [[01-09-2025]]**
+ collapsed:: true
+ - ##### I talked with different people after my talk
+ - I talked with a student working with Javier from **Universitat Politècnica de Catalunya** on the EU project [HIVEMIND | Human-centred collaboratIVE MultI-ageNt framework for accelerating software Development and maintenance - HIVEMIND](https://hivemind-project.eu/) [[PROJECTS/MOSAICO]]
+ - **Jesús M. González Barahona** offered to collaborate concerning the "community" aspects of agents.
+ - I talked with **Jie Zhang**
+ - Here is the AIware arXiv track I mentioned, the deadline is this Friday: [https://2025.aiwareconf.org/track/aiware-2025-arxiv-track](https://2025.aiwareconf.org/track/aiware-2025-arxiv-track)
+ - There is also a benchmark and dataset track with the same deadline.
+ - The efficiency benchmark I mentioned is: [https://arxiv.org/abs/2402.02037](https://arxiv.org/abs/2402.02037)
+ - The test case generation benchmark (under submission): [https://arxiv.org/abs/2508.00408](https://arxiv.org/abs/2508.00408)
+ - [[Benchmarks]] seem to be very relevant and is attracting the community. We need to focus on that. There is one slide from the talk of Jesus we can have a look at ((68b57fc1-5214-405c-b4f7-58296590c06d))
+ - ##### **Generative AI models running in your own structure**
+ id:: 68bac2bb-1db8-41cb-81ed-7ef7f76e1491
+ - [tdd-workshop / SelfHostable-AI-Models · GitLab](https://gitlab.com/tdd-workshop/selfhostable-ai-models)
+ - 
+ - ((68b572ad-6444-494c-8929-43d2665321e6)) for instance if we are fine-tuning we can share the results of the fine-tuning
+ - ((68b572d4-f669-47ca-b942-f3a52b9e0683)) parts of the open-source aspects are applied to models
+ - ((68b57311-0b75-4a2a-86a9-b7236e7d2611))
+ - Important for different reasons, e.g., trust, data leakage,. You really control the information provided by the model.
+ - ((68b5737f-d5d0-41fd-bdc5-e574964d08ed)) [[STAR]]
+ id:: 68b57381-292d-4e53-8b79-b0378d3ddcca
+ - Papers on ((68b57a82-c115-4a56-a85b-4241b54bda29))
+ - What is fine-tuning ((68b57e64-b29f-42ea-9620-be4bbfa7edc2))
+ - Have a look at OpenRouter to see the attributes that are given to each of the managed models [[PROJECTS/MOSAICO/WP2]]
+ id:: 68b598e8-992a-433f-b685-5318c5ba0f4d
+ :LOGBOOK:
+ CLOCK: [2025-09-02 Tue 11:28:12]--[2025-09-02 Tue 11:28:13] => 00:00:01
+ :END:
+ - ##### **Workshop 1. Test-driven development with the help of generative AI**
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - http://www.promptingguide.ai
+ - {:height 354, :width 519}
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - 
+ - ```
+ export OPENROUTER_API_KEY="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"
+ ```
+ - [Giovanni Rosa / Currante · GitLab](https://gitlab.com/grosa1/currante)
+ - [tdd-workshop / TDD-for-Code-Generation-Lab-Sept-25 · GitLab](https://gitlab.com/tdd-workshop/tdd-for-code-generation-lab-sept-25)
+ - #### **Second day of the event [[02-09-2025]]**
+ - ##### **MAS for Code Generation - Jie M.Zhang, King's College London**
+ - *History of agents*
+ - 1980s- software agents
+ - 1990s - MAS
+ - 2010 - Agents in deep reinforcement learning
+ - 2020- LLM-based agents, AI agents
+ - *There are a lot of definition about agents.*
+ - There is one that has been mentioned, from *Wooldrige, MIchael "Intelligent agents: The key concepts"*
+ - Hugging face in its "Agent course" gives the following definition: An agent is a system that leverages an AI model to interact with its environment....
+ - Tutorial fro ICML 2025: Jailbreking LLMs and Agentic Systems
+ - Mistral AI has also another definition:
+ - >AI agents are autonomous systems powered by large language models (LLMs) that, given high-level instructions, can plan, use tools, carry out processing steps, and take actions to achieve specific goals. These agents leverage advanced natural language processing capabilities to understand and execute complex tasks efficiently and can even collaborate with each other to achieve more sophisticated outcomes.
+ - [Agents Introduction | Mistral AI](https://docs.mistral.ai/agents/agents_introduction/#:~:text=%E2%80%8B,to%20achieve%20more%20sophisticated%20outcomes.)
+ - *When to use multiple agents?*
+ - A number of questions need to be considered including
+ - How big and complex is the task?
+ - Budget?
+ - Capabilities of a single agent?
+ - Do the agents have different expertise that I need?
+ - Advantages of multi-agents
+ - Objectivity: provide more reliable and objective feedback towards sub-task performance
+ - Clear instructions: task-switches can lead to significant performance degradation
+ - Scalability: Easier to scale systems by adding more agents
+ - Fault tolerance: if one agent fails, others can continue
+ - How to use agents for code genration?
+ - look at the "Tutorial fro ICML 2025: Jailbreking LLMs and Agentic Systems"
+ - [A survey of self-evolving agents](https://arxiv.org/abs/2507.21046) [[PROJECTS/MOSAICO]] [[TEACHING/SE4AS]] [[Reading]]
+ id:: 68b6a403-1ce2-4fe5-9668-54e32ac0e222
+ :LOGBOOK:
+ CLOCK: [2025-09-02 Tue 10:20:45]--[2025-09-02 Tue 10:20:46] => 00:00:01
+ :END:
+ - *Challenges and Opportunities*
+ - TODO [2503.13657 - Why Do Multi-Agent LLM Systems Fail?](https://arxiv.org/abs/2503.13657) [[Reading]]
+ - Non-determinism
+ - [En Empirical Study of the non-determinism of chatgpt and code generation](https://arxiv.org/abs/2308.02828) [[Reading]]
+ - Efficiency
+ - SWE-Effi: Re-Evaluating SWE Agent Solutions for their Efficiency
+ - [SWE Effi](https://centre-for-software-excellence.github.io/SWE-Effi/about/introducing-SWE-effi)
+ - [EffiBench: Benchmarking the Efficiency of Automatically Generated Code](https://arxiv.org/abs/2402.02037)
+ id:: 68b6a86a-0914-4535-b10a-d81519358f6a
+ - Hallucination
+ - [Hallucination Detection in LLM](https://arxiv.org/abs/2502.15844) [[Reading]]
+ -
+ -
+ - *Books*:
+ - Agent-based software development - Michael Luck, D'Inverno et
+ - [Agent-based Software Development - Michael M. Luck, Ronald Ashri, Mark D'Inverno - Google Books](https://books.google.es/books/about/Agent_based_Software_Development.html?id=AXMhngEACAAJ&redir_esc=y)
+ -
+ - ##### **AI and Software Development**
+ - Expectation from Industry about AI
+ - For CTO the main reason is 20% productivity gain
+ - For Engineer managers/team leads: faster delivery, satisfaction (+10 hours/week saved). They are worried about quality and maintainability
+ - For senior/staff developers: Skeptical, fear of being behind or deskilled (19% slower for experienced devs)
+ - For junor developers: embrace it quickly, unclear how it affects learning
+ - Il ruolo di AI secondo Microsoft
+ - 
+ - Risks from an industry perspective
+ - Intellectual property
+ - Security
+ - Reliability
+ - Reliance (e.g., what happens when Copilot is down)
+ - Guardrails
+ - Trust
+ - Evaluation
+ - How to compare different tools/agents?
+ - [Vibe Busters - Your AI-Generated Codebase is Haunted.](https://vibebusters.com/)
+ - When it works best
+ - Scripting
+ - Small projects
+ - Prototyping
+ - Code review
+ - When it doesn't
+ - Very large codebases
+ - Custom undocumented frameworks or tooling
+ - Debugging internals
+ - [MIT report: 95% of generative AI pilots at companies are failing | Fortune](https://fortune.com/2025/08/18/mit-report-95-percent-generative-ai-pilots-at-companies-failing-cfo/) [[Reading]]
+ - Why should we study
+ - Not knowing things in themselvers limits your ability to use them ot to realize that what you are reading is wrong [[TEACHING/SE4AS]]
+ - TESTING EFFECT
+ - >In psychology, the testing effect is ==the phenomenon where taking a practice test or retrieving information from memory enhances long-term memory retention and learning more effectively than passively restudying the same material==. This finding shows that the act of "testing" is not just an assessment tool but also a powerful learning tool, improving one's ability to recall information later.
+ -
+ - ##### **From workflow-based to fully-agentic applications: smolagents and LangGraph - Antonio Garcia-Dominguez**
+ collapsed:: true
+ - [agarciadom/llma4se-2025: Materials for LLMA4SE talk + workshop](https://github.com/agarciadom/llma4se-2025) [[TEACHING/SE4AS]]
+ - *From LMs to agents*
+ - Agents = LM + tools + prompt
+ - tool is a manually written code that an LM can invoke to retrieve information, or permorm an action on our behalf
+ - Interesting patterns of integrating different agents
+ -
+ - ##### **Workshop 2 - Development of agentic applications with human-in-the-loop via LangGraph**
+ source:: [agarciadom/llma4se-2025: Materials for LLMA4SE talk + workshop](https://github.com/agarciadom/llma4se-2025/tree/main)
+ collapsed:: true
+ - default langsmith API KEY
+ - ```
+ LANGSMITH_API_KEY="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"
+ ```
+ - The Service langsmith API KEY
+ - ```
+ LANGSMITH_API_KEY="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"
+ ```
+ - Context schema is to configure the agent
+ -
\ No newline at end of file
diff --git a/pages/Invited talk at MDE Intelligence.md b/pages/Invited talk at MDE Intelligence.md
new file mode 100644
index 00000000..11648883
--- /dev/null
+++ b/pages/Invited talk at MDE Intelligence.md
@@ -0,0 +1,18 @@
+tags:: #todoist-task, #invitedtalk
+date:: [[28-09-2025]] - 18:40
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ -
+ - ### Notes
+ - You can find the program of the MDE Intelligence 2025 workshop here:
+ [MDE Intelligence](https://mde-intelligence.github.io/#program)
+ - Title: Modeling for Agentic AI - Opportunities for the MDE Community in the AgentWare Era
+ - Abstract: The transition from PromptWare to AgentWare raises fundamental questions on how to design, orchestrate, and govern communities of AI agents in software engineering. The modeling community has an important opportunity to shape this transformation. This talk will highlight how Model-Driven Engineering can provide the abstractions, languages, and tools to specify agent roles, protocols, governance policies, and quality assessment frameworks for multi-agent systems. I will discuss how the EU MOSAICO project (https://mosaico-project.eu/) is going to leverage model-based techniques to build a repository of AI agents enriched with standardized metadata, KPIs, and governance mechanisms. By presenting MOSAICO's contributions, such as its taxonomy of AI agents, repository design, and [[benchmarking framework]], the talk will highlight specific research challenges for the MDE community, including the modeling of agent roles, interaction protocols, and governance policies.
+ - Short bio: Davide Di Ruscio is a Full Professor of Computer Science at the University of L’Aquila, Italy, where he also serves as Director of the PhD Program in Information and Communication Technology. His research interests include software engineering, model-driven engineering (MDE), and the application of artificial intelligence to software development. He has contributed to several European and national research projects, most recently MOSAICO, a Horizon Europe project on multi-agent systems for software engineering. He has co-authored numerous publications in top-tier international venues and has been actively involved in conference organization and editorial activities. His current work focuses on how generative AI and multi-agent systems can transform the engineering of software systems.
+ - SCHEDULE
+ - The evolution of software development paradigms - 5 mins
+ - Opportunities and challenges of applying generative AI in software engineering - 5 mins
+ - Introduce the MOSAICO EU project - 10 mins
+ - Opportunities for the MDE community - 10 mins
+ - Slides: 
\ No newline at end of file
diff --git a/pages/Invited talk at workshop ASE.md b/pages/Invited talk at workshop ASE.md
new file mode 100644
index 00000000..88b7742d
--- /dev/null
+++ b/pages/Invited talk at workshop ASE.md
@@ -0,0 +1,12 @@
+tags:: #todoist-task, #invitedtalk, [[PROJECTS/MOSAICO]]
+date:: [[28-09-2025]] - 18:24
+email:: ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAhQr2DBAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Il talk si farà il [[16-11-2025]]
+ - **Title**: From PromptWare to AgentWare: Multi-Agent Systems for Reliable AI in Software Engineering
+ - **Abstract**: Software development is rapidly evolving from traditional coding practices to new paradigms where Large Language Models (LLMs) and agentic AI play a central role. After the emergence of PromptWare, we are now entering the AgentWare era, where multi-agent systems (MAS) collaborate to design, implement, and validate software. This talk explores the opportunities and challenges of LLM-based multi-agent systems in software engineering. I will illustrate how multiple AI agents can cooperate, complement each other's strengths, and be governed under human supervision to increase reliability, transparency, and trust in AI-assisted development. Special emphasis will be given to the MOSAICO Horizon Europe project (https://mosaico-project.eu/), which is building a platform for managing, orchestrating, and supervising AI agents tailored to software engineering tasks. The talk will present examples, insights from existing MAS frameworks, and future research directions on governance and quality assessment in AI-driven software engineering.
+ - **Short bio**: Davide Di Ruscio is a Full Professor of Computer Science at the University of L’Aquila, Italy, where he also serves as Director of the PhD Program in Information and Communication Technology. His research interests include software engineering, model-driven engineering (MDE), and the application of artificial intelligence to software development. He has contributed to several European and national research projects, most recently MOSAICO, a Horizon Europe project on multi-agent systems for software engineering. He has co-authored numerous publications in top-tier international venues and has been actively involved in conference organization and editorial activities. His current work focuses on how generative AI and multi-agent systems can transform the engineering of software systems.
\ No newline at end of file
diff --git a/pages/KaraKeep-Highlights (conflicted copy 2025-12-27 195913).md b/pages/KaraKeep-Highlights (conflicted copy 2025-12-27 195913).md
new file mode 100644
index 00000000..5bb5aa8f
--- /dev/null
+++ b/pages/KaraKeep-Highlights (conflicted copy 2025-12-27 195913).md
@@ -0,0 +1,76 @@
+icon:: ✏️
+generation_time:: [[2025-12-27]] T17:00:54Z
+
+- # **TODOs and IDEAs**
+ - {{query (and [[TODO]] [[KaraKeep-Highlights]] (or [[Ideas]] [[KaraKeep-Highlights]]))}}
+ query-table:: true
+ query-properties:: [:block]
+- ## **Open - Le regole del gioco**
+ source:: https://www.open.online/le-regole-del-gioco/
+ url:: https://karakeep.diruscio.org/dashboard/preview/au4h7zjntjdakspb0gcl51bd
+ tags:: [[behavioral addiction]] [[digital addiction]] [[gaming disorder]] [[mental health]] [[youth risk]]
+ - Le cosiddette New Addiction sono capaci di diventare l’obiettivo primario della nostra mente finché l’opzione di smettere non rappresenta più una scelta libera.
+ background-color:: green
+ - in Italia tra il 10 e il 15% della popolazione presenti comportamenti che rientrano, in forma più o meno manifesta, nei criteri delle nuove dipendenze
+ background-color:: green
+ - Durante il primo lockdown uno studio pubblicato su Frontiers in Psychiatry, condotto dall’Istituto di Neuroscienze di Firenze in collaborazione con il Dipartimento di Psichiatria e Scienze del Comportamento della Albert Einstein College of Medicine di New York, ha rilevato che il 23,6% dei soggetti coinvolti mostrava sintomi compatibili con una forma di gioco d’azzardo patologico.
+ background-color:: green
+ - Nello studio condotto su studenti delle scuole superiori pubblicato su CNS Spectrums, i ricercatori hanno registrato il 5,4% degli studenti nella categoria di “internet addicted”; percentuali preoccupanti sono emerse anche per altre dipendenze: il 16% degli studenti ha ottenuto per esempio punteggi talmente alti nella scala dedicata al gioco d’azzardo da essere classificato nella fascia clinica definita come “problema estremo”
+ background-color:: green
+ - id:: 69500f28-4528-4606-9cdb-acc40518e3a4
+ > **Note:** #card
+- ## **Top AI Agentic Workflow Patterns**
+ source:: https://blog.bytebytego.com/p/top-ai-agentic-workflow-patterns
+ url:: https://karakeep.diruscio.org/dashboard/preview/iz529wt1xybxstag5cmcrl1l
+ tags:: [[AI automation]] [[Agentic Workflows]] [[Artificial Intelligence]] [[Reflective Systems]] [[Tool Integration]]
+ - An agentic workflow doesn’t just respond to a single instruction. Instead, it operates with a degree of autonomy, making decisions about how to approach a task, what steps to take, and how to adapt based on what it discovers along the way. This represents a fundamental shift in how we think about using AI systems.
+ background-color:: green
+ - > **Note:** #IMPORTANT
+ - An agentic system, however, might first search the web for current information on the topic, then organize the findings into themes, draft sections of the report, review each section for accuracy and coherence, revise weak areas, and finally compile everything into a polished document
+ background-color:: green
+ - Instead of generating output in a single pass, agentic workflows involve cycles where the agent takes an action, observes the result, and uses that observation to inform the next action
+ background-color:: green
+ - Agentic workflows bring this same adaptive, iterative quality to AI systems.
+ background-color:: green
+ - five essential agentic workflow patterns
+ background-color:: blue
+ - The reflection pattern works best for tasks where quality matters more than speed and where there are subjective aspects that benefit from review.
+ background-color:: blue
+ - > **Note:** Reflection Pattern
+ - In the tool use pattern, agents are equipped with a set of capabilities they can invoke when needed. These might include web search engines for finding current information, APIs for accessing services like weather data or stock prices, code interpreters for running programs and performing calculations, database query tools for retrieving specific records, file system access for reading and writing documents, and countless other specialized functions. The critical distinction from traditional software is that the agent itself decides when and how to use these tools based on the task at hand.
+ background-color:: blue
+ - > **Note:** Tool use pattern
+- ## **Contratto “Istruzione e Ricerca” 2022/2024, FLC CGIL: retribuzioni insufficienti, non firmiamo**
+ source:: https://m.flcgil.it/comunicati-stampa/flc/contratto-istruzione-e-ricerca-2022-2024-flc-cgil-retribuzioni-insufficienti-non-firmiamo.flc
+ url:: https://karakeep.diruscio.org/dashboard/preview/khv9wkq94ax8wi79swli9hnz
+ tags:: [[collective bargaining]] [[education]] [[labor union]] [[public sector]] [[research]]
+ - La nostra non firma di oggi vuole essere un messaggio chiaro nei confronti di un Governo che ha scientemente programmato il taglio delle retribuzioni di oltre 1,3 milioni di lavoratrici e lavoratori, già con gli stipendi più bassi di tutto il settore pubblico. Ora il Governo si deve far carico di colmare il divario retributivo con il resto dei dipendenti della pubblica amministrazione e garantire il completo recupero dell’inflazione
+ background-color:: green
+- ## **GitHub - muratcankoylan/Agent-Skills-for-Context-Engineering: A comprehensive collection of Agent Skills for context engineering, multi-agent architectures, and production agent systems. Use when building, optimizing, or debugging agent systems that require effective context management.**
+ source:: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering
+ url:: https://karakeep.diruscio.org/dashboard/preview/mujjzfwwjb2xbqiugz3i92nv
+ tags:: [[AI System Optimization]] [[Agent Architectures]] [[Artificial Intelligence]] [[Context Engineering]] [[Multi-Agent Systems]] [[agent skills]]
+ - The fundamental challenge is that context windows are constrained not by raw token capacity but by attention mechanics
+ background-color:: green
+ - "lost-in-the-middle" phenomenon, U-shaped attention curves, and attention scarcity.
+ background-color:: yellow
+ - Effective context engineering means finding the smallest possible set of high-signal tokens that maximize the likelihood of desired outcomes.
+ background-color:: blue
+ - > **Note:** #card
+- ## **7 Tiny AI Models for Raspberry Pi - KDnuggets**
+ source:: https://www.kdnuggets.com/7-tiny-ai-models-for-raspberry-pi
+ url:: https://karakeep.diruscio.org/dashboard/preview/wrwx75un37buyqnusi33ygm7
+ tags:: [[Artificial Intelligence]] [[Local AI]] [[Machine Learning]] [[READ]] [[Raspberry Pi]] [[Tiny AI Models]]
+ - aggressive quantization
+ background-color:: green
+ - llama.cpp
+ background-color:: green
+ - > **Note:** What's llama.cpp? #TODO To be checked.
+ - tool calling, vision understanding, and structured outputs
+ background-color:: green
+ - vision‑language model
+ background-color:: green
+ - > **Note:** Vision Language Models (VLMs) are powerful AI systems that merge computer vision and natural language processing, allowing them to understand, interpret, and generate content from both images/videos and text inputs, enabling tasks like describing photos (captioning), answering questions about visuals (VQA), generating images from text, and understanding complex documents. #card
+ - Tiny models have reached a point where size is no longer a limitation to capability. The Qwen 3 series stands out in this list, delivering performance that rivals much larger language models and even challenges some proprietary systems. If you are building applications for a Raspberry Pi or other low-power devices, Qwen 3 is an excellent starting point and well worth integrating into your setup.
+ background-color:: green
+ - > **Note:** #IMPORTANT
\ No newline at end of file
diff --git a/pages/KaraKeep-Highlights-Summary.md b/pages/KaraKeep-Highlights-Summary.md
new file mode 100644
index 00000000..c0540818
--- /dev/null
+++ b/pages/KaraKeep-Highlights-Summary.md
@@ -0,0 +1,41 @@
+## Summary
+The article discusses the advancements in AI agent frameworks, specifically LangChain and LangGraph. LangChain is a user-friendly tool for building AI agents, while LangGraph is a lower-level framework for highly custom and controllable agents. The article also highlights the importance of agentic workflows, which allow AI systems to make decisions and adapt based on their environment. Five essential agentic workflow patterns are identified: reflection, tool use, planning, learning, and optimization.
+- ## Mermaid Mindmap
+- {{renderer :mermaid_694c8c42-5621-4d95-bd16-8261a5eb4f1c, 3}}
+ - ```mermaid
+ graph TD
+ A[LangChain] --> B[User-Friendly AI Agent Framework]
+ A --> C[Standard Tool Calling Architecture]
+ A --> D[Provider Agnostic Design]
+ A --> E[Middleware for Customization]
+ E --> F[Note: MOSAICO]
+ E --> G[LangGraph: Lower Level Framework]
+ G --> H[Useful for Highly Custom and Controllable Agents]
+ G --> I[Support Production-Grade, Long Running Agents]
+ B --> J[Background Color: Green]
+ C --> J
+ D --> J
+ E --> J
+ F --> J
+ H --> J
+ A --> K[Top AI Agentic Workflow Patterns]
+ K --> L[AI Automation]
+ K --> M[Agentic Workflows]
+ K --> N[Reflective Systems]
+ K --> O[Tool Integration]
+ L --> P[An agentic workflow doesn’t just respond to a single instruction. Instead, it operates with a degree of autonomy, making decisions about how to approach a task, what steps to take, and how to adapt based on what it discovers along the way.]
+ L --> Q[An agentic system might first search the web for current information on the topic, then organize the findings into themes, draft sections of the report, review each section for accuracy and coherence, revise weak areas, and finally compile everything into a polished document.]
+ L --> R[Instead of generating output in a single pass, agentic workflows involve cycles where the agent takes an action, observes the result, and uses that observation to inform the next action]
+ L --> S[Agentic workflows bring this same adaptive, iterative quality to AI systems.]
+ K --> T[Five Essential Agentic Workflow Patterns]
+ T --> U[Reflection Pattern: Works best for tasks where quality matters more than speed and where there are subjective aspects that benefit from review.]
+ T --> V[Tool Use Pattern: Agents are equipped with a set of capabilities they can invoke when needed. These might include web search engines, APIs, code interpreters, database query tools, and file system access.]
+ K --> W[The Fundamental Challenge: Context windows are constrained not by raw token capacity but by attention mechanics]
+ W --> X[U-Shaped Attention Curves, and Attention Scarcity]
+ W --> Y[Effective Context Engineering Means Finding the Smallest Possible Set of High-Signal Tokens that Maximize the Likelihood of Desired Outcomes.]
+ K --> Z[7 Tiny AI Models for Raspberry Pi - KDnuggets]
+ Z --> AA[Aggressive Quantization]
+ Z --> AB[llama.cpp: What's llama.cpp? #TODO To be checked.]
+ Z --> AC[Tool Calling, Vision Understanding, and Structured Outputs]
+ Z --> AD[Vision-Language Model: Merges Computer Vision and Natural Language Processing, Allowing Them to Understand, Interpret, and Generate Content from Both Images/Videos and Text Inputs, Enabling Tasks Like Describing Photos (Captioning), Answering Questions About Visuals (VQA), Generating Images from Text, and Understanding Complex Documents.]
+ ```
\ No newline at end of file
diff --git a/pages/KaraKeep-Highlights.md b/pages/KaraKeep-Highlights.md
new file mode 100644
index 00000000..be75f65b
--- /dev/null
+++ b/pages/KaraKeep-Highlights.md
@@ -0,0 +1,80 @@
+icon:: ✏️
+generation_time:: [[2025-12-27]] T19:00:54Z
+
+- # **TODOs and IDEAs**
+ - {{query (and [[TODO]] [[KaraKeep-Highlights]] (or [[Ideas]] [[KaraKeep-Highlights]]))}}
+ query-table:: true
+ query-properties:: [:block]
+- ## **Open - Le regole del gioco**
+ source:: https://www.open.online/le-regole-del-gioco/
+ url:: https://karakeep.diruscio.org/dashboard/preview/au4h7zjntjdakspb0gcl51bd
+ tags:: [[behavioral addiction]] [[digital addiction]] [[gaming disorder]] [[mental health]] [[youth risk]]
+ - Le cosiddette New Addiction sono capaci di diventare l’obiettivo primario della nostra mente finché l’opzione di smettere non rappresenta più una scelta libera.
+ background-color:: green
+ - in Italia tra il 10 e il 15% della popolazione presenti comportamenti che rientrano, in forma più o meno manifesta, nei criteri delle nuove dipendenze
+ background-color:: green
+ - Durante il primo lockdown uno studio pubblicato su Frontiers in Psychiatry, condotto dall’Istituto di Neuroscienze di Firenze in collaborazione con il Dipartimento di Psichiatria e Scienze del Comportamento della Albert Einstein College of Medicine di New York, ha rilevato che il 23,6% dei soggetti coinvolti mostrava sintomi compatibili con una forma di gioco d’azzardo patologico.
+ background-color:: green
+ - Nello studio condotto su studenti delle scuole superiori pubblicato su CNS Spectrums, i ricercatori hanno registrato il 5,4% degli studenti nella categoria di “internet addicted”; percentuali preoccupanti sono emerse anche per altre dipendenze: il 16% degli studenti ha ottenuto per esempio punteggi talmente alti nella scala dedicata al gioco d’azzardo da essere classificato nella fascia clinica definita come “problema estremo”
+ background-color:: green
+ - > **Note:** #card
+
+- ## **LangChain and LangGraph Agent Frameworks Reach v1.0 Milestones**
+ source:: https://blog.langchain.com/langchain-langgraph-1dot0/
+ url:: https://karakeep.diruscio.org/dashboard/preview/gfuwsnyaj3k8sglws9kncv27
+ tags:: [[Agent Frameworks]] [[Artificial Intelligence]] [[Machine Learning Framework]] [[Open Source]] [[P1]] [[Software Development]]
+ - LangGraph is a lower level framework and runtime, useful for highly custom and controllable agents, designed to support production-grade, long running agents
+ background-color:: green
+ - > **Note:** [[MOSAICO]]
+
+- ## **Top AI Agentic Workflow Patterns**
+ source:: https://blog.bytebytego.com/p/top-ai-agentic-workflow-patterns
+ url:: https://karakeep.diruscio.org/dashboard/preview/iz529wt1xybxstag5cmcrl1l
+ tags:: [[AI automation]] [[Agentic Workflows]] [[Artificial Intelligence]] [[Reflective Systems]] [[Tool Integration]]
+ - An agentic workflow doesn’t just respond to a single instruction. Instead, it operates with a degree of autonomy, making decisions about how to approach a task, what steps to take, and how to adapt based on what it discovers along the way. This represents a fundamental shift in how we think about using AI systems.
+ background-color:: green
+ - > **Note:** #IMPORTANT
+ - An agentic system, however, might first search the web for current information on the topic, then organize the findings into themes, draft sections of the report, review each section for accuracy and coherence, revise weak areas, and finally compile everything into a polished document
+ background-color:: green
+ - Instead of generating output in a single pass, agentic workflows involve cycles where the agent takes an action, observes the result, and uses that observation to inform the next action
+ background-color:: green
+ - Agentic workflows bring this same adaptive, iterative quality to AI systems.
+ background-color:: green
+ - five essential agentic workflow patterns
+ background-color:: blue
+ - The reflection pattern works best for tasks where quality matters more than speed and where there are subjective aspects that benefit from review.
+ background-color:: blue
+ - > **Note:** Reflection Pattern
+ - In the tool use pattern, agents are equipped with a set of capabilities they can invoke when needed. These might include web search engines for finding current information, APIs for accessing services like weather data or stock prices, code interpreters for running programs and performing calculations, database query tools for retrieving specific records, file system access for reading and writing documents, and countless other specialized functions. The critical distinction from traditional software is that the agent itself decides when and how to use these tools based on the task at hand.
+ background-color:: blue
+ - > **Note:** Tool use pattern
+
+- ## **GitHub - muratcankoylan/Agent-Skills-for-Context-Engineering: A comprehensive collection of Agent Skills for context engineering, multi-agent architectures, and production agent systems. Use when building, optimizing, or debugging agent systems that require effective context management.**
+ source:: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering
+ url:: https://karakeep.diruscio.org/dashboard/preview/mujjzfwwjb2xbqiugz3i92nv
+ tags:: [[AI System Optimization]] [[Agent Architectures]] [[Artificial Intelligence]] [[Context Engineering]] [[Multi-Agent Systems]] [[agent skills]]
+ - The fundamental challenge is that context windows are constrained not by raw token capacity but by attention mechanics
+ background-color:: green
+ - "lost-in-the-middle" phenomenon, U-shaped attention curves, and attention scarcity.
+ background-color:: yellow
+ - Effective context engineering means finding the smallest possible set of high-signal tokens that maximize the likelihood of desired outcomes.
+ background-color:: blue
+ - > **Note:** #card
+
+- ## **7 Tiny AI Models for Raspberry Pi - KDnuggets**
+ source:: https://www.kdnuggets.com/7-tiny-ai-models-for-raspberry-pi
+ url:: https://karakeep.diruscio.org/dashboard/preview/wrwx75un37buyqnusi33ygm7
+ tags:: [[Artificial Intelligence]] [[Local AI]] [[Machine Learning]] [[READ]] [[Raspberry Pi]] [[Tiny AI Models]]
+ - aggressive quantization
+ background-color:: green
+ - llama.cpp
+ background-color:: green
+ - > **Note:** What's llama.cpp? #TODO To be checked.
+ - tool calling, vision understanding, and structured outputs
+ background-color:: green
+ - vision‑language model
+ background-color:: green
+ - > **Note:** Vision Language Models (VLMs) are powerful AI systems that merge computer vision and natural language processing, allowing them to understand, interpret, and generate content from both images/videos and text inputs, enabling tasks like describing photos (captioning), answering questions about visuals (VQA), generating images from text, and understanding complex documents. #card
+ - Tiny models have reached a point where size is no longer a limitation to capability. The Qwen 3 series stands out in this list, delivering performance that rivals much larger language models and even challenges some proprietary systems. If you are building applications for a Raspberry Pi or other low-power devices, Qwen 3 is an excellent starting point and well worth integrating into your setup.
+ background-color:: green
+ - > **Note:** #IMPORTANT
diff --git a/pages/LARC-2026-70.md b/pages/LARC-2026-70.md
new file mode 100644
index 00000000..d37b6ade
--- /dev/null
+++ b/pages/LARC-2026-70.md
@@ -0,0 +1,22 @@
+type:: [[REVIEWS]]
+tags::
+year:: 2026
+venue:: [[ICSE2026-WS]]
+full-title:: AI-Assisted Modeling: DSL-Driven AI Interactions
+date-start:: [[07-12-2025]] - 16:08
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@AI-Assisted Modeling: DSL-Driven AI Interactions]]
+parent::
+todoist:: https://app.todoist.com/app/task/l-arc-2026-new-review-assignments-6fGCJrj25FF2VXw8
+
+ - ### [[Comments]]
+ - SUMMARY: The paper proposes an approach to assist programming activities by integrating domain-specific modeling techniques with real-time graphical visualizations of AI-generated code. The conceived technique has been implemented as a Visual Studio Code extension for the Lingua Franca language that enables iterative model development through structured prompt templates and dialog-driven feedback mechanisms.
+ - COMMENTS: The paper is about an interesting application of AI technologies and domain-specific modeling. However, I have some major concerns that are related to the presentation of the work. Most notably, the paper's primary goal, whether it targets modeling activities (e.g., defining system behavior) or code development (e.g., generating implementation artifacts), remains unclear. The examples (e.g., adding a "compute" reactor that multiplies input by three) and workflow descriptions suggest a modeling-centric focus, yet phrases like "automatically integrated in the overall system" imply code generation is the end goal. This dual perspective risks confusion for readers. The authors should explicitly state whether the extension prioritizes model refinement before code generation or enables parallel modeling/code development with visual feedback.
+ - The concept of "visual verification tailored to DSL development" also lacks specificity. The paper mentions model checking but does not clarify the scope of verification, whether it involves syntax validation, semantic consistency checks, or runtime behavior testing. Given the example where the multiplier function is defined in code rather than the model (e.g., "multiplies input by three" vs. "multiplies input by five"), it is essential to specify how the system handles manual interventions. For instance, if a model source is altered post-generation, does the system automatically update the code? The current description implies such updates are manual, yet the workflow claims to support "iterative" refinement without detailing this feedback loop.
+ - Additionally, the paper underestimates the complexity of DSL-specific tooling. Listing 2 shows the Lingua Franca timer definition, but the efforts required to define language-specific APIs are not properly discussed. The authors note that "generating graphical models via AI is technically demanding" yet fail to address how this challenge scales across diverse DSLs. A more thorough discussion of the trade-offs in API design, particularly for languages with complex semantics, would strengthen the paper's relevance. The example in Figure 4 further highlights this gap: the configuration step (e.g., reactor connections) is omitted, and the Lingua Franca language's settings are not visualized. Clarifying that this is a modeling phase rather than a code generation step would prevent misinterpretation.
+ - Overall, the approach is innovative but requires sharper articulation of its boundaries and mechanisms. The paper would benefit from a dedicated section addressing how manual interventions (e.g., modifying model sources) trigger automated code updates, as this is central to the claimed "iterative" workflow. With these refinements, the contribution could more effectively advance the field of DSL-driven AI interactions.
+ - Despite these considerations, which can be addressed through minor revisions, the paper presents interesting insights to be discussed during the workshop.
+-
\ No newline at end of file
diff --git a/pages/LLM-based Planner.md b/pages/LLM-based Planner.md
new file mode 100644
index 00000000..c8892038
--- /dev/null
+++ b/pages/LLM-based Planner.md
@@ -0,0 +1,18 @@
+tags:: #TEACHING/SE4AS
+
+- [[OLLAMA]]
+ - ```
+ docker exec -it my_se4as_pr_PLANNER /bin/bash
+
+ curl -s http://host.docker.internal:11434/api/chat -H "Content-Type: application/json" -d '{
+ "model": "qwen3:4b",
+ "messages": [
+ {"role": "user", "content": "Say hello"}
+ ],
+ "stream": false
+ }'
+
+ ollama list //to list the available models
+ ```
+ - docker exec -it n8n_ollama_1 sh
+ -
\ No newline at end of file
diff --git a/pages/LLMs-from-scratch%3A Implement a ChatGPT-like LLM in PyTorch from scratch, step by step.md b/pages/LLMs-from-scratch%3A Implement a ChatGPT-like LLM in PyTorch from scratch, step by step.md
new file mode 100644
index 00000000..a0c16d9a
--- /dev/null
+++ b/pages/LLMs-from-scratch%3A Implement a ChatGPT-like LLM in PyTorch from scratch, step by step.md
@@ -0,0 +1,3 @@
+source:: [rasbt/LLMs-from-scratch: Implement a ChatGPT-like LLM in PyTorch from scratch, step by step](https://github.com/rasbt/LLMs-from-scratch?utm_campaign=17499772-%5BLIVE%5D-CAMP-PUBLIC_EXTERNAL-TOBO-LI-AI_Agents_Hub_PUSH-2025_07&utm_content=346646057&utm_medium=social&utm_source=linkedin&hss_channel=lcp-91651675)
+
+ -
\ No newline at end of file
diff --git a/pages/MDE_Intelligence_2024_paper_5.md b/pages/MDE_Intelligence_2024_paper_5.md
index dae6b545..cce8944c 100644
--- a/pages/MDE_Intelligence_2024_paper_5.md
+++ b/pages/MDE_Intelligence_2024_paper_5.md
@@ -33,7 +33,7 @@ todoist:: https://app.todoist.com/app/task/5-thomas-buchmann-rene-peinl-and-feli
- - “identification of processes based on documents” ([Buchmann et al., 2018, p. 2](zotero://select/library/items/YA3WBXNL)) ([pdf](zotero://open-pdf/library/items/IA6G7ECR?page=2&annotation=D55I4LBU)) #5fb236
- - “Vidgof et al.” ([Buchmann et al., 2018, p. 2](zotero://select/library/items/YA3WBXNL)) ([pdf](zotero://open-pdf/library/items/IA6G7ECR?page=2&annotation=PE22Y6P8)) #ff6666
- *Missing ref.*
- - - ““which tasks can be achieved with already existing models” and that data sets, benchmarks and new LLMs specialized on process management are required.” ([Buchmann et al., 2018, p. 2](zotero://select/library/items/YA3WBXNL)) ([pdf](zotero://open-pdf/library/items/IA6G7ECR?page=2&annotation=WSHW9BDT)) #5fb236
+ - - ““which tasks can be achieved with already existing models” and that data sets, [[benchmarks]] and new LLMs specialized on process management are required.” ([Buchmann et al., 2018, p. 2](zotero://select/library/items/YA3WBXNL)) ([pdf](zotero://open-pdf/library/items/IA6G7ECR?page=2&annotation=WSHW9BDT)) #5fb236
- - “[4] use” ([Buchmann et al., 2018, p. 2](zotero://select/library/items/YA3WBXNL)) ([pdf](zotero://open-pdf/library/items/IA6G7ECR?page=2&annotation=89P468CV)) #ffd400
- *Avoid using references as subject of sentences. Write instead Forell et. al [4] use...*
- - “mining declarative process models from textual descriptions,” ([Buchmann et al., 2018, p. 2](zotero://select/library/items/YA3WBXNL)) ([pdf](zotero://open-pdf/library/items/IA6G7ECR?page=2&annotation=4UAJ6QDV)) #ff6666
diff --git a/pages/MDE_Intelligence_2025_modeling_ai_driven.md b/pages/MDE_Intelligence_2025_modeling_ai_driven.md
new file mode 100644
index 00000000..f69716d3
--- /dev/null
+++ b/pages/MDE_Intelligence_2025_modeling_ai_driven.md
@@ -0,0 +1,23 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2025
+venue:: [[MODELS-WS]]
+full-title:: Modeling AI-Driven Workflows for Ecosystem Resilience Prediction
+date-start:: [[29-07-2025]] - 15:17
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Modeling AI-Driven Workflows for Ecosystem Resilience Prediction]]
+parent::
+todoist:: https://app.todoist.com/app/task/3-tiago-sousa-nicolas-guelfi-and-benoit-ries-modeling-ai-driven-workflows-for-ec-6cVfQ9fHM7mgvQ2c
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - **SUMMARY: **The paper presents an approach for supporting the development of Ecosystem Resilience Prediction Systems (ERPS). The approach consists of two main metamodels, i.e., EcoSys and PredSys, to precisely define the ecosystems of interest and design the corresponding AI-based prediction systems. The approach's primary goal is to ensure the consistency and traceability of the prediction workflow involving ecosystem properties, data constraints, and AI capabilities. Different scenarios are given to illustrate the adoption of the presented approach.
+ - *COMMENTS:* The paper is interesting and about a relevant topic. I have only a few concerns related to the work presentation. In particular,
+ - The concept of *ecosystem resilience* is central to the work, but it is never explicitly defined initially. It remains unclear whether the paper refers exclusively to natural ecosystems and what specific resilience properties are considered. Similarly, the application context emerges only later, which can confuse readers. Early inclusion of concrete examples, such as the types of ecosystems or the resilience indicators targeted, would improve the work's readability.
+ - The methodology introduces important concepts, yet some remain abstract. For example, while the authors mention *resilience patterns*, they do not provide concrete examples of what these patterns are or how they are used to drive prediction. It is also unclear where features of interest and prediction goals are specified in the proposed models.
+ - The description of how data is validated against the requirements defined in EcoSys is insufficient and should be expanded. The same applies to the roles of users: the paper should clarify who is expected to use the approach (ecologists, AI engineers, both?) and how they interact during the process.
+ - A significant weakness is the limited connection with practical execution environments. The workflow is well described at a conceptual level, but how the presented models are operationalized remains unclear. Are there tools or environments capable of interpreting these specifications? Are there code generation steps involved? Without this information, the approach risks remaining purely theoretical. Similarly, while the scenarios are helpful, they do not bridge the gap between abstract modeling and real-world deployment.
\ No newline at end of file
diff --git a/pages/MDE_Intelligence_2025_paper_15.md b/pages/MDE_Intelligence_2025_paper_15.md
new file mode 100644
index 00000000..4b312d7b
--- /dev/null
+++ b/pages/MDE_Intelligence_2025_paper_15.md
@@ -0,0 +1,34 @@
+type:: [[REVIEWS]]
+tags::
+year:: 2025
+venue:: [[MODELS-WS]]
+full-title:: Generation of Unit Tests for Test-Driven Development using Large Language Models
+date-start:: [[30-07-2025]] - 12:22
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@Generation of Unit Tests for Test-Driven Development using Large Language Models]]
+parent::
+todoist:: https://app.todoist.com/app/task/15-nathanael-yao-juergen-dingel-and-ali-tizghadam-generation-of-unit-tests-for-t-6cVfQ9gQhx4Hq826
+collapsed:: true
+
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - **SUMMARY** The paper presents an approach based on generative AI, to support Test-Driven Development (TDD) by automatically generating unit tests from high-level user-defined goals. The approach is supported by a prototype developed primarily for the network domain and evaluated through manual checks and feedback from an industrial partner.
+ - **COMMENTS ** The work addresses an important topic, and the idea of generating tests from user-specified goals rather than implementation code is interesting. However, I have some concerns about the presentation of the work as detailed below:
+ - The presentation of the proposed approach, especially in Section 5, is not effective. The steps involved in refining high-level goals into subgoals and generating unit tests are described in a confusing manner, with unclear distinctions between what is generic and what is application-specific.
+ - The human involvement in the process, how feedback is integrated, and how the iterative nature of TDD is supported remain ambiguous. Figures, particularly the algorithm in Figure 1, do not enhance understanding; a more concise representation of the three main steps of the process would be more appropriate.
+ - The explanation of the pool of basic actions raises some questions: Who defines these actions, whether they are domain-specific, and how they scale to arbitrary user goals, as claimed, is not clarified. Similarly, the syntax or format of the goal models is not specified, making it hard to assess the generality of the approach.
+ - When describing the use of few-shot examples for unit test generation, the paper fails to clearly explain how these examples are composed to create tests tailored to the target application and what the expected granularity of the generated unit tests is. Additionally, it should be explicitly stated that the current prototype is Python-specific.
+
+ Overall, the paper presents an interesting idea but requires improving clarity and explanation of the technical details to convey its contribution.
+ - ### [[REVIEWS/Notes]]
+ - ### YELLOW CONCERNS
+ background-color:: yellow
+ - {{query (and [[ffd400]] [[MDE_Intelligence_2025_paper_15]] )}}
+ collapsed:: true
+ - ### ❓️Questions
+ - {{query (and [[question]] [[MDE_Intelligence_2025_paper_15]] )[[question]]}}
+ query-table:: true
+ query-properties:: [:block]
\ No newline at end of file
diff --git a/pages/MDE_Intelligence_2025_paper_6.md b/pages/MDE_Intelligence_2025_paper_6.md
new file mode 100644
index 00000000..e4208375
--- /dev/null
+++ b/pages/MDE_Intelligence_2025_paper_6.md
@@ -0,0 +1,29 @@
+type:: [[REVIEWS]]
+tags::
+year:: 2025
+venue:: [[MODELS-WS]]
+full-title::
+date-start:: [[30-07-2025]] - 14:58
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@LLM-assisted configuration of model-driven business process families]]
+parent::
+todoist:: https://app.todoist.com/app/task/6-daniel-calegari-and-andrea-delgado-llm-assisted-configuration-of-model-driven-6cVfQ9jXM6pqQv9c
+
+ - LLM-assisted configuration of model-driven business process families
+ -
+ - ### [[Highlights]]
+ - ### [[Comments]]
+ - The paper proposes an approach to integrate Large Language Models (LLMs) with a model-driven engineering (MDE) framework for managing business process families. The approach builds on the existing Business Process Family Manager (BPFM) tool and leverages LLMs to generate questionnaires that guide users through the configuration of process variants. The process is supported by metamodels, model-to-model transformations, and a questionnaire mechanism, aiming to improve the configuration of business process variants.
+
+ DETAILED COMMENTS: The paper is about an interesting problem. However, several aspects need clarification to make the contribution clearer and more convincing, as discussed below:
+ - First, the novelty of this work compared to reference [3] must be made explicit early in the paper. Much of the metamodel and underlying concepts are reused, and the added value of integrating LLMs should be better highlighted. Similarly, the BPFM tool appears central to the approach, but its last update dates back four years; this raises concerns about its current applicability and maintenance status, which should be discussed.
+ - The description of business process families is at the conceptual level and remains abstract. To help readers better grasp the approach, illustrative examples of process variants, variation points, and contexts should be introduced earlier in the paper. The same holds for the questionnaire mechanism: while the paper explains that questionnaires guide the configuration, concrete examples of questions should be given, otherwise it's hard to visualize their practical usage. Examples should also be added when discussing how questions relate to facts and dependencies, and when explaining the three parts of the prompt used for LLM generation.
+ - Regarding the LLM-assisted part, the zero-shot experiment is verbose and lacks concrete examples, making the results difficult to interpret.
+ - The evaluation mentions metrics based on semantic equivalence, but how this equivalence was assessed is unclear. Clarifying the methodology here is essential.
+ - The configurations produced by the approach are a crucial output, yet the paper does not sufficiently explain how these configurations are "consumed" in practice.
+ - Finally, details on the technological updates and how they improve over the original proposal [9] would make the paper convincing.
+
+ Overall, while the paper introduces an interesting integration of LLMs in the configuration of business process families, it requires additional illustrative examples and a more explicit discussion of the approach's novelty and the tool's applicability.
\ No newline at end of file
diff --git a/pages/MENTORING___TESISTI.md b/pages/MENTORING___TESISTI.md
index d8b6ece5..6eeac63d 100644
--- a/pages/MENTORING___TESISTI.md
+++ b/pages/MENTORING___TESISTI.md
@@ -1,6 +1,7 @@
-
- # Students
- [[people/azimov]]
+ collapsed:: true
- titolo-tesi::
tipo-tesi:: [[magistrale]]
email:: sherkhan.azimov@student.univaq.it
@@ -34,6 +35,12 @@
struttura:: [[company/Tirasa]]
deadline-titolo:: [[18-01-2023]]
deadline-tesi:: [[11-03-2023]]
+ collapsed:: true
+ - [[people/MarcoGiarrusso]]
+ - type:: [[masterStudent]]
+ titolo-tesi::
+ page-type:: [[people]]
+-
- ## General information
- The next dates to discuss your thesis are as follows ([Dipartimento di Ingegneria e Scienze dell'Informazione e Matematica (univaq.it)](https://www.disim.univaq.it/page.php?page_id=197)):
- 
diff --git a/pages/MODELS Journal-First-track + 1 more.md b/pages/MODELS Journal-First-track + 1 more.md
index e6d8efe0..04f85d25 100644
--- a/pages/MODELS Journal-First-track + 1 more.md
+++ b/pages/MODELS Journal-First-track + 1 more.md
@@ -7,12 +7,24 @@ goal:: ((6832257a-2676-4bf1-8958-81797e5c7003))
CLOCK: [2025-06-03 Tue 16:05:13]--[2025-06-03 Tue 16:05:13] => 00:00:00
:END:
- DONE Mandare mail a Maurane circa il processo
-id:: 683f0108-c7ac-41ae-a6bd-b9c02829e6fc
+ id:: 683f0108-c7ac-41ae-a6bd-b9c02829e6fc
:LOGBOOK:
CLOCK: [2025-06-03 Tue 16:05:10]--[2025-06-03 Tue 16:05:11] => 00:00:01
:END:
- - TODO Inviare email a tutti i paper che dovranno rispondere entro il 20 Giugno (se intendono partecipare o meno)
+ - DONE Inviare email a tutti i paper che dovranno rispondere entro il 20 Giugno (se intendono partecipare o meno)
+ id:: 68584ea7-8fde-4a5e-9367-f7054ced2f88
-
+- Email template
+ - Dear Authors,
+ - Thank you for your interest in the *Journal First* track at MODELS 2025.
+ - We are pleased to inform you that your SoSyM paper has been **accepted** for inclusion in the *Journal First* track of MODELS 2025.
+ - Please note that *Journal First* manuscripts are published in the journal and will not appear in the MODELS 2025 proceedings, but they will be listed in the official conference program.
+ - As you may know, MODELS 2025 will be held in a hybrid format, allowing authors to participate either in person or online.
+ - To ensure your paper is included in the MODELS 2025 program, at least one author must register for the **main conference** by **September 1st** at the applicable rate:
+ - [https://2025.models-conf.com/attending/registration](https://2025.models-conf.com/attending/registration)
+ - We look forward to your presentation at MODELS 2025!
+ - Best regards,
+ - Davide
- [[26-05-2025]] ho contattato Martin per chiedere la lista di paper accettati tra Maggio 2024 e oggi
- Dear Davide,
- please excuse my late reply. I was on vacation last week without
diff --git a/pages/Meeting ATOS.md b/pages/Meeting ATOS.md
index 65ef8c00..465a755c 100644
--- a/pages/Meeting ATOS.md
+++ b/pages/Meeting ATOS.md
@@ -1,7 +1,7 @@
type:: [[meeting]]
external-links::
tags:: [[SERVICES/PLACEMENT-ATENEO]]
-people:: #people/santucci #company/ATOS
+people:: #people/FortunatoSantucci #company/ATOS
tags::
date:: [[07-09-2022]]
diff --git a/pages/Meetings/2020-12-23-Meeting con azienda Eustema - 202012231241.md b/pages/Meetings/2020-12-23-Meeting con azienda Eustema - 202012231241.md
index 528c2d55..4c5c080c 100644
--- a/pages/Meetings/2020-12-23-Meeting con azienda Eustema - 202012231241.md
+++ b/pages/Meetings/2020-12-23-Meeting con azienda Eustema - 202012231241.md
@@ -2,25 +2,25 @@
---
-# ** Meeting con azienda Eustema **
-Date:2020-12-23
-Time: 12:41
-Attendend: #attendance/online
-Project:
-People attended: #people/alfonso
-
----
-
-
-
-![[Pasted image 20201223122559.png]]
-## Domande fatte
+- # ** Meeting con azienda Eustema **
+ Date:2020-12-23
+ Time: 12:41
+ Attendend: #attendance/online
+ Project:
+ People attended: #people/AlfonsoPierantonio
+
+ ---
+
+
+
+ ![[Pasted image 20201223122559.png]]
+- ## Domande fatte
- Qual e' l'uso envisioned per voi?
- Chi e' l'utente finale?
- L'utente business
- Progettista di processo
- Figura intermedia che sa modellare un processo
- Sono interessati all'uso di sistemi di raccomandazione
-## La proposta fatta è:
+- ## La proposta fatta è:
- [ ] Lavorare su un dottorando PON
- [ ] Proposta di progetto MISE in cui l'obiettivo principale e' quello di sviluppare una nuova piattaforma Lowcode interna per supportare lo sviluppo di sistemi mediante gli asset interni (includendo sistemi di raccomandazione)
\ No newline at end of file
diff --git a/pages/Meetings/Mentoring/2021-01-15-Call with Philip Langer Damiano Alfonso and Juri.md b/pages/Meetings/Mentoring/2021-01-15-Call with Philip Langer Damiano Alfonso and Juri.md
index 34401ca8..02569431 100644
--- a/pages/Meetings/Mentoring/2021-01-15-Call with Philip Langer Damiano Alfonso and Juri.md
+++ b/pages/Meetings/Mentoring/2021-01-15-Call with Philip Langer Damiano Alfonso and Juri.md
@@ -2,24 +2,24 @@
---
-# **Call with Philip Langer Damiano Alfonso and Juri**
-Date: 2021-01-15
-Time: 16:28
-Attendend: #attendance/online
-Project: #mdegroup
-People attended: #people/alfonso #people/juri #people/damiano #externalpeople/phliplanger
-
----
-## Damiano presented some capabilities of the tool he is developing
-**Some notes below**
-
-** [Sprotty](https://github.com/eclipse/sprotty) is just to link metaclasses with SVG **
-So this means that if you want restrict the behaviour of the editor, you need to develop this. Sprotty does not have first class elements for doing this.
-
-** Co-evolution capabilities of the tool**
-Currently basic cases are supported to automatically evolve models according to operated metamodel changes.
-
-** Styling elements and add constraints to graphical elements **
+- # **Call with Philip Langer Damiano Alfonso and Juri**
+ Date: 2021-01-15
+ Time: 16:28
+ Attendend: #attendance/online
+ Project: #mdegroup
+ People attended: #people/AlfonsoPierantonio #people/juri #people/damiano #externalpeople/phliplanger
+
+ ---
+- ## Damiano presented some capabilities of the tool he is developing
+ **Some notes below**
+
+ ** [Sprotty](https://github.com/eclipse/sprotty) is just to link metaclasses with SVG **
+ So this means that if you want restrict the behaviour of the editor, you need to develop this. Sprotty does not have first class elements for doing this.
+
+ ** Co-evolution capabilities of the tool**
+ Currently basic cases are supported to automatically evolve models according to operated metamodel changes.
+
+ ** Styling elements and add constraints to graphical elements **
- There is a bidirectional relationship between the graphical position of the element and model attributes.
- It is possible to define rules involving different graphical elements.
![[Pasted image 20210115164633.png]]
diff --git a/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso.md b/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso.md
index 6e226757..6fcc3668 100644
--- a/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso.md
+++ b/pages/Meetings/Mentoring/2021-01-22-1046-Meeting-Apurv-Alfonso.md
@@ -1,7 +1,7 @@
type:: #meeting
date:: [[22-01-2021]]
time:: 10:46
-people:: #people/alfonso #people/apurv
+people:: #people/AlfonsoPierantonio #people/apurv
- Presentation of the SOSYM paper about about BPMN vs Low-code
- Problem with section 5.4 concerning the usability
diff --git a/pages/Meetings/PhDICT/2021-01-18-0936-GiuliaDeMasi.md b/pages/Meetings/PhDICT/2021-01-18-0936-GiuliaDeMasi.md
index 53411a44..f828440b 100644
--- a/pages/Meetings/PhDICT/2021-01-18-0936-GiuliaDeMasi.md
+++ b/pages/Meetings/PhDICT/2021-01-18-0936-GiuliaDeMasi.md
@@ -8,7 +8,7 @@ type:: [[meeting]]
**Time**: 09:37
**Attendend**: #attendance/online
**Project**:
- **People attended**: #people/Vittorio_Cortellessa #people/henry #externalpeople/giuliademasi
+ **People attended**: #people/Vittorio_Cortellessa #people/HenryMuccini #externalpeople/giuliademasi
_Celano: 🌫 -3°C_
---
diff --git a/pages/Missione FSE 2025.md b/pages/Missione FSE 2025.md
index 43b99d07..94cf35bc 100644
--- a/pages/Missione FSE 2025.md
+++ b/pages/Missione FSE 2025.md
@@ -11,11 +11,9 @@ external-link:: [Program - FSE 2025](https://conf.researchr.org/program/fse-2025
- ### Notes
id:: 68584ea8-f9f8-49c5-a552-12194c301df5
- #### Slides preparation
- collapsed:: true
- "Teamwork makes the dream work: LLMs-Based Agents for GitHub README.MD Summarization", has been accepted for presentation in the Ideas, Visions, and Reflections track at FSE 2025
- Instructions to upload / send the slides ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgNERPBAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
- #### Day 1
- collapsed:: true
- **FSE Keynote: Mark Harman, Peter O’Hearn, and Shubho Sengupta****[Harden and Catch for Just-in-Time Assured LLM-Based Software Testing: An Industrial Perspective and Open Research Challenge](https://conf.researchr.org/program/fse-2025/program-fse-2025/?date=Mon%2023%20Jun%202025%2BTue%2024%20Jun%202025%2BWed%2025%20Jun%202025%2BThu%2026%20Jun%202025%2BFri%2027%20Jun%202025&past=Show%20upcoming%20events%20only#)**
collapsed:: true
- Abstract:
@@ -41,7 +39,6 @@ external-link:: [Program - FSE 2025](https://conf.researchr.org/program/fse-2025
- Grounds for optimism today! (oracle problem)
-
- #### Day 2
- collapsed:: true
- **[Risk Assessment Framework for Code LLMs via Leveraging Internal States](https://conf.researchr.org/program/fse-2025/program-fse-2025/?date=Mon%2023%20Jun%202025%2BTue%2024%20Jun%202025%2BWed%2025%20Jun%202025%2BThu%2026%20Jun%202025%2BFri%2027%20Jun%202025&past=Show%20upcoming%20events%20only#)**
collapsed:: true
- Industry Papers
@@ -58,13 +55,11 @@ external-link:: [Program - FSE 2025](https://conf.researchr.org/program/fse-2025
- 
-
- **[Hallucination Detection in Large Language Models with Metamorphic Relations](https://conf.researchr.org/program/fse-2025/program-fse-2025/?date=Mon%2023%20Jun%202025%2BTue%2024%20Jun%202025%2BWed%2025%20Jun%202025%2BThu%2026%20Jun%202025%2BFri%2027%20Jun%202025&past=Show%20upcoming%20events%20only#)**
- collapsed:: true
- Research Papers
- [Borui Yang](https://conf.researchr.org/profile/fse-2025/boruiyang) Beijing University of Posts ad Telecommunications, [Md Afif Al Mamun](https://conf.researchr.org/profile/fse-2025/mdafifalmamun) University of Calgary, [Jie M. Zhang](https://conf.researchr.org/profile/fse-2025/jiemzhang) King's College London, [Gias Uddin](https://conf.researchr.org/profile/fse-2025/giasuddin2) York University, Canada
- [DOI](https://doi.org/10.1145/3715735)
-
- **[Migrating Code At Scale With LLMs At Google](https://conf.researchr.org/program/fse-2025/program-fse-2025/?date=Mon%2023%20Jun%202025%2BTue%2024%20Jun%202025%2BWed%2025%20Jun%202025%2BThu%2026%20Jun%202025%2BFri%2027%20Jun%202025&past=Show%20upcoming%20events%20only#)**
- collapsed:: true
- Industry Papers
- [Celal Ziftci](https://conf.researchr.org/profile/fse-2025/celalziftci1) Google, [Stoyan Nikolov](https://conf.researchr.org/profile/fse-2025/stoyannikolov) Google, Inc., [Anna Sjovall](https://conf.researchr.org/profile/fse-2025/annasjovall) Google, Inc., [Bo Kim](https://conf.researchr.org/profile/fse-2025/bokim) Google, [Daniele Codecasa](https://conf.researchr.org/profile/fse-2025/danielecodecasa) Google, Inc., [Max Kim](https://conf.researchr.org/profile/fse-2025/maxkim) Google
- TODO Da vedere questo paper [[@Migrating Code At Scale With LLMs At Google]]
diff --git a/pages/Missione ROMA Mosaico.md b/pages/Missione ROMA Mosaico.md
index b6ba51bf..459e11d8 100644
--- a/pages/Missione ROMA Mosaico.md
+++ b/pages/Missione ROMA Mosaico.md
@@ -3,7 +3,6 @@ date:: [[01-07-2025]] - 09:25
progress:: {{renderer :todomaster}}
- ### Tasks
- collapsed:: true
- {{query (and [[TODO]] [[Missione ROMA Mosaico]] )}}
query-sort-by:: block
query-table:: true
@@ -12,10 +11,11 @@ progress:: {{renderer :todomaster}}
- ### Notes
- Agenda: 
- Participants: 
- -
+ - 
- **First day of meeting [[01-07-2025]]**
query-table:: true
query-properties:: [:block]
+ collapsed:: true
- ### Overview
collapsed:: true
- 
@@ -43,17 +43,30 @@ progress:: {{renderer :todomaster}}
- Opentelemetry is a communication protocol and LangFuse supports this protocol.
- 
- 
- - TODO [[p1]] Da guardare A2A agent card per la tassonomia relativa al repository
+ - DONE [[p1]] Da guardare A2A agent card per la tassonomia relativa al repository
+ id:: 6863a4ff-c366-4708-8009-34f6b34fedbb
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 18:04:55]--[2025-08-19 Tue 18:04:55] => 00:00:00
+ :END:
- 
- 
- 
- - TODO [[p2]] The agent discovery mechanism is very much related to that of MOSAICO. Have a look at them especially to see what is the taxonomy underpinning them
+ - DONE [[p2]] The agent discovery mechanism is very much related to that of MOSAICO. Have a look at them especially to see what is the taxonomy underpinning them
+ id:: 6863a692-e9b0-4b8f-ba41-a9d4a1043651
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 18:05:59]--[2025-08-19 Tue 18:06:00] => 00:00:01
+ :END:
- 
- 
- 
- - TODO This is an idea related to the WP2 taxonomy
+ - DONE This is an idea related to the WP2 taxonomy
+ id:: 6863a8b5-35d5-492e-a8cf-2549750d9965
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 18:08:44]--[2025-08-19 Tue 18:08:47] => 00:00:03
+ :END:
- 
- ### WP2 Presentation
+ collapsed:: true
- 
- TODO Developer Interface is not the right naming. THis needs to be changed
- 
@@ -65,11 +78,14 @@ progress:: {{renderer :todomaster}}
- TODO Do they support agents in different technologies?
- TODO What about parallel executions?
- TODO Improve the relation vs existing model repositories
- - TODO [[p1]] Have a look at the different repositories shared by Antonio
+ - DONE [[p1]] Have a look at the different repositories shared by Antonio [[Resources]]
+ id:: 6863b98d-74e6-435a-8631-c03155c89300
- https://beeai.dev/agents
- https://www.agentlocker.ai/
- https://aiagentslist.com/
- [Taxonomy of AI Agent Skills - Agntcy](https://docs.agntcy.org/oasf/taxonomy/)
+ -
+ -
- TODO Look at Traces and Metrics (OpenTelemetry with Spring)
- Our application should be ready to gather telemetry
- It is related to LangFuse
@@ -127,6 +143,7 @@ progress:: {{renderer :todomaster}}
- 
- 
- **Second day of the meeting [[02-07-2025]]**
+ collapsed:: true
- ### WP10 Presentation
collapsed:: true
- [Florence Bonnet | CEPR](https://cepr.org/about/people/florence-bonnet)
@@ -179,7 +196,8 @@ progress:: {{renderer :todomaster}}
- We removed X from our socialmedia. We should decide what to do. It makes sense to increase the Linkedin KPI
- So far no visits to schools or alike
- {:height 582, :width 980}
- - TODO [[p1]] Aggiungere presentazione MOSAICO a FSE
+ - DONE [[p1]] Aggiungere presentazione MOSAICO a FSE
+ id:: 6864fa38-39bb-42b6-94f5-ba9bccfc4f04
- 
- 
- Concerning T6.1 and T6.3 (from Eclipse)
@@ -206,9 +224,11 @@ progress:: {{renderer :todomaster}}
- 
- 
- 
- - TODO We have now a latex template for deliverables. It's in our Sharepoint. DOwnload it!
+ - DONE We have now a latex template for deliverables. It's in our Sharepoint. DOwnload it!
+ id:: 686503c5-75e8-45ab-9237-aa9eb32c63cc
-
- ### WP5 Presentation
+ collapsed:: true
- 
- 
- 
@@ -220,15 +240,22 @@ progress:: {{renderer :todomaster}}
- 
-
- ### WP8 and WP9
+ collapsed:: true
- Talked about deliverable 8.2
- 
- 
- ### Discussion
- - TODO [[p2]] Look at [MOSAICO Architecture - Google Drawings](https://docs.google.com/drawings/d/1zyO2GLFj8PtQD9j6MZ1AksQwwLM_XmZX8AOPGNs8m_Y/edit)
+ collapsed:: true
+ - DONE [[p2]] Look at [MOSAICO Architecture - Google Drawings](https://docs.google.com/drawings/d/1zyO2GLFj8PtQD9j6MZ1AksQwwLM_XmZX8AOPGNs8m_Y/edit) [[Resources]]
+ id:: 68653364-55e9-4d49-85e1-0c8a9f186e8e
+ :LOGBOOK:
+ CLOCK: [2025-08-19 Tue 18:03:00]--[2025-08-19 Tue 18:03:01] => 00:00:01
+ :END:
- **Third day of the meeting [[03-07-2025]]**
- Agenda: [MOSAICO 2nd Co-Creation meeting Rome_proposed agenda_20250619.docx](https://imtatlantiquefr.sharepoint.com/:w:/r/sites/MOSAICO/_layouts/15/Doc.aspx?sourcedoc=%7BBC69EB4B-582A-4E6B-A86A-13D04EF8FA93%7D&file=MOSAICO%202nd%20Co-Creation%20meeting%20Rome_proposed%20agenda_20250619.docx&action=default&mobileredirect=true)
- Link: https://gov.teams.microsoft.us/l/meetup-join/19%3agcch%3ameeting_cb5648e689bb4db19ab298cdfad07f3f%40thread.v2/0?context=%7b%22Tid%22%3a%227a18110d-ef9b-4274-acef-e62ab0fe28ed%22%2c%22Oid%22%3a%2272d155af-f561-43e3-88f0-0ae9416888e8%22%7d
- ### Critical and important aspects
+ collapsed:: true
- {{query (and (or [[critical]] [[IMPORTANT]]) [[Missione ROMA Mosaico]])}}
query-table:: true
query-properties:: [:block]
diff --git a/pages/Missione STAF 2025.md b/pages/Missione STAF 2025.md
index f2a04f18..f2b4c2d3 100644
--- a/pages/Missione STAF 2025.md
+++ b/pages/Missione STAF 2025.md
@@ -61,7 +61,7 @@ progress:: {{renderer :todomaster}}
- 
-
- 
- - This is related to [[Model Context Protocol (MCP)]] #LLMs #PROJECTS/MOSAICO #reading
+ - This is related to [[Model Context Protocol (MCP)]] #LLMs #PROJECTS/MOSAICO #Reading
- 
- 
- 
diff --git a/pages/Model Context Protocol (MCP).md b/pages/Model Context Protocol (MCP).md
index a37f1828..0557aafc 100644
--- a/pages/Model Context Protocol (MCP).md
+++ b/pages/Model Context Protocol (MCP).md
@@ -1,4 +1,4 @@
-tags:: #LLMs #PROJECTS/MOSAICO #reading
+tags:: #LLMs #PROJECTS/MOSAICO #Reading
- MCP has quickly become a cornerstone in enabling AI models—particularly large language models (LLMs) and autonomous agents—to interact with external tools, APIs, and data sources through a standardized interface. Much like USB-C revolutionized device connectivity, MCP aims to standardize how models access and apply contextual information.
- While MCP initially focused on simplifying integrations, its broader impact is now coming into view. We're beginning to see MCP evolve into a foundational layer for distributed AI systems. These systems involve not just a single model with a static toolbox, but networks of interoperating agents, dynamically discovering, invoking, and coordinating with external resources.
diff --git a/pages/Omnivore.md b/pages/Omnivore.md
index 78d632d5..6a016d79 100644
--- a/pages/Omnivore.md
+++ b/pages/Omnivore.md
@@ -5,6 +5,7 @@ icon:: ⤴️
query-sort-by:: block
query-table:: true
query-sort-desc:: false
+ collapsed:: true
#+BEGIN_QUERY
{:title "STARRED ITEMS"
:query
diff --git a/pages/Omnivore___01-05-2024___Dottorati di ricerca — Italiano.md b/pages/Omnivore___01-05-2024___Dottorati di ricerca — Italiano.md
index 9bc3d9f2..330bc48a 100644
--- a/pages/Omnivore___01-05-2024___Dottorati di ricerca — Italiano.md
+++ b/pages/Omnivore___01-05-2024___Dottorati di ricerca — Italiano.md
@@ -4,4 +4,4 @@ author:: pubblicato il 30/04/2024 — ultima modifica 30/04/2024
labels:: [[SERVICES/PHDICT]]
date-saved:: [[01-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___02-04-2024___Edge 383- The Key Capabilities of Autonomous Agens.md b/pages/Omnivore___02-04-2024___Edge 383- The Key Capabilities of Autonomous Agens.md
index 735c754d..6839f3bc 100644
--- a/pages/Omnivore___02-04-2024___Edge 383- The Key Capabilities of Autonomous Agens.md
+++ b/pages/Omnivore___02-04-2024___Edge 383- The Key Capabilities of Autonomous Agens.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[02-04-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___02-05-2024___Edge 392- Meet RAFT- UC Berkeley's New Method to Improve RAG Patterns in LLMs.md b/pages/Omnivore___02-05-2024___Edge 392- Meet RAFT- UC Berkeley's New Method to Improve RAG Patterns in LLMs.md
index ed2c099c..867353d4 100644
--- a/pages/Omnivore___02-05-2024___Edge 392- Meet RAFT- UC Berkeley's New Method to Improve RAG Patterns in LLMs.md
+++ b/pages/Omnivore___02-05-2024___Edge 392- Meet RAFT- UC Berkeley's New Method to Improve RAG Patterns in LLMs.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]] [[RAG]]
date-saved:: [[02-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___02-05-2024___MAIA.md b/pages/Omnivore___02-05-2024___MAIA.md
index a5dc2c9d..e96148db 100644
--- a/pages/Omnivore___02-05-2024___MAIA.md
+++ b/pages/Omnivore___02-05-2024___MAIA.md
@@ -3,4 +3,4 @@ site:: [multimodal-interpretability.csail.mit.edu](https://multimodal-interpreta
author:: Tamar Rott Shaham*,
date-saved:: [[02-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___02-05-2024___Phi-3 Technical Report- A Highly Capable Language Model Locally on Your Phone.md b/pages/Omnivore___02-05-2024___Phi-3 Technical Report- A Highly Capable Language Model Locally on Your Phone.md
index 21340f17..9e9d3378 100644
--- a/pages/Omnivore___02-05-2024___Phi-3 Technical Report- A Highly Capable Language Model Locally on Your Phone.md
+++ b/pages/Omnivore___02-05-2024___Phi-3 Technical Report- A Highly Capable Language Model Locally on Your Phone.md
@@ -3,4 +3,4 @@ site:: [arxiv.org](https://arxiv.org/html/2404.14219v1)
author:: Microsoft
date-saved:: [[02-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___02-05-2024___[2403.10131] RAFT- Adapting Language Model to Domain Specific RAG.md b/pages/Omnivore___02-05-2024___[2403.10131] RAFT- Adapting Language Model to Domain Specific RAG.md
index 0dca7bd7..80255682 100644
--- a/pages/Omnivore___02-05-2024___[2403.10131] RAFT- Adapting Language Model to Domain Specific RAG.md
+++ b/pages/Omnivore___02-05-2024___[2403.10131] RAFT- Adapting Language Model to Domain Specific RAG.md
@@ -3,4 +3,4 @@ site:: [arXiv.org](https://arxiv.org/abs/2403.10131)
author:: [Submitted on 15 Mar 2024]
date-saved:: [[02-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___03-01-2024___ChatGPT in software modeling - Software and Systems Modeling.md b/pages/Omnivore___03-01-2024___ChatGPT in software modeling - Software and Systems Modeling.md
index fe60c6cb..caf69303 100644
--- a/pages/Omnivore___03-01-2024___ChatGPT in software modeling - Software and Systems Modeling.md
+++ b/pages/Omnivore___03-01-2024___ChatGPT in software modeling - Software and Systems Modeling.md
@@ -5,4 +5,4 @@ labels:: [[MDE]] [[ResearchPaper]] [[AI]]
date-saved:: [[03-01-2024]]
date-published:: [[01-06-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___03-01-2024___Leveraging Artificial Intelligence for Model-based Software Analysis and Desi...___.md b/pages/Omnivore___03-01-2024___Leveraging Artificial Intelligence for Model-based Software Analysis and Desi...___.md
index fc8d14fd..c0623a80 100644
--- a/pages/Omnivore___03-01-2024___Leveraging Artificial Intelligence for Model-based Software Analysis and Desi...___.md
+++ b/pages/Omnivore___03-01-2024___Leveraging Artificial Intelligence for Model-based Software Analysis and Desi...___.md
@@ -5,4 +5,4 @@ labels:: [[MDE]] [[ResearchPaper]] [[AI]]
date-saved:: [[03-01-2024]]
date-published:: [[01-01-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___04-04-2024___The Todoist Bulletin.md b/pages/Omnivore___04-04-2024___The Todoist Bulletin.md
index 6741c641..bbd1c893 100644
--- a/pages/Omnivore___04-04-2024___The Todoist Bulletin.md
+++ b/pages/Omnivore___04-04-2024___The Todoist Bulletin.md
@@ -2,4 +2,4 @@ full-title:: [The Todoist Bulletin](https://omnivore.app/me/the-todoist-bulletin
site:: [todoist.news](https://todoist.news/2024%5F04)
date-saved:: [[04-04-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___04-06-2024___Edge 401- Reflection and Refinement Planning Methods in Autonomous Agents.md b/pages/Omnivore___04-06-2024___Edge 401- Reflection and Refinement Planning Methods in Autonomous Agents.md
index e937a1dd..1c0cf58c 100644
--- a/pages/Omnivore___04-06-2024___Edge 401- Reflection and Refinement Planning Methods in Autonomous Agents.md
+++ b/pages/Omnivore___04-06-2024___Edge 401- Reflection and Refinement Planning Methods in Autonomous Agents.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[04-06-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___05-04-2024___RAG, portare l'intelligenza artificiale in azienda e migliorare il business c...___.md b/pages/Omnivore___05-04-2024___RAG, portare l'intelligenza artificiale in azienda e migliorare il business c...___.md
index a822abd6..3c0917a3 100644
--- a/pages/Omnivore___05-04-2024___RAG, portare l'intelligenza artificiale in azienda e migliorare il business c...___.md
+++ b/pages/Omnivore___05-04-2024___RAG, portare l'intelligenza artificiale in azienda e migliorare il business c...___.md
@@ -4,4 +4,4 @@ author:: Michele Nasi Pubblicato il 4 apr 2024
labels:: [[RAG]]
date-saved:: [[05-04-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___06-02-2024___Cahiers de doléances - Wikipedia.md b/pages/Omnivore___06-02-2024___Cahiers de doléances - Wikipedia.md
index cc81c0d6..87fb89a7 100644
--- a/pages/Omnivore___06-02-2024___Cahiers de doléances - Wikipedia.md
+++ b/pages/Omnivore___06-02-2024___Cahiers de doléances - Wikipedia.md
@@ -4,4 +4,4 @@ author:: Contributori ai progetti Wikimedia
date-saved:: [[06-02-2024]]
date-published:: [[08-03-2006]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___06-05-2024___Editorial- ICSE and the Incredible Contradictions of Software Engineering - A...___.md b/pages/Omnivore___06-05-2024___Editorial- ICSE and the Incredible Contradictions of Software Engineering - A...___.md
index 3e18969e..61f9a983 100644
--- a/pages/Omnivore___06-05-2024___Editorial- ICSE and the Incredible Contradictions of Software Engineering - A...___.md
+++ b/pages/Omnivore___06-05-2024___Editorial- ICSE and the Incredible Contradictions of Software Engineering - A...___.md
@@ -5,7 +5,7 @@ labels:: [[MauroPezze]] [[P1]]
date-saved:: [[06-05-2024]]
date-published:: [[18-04-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___08-09-2023___Ddl affitti brevi — idealista-news.md b/pages/Omnivore___08-09-2023___Ddl affitti brevi — idealista-news.md
index 0ad09d86..eee82fc5 100644
--- a/pages/Omnivore___08-09-2023___Ddl affitti brevi — idealista-news.md
+++ b/pages/Omnivore___08-09-2023___Ddl affitti brevi — idealista-news.md
@@ -5,9 +5,10 @@ labels:: [[affitti]]
date-saved:: [[08-09-2023]]
date-published:: [[07-09-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > **affitti brevi con il nuovo ddl diffuso dal Ministero del Turismo** si abbatterà soprattutto sul piccolo proprietario [⤴️](https://omnivore.app/me/ddl-affitti-brevi-idealista-news-18a74e0b011#7c279898-00b6-4bf2-af16-75a400c87506)
- > si conferma l’obbligo di essere registrati ad un apposito registro nazionale e di essere soggetti a controlli da parte dei Comuni. [⤴️](https://omnivore.app/me/ddl-affitti-brevi-idealista-news-18a74e0b011#6acee3d7-09da-4c2c-9f76-46767c1a4d3f)
diff --git a/pages/Omnivore___10-02-2024___Nutrizionista Roma - Nutrizionista Daniele Sciotti.md b/pages/Omnivore___10-02-2024___Nutrizionista Roma - Nutrizionista Daniele Sciotti.md
index 16578136..c83b1887 100644
--- a/pages/Omnivore___10-02-2024___Nutrizionista Roma - Nutrizionista Daniele Sciotti.md
+++ b/pages/Omnivore___10-02-2024___Nutrizionista Roma - Nutrizionista Daniele Sciotti.md
@@ -2,4 +2,4 @@ full-title:: [Nutrizionista Roma | Nutrizionista Daniele Sciotti](https://omnivo
site:: [Daniele Sciotti](https://www.nutrizionistadanielesciotti.it)
date-saved:: [[10-02-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___10-06-2024___ModelXGlue- a benchmarking framework for ML tools in MDE - Software and Syste...___.md b/pages/Omnivore___10-06-2024___ModelXGlue- a benchmarking framework for ML tools in MDE - Software and Syste...___.md
index 963ca253..ef302b3e 100644
--- a/pages/Omnivore___10-06-2024___ModelXGlue- a benchmarking framework for ML tools in MDE - Software and Syste...___.md
+++ b/pages/Omnivore___10-06-2024___ModelXGlue- a benchmarking framework for ML tools in MDE - Software and Syste...___.md
@@ -4,4 +4,4 @@ author:: Di Ruscio, Davide
date-saved:: [[10-06-2024]]
date-published:: [[10-06-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___11-01-2024___Meet Ghostbuster- An AI Technique for Detecting LLM-Generated Content.md b/pages/Omnivore___11-01-2024___Meet Ghostbuster- An AI Technique for Detecting LLM-Generated Content.md
index eecb48ae..bf6b52ed 100644
--- a/pages/Omnivore___11-01-2024___Meet Ghostbuster- An AI Technique for Detecting LLM-Generated Content.md
+++ b/pages/Omnivore___11-01-2024___Meet Ghostbuster- An AI Technique for Detecting LLM-Generated Content.md
@@ -1,12 +1,10 @@
--
-full-title:: [Meet Ghostbuster: An AI Technique for Detecting LLM-Generated Content](https://omnivore.app/me/meet-ghostbuster-an-ai-technique-for-detecting-llm-generated-con-18cf870b527)
-site:: [thesequence.substack.com](https://thesequence.substack.com/p/meet-ghostbuster-an-ai-technique?isFreemail=true&post_id=140578123&publication_id=54309&r=z2w67&token=eyJ1c2VyX2lkIjo1ODkyMTU2NywicG9zdF9pZCI6MTQwNTc4MTIzLCJpYXQiOjE3MDQ5NzUwOTcsImV4cCI6MTcwNzU2NzA5NywiaXNzIjoicHViLTU0MzA5Iiwic3ViIjoicG9zdC1yZWFjdGlvbiJ9.xmHZDax66HJi0V8onrVLKtwnQAUQuOQUyVyDiFn0Vrs)
-author:: davide.diruscio@gmail.com
-labels:: [[Newsletter]] [[LLMs]] [[P1]]
-date-saved:: [[11-01-2024]]
-source:: [[Omnivore]]
-state:: [[reading]]
-
+- full-title:: [Meet Ghostbuster: An AI Technique for Detecting LLM-Generated Content](https://omnivore.app/me/meet-ghostbuster-an-ai-technique-for-detecting-llm-generated-con-18cf870b527)
+ site:: [thesequence.substack.com](https://thesequence.substack.com/p/meet-ghostbuster-an-ai-technique?isFreemail=true&post_id=140578123&publication_id=54309&r=z2w67&token=eyJ1c2VyX2lkIjo1ODkyMTU2NywicG9zdF9pZCI6MTQwNTc4MTIzLCJpYXQiOjE3MDQ5NzUwOTcsImV4cCI6MTcwNzU2NzA5NywiaXNzIjoicHViLTU0MzA5Iiwic3ViIjoicG9zdC1yZWFjdGlvbiJ9.xmHZDax66HJi0V8onrVLKtwnQAUQuOQUyVyDiFn0Vrs)
+ author:: davide.diruscio@gmail.com
+ labels:: [[Newsletter]] [[LLMs]] [[P1]]
+ date-saved:: [[11-01-2024]]
+ source:: [[Omnivore]]
+ state:: [[Reading]]
- ### Highlights
- > The rapid evolution of large language models(LLMs) has created new challenges in terms of differentiating between human and AI-generated content. [⤴️](https://omnivore.app/me/meet-ghostbuster-an-ai-technique-for-detecting-llm-generated-con-18cf870b527#1db2b88d-fc61-48dd-bb45-35592804ad8f)
diff --git a/pages/Omnivore___11-01-2024___OpenAI lancia lo store di ChatGPT - Il Sole 24 ORE.md b/pages/Omnivore___11-01-2024___OpenAI lancia lo store di ChatGPT - Il Sole 24 ORE.md
index 941a540a..7f901379 100644
--- a/pages/Omnivore___11-01-2024___OpenAI lancia lo store di ChatGPT - Il Sole 24 ORE.md
+++ b/pages/Omnivore___11-01-2024___OpenAI lancia lo store di ChatGPT - Il Sole 24 ORE.md
@@ -1,15 +1,13 @@
--
-full-title:: [OpenAI lancia lo store di ChatGPT - Il Sole 24 ORE](https://omnivore.app/me/https-www-ilsole-24-ore-com-art-openai-lancia-store-chatgpt-a-fj-18cf7f7b953)
-site:: [Il Sole 24 ORE](https://www.ilsole24ore.com/art/openai-lancia-store-chatgpt-AFjzgwIC)
-author:: Il Sole 24 Ore
-labels:: [[PROJECTS/SE-H2020-March-Call]] [[LLMs]]
-date-saved:: [[11-01-2024]]
-date-published:: [[10-01-2024]]
-date-archived:: [[11-01-2024]]
-is-archived:: 10
-source:: [[Omnivore]]
-state:: [[archived]]
-
+- full-title:: [OpenAI lancia lo store di ChatGPT - Il Sole 24 ORE](https://omnivore.app/me/https-www-ilsole-24-ore-com-art-openai-lancia-store-chatgpt-a-fj-18cf7f7b953)
+ site:: [Il Sole 24 ORE](https://www.ilsole24ore.com/art/openai-lancia-store-chatgpt-AFjzgwIC)
+ author:: Il Sole 24 Ore
+ labels:: [[PROJECTS/MOSAICO]] [[LLMs]]
+ date-saved:: [[11-01-2024]]
+ date-published:: [[10-01-2024]]
+ date-archived:: [[11-01-2024]]
+ is-archived:: 10
+ source:: [[Omnivore]]
+ state:: [[archived]]
- ### Highlights
- > OpenAI ha finalmente lanciato lo store dove gli utenti possono condividere (e vendere/acquistare) versioni personalizzate del popolare chatbot ChatGPT. [⤴️](https://omnivore.app/me/https-www-ilsole-24-ore-com-art-openai-lancia-store-chatgpt-a-fj-18cf7f7b953#e9bb6bd8-9360-4a1e-b9d5-87b80e7d46ba)
- > GPT Store permetterà agli utenti di vedere i chatbot più popolari e di tendenza in una classifica e di cercarli per categoria. [⤴️](https://omnivore.app/me/https-www-ilsole-24-ore-com-art-openai-lancia-store-chatgpt-a-fj-18cf7f7b953#7d79c5a2-5074-4379-b376-d285e3a648b3)
diff --git a/pages/Omnivore___12-08-2023___The Secret Power of ‘Read It Later’ Apps.md b/pages/Omnivore___12-08-2023___The Secret Power of ‘Read It Later’ Apps.md
index 8cb397e1..b8985346 100644
--- a/pages/Omnivore___12-08-2023___The Secret Power of ‘Read It Later’ Apps.md
+++ b/pages/Omnivore___12-08-2023___The Secret Power of ‘Read It Later’ Apps.md
@@ -9,7 +9,8 @@ is-archived:: 10
source:: [[Omnivore]]
state:: [[archived]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > Pocket over the course of the year. [⤴️](https://omnivore.app/me/the-secret-power-of-read-it-later-apps-189eb9ce888#80cf319f-6a4e-4f98-acbe-91aa5b56f5a9)
omnivore-note:: This is a test note.
@@ -35,4 +36,4 @@ state:: [[archived]]
- > Ideas are high leverage agents. They become more so when arranged in highly cross-referenced networks. [⤴️](https://omnivore.app/me/the-secret-power-of-read-it-later-apps-189eb9ce888#c4cb4fb5-b404-4537-9399-0a0d4822f149)
omnivore-note:: [[ideas]]
- > Reading is the closest thing we have to thinking another’s thoughts. It’s long and sometimes ponderous, but that work is required to wrap yourself in another person’s paradigm. Which is the first step in madly letting go of your own. [⤴️](https://omnivore.app/me/the-secret-power-of-read-it-later-apps-189eb9ce888#5879ed6c-6777-412b-ad61-9eb015fdb108)
- omnivore-note:: #reading
\ No newline at end of file
+ omnivore-note:: #Reading
\ No newline at end of file
diff --git a/pages/Omnivore___12-09-2023___Obsidian- Stop Wasting Time With Directories and Filenames - by Brian Carey -...___.md b/pages/Omnivore___12-09-2023___Obsidian- Stop Wasting Time With Directories and Filenames - by Brian Carey -...___.md
index f084c16f..d08c5d96 100644
--- a/pages/Omnivore___12-09-2023___Obsidian- Stop Wasting Time With Directories and Filenames - by Brian Carey -...___.md
+++ b/pages/Omnivore___12-09-2023___Obsidian- Stop Wasting Time With Directories and Filenames - by Brian Carey -...___.md
@@ -4,9 +4,10 @@ author:: Brian Carey
date-saved:: [[12-09-2023]]
date-published:: [[29-08-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > we use Obsidian for information management, not file management. [⤴️](https://omnivore.app/me/obsidian-stop-wasting-time-with-directories-and-filenames-by-bri-18a87f2d720#863d2bbb-2a01-42a6-b465-aeab9fc0e4d2)
- > The Bookmarks panel provides an information tree, the Navigator panel provides a file tree. I want the information tree. [⤴️](https://omnivore.app/me/obsidian-stop-wasting-time-with-directories-and-filenames-by-bri-18a87f2d720#f820512c-1994-4ec6-b090-a90c66c25c47)
\ No newline at end of file
diff --git a/pages/Omnivore___12-09-2024___Edge 430- Learn About The AI Scientist, The Model that can Conduct Long Term ...___.md b/pages/Omnivore___12-09-2024___Edge 430- Learn About The AI Scientist, The Model that can Conduct Long Term ...___.md
index bea27ad9..1894bcad 100644
--- a/pages/Omnivore___12-09-2024___Edge 430- Learn About The AI Scientist, The Model that can Conduct Long Term ...___.md
+++ b/pages/Omnivore___12-09-2024___Edge 430- Learn About The AI Scientist, The Model that can Conduct Long Term ...___.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[12-09-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___13-01-2024___David Lo - nuovi articoli.md b/pages/Omnivore___13-01-2024___David Lo - nuovi articoli.md
index efa408f9..1651c9be 100644
--- a/pages/Omnivore___13-01-2024___David Lo - nuovi articoli.md
+++ b/pages/Omnivore___13-01-2024___David Lo - nuovi articoli.md
@@ -3,4 +3,4 @@ site:: [omnivore.app](https://omnivore.app/no_url?q=eef4537b-6dda-4960-a544-943f
labels:: [[Newsletter]]
date-saved:: [[13-01-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___13-08-2023___Rivoluzione dell'Ingegneria del Software- L'Impatto dell'Intelligenza Artific...___.md b/pages/Omnivore___13-08-2023___Rivoluzione dell'Ingegneria del Software- L'Impatto dell'Intelligenza Artific...___.md
index fa8e30c9..ddf1dae1 100644
--- a/pages/Omnivore___13-08-2023___Rivoluzione dell'Ingegneria del Software- L'Impatto dell'Intelligenza Artific...___.md
+++ b/pages/Omnivore___13-08-2023___Rivoluzione dell'Ingegneria del Software- L'Impatto dell'Intelligenza Artific...___.md
@@ -5,9 +5,10 @@ labels:: [[AI]] [[SoftwareEngineering]]
date-saved:: [[13-08-2023]]
date-published:: [[12-08-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > L’integrazione dell’IA nell’ingegneria del software è una svolta epocale, principalmente perché automatizza molti aspetti del processo di sviluppo del software. [⤴️](https://omnivore.app/me/https-ts-2-space-it-rivoluzione-dellingegneria-del-software-limp-189ed6d03b3#8e7397ff-d6de-41ba-a197-9407ff8458ca)
- > strumenti basati sull’IA possono generare automaticamente il codice in base ai requisiti specifici, riducendo la necessità di scrittura manuale del codice. [⤴️](https://omnivore.app/me/https-ts-2-space-it-rivoluzione-dellingegneria-del-software-limp-189ed6d03b3#231abe30-8f41-4d5f-878a-6d773f09491f)
diff --git a/pages/Omnivore___14-01-2024___A New Compute Platform for Generative AI -.md b/pages/Omnivore___14-01-2024___A New Compute Platform for Generative AI -.md
index 6d66d478..0f62df88 100644
--- a/pages/Omnivore___14-01-2024___A New Compute Platform for Generative AI -.md
+++ b/pages/Omnivore___14-01-2024___A New Compute Platform for Generative AI -.md
@@ -4,7 +4,8 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[14-01-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
+tags:: [[Benchmarks]] [[PROJECTS/MOSAICO]]
- ### Highlights
- > Large Action Model (LAM) paradigms. [⤴️](https://omnivore.app/me/a-new-compute-platform-for-generative-ai-18d07ea7958#5dad5316-11a3-45c7-963a-f7bc42c4f85f)
diff --git a/pages/Omnivore___14-05-2024___Edge 395- Task Decomposition in Autonomous Agents.md b/pages/Omnivore___14-05-2024___Edge 395- Task Decomposition in Autonomous Agents.md
index 1a761182..280ec129 100644
--- a/pages/Omnivore___14-05-2024___Edge 395- Task Decomposition in Autonomous Agents.md
+++ b/pages/Omnivore___14-05-2024___Edge 395- Task Decomposition in Autonomous Agents.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[14-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat.md b/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat.md
index 1b63802c..5caadbf0 100644
--- a/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat.md
+++ b/pages/Omnivore___14-08-2023___Generative AI- A new Gold Rush for software engineering innovation - VentureBeat.md
@@ -9,7 +9,8 @@ is-archived:: 10
source:: [[Omnivore]]
state:: [[archived]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > For all the benefits that generative AI promises, voices are getting louder about the unintended societal effects of this technology. [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#b52716a9-84fb-490b-9b55-b6c22ece3c8c)
- > It is the first time in the history of humanity that white-collar jobs stand to be automated, potentially rendering expensive degrees and years of experience meaningless. [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#5e926a10-acfb-4733-a962-6a82de3dbfbb)
@@ -21,8 +22,8 @@ state:: [[archived]]
omnivore-note:: #TODO
- > Microsoft CEO Satya Nadella famously asked about generative AI, “OpenAI built this with 250 people; why do we have Microsoft Research at all?” [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#e7d5743e-ea5a-4789-88b6-f59ddf9e1d0d)
- > Why would you stop at a ten-billion-parameter model when you can train a massive general-purpose model with 500 billion parameters that can answer questions about any topic from any industry? [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#21cb06ec-c2a4-4b0d-bc56-ce8639b449ba)
- - > There has been a realization recently that we might have hit the limit of productivity gains that can be achieved by the size of a model. [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#2c17576d-e8b9-477c-8557-933e82271565)
- omnivore-note:: #CARDS
+ - id:: 68584eb4-9919-41da-ab7f-d39dfb933470
+ > There has been a realization recently that we might have hit the limit of productivity gains that can be achieved by the size of a model. [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#2c17576d-e8b9-477c-8557-933e82271565)
- > Independent evaluations of models have proved that there is no silver bullet, but the best model for an enterprise will be use-case specific. [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#5c1588e0-b008-43d9-816e-f452bef888d5)
- > In the comprehensive evaluation completed by Stanford using models from openAI, Cohere, Anthropic and others, it was found that smaller models may perform better than their larger counterparts. [⤴️](https://omnivore.app/me/https-venturebeat-com-ai-generative-ai-a-new-gold-rush-for-softw-189f107a215#6c8fc1ef-4578-4396-835f-8144ebd8d569)
omnivore-note:: #STAR
diff --git a/pages/Omnivore___14-12-2023___(20) The Future of Software Engineering with AI Agents - LinkedIn.md b/pages/Omnivore___14-12-2023___(20) The Future of Software Engineering with AI Agents - LinkedIn.md
index 1267219e..7adc0a86 100644
--- a/pages/Omnivore___14-12-2023___(20) The Future of Software Engineering with AI Agents - LinkedIn.md
+++ b/pages/Omnivore___14-12-2023___(20) The Future of Software Engineering with AI Agents - LinkedIn.md
@@ -2,7 +2,7 @@
- full-title:: [(20) The Future of Software Engineering with AI Agents | LinkedIn](https://omnivore.app/me/20-the-future-of-software-engineering-with-ai-agents-linked-in-18c6784cdf7)
site:: [linkedin.com](https://www.linkedin.com/pulse/future-software-engineering-ai-agents-selim-salman/)
author:: Selim Salman
- labels:: [[PROJECTS/SE-H2020-March-Call]]
+ labels:: [[PROJECTS/MOSAICO]]
date-saved:: [[14-12-2023]]
date-published:: [[12-09-2023]]
date-archived:: [[10-01-2024]]
diff --git a/pages/Omnivore___15-04-2024___Why Entire AI field is headed towards AI Agents - by Aniket Hingane - Apr, 20...___.md b/pages/Omnivore___15-04-2024___Why Entire AI field is headed towards AI Agents - by Aniket Hingane - Apr, 20...___.md
index dad8d012..b5bb39b1 100644
--- a/pages/Omnivore___15-04-2024___Why Entire AI field is headed towards AI Agents - by Aniket Hingane - Apr, 20...___.md
+++ b/pages/Omnivore___15-04-2024___Why Entire AI field is headed towards AI Agents - by Aniket Hingane - Apr, 20...___.md
@@ -4,4 +4,4 @@ author:: Aniket Hingane
date-saved:: [[15-04-2024]]
date-published:: [[03-04-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___15-07-2024___Saper scrivere è così importante- - Il Sole 24 ORE.md b/pages/Omnivore___15-07-2024___Saper scrivere è così importante- - Il Sole 24 ORE.md
index 49892738..423dc1ac 100644
--- a/pages/Omnivore___15-07-2024___Saper scrivere è così importante- - Il Sole 24 ORE.md
+++ b/pages/Omnivore___15-07-2024___Saper scrivere è così importante- - Il Sole 24 ORE.md
@@ -4,4 +4,4 @@ author:: Il Sole 24 Ore
date-saved:: [[15-07-2024]]
date-published:: [[12-02-2017]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___15-11-2023___Introducing GPTs.md b/pages/Omnivore___15-11-2023___Introducing GPTs.md
index 619c7b9b..6150f1f2 100644
--- a/pages/Omnivore___15-11-2023___Introducing GPTs.md
+++ b/pages/Omnivore___15-11-2023___Introducing GPTs.md
@@ -2,14 +2,15 @@
- full-title:: [Introducing GPTs](https://omnivore.app/me/https-openai-com-blog-introducing-gpts-18bd1d809d8)
site:: [openai.com](https://openai.com/blog/introducing-gpts)
author:: Authors
- labels:: [[STAR]] [[PROJECTS/SE-H2020-March-Call]] [[LLMs]] [[gpts]]
+ labels:: [[STAR]] [[PROJECTS/MOSAICO]] [[LLMs]] [[gpts]]
date-saved:: [[15-11-2023]]
date-published:: [[06-11-2023]]
date-archived:: [[16-11-2023]]
is-archived:: 10
source:: [[Omnivore]]
state:: [[archived]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > Like plugins, actions allow GPTs to integrate external data or interact with the real-world. [⤴️](https://omnivore.app/me/https-openai-com-blog-introducing-gpts-18bd1d809d8#b648ce4c-cd25-45a5-8e0b-54aa314bf4ae)
- id:: 29be0b05-e52f-4d27-b1bd-5d7f64b25b54
@@ -25,7 +26,7 @@
omnivore-note:: #STAR #omnivore-note-color
> Whether you’re an educator, coach, or just someone who loves to build helpful tools, you don’t need to know coding to make one and share your expertise. [⤴️](https://omnivore.app/me/https-openai-com-blog-introducing-gpts-18bd1d809d8#62a47347-e99b-4924-b06b-3ec59951deaf)
- id:: c948b3f2-1690-4adb-9891-c8c359b8050a
- omnivore-note:: This is very much related to one of the WPs of the [[PROJECTS/SE-H2020-March-Call]] project proposal. #omnivore-note-color
+ omnivore-note:: This is very much related to one of the WPs of the [[PROJECTS/MOSAICO]] project proposal. #omnivore-note-color
> GPT Store, featuring creations by verified builders. [⤴️](https://omnivore.app/me/https-openai-com-blog-introducing-gpts-18bd1d809d8#c948b3f2-1690-4adb-9891-c8c359b8050a) #[[LLMs]]
- id:: 16378bfa-5758-4eec-a05b-034bde5ed6ef
> you’ll also be able to earn money based on how many people are using your GPT. [⤴️](https://omnivore.app/me/https-openai-com-blog-introducing-gpts-18bd1d809d8#16378bfa-5758-4eec-a05b-034bde5ed6ef)
diff --git a/pages/Omnivore___16-01-2024___Exploring the Effect of Multiple Natural Languages on Code Suggestion Using G...___.md b/pages/Omnivore___16-01-2024___Exploring the Effect of Multiple Natural Languages on Code Suggestion Using G...___.md
index b1f3387c..eaa1b3bc 100644
--- a/pages/Omnivore___16-01-2024___Exploring the Effect of Multiple Natural Languages on Code Suggestion Using G...___.md
+++ b/pages/Omnivore___16-01-2024___Exploring the Effect of Multiple Natural Languages on Code Suggestion Using G...___.md
@@ -4,4 +4,4 @@ labels:: [[ResearchPaper]] [[LLMs]]
date-saved:: [[16-01-2024]]
date-published:: [[13-01-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___16-12-2023___Breaking the Silence- the Threats of Using LLMs in Software Engineering.md b/pages/Omnivore___16-12-2023___Breaking the Silence- the Threats of Using LLMs in Software Engineering.md
index 59e86b97..76b99420 100644
--- a/pages/Omnivore___16-12-2023___Breaking the Silence- the Threats of Using LLMs in Software Engineering.md
+++ b/pages/Omnivore___16-12-2023___Breaking the Silence- the Threats of Using LLMs in Software Engineering.md
@@ -1,16 +1,14 @@
--
-full-title:: [Breaking the Silence: the Threats of Using LLMs in Software Engineering](https://omnivore.app/me/file-18c732585b2)
-site:: [d1ysz50cxb9zwl.cloudfront.net](https://d1ysz50cxb9zwl.cloudfront.net/pOrqYDyTV9CKBD0eeANYu2WZHCNdDQB7wDT_y58lU4lasW4JqbXmMuD6RpY9fY_0/by/4646762/as/file.pdf?Expires=1702738936&Key-Pair-Id=APKAJAERRT46LD6FN4NA&Signature=daWQlTU0pvSQ2v1qvc%7Etw7E%7E-YHmoS0DO-9oApc-%7EvNdYYJJ7noVKPh47u8AcrCK7C%7ESsdvDy5srp0X3NgRO5sxex5baLc0JaXyEcmN1zZGfiiowxrWGrm64ANfBf1sRLBF6jzPxCPesgeqjRsAGp3NAZcVSLO21idC9Hnc5BBh%7ERMWJ29kZ7CmXvOLMJn0STgFIPhFKKqUz1FNequeaA3R0-DL7A7bqtpfMCzv-JtyhFWoabWul10mLO9I%7E3-3DMXzPT%7EOyGLGIv4STefVk-R0MWAo-NcXssAdPsV0epbks3GNnwhveFR9Za7j5h4HSM6sxl7ymxQvIwSChBLrIwA__)
-labels:: [[PROJECTS/SE-H2020-March-Call]] [[ResearchPaper]] [[LLMs]] [[P1]]
-date-saved:: [[16-12-2023]]
-date-archived:: [[10-01-2024]]
-is-archived:: 10
-source:: [[Omnivore]]
-state:: [[archived]]
-
+- full-title:: [Breaking the Silence: the Threats of Using LLMs in Software Engineering](https://omnivore.app/me/file-18c732585b2)
+ site:: [d1ysz50cxb9zwl.cloudfront.net](https://d1ysz50cxb9zwl.cloudfront.net/pOrqYDyTV9CKBD0eeANYu2WZHCNdDQB7wDT_y58lU4lasW4JqbXmMuD6RpY9fY_0/by/4646762/as/file.pdf?Expires=1702738936&Key-Pair-Id=APKAJAERRT46LD6FN4NA&Signature=daWQlTU0pvSQ2v1qvc%7Etw7E%7E-YHmoS0DO-9oApc-%7EvNdYYJJ7noVKPh47u8AcrCK7C%7ESsdvDy5srp0X3NgRO5sxex5baLc0JaXyEcmN1zZGfiiowxrWGrm64ANfBf1sRLBF6jzPxCPesgeqjRsAGp3NAZcVSLO21idC9Hnc5BBh%7ERMWJ29kZ7CmXvOLMJn0STgFIPhFKKqUz1FNequeaA3R0-DL7A7bqtpfMCzv-JtyhFWoabWul10mLO9I%7E3-3DMXzPT%7EOyGLGIv4STefVk-R0MWAo-NcXssAdPsV0epbks3GNnwhveFR9Za7j5h4HSM6sxl7ymxQvIwSChBLrIwA__)
+ labels:: [[PROJECTS/MOSAICO]] [[ResearchPaper]] [[LLMs]] [[P1]]
+ date-saved:: [[16-12-2023]]
+ date-archived:: [[10-01-2024]]
+ is-archived:: 10
+ source:: [[Omnivore]]
+ state:: [[archived]]
- ### Highlights
- id:: ca01de43-6653-404a-a516-5f2761c38163
- omnivore-note:: This is important to mention as a real example of when it is essential to evaluate different LLMs (AI agents) that are supposed to do the same tasks but with different accuracy [[PROJECTS/SE-H2020-March-Call]] #omnivore-note-color
+ omnivore-note:: This is important to mention as a real example of when it is essential to evaluate different LLMs (AI agents) that are supposed to do the same tasks but with different accuracy [[PROJECTS/MOSAICO]] #omnivore-note-color
> Schäfer et al. [34] investigated the performances of three LLMs (Codex, ChatGPT3.5 [28], and CodeGen [27]) in generating unit tests for Java programs. They reported remarkable performance discrepan- cies between the HumanEval [12] (>69% branch coverage) and the SF110 [21] (2% branch coverage) datasets. We remark that the for- mer is available on GitHub [12] while the latter is is not (available on SourceForge instead) [⤴️](https://omnivore.app/me/file-18c732585b2#ca01de43-6653-404a-a516-5f2761c38163)
- id:: 233aa621-eaea-458e-90cf-742ebfd300a1
> researchers can use well-established code clone detection techniques [4] to check if the generated code (e.g., test cases) is similar to code seen in online repositories [⤴️](https://omnivore.app/me/file-18c732585b2#233aa621-eaea-458e-90cf-742ebfd300a1)
@@ -40,7 +38,7 @@ state:: [[archived]]
omnivore-note:: #challenges #llms #omnivore-note-color
> Consequently, a scenario of data leakage can arise if the LLM is trained on “project A” that employs a specific API, and the resulting model is subsequently used to fix the usage of the same API in another project within the test set [⤴️](https://omnivore.app/me/file-18c732585b2#c107fb67-4ea3-4e91-bf0c-d14d32a8cb7b)
- id:: d7b35ee6-fa3f-4dd9-a71c-8497cc92023f
- omnivore-note:: This seems to be very relevant for [[PROJECTS/SE-H2020-March-Call]] #omnivore-note-color
+ omnivore-note:: This seems to be very relevant for [[PROJECTS/MOSAICO]] #omnivore-note-color
> ONNX simplifies the transition between various models, enhancing the efficiency and consistency of experimentation [⤴️](https://omnivore.app/me/file-18c732585b2#d7b35ee6-fa3f-4dd9-a71c-8497cc92023f)
- id:: c8788939-497a-4634-9a9b-0ae110c16cb4
> we advise researchers to complement the analysis of the LLMs performance with new data samples generated with metamorphic testing [⤴️](https://omnivore.app/me/file-18c732585b2#c8788939-497a-4634-9a9b-0ae110c16cb4)
diff --git a/pages/Omnivore___18-09-2023___Generative AI - Business & Information Systems Engineering.md b/pages/Omnivore___18-09-2023___Generative AI - Business & Information Systems Engineering.md
index 94abf664..fa602f79 100644
--- a/pages/Omnivore___18-09-2023___Generative AI - Business & Information Systems Engineering.md
+++ b/pages/Omnivore___18-09-2023___Generative AI - Business & Information Systems Engineering.md
@@ -4,7 +4,7 @@ author:: Zschech, Patrick
labels:: [[ResearchPaper]]
date-saved:: [[18-09-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- collapsed:: true
* ### Highlights
diff --git a/pages/Omnivore___18-10-2023___Understanding Encoder And Decoder LLMs.md b/pages/Omnivore___18-10-2023___Understanding Encoder And Decoder LLMs.md
index 37853b27..b7b43115 100644
--- a/pages/Omnivore___18-10-2023___Understanding Encoder And Decoder LLMs.md
+++ b/pages/Omnivore___18-10-2023___Understanding Encoder And Decoder LLMs.md
@@ -1,7 +1,7 @@
full-title:: [Understanding Encoder And Decoder LLMs](https://omnivore.app/me/understanding-encoder-and-decoder-ll-ms-18b4225c289)
site:: [Ahead of AI](https://magazine.sebastianraschka.com/p/understanding-encoder-and-decoder)
author:: Sebastian Raschka, PhD
-labels:: [[PROJECTS/SE-H2020-March-Call]]
+labels:: [[PROJECTS/MOSAICO]]
date-saved:: [[18-10-2023]]
date-published:: [[17-06-2023]]
date-archived:: [[18-10-2023]]
@@ -9,7 +9,8 @@ is-archived:: 10
source:: [[Omnivore]]
state:: [[archived]]
- - * ### Highlights
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > BERT (**B**idirectional **E**ncoder **R**epresentations from **T**ransformers) is an encoder-only architecture based on the Transformer's encoder module. [⤴️](https://omnivore.app/me/understanding-encoder-and-decoder-ll-ms-18b4225c289#b769d9a7-30b4-414f-9fe7-b492112c397b)
- > The main idea behind masked language modeling is to mask (or replace) random word tokens in the input sequence and then train the model to predict the original masked tokens based on the surrounding context. [⤴️](https://omnivore.app/me/understanding-encoder-and-decoder-ll-ms-18b4225c289#7406f31a-4621-49f5-a442-0369e9b192be)
diff --git a/pages/Omnivore___19-01-2024___📝 Guest Post- How to Build the Right Team for Generative AI-.md b/pages/Omnivore___19-01-2024___📝 Guest Post- How to Build the Right Team for Generative AI-.md
index 77fd19fb..9c31366a 100644
--- a/pages/Omnivore___19-01-2024___📝 Guest Post- How to Build the Right Team for Generative AI-.md
+++ b/pages/Omnivore___19-01-2024___📝 Guest Post- How to Build the Right Team for Generative AI-.md
@@ -4,7 +4,7 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[19-01-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___19-02-2024___ChatGPT Prompt Engineering - Prompt Engineering Guide.md b/pages/Omnivore___19-02-2024___ChatGPT Prompt Engineering - Prompt Engineering Guide.md
index 020e0cc0..3becd2d0 100644
--- a/pages/Omnivore___19-02-2024___ChatGPT Prompt Engineering - Prompt Engineering Guide.md
+++ b/pages/Omnivore___19-02-2024___ChatGPT Prompt Engineering - Prompt Engineering Guide.md
@@ -2,4 +2,4 @@ full-title:: [ChatGPT Prompt Engineering | Prompt Engineering Guide](https://omn
site:: [promptingguide.ai](https://www.promptingguide.ai/models/chatgpt)
date-saved:: [[19-02-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___19-05-2024___Due minacce alla reputazione delle università telematiche - ROARS.md b/pages/Omnivore___19-05-2024___Due minacce alla reputazione delle università telematiche - ROARS.md
index 8207edda..48f6b87a 100644
--- a/pages/Omnivore___19-05-2024___Due minacce alla reputazione delle università telematiche - ROARS.md
+++ b/pages/Omnivore___19-05-2024___Due minacce alla reputazione delle università telematiche - ROARS.md
@@ -5,7 +5,7 @@ labels:: [[University]]
date-saved:: [[19-05-2024]]
date-published:: [[10-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___20-02-2024___Announcing the General Availability of LangSmith and Our Series A Led By Sequ...___.md b/pages/Omnivore___20-02-2024___Announcing the General Availability of LangSmith and Our Series A Led By Sequ...___.md
index 82fa1e89..80f461e9 100644
--- a/pages/Omnivore___20-02-2024___Announcing the General Availability of LangSmith and Our Series A Led By Sequ...___.md
+++ b/pages/Omnivore___20-02-2024___Announcing the General Availability of LangSmith and Our Series A Led By Sequ...___.md
@@ -5,4 +5,4 @@
date-saved:: [[20-02-2024]]
date-published:: [[15-02-2024]]
source:: [[Omnivore]]
- state:: [[reading]]
\ No newline at end of file
+ state:: [[Reading]]
\ No newline at end of file
diff --git a/pages/Omnivore___20-10-2024___NVIDIA Releases Nemotron 70B.md b/pages/Omnivore___20-10-2024___NVIDIA Releases Nemotron 70B.md
index c93fc3ae..4f6e21e4 100644
--- a/pages/Omnivore___20-10-2024___NVIDIA Releases Nemotron 70B.md
+++ b/pages/Omnivore___20-10-2024___NVIDIA Releases Nemotron 70B.md
@@ -4,7 +4,7 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[20-10-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
- > NVIDIA made headlines in AI again this week, but surprisingly, it wasn’t about GPUs. Beyond its hardware dominance, the tech giant has been making waves in the AI software space by releasing advanced models built on Llama technology. [⤴️](https://omnivore.app/me/nvidia-releases-nemotron-70-b-192a9a6ac40#88a7b983-e1e7-476b-9124-d6e6a08a1954)
diff --git a/pages/Omnivore___20-11-2023___Per capire cos’è successo a Sam Altman, bisogna sapere com’è fatta davvero Op...___.md b/pages/Omnivore___20-11-2023___Per capire cos’è successo a Sam Altman, bisogna sapere com’è fatta davvero Op...___.md
index 434fdac1..ff8de0f8 100644
--- a/pages/Omnivore___20-11-2023___Per capire cos’è successo a Sam Altman, bisogna sapere com’è fatta davvero Op...___.md
+++ b/pages/Omnivore___20-11-2023___Per capire cos’è successo a Sam Altman, bisogna sapere com’è fatta davvero Op...___.md
@@ -19,8 +19,20 @@ state:: [[archived]]
- * id:: bdf4de5f-3201-45a1-a997-c7a32962c209
> **OpenAI LP**, un’azienda _“capped-profit”_ che invece insegue i profitti per garantire al laboratorio non profit di portare avanti il suo lavoro. [⤴️](https://omnivore.app/me/https-www-repubblica-it-tecnologia-2023-11-19-news-licenziamento-18becf1a7dc#bdf4de5f-3201-45a1-a997-c7a32962c209)
- id:: 65c8d46a-a96c-439a-a422-5844900d83ea
- * id:: 14e1f8c8-76e1-4e9e-99b2-e69839a2cc96
- > “capped-profit” si intende che i profitti di OpenAI LP **vengono distribuiti agli investitori entro un certo limite** [⤴️](https://omnivore.app/me/https-www-repubblica-it-tecnologia-2023-11-19-news-licenziamento-18becf1a7dc#14e1f8c8-76e1-4e9e-99b2-e69839a2cc96)
+ card-last-interval:: 4
+ card-repeats:: 1
+ card-ease-factor:: 2.6
+ card-next-schedule:: 2025-12-28T09:11:17.407Z
+ card-last-reviewed:: 2025-12-24T09:11:17.408Z
+ card-last-score:: 5
omnivore-note:: #card
+ card-last-interval:: 4
+ card-repeats:: 1
+ card-ease-factor:: 2.6
+ card-next-schedule:: 2025-12-28T09:11:17.407Z
+ card-last-reviewed:: 2025-12-24T09:11:17.408Z
+ card-last-score:: 5
+ * id:: 14e1f8c8-76e1-4e9e-99b2-e69839a2cc96
+ > “capped-profit” si intende che i profitti di OpenAI LP **vengono distribuiti agli investitori entro un certo limite** [⤴️](https://omnivore.app/me/https-www-repubblica-it-tecnologia-2023-11-19-news-licenziamento-18becf1a7dc#14e1f8c8-76e1-4e9e-99b2-e69839a2cc96)
- * id:: 3d0ff0f3-f41c-40a8-96e9-c2a95ceac8ef
> Sutskever teme che i rapidi progressi dell’IA possano costituire **un pericolo per l’uomo**. E che la guida di Sam Altman - **che ha trasformato OpenAI in una macchina da soldi** \- non abbia tenuto abbastanza conto di questi rischi. [⤴️](https://omnivore.app/me/https-www-repubblica-it-tecnologia-2023-11-19-news-licenziamento-18becf1a7dc#3d0ff0f3-f41c-40a8-96e9-c2a95ceac8ef)
\ No newline at end of file
diff --git a/pages/Omnivore___21-01-2024___The Model Solving Geometry Problems at the Level of a Math Olympiad Gold Meda...___.md b/pages/Omnivore___21-01-2024___The Model Solving Geometry Problems at the Level of a Math Olympiad Gold Meda...___.md
index 635f0c8b..40b4b36b 100644
--- a/pages/Omnivore___21-01-2024___The Model Solving Geometry Problems at the Level of a Math Olympiad Gold Meda...___.md
+++ b/pages/Omnivore___21-01-2024___The Model Solving Geometry Problems at the Level of a Math Olympiad Gold Meda...___.md
@@ -5,6 +5,6 @@
labels:: [[Newsletter]]
date-saved:: [[21-01-2024]]
source:: [[Omnivore]]
- state:: [[reading]]
+ state:: [[Reading]]
- ### Highlights
- > The most interesting aspect of AlphaGeometry is its architecture, which combines a Large Language Model (LLM) with a symbolic model. Neuro-symbolic architectures have long [⤴️](https://omnivore.app/me/the-model-solving-geometry-problems-at-the-level-of-a-math-olymp-18d2bf79d08#483b34ef-9b24-4742-a333-72202f9bca69) #[[STAR]]
\ No newline at end of file
diff --git a/pages/Omnivore___21-03-2024___Edge 380- Inside SELF-Discover- Google DeepMind's LLM Reasoning Method for So...___.md b/pages/Omnivore___21-03-2024___Edge 380- Inside SELF-Discover- Google DeepMind's LLM Reasoning Method for So...___.md
index 3be5ac58..6c20fa99 100644
--- a/pages/Omnivore___21-03-2024___Edge 380- Inside SELF-Discover- Google DeepMind's LLM Reasoning Method for So...___.md
+++ b/pages/Omnivore___21-03-2024___Edge 380- Inside SELF-Discover- Google DeepMind's LLM Reasoning Method for So...___.md
@@ -4,7 +4,7 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]] [[LLMs]]
date-saved:: [[21-03-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___21-03-2024___GPT-5 leaked new features and release date.___.md b/pages/Omnivore___21-03-2024___GPT-5 leaked new features and release date.___.md
index 3849141e..8232394f 100644
--- a/pages/Omnivore___21-03-2024___GPT-5 leaked new features and release date.___.md
+++ b/pages/Omnivore___21-03-2024___GPT-5 leaked new features and release date.___.md
@@ -3,4 +3,4 @@ site:: [omnivore.app](https://omnivore.app/no_url?q=e9ddbc2f-e2df-416b-9293-42cb
labels:: [[Newsletter]]
date-saved:: [[21-03-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___21-05-2024___Il piano inclinato. Rischi e punti di tenuta del sistema universitario italia...___.md b/pages/Omnivore___21-05-2024___Il piano inclinato. Rischi e punti di tenuta del sistema universitario italia...___.md
index 776c16b4..84d21e5c 100644
--- a/pages/Omnivore___21-05-2024___Il piano inclinato. Rischi e punti di tenuta del sistema universitario italia...___.md
+++ b/pages/Omnivore___21-05-2024___Il piano inclinato. Rischi e punti di tenuta del sistema universitario italia...___.md
@@ -4,4 +4,4 @@ author:: Di Redazione ROARS -
date-saved:: [[21-05-2024]]
date-published:: [[20-05-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___21-08-2023___OpenCopilot, assistente digitale open source per qualunque progetto.md b/pages/Omnivore___21-08-2023___OpenCopilot, assistente digitale open source per qualunque progetto.md
index 82549ef9..edf37daf 100644
--- a/pages/Omnivore___21-08-2023___OpenCopilot, assistente digitale open source per qualunque progetto.md
+++ b/pages/Omnivore___21-08-2023___OpenCopilot, assistente digitale open source per qualunque progetto.md
@@ -4,7 +4,7 @@ author:: Michele Nasi
date-saved:: [[21-08-2023]]
date-published:: [[21-08-2023]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- collapsed:: true
* ### Highlights
diff --git a/pages/Omnivore___22-11-2023___IngestAI-deepmark- Deepmark AI enables a unique testing environment for langu...___.md b/pages/Omnivore___22-11-2023___IngestAI-deepmark- Deepmark AI enables a unique testing environment for langu...___.md
index 39beeeee..8ef161b0 100644
--- a/pages/Omnivore___22-11-2023___IngestAI-deepmark- Deepmark AI enables a unique testing environment for langu...___.md
+++ b/pages/Omnivore___22-11-2023___IngestAI-deepmark- Deepmark AI enables a unique testing environment for langu...___.md
@@ -1,12 +1,13 @@
--
-- full-title:: [IngestAI/deepmark: Deepmark AI enables a unique testing environment for language models (LLM) assessment on task-specific metrics and on your own data so your GenAI-powered solution has predictable and reliable performance.](https://omnivore.app/me/ingest-ai-deepmark-deepmark-ai-enables-a-unique-testing-environm-18bf7591eb9)
- site:: [GitHub](https://github.com/IngestAI/deepmark)
- labels:: [[PROJECTS/SE-H2020-March-Call]]
- date-saved:: [[22-11-2023]]
- date-archived:: [[10-01-2024]]
- is-archived:: 10
- source:: [[Omnivore]]
- state:: [[archived]]
+full-title:: [IngestAI/deepmark: Deepmark AI enables a unique testing environment for language models (LLM) assessment on task-specific metrics and on your own data so your GenAI-powered solution has predictable and reliable performance.](https://omnivore.app/me/ingest-ai-deepmark-deepmark-ai-enables-a-unique-testing-environm-18bf7591eb9)
+site:: [GitHub](https://github.com/IngestAI/deepmark)
+labels:: [[PROJECTS/MOSAICO]]
+date-saved:: [[22-11-2023]]
+date-archived:: [[10-01-2024]]
+is-archived:: 10
+source:: [[Omnivore]]
+state:: [[archived]]
+tags:: [[PROJECTS/MOSAICO]] [[Benchmarks]]
+
- ### Highlights
- > 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. [⤴️](https://omnivore.app/me/ingest-ai-deepmark-deepmark-ai-enables-a-unique-testing-environm-18bf7591eb9#f595a922-f1b1-42d5-8354-fe6dfd39bb32)
diff --git a/pages/Omnivore___23-02-2024___📝 Guest Post- LoRA Land- 25 Fine-Tuned Mistral-7b LLMs that Rival or Outperfo...___.md b/pages/Omnivore___23-02-2024___📝 Guest Post- LoRA Land- 25 Fine-Tuned Mistral-7b LLMs that Rival or Outperfo...___.md
index 0ae88eaa..084b606c 100644
--- a/pages/Omnivore___23-02-2024___📝 Guest Post- LoRA Land- 25 Fine-Tuned Mistral-7b LLMs that Rival or Outperfo...___.md
+++ b/pages/Omnivore___23-02-2024___📝 Guest Post- LoRA Land- 25 Fine-Tuned Mistral-7b LLMs that Rival or Outperfo...___.md
@@ -5,4 +5,4 @@
labels:: [[Newsletter]]
date-saved:: [[23-02-2024]]
source:: [[Omnivore]]
- state:: [[reading]]
\ No newline at end of file
+ state:: [[Reading]]
\ No newline at end of file
diff --git a/pages/Omnivore___24-01-2024___Cineca e iGenius insieme- nasce la prima Intelligenza Artificiale generativa ...___.md b/pages/Omnivore___24-01-2024___Cineca e iGenius insieme- nasce la prima Intelligenza Artificiale generativa ...___.md
index 6ec1c2a4..0d8d1273 100644
--- a/pages/Omnivore___24-01-2024___Cineca e iGenius insieme- nasce la prima Intelligenza Artificiale generativa ...___.md
+++ b/pages/Omnivore___24-01-2024___Cineca e iGenius insieme- nasce la prima Intelligenza Artificiale generativa ...___.md
@@ -4,4 +4,4 @@ author:: Luca De Biase
date-saved:: [[24-01-2024]]
date-published:: [[24-01-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___24-01-2024___Come utilizzare ChatGPT-4 gratis - FASTWEBPLUS.md b/pages/Omnivore___24-01-2024___Come utilizzare ChatGPT-4 gratis - FASTWEBPLUS.md
index a83214a8..be669c47 100644
--- a/pages/Omnivore___24-01-2024___Come utilizzare ChatGPT-4 gratis - FASTWEBPLUS.md
+++ b/pages/Omnivore___24-01-2024___Come utilizzare ChatGPT-4 gratis - FASTWEBPLUS.md
@@ -11,11 +11,17 @@
- ### Highlights
collapsed:: true
- > Da **Bing** a **Perplexity**, passando per **Merlyn**, **Nat.dev** e **Hugging Face**. Software che garantiscono **l’utilizzo gratuito del GPT-4**. Ma che presentano anche **qualche limitazione**: sia in termini di operatività che di funzioni disponibili. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#8a570183-40d3-4832-a270-63a0aff60887)
- - > **GPT-4** è invece la sigla utilizzata per fare riferimento alla quarta generazione di un **modello linguistico multimodale**. In entrambi i casi l’acronimo GPT sta per **Generative Pre-Trained**: un algoritmo in grado di creare o **generare contenuti inediti**, a partire da input noti col nome di prompt. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#4c7d794f-1e81-4396-8d10-8e9631e88eff)
+ - omnivore-note:: #card #omnivore-note-color
+ id:: 68584ebb-48dc-45bd-beab-d9d18678343c
+ > **GPT-4** è invece la sigla utilizzata per fare riferimento alla quarta generazione di un **modello linguistico multimodale**. In entrambi i casi l’acronimo GPT sta per **Generative Pre-Trained**: un algoritmo in grado di creare o **generare contenuti inediti**, a partire da input noti col nome di prompt. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#4c7d794f-1e81-4396-8d10-8e9631e88eff)
- omnivore-note:: #cards #omnivore-note-color
+ omnivore-note:: #card #omnivore-note-color
+ id:: 68584ebb-48dc-45bd-beab-d9d18678343c
- > [**Bing Chat AI**](https://www.fastweb.it/fastweb-plus/digital-dev-security/principali-funzionalita-di-bing-chat-ai/) utilizzava proprio il **modello di linguaggio GPT-4**, ma non solo. A differenza di ChatGPT 4 infatti, Bing può essere **testato gratuitamente**. A patto che non si superi il limite di **300 chat quotidiane**. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#cf8f3aab-a36b-4593-9b9e-cf30f502efff)
- > **Perplexity**: un **motore di ricerca** molto promettente, che ha già convinto a investire stakeholder del calibro di **Amazon** e **Shopify**. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#57b1fa4c-90b2-40df-997f-965ea927c094)
- - > Hugging Face è **un sito web** creato proprio per l’apprendimento automatico. Uno **spazio open source**, in cui migliaia di utenti, sviluppatori e non, contribuiscono alla **crescita di un’intelligenza artificiale**. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#d3e5c8a0-3914-43ac-85ce-c838a677d19a)
+ - omnivore-note:: #card #omnivore-note-color
+ id:: 68584ebb-3225-48c8-8779-d16e764b8808
+ > Hugging Face è **un sito web** creato proprio per l’apprendimento automatico. Uno **spazio open source**, in cui migliaia di utenti, sviluppatori e non, contribuiscono alla **crescita di un’intelligenza artificiale**. [⤴️](https://omnivore.app/me/come-utilizzare-chat-gpt-4-gratis-fastwebplus-18d3ac97c71#d3e5c8a0-3914-43ac-85ce-c838a677d19a)
- omnivore-note:: #cards #omnivore-note-color
\ No newline at end of file
+ omnivore-note:: #card #omnivore-note-color
+ id:: 68584ebb-3225-48c8-8779-d16e764b8808
\ No newline at end of file
diff --git a/pages/Omnivore___24-09-2023___Data science for next-generation recommender systems.md b/pages/Omnivore___24-09-2023___Data science for next-generation recommender systems.md
index ed5965c2..119b8779 100644
--- a/pages/Omnivore___24-09-2023___Data science for next-generation recommender systems.md
+++ b/pages/Omnivore___24-09-2023___Data science for next-generation recommender systems.md
@@ -1,13 +1,12 @@
--
-full-title:: [Data science for next-generation recommender systems](https://omnivore.app/me/s-41060-023-00404-w-18ac7cbb212)
-site:: [link.springer.com](https://link.springer.com/content/pdf/10.1007/s41060-023-00404-w.pdf)
-author:: Shoujin Wang
-labels:: [[ResearchPaper]] [[P1]] [[recsys]]
-date-saved:: [[24-09-2023]]
-source:: [[Omnivore]]
-state:: [[reading]]
-
- - * ### Highlights
+- full-title:: [Data science for next-generation recommender systems](https://omnivore.app/me/s-41060-023-00404-w-18ac7cbb212)
+ site:: [link.springer.com](https://link.springer.com/content/pdf/10.1007/s41060-023-00404-w.pdf)
+ author:: Shoujin Wang
+ labels:: [[ResearchPaper]] [[P1]] [[recsys]]
+ date-saved:: [[24-09-2023]]
+ source:: [[Omnivore]]
+ state:: [[Reading]]
+ - collapsed:: true
+ * ### Highlights
collapsed:: true
- > Data science has been the foundation of recommender systems for a long time [⤴️](https://omnivore.app/me/s-41060-023-00404-w-18ac7cbb212#cfd7078e-db00-44f3-b27e-8f2af0122401)
- > various recommender systems have been developed using different data science and machine learning methodologies and techniques [⤴️](https://omnivore.app/me/s-41060-023-00404-w-18ac7cbb212#c0f64226-c49b-4b65-a681-290585565139)
diff --git a/pages/Omnivore___25-01-2024___About COSP and USP- Two New LLM Reasoning Methods Built by Google Research.md b/pages/Omnivore___25-01-2024___About COSP and USP- Two New LLM Reasoning Methods Built by Google Research.md
index 961950d3..959f61ee 100644
--- a/pages/Omnivore___25-01-2024___About COSP and USP- Two New LLM Reasoning Methods Built by Google Research.md
+++ b/pages/Omnivore___25-01-2024___About COSP and USP- Two New LLM Reasoning Methods Built by Google Research.md
@@ -5,4 +5,4 @@
labels:: [[Newsletter]]
date-saved:: [[25-01-2024]]
source:: [[Omnivore]]
- state:: [[reading]]
\ No newline at end of file
+ state:: [[Reading]]
\ No newline at end of file
diff --git a/pages/Omnivore___25-01-2024___Announcing LangSmith, a unified platform for debugging, testing, evaluating, ...___.md b/pages/Omnivore___25-01-2024___Announcing LangSmith, a unified platform for debugging, testing, evaluating, ...___.md
index d5790758..6f302940 100644
--- a/pages/Omnivore___25-01-2024___Announcing LangSmith, a unified platform for debugging, testing, evaluating, ...___.md
+++ b/pages/Omnivore___25-01-2024___Announcing LangSmith, a unified platform for debugging, testing, evaluating, ...___.md
@@ -2,7 +2,7 @@
- full-title:: [Announcing LangSmith, a unified platform for debugging, testing, evaluating, and monitoring your LLM applications](https://omnivore.app/me/announcing-lang-smith-a-unified-platform-for-debugging-testing-e-18d3fd3565c)
site:: [LangChain Blog](https://blog.langchain.dev/announcing-langsmith/)
author:: LangChain
- labels:: [[PROJECTS/SE-H2020-March-Call]]
+ labels:: [[PROJECTS/MOSAICO]]
date-saved:: [[25-01-2024]]
date-published:: [[18-07-2023]]
source:: [[Omnivore]]
diff --git a/pages/Omnivore___25-01-2024___Overview - 🦜️🛠️ LangSmith.md b/pages/Omnivore___25-01-2024___Overview - 🦜️🛠️ LangSmith.md
index dcd2ea8c..0638e459 100644
--- a/pages/Omnivore___25-01-2024___Overview - 🦜️🛠️ LangSmith.md
+++ b/pages/Omnivore___25-01-2024___Overview - 🦜️🛠️ LangSmith.md
@@ -1,6 +1,6 @@
full-title:: [Overview | 🦜️🛠️ LangSmith](https://omnivore.app/me/overview-lang-smith-18d3fd0ea08)
site:: [docs.smith.langchain.com](https://docs.smith.langchain.com/tracing)
-labels:: [[PROJECTS/SE-H2020-March-Call]]
+labels:: [[PROJECTS/MOSAICO]]
date-saved:: [[25-01-2024]]
source:: [[Omnivore]]
state:: [[saved]]
diff --git a/pages/Omnivore___26-10-2024___Cache All the Things.md b/pages/Omnivore___26-10-2024___Cache All the Things.md
index 9535ba08..9b10d24b 100644
--- a/pages/Omnivore___26-10-2024___Cache All the Things.md
+++ b/pages/Omnivore___26-10-2024___Cache All the Things.md
@@ -3,4 +3,4 @@ site:: [blog.dendron.so](https://blog.dendron.so/notes/o2qlr31o99tycon4hlhgjhw/)
author:: unknown
date-saved:: [[26-10-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___27-02-2024___5 esercizi per un core forte e stabile.md b/pages/Omnivore___27-02-2024___5 esercizi per un core forte e stabile.md
index aba35c79..c6d2741c 100644
--- a/pages/Omnivore___27-02-2024___5 esercizi per un core forte e stabile.md
+++ b/pages/Omnivore___27-02-2024___5 esercizi per un core forte e stabile.md
@@ -4,4 +4,4 @@ author:: Elisabetta Brivio
date-saved:: [[27-02-2024]]
date-published:: [[20-02-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___27-02-2024___ORBi UMONS- Detailled Reference.md b/pages/Omnivore___27-02-2024___ORBi UMONS- Detailled Reference.md
index 7d180569..ef8a1036 100644
--- a/pages/Omnivore___27-02-2024___ORBi UMONS- Detailled Reference.md
+++ b/pages/Omnivore___27-02-2024___ORBi UMONS- Detailled Reference.md
@@ -3,4 +3,4 @@ site:: [orbi.umons.ac.be](https://orbi.umons.ac.be/handle/20.500.12907/48470)
author:: Decan, Alexandre; Université de Mons - UMONS > Faculté des Sciences > Service de Génie Logiciel
date-saved:: [[27-02-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___27-06-2024___Edge 406- Inside OpenAI's Recent Breakthroughs in GPT-4 Interpretability.md b/pages/Omnivore___27-06-2024___Edge 406- Inside OpenAI's Recent Breakthroughs in GPT-4 Interpretability.md
index 996c64c7..bae7a416 100644
--- a/pages/Omnivore___27-06-2024___Edge 406- Inside OpenAI's Recent Breakthroughs in GPT-4 Interpretability.md
+++ b/pages/Omnivore___27-06-2024___Edge 406- Inside OpenAI's Recent Breakthroughs in GPT-4 Interpretability.md
@@ -4,7 +4,7 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[27-06-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___27-09-2024___How Does AI -See- Us-.md b/pages/Omnivore___27-09-2024___How Does AI -See- Us-.md
index 1a9bd09e..6661ac21 100644
--- a/pages/Omnivore___27-09-2024___How Does AI -See- Us-.md
+++ b/pages/Omnivore___27-09-2024___How Does AI -See- Us-.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[27-09-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___27-10-2024___How to Get a PhD- Your Journey to a Doctoral Degree.md b/pages/Omnivore___27-10-2024___How to Get a PhD- Your Journey to a Doctoral Degree.md
index b18da33c..b9c61c05 100644
--- a/pages/Omnivore___27-10-2024___How to Get a PhD- Your Journey to a Doctoral Degree.md
+++ b/pages/Omnivore___27-10-2024___How to Get a PhD- Your Journey to a Doctoral Degree.md
@@ -4,7 +4,7 @@ author:: Mark Bennett
date-saved:: [[27-10-2024]]
date-published:: [[14-09-2022]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
- > ### 1\. Preparing a research proposal [⤴️](https://omnivore.app/me/how-to-get-a-ph-d-your-journey-to-a-doctoral-degree-192cde033e1#f9a64964-ab60-468c-ab88-4f6a84925c4d)
\ No newline at end of file
diff --git a/pages/Omnivore___28-06-2024___📝 Guest Post- Designing Prompts for LLM-as-a-Judge Model Evals-.md b/pages/Omnivore___28-06-2024___📝 Guest Post- Designing Prompts for LLM-as-a-Judge Model Evals-.md
index 567b7b6d..ba5dd5f1 100644
--- a/pages/Omnivore___28-06-2024___📝 Guest Post- Designing Prompts for LLM-as-a-Judge Model Evals-.md
+++ b/pages/Omnivore___28-06-2024___📝 Guest Post- Designing Prompts for LLM-as-a-Judge Model Evals-.md
@@ -4,4 +4,4 @@ author:: davide.diruscio@gmail.com
labels:: [[Newsletter]]
date-saved:: [[28-06-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___29-08-2024___Brain fog - healthdirect.md b/pages/Omnivore___29-08-2024___Brain fog - healthdirect.md
index 390e4156..9a391c8e 100644
--- a/pages/Omnivore___29-08-2024___Brain fog - healthdirect.md
+++ b/pages/Omnivore___29-08-2024___Brain fog - healthdirect.md
@@ -3,4 +3,4 @@ site:: [healthdirect.gov.au](https://www.healthdirect.gov.au/brain-fog)
author:: Healthdirect Australia
date-saved:: [[29-08-2024]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
diff --git a/pages/Omnivore___29-08-2024___How to Recharge Your Mind and Body When You Feel Drained.md b/pages/Omnivore___29-08-2024___How to Recharge Your Mind and Body When You Feel Drained.md
index b2bfce4f..9dd05cac 100644
--- a/pages/Omnivore___29-08-2024___How to Recharge Your Mind and Body When You Feel Drained.md
+++ b/pages/Omnivore___29-08-2024___How to Recharge Your Mind and Body When You Feel Drained.md
@@ -4,7 +4,7 @@ author:: Erica Cirino
date-saved:: [[29-08-2024]]
date-published:: [[26-10-2018]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___30-03-2024___The rise and fall of peer review - by Adam Mastroianni.md b/pages/Omnivore___30-03-2024___The rise and fall of peer review - by Adam Mastroianni.md
index 209ef1bd..7e837b0f 100644
--- a/pages/Omnivore___30-03-2024___The rise and fall of peer review - by Adam Mastroianni.md
+++ b/pages/Omnivore___30-03-2024___The rise and fall of peer review - by Adam Mastroianni.md
@@ -4,7 +4,7 @@ author:: Adam Mastroianni
date-saved:: [[30-03-2024]]
date-published:: [[13-12-2022]]
source:: [[Omnivore]]
-state:: [[reading]]
+state:: [[Reading]]
- ### Highlights
collapsed:: true
diff --git a/pages/Omnivore___30-11-2023___Realising synergy for bots and engineers - Office of Research.md b/pages/Omnivore___30-11-2023___Realising synergy for bots and engineers - Office of Research.md
index 6131c537..0f0652ea 100644
--- a/pages/Omnivore___30-11-2023___Realising synergy for bots and engineers - Office of Research.md
+++ b/pages/Omnivore___30-11-2023___Realising synergy for bots and engineers - Office of Research.md
@@ -1,7 +1,7 @@
-
- full-title:: [Realising synergy for bots and engineers | Office of Research](https://omnivore.app/me/realising-synergy-for-bots-and-engineers-office-of-research-18c1f617ed5)
site:: [Office of Research](https://research.smu.edu.sg/news/2023/feb/09/realising-synergy-bots-and-engineers)
- labels:: [[PROJECTS/SE-H2020-March-Call]]
+ labels:: [[PROJECTS/MOSAICO]]
date-saved:: [[30-11-2023]]
date-published:: [[09-02-2023]]
date-archived:: [[10-01-2024]]
diff --git a/pages/PAPERS.md b/pages/PAPERS.md
index 9a81a3a6..4230fac6 100644
--- a/pages/PAPERS.md
+++ b/pages/PAPERS.md
@@ -4,7 +4,6 @@ progress:: {{renderer :todomaster}}
- ## ⛑️ WORKING
id:: 656bb92d-99b8-4f8c-8498-d79698ff9dc8
- collapsed:: true
- {{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
@@ -24,18 +23,16 @@ progress:: {{renderer :todomaster}}
query-sort-by:: block
query-sort-desc:: true
- ## [[SUBMITTED]]
- collapsed:: true
- {{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]]
- collapsed:: true
- - {{query (and (namespace [[papers]]) (page-property :status [[ACCEPTED]]) (page-property :year "2024"))}}
- query-properties:: [:page :year :venue :todoist :type]
+ - {{query (and (namespace [[papers]]) (page-property :status [[ACCEPTED]]) (page-property :year "2025"))}}
query-sort-by:: type
query-sort-desc:: false
+ query-properties:: [:page :year :venue :todoist :type]
- ## [[REJECTED]]
collapsed:: true
- {{query (and (namespace [[papers]]) (page-property :status [[REJECTED]]) (page-property :year "2024"))}}
@@ -44,5 +41,6 @@ progress:: {{renderer :todomaster}}
collapsed:: true
- {{query (and (namespace [[papers]]) (page-property :status [[IDLE]] ) )}}
- ## Acknowledgments
+ collapsed:: true
- 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.
-
\ No newline at end of file
diff --git a/pages/PAPERS___2024-TESORO.md b/pages/PAPERS___2024-TESORO.md
index 3ccbae80..0735afa4 100644
--- a/pages/PAPERS___2024-TESORO.md
+++ b/pages/PAPERS___2024-TESORO.md
@@ -5,7 +5,7 @@ external-links:: [TSE-Tesoro (Copy) - Online LaTeX Editor Overleaf](https://www
todoist:: [7840710789](https://todoist.com/showTask?id=7840710789)
year::
date-start::
-status:: [[DOING]]
+status:: [[SUBMITTED]]
priority:: [[p1]]
leader:: [[people/PhuongNguyen]]
progress:: {{renderer :todomaster}}
diff --git a/pages/PAPERS___2024-TOSEM-FUTURE-SE.md b/pages/PAPERS___2024-TOSEM-FUTURE-SE.md
index 2e80656d..673bf10c 100644
--- a/pages/PAPERS___2024-TOSEM-FUTURE-SE.md
+++ b/pages/PAPERS___2024-TOSEM-FUTURE-SE.md
@@ -44,8 +44,8 @@ progress:: {{renderer :todomaster}}
The proliferation of domain-specific modeling languages (DSMLs) and modeling paradigms has led to a diverse landscape of formalisms and languages within MDE. This diversity poses challenges for automation, as each modeling language may have its own syntax, semantics, and transformation rules. Ensuring interoperability and tooling support across diverse formalisms and languages requires developing standardized interfaces, transformation mechanisms, and model interchange formats. Moreover, accommodating new modeling paradigms, such as graph-based modeling or aspect-oriented modeling, necessitates continuous adaptation of automation techniques and tools.
- 3. **The Allware/Low-Code Objective of MDE:**
MDE aims to democratize software development by enabling non-computer science and software engineering specialists to participate in modeling and code generation activities. However, achieving this objective requires overcoming several challenges. One challenge is designing intuitive modeling tools that abstract away technical complexities and provide user-friendly interfaces for creating and manipulating models. Additionally, ensuring that automated code generation processes produce high-quality, maintainable code requires addressing issues related to code efficiency, readability, and adherence to coding standards. Moreover, integrating MDE capabilities into low-code platforms and environments necessitates developing standardized interfaces and interoperability protocols.
- - 4. **Scarcity of Datasets and Benchmarks for AI Models:**
- The advancement of AI-driven automation in MDE is hindered by the scarcity of high-quality datasets and benchmarks for training and evaluating AI models. Unlike domains like natural language processing or computer vision, where large-scale datasets are readily available, MDE lacks comprehensive datasets that capture the diverse range of modeling tasks and domains. Moreover, concerns regarding data privacy and the ethical use of data further complicate the acquisition and sharing of modeling datasets. Addressing these challenges requires collaboration between researchers, practitioners, and stakeholders to curate datasets, define evaluation metrics, and establish best practices for data collection and sharing in MDE contexts.
+ - 4. **Scarcity of Datasets and [[Benchmarks]] for AI Models:**
+ The advancement of AI-driven automation in MDE is hindered by the scarcity of high-quality datasets and [[benchmarks]] for training and evaluating AI models. Unlike domains like natural language processing or computer vision, where large-scale datasets are readily available, MDE lacks comprehensive datasets that capture the diverse range of modeling tasks and domains. Moreover, concerns regarding data privacy and the ethical use of data further complicate the acquisition and sharing of modeling datasets. Addressing these challenges requires collaboration between researchers, practitioners, and stakeholders to curate datasets, define evaluation metrics, and establish best practices for data collection and sharing in MDE contexts.
- 5. **Better Modeling Tools:**
Despite significant advancements in modeling tools, many existing tools in MDE are tailored towards expert users and lack intuitive interfaces for non-specialists. This poses challenges for broadening the adoption of MDE methodologies across diverse domains and user communities. Improving the accessibility and usability of modeling tools requires incorporating user-centered design principles, conducting usability studies, and providing comprehensive documentation and training materials. Additionally, ensuring compatibility and interoperability between different modeling tools and environments is essential for facilitating seamless collaboration and exchange of models among users with varying expertise levels.
- ### Perspectives
diff --git a/pages/PAPERS___2025-IEEESOFTWARE-AGENTIC-SI.md b/pages/PAPERS___2025-IEEESOFTWARE-AGENTIC-SI.md
new file mode 100644
index 00000000..e451b892
--- /dev/null
+++ b/pages/PAPERS___2025-IEEESOFTWARE-AGENTIC-SI.md
@@ -0,0 +1,28 @@
+tags:: #todoist-task [[PAPERS]]
+date:: [[09-12-2025]] - 11:27
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ - TODO Figura 1 va rifatta per evitare problemi di Copyright
+ - TODO Prendere Fig. 8 del deliverable
+ - TODO Capire come gestire i riferimenti di tabella 1, quindi se avere o meno una sezzione appendix
+ - TODO Forse da aggiungere un esempio/dettaglio in una delle 5 dimensioni
+ - TODO Sfruttare quando possibile i footnote invece delle ref (limitate a 15)
+ -
+ - ### Notes
+ - This is a paper to be submitted to the IEEE Special issue [Call for Papers: Special Issue on Engineering Agentic Systems](https://www.computer.org/digital-library/magazines/so/cfp-engineering-agentic-systems)
+ - The issue is seeking submissions meeting the following requests:
+ - Developers must **decide whether to rely on the FM/LLM or external tools/systems for the same functionality**. These decisions can be made at various stages depending on the problem and context: during design time, development time, or event at runtime from a software engineering perspective, and at pre-training time, post-training time, test/inference time, and post-inference time from an AI perspective. Highly autonomous agentic systems also require continuous monitoring, evaluation, observability, intervention, and oversight after deployment, an emerging discipline referred to as AgentOps. Designing this post-deployment environment is also highly complex, with many interdependent design choices.
+ - This special issue aims to address these challenges by **exploring cutting-edge engineering methods, techniques, tools, and practices for agentic systems.** It seeks articles that provide with **insights into the design, development, and operation of agentic systems**, emphasizing practical applications and **real-world experiences**.
+ - Topics of interests include, but are not limited to:
+ - Requirements engineering for agentic systems
+ - Architectural design for agentic systems
+ - Verification, validation, and testing of agentic systems
+ - AgentOps - DevOps for agentic systems
+ - Development processes and lifecycle management for agentic systems
+ - Evaluation methodologies, tools, and benchmarks for agentic systems
+ - Responsible AI and AI safety of agentic systems
+ - Agentic systems for software engineering, including requirements, design, coding, testing, deployment, and operations
+ - Human-agent interaction, collaboration, and oversight
+ - Risk and impact assessment (e.g. economic/social impact)
+ - Real-world case studies and practical experiences in different domain
\ No newline at end of file
diff --git a/pages/PAPERS___2025-JSS-LAMPS-UMAR.md b/pages/PAPERS___2025-JSS-LAMPS-UMAR.md
new file mode 100644
index 00000000..775265ef
--- /dev/null
+++ b/pages/PAPERS___2025-JSS-LAMPS-UMAR.md
@@ -0,0 +1,40 @@
+type:: [[JournalPaper]]
+date:: [[19-09-2025]] - 14:55
+full-title::
+external-links::
+todoist::
+year:: 2025
+date-start::
+status:: [[SUBMITTED]]
+venue::
+priority:: [[P1]]
+parent::
+leader::
+todoist:: https://app.todoist.com/app/task/papers-2025-jss-lamps-umar-6cpGFH78M2c7JcC5
+progress:: {{renderer :todomaster}}
+
+ - #.tabular
+ - ## MEETINGS
+ - {{query (and [[PAPERS/2025-JSS-LAMPS-UMAR]] (block-property :type [[meeting]]) (not (page [[PAPERS/2025-JSS-LAMPS-UMAR]])))}}
+ - 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]][[PAPERS/2025-JSS-LAMPS-UMAR]])}}
+ - ## [[PAPERS/NOTES]]
+ -
\ No newline at end of file
diff --git a/pages/PAPERS___2025-Survey-MOSAICO.md b/pages/PAPERS___2025-Survey-MOSAICO.md
index b12ab21c..892cc934 100644
--- a/pages/PAPERS___2025-Survey-MOSAICO.md
+++ b/pages/PAPERS___2025-Survey-MOSAICO.md
@@ -5,7 +5,7 @@ external-links::
todoist:: https://app.todoist.com/app/task/papers-2025-survey-mosaico-6Xw9qwp3rvmj4W2X
year:: 2025
date-start::
-status:: [[SUBMITTED]]
+status:: [[REJECTED]]
venue:: [[IST]]
priority:: [[P1]]
parent::
diff --git a/pages/PAPERS___2026-ECMFA-LOMBARDI.md b/pages/PAPERS___2026-ECMFA-LOMBARDI.md
new file mode 100644
index 00000000..8282ffea
--- /dev/null
+++ b/pages/PAPERS___2026-ECMFA-LOMBARDI.md
@@ -0,0 +1,9 @@
+tags:: #todoist-task, [[PAPERS]]
+date:: [[02-12-2025]] - 09:04
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Sun 7 Dec 2025 - Round 1 - Abstract Submission
+ - Fri 19 Dec 2025 - Round 1 - Paper Submission
\ No newline at end of file
diff --git a/pages/PAPERS___2026-SANER-PERFORMANCE-BUG-DETECTION.md b/pages/PAPERS___2026-SANER-PERFORMANCE-BUG-DETECTION.md
new file mode 100644
index 00000000..3e1c1f3f
--- /dev/null
+++ b/pages/PAPERS___2026-SANER-PERFORMANCE-BUG-DETECTION.md
@@ -0,0 +1,20 @@
+type:: [[conferencepaper]]
+date:: [[01-08-2025]] - 09:25
+full-title::
+external-links::
+year:: 2026
+date-start::
+status:: [[DOING]]
+priority:: [[P1]]
+parent::
+venue:: [[SANER]]
+leader::
+todoist::
+progress:: {{renderer :todomaster}}
+
+ - This is a resubmission of the ICSME paper.
+ - [ICSME rebuttal - Google Docs](https://docs.google.com/document/d/1Z0AaBhnIO4rWDycA4UUZ2xlwyM0tctta_9yKTB7oJMM/edit?tab=t.0)
+ - [Large Language Models Effectiveness on Performance Bug Detection - ICSME - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/67a0d5a98e5fd171cc9fd539)
+ - TODO Additional results
+ - TODO More performance bugs
+ - TODO Qualitative analysis
\ No newline at end of file
diff --git a/pages/PAPERS___AUSE-Metagente.md b/pages/PAPERS___AUSE-Metagente.md
index 92b6d04b..b5204e07 100644
--- a/pages/PAPERS___AUSE-Metagente.md
+++ b/pages/PAPERS___AUSE-Metagente.md
@@ -4,7 +4,7 @@ full-title::
external-links::
year:: 2025
date-start::
-status:: [[DOING]]
+status:: [[SUBMITTED]]
venue:: [[AUSE]]
priority:: [[P1]]
parent::
@@ -12,7 +12,7 @@ leader::
todoist::
progress:: {{renderer :todomaster}}
-- This is the extensio of the FSE paper on METAGENTE
+- This is the extension of the FSE paper on METAGENTE
- Another student from Phuong can be interested to join and work on the technical part of the paper.
- Phuong is leading this. Probably I have to pay OpenAPI and then understand how to get reimburse!
-
\ No newline at end of file
diff --git a/pages/PAPERS___EMSE-D-25-00044-IMRAN.md b/pages/PAPERS___EMSE-D-25-00044-IMRAN.md
index c38f29b9..d69a25b7 100644
--- a/pages/PAPERS___EMSE-D-25-00044-IMRAN.md
+++ b/pages/PAPERS___EMSE-D-25-00044-IMRAN.md
@@ -3,7 +3,7 @@ date:: [[18-03-2025]] - 10:36
full-title:: Is Code Coverage of Performance Tests Related to Source Code Features? An Empirical Study on Open-Source Systems
external-links:: [Empirical Study - JSS Extended Article - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/65d4d96d4bb4aa9bd7250228)
year:: 2025
-status:: [[UNDER-REVISION]]
+status:: [[ACCEPTED]]
venue:: [[EMSE]]
priority:: [[P1]]
file::  https://docs.google.com/document/d/18Irk80Z0UlLFJ_e3kIdb8T3MUcyfXb4gw7ePcVsro6U/edit?tab=t.0
diff --git a/pages/PAPERS___IST-DeepMig.md b/pages/PAPERS___IST-DeepMig.md
index 1716032c..d5b4b01c 100644
--- a/pages/PAPERS___IST-DeepMig.md
+++ b/pages/PAPERS___IST-DeepMig.md
@@ -4,7 +4,7 @@ full-title:: DeepMig: a transformer-based approach to support coupled library an
external-links::
todoist:: https://app.todoist.com/showTask?id=7660428852
year:: 2024
-status:: [[SUBMITTED]]
+status:: [[ACCEPTED]]
venue:: [[IST]]
priority:: [[P4]]
parent:: [[PAPERS/DEEPMIG-JSS-RESUBMISSION]]
diff --git a/pages/PAPERS___Journal-Green-Paper.md b/pages/PAPERS___Journal-Green-Paper.md
new file mode 100644
index 00000000..ed2b6e7e
--- /dev/null
+++ b/pages/PAPERS___Journal-Green-Paper.md
@@ -0,0 +1,189 @@
+type:: [[JournalPaper]]
+date:: [[31-07-2025]] - 18:12
+full-title::
+external-links::
+todoist::
+year::
+date-start::
+status:: [[DOING]]
+venue::
+priority:: [[P1]]
+parent::
+leader::
+todoist::
+progress:: {{renderer :todomaster}}
+
+- Tasks
+ - DONE Finire sezione 3 (riprendere da 3.2.2)
+id:: 688b9643-5053-49b9-b9ed-b559e7bf653c
+ - TODO Sezione 4
+ - TODO Sezione 5
+ - TODO Sezione 6
+ - TODO Fare passaggio tramite chat per fare un check su eventuali ulteriori aspetti da approfondire
+ - TODO Gestire la definizione di "prompt customization"
+ - TODO Vedere questione statistical tests
+ -
+-
+- ### ⚠️ **Areas That May Undermine Convincingness**
+ - **Link between energy usage and output size needs stronger evidence.**
+
+ The claim that *“energy consumption is strictly related to the size of the output”* is intuitive but not rigorously validated in the current text. Including a more detailed correlation analysis (scatter plots, regression, or correlation coefficient) would strengthen this conclusion.
+ - **Codellama’s negative performance is not fully explained.**
+
+ The paper observes that Codellama consumes more energy and is verbose, but the reasons for this behavior (architecture differences, tokenization strategy, fine-tuning objectives) are only hinted at.
+
+ 🔹 Suggestion: add a discussion grounded in literature or empirical reasoning to explain why code-specific tuning might lead to over-generation.
+ - **Impact of text format on summarization is under-discussed.**
+
+ While results show that text format has “less pronounced” effects, the explanation remains superficial. Providing hypotheses (e.g., tokenizer normalization, model robustness to markup) or a short qualitative analysis would make this claim more convincing.
+ - **Comparative discussion with related work is weak.**
+
+ The related work section mentions several studies but does not explicitly compare your findings to them.
+
+ 🔹 Suggestion: add a paragraph discussing how your results confirm, contradict, or extend previous findings (e.g., Adamska et al. on answer length, Husom et al. on correlation between response size and energy use).
+ - **Lack of statistical analysis.**
+
+ While average values are presented, no statistical test (e.g., t-test, ANOVA) is reported to support claims of significant differences between configurations. Even a basic significance analysis would increase persuasiveness.
+ - **Some methodological choices need more justification.**
+
+ For example:
+ - Why were exactly 1,000 snippets and 343 README files selected?
+ - Why was a 5-second pause deemed sufficient, despite acknowledging standard practice is longer?
+
+ These decisions should be reframed as conscious design choices, not constraints.
+- ### **Weaknesses & Concerns**
+ collapsed:: true
+ - **Lack of statistical significance analysis**:
+
+ Differences in energy consumption and accuracy are reported as percentages or observations, but without statistical testing it is unclear whether they are significant.
+ - **Partial explanation of key findings**:
+ - The strong correlation between output size and energy consumption is asserted but not quantitatively validated.
+ - Codellama’s verbosity and inefficiency are observed but not fully explained.
+ - **Under-discussed text summarization results**:
+
+ The impact of input format is deemed minor, but no deeper reasoning or hypotheses are offered.
+ - **Limited comparative discussion with prior work**:
+
+ Related work is cited, but the paper does not explicitly position its findings relative to existing literature (e.g., whether your observations about answer length confirming Adamska et al.’s results).
+ - **Methodological decisions appear ad-hoc**:
+
+ The justification for dataset sizes, input limits, and pause intervals could be better framed as design decisions rather than constraints.
+
+ ---
+- ### **Overall Evaluation**
+ collapsed:: true
+ - **Technical Soundness:** ★★★★☆ (solid but needs more statistical rigor and stronger causal explanations)
+ - **Persuasiveness:** ★★★☆☆ (results are interesting but require deeper contextualization and comparison with literature)
+ - **Contribution:** ★★★★☆ (original and significant in the context of Green AI and SE)
+
+ ---
+- ## 2. **Concrete Suggestions to Strengthen the Paper**
+ collapsed:: true
+ - ### **A. Strengthen Explanations**
+ - Provide a **quantitative correlation** between output length and energy consumption (scatter plot + Pearson correlation).
+ - Explain Codellama’s behavior with references to differences in training data, tokenization, or decoding strategies.
+ - ### **B. Expand Comparative Discussion**
+ - Explicitly compare findings to **Adamska et al.** (on output length) and **Husom et al.** (on response-energy correlation).
+ - Mention whether your findings align or contradict prior observations on prompt engineering’s energy effects.
+ - ### **C. Improve the Text Summarization Analysis**
+ - Discuss **why** different formats (HTML vs. Markdown vs. Plain Text) had little impact—e.g., tokenization robustness, model pretraining exposure.
+ - Add qualitative examples of how outputs differ across formats.
+ - ### **D. Add Minimal Statistical Support**
+ - Perform at least a **paired t-test or ANOVA** to confirm differences between configurations are significant.
+ - Report **confidence intervals** alongside averages.
+ - ### **E. Reframe Methodological Constraints**
+ - Reword justifications like *“forced to opt for”* or *“for the sake of time”* to *“we selected a 5-second interval based on empirical trade-offs between experimental feasibility and consistency with prior studies”*.
+ - ### **F. Strengthen Conclusions**
+ - End with a clear, strong statement:
+ *“Our findings demonstrate that prompt design is a non-trivial factor in the energy efficiency of LLMs. This opens the way for energy-aware prompt engineering strategies, bridging Green AI and software engineering practices.”*
+- ## **A. Additional Paragraph for the Discussion Section**
+ - **Impact of Output Size, Model Behavior, and Format Robustness**
+
+ Our experimental results suggest a strong link between the size of the generated output and the observed energy consumption. This observation aligns with prior findings by Adamska et al. [1] and Husom et al. [15], who also reported a direct relationship between output verbosity and energy demand during inference. However, unlike previous works, our study demonstrates that this effect is modulated by prompt engineering: configurations that constrain generation length (e.g., $C_{c2}$) not only reduce energy consumption but also improve accuracy for Llama 3.1. Interestingly, Codellama—despite being specialized for code—exhibited systematically higher consumption and verbosity, likely due to its decoding strategies and fine-tuning objectives, which encourage detailed explanations. Further investigation is required to determine whether this behavior is inherent to code-specific LLMs or an artifact of the model architecture. Regarding text summarization, we observed that input format variations (Markdown, HTML, plain text) had negligible influence on energy usage and predictive performance. This may be explained by the tokenizer’s robustness to markup structures and the model’s exposure to diverse formats during pretraining. These findings highlight that prompt engineering can be an effective lever for controlling energy consumption, while input formatting has a more marginal role.
+- ## **B. Strengthened Conclusion**
+ - **6 Conclusion and Future Directions**
+
+ This paper empirically investigated how prompt engineering techniques and input text formats influence the energy consumption and predictive performance of large language models in two representative software engineering tasks: code completion and text summarization. By systematically comparing different prompt configurations across Llama 3.1 and Codellama, we demonstrated that prompt design significantly impacts both energy efficiency and output accuracy. In particular, configurations that explicitly guide the model through custom tags while constraining verbosity (e.g., $C_{c2}$) resulted in up to a twofold reduction in energy usage and substantial accuracy improvements for Llama 3.1. Conversely, Codellama, despite its code specialization, was found to be energy-inefficient and prone to verbose outputs, raising new questions about the trade-offs of domain-specific fine-tuning. For text summarization, our findings indicate that input format variations (plain text, Markdown, HTML) have minimal impact on energy consumption, suggesting that model tokenization and pretraining mitigate format-related differences.
+
+ Overall, our results provide actionable evidence that **prompt engineering is a key factor in shaping the energy footprint of LLMs**. This insight opens the door to **energy-aware prompting strategies** that align with the principles of Green AI and sustainable software engineering. Future work will explore the integration of prompt optimization with dynamic energy monitoring, the extension of our analysis to larger and more diverse models, and the design of automated frameworks to balance performance and environmental costs.
+-
+- **Threats to Validity**
+ - Our study is subject to several threats to validity that warrant discussion. **Internal validity** may be affected by the hardware configuration and monitoring tools. To mitigate this, all experiments were executed on the same high-performance server, and energy measurements were consistently collected using CodeCarbon, a widely adopted and validated tool. We also performed five repetitions per configuration to minimize random fluctuations. **Construct validity** relates to whether our metrics truly capture the energy-performance trade-off. While CodeCarbon provides reliable estimates of GPU energy usage, future work could incorporate direct hardware-level measurements (e.g., using NVIDIA-smi logging) for finer granularity. **External validity** concerns the generalizability of our findings. We evaluated only two LLMs and two tasks; while they are representative of common SE scenarios, extending the analysis to larger models, diverse tasks, and alternative architectures is necessary to confirm the observed trends. Finally, **conclusion validity** may be impacted by the absence of formal statistical testing. Although we observed clear differences across configurations, future work should integrate statistical analyses (e.g., t-tests, ANOVA) to rigorously assess the significance of these differences. Despite these limitations, the consistent patterns observed across multiple metrics and repetitions strengthen our confidence in the reported findings.
+- ## ✅ **Final Journal-Readiness Checklist**
+ - ### DONE **1. Title & Abstract**
+id:: 688cc320-7b06-4594-943f-f302da78f521
+ - **Change the title** (current one duplicates the GREEN paper).
+
+ 👉 Example: *"Energy-Aware Prompt Engineering for Large Language Models: An Empirical Study on Software Engineering Tasks"*
+ - **Enrich abstract** with a sentence highlighting the novelty (*“This is the first work systematically linking prompt design to energy consumption in LLM-based software engineering tasks.”*).
+
+ ---
+ - ### **2. References**
+ - Add **recent citations** for:
+ - LLMs in code completion (e.g., Copilot, Codex studies).
+ - Energy-aware AI and Green AI.
+ - Specific LLMs mentioned (Gemma, Mistral, Vicuna).
+ - Complete missing citations flagged as **DAVIDE ▶Reference◀**.
+
+ ---
+ - ### **3. Methodology**
+ - Reframe **dataset size and pause interval** as design decisions, not constraints.
+ - Clarify ambiguous text in the **Prompt Creator** subsection.
+ - Add reference to **Table 1** when configurations are introduced.
+
+ ---
+ - ### **4. Results & Analysis**
+ - Provide **correlation analysis** between **output length** and **energy consumption** (supports main claim).
+ - Discuss **why Codellama over-generates** with reference to architecture/training.
+ - Expand discussion on **text summarization robustness** to input formats.
+
+ ---
+ - ### **5. Threats to Validity**
+ - Include the refined paragraph I provided.
+ - Explicitly mention potential **bias from hardware configuration** and **use of one monitoring tool**.
+
+ ---
+ - ### **6. Discussion & Conclusion**
+ - Include the **additional paragraph** and **strengthened conclusion**.
+ - Add a sentence on **practical implications** (e.g., guidelines for energy-efficient prompting).
+
+ ---
+- ## ✅ **Draft: Statistical Tests to Include**
+
+ To make your analysis statistically rigorous without overcomplicating, here is a **minimal set of tests** you can integrate:
+
+ ---
+ - ### **1. Paired t-tests**
+ - **Purpose:** Compare energy consumption (and accuracy) between two configurations (e.g., $C_{c0}$ vs. $C_{c2}$).
+ - **Application:**
+ - For each task and PET (zero/one/few-shot), run a paired t-test on the five repetitions per configuration.
+ - **Reporting:**
+ - Report p-values and effect sizes (Cohen’s d).
+ - Example statement:
+
+ *“The energy consumption of $C_{c2}$ was significantly lower than $C_{c0}$ for the code completion task (t(4) = 5.67, p < 0.01, d = 1.9).”*
+
+ ---
+ - ### **2. One-way ANOVA**
+ - **Purpose:** Compare **all configurations ($C_{c0}$–$C_{c4}$)** simultaneously to determine if differences are statistically significant.
+ - **Application:**
+ - Run separately for Llama 3.1 and Codellama, for both energy and accuracy metrics.
+ - **Reporting:**
+ - Include F-statistic and p-value.
+ - Example:
+
+ *“ANOVA revealed a significant effect of prompt configuration on energy consumption for Llama 3.1 (F(4,20) = 12.4, p < 0.001). Post-hoc Tukey tests showed that $C_{c2}$ and $C_{c3}$ consumed significantly less energy than $C_{c0}$ and $C_{c4}$.”*
+
+ ---
+ - ### **3. Correlation (Pearson’s r)**
+ - **Purpose:** Quantify relationship between **output length** and **energy consumption**.
+ - **Application:**
+ - Compute Pearson correlation per model and per task.
+ - **Reporting:**
+ - Example:
+
+ *“Output length was strongly correlated with energy consumption for Codellama (r = 0.89, p < 0.001), confirming that verbosity is a primary driver of higher energy usage.”*
+
+ ---
+ - ### **4. Optional: Boxplots/Violin Plots**
+ - Complement statistical tests with **visualizations** to show distribution differences.
\ No newline at end of file
diff --git a/pages/PAPERS___MT-ENERGY-CONSUMPTION.md b/pages/PAPERS___MT-ENERGY-CONSUMPTION.md
index 03356955..0b4b0216 100644
--- a/pages/PAPERS___MT-ENERGY-CONSUMPTION.md
+++ b/pages/PAPERS___MT-ENERGY-CONSUMPTION.md
@@ -5,7 +5,7 @@ external-links:: https://join.skype.com/Dayvow7ShpvA
todoist:: https://todoist.com/showTask?id=7182359800
year:: 2024
date-start:: [[30-08-2023]]
-status:: [[SUBMITTED]]
+status:: [[ACCEPTED]]
venue:: [[SPE]]
priority:: [[P4]]
deadline-submission:: [[25-05-2024]]
diff --git a/pages/PAPERS___REVISION Jesus-Software-and-Systems-Modeling-SOSYM-23-00004436.md b/pages/PAPERS___REVISION Jesus-Software-and-Systems-Modeling-SOSYM-23-00004436.md
index 4218225b..21e61dad 100644
--- a/pages/PAPERS___REVISION Jesus-Software-and-Systems-Modeling-SOSYM-23-00004436.md
+++ b/pages/PAPERS___REVISION Jesus-Software-and-Systems-Modeling-SOSYM-23-00004436.md
@@ -1,6 +1,6 @@
type:: [[JournalPaper]]
date:: [[05-12-2023]] - 11:11
-full-title:: ModelXGlue: A benchmarking framework for ML tools in MDE
+full-title:: ModelXGlue: A [[benchmarking framework]] for ML tools in MDE
date-submitted:: [[12-01-2024]]
external-links:: [Sosym-Systematic benchmarking of ML tools for MDE Rebuttal Letter - Google Docs](https://docs.google.com/document/d/1RFsbbjeR-htBlLiy2tKJkieOkSLAzurF3mpSgPebWyI/edit)
todoist:: https://app.todoist.com/showTask?id=7343907990
diff --git a/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING.md b/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING.md
index aed5262d..8cca8b4f 100644
--- a/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING.md
+++ b/pages/PAPERS___SOSYM-MODELS-EXTENSION-ML-BENCHMARKING.md
@@ -94,7 +94,7 @@ priority:: [[P4]]
- 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.
+ - 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]]
\ No newline at end of file
diff --git a/pages/PAPERS___SOSYM-Vallecillo.md b/pages/PAPERS___SOSYM-Vallecillo.md
index 98a9ca36..141f914e 100644
--- a/pages/PAPERS___SOSYM-Vallecillo.md
+++ b/pages/PAPERS___SOSYM-Vallecillo.md
@@ -7,7 +7,7 @@ chat:: https://join.skype.com/CB4p2ilyjeie
todoist:: https://app.todoist.com/showTask?id=7395026165
year:: 2024
date-submitted:: [[22-03-2024]]
-status:: [[SUBMITTED]]
+status:: [[ACCEPTED]]
venue:: [[SOSYM]]
priority:: [[P1]]
leader:: [[people/davide]]
@@ -97,7 +97,7 @@ progress:: {{renderer :todomaster}}
- Propose guidelines and best practices for the responsible integration of LLMs in MDE workflows, considering the potential impact on stakeholders.
- **Benchmarking and Evaluation Metrics:**
collapsed:: true
- - Establish standardized benchmarks for evaluating the performance of LLMs in MDE tasks, considering factors such as model accuracy, efficiency, and adaptability.
+ - Establish standardized [[benchmarks]] for evaluating the performance of LLMs in MDE tasks, considering factors such as model accuracy, efficiency, and adaptability.
- Define metrics that go beyond traditional evaluation criteria to capture the unique challenges and requirements of MDE scenarios.
- **Scalability and Resource Efficiency:**
collapsed:: true
diff --git a/pages/PAPERS___Software-ecosystem-book-chapter.md b/pages/PAPERS___Software-ecosystem-book-chapter.md
index 9a585c06..caae3558 100644
--- a/pages/PAPERS___Software-ecosystem-book-chapter.md
+++ b/pages/PAPERS___Software-ecosystem-book-chapter.md
@@ -3,7 +3,7 @@ external-links::
todoist:: https://todoist.com/showTask?id=5492418790
year:: 2023
date-start:: [[05-09-2022]]
-people:: [[people/alfonso]] [[people/PhuongNguyen]]
+people:: [[people/AlfonsoPierantonio]] [[people/PhuongNguyen]]
status:: [[ACCEPTED]]
- **30 #PAPERS MERGED WITH 20 MANUALLY SELECTED**
diff --git a/pages/PRIN 2020 - scadenza rendicontazione finale.md b/pages/PRIN 2020 - scadenza rendicontazione finale.md
new file mode 100644
index 00000000..24ca6aae
--- /dev/null
+++ b/pages/PRIN 2020 - scadenza rendicontazione finale.md
@@ -0,0 +1,2 @@
+- Tabelle stipendiali - [Ateneo - Trattamento economico](https://www.univaq.it/section.php?id=2249)
+-
\ No newline at end of file
diff --git a/pages/PRIN.md b/pages/PRIN.md
index e69de29b..484a8a85 100644
--- a/pages/PRIN.md
+++ b/pages/PRIN.md
@@ -0,0 +1,8 @@
+- Al [[03-12-2025]] lo stato dei progetti PRIN attualmente attivi o in via di chiusura sono i seguenti:
+ - [[PROJECTS/PRIN-EMELIOT]]
+ - Abbiamo chiuso per gli inizi di Agosto. Occorre fare una rendicontazione integrativa (fine Febbraio) con la quale giustificare il residuo di **16.437,54**
+ - Su questo posso far gravare la parte mancante di ASE
+ - [[PROJECTS/PRIN-PNRR-2022-FRINGE]]
+ -
+ - [[PROJECTS/PRIN-2022-TREXSE]]
+ -
\ No newline at end of file
diff --git a/pages/PROJECTS___MOSAICO.md b/pages/PROJECTS___MOSAICO.md
new file mode 100644
index 00000000..34758e53
--- /dev/null
+++ b/pages/PROJECTS___MOSAICO.md
@@ -0,0 +1,250 @@
+filters:: {}
+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}}
+alias:: MOSAICO
+
+ - ## Meetings
+ - {{query (and [[meeting]] [[PROJECTS/MOSAICO]])}}
+ query-table:: true
+ query-properties:: [:page :progress]
+ query-sort-by:: page
+ query-sort-desc:: false
+ - ## 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)
\ No newline at end of file
diff --git a/pages/PROJECTS___MOSAICO___WP2.md b/pages/PROJECTS___MOSAICO___WP2.md
index 0d922d1e..5d755a0a 100644
--- a/pages/PROJECTS___MOSAICO___WP2.md
+++ b/pages/PROJECTS___MOSAICO___WP2.md
@@ -7,78 +7,60 @@
date:: [[04-07-2025]] - 11:44
duration::
-
-- ### Notes sul deliverable D2.1
- - Da considerare anche il prompt?
- - {{renderer :mermaid_68668a24-ce43-472e-b787-a53b895f7c75, 3}}
- collapsed:: true
- - ```mermaid
- classDiagram
- class Agent {
- id
- name
- version
- owner
- }
-
- class Capability {
- domain
- taskType
- supportedLanguages
- inputFormats
- outputFormats
- }
-
- class PerformanceKPI {
- accuracy
- latencyMs
- resourceConsumption
- robustnessMetrics
- }
-
- class Governance {
- license
- dataResidency
- GDPRCompliance
- auditTrailAvailable
- }
-
- class FairnessEthics {
- biasDetected
- fairnessConstraints
- explanationCapabilities
- }
-
- class RuntimeEnvironment {
- runtime
- requiredLibraries
- hardwareAcceleration
- }
-
- class Provenance {
- trainingDataSources
- modelLineage
- lastUpdated
- }
-
- class ContactInfo {
- maintainerEmail
- documentationUrl
- }
-
- class AgentRepository {
- <>
- }
-
- Agent --> Capability : has
- Agent --> PerformanceKPI : provides
- Agent --> Governance
- Agent --> FairnessEthics
- Agent --> RuntimeEnvironment
- Agent --> Provenance
- Agent --> ContactInfo
- AgentRepository --> Agent : manages
-
-
- ```
- - Agents should be also marked if they keep information or not for IP purposes.
- -
\ No newline at end of file
+- ### [[Deliverable D2.1]]
+ - What we're envisioning is that the protocol exposes the information about the agents in a given agent server, which then can be easily consumed by your repository (for indexing). This is the same approach as A2A agent cards and as MCP tool descriptions. A single agent server only lists its own agents: the MOSAICO repository is the one that actually indexes all the agents available across all the servers.
+ - I think this is needed, because I cannot imagine people going to a web interface and filling in form field after form field with all this information. A2A precisely does this so that they could do a type of web crawler that would go through "well-known URIs" ([http://host/.well-known/agent.json](http://host/.well-known/agent.json)) to find agents at will. In fact, I suspect your repository may need to do exactly this.
+ - ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAhIg5c2AAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
+ -
+- ### [[MENTORING/TESISTI]]
+ collapsed:: true
+ - **Marco Giarrusso**
+ - **Mariama Celi S. de Oliveira**
+ - Rehearsal presentation
+ - what about adding an explanatory workflow to show an orchestration of agents with Dify or AutoGPT?
+ - Collaborative optimization task--> explain
+ - Just motivate the choices for the configurations slide 8
+ - Slide 9
+ - too small
+ - Slide 13
+ - What do you mean with Each pipeline runs only once?
+ -
+ - **Motunrayo Ibiyo**
+ - Rehearsal presentation
+ collapsed:: true
+ - Mention MOSAICO at the beginning where we are studying the usage of LLM-based multi agent systems to support software engineering tasks
+ - Very fast, reduce the content and speak slowly. Too many slides!!! You should cut half of them!!!
+ - It's easy to get lost in the details
+ - Slides 4
+ - What are the limitations of existing approaches?
+ - Slide 6
+ - with-out (typo)
+ - Slide 7
+ - Put the updated reference
+ - Slide 8
+ - highlight the different components while presenting (one by one)
+ - Slide 10
+ - 
+ - what does it mean?
+ - Slide 11
+ - Many typos
+ - a file in the package is...
+ - Slide 12
+ - 
+ - too many things
+ - Slide 14
+ - 
+ - It's too much,
+ - It's more beneficial presenting some explanatory examples instead of all these numbers, in line with what you have with slide 16.
+ -
+ - TOOLS evaluated
+ - Qualitative + Quantitative
+ - AutoGen
+ - AutoGPT
+ - Dify
+ - SemanticKernel
+ - LlamaIndex
+ - Heystack
+ - Qualitative
+ - Those from Motunrayoi
+ -
\ No newline at end of file
diff --git a/pages/PROJECTS___PRIN-EMELIOT.md b/pages/PROJECTS___PRIN-EMELIOT.md
index 761073bc..fe28f174 100644
--- a/pages/PROJECTS___PRIN-EMELIOT.md
+++ b/pages/PROJECTS___PRIN-EMELIOT.md
@@ -5,7 +5,6 @@ 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
diff --git a/pages/PROJECTS___SERICS-MATTERS.md b/pages/PROJECTS___SERICS-MATTERS.md
index b638022f..18aa722d 100644
--- a/pages/PROJECTS___SERICS-MATTERS.md
+++ b/pages/PROJECTS___SERICS-MATTERS.md
@@ -5,4 +5,5 @@ project-type:: [[PNRR]]
todoist:: https://app.todoist.com/app/project/projects-serics-matters-6V5mM2qQrvfwwJ38
nextcloud:: https://vps.diruscio.org/nc/index.php/f/2745428
- - 
\ No newline at end of file
+- [MATTERS - Documenti - Deliverable Finale - Tutti i documenti](https://univaq.sharepoint.com/sites/MATTERS/Documenti%20condivisi/Forms/AllItems.aspx?id=%2Fsites%2FMATTERS%2FDocumenti%20condivisi%2FGeneral%2FDeliverable%20Finale&p=true&ct=1758007475995&or=OWA%2DNT%2DMail&cid=d859652e%2Dff3e%2D27ae%2D184d%2Dd16effd6efb2&ga=1)
+- 
\ No newline at end of file
diff --git a/pages/Planner.md b/pages/Planner.md
index b0bc7e82..87f910ac 100644
--- a/pages/Planner.md
+++ b/pages/Planner.md
@@ -1,5 +1,46 @@
icon:: 📅
+- ## FOCUS
+ - [[REVIEWS]]
+id:: 6938231c-2456-474f-b723-54a14064632f
+ :LOGBOOK:
+ CLOCK: [2025-12-16 Tue 09:55:28]--[2025-12-16 Tue 09:55:29] => 00:00:01
+ :END:
+ - [[PAPERS/2025-IEEESOFTWARE-AGENTIC-SI]]
+ - [[ADMIN/MISSIONI]]
+ - ---
+ - [[PROJECTS/MOSAICO]]
+ - [[Benchmarking framework]]
+ - [[Benchmarks]] #PROJECTS/MOSAICO #P1
+ - [[CV Empower]]
+ - [[Linee guida afferenza Collegio dottorato ICT]] #todoist-task #SERVICES/PHDICT
+ - ---
+- ## Chiusura estiva
+ - DONE Gestione Bando studenti Palestina
+ id:: 68874dfe-bd98-41ce-8216-3663c2439bc2
+ - DONE [[PAPERS/AUSE-Metagente]] [[P1]]
+ id:: 68946800-1268-43e8-8971-44b6c0d2ce9c
+ - DONE [[PAPERS/TOSEM2025-TESORO]]
+ id:: 6884f13b-60da-48da-abe9-8a522cde5d29
+ :LOGBOOK:
+ CLOCK: [2025-08-07 Thu 09:11:29]--[2025-08-07 Thu 09:11:29] => 00:00:00
+ :END:
+ - ### **Possibile periodi di break**
+ - Mezza giornata: dal 4 Agosto all'8, dal 18 al 26 Agosto
+ background-color:: yellow
+ - DONE [[Invited talk at LLMA4SE Summer School website]] [[P1]]
+ id:: 68946800-a5fe-4f75-af64-8b2509daf7fd
+ :LOGBOOK:
+ CLOCK: [2025-08-31 Sun 11:52:02]--[2025-09-02 Tue 10:06:45] => 46:14:43
+ :END:
+ - Stacco completo: dall'11 al 17
+ background-color:: green
+ -
+- ## PRESSIONI
+ - ACQUISTO CASA PESCARA
+ id:: 6895c9da-572c-48e2-8d71-80a61f7e0c81
+ - Gestione questione corsignani
+ - Affitto capannone
- [[GOALS-TODOIST]]
- **WEEK BLOCKING (First Semester)**
id:: 650b4d6e-0015-446a-bc62-629af3621638
@@ -26,8 +67,11 @@ icon:: 📅
- 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
\ No newline at end of file
+ - TODO [[PAPERS]]
+ - TODO Sistemare rendicontazione PRIN
+ :LOGBOOK:
+ CLOCK: [2025-09-06 Sat 10:50:27]
+ :END:
+ - TODO [[SERVICES/PHDICT]]
+ -
+-
\ No newline at end of file
diff --git a/pages/Preparazione Intervento PINKAMP.md b/pages/Preparazione Intervento PINKAMP.md
index 9cb35b47..73b4087f 100644
--- a/pages/Preparazione Intervento PINKAMP.md
+++ b/pages/Preparazione Intervento PINKAMP.md
@@ -5,7 +5,7 @@ progress:: {{renderer :todomaster}}
- ## Notes
- DONE Recuperare qualche esempio di software engineering and AI
- DONE Sviluppare qualche esempio con VSCode e ChatGPT
-id:: 68584ec9-3c3f-4ea3-8e31-cb2e6f469bef
+ id:: 68584ec9-3c3f-4ea3-8e31-cb2e6f469bef
- Mostrare qualche challenge
- DONE Introdurre all'AI facendo qualche esempio di sistema di raccomandazione ?
- Esempio di Netflix o di scelta di un ristorante
@@ -168,7 +168,8 @@ id:: 68584ec9-3c3f-4ea3-8e31-cb2e6f469bef
CLOCK: [2025-06-17 Tue 16:45:19]--[2025-06-17 Tue 16:45:20] => 00:00:01
:END:
- Forse qualcosa da prendere dalla tesi di Marco Giarrusso
- - DONE [[18-08-2025]] Raffinamento contenuti e grafica delle slides
+ - DONE [[18-06-2025]] Raffinamento contenuti e grafica delle slides
+ id:: 68584ec9-a2a1-4685-b559-141f96bb61f2
- ## Struttura intervento di circa 2 ore
- Dalle 11:15 alle 13:00
- 
diff --git a/pages/Presentazione dei documenti di monitoraggio.md b/pages/Presentazione dei documenti di monitoraggio.md
index cbc26bb4..6d8bbe10 100644
--- a/pages/Presentazione dei documenti di monitoraggio.md
+++ b/pages/Presentazione dei documenti di monitoraggio.md
@@ -1,4 +1,4 @@
-tags:: #todoist-task, [[SERVICES/PHDICT]]
+tags:: #todoist-task, [[SERVICES/PHDICT]] , #AVA3
date:: [[16-06-2025]] - 16:49
progress:: {{renderer :todomaster}}
@@ -34,5 +34,5 @@ progress:: {{renderer :todomaster}}
- DONE Finalizzare dati terza sezione
- DONE Scrivere commenti terza sezione
- DONE Condividere scheda per il [[07-07-2025]]
-id:: 686e52cd-0003-4306-936b-f4756724680f
+ id:: 686e52cd-0003-4306-936b-f4756724680f
- DONE Ricevere commenti per il [[10-07-2025]]
\ No newline at end of file
diff --git a/pages/Progettazione Offerta Formativa.md b/pages/Progettazione Offerta Formativa.md
index a188e39a..9f0f2e11 100644
--- a/pages/Progettazione Offerta Formativa.md
+++ b/pages/Progettazione Offerta Formativa.md
@@ -2,9 +2,19 @@ progress:: {{renderer :todomaster}}
tags:: [[SERVICES/PHDICT]] #todoist-task
- TODO Guardare corsi di altri dottorati ICT
+- DONE Fare un Excel con tutti i corsi distinguendo quelli dell'anno scorso (quindi quelli che hanno dato conferma), quelli nuovi già passati in collegio, quelli nuovi che devono essere approvati dal Collegio e messi nell'excel solo come riferimento.
+ id:: 68dc3033-9770-4fd0-b2ea-87025e587615
- DONE Fare una call? chiedendo alle singole aree di proporre dei corsi
-id:: 68372640-5f76-4640-8b49-7d79dc1e8c7a
-- Possiamo coinvolgere i reference group chiedendo alle aree di esprimersi con delle proposte di corso.
-- Il [[30-05-2025]] mi ha contattato Antinsica dicendomi che e' interessata a fornire un corso di 12 crediti su fairness. La cosa la si fa solo se poi c'e' il riconoscimento della docenza a Giordano. !?!?!?!?
+ id:: 68372640-5f76-4640-8b49-7d79dc1e8c7a
+- DONE Possiamo coinvolgere i reference group chiedendo alle aree di esprimersi con delle proposte di corso.
+ id:: 68584ec9-e757-4b59-adae-09b0616243c2
+- DONE Il [[30-05-2025]] mi ha contattato Antinsica dicendomi che e' interessata a fornire un corso di 12 crediti su fairness. La cosa la si fa solo se poi c'e' il riconoscimento della docenza a Giordano. !?!?!?!?
+ id:: 68584ec9-a8ef-4798-a441-6ee772d7e22b
collapsed:: true
- - Trovo questa proposta del tutto fuori luogo. Conferma quello che penso circa la considerazione che hanno del dottorato molti dei colleghi. E' visto come uno strumento utile per il raggiungimento di scopi propri al di la di quello che dovrebbe essere l'obiettivo: essere funzionale alla causo, allo scopo principe, il bene dei nostri studenti! #thoughts
\ No newline at end of file
+ :LOGBOOK:
+ CLOCK: [2025-10-02 Thu 14:19:51]--[2025-10-02 Thu 14:19:52] => 00:00:01
+ :END:
+ - Trovo questa proposta del tutto fuori luogo. Conferma quello che penso circa la considerazione che hanno del dottorato molti dei colleghi. E' visto come uno strumento utile per il raggiungimento di scopi propri al di la di quello che dovrebbe essere l'obiettivo: essere funzionale alla causo, allo scopo principe, il bene dei nostri studenti! #thoughts
+- TODO Necessario gestire perfezionamento lingua Inglese
+ - Livello C1 (anche Salerno richiede questo livello)
+ - Vedere se c'e' traccia in qualche vecchio verbale
\ No newline at end of file
diff --git a/pages/READ.md b/pages/READ.md
new file mode 100644
index 00000000..e7e218a1
--- /dev/null
+++ b/pages/READ.md
@@ -0,0 +1 @@
+icon:: ✅
diff --git a/pages/REVIEWS.md b/pages/REVIEWS.md
index 0b1d1c7e..dcba81f6 100644
--- a/pages/REVIEWS.md
+++ b/pages/REVIEWS.md
@@ -11,7 +11,6 @@ icon:: 📜
- Purple -> Key sentence / aspect in the document.
background-color:: purple
- ## REVIEWS - DOING
- collapsed:: true
- {{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
@@ -20,9 +19,9 @@ icon:: 📜
- ## REVIEWS - DONE
- {{query (and (property :status [[DONE]]) (property :type [[REVIEWS]]) (not [[templates]]) (property :year "2025"))}}
query-sort-by:: venue
- query-properties:: [:venue :full-title :date-submitted :year]
- query-sort-desc:: false
query-table:: true
+ query-sort-desc:: false
+ query-properties:: [:venue :full-title]
- ## OTHER REVIEWS
collapsed:: true
- DONE [[JSSOFTWARE-D-22-00977_reviewer.pdf]]
diff --git a/pages/Rapporti con il GSSI.md b/pages/Rapporti con il GSSI.md
new file mode 100644
index 00000000..de7071f7
--- /dev/null
+++ b/pages/Rapporti con il GSSI.md
@@ -0,0 +1,118 @@
+tags:: #todoist-task, [[SERVICES/PHDICT]]
+date:: [[24-08-2025]] - 18:56
+progress:: {{renderer :todomaster}}
+
+ - ### **Tasks**
+ - TODO Vedere convenzione Univaq GSSI che ha ritrovato Fortunato/Elena
+ - 
+ - ### **Notes**
+ - #### **Canali formali** per collaborazioni sui dottorati in Italia (DM 226/2021)
+ - **Dottorato consorziato**
+ - Previsto dall’art. 3, c. 2, DM 226/2021.
+ - Più enti (università, enti di ricerca, scuole superiori) istituiscono **un unico corso di dottorato**, con un coordinatore e un collegio unico.
+ - Lo statuto/regolamento di ciascun partner deve essere allineato.
+ - Il titolo finale è **unico** con i loghi di tutti gli enti consorziati.
+ - Richiede accreditamento ANVUR/MUR del dottorato come “consortile”.
+ - 👉 **Esempio tipico:** Dottorato nazionale in Intelligenza Artificiale (coordinato da CNR, con decine di sedi).
+ - **Dottorato in convenzione**
+ - Sempre art. 3, DM 226/2021.
+ - L’ente titolare del dottorato (es. UNIVAQ) stipula **una convenzione** con un altro ente (es. GSSI).
+ - Si possono cofinanziare borse, condividere corsi, laboratori, co-supervisioni.
+ - Il titolo è dell’ente titolare (non congiunto), ma nel diploma può essere riportata la convenzione.
+ - 👉 **Molto più leggero** da attivare, spesso usato come primo passo.
+ - **Accordi di co-tutela internazionale**
+ - Per singoli studenti.
+ - Si stipula un accordo ad hoc fra UNIVAQ e un altro ateneo (anche italiano, anche se più raro), che prevede doppia supervisione, periodi minimi di permanenza in entrambe le sedi e rilascio di **doppio titolo di dottore di ricerca**.
+ - 👉 È utile per avviare collaborazioni mirate senza cambiare la governance complessiva del corso.
+ - **Accordi quadro / MoU**
+ - Non sono previsti dal DM 226, ma servono come **cornice politica**.
+ - Sono protocolli d’intesa firmati dai Rettori per dichiarare la volontà di collaborare su didattica, ricerca e dottorato.
+ - Da soli non attivano nulla, ma permettono poi di formalizzare convenzioni specifiche su borse e corsi.
+ - #### Per instaurare possibili collaborazioni tra Univaq e GSSI è possibile svolgere le seguenti **azioni**
+ - TODO Mappare le aree di sinergia
+ - ICT a L’Aquila → MDE, SE, AI multi-agente, sistemi complessi.
+ - GSSI → Computer Science (algoritmi, HPC, AI, network science, quantum, ecc.).
+ - Individuare 2-3 **temi trasversali forti** (es. AI per software engineering, HPC per agent-based systems, quantum-inspired computing, fairness & AI) e proponi un “focus congiunto”
+ - TODO Capire quale canale formale perseguire tra i seguenti disponibili:
+ - **Dottorati consorziati / in convenzione** (art. 3 DM 226/2021): si può creare un percorso congiunto con GSSI mantenendo autonomia dei singoli corsi, ma con borse e corsi condivisi.
+ - **Accordi quadro / convenzioni specifiche**: più semplice e veloce, per avviare subito co-supervisioni e attività comuni.
+ - **Co-tutela di dottorato**: attivabile per singoli studenti (titolo con doppio sigillo L’Aquila–GSSI). Può essere un buon primo passo.
+ - **Dottorati nazionali tematici**: se in futuro il MUR lancia bandi tematici (AI, Quantum, Cybersecurity), un consorzio UNIVAQ+GSSI sarebbe competitivo.
+ - Confronto tra **Accordi quadro/convenzioni specifiche** e **Dottorato consorziato**
+ - | Aspetto | **Convenzione** | **Consorzio (dottorato consorziato)** |
+ | ---- |
+ | **Base normativa** | Art. 3, c. 2, DM 226/2021 | Art. 3, c. 2, DM 226/2021 |
+ | **Governance** | Rimane al dottorato titolare (es. UNIVAQ). L’altro ente partecipa con alcuni membri nel collegio. | Collegio e coordinamento condivisi tra tutti i partner. |
+ | **Titolo finale** | Titolo di UNIVAQ, con menzione della convenzione con GSSI. | Titolo unico con loghi di UNIVAQ + GSSI (e altri se presenti).|
+ | **Burocrazia** | Bassa: basta una convenzione approvata dai Senati Accademici. Non richiede nuovo accreditamento ANVUR. | Alta: serve domanda di accreditamento ANVUR/MUR del dottorato come consorziato. Più lenta e complessa. |
+ | **Tempistiche** | 3–6 mesi (realistico se c’è volontà politica e supporto amministrativo). | 1–2 anni (per preparare documenti, revisione ANVUR, nuovo accreditamento). |
+ | **Flessibilità** | Alta: si possono cofinanziare borse singole, aprire corsi incrociati, attivare co-supervisioni. | Bassa: una volta accreditato, il programma è più rigido (governance, regolamenti comuni, ecc.). |
+ | **Visibilità esterna** | Limitata: il brand rimane soprattutto di UNIVAQ. | Molto alta: “PhD UNIVAQ–GSSI” ha forte attrattiva internazionale. |
+ | **Rischio politico** | Minimo: se non funziona, basta non rinnovare la convenzione. | Alto: se non funziona, si compromette la reputazione del corso e servono modifiche statutarie. |
+ | **Esempi tipici** | Singole borse cofinanziate con enti di ricerca o aziende. | Dottorato in Data Science (Pisa–Sant’Anna–Normale–IMT–CNR). [Dottorato congiunto in Data Science IMT](https://www.imtlucca.it/phd/joint-phd-programs) |
+ - In merito alla riga flessibilità, è importante chiarire quanto segue:
+ - **Flessibilità: cosa cambia **con** e **senza convenzione****
+ - | Aspetto | Senza convenzione | Con convenzione |
+ | ---- | ---- | ---- |
+ | **Co-supervisori esterni** | Possibili, ma senza ruolo formale. Delibere singole ogni volta. | Riconosciuti ufficialmente nel collegio (anche come membri aggregati). Processo standardizzato. |
+ | **Corsi incrociati** | Possibili, ma ogni studente deve chiedere riconoscimento singolo. | Automatici: i corsi dell’altro ente valgono di default come parte dell’offerta formativa. |
+ | **Borse cofinanziate** | Più difficile: servono atti singoli di cofinanziamento. | Regolamentate: la convenzione prevede già come cofinanziare borse. |
+ | **Mobilità studenti** | Possibile, ma gestita con autorizzazioni individuali (missioni, nulla osta). | Prevista e semplificata come parte della convenzione. |
+ | **Visibilità esterna** | Collaborazioni meno chiare, percepite come “episodiche”. | La collaborazione è “brandizzata”: appare nei bandi, nei titoli di borse, nelle call internazionali. |
+ - TODO Identificare azioni pratiche immediate
+ - **Workshop congiunto**: “GSSI–UNIVAQ Joint Workshop on AI & Software Systems” (a L’Aquila, possibilmente in sede neutrale) con talk dei rispettivi PhD students. Serve come “prova generale” e segnale politico.
+ - **Proposta di convenzione** - se il workshop ha esito positivo, far predisporre dal Settore Dottorati un **accordo di collaborazione formale** con GSSI (es. borse in cofinanziamento, corsi aperti, accesso ai laboratori).
+ - **Co-supervisioni pilota** - Identificare 1–2 studenti UNIVAQ e 1–2 del GSSI che possano avere relatori incrociati. Questo crea legami concreti e prepara il terreno ad accordi più strutturati.
+ - #### Sintesi operativa
+ - **Per partire subito**: attiva una **convenzione UNIVAQ–GSSI** su alcune borse ICT → rapido, a basso rischio, gestibile politicamente.
+ - **Se la collaborazione funziona** (entro 2–3 anni): valutare la creazione di un **dottorato consorziato UNIVAQ–GSSI in ICT/AI/Complex Systems**, che avrebbe una forte attrattiva internazionale (come Pisa–Sant’Anna).
+ - [Data Science | Scuola Superiore Sant'Anna](https://www.santannapisa.it/it/formazione/data-science)
+ - [DataSciencePHD.eu |](https://datasciencephd.eu/)
+ - {{embed ((68584ed7-9cdb-439a-a339-9a61640037df))}}
+ - #### 🗓️ Roadmap 12 mesi – Collaborazione UNIVAQ–GSSI (PhD ICT & CS)
+ - ##### 🔹 0–3 mesi: Avvio “soft”
+ background-color:: green
+ - **Co-supervisioni pilota**
+ - Identificare 1–2 dottorandi UNIVAQ ICT che abbiano un tema sinergico con GSSI.
+ background-color:: purple
+ - Collegio ICT delibera la nomina di 1–2 co-supervisori GSSI (senza bisogno di convenzione).
+ - Obiettivo: casi concreti subito attivi.
+ - **Corsi incrociati ad hoc**
+ - Informale: studenti ICT seguono 1 corso PhD al GSSI (es. AI, Algorithms, HPC).
+ - Collegio ICT riconosce i CFU caso per caso.
+ - Obiettivo: prima esperienza di “cross training”.
+ - **Workshop inaugurale (Q1 2026)**
+ - Evento congiunto UNIVAQ–GSSI con presentazione delle ricerche dei dottorandi.
+ - Output: visibilità interna ed esterna (anche comunicazione stampa locale/nazionale).
+ - ##### 🔹 4–6 mesi: Strutturazione
+ - **Valutazione interna**
+ - Feedback dai dottorandi su co-supervisioni e corsi incrociati.
+ background-color:: purple
+ - Identificare benefici e ostacoli burocratici.
+ - **Definizione di una bozza di convenzione quadro**
+ - Redatta dal Settore Dottorati UNIVAQ con input GSSI.
+ - Contenuti minimi:
+ - regole su co-supervisioni,
+ - riconoscimento automatico corsi,
+ - possibilità di cofinanziamento borse,
+ background-color:: purple
+ - mobilità studenti.
+ - **Presentazione al Rettore UNIVAQ e al Direttore GSSI**
+ - Documento breve (2–3 pagine) con vantaggi reciproci.
+ - ##### 🔹 7–12 mesi: Formalizzazione
+ - **Firma convenzione quadro UNIVAQ–GSSI**
+ - Approvazione nei rispettivi Senati Accademici/Consigli.
+ - Entrata in vigore dal ciclo successivo (XLI).
+ - **Borse cofinanziate**
+ - Proposta di almeno 1–2 borse ICT in cofinanziamento UNIVAQ–GSSI da bandire congiuntamente.
+ - Possibilità di sfruttare FSE+ Abruzzo o bandi nazionali (DM351/352).
+ - **Stabilizzazione corsi incrociati**
+ - I corsi GSSI diventano parte riconosciuta dell’offerta ICT UNIVAQ e viceversa.
+ background-color:: purple
+ - Riduzione drastica della burocrazia per gli studenti.
+ - ##### 🔹 Output dopo 12 mesi
+ - 2–3 dottorandi ICT già con co-supervisori GSSI.
+ - 1–2 corsi incrociati attivi con riconoscimento automatico.
+ - 1 workshop congiunto già organizzato → ottima visibilità.
+ - Convenzione quadro firmata e operativa.
+ - Preparazione a medio termine (24–36 mesi) di un **PhD consorziato UNIVAQ–GSSI** (opzione se la collaborazione funziona).
\ No newline at end of file
diff --git a/pages/Reading.md b/pages/Reading.md
new file mode 100644
index 00000000..7a459627
--- /dev/null
+++ b/pages/Reading.md
@@ -0,0 +1 @@
+icon:: 📚
diff --git a/pages/Rendicontazione EMELIOT.md b/pages/Rendicontazione EMELIOT.md
new file mode 100644
index 00000000..18aa44d4
--- /dev/null
+++ b/pages/Rendicontazione EMELIOT.md
@@ -0,0 +1,11 @@
+tags:: #todoist-task, [[PROJECTS/PRIN-EMELIOT]], [[ADMIN]]
+date:: [[18-07-2025]] - 09:02
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ -
+ - ### Notes
+ - Link al report: [Rendicontazione Scientifica - Google Docs](https://docs.google.com/document/d/1bOgGJKC6lVFvNZTR4d5mEdgoIvfkoVCaxX1RKhiuGv0/edit?tab=t.0)
+ - Link a lista pubblicazioni Univaq su EMELIOT: [EMELIOT papers - Google Docs](https://docs.google.com/document/d/1OhCZzcwPIFyf6hJCuW0tG-Ekyq25RnlYhyIJsaH0wZk/edit?tab=t.0)
+- {:height 324, :width 876}
+ - Chiuso il 25/07/2025 15:03
\ No newline at end of file
diff --git a/pages/Resources.md b/pages/Resources.md
new file mode 100644
index 00000000..ebe8a782
--- /dev/null
+++ b/pages/Resources.md
@@ -0,0 +1,4 @@
+filters:: {}
+icon:: 🗂️
+
+-
\ No newline at end of file
diff --git a/pages/Richardson-ECONOMIA E FINANZA LE BASI.md b/pages/Richardson-ECONOMIA E FINANZA LE BASI.md
index 93a3d7a1..f2ec1599 100644
--- a/pages/Richardson-ECONOMIA E FINANZA LE BASI.md
+++ b/pages/Richardson-ECONOMIA E FINANZA LE BASI.md
@@ -11,138 +11,139 @@ kindle-sync:
bookImageUrl: 'https://m.media-amazon.com/images/I/81GqZieo3RL._SY160.jpg'
highlightsCount: 39
---
-# ECONOMIA E FINANZA: LE BASI
-## Metadata
-* Author: [George Richardson](https://www.amazon.comundefined)
-* ASIN: B08BHTHT4B
-* Reference: https://www.amazon.com/dp/B08BHTHT4B
-* [Kindle link](kindle://book?action=open&asin=B08BHTHT4B)
-## Highlights
-Оggi indiса quеll’аrеа in сui hаnnо luоgо lа рrоduziоnе, lа distribuziоnе е il соmmеrсiо, соsì соmе il соnsumо, di bеni е sеrvizi. — location: [119](kindle://book?action=open&asin=B08BHTHT4B&location=119) ^ref-12083
-
----
-vеnditа, асquistо, distribuziоnе е рrоduziоnе di bеni е sеrvizi, viеnе, реrсiò, dеttа есоnоmiа — location: [122](kindle://book?action=open&asin=B08BHTHT4B&location=122) ^ref-4429
-
----
-Рrimа dеllа nаsсitа dеllа соsiddеttа есоnоmiа “сlаssiса”, nеssunо еrа in grаdо di sераrаrе lе dесisiоni есоnоmiсhе dа quеllе роlitiсhе. — location: [128](kindle://book?action=open&asin=B08BHTHT4B&location=128) ^ref-21086
-
----
-l’intеrеssе individuаlе роssа аnсhе аndаrе а соinсidеrе соn l’intеrеssе gеnеrаlе. — location: [132](kindle://book?action=open&asin=B08BHTHT4B&location=132) ^ref-37547
-
----
-L’аttività есоnоmiса riсhiеdе соsì risоrsе, сhе роssоnо еssеrе quеllе nаturаli, соmе il реtrоliо о il gаs, mа аnсhе оgni аltrа mаtеriа рrimа nесеssаriа а рrоdurrе un dеtеrminаtо bеnе; — location: [137](kindle://book?action=open&asin=B08BHTHT4B&location=137) ^ref-14857
-
----
-Nеl соrsо dеllа stоriа dеll’uоmо, il раssаggiо dа unа mаtеriа еnеrgеtiса аll’аltrа è sеmрrе stаtо ассоmраgnаtо dа un mаssiссiо imрiеgо tесnоlоgiсо, tесnоlоgiа сhе è divеnutа sеmрrе рiù соmрlеssа. — location: [147](kindle://book?action=open&asin=B08BHTHT4B&location=147) ^ref-9878
-
----
-аnсоrа mоlti sоnо i nullаtеnеnti о i раеsi sfruttаti а lоrо sсарitо е а vаntаggiо sоltаntо di аltri. — location: [162](kindle://book?action=open&asin=B08BHTHT4B&location=162) ^ref-61717
-
----
-Lа mеrсе hа lа сарасità di сrеsсеrе а dismisurа, mа nоn lе соndiziоni есоnоmiсhе dеll’individuо аll’intеrnо dеllа sосiеtà — location: [165](kindle://book?action=open&asin=B08BHTHT4B&location=165) ^ref-23377
-
----
-рrоduziоnе, fоrzе рrоduttivе е lе соndiziоni di sсаmbiо, а gеnеrаrе sреssо disаgi е mаlсоntеntо trа lа ророlаziоnе. — location: [168](kindle://book?action=open&asin=B08BHTHT4B&location=168) ^ref-17025
-
----
-vаlоrе есоnоmiсо dеl tеrritоriо è un аsреttо mоltо imроrtаntе реr соmрrеndеrе gli sсеnаri есоnоmiсi nеllа lоrо tоtаlità, sорrаttuttо nеl mоndо glоbаlizzаtо. — location: [173](kindle://book?action=open&asin=B08BHTHT4B&location=173) ^ref-55426
-
----
-Аll’есоnоmiа si аggiungе un suо strumеntо imрrеsсindibilе, оvvеrо lа finаnzа — location: [194](kindle://book?action=open&asin=B08BHTHT4B&location=194) ^ref-2505
-
----
-gеstiоnе dеl dаnаrо”: — location: [196](kindle://book?action=open&asin=B08BHTHT4B&location=196) ^ref-10862
-
----
-mоdаlità di асquistо dеl dаnаrо, оvvеrо il сарitаlе, е dеl соmе quеstо viеnе sреsо оd invеstitо. — location: [198](kindle://book?action=open&asin=B08BHTHT4B&location=198) ^ref-50250
-
----
-Lа finаnzа si рuò suddividеrе in trе mасrосаtеgоriе: lа finаnzа d’imрrеsа, lа рiаnifiсаziоnе раtrimоniаlе, е lа finаnzа рubbliса — location: [200](kindle://book?action=open&asin=B08BHTHT4B&location=200) ^ref-21085
-
-#cards
-
----
-gоld stаndаrd. — location: [249](kindle://book?action=open&asin=B08BHTHT4B&location=249) ^ref-33962
-
----
-gоld еxсhаngе stаndаrd, оvvеrо il саmbiо vаlutа, соnvеrtibilе in bаsе аllе risеrvе аurее di сiаsсunо Stаtо, — location: [261](kindle://book?action=open&asin=B08BHTHT4B&location=261) ^ref-47111
-
----
-sistеmа fluttuаntе dеi саmbi flеssibili. — location: [274](kindle://book?action=open&asin=B08BHTHT4B&location=274) ^ref-15912
-
----
-I саmbi flеssibili sоnо quеlli сhе соnоsсiаmо nоi оggi, è un sistеmа intеrnаziоnаlе сhе si bаsа su lеggi di mеrсаtо. Nоn sоnо, quindi, gli Stаti sоvrаni а dеtеrminаrе il рrеzzо dеllа lоrо vаlutа in bаsе аllе lоrо sресifiсhе risеrvе аurее, mа il mеrсаtо stеssо. — location: [275](kindle://book?action=open&asin=B08BHTHT4B&location=275) ^ref-55936
-
-#cards
-
----
-роssibilità сhе il suо рrеzzо роssа diminuirе а саusа dеi tаssi. — location: [406](kindle://book?action=open&asin=B08BHTHT4B&location=406) ^ref-2061
-
----
-i titоli а tаssо fissо sоnо рiù sоggеtti а risсhiо di quеlli vаriаbili, реrсhé роtrеbbе diminuirе il lоrо рrеzzо еssеndо il lоrо tаssо d’intеrеssе соstаntе е nоn vаriаbilе. — location: [407](kindle://book?action=open&asin=B08BHTHT4B&location=407) ^ref-24957
-
----
-risсhiо liquidità, аndiаmо а rifеrirсi аllа diffiсоltà сhе si inсоntrаnо аl mоmеntо dеllа vеnditа dеll’оbbligаziоnе, quаndо quеstа vuоlе еssеrе rарidаmеntе сеdutа, riеntrаndо dеl guаdаgnо sеnzа раrtiсоlаri реrditе. — location: [442](kindle://book?action=open&asin=B08BHTHT4B&location=442) ^ref-56720
-
----
-titоli nоn quоtаti, — location: [445](kindle://book?action=open&asin=B08BHTHT4B&location=445) ^ref-35546
-
----
-Il рrоfilо di risсhiо viеnе sеmрrе indiсаtо соn un numеrо, сhе рuò аndаrе dаl minimо di 1 аl mаssimо di 7. — location: [504](kindle://book?action=open&asin=B08BHTHT4B&location=504) ^ref-45243
-
----
-рrоdоtti dеrivаti dеvоnо il lоrо nоmе dаll'аndаmеntо dеl vаlоrе di unа аttività in рrоsреttivа futurа, сiоè di рrеvisiоnе, оvvеrо сiò сhе si еvinсе dеrivа, dаtо un еvеntо оssеrvаbilе оggеttivаmеntе. — location: [523](kindle://book?action=open&asin=B08BHTHT4B&location=523) ^ref-531
-
----
-nоn раrtiсоlаrе а nеssunо Stаtо sоvrаnо, mа сhе еsistе su Intеrnеt: è virtuаlе е nоn si rifеrisсе а nеssun vаlоrе di bеnе mаtеriаlе, — location: [671](kindle://book?action=open&asin=B08BHTHT4B&location=671) ^ref-43494
-
----
-сriрtоvаlutе: vаlutе digitаli, е quindi nоn fisiсhе, mа virtuаli, е quindi nоn si trоvаnо in fоrmа саrtасеа, соmе lе bаnсоnоtе о lе mоnеtе аllе quаli siаmо аbituаti, mа si trоvаnо sоltаntо su Intеrnеt in fоrmаtо digitаlе. — location: [706](kindle://book?action=open&asin=B08BHTHT4B&location=706) ^ref-47519
-
-#cards
-
----
-Sаrdеx, сriрtоvаlutа соmрlеmеntаrе аll’Еurо е соn раri vаlоrе (1 Sаrdеx = 1 еurо), nоn соnvеrtibilе, di sоstеgnо аll’есоnоmiа dеl tеrritоriо е аl lаvоrо fiduсiаriо, — location: [726](kindle://book?action=open&asin=B08BHTHT4B&location=726) ^ref-39281
-
----
-blосkсhаin, оvvеrо unа strutturа di dаti соndivisа еd immutаbilе. — location: [781](kindle://book?action=open&asin=B08BHTHT4B&location=781) ^ref-45816
-
-#cards
-
----
-hаsh dеl blоссо рrесеdеntе, — location: [801](kindle://book?action=open&asin=B08BHTHT4B&location=801) ^ref-46775
-
----
-L’uniса viа реrсоrribilе раrе, реrсiò, саmbiаrе i раrаdigmi di mеrсаtо еd есоnоmiсi, раrtеndо dаll’аdоziоnе di nuоvi stili di vitа рiù sоstеnibili е di соnsumо diffеrеntе. — location: [967](kindle://book?action=open&asin=B08BHTHT4B&location=967) ^ref-33086
-
----
-Lа сirсulаr есоnоmy è stаtа invеntаtа рrорriо in funziоnе dеllа grееn есоnоmy. È un suо аsреttо раrtiсоlаrе, infаtti, е рrеvеdе сhе аll’intеrnо dеl сiсlо рrоduttivо niеntе vеngа sрrесаtо, mа роssibilmеntе riutilizzаtо. — location: [991](kindle://book?action=open&asin=B08BHTHT4B&location=991) ^ref-17459
-
----
-in un mеrсаtо реrfеttаmеntе соnсоrrеnziаlе, lе sсеltе di finаnziаmеntо dеll’ imрrеsа sоnо irrilеvаnti реr сарirе il vаlоrе dеll’ imрrеsа stеssа. — location: [1085](kindle://book?action=open&asin=B08BHTHT4B&location=1085) ^ref-48027
-
----
-l'аltо livеllо di sсоlаrizzаziоnе е lа riссhеzzа di рrоvеniеnzа dеllе fаmigliе gеnеrа dеllе аsреttаtivе рiuttоstо аltе, — location: [1147](kindle://book?action=open&asin=B08BHTHT4B&location=1147) ^ref-17642
-
----
-I соnsigli сhе роssiаmо suggеrirе, risреttо аllа rеаltà сhе viviаmо оggi, сi rimаndаnо аllа tеоriа dеl сiсlо di vitа finаnziаriо. Сеrсhiаmо di еssеrе аttivi lаvоrаtivаmеntе, ассеttаndо аnсhе lаvоri сhе nоn riеntrаnо nеllе nоstrе сарасità, in mоdо tаlе dа gеnеrаrе rеdditо сhе рuò еssеrе роi risраrmiаtо, rifоrmuliаmо lе nоstrе аsреttаtivе, ridimеnsiоniаmо lе nоstrе sреsе, tеniаmо sеmрrе а mеntе l'аndаmеntо dеllе nоstrе finаnzе е dеi nоstri bisоgni, sviluррiаmо unа сulturа есоnоmiса е finаnziаriа bеn rаdiсаtа in nоi. — location: [1157](kindle://book?action=open&asin=B08BHTHT4B&location=1157) ^ref-17790
-
-#STAR
-
----
-Lа рiаnifiсаziоnе di un invеstimеntо è соrrеttа quаndо nаsсе а раrtirе dаllе рrорriе еsigеnzе. — location: [1175](kindle://book?action=open&asin=B08BHTHT4B&location=1175) ^ref-30456
-
----
-роssibilе risраrmiо; — location: [1183](kindle://book?action=open&asin=B08BHTHT4B&location=1183) ^ref-64584
-
----
-Quеllо сhе оссоrrе соnsidеrаrе, durаntе l'аnаlisi е lа рiаnifiсаziоnе finаnziаriа, è il rеndimеntо minimо еd il risсhiо mаssimо. — location: [1205](kindle://book?action=open&asin=B08BHTHT4B&location=1205) ^ref-55288
-
----
-Il suо vаlоrе sаlе nеi mоmеnti di сrisi еd è stаbilе nеi mоmеnti di сrеsсitа. — location: [1729](kindle://book?action=open&asin=B08BHTHT4B&location=1729) ^ref-38371
-
----
-Mоnеtаriо е di liquidità, dоvе l'invеstimеntо è а brеvе tеrminе, соn lо sсоро di bеnеfiсiаrе di tаssi d'intеrеssе suреriоri, аvеndо lа nесеssità di ассеdеrvi nеl brеvе реriоdо; — location: [1948](kindle://book?action=open&asin=B08BHTHT4B&location=1948) ^ref-43924
-
----
+- # ECONOMIA E FINANZA: LE BASI
+- ## Metadata
+ * Author: [George Richardson](https://www.amazon.comundefined)
+ * ASIN: B08BHTHT4B
+ * Reference: https://www.amazon.com/dp/B08BHTHT4B
+ * [Kindle link](kindle://book?action=open&asin=B08BHTHT4B)
+- ## Highlights
+ id:: 695003ab-29ec-47b3-8126-80c1c2b7742f
+ Оggi indiса quеll’аrеа in сui hаnnо luоgо lа рrоduziоnе, lа distribuziоnе е il соmmеrсiо, соsì соmе il соnsumо, di bеni е sеrvizi. — location: [119](kindle://book?action=open&asin=B08BHTHT4B&location=119) ^ref-12083
+
+ ---
+ vеnditа, асquistо, distribuziоnе е рrоduziоnе di bеni е sеrvizi, viеnе, реrсiò, dеttа есоnоmiа — location: [122](kindle://book?action=open&asin=B08BHTHT4B&location=122) ^ref-4429
+
+ ---
+ Рrimа dеllа nаsсitа dеllа соsiddеttа есоnоmiа “сlаssiса”, nеssunо еrа in grаdо di sераrаrе lе dесisiоni есоnоmiсhе dа quеllе роlitiсhе. — location: [128](kindle://book?action=open&asin=B08BHTHT4B&location=128) ^ref-21086
+
+ ---
+ l’intеrеssе individuаlе роssа аnсhе аndаrе а соinсidеrе соn l’intеrеssе gеnеrаlе. — location: [132](kindle://book?action=open&asin=B08BHTHT4B&location=132) ^ref-37547
+
+ ---
+ L’аttività есоnоmiса riсhiеdе соsì risоrsе, сhе роssоnо еssеrе quеllе nаturаli, соmе il реtrоliо о il gаs, mа аnсhе оgni аltrа mаtеriа рrimа nесеssаriа а рrоdurrе un dеtеrminаtо bеnе; — location: [137](kindle://book?action=open&asin=B08BHTHT4B&location=137) ^ref-14857
+
+ ---
+ Nеl соrsо dеllа stоriа dеll’uоmо, il раssаggiо dа unа mаtеriа еnеrgеtiса аll’аltrа è sеmрrе stаtо ассоmраgnаtо dа un mаssiссiо imрiеgо tесnоlоgiсо, tесnоlоgiа сhе è divеnutа sеmрrе рiù соmрlеssа. — location: [147](kindle://book?action=open&asin=B08BHTHT4B&location=147) ^ref-9878
+
+ ---
+ аnсоrа mоlti sоnо i nullаtеnеnti о i раеsi sfruttаti а lоrо sсарitо е а vаntаggiо sоltаntо di аltri. — location: [162](kindle://book?action=open&asin=B08BHTHT4B&location=162) ^ref-61717
+
+ ---
+ Lа mеrсе hа lа сарасità di сrеsсеrе а dismisurа, mа nоn lе соndiziоni есоnоmiсhе dеll’individuо аll’intеrnо dеllа sосiеtà — location: [165](kindle://book?action=open&asin=B08BHTHT4B&location=165) ^ref-23377
+
+ ---
+ рrоduziоnе, fоrzе рrоduttivе е lе соndiziоni di sсаmbiо, а gеnеrаrе sреssо disаgi е mаlсоntеntо trа lа ророlаziоnе. — location: [168](kindle://book?action=open&asin=B08BHTHT4B&location=168) ^ref-17025
+
+ ---
+ vаlоrе есоnоmiсо dеl tеrritоriо è un аsреttо mоltо imроrtаntе реr соmрrеndеrе gli sсеnаri есоnоmiсi nеllа lоrо tоtаlità, sорrаttuttо nеl mоndо glоbаlizzаtо. — location: [173](kindle://book?action=open&asin=B08BHTHT4B&location=173) ^ref-55426
+
+ ---
+ Аll’есоnоmiа si аggiungе un suо strumеntо imрrеsсindibilе, оvvеrо lа finаnzа — location: [194](kindle://book?action=open&asin=B08BHTHT4B&location=194) ^ref-2505
+
+ ---
+ gеstiоnе dеl dаnаrо”: — location: [196](kindle://book?action=open&asin=B08BHTHT4B&location=196) ^ref-10862
+
+ ---
+ mоdаlità di асquistо dеl dаnаrо, оvvеrо il сарitаlе, е dеl соmе quеstо viеnе sреsо оd invеstitо. — location: [198](kindle://book?action=open&asin=B08BHTHT4B&location=198) ^ref-50250
+
+ ---
+ Lа finаnzа si рuò suddividеrе in trе mасrосаtеgоriе: lа finаnzа d’imрrеsа, lа рiаnifiсаziоnе раtrimоniаlе, е lа finаnzа рubbliса — location: [200](kindle://book?action=open&asin=B08BHTHT4B&location=200) ^ref-21085
+
+ #card
+
+ ---
+ gоld stаndаrd. — location: [249](kindle://book?action=open&asin=B08BHTHT4B&location=249) ^ref-33962
+
+ ---
+ gоld еxсhаngе stаndаrd, оvvеrо il саmbiо vаlutа, соnvеrtibilе in bаsе аllе risеrvе аurее di сiаsсunо Stаtо, — location: [261](kindle://book?action=open&asin=B08BHTHT4B&location=261) ^ref-47111
+
+ ---
+ sistеmа fluttuаntе dеi саmbi flеssibili. — location: [274](kindle://book?action=open&asin=B08BHTHT4B&location=274) ^ref-15912
+
+ ---
+ I саmbi flеssibili sоnо quеlli сhе соnоsсiаmо nоi оggi, è un sistеmа intеrnаziоnаlе сhе si bаsа su lеggi di mеrсаtо. Nоn sоnо, quindi, gli Stаti sоvrаni а dеtеrminаrе il рrеzzо dеllа lоrо vаlutа in bаsе аllе lоrо sресifiсhе risеrvе аurее, mа il mеrсаtо stеssо. — location: [275](kindle://book?action=open&asin=B08BHTHT4B&location=275) ^ref-55936
+
+ #card
+
+ ---
+ роssibilità сhе il suо рrеzzо роssа diminuirе а саusа dеi tаssi. — location: [406](kindle://book?action=open&asin=B08BHTHT4B&location=406) ^ref-2061
+
+ ---
+ i titоli а tаssо fissо sоnо рiù sоggеtti а risсhiо di quеlli vаriаbili, реrсhé роtrеbbе diminuirе il lоrо рrеzzо еssеndо il lоrо tаssо d’intеrеssе соstаntе е nоn vаriаbilе. — location: [407](kindle://book?action=open&asin=B08BHTHT4B&location=407) ^ref-24957
+
+ ---
+ risсhiо liquidità, аndiаmо а rifеrirсi аllа diffiсоltà сhе si inсоntrаnо аl mоmеntо dеllа vеnditа dеll’оbbligаziоnе, quаndо quеstа vuоlе еssеrе rарidаmеntе сеdutа, riеntrаndо dеl guаdаgnо sеnzа раrtiсоlаri реrditе. — location: [442](kindle://book?action=open&asin=B08BHTHT4B&location=442) ^ref-56720
+
+ ---
+ titоli nоn quоtаti, — location: [445](kindle://book?action=open&asin=B08BHTHT4B&location=445) ^ref-35546
+
+ ---
+ Il рrоfilо di risсhiо viеnе sеmрrе indiсаtо соn un numеrо, сhе рuò аndаrе dаl minimо di 1 аl mаssimо di 7. — location: [504](kindle://book?action=open&asin=B08BHTHT4B&location=504) ^ref-45243
+
+ ---
+ рrоdоtti dеrivаti dеvоnо il lоrо nоmе dаll'аndаmеntо dеl vаlоrе di unа аttività in рrоsреttivа futurа, сiоè di рrеvisiоnе, оvvеrо сiò сhе si еvinсе dеrivа, dаtо un еvеntо оssеrvаbilе оggеttivаmеntе. — location: [523](kindle://book?action=open&asin=B08BHTHT4B&location=523) ^ref-531
+
+ ---
+ nоn раrtiсоlаrе а nеssunо Stаtо sоvrаnо, mа сhе еsistе su Intеrnеt: è virtuаlе е nоn si rifеrisсе а nеssun vаlоrе di bеnе mаtеriаlе, — location: [671](kindle://book?action=open&asin=B08BHTHT4B&location=671) ^ref-43494
+
+ ---
+ сriрtоvаlutе: vаlutе digitаli, е quindi nоn fisiсhе, mа virtuаli, е quindi nоn si trоvаnо in fоrmа саrtасеа, соmе lе bаnсоnоtе о lе mоnеtе аllе quаli siаmо аbituаti, mа si trоvаnо sоltаntо su Intеrnеt in fоrmаtо digitаlе. — location: [706](kindle://book?action=open&asin=B08BHTHT4B&location=706) ^ref-47519
+
+ #card
+
+ ---
+ Sаrdеx, сriрtоvаlutа соmрlеmеntаrе аll’Еurо е соn раri vаlоrе (1 Sаrdеx = 1 еurо), nоn соnvеrtibilе, di sоstеgnо аll’есоnоmiа dеl tеrritоriо е аl lаvоrо fiduсiаriо, — location: [726](kindle://book?action=open&asin=B08BHTHT4B&location=726) ^ref-39281
+
+ ---
+ blосkсhаin, оvvеrо unа strutturа di dаti соndivisа еd immutаbilе. — location: [781](kindle://book?action=open&asin=B08BHTHT4B&location=781) ^ref-45816
+
+ #card
+
+ ---
+ hаsh dеl blоссо рrесеdеntе, — location: [801](kindle://book?action=open&asin=B08BHTHT4B&location=801) ^ref-46775
+
+ ---
+ L’uniса viа реrсоrribilе раrе, реrсiò, саmbiаrе i раrаdigmi di mеrсаtо еd есоnоmiсi, раrtеndо dаll’аdоziоnе di nuоvi stili di vitа рiù sоstеnibili е di соnsumо diffеrеntе. — location: [967](kindle://book?action=open&asin=B08BHTHT4B&location=967) ^ref-33086
+
+ ---
+ Lа сirсulаr есоnоmy è stаtа invеntаtа рrорriо in funziоnе dеllа grееn есоnоmy. È un suо аsреttо раrtiсоlаrе, infаtti, е рrеvеdе сhе аll’intеrnо dеl сiсlо рrоduttivо niеntе vеngа sрrесаtо, mа роssibilmеntе riutilizzаtо. — location: [991](kindle://book?action=open&asin=B08BHTHT4B&location=991) ^ref-17459
+
+ ---
+ in un mеrсаtо реrfеttаmеntе соnсоrrеnziаlе, lе sсеltе di finаnziаmеntо dеll’ imрrеsа sоnо irrilеvаnti реr сарirе il vаlоrе dеll’ imрrеsа stеssа. — location: [1085](kindle://book?action=open&asin=B08BHTHT4B&location=1085) ^ref-48027
+
+ ---
+ l'аltо livеllо di sсоlаrizzаziоnе е lа riссhеzzа di рrоvеniеnzа dеllе fаmigliе gеnеrа dеllе аsреttаtivе рiuttоstо аltе, — location: [1147](kindle://book?action=open&asin=B08BHTHT4B&location=1147) ^ref-17642
+
+ ---
+ I соnsigli сhе роssiаmо suggеrirе, risреttо аllа rеаltà сhе viviаmо оggi, сi rimаndаnо аllа tеоriа dеl сiсlо di vitа finаnziаriо. Сеrсhiаmо di еssеrе аttivi lаvоrаtivаmеntе, ассеttаndо аnсhе lаvоri сhе nоn riеntrаnо nеllе nоstrе сарасità, in mоdо tаlе dа gеnеrаrе rеdditо сhе рuò еssеrе роi risраrmiаtо, rifоrmuliаmо lе nоstrе аsреttаtivе, ridimеnsiоniаmо lе nоstrе sреsе, tеniаmо sеmрrе а mеntе l'аndаmеntо dеllе nоstrе finаnzе е dеi nоstri bisоgni, sviluррiаmо unа сulturа есоnоmiса е finаnziаriа bеn rаdiсаtа in nоi. — location: [1157](kindle://book?action=open&asin=B08BHTHT4B&location=1157) ^ref-17790
+
+ #STAR
+
+ ---
+ Lа рiаnifiсаziоnе di un invеstimеntо è соrrеttа quаndо nаsсе а раrtirе dаllе рrорriе еsigеnzе. — location: [1175](kindle://book?action=open&asin=B08BHTHT4B&location=1175) ^ref-30456
+
+ ---
+ роssibilе risраrmiо; — location: [1183](kindle://book?action=open&asin=B08BHTHT4B&location=1183) ^ref-64584
+
+ ---
+ Quеllо сhе оссоrrе соnsidеrаrе, durаntе l'аnаlisi е lа рiаnifiсаziоnе finаnziаriа, è il rеndimеntо minimо еd il risсhiо mаssimо. — location: [1205](kindle://book?action=open&asin=B08BHTHT4B&location=1205) ^ref-55288
+
+ ---
+ Il suо vаlоrе sаlе nеi mоmеnti di сrisi еd è stаbilе nеi mоmеnti di сrеsсitа. — location: [1729](kindle://book?action=open&asin=B08BHTHT4B&location=1729) ^ref-38371
+
+ ---
+ Mоnеtаriо е di liquidità, dоvе l'invеstimеntо è а brеvе tеrminе, соn lо sсоро di bеnеfiсiаrе di tаssi d'intеrеssе suреriоri, аvеndо lа nесеssità di ассеdеrvi nеl brеvе реriоdо; — location: [1948](kindle://book?action=open&asin=B08BHTHT4B&location=1948) ^ref-43924
+
+ ---
\ No newline at end of file
diff --git a/pages/Richiesta compilazione tabella relativa alle attività didattiche svolte durante il triennio_Dottorato di Ricerca in Ingegneria e scienze dell'informazione_XXXVIII ciclo.md b/pages/Richiesta compilazione tabella relativa alle attività didattiche svolte durante il triennio_Dottorato di Ricerca in Ingegneria e scienze dell'informazione_XXXVIII ciclo.md
new file mode 100644
index 00000000..c9f82459
--- /dev/null
+++ b/pages/Richiesta compilazione tabella relativa alle attività didattiche svolte durante il triennio_Dottorato di Ricerca in Ingegneria e scienze dell'informazione_XXXVIII ciclo.md
@@ -0,0 +1,38 @@
+tags:: #todoist-task, [[SERVICES/PHDICT]]
+date:: [[22-09-2025]] - 11:16
+progress:: {{renderer :todomaster}}
+
+ - ### Tasks
+ collapsed:: true
+ -
+ - ### Notes
+ - Studenti coinvolti:
+ - ==Zeeshan Ali==
+ background-color:: green
+ - 
+ - ==Steve Azarsh Ratti==
+ - 
+ - ==Federico Di Menna==
+ - 
+ - ==Gennaro Zanfardino==
+ - 
+ - ==Alessandro Di Matteo==
+ - 
+ - ==Andrea D'Angelo==
+ - 
+ - ==Sahar Badri==
+ - 
+ - ==Isabella Presutti Gasbarro==
+ - 
+ - ==Giammarco Di Sciullo==
+ - 
+ - ==Pasquale Salucci==
+ - 
+ - ==Payel Patra==
+ - 
+ - ==Simone Angelucci==
+ - 
+ - ==Anjum Naveed==
+ - 
+ - ==Gizealew Alazie Dagnaw==
+ - 
\ No newline at end of file
diff --git a/pages/SERVICES___PHDICT.md b/pages/SERVICES___PHDICT.md
index d689faa7..5be4d398 100644
--- a/pages/SERVICES___PHDICT.md
+++ b/pages/SERVICES___PHDICT.md
@@ -2,7 +2,7 @@ icon:: 🎓
page-type:: [[SERVICES]]
progress:: {{renderer :todomaster}}
-- ## **Resources**
+- ## **RESOURCES**
- #.tabular
- **BOOX NOTES**
- 
@@ -74,16 +74,105 @@ progress:: {{renderer :todomaster}}
- [STARRED EMAILS](https://mail.google.com/mail/u/0/#search/label%3A%F0%9F%91%B7-work-services-%F0%9F%8E%93-services-phdict++is%3Astarred)
- [💸 BUDGET RELATED](https://mail.google.com/mail/u/0/#search/label%3A%F0%9F%92%B8-budget+label%3A%F0%9F%91%B7-WORK-Services-%F0%9F%8E%93-Services-PHDICT)
- [🗂 RESOURCES](https://mail.google.com/mail/u/0/#search/label%3A%F0%9F%97%82%EF%B8%8F-resource+label%3A%F0%9F%91%B7-WORK-Services-%F0%9F%8E%93-Services-PHDICT)
+- ## Azioni migliorative
+ - ### **A. Progettazione e offerta formativa**
+ - Consolidamento e applicazione sistematica della distinzione tra **Learning Activities** e **Training Activities**, formalizzata nelle CFU Recognition Rules.
+ - Aggiornamento annuale del catalogo dei corsi ad hoc dei due curricula, con attenzione all’equilibrio tra formazione metodologica, scientifica e professionalizzante.
+ - Rafforzamento delle **attività formative trasversali** (research methodology, scientific writing, project proposal design, project management, AI ethics).
+ - Maggiore integrazione di corsi offerti da **altri dottorati e istituzioni esterne**, con riconoscimento formale dei CFU.
+ - ### **B. Supervisione, ricerca e produzione scientifica**
+ - Rafforzamento del ruolo dei supervisori nel **monitoraggio della produzione scientifica** dei dottorandi lungo tutto il percorso.
+ - Promozione di una **disseminazione scientifica più continua e distribuita nel tempo**, coerente con l’evoluzione del lavoro di tesi.
+ - Maggiore supporto strutturato alla **costruzione di reti di collaborazione scientifica**, oltre all’iniziativa individuale di dottorandi e supervisori.
+ - Valorizzazione delle attività di ricerca applicata e delle collaborazioni con partner industriali e istituzionali.
+
+ ---
+ - ### **C. Tracciabilità, IRIS e qualità dei dati**
+ - Presidio strutturato dell’**inserimento dei prodotti della ricerca su IRIS**, con responsabilizzazione condivisa di dottorandi, supervisori e coautori.
+ - Sensibilizzazione su **attribuzione corretta, accessibilità e visibilità** dei prodotti scientifici nel rispetto delle politiche di Ateneo.
+ - Definizione di **linee guida comuni** per la raccolta e validazione dei dati su pubblicazioni, premi, partecipazioni a eventi scientifici.
+ - Rafforzamento del coordinamento con i **cinque Reference Group** per garantire uniformità e completezza dei dati di monitoraggio.
+
+ ---
+ - ### **D. Internazionalizzazione e mobilità**
+ - Miglioramento del **supporto scientifico durante i periodi all’estero**, con maggiore attenzione alla co-supervisione.
+ - Formalizzazione dei processi di monitoraggio e accompagnamento delle esperienze di mobilità internazionale.
+ - Rafforzamento del coinvolgimento di **docenti ed esperti internazionali** nelle attività formative e seminariali.
+
+ ---
+ - ### **E. Trasferimento tecnologico e proprietà intellettuale**
+ - Maggiore integrazione del **trasferimento tecnologico** nel progetto formativo del dottorato.
+ - Rafforzamento del raccordo con le strutture di Ateneo dedicate alla **proprietà intellettuale**, per la tutela dei risultati di ricerca quando applicabile.
+ - Sensibilizzazione su brevetti, prototipi, impatti applicativi e valorizzazione industriale dei risultati.
+
+ ---
+ - ### **F. Strutture, risorse e servizi**
+ - Aggiornamento progressivo delle **dotazioni informatiche** e delle postazioni di lavoro dei dottorandi.
+ - Consolidamento dell’accesso alle **infrastrutture di ricerca** (laboratori, HPC, risorse dipartimentali).
+ - Miglioramento della **trasparenza nell’allocazione e utilizzo delle risorse finanziarie** per ricerca e formazione.
+
+ ---
+ - ### **G. Trasparenza, comunicazione e visibilità**
+ - Rafforzamento del sito web del Dottorato come **punto di accesso unico** alle informazioni rilevanti.
+ - Miglioramento della visibilità dei risultati di ricerca, delle attività formative e delle opportunità internazionali.
+ - Consolidamento di iniziative di comunicazione istituzionale (PhD Welcome Day, eventi pubblici, attività divulgative).
+
+ ---
+ - ### **H. Sistema di Assicurazione della Qualità**
+ - Formalizzazione del **ciclo di AQ del Corso di Dottorato**, chiarendo fasi, momenti e responsabilità.
+ - Definizione di **momenti strutturati di confronto collegiale** sugli esiti delle SMA, delle rilevazioni di opinione e delle osservazioni NdV/PQA.
+ - Rafforzamento del coinvolgimento dei dottorandi nel sistema di AQ, anche tramite restituzione esplicita dei risultati.
+ - Migliore integrazione tra il sistema di AQ del Corso, del Dipartimento e dell’Ateneo.
+ - Evoluzione del sistema di AQ da strumento descrittivo a **leva di miglioramento continuo**, orientata all’azione e alla verifica degli esiti.
+- ## **SCADENZE**
+ - DONE Compilazione tabella relativa alle attività didattiche svolte durante il triennio_Dottorato di Ricerca in Ingegneria e scienze dell'informazione_XXXVIII ciclo
+ link:: [mail](https://outlook.office.com/mail/inbox/id/AAQkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwAQAIQhK7AJsUFJs8hFcqnt4sU%3D?nativeVersion=1.2025.806.300)
+ id:: 68bac2ea-d21f-45cb-b0b0-b7ba4bde8bf8
+ collapsed:: true
+ - i dottorandi trasmetteranno la tabella, e gli eventuali allegati, ai tutor entro il [[05-09-2025]];
+ - il coordinatore trasmetterà al nostro settore i file excel compilati ed approvati dai tutor entro il [[19-09-2025]] o, al più tardi, entro la fine del mese di settembre.
+ - DONE Selezione XLI ciclo posizione destinata a candidati palestinesi:
+ id:: 68bac2ea-edb2-4b78-b0eb-182a010233ec
+ collapsed:: true
+ - emanazione del bando di selezione al massimo entro il 5 agosto 2025:
+ - scadenza del termine per la presentazione delle domande fissata al massimo al 10 settembre 2025;
+ - nomina commissioni entro il 15 settembre 2025;
+ - prove selettive tra il 18 e il 26 settembre 2025;
+ - consegna degli atti concorsuali improrogabilmente entro il 30 settembre 2025;
+ - **pubblicazione dell’approvazione degli atti concorsuali entro il 6 ottobre 2025;**
+ - **immatricolazione dei vincitori entro il 21 ottobre 2025;**
+ - eventuali scorrimenti e ammissione ai corsi entro il 31 ottobre 2025;
+ - inizio dei corsi fissato al 1° novembre 2025.
+ - DONE Selezione XLI ciclo
+ file:: 
+ collapsed:: true
+ - emanazione del bando di selezione il 14 LUGLIO 2025:
+ - scadenza del termine per la presentazione delle domande 22 Agosto 2025;
+ - nomina commissioni entro il 28 Agosto 2025;
+ - prove selettive il 3 e il 9 settembre 2025;
+ - consegna degli atti concorsuali improrogabilmente entro il 15 settembre 2025;
+ - **pubblicazione dell’approvazione degli atti concorsuali entro il 25 settembre 2025;**
+ - **immatricolazione dei vincitori entro il 10 ottobre 2025;**
+ - eventuali scorrimenti e ammissione ai corsi entro il 31 ottobre 2025;
+ - inizio dei corsi fissato al 1° novembre 2025.
+- ## **TAGGED PAGES**
+ - {{query (property :tags [[SERVICES/PHDICT]])}}
+ query-table:: true
+ collapsed:: true
- ## **TASKS**
- collapsed:: true
- {{query (and [[SERVICES/PHDICT]] (task TODO DOING) (not [[GOALS-TODOIST]]) (not [[TODOIST-LOGSEQED]]))}}
query-table:: true
- query-sort-by:: page
+ query-sort-by:: block
query-sort-desc:: false
- ## **Gestione offerta formativa**
+ collapsed:: true
+ - DOING [[p1]] [[Progettazione Offerta Formativa]]
+ :LOGBOOK:
+ CLOCK: [2025-08-20 Wed 11:57:32]
+ :END:
- Spunti dalla chiamata fatta [[28-05-2025]] con [[people/AntonioSulli]]
- [[Mutuazione parziale corsi magistrale e o triennale]]
- - DOING [[Gestione studenti del primo anno che hanno già seguito corsi non nell'offerta formativa]]
+ - DOING [[p1]] [[Gestione studenti del primo anno che hanno già seguito corsi non nell'offerta formativa]]
:LOGBOOK:
CLOCK: [2025-05-27 Tue 15:42:48]
CLOCK: [2025-05-27 Tue 15:42:50]
@@ -99,17 +188,13 @@ progress:: {{renderer :todomaster}}
CLOCK: [2025-05-26 Mon 10:46:42]--[2025-06-10 Tue 14:42:00] => 363:55:18
:END:
- ## **Studenti attualmente all'estero con maggiorazione 50%**
- - CHIKE Kenneth Chijioke - dal [[08-01-2025]] al [[30-06-2025]] - Mai chiesto richiesta maggiorazione
- - Alessandro Di Matteo - dal [[01-02-2025]] al [[01-06-2025]]
- - Andrea D'Angelo - dal [[15-01-2025]] al [[13-07-2025]]
- - Isabella Gasbarro - dal [[07-09-2024]] al [[03-12-2024]], dal [[08-03-2025]] a inizi Giugno?
+ collapsed:: true
- Dagnaw - dal [[28-06-2025]] per 6 mesi
- ## **Studenti attualmente presso altro ente Italiano**
collapsed:: true
- - Dagnaw Gizealwe Alazie - dal [[27-12-2024]] al [[25-06-2025]] presso l'Università di Salerno (in attesa di riscontro del Ministero in merito al periodo da svolgere subito dopo presso Alicante in Spagna)
+ -
-
- ## **TODOs**
- collapsed:: true
- DONE [[Accreditamento Dottorato di Ricerca in Ingegneria e scienze dell'informazione - XLI ciclo]]
:LOGBOOK:
CLOCK: [2025-05-26 Mon 10:46:29]--[2025-06-12 Thu 13:37:58] => 410:51:29
@@ -179,8 +264,9 @@ progress:: {{renderer :todomaster}}
id:: 6659d0ed-b485-4423-9c75-a8f5d715b31f
- Questo e' un anti-pattern -> _1712172077031_0.pdf)
- ## FAQs
+ collapsed:: true
- ### **[[Frammenti di verbale riusabili]]**
- - ### Templates emails
+ - ### **Templates emails**
collapsed:: true
- **INVIO TESI AI REVISORI** (esempio subject Asad's PhD thesis review)
collapsed:: true
@@ -231,8 +317,9 @@ progress:: {{renderer :todomaster}}
- For the online defense, we use MS Teams. You can join the call scheduled in the Team named "PHD ICT - Student Presentations" (code 9y06sdz). You are free to use any other platform for your preparatory discussions.
- Thank you again for your support.
-
- - **INVIO MATERIALE AI MEMBRI COMMISSIONE FINALE (dopo decreto nomina in italiano)**
+ - **INVIO MATERIALE AI MEMBRI COMMISSIONE FINALE (dopo decreto nomina in italiano) **
collapsed:: true
+ - Esempio di mail con decreto di nomina ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAh5BSvzAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
- Carissimi/a,
in qualità di Coordinatore del Corso di Dottorato in ICT, desidero ringraziarvi per aver accettato il ruolo di membro della commissione giudicatrice per il conferimento del titolo di "Dottore di Ricerca in Ingegneria e Scienze dell'Informazione" - XXXVI ciclo. Il vostro compito sarà valutare il lavoro svolto dal dottorando Rehman Abdul.
@@ -250,6 +337,7 @@ progress:: {{renderer :todomaster}}
A presto,
Davide
+ -
- **LETTERA CAMBIO Azienda / Soggetto Ospitante**
collapsed:: true
- _1729328105582_0.pdf)
@@ -268,13 +356,43 @@ progress:: {{renderer :todomaster}}
- To facilitate this process, I will need the final version of your thesis by January 10th, which I will then forward to the reviewers.
- All the best
- Davide
+ - **Cosa ricevono gli studenti che devono presentare il lavoro davanti la commissione finale?**
+ collapsed:: true
+ - **From:** Settore dottorati, assegni e borse di ricerca
+ **Sent:** Wednesday, November 26, 2025 9:37 AM
+ **To:** Muhammad Asad ; Muhammad Imran
+ **Subject:** Convocation to the final exam
+ - Dear Doctor,
+ - please find attached the protocol letter n. 184149 of 26/11/2025 related to the convocation to the final exam.
+ - From now until December 3, 2025, you are allowed to upload your Final Thesis on Virtual Secretary.
+ - It's important that the thesis includes a short abstract in English.
+ - Moreover, within 5 days from this communication, you should send to the examination board your final thesis and your triennial report of the Ph.D. activities by e-mail.
+ - Best Regards
+ - Veronica
+ - 
+ - **EMAIL A STUDENTI NUOVO CICLO DOPO CONVOCAZIONE COLLEGIO DI FINE OTTOBRE**
+ collapsed:: true
+ - Dear all,
+ Thank you for participating in yesterday's PhD Board meeting, and congratulations once again on starting your journey in our PhD program!
+ Following our discussion, I would like to share a few important updates and next steps:
+ - *PhD Courses*: The preliminary list of currently available courses can be found in the shared folder titled [PhD Courses - 2025 - 2026](https://univaq.sharepoint.com/:f:/s/PHDICT-SeminarsandCourses/Eiq07sOc-j1EtjanyuaPshUBWakxh9G6gx1RII-Ka39W4w?e=KDIIHe) within the "*PHD ICT - Seminars and Courses*" team on MS Teams. We are in the process of finalizing the schedule, and further details will be shared soon. To join this team, please use the code: 9kkf5ny.
+ - *Research program and study plan*: As mentioned yesterday, please send me as soon as possible a tentative research program outlining the activities you plan to carry out during your PhD. To this end, please coordinate with your (co-)advisors. You can use the template available in the "Documents" section of our website at [http://phdict.disim.univaq.it/documents/](http://phdict.disim.univaq.it/documents/) , specifically the form titled "Proposal for the Next Years". Students with a PR FSE+ ABRUZZO scholarship (i.e., Nanni Gianluca, Mughal Abdul Basit, Ganesh Venkata Subramaniyan, and Bilal Hafiz Anas) can use the same document template to indicate the tentative list of courses they plan to attend during the first year and refer to the thematic number as the project description.
+ - *Laptop Requests*: If you require a laptop for your PhD work, please let me know.
+ - *Email address*: Once you get the "[univaq.it](http://univaq.it/)" email address, please share it with us.
+ - *Website*: the official website available at [Doctoral Program in ICT – University of L'Aquila (Italy)](http://phdict.disim.univaq.it/) is your main reference point. The ad-hoc courses section will be updated soon. Please check it regularly, as it contains important updates and information related to our PhD program. As you can see, you are already listed as current students at [http://phdict.disim.univaq.it/students/](http://phdict.disim.univaq.it/students/)
+ - *Welcome Day*: On November 26th at 10:00, we will hold the first "PhD Welcome Day", an event organized especially for first-year PhD students. The goal is to provide you with essential administrative and practical information about the program, explain how it works, and allow everyone to introduce themselves. At the end of the event, we plan to take a coffee break to enjoy some time together. The event will take place on the same floor where we had the meeting yesterday. We are currently planning to start around 9:30, but this will be confirmed soon.
+
+
+
+ Welcome again and see you soon,
+
+ Davide
- ### **PUBLIC**
collapsed:: true
- [FAQs (notion.so)](https://www.notion.so/phd-ict-univaq/FAQs-ef2849e8affc4c21ab1999e32b5eb009)
- ### **PRIVATE**
collapsed:: true
- #### Incremento borsa dottorato per periodo all'estero
- collapsed:: true
- Ciao Giordano,
collapsed:: true
- quando saprai la data precisa io produrrò una autorizzazione per
@@ -291,7 +409,7 @@ progress:: {{renderer :todomaster}}
- Ciao,
- Vittorio
- https://www.dropbox.com/scl/fi/50tbr6pkx7jloofsr3b8p/Autorizzazione-D-Aloisio.pdf?rlkey=w12y8fa6lkuer5y07xfdboc14&dl=0
- - ### *COSTO BORSA DI DOTTORATO*
+ - ### **COSTO BORSA DI DOTTORATO**
collapsed:: true
- 
- Circa 95'000 Euro incluso 10% per fondi di ricerca e 50% di maggiorazione per 6 mesi all'estero. Senza periodo all'estero siamo sui 65'000
@@ -300,6 +418,32 @@ progress:: {{renderer :todomaster}}
collapsed:: true
- 
- ## 2025/2026 #XLI ciclo
+ collapsed:: true
+ - 
+ - **Assegnamenti**
+ - |Candidato|Borsa|Supervisor|Co-supervisor|RG|
+ |--|--|--|--|--|
+ |((68ecf9ce-81bc-471c-94f4-06be923f5ff1))|MUR||||
+ |((68ecf9e5-04a9-4045-99da-a1e3cb737b35))|MUR|Stefano Smriglio|Fabrizio Rossi| RG2.1|
+ |((68ecf9fd-fe29-4224-9cd8-9014f68fdced))|MUR|Tania Di Mascio||RG1.3|
+ |((68ecfa05-7d25-4847-8fab-05a52f7f7f96))|MUR||||
+ |((68ecfa0e-4146-47ce-9b9f-225e708dc1cf))|MUR|Stefano Smriglio|Fabrizio Rossi| RG2.1|
+ |((68ecfa16-6986-4f5e-a69b-e793c43b7a61))|MUR||||
+ |((68ecfab2-c50c-4c53-8e7a-9d8ff511c9f7))|((68ecfac2-4348-442e-8e26-fa99e988033f))|Tania Di Mascio | Luigi Pomante | RG1.3|
+ |((68ecfb18-f881-4bfd-bbea-69920b5aa74d))|((68ecfb5d-37f6-4fa8-b320-3c2c845af8dd))|Antinisca Di Marco||RG2.2|
+ |((68ecfb2f-0d34-426c-ac2f-bd8ec548147c))|((68ecfb4e-6d06-407d-8ae4-71387deb5c0d))|Henry Muccini||RG2.2|
+ |((68ecfb71-cc6f-4d08-b54d-44b2644e2594))|((68ecfb98-9a60-4033-8b40-90b7abd3194c))|Antonio Bucchiarone| Marco Autili|RG2.2|
+ |((68ecfbb6-3b34-4145-86df-c215def56aa7))|((68ecfc10-e7ff-4c7c-a972-75a6c424b785))|Fortunato Santucci | | RG1.2|
+ |((68ecfc29-3506-4656-8847-cb584846ac9b))|((68ecfc39-0e6d-4cf6-bb05-e9db606d82a5))|Davide Di Ruscio | Phuong T. Nguyen, Juri Di Rocco | RG2.2|
+ |((68ecfc77-a51f-4bce-bac6-886e023990cc))|((68ecfc60-f07d-482e-a0b6-b5ac60f864d9))|Elena De Santis | |RG1.1|
+ |((68ecfca3-81db-4791-8c34-db6a07a5fde4))|((68ecfcaf-736d-468a-8894-f144c7a5529b))|Vittorio Cortellessa | | RG2.2|
+ |((68ecfce3-ef15-450e-8131-d3b3cac77f8d))|Senza Borsa | Antinisca Di Marco| | RG2.2 |
+ |((68ecfcf9-61d1-431d-97ac-22a7a5736c7a))| Senza Borsa | | | |
+ |((68ecfd12-2d01-4b73-9caf-0da45837c9e2))|Senza Borsa | | | |
+ |((68ed3720-5254-46fc-981a-b6ddc9b19bcf))|Senza Borsa | | | |
+ -
+ - **CALENDARIO**
+ - 
- **Commissione ammissione**
- *Membri effettivi*
- Daniele Frigioni - ING-INF/05
@@ -311,9 +455,7 @@ progress:: {{renderer :todomaster}}
- Andrea De Marcellis
- Tania Di Mascio ING-INF/05
- Alfonso Pierantonio INF/01
- - **CALENDARIO**
- - 
- - Overview borse (totale 14 con borsa, 4 senza):
+ - **Overview borse (totale 14 con borsa, 4 senza):**
collapsed:: true
- [MODELLO](https://dottorati.mur.gov.it/php5/compilazione/2025/vis_modello.php?amm=0&codice=3907831713T97VJY3J86094281322294397041&c=DO&PREF_X_TABELLE=DOTT25&modello=A&db=MIUR9&chiave=7TKD5JWN9GHQRUM1295875256&x=15&y=23)
- 6 MUR
@@ -321,21 +463,53 @@ progress:: {{renderer :todomaster}}
- 1 INAF
- 1 Palestina
- 1 Mosaico
+ - 1 Vittorio
- 4 senza borsa
- ---
- In ballo ce ne sono altre 3 dall'Agenzia Nazionale sulla Cybersicurezza
- - [[Accreditamento Dottorato di Ricerca in Ingegneria e scienze dell'informazione - XLI ciclo]]
+ background-color:: red
+ - **[[Accreditamento Dottorato di Ricerca in Ingegneria e scienze dell'informazione - XLI ciclo]]**
- 
- - ((67d84475-4b24-4d76-bcf1-d789c5506c95))
- - Ci deve essere un coordinamento a livello di Ateneo?
- - ((67d844b6-4598-451a-9344-33aced047c68))
- collapsed:: true
- - Questo non dipende da noi... ancora non viene inoltrata la scheda informativa !!!
- - ((67d844f6-acec-4dca-8f3d-166c93371afe))
- collapsed:: true
- - Questo e' fondamentale!!!
- - ((67d8451e-abb9-4a76-9982-be8e0d8b7507))
- - Questo anche e' da vedere!!!
+ - ((67d84475-4b24-4d76-bcf1-d789c5506c95))
+ - Ci deve essere un coordinamento a livello di Ateneo?
+ - ((67d844b6-4598-451a-9344-33aced047c68))
+ collapsed:: true
+ - Questo non dipende da noi... ancora non viene inoltrata la scheda informativa !!!
+ - ((67d844f6-acec-4dca-8f3d-166c93371afe))
+ collapsed:: true
+ - Questo e' fondamentale!!!
+ - ((67d8451e-abb9-4a76-9982-be8e0d8b7507))
+ - Questo anche e' da vedere!!!
+ - **Borsa aggiuntiva riservata studenti Palestina**
+ - 
+ - ((6887884d-9fdf-4135-b06d-65ed75c76950))
+ - Mail dal settore dottorati
+ collapsed:: true
+ - Gentili Coordinatori,
+
+ Vi informiamo che l'Università degli Studi dell'Aquila, in partenariato con l'Università di Perugia, l'Università Politecnica delle Marche e la Scuola Superiore Sant'Anna di Pisa partecipa all'Iniziativa AICS “Intervento multidisciplinare a sostegno dell’educazione alla parità di genere in Palestina” (“Multi-disciplinary action aimed at supporting the gender equality education in Palestine”).
+
+ Forniamo in allegato la relativa documentazione.
+
+ Il Consiglio di Amministrazione, nella seduta del 28/05/2025 ha deliberato in merito all' emanazione di un bando di selezione, destinato esclusivamente a candidati Palestinesi, per l’assegnazione di n. 1 borsa di studio per il Dottorato di Ricerca in Ingegneria e scienze dell’informazione e n. 1 borsa di studio per il Dottorato di Ricerca in Letterature, arti, media: la transcodificazione - XLI ciclo - a.a. 2025/2026.
+
+ Le scadenze proposte sono le seguenti:
+ - emanazione del bando di selezione al massimo entro il 5 agosto 2025:
+ - scadenza del termine per la presentazione delle domande fissata al massimo al 10 settembre 2025;
+ - nomina commissioni entro il 15 settembre 2025;
+ - prove selettive tra il 18 e il 26 settembre 2025;
+ - consegna degli atti concorsuali improrogabilmente entro il 30 settembre 2025;
+ - pubblicazione dell’approvazione degli atti concorsuali entro il 6 ottobre 2025;
+ - immatricolazione dei vincitori entro il 21 ottobre 2025;
+ - eventuali scorrimenti e ammissione ai corsi entro il 31 ottobre 2025;
+ - inizio dei corsi fissato al 1° novembre 2025.
+
+ Trasmettiamo pertanto le schede da allegare al bando, da controllare e da integrare/modificare nelle parti evidenziate in giallo, con preghiera di inoltrarle a questo Settore entro il 30 luglio p.v.
+
+ Cordiali saluti
+
+ Rossana Rotondi
+ -
- ## 2024/2025 #DM629 #DM630 #[[XL Ciclo]]
- ### Lavori commissione ammissione
- [Scheda informativa](https://www.univaq.it/include/utilities/blob.php?table=corso_dottorato&id=283&item=scheda_informativa)
@@ -345,6 +519,8 @@ progress:: {{renderer :todomaster}}
[Risultati della valutazione dei titoli](https://www.univaq.it/include/utilities/blob.php?table=corso_dottorato&id=283&item=risultati_valutazione_titoli)
[Approvazione atti e graduatoria](https://www.univaq.it/include/utilities/blob.php?table=corso_dottorato&id=283&item=graduatoria)
- [Domande prova orale](https://www.univaq.it/include/utilities/blob.php?table=corso_dottorato&id=283&item=domanda_prova_orale)
+ - 
+ collapsed:: true
- ### #DM629 #DM630
- Passaggi importanti:
- 1. il DM 629 (ex 118 - dottorati PNRR) assegna 779 borse con finanziamento da 70mila euro (e 15+15 borse ai due dottorati nazionali accreditati nel 37° ciclo);
@@ -384,7 +560,6 @@ progress:: {{renderer :todomaster}}
- ((6638b48b-081c-4aac-9983-300788b7d416))
- ((6638b4a5-76c9-4adb-b430-c5989548cd83))
id:: 6638b4ab-84e7-45eb-a30a-a0e6de2d0cc6
- -
-  [[P1]]
- ((6638a4a3-0308-4df7-a3ef-2993991a18ba))
- [[question]] Quando puo' accadere questo?
@@ -395,11 +570,10 @@ progress:: {{renderer :todomaster}}
- 
- {:height 916, :width 564}
- {:height 429, :width 563}
- -
- -
- ## 2022/2023 #DM351 #DM352 #[[XXXVIII Ciclo]]
- Decreti Ministeriali n. 351, n. 352 del 9 aprile 2022 e n. 925 del 29 luglio 2022
- ## REGOLAMENTI
+ collapsed:: true
- [[@REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023.pdf]] [[STAR]]
- 
- ((65a67a30-5794-4a02-83cc-94275264adb3))
@@ -407,6 +581,8 @@ progress:: {{renderer :todomaster}}
id:: 65a67a37-1862-4c97-b497-ac9883e8281a
- [Decreto Ministeriale n.226 del 14-12-2021 | Ministero dell'Università e della Ricerca (mur.gov.it)](https://www.mur.gov.it/it/atti-e-normativa/decreto-ministeriale-n226-del-14-12-2021)
-  [[STAR]]
+ id:: 68584ed7-9cdb-439a-a339-9a61640037df
+ -
- 
- ((673b1b54-47b9-44d4-8363-a6753c381283))
- ((673b1b5a-f16f-4535-b1fd-ecc8eb084e49))
@@ -417,6 +593,7 @@ progress:: {{renderer :todomaster}}
collapsed:: true
- 
- [AVA3_ModelloNote_2022_10_12.pdf (anvur.it)](https://www.anvur.it/wp-content/uploads/2023/02/AVA3_ModelloNote_2022_10_12.pdf) [[STAR]] [[AVA3]]
+ id:: 68584ed7-1a9f-42ba-85b0-9cd778066ea7
collapsed:: true
- 
- 
@@ -574,6 +751,7 @@ progress:: {{renderer :todomaster}}
- MAROTTA Andrea RTD/A Componente ING INF/03
background-color:: green
logseq.order-list-type:: number
+ collapsed:: true
- PINAR Mustafa PO MAT/09
logseq.order-list-type:: number
- FISCHIONE Carlo PO ING INF/03
@@ -587,4 +765,5 @@ progress:: {{renderer :todomaster}}
- ## SOME FEW WORDS
collapsed:: true
- "Thank you all for being here today and for your insightful questions and contributions. Congratulations to [PhD candidate's name] for a thorough and well-executed presentation. The work you have presented today showcases the depth of your research and your dedication to advancing the field of ICT. I want to commend you on the significant effort and perseverance that brought you to this point.
- - On behalf of the committee and the programme, I wish you continued success in your future endeavors. Let this achievement be the beginning of even greater contributions to the academic and professional community. Once again, congratulations."
\ No newline at end of file
+ - On behalf of the committee and the programme, I wish you continued success in your future endeavors. Let this achievement be the beginning of even greater contributions to the academic and professional community. Once again, congratulations."
+-
\ No newline at end of file
diff --git a/pages/SERVICES___RADIOLABS.md b/pages/SERVICES___RADIOLABS.md
new file mode 100644
index 00000000..f0419f72
--- /dev/null
+++ b/pages/SERVICES___RADIOLABS.md
@@ -0,0 +1,4 @@
+icon:: 📻
+
+- #Resources
+ - 
\ No newline at end of file
diff --git a/pages/SOSYM-23-00004472_Proof_hi.md b/pages/SOSYM-23-00004472_Proof_hi.md
index 7367e003..fa73eae4 100644
--- a/pages/SOSYM-23-00004472_Proof_hi.md
+++ b/pages/SOSYM-23-00004472_Proof_hi.md
@@ -23,8 +23,8 @@ file:: )
- What's that?
- - DONE Guardare Design Science Research #reading
-id:: 65c8d477-cade-4b0b-a8b4-2756a6b98e6e
+ - DONE Guardare Design Science Research #Reading
+ id:: 65c8d477-cade-4b0b-a8b4-2756a6b98e6e
- ((64f5ecd3-6ecb-48c6-a506-afc8e4a261af))
- ((64f5fabc-0007-47cd-8b9c-f733ec7736cd))
- You said that many times. I would make the section shorter and maybe discuss a motivating / explanatory example
@@ -81,9 +81,9 @@ id:: 65c8d477-cade-4b0b-a8b4-2756a6b98e6e
- [[Notes]]
- ((650430e7-dee7-4807-82c8-d8cd1c4ac42e))
- DONE Guardare ontologia IoT-Lite per corso IoT
-id:: 65c8d477-2c6c-4548-9e72-09cee84bec35
- - DONE ((6504517f-4d23-4d6d-9a71-cd8b0da1d5fc)) [[empirical]] [[reading]]
-id:: 65c8d477-b5c3-45c1-986d-9daf3563a1d1
+ id:: 65c8d477-2c6c-4548-9e72-09cee84bec35
+ - DONE ((6504517f-4d23-4d6d-9a71-cd8b0da1d5fc)) [[empirical]] [[Reading]]
+ id:: 65c8d477-b5c3-45c1-986d-9daf3563a1d1
:LOGBOOK:
CLOCK: [2025-05-26 Mon 22:21:22]--[2025-05-26 Mon 22:21:23] => 00:00:01
:END:
diff --git a/pages/SWEN Retreat 2025.md b/pages/SWEN Retreat 2025.md
index 10a6e319..4210efaf 100644
--- a/pages/SWEN Retreat 2025.md
+++ b/pages/SWEN Retreat 2025.md
@@ -3,9 +3,13 @@ date:: [[13-07-2025]] - 16:57
link:: https://univaq-my.sharepoint.com/:w:/g/personal/juri_dirocco_univaq_it/EQ-K23f6XrJPvu0NMEBJbwMB2mOKj0PTLNoPBrgOsUEeGQ?e=fSHI0E
progress:: {{renderer :todomaster}}
- - ### Tasks
- -
+ - ### TASKS
+ collapsed:: true
+ - {{query (and [[SWEN Retreat 2025]] (task TODO DOING) (not [[GOALS-TODOIST]]) (not [[TODOIST-LOGSEQED]]))}}
+ query-table:: true
+ query-properties:: [:block]
- ### Notes
+ - 
- ## First day [[15-07-2025]]
collapsed:: true
- ### Points for discussion
@@ -41,47 +45,51 @@ progress:: {{renderer :todomaster}}
- Discrimination of universities depending on their possibility of training/fine-tuning
- Alfonso was suggesting to use Wikidata for generating domain models from textual descriptions
- ## Second day [[16-07-2025]]
- - Topics of the groups
- - Green SW Engineering
- - Sustainabiolity
- - Simlation in federated digital twins
- - Cultural Heritage
- - RecSys
- - Multi-view Modeling
- - Reuse of LLM Agents for Software Engineering
- - Performance Analysis
- - Model
- - Code
- - NF Analysis for SW
- - AI Ops
- - Code execution and LLMs
- - Ethic for SW
- - MDE techniques + JJodel
- - CONCEPTS
- - System views
- - Pre deployment
- - Statics
- - Forward vs reverse engineering
- - Dynamics
- - Forward vs reverse engineering
- - Analysis
- - Predictive
- - Prescriptive
- - Simulation
- - It requires semantics
- - Post deployment
- - System Monitoring
- - System Adaptation
- - Supporting tools
- - Modeling environments
- - LLMs
- - To move from statics to dynamics
- - To support deployment (e.g., reconstruct the microservice architecture)
- - Configurations
- - Single agent
- - MAS workflows
- - e.g, design patterns for software architecture perspectives
- - WPs
+ collapsed:: true
+ - [SWEN Project - Google Docs](https://docs.google.com/document/d/1cvbufoeL0JcZKgHEUpy71P7677eE4UwQu_VAgLvgzwo/edit?tab=t.0)
+ - Topics of the groups
+ collapsed:: true
+ - Green SW Engineering
+ - Sustainabiolity
+ - Simlation in federated digital twins
+ - Cultural Heritage
+ - RecSys
+ - Multi-view Modeling
+ - Reuse of LLM Agents for Software Engineering
+ - Performance Analysis
+ - Model
+ - Code
+ - NF Analysis for SW
+ - AI Ops
+ - Code execution and LLMs
+ - Ethic for SW
+ - MDE techniques + JJodel
+ - CONCEPTS
+ collapsed:: true
+ - System views
+ - Pre deployment
+ - Statics
+ - Forward vs reverse engineering
+ - Dynamics
+ - Forward vs reverse engineering
+ - Analysis
+ - Predictive
+ - Prescriptive
+ - Simulation
+ - It requires semantics
+ - Post deployment
+ - System Monitoring
+ - System Adaptation
+ - Supporting tools
+ - Modeling environments
+ - LLMs
+ - To move from statics to dynamics
+ - To support deployment (e.g., reconstruct the microservice architecture)
+ - Configurations
+ - Single agent
+ - MAS workflows
+ - e.g, design patterns for software architecture perspectives
+ - Workpackages
- **WP1: Pre-deployment design and anlysis of software systems**
- T1.1: Multi-dimensional non-functional analysis
- T1.2: Multi-dimensional software architectures (e.s. green) (deps: T1.1)
@@ -98,6 +106,89 @@ progress:: {{renderer :todomaster}}
- **WP5: Impact**
- Use case scenarios (Cultural heritage, Territorial monitoring)
- Education
- -
- -
- -
\ No newline at end of file
+ - Investigating the impact of code refactoing on perfomance and energy
+ - Code refactoring vs software security and its impact on energy consumption
+ - all the commits of the history are considered for the analysis
+ - Martin Beseda - Steady-state detection in timeseries and stuff
+ - Timeseries classification / hierarchical clustreing
+ - Test case selection in collaboration with Dario Di Nucci
+ - Quantum Computing for NISQ
+ -
+ - ## Third day [[17-07-2025]]
+ - ### **SWEN Research Group Strategic Meeting**
+ collapsed:: true
+ - ##### Meeting Overview
+ - The SWEN software engineering research group met to discuss strategic positioning within the university, administrative challenges with research funding, curriculum development around AI/LLM, and potential organizational structures to facilitate operations. The group focused on strengthening their influence in university governance while maintaining research excellence.
+ - ##### University Politics and Positioning
+ - The group acknowledged they need more strategic involvement in university politics to protect their interests:
+ - Need for representation in key committees, particularly the Resources Commission
+ - Discussion about potentially supporting a vice-director candidate from the SWEN group
+ - Recognition that while research excellence is their priority, political engagement is necessary
+ - Proposal to improve information sharing about university developments through a dedicated WhatsApp group
+ - Concern about maintaining appropriate recognition despite administrative challenges
+ - ##### Administrative Challenges and Solutions
+ - Participants expressed significant frustration with administrative barriers to research:
+ - Difficulty executing research contracts and efficiently using project funds
+ - Challenge of maintaining staff continuity when projects end
+ - Several organizational structures were discussed:
+ - Creating a foundation or spin-off
+ - Exploring examples from other universities (Bari, Salerno)
+ - Investigating integration with existing entities like Vitality Foundation
+ - Considering tax hubs for supporting open source projects
+ - Agreement to coordinate sharing human resources across projects when possible
+ - ##### Research Strategy and Visibility
+ - The group discussed developing a comprehensive document/manifesto that:
+ - Maps research competencies and potential synergies
+ - Identifies resource requirements including PhD positions
+ - Serves both internal coordination and external communication
+ - Could be presented as an event for visibility
+ - Would support funding applications in the post-PNRR era
+ - ##### Education and Curriculum Development
+ - With growing student interest in AI, the group discussed approaches to curriculum enhancement:
+ - Incorporating AI/LLM content into existing software engineering courses
+ - Creating dedicated courses on AI applications in software engineering
+ - Leveraging a newly approved course in the EDIS program on LLM in Software Engineering
+ - Concerns about securing computational resources (tokens) needed for these initiatives
+ - Need to better communicate SWEN's relationship to AI to attract students
+ - ##### International Collaboration
+ - Potential bilateral agreement with ITU Vienna for a double degree program
+ - Options in either software engineering or business informatics
+ - Discussion about Green Deal program possibilities
+ - Potential to host the ICT4Sustainability conference in L'Aquila in 2027
+ - ##### Action Items
+ - TODO Create a WhatsApp group for sharing information on university politics and governance
+ - TODO Develop comprehensive document showcasing SWEN research topics and capabilities
+ - TODO Incorporate AI/LLM content in curriculum by end of July
+ - TODO Follow up on potential bilateral agreement with ITU Vienna
+ - TODO Consider organizing ICT4Sustainability conference in L'Aquila 2027
+ - TODO Establish better coordination for sharing resources across projects
+ - TODO Gather data on SWEN's contribution to student enrollment to strengthen position in resource discussions
+ - TODO Explore options for establishing an external entity to facilitate research operations
+ - ### **Academic Group Planning Meeting**
+ collapsed:: true
+ - #### Meeting Overview
+ - This meeting focused on finalizing a collaboration document, improving student engagement strategies, enhancing the group's visibility through various communication channels, and establishing better operational protocols. The discussion centered around how to attract more students and increase the group's presence both internally and externally.
+ - #### Collaboration Document
+ - The group is working on consolidating a document that outlines collaboration opportunities, responsibilities, and project details. This document needs to be finalized before the academic year begins.
+ - TODO Finalize the collaboration document by mid-September (before classes start on September 22nd)
+ - #### Student Engagement Initiatives
+ - Participants discussed creating regular thesis presentation days to inform students about available bachelor's and master's thesis opportunities. This would include small gatherings where students could interact with faculty in a comfortable environment.
+ - TODO Develop a proposal for thesis presentation days (once per semester)
+ - TODO Create a process for publishing and promoting thesis opportunities
+ - #### Communication Strategy
+ - A significant portion of the meeting focused on improving the group's visibility through various communication channels:
+ - **Booklet/Manifesto**: Creating a concise printed document highlighting the group's activities, projects, and opportunities that could be distributed to students and external partners.
+ - **Social Media Presence**: Establishing a consistent presence across appropriate platforms with regular updates about achievements, publications, and activities.
+ - **Website Improvements**: The current website was described as difficult to navigate, particularly for students.
+ - **Brand Identity**: The need for consistent branding across all presentations, materials, and communications was emphasized.
+ - TODO Develop a concise booklet/manifesto about the group's activities
+ - TODO Create a social media strategy with differentiated content for different platforms
+ - TODO Improve website navigation and user experience
+ - TODO Establish consistent branding guidelines for presentations and materials
+ - #### Operational Improvements
+ - The group discussed the need for better protocols for internal communication and data sharing:
+ - [ ] Develop a protocol for collecting and sharing important data and achievements
+ - TODO Establish a process for regular updates to communication materials
+ - #### Future Planning
+ - The meeting concluded with plans for making this type of gathering a recurring event.
+ - TODO Schedule the next meeting for mid-February (before the start of teaching)
\ No newline at end of file
diff --git a/pages/Services-Commissione-Ricerca-DISIM.md b/pages/Services-Commissione-Ricerca-DISIM.md
new file mode 100644
index 00000000..b4a1b967
--- /dev/null
+++ b/pages/Services-Commissione-Ricerca-DISIM.md
@@ -0,0 +1 @@
+icon:: 🔭
diff --git a/pages/Services/CollegioPhD/Assegnazione borse ai nuovi dottorandi.md b/pages/Services/CollegioPhD/Assegnazione borse ai nuovi dottorandi.md
index 3a677537..fbfeae0d 100644
--- a/pages/Services/CollegioPhD/Assegnazione borse ai nuovi dottorandi.md
+++ b/pages/Services/CollegioPhD/Assegnazione borse ai nuovi dottorandi.md
@@ -1,8 +1,8 @@
Il Collegio assegna le borse a fronte di:
-- Progetto di ricerca presentato dai dottori
-- Dichiarazione di accettazione della borsa
-
-
-In questa sede si inidca qui la data di inzio dei corsi
-
+ - Progetto di ricerca presentato dai dottori
+ - Dichiarazione di accettazione della borsa
+
+
+ In questa sede si inidca qui la data di inzio dei corsi
+-
\ No newline at end of file
diff --git a/pages/SoftwareMiningGroup.md b/pages/SoftwareMiningGroup.md
index c8be6a13..d6407446 100644
--- a/pages/SoftwareMiningGroup.md
+++ b/pages/SoftwareMiningGroup.md
@@ -2,4 +2,7 @@ icon:: 🔨
- ### Meetings
- {{query (and [[meeting]] [[SoftwareMiningGroup]])}}
- query-table:: true
\ No newline at end of file
+ query-table:: true
+ query-properties:: [:page :tags]
+ query-sort-by:: page
+ query-sort-desc:: false
\ No newline at end of file
diff --git a/pages/TEACHING.md b/pages/TEACHING.md
index 0ee3b42d..db8321d6 100644
--- a/pages/TEACHING.md
+++ b/pages/TEACHING.md
@@ -1,6 +1,13 @@
icon:: 👨🏫
+- 25/26
+ - | Corso di Laurea Scienze del servizio sociale S3S (L39) |
+ - | DQ0716 - Multimedialità e informatica per le scienze sociali A
+ - prof. D. Di Ruscio
+ - aula 3B
+ - data inizio 30/092025 |
- **24/25**
+ collapsed:: true
- 
- **Corso di laurea - S3F -Scienze dell'educazione e della formazione**
- **_DQ0570 - Multimedialità per le scienze dell'educazione - 6 cfu- 36 ore -** _(obbligatorio)_
diff --git a/pages/TODOIST-LOGSEQED.md b/pages/TODOIST-LOGSEQED.md
index 4fc01bdb..9457a8d2 100644
--- a/pages/TODOIST-LOGSEQED.md
+++ b/pages/TODOIST-LOGSEQED.md
@@ -21,10 +21,9 @@ progress:: {{renderer :todomaster}}
todoist-desc:: logseq://graph/Logseq?page=Definizione%20processo%20gestione%20moduli%20didattica%20studenti
todoist-id:: [9204275059](https://app.todoist.com/app/task/9204275059)
SCHEDULED: <2025-06-04 Wed>
-- TODO [#A] [[Progettazione Offerta Formativa]]
+- DONE [[Progettazione Offerta Formativa]]
todoist-desc:: logseq://graph/Logseq?page=Progettazione%20Offerta%20Formativa
todoist-id:: [9205819498](https://app.todoist.com/app/task/9205819498)
- SCHEDULED: <2025-07-17 Thu>
- DONE [#A] [[Missione STAF 2025]]
todoist-id:: [9135141990](https://app.todoist.com/app/task/9135141990)
SCHEDULED: <2025-06-19 Thu>
@@ -38,32 +37,33 @@ progress:: {{renderer :todomaster}}
:LOGBOOK:
CLOCK: [2025-06-04 Wed 21:44:24]--[2025-06-08 Sun 18:00:14] => 92:15:50
:END:
-- TODO [#C] [[PAPERS/SOSYM-EXPERT-VOICE-2024-ML-EVOLUTION]]
+- TODO [[PAPERS/SOSYM-EXPERT-VOICE-2024-ML-EVOLUTION]]
todoist-desc:: [Sosym Expert voice: Co-evo in the era of Low code - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/680d243a75547ff8d273e791)
todoist-id:: [7584640828](https://app.todoist.com/app/task/7584640828)
-- TODO [#A] [[PAPERS/AUSE-Metagente]]
+- DONE [#A] [[PAPERS/AUSE-Metagente]]
todoist-desc:: [MDEGroup/AUSE-Metagente: A paper to be submitted to a special issue of the Automated Software Engineering journal](https://github.com/MDEGroup/AUSE-Metagente)
todoist-id:: [9213097648](https://app.todoist.com/app/task/9213097648)
+ SCHEDULED: <2025-09-03 Wed>
:LOGBOOK:
CLOCK: [2025-06-20 Fri 22:58:39]--[2025-06-30 Mon 15:43:41] => 232:45:02
:END:
- TODO [#B] [[Call per posizioni MOSAICO]]
todoist-desc:: logseq://graph/Logseq?page=Call%20per%20posizioni%20MOSAICO
todoist-id:: [8663268357](https://app.todoist.com/app/task/8663268357)
- SCHEDULED: <2025-07-15 Tue>
+ SCHEDULED: <2025-12-29 Mon>
:LOGBOOK:
CLOCK: [2025-06-14 Sat 11:21:37]--[2025-06-14 Sat 21:27:23] => 10:05:46
:END:
-- TODO [[Missione FSE 2025]]
- todoist-desc:: [FSE 2025](https://conf.researchr.org/home/fse-2025)
+- DONE [[Missione FSE 2025]]
todoist-id:: [9074935545](https://app.todoist.com/app/task/9074935545)
- SCHEDULED: <2025-07-18 Fri>
+ SCHEDULED✔️ <2025-07-21 Mon>
:LOGBOOK:
CLOCK: [2025-06-23 Mon 08:20:59]--[2025-06-29 Sun 08:34:46] => 144:13:47
:END:
-- TODO [#A] [[PAPERS/MOSAICO-Technical-Report]]
+- DONE [#A] [[PAPERS/2025-EMSE-MOSAICO-Experience-Report]]
todoist-desc:: logseq://graph/Logseq?page=PAPERS%2FMOSAICO-Technical-Report
todoist-id:: [9187744429](https://app.todoist.com/app/task/9187744429)
+ SCHEDULED: <2025-10-05 Sun>
:LOGBOOK:
CLOCK: [2025-06-07 Sat 13:49:10]--[2025-06-08 Sun 21:19:31] => 31:30:21
CLOCK: [2025-06-13 Fri 12:00:06]--[2025-06-14 Sat 09:56:22] => 21:56:16
@@ -74,22 +74,21 @@ progress:: {{renderer :todomaster}}
SCHEDULED: <2025-06-19 Thu>
- TODO [#B] [[Aggiornamento uso fondi progetti]]
todoist-id:: [9143259271](https://app.todoist.com/app/task/9143259271)
- SCHEDULED: <2025-07-16 Wed>
-- TODO [[Invited talk at LLMA4SE Summer School website]]
- todoist-id:: [9201031612](https://app.todoist.com/app/task/9201031612)
+ SCHEDULED: <2025-12-27 Sat>
+- DONE [#A] [[Invited talk at LLMA4SE Summer School website]]
todoist-desc:: From: chemacm@unex.es
- SCHEDULED: <2025-08-18 Mon>
-- TODO [#A] [[Missione Emeliot Salerno - Luglio 2025]]
+ todoist-id:: [9201031612](https://app.todoist.com/app/task/9201031612)
+ SCHEDULED: <2025-09-01 Mon>
+- DONE [#C] [[Missione Emeliot Salerno - Luglio 2025]]
todoist-desc:: From: leonardo.mariani@unimib.it
todoist-id:: [9161916557](https://app.todoist.com/app/task/9161916557)
- SCHEDULED: <2025-07-18 Fri>
+ SCHEDULED: <2025-09-29 Mon>
- DONE [#A] [[I: ELSEVIER IST: Your Submission - INFSOF-D-25-00112 - Major Revision]]
todoist-desc:: From: [giordano.daloisio@univaq.it](mailto:giordano.daloisio@univaq.it)
todoist-id:: [9223518427](https://app.todoist.com/app/task/9223518427)
- TODO [#C] [[Linee guida afferenza Collegio dottorato ICT]]
todoist-desc:: [Linee guida per la valutazione richieste afferenza dottorato ICT.docx](https://univaq-my.sharepoint.com/:w:/g/personal/davide_diruscio_univaq_it/EbLmq-bFlvZDpxTZLeHiQFgBBlAIxRR_3aoAZsNBUHFyXw?e=cXOsS3)
todoist-id:: [8912715542](https://app.todoist.com/app/task/8912715542)
- SCHEDULED: <2025-07-17 Thu>
:LOGBOOK:
CLOCK: [2025-06-13 Fri 11:59:57]--[2025-06-14 Sat 09:56:22] => 21:56:25
:END:
@@ -99,18 +98,18 @@ progress:: {{renderer :todomaster}}
:LOGBOOK:
CLOCK: [2025-06-20 Fri 16:29:44]--[2025-06-23 Mon 17:11:39] => 72:41:55
:END:
-- TODO [#B] [[PRIN 2020 - scadenza rendicontazione finale]]
+- DONE [#A] [[PRIN 2020 - scadenza rendicontazione finale]]
todoist-desc:: From: proget@strutture.univaq.it
todoist-id:: [9134866367](https://app.todoist.com/app/task/9134866367)
- SCHEDULED: <2025-07-16 Wed>
-- TODO [#C] [[Missione ROMA Mosaico]]
+ SCHEDULED: <2025-07-25 Fri 09:30>
+- DONE [#C] [[Missione ROMA Mosaico]]
todoist-id:: [9204561368](https://app.todoist.com/app/task/9204561368)
- SCHEDULED: <2025-07-18 Fri>
+ SCHEDULED: <2025-09-29 Mon>
- DONE [#B] [[MODELS: 10 years most infuential paper selection committee]]
todoist-desc:: From: manuel.wimmer@jku.at
todoist-id:: [9153069465](https://app.todoist.com/app/task/9153069465)
SCHEDULED: <2025-06-19 Thu>
-- TODO [#B] [[PAPERS/2025-LLM-GENERATION]]
+- DONE [#C] [[PAPERS/2025-LLM-GENERATION]]
todoist-id:: [9273049128](https://app.todoist.com/app/task/9273049128)
- DONE [#A] [[PAPERS/2025-ASE-NIER-MALICIOUS-CODE-DETECTION]]
todoist-desc:: [MDEGroup/ASE2025-NIER: A paper to be submitted to the NIER track of ASE 2025](https://github.com/MDEGroup/ASE2025-NIER)
@@ -119,7 +118,93 @@ progress:: {{renderer :todomaster}}
todoist-desc:: From: [antonio.mecozzi@univaq.it](mailto:antonio.mecozzi@univaq.it)
todoist-id:: [9223534564](https://app.todoist.com/app/task/9223534564)
SCHEDULED: <2025-07-14 Mon>
-- TODO [#A] [[SWEN Retreat 2025]]
- todoist-desc:: From: [alfonso.pierantonio@univaq.it](mailto:alfonso.pierantonio@univaq.it)
+- DONE [#A] [[SWEN Retreat 2025]]
todoist-id:: [9308806176](https://app.todoist.com/app/task/9308806176)
- SCHEDULED: <2025-07-15 Tue>
\ No newline at end of file
+ id:: 6873c94d-06e6-466f-a125-f321b20c39fb
+ SCHEDULED✔️ <2025-07-20 Sun>
+- DONE [#A] [[Rendicontazione EMELIOT]]
+ todoist-desc:: From: leonardo.mariani@unimib.it
+ todoist-id:: [9345475244](https://app.todoist.com/app/task/9345475244)
+ SCHEDULED: <2025-07-24 Thu>
+- DONE [#A] [[Deliverable D2.1]]
+ todoist-id:: [9360212650](https://app.todoist.com/app/task/9360212650)
+ SCHEDULED: <2025-10-02 Thu>
+- DONE [#B] [[PAPERS/TOSEM2025-TESORO]]
+ todoist-desc:: [TOSEM-TESORO - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/66d9716bef9f27487e485b86)
+ todoist-id:: [8908503469](https://app.todoist.com/app/task/8908503469)
+- TODO [#C] [[Rapporti con il GSSI]]
+ todoist-desc:: From: alfonso.pierantonio@univaq.it
+ todoist-id:: [9277838289](https://app.todoist.com/app/task/9277838289)
+- TODO [#A] [[Acquisto CASA Pescara]]
+ todoist-id:: [9401023109](https://app.todoist.com/app/task/9401023109)
+- DONE [#A] [[PAPERS/2026-SANER-RENE-PERFORMANCE-BUG-DETECTION]]
+ todoist-desc:: Paper submission deadline: 16 Ottobre
+ todoist-id:: [9402725388](https://app.todoist.com/app/task/9402725388)
+- DONE [#A] [[PAPERS/2026-SANER-Mutation_Analysis_Bias_Symptoms_Salerno]]
+ todoist-desc:: [SANER 2026](https://conf.researchr.org/home/saner-2026)
+ todoist-id:: [9456391671](https://app.todoist.com/app/task/9456391671)
+ SCHEDULED: <2025-10-17 Fri>
+- DONE [[PAPERS/2025-JSS-LAMPS-UMAR]]
+ todoist-desc:: [JSS-LAMPS-CoverLetter - Documenti Google](https://docs.google.com/document/d/1hyedGozjshSJhKdhcMHuabrmM3I4YOk2OCS9i5OeJCo/edit?tab=t.0)
+ todoist-id:: [9509552863](https://app.todoist.com/app/task/9509552863)
+- DONE [#A] [[Invited talk at workshop ASE]]
+ todoist-id:: [9535781602](https://app.todoist.com/app/task/9535781602)
+ SCHEDULED: <2025-11-16 Sun 14:00>
+- DONE [#B] [[Invited talk at MDE Intelligence]]
+ todoist-id:: [9535782792](https://app.todoist.com/app/task/9535782792)
+ SCHEDULED: <2025-10-07 Tue>
+- DONE [#A] [[Richiesta compilazione tabella relativa alle attività didattiche svolte durante il triennio_Dottorato di Ricerca in Ingegneria e scienze dell'informazione_XXXVIII ciclo]]
+ todoist-desc:: From: dot@strutture.univaq.it
+ todoist-id:: [9414891247](https://app.todoist.com/app/task/9414891247)
+ SCHEDULED: <2025-09-24 Wed>
+- DONE [#A] [[PAPERS/2026-SANER-RAG-ATTACK]]
+ todoist-desc:: The guys in Vietnam already invited you on Overleaf using you email. Please check if you have got it. The project is available in the following link: https://www.overleaf.com/project/684e2983ca5f3e4929b35c63
+ todoist-id:: [9553350820](https://app.todoist.com/app/task/9553350820)
+ SCHEDULED: <2025-10-16 Thu>
+- DONE [#A] [[Deliverable D3.1]]
+ todoist-desc:: From: massimo.tisi@imt-atlantique.fr
+ todoist-id:: [9502385342](https://app.todoist.com/app/task/9502385342)
+ SCHEDULED: <2025-10-01 Wed>
+- DONE [#A] [[Giornata di presentazione del dottorato]]
+ todoist-id:: [8105332696](https://app.todoist.com/app/task/8105332696)
+ SCHEDULED: <2025-11-26 Wed>
+- DONE [#A] [[Assicurazione della Qualità di Corsi di Studio e di dottorato e Dipartimenti - Audizione del 21 novembre 2025]]
+ todoist-desc:: From: donatella.donatelli@univaq.it
+ todoist-id:: [9603360520](https://app.todoist.com/app/task/9603360520)
+ SCHEDULED: <2025-11-21 Fri>
+- TODO [#B] [[Benchmarking framework]]
+ todoist-id:: [9524235429](https://app.todoist.com/app/task/9524235429)
+ SCHEDULED: <2025-12-27 Sat 12:00>
+ :LOGBOOK:
+ CLOCK: [2025-12-16 Tue 16:19:32]--[2025-12-17 Wed 16:06:00] => 23:46:28
+ :END:
+- DONE [#A] [[Assicurazione della qualità dei corsi di Dottorato di Ricerca – AVA3 – Calendario delle scadenze. Presentazione relazione di fine ciclo (RC.PHD)]]
+ todoist-desc:: From: dot@strutture.univaq.it
+ todoist-id:: [9734747741](https://app.todoist.com/app/task/9734747741)
+ SCHEDULED: <2025-12-19 Fri 11:00>
+- DONE [#A] [[PAPERS/2026-ECMFA-LOMBARDI]]
+ todoist-desc:: [ECMFA 2026 - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/691309b6cec10834e115dc0e)
+ todoist-id:: [9699657368](https://app.todoist.com/app/task/9699657368)
+ SCHEDULED: <2025-12-19 Fri 11:00>
+ :LOGBOOK:
+ CLOCK: [2025-12-16 Tue 16:19:41]--[2025-12-19 Fri 10:35:24] => 66:15:43
+ :END:
+- TODO [[MODELS 2027]]
+ todoist-desc:: From: daniel.varro@liu.se
+ todoist-id:: [9794701704](https://app.todoist.com/app/task/9794701704)
+ SCHEDULED: <2026-01-12 Mon>
+- TODO [#B] [[PAPERS/2025-IEEESOFTWARE-AGENTIC-SI]]
+ todoist-desc:: Resubmission of ELSEVIER IST: Your Submission - INFSOF-D-25-00633
+ todoist-id:: [9322035676](https://app.todoist.com/app/task/9322035676)
+ SCHEDULED: <2025-12-26 Fri 14:00>
+ :LOGBOOK:
+ CLOCK: [2025-12-16 Tue 16:19:57]--[2025-12-19 Fri 10:35:24] => 66:15:27
+ :END:
+- TODO [[Deliverable D3.2]]
+ todoist-id:: [9822333606](https://app.todoist.com/app/task/9822333606)
+ todoist-desc:: [MOSAICO D3.2 - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/693c083f94f20a5d73e1824c)
+ SCHEDULED: <2026-01-05 Mon>
+- TODO [[TOOL DEMO TRACK - MODELS 2026 Organizing Committee]]
+ todoist-id:: [9789940282](https://app.todoist.com/app/task/9789940282)
+ todoist-desc:: From: lolaburgueno@uma.es
+ SCHEDULED: <2025-12-30 Tue>
\ No newline at end of file
diff --git a/pages/TOSEM-2025-0054.md b/pages/TOSEM-2025-0054.md
index c290f180..e0b95111 100644
--- a/pages/TOSEM-2025-0054.md
+++ b/pages/TOSEM-2025-0054.md
@@ -13,6 +13,7 @@ parent::
todoist:: https://app.todoist.com/app/task/tosem-2025-0054-reviewer-agreed-6XCQHqwm45x466c8
- ### [[Highlights]]
+ collapsed:: true
- # Annotazioni
(1/4/2025, 14:25:59)
diff --git a/pages/TOSEM-2025-0885.md b/pages/TOSEM-2025-0885.md
new file mode 100644
index 00000000..a2ac7d5e
--- /dev/null
+++ b/pages/TOSEM-2025-0885.md
@@ -0,0 +1,24 @@
+type:: [[REVIEWS]]
+tags::
+year:: 2025
+venue:: [[TOSEM]]
+full-title:: Addressing Visual Impairments with Model-Driven Engineering: A Systematic Literature Review
+date-start:: [[18-11-2025]] - 07:07
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file:: [[@TOSEM-2025-0885]]
+parent::
+todoist:: https://app.todoist.com/app/task/tosem-2025-0885-reviewer-agreed-6f4vvMGPcFvWHVJg
+
+ - SUMMARY
+ - The paper presents a systematic literature review on the application of Model-Driven Engineering to address accessibility needs of visually impaired users. From an initial set of 447 papers, 30 primary studies were selected and analyzed with respect to different aspects including considered impairments, employed modeling techniques, adopted evaluation practices, and reported strengths and limitations. The review highlights that most studies operate at a high level of abstraction, rely extensively on WCAG guidelines, provide limited implementation details, and seldom involve visually impaired end users.
+ - COMMENTS
+ - The paper is about an important and interesting topic discussing the outcomes of a systematic review effort. However, my main concerns about the paper are related to the following points:
+ - A first overall impression is that the manuscript is verbose. The clarity of the contribution would improve significantly by reducing descriptive passages and sharpening the analytical core of the review. For instance, the decreasing trend in publications and the low impact within MDE venues are noted, but the paper does not explain why these observations matter. Is the decline due to intrinsic difficulty? A shift in the community? A mismatch between MDE and accessibility needs?
+ - After reading the paper, I'm still questioning what an effective MDE contribution for visual impairments should entail. The authors note that most works overlook the real nature of visual impairments and provide only abstract role models. However, the paper could be more explicit about what it expected to see from an MDE perspective: how should modeling languages encode impairment-specific requirements? What does "accessibility challenges" mean in practice? What would a meaningful MDE-based pipeline look like? Without articulating this ideal perspective, the criticism remains vague.
+ - Table 1 introduces a scoring system apparently defined by the authors, but the paper does not explain how the criteria were derived, whether existing SLR guidelines influenced them, or whether a structured elicitation process was followed. A short methodological paragraph would strengthen transparency.
+ - Authors repeatedly claim that approaches lack reusability, reusable components, or reusable transformations. However, given the diversity of impairments, contexts, user needs, application domains, and UI constraints, it is not obvious what reusability should realistically mean in this space. The paper should clarify what kinds of artifacts could be reused (e.g., domain-independent modeling constructs, modular transformation patterns, template structures) and what cannot. Without this distinction, the critique risks becoming generic and not fully justified.
+ - The authors observe that DSLs generally capture UI structure rather than accessibility; this is a valuable point, but the analysis should identify what specific modeling constructs are missing and what an accessibility-aware DSL would need to express.
+ - Some structural issues also affect readability. Important figures are referenced long before they appear (e.g., Figure 4), breaking the flow. Certain sentences are abstract or vague ("robust", "transparent", "technically grounded work") and need clarification.
\ No newline at end of file
diff --git a/pages/TSE-2025-06-0540_Proof_hi.md b/pages/TSE-2025-06-0540_Proof_hi.md
new file mode 100644
index 00000000..75a727f1
--- /dev/null
+++ b/pages/TSE-2025-06-0540_Proof_hi.md
@@ -0,0 +1,31 @@
+collapsed:: true
+type:: [[REVIEWS]]
+tags::
+year:: 2025
+venue:: [[TSE]]
+full-title:: Automating UML Class Diagram Generation from Natural Language via Transformer-Based Structured Translation
+date-start:: [[18-09-2025]] - 14:13
+date-submitted::
+external-links::
+status:: [[DONE]]
+deadline-submission::
+file::
+parent::
+todoist:: https://app.todoist.com/app/task/tse-2025-06-0540-now-in-your-reviewer-center-6cRhXHmM2jJw8hjg
+
+ - ### [[Comments]]
+ - Summary: This paper presents an approach to generate UML class diagrams expressed in PlantUML starting from software requirements given in natural language. The approach consists of two main steps. A first phase generate a model conforming to a defined schema by means of a Sequence-to-AST translation. A second step generates PlantUML models by relying on a learning phase leveraging both manually curated and automatically extracted datasets. The approach shows promising results, with the Seq2AST model outperforming baseline Seq2Seq approaches and zero-shot LLMs in terms of F1-score, syntactic correctness, and robustness against hallucinations.
+ - Comments: The problem is timely and the contributions are relevant to the software engineering and model-driven engineering. However, the paper requires a revision to solve presentation issues, unclear methodological details, and insufficient discussion of alternative approaches and evaluation metrics. In particular, my main concerns about the paper are related to the following issues:
+ - The rationale for introducing a custom AST grammar instead of directly using PlantUML's own grammar is not clear. PlantUML is already a stable and widely accepted language. The authors should clarify what limitations they encountered in PlantUML that justified designing a new grammar.
+ - The description of the AST representation needs to be improved. It’s unclear what kind of constraints are expressible in the grammar (e.g., are OCL constraints supported? Multiplicities? Invariants?). Also, the semantics referred to appear to be mainly static semantics.
+ - Several works already explore recommendation or generation of UML elements from context using ML or heuristics. A comparison with these is missing.
+ - The data augmentation step based on rephrasing is underspecified. How is quality controlled? Are rephrasings semantically equivalent to the originals? This is crucial for training reliable models from small supervised datasets.
+ - The connection between the two datasets (one derived from supervised student input, the other from ModelSet) is not sufficiently clarified. Are the model components trained separately? How is consistency ensured?
+ - Figure 1 should be expanded to include all the components and steps discussed in Section III, including the use of ASTs, multi-task training, and inference pipeline.
+ - Algorithm 1 should be contextualized with respect to the end-to-end process described in Figure 1. Their relationship is unclear.
+ - The evaluation uses Precision, Recall, F1, and BLEU-4. However, these metrics are insufficient to assess the semantic equivalence between diagrams. Different UML models can express the same requirement in multiple valid ways. Some structural similarity or model comparison metric (e.g., graph edit distance) should be considered.
+ - To summarize, the paper is about an interesting topic, even though a major revision is required to address the following main issues as discussed above:
+ - Clarify the motivation and role of the custom AST grammar.
+ - Better present the data augmentation, dataset preparation, and model training pipelines.
+ - Improve the figures and align them with the textual description.
+ - More meaningful metrics for model comparison need to be taken into account for the evaluation.
\ No newline at end of file
diff --git a/pages/Teaching/20_21/SE4IOT/InfluxDB.pdf b/pages/Teaching/20_21/SE4IOT/InfluxDB.pdf
deleted file mode 100644
index 89c78817..00000000
Binary files a/pages/Teaching/20_21/SE4IOT/InfluxDB.pdf and /dev/null differ
diff --git a/pages/Templates.md b/pages/Templates.md
index 29634850..ef16aaeb 100644
--- a/pages/Templates.md
+++ b/pages/Templates.md
@@ -72,32 +72,21 @@ template:: JOURNAL-TEMPLATE-OLD
file::
parent::
todoist::
- collapsed:: true
- - ### [[Highlights]]
- ### [[Comments]]
- #.tabular
- - - ### Paper summary
+ - ### Paper summary
-
- - - ### Strengths
+ - ### Strengths
- +
- - - ### Weaknesses
+ - ### Weaknesses
- -
- - - ### Detailed comments for authors
+ - ### 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%>
diff --git a/pages/Writing Challenges.md b/pages/Writing Challenges.md
index e124fe59..e82e9b95 100644
--- a/pages/Writing Challenges.md
+++ b/pages/Writing Challenges.md
@@ -12,7 +12,6 @@ icon:: 👀
- Prompt copilot
- `Vorrei migliorare la mia scrittura creativa prendendo esempio da alcuni classici della letteratura. Puoi aiutarmi con alcuni esempi ed esercizi?`
- [[31-05-2025]]
- collapsed:: true
- DONE **🎯 Sfida di scrittura: “Il messaggio nella macchina”**
- **Prompt:**
- Accendi un vecchio computer in un laboratorio abbandonato. All’avvio, compare un messaggio di errore. Ma qualcosa non torna: il messaggio sembra rivolgersi direttamente a te, come se la macchina stesse cercando di comunicare.
@@ -21,7 +20,7 @@ icon:: 👀
- **Vincolo opzionale:**
- Inserisci una riga di “codice” o output di sistema che sembri al confine tra il tecnico e l’emotivo (es. `Eccezione nel thread "memoria": frammento non trovato.`).
- {{renderer :wordcount_683a9b29-4a30-4226-8c1e-4a6bd11560b3, 300}}
- - Sono le due del pomeriggio, con fatica sono in cammino verso il laboratorio. Fuori il sole è cocente, non si respira, l'aria brucia i polmoni quando entra. Le porte scorrevoli dell'edificio F del laboratorio di genetica si aprono automaticamente appena mi avvicino facendo uscire aria gelida che contrasta con quella bollente dell'esterno. Arrivato al tornello avvicino il mio badge al lettore che fa fatica a riconoscermi. Devo insistere due volte prima di vedere il led verde accendersi e il passaggio sbloccarsi. Abbottono la camicia al collo, il sudore diventa gelido per tutta la schiena. Entro nel mio studio, accendo le luci a led. Anche loro fanno fatica ad attivarsi, sono necessari alcuni secondi prima di vedere la luce bianca accecante. Sono impaziente, voglio vedere il contenuto della chiavetta USB che mi ha dato Franco, esperto genetista fidato a cui ho chiesto un parere in merito alle tracce di sangue trovate sul pantalone della povera Clara. Aveva appena finito il suo turno di pomeriggio quando quel bastardo l'ha bloccata con forza sulla strada di casa. Spero che Franco abbia fatto un buon lavoro, è da incastrare quel figlio di puttana. Inserisco la chiavetta nella porta USB. Il mio vecchio PC, dopo minuti interminabili, si è finalmente messo in moto. Visualizzo il contenuto della chiavetta, contiene molte cartelle, sono necessari diversi secondi prima di riuscire a vedere la cartella con i file di famiglia. Entro dentro e trovo il file referto_clara.pdf. Mi tremano le dita, a malapena riesco a fare doppio click sul pulsante sinistro del mouse. Finalmente riesco ad aprire il documento, e' lento a caricare, vedo solo 5 pagine vuote, a fatica comincia a comparire il contenuto della prima pagina. Ma prima che riesca a leggere una sola riga, lo schermo si spegne. Poi, sullo sfondo nero, compare una scritta: "Eccezione nel thread "memoria": frammento non trovato....
+ - Sono le due del pomeriggio, con fatica sono in cammino verso il laboratorio. Fuori il sole è cocente, non si respira, l'aria brucia i polmoni quando entra. Le porte scorrevoli dell'edificio F del laboratorio di genetica si aprono automaticamente appena mi avvicino facendo uscire aria gelida che contrasta con quella bollente dell'esterno. Arrivato al tornello avvicino il mio badge al lettore che fa fatica a riconoscermi. Devo insistere due volte prima di vedere il led verde accendersi e il passaggio sbloccarsi. Abbottono la camicia al collo, il sudore diventa gelido per tutta la schiena. Entro nel mio studio, accendo le luci a neon. Anche loro fanno fatica ad attivarsi, sono necessari alcuni secondi prima di vedere la luce bianca accecante. Sono impaziente, voglio vedere il contenuto della chiavetta USB che mi ha dato Franco, esperto genetista fidato a cui ho chiesto un parere in merito alle tracce di sangue trovate sul pantalone della povera Clara. Aveva appena finito il suo turno di pomeriggio quando quel bastardo l'ha bloccata con forza sulla strada di casa. Spero che Franco abbia fatto un buon lavoro, è da incastrare quel figlio di puttana. Inserisco la chiavetta nella porta USB. Il mio vecchio PC, dopo minuti interminabili, si è finalmente messo in moto. Visualizzo il contenuto della chiavetta, contiene molte cartelle, sono necessari diversi secondi prima di riuscire a vedere la cartella con i file di famiglia. Entro dentro e trovo il file referto_clara.pdf. Mi tremano le dita, a malapena riesco a fare doppio click sul pulsante sinistro del mouse. Finalmente riesco ad aprire il documento, e' lento a caricare, vedo solo 5 pagine vuote, a fatica comincia a comparire il contenuto della prima pagina. Ma prima che riesca a leggere una sola riga, lo schermo si spegne. Poi, sullo sfondo nero, compare una scritta: "Eccezione nel thread "memoria": frammento non trovato....
- Cosa ne pensa chat?
- Il testo ha un’ottima atmosfera, costruita con cura e attenzione ai dettagli sensoriali. C’è tensione crescente, un ritmo incalzante, e un efficace equilibrio tra elementi realistici e quel tocco di mistero che culmina perfettamente nel messaggio finale. Ecco qualche osservazione e suggerimento per migliorare ulteriormente:
- ---
@@ -52,9 +51,7 @@ icon:: 👀
**`Eccezione nel thread "memoria": frammento non trovato.`**
- [[01-06-2025]]
- collapsed:: true
- TODO **🎯 Sfida di scrittura: “L’inventario delle piccole cose”**
- collapsed:: true
- **Prompt:**
- Scegli un luogo ordinario (una cucina, una fermata dell’autobus, una sala d’attesa, la tua scrivania…) e descrivilo come se fosse un universo interiore. Ogni oggetto presente deve rappresentare un ricordo, un pensiero o un’emozione.
- **Il tuo compito:**
@@ -64,7 +61,6 @@ icon:: 👀
- **“Era lì da sempre, eppure non l’avevo mai davvero visto.”**
- {{renderer :wordcount_683df732-07bf-4df5-866e-645918812343, 300}}
- [[02-06-2025]]
- collapsed:: true
- DOING **🎯 Sfida di scrittura: “Il mestiere dei sogni perduti”**
:LOGBOOK:
CLOCK: [2025-06-02 Mon 21:33:46]
diff --git a/pages/company___ESA.md b/pages/company___ESA.md
new file mode 100644
index 00000000..997ff8d5
--- /dev/null
+++ b/pages/company___ESA.md
@@ -0,0 +1 @@
+- 
\ No newline at end of file
diff --git a/pages/duration.md b/pages/duration.md
new file mode 100644
index 00000000..aad86a01
--- /dev/null
+++ b/pages/duration.md
@@ -0,0 +1 @@
+- cont
\ No newline at end of file
diff --git a/pages/hls__2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.md b/pages/hls__2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.md
new file mode 100644
index 00000000..5fcf94ce
--- /dev/null
+++ b/pages/hls__2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.md
@@ -0,0 +1,2 @@
+file:: [2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.pdf](../assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.pdf)
+file-path:: ../assets/2022_Approvazione_relazione_AR-DI_Sipio-Rinuncia_1760531367087_0.pdf
diff --git a/pages/hls__2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.md b/pages/hls__2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.md
new file mode 100644
index 00000000..16436544
--- /dev/null
+++ b/pages/hls__2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.md
@@ -0,0 +1,2 @@
+file:: [2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.pdf](../assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.pdf)
+file-path:: ../assets/2025-10-MDEIntelligence-MoDELS-WS_1760163488768_0.pdf
diff --git a/pages/hls__2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.md b/pages/hls__2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.md
new file mode 100644
index 00000000..c5cf31ff
--- /dev/null
+++ b/pages/hls__2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.md
@@ -0,0 +1,2 @@
+file:: [2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.pdf](../assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.pdf)
+file-path:: ../assets/2025_Approvazione_relazione_AR-RUBEI-Rinuncia_1760531467122_0.pdf
diff --git a/pages/hls__Calendario_scadenze_Coordinatori_1764006171407_0.md b/pages/hls__Calendario_scadenze_Coordinatori_1764006171407_0.md
new file mode 100644
index 00000000..cbbeb2c7
--- /dev/null
+++ b/pages/hls__Calendario_scadenze_Coordinatori_1764006171407_0.md
@@ -0,0 +1,2 @@
+file:: [Calendario_scadenze_Coordinatori_1764006171407_0.pdf](../assets/Calendario_scadenze_Coordinatori_1764006171407_0.pdf)
+file-path:: ../assets/Calendario_scadenze_Coordinatori_1764006171407_0.pdf
diff --git a/pages/hls__Convenzione_GSSI-INFN_univaq_1757484773208_0.md b/pages/hls__Convenzione_GSSI-INFN_univaq_1757484773208_0.md
new file mode 100644
index 00000000..178d4e2c
--- /dev/null
+++ b/pages/hls__Convenzione_GSSI-INFN_univaq_1757484773208_0.md
@@ -0,0 +1,2 @@
+file:: [Convenzione_GSSI-INFN_univaq_1757484773208_0.pdf](../assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.pdf)
+file-path:: ../assets/Convenzione_GSSI-INFN_univaq_1757484773208_0.pdf
diff --git a/pages/hls__Convocazione-Audizione-2025_1759759982455_0.md b/pages/hls__Convocazione-Audizione-2025_1759759982455_0.md
new file mode 100644
index 00000000..14bc7cf4
--- /dev/null
+++ b/pages/hls__Convocazione-Audizione-2025_1759759982455_0.md
@@ -0,0 +1,2 @@
+file:: [Convocazione-Audizione-2025_1759759982455_0.pdf](../assets/Convocazione-Audizione-2025_1759759982455_0.pdf)
+file-path:: ../assets/Convocazione-Audizione-2025_1759759982455_0.pdf
diff --git a/pages/hls__Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.md b/pages/hls__Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.md
new file mode 100644
index 00000000..d5dbb873
--- /dev/null
+++ b/pages/hls__Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.md
@@ -0,0 +1,13 @@
+file:: [Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.pdf](../assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.pdf)
+file-path:: ../assets/Convocazione_CD_ExEmerge_2025.12.17_1765972506752_0.pdf
+
+- ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 69429a33-8e6f-447d-ac26-253af028914b
+ 5. BILANCIO E CONTABILITÀ
+- ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 69429b19-0a88-450b-ad31-ee8a9bf8884d
+ 9. RICERCA
\ No newline at end of file
diff --git a/pages/hls__Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.md b/pages/hls__Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.md
new file mode 100644
index 00000000..cc749e64
--- /dev/null
+++ b/pages/hls__Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.md
@@ -0,0 +1,2 @@
+file:: [Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.pdf](../assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.pdf)
+file-path:: ../assets/Convocazione_DISIM_03.12.2025_-_INTEGRATO_1764771366566_0.pdf
diff --git a/pages/hls__Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.md b/pages/hls__Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.md
new file mode 100644
index 00000000..fc3540c6
--- /dev/null
+++ b/pages/hls__Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.md
@@ -0,0 +1,2 @@
+file:: [Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.pdf](../assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.pdf)
+file-path:: ../assets/Convocazione_DISIM_10.09.2025_-_INTEGRATO_1757508346648_0.pdf
diff --git a/pages/hls__Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.md b/pages/hls__Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.md
new file mode 100644
index 00000000..0f93f555
--- /dev/null
+++ b/pages/hls__Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.md
@@ -0,0 +1,2 @@
+file:: [Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.pdf](../assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.pdf)
+file-path:: ../assets/Convocazione_DISIM_12.11.2025_-_INTEGRATO_1762955187437_0.pdf
diff --git a/pages/hls__Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.md b/pages/hls__Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.md
new file mode 100644
index 00000000..45016e1a
--- /dev/null
+++ b/pages/hls__Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.md
@@ -0,0 +1,43 @@
+file:: [Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.pdf](../assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.pdf)
+file-path:: ../assets/Convocazione_DISIM_15.10.2025_-_INTEGRATO-_1760531199552_0.pdf
+
+- Approvazione relazione attività Assegno di Ricerca dott. Claudio Di Sipio – responsabile scientifico prof. Davide Di Ruscio.
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68ef936d-6021-40e8-993e-c78676f55faf
+- Approvazione relazione attività Assegno di Ricerca dott. Riccardo Rubei – responsabile scientifico prof. Davide Di Ruscio.
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68ef937a-3d89-4739-b4a2-e73c924a79fc
+- Richiesta proroga Borsa di Ricerca dott. Damiano Di Vincenzo – responsabile scientifico prof. Alfonso Pierantonio
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ef942a-5b23-422b-8d88-4c49778a16d7
+- Approvazione relazione tecnico-scientifica RTD b) secondo anno (01.10.2024 – 30.09.2025) dott. Juri Di Rocco
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68ef94d6-f616-4fa4-95ad-754fb3874601
+- COMUNICAZIONI
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68ef9735-4af7-4e7e-909d-98d1f1196f19
+- Nomina Commissioni di Dipartimento
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68ef9bb4-c1e9-4a97-85a3-9a80679645ab
+- Nomina Commissione didattica paritetica docenti-studenti DISIM triennio accademico 2025/20262026/2027-2027/2028 – sostituzione membro
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68ef9c5e-f8c7-45e8-8b2d-8eb38117c8d5
+- Nomina Delegati di Dipartimento
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68ef9cd5-4623-42a3-b5d6-75212323e48b
\ No newline at end of file
diff --git a/pages/hls__D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.md b/pages/hls__D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.md
new file mode 100644
index 00000000..b88fd977
--- /dev/null
+++ b/pages/hls__D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.md
@@ -0,0 +1,2 @@
+file:: [D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.pdf](../assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.pdf)
+file-path:: ../assets/D2_1-InternalReview_version_20250827-agd220250907_1758720457899_0.pdf
diff --git a/pages/hls__DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.md b/pages/hls__DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.md
new file mode 100644
index 00000000..a07e781a
--- /dev/null
+++ b/pages/hls__DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.md
@@ -0,0 +1,135 @@
+file:: [DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.pdf](../assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.pdf)
+file-path:: ../assets/DR_ICT_APPROVAZIONE_ATTI_XLI_CICLO_WEB_1760360894529_0.pdf
+
+- 1 NISAR Fatima
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ecf9ce-81bc-471c-94f4-06be923f5ff1
+- 2 PELLONE Katiuscia
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ecf9e5-04a9-4045-99da-a1e3cb737b35
+- 3 GIONA Valentino
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ecf9fd-fe29-4224-9cd8-9014f68fdced
+- 4 COLLI Giordano
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ecfa05-7d25-4847-8fab-05a52f7f7f96
+- 5 GRANDE Federico
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ecfa0e-4146-47ce-9b9f-225e708dc1cf
+- 6 RAZA Muhammad Mudassar
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68ecfa16-6986-4f5e-a69b-e793c43b7a61
+- NANNI Gianluca
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68ecfab2-c50c-4c53-8e7a-9d8ff511c9f7
+- Metodologie di progetto a livello sistema per applicazioni real-time embedded su piattaforme parallele eterogenee riconfigurabili”
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: blue
+ id:: 68ecfac2-4348-442e-8e26-fa99e988033f
+ hl-stamp:: 1760361318466
+- MUGHAL Abdul Basit
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68ecfb18-f881-4bfd-bbea-69920b5aa74d
+- GANESH Venkata Subramaniyan
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68ecfb2f-0d34-426c-ac2f-bd8ec548147c
+- rogettazione e Sviluppo di Ambienti Intelligenti per la Valorizzazione del Patrimonio Culturale tramite Gamification e Realtà Aumentata
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: blue
+ id:: 68ecfb4e-6d06-407d-8ae4-71387deb5c0d
+- Sistema di raccolta e analisi di dati provenienti da un sistema di videosorveglianza di una rete di comuni del cratere del sisma 2009 per la progettazione di un sistema di Smart Urban Living
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: blue
+ id:: 68ecfb5d-37f6-4fa8-b320-3c2c845af8dd
+- BILAL Hafiz Anas
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68ecfb71-cc6f-4d08-b54d-44b2644e2594
+- Sistemi Software Agili e Motivazionali per la Mobilità Sostenibile: Microservizi e Gamification al Servizio di Cittadini e Imprese
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: blue
+ id:: 68ecfb98-9a60-4033-8b40-90b7abd3194c
+- MAAMOOR Rida
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: green
+ id:: 68ecfbb6-3b34-4145-86df-c215def56aa7
+- tudio di architetture e protocolli per reti veicolari nell’ambito della mobilità CCAM (Cooperative, Connected and Automated Mobility
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: blue
+ id:: 68ecfc10-e7ff-4c7c-a972-75a6c424b785
+- MENGISTU Minase Mekete
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: green
+ id:: 68ecfc29-3506-4656-8847-cb584846ac9b
+- ngegneria del software con sistemi multi-agente basati su LLM
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: blue
+ id:: 68ecfc39-0e6d-4cf6-bb05-e9db606d82a5
+ hl-stamp:: 1760361572791
+- Machine Learning applicato all’astrofisica
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: blue
+ id:: 68ecfc60-f07d-482e-a0b6-b5ac60f864d9
+- MUSTAFA Muzzamil
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: green
+ id:: 68ecfc77-a51f-4bce-bac6-886e023990cc
+- AHMED Ayaz
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: green
+ id:: 68ecfca3-81db-4791-8c34-db6a07a5fde4
+- Generazione e ottimizzazione model-based di scenari di test per sistemi avanzati di assistenza alla guida (ADAS) in co-simulazione
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: blue
+ id:: 68ecfcaf-736d-468a-8894-f144c7a5529b
+- VEGLIANTE Davide
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68ecfce3-ef15-450e-8131-d3b3cac77f8d
+- ZAHRA Tazeen
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68ecfcf9-61d1-431d-97ac-22a7a5736c7a
+- SRIVASTAVA Aditya
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68ecfd12-2d01-4b73-9caf-0da45837c9e2
+- OTHMAN Ali Mohamed Saed
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68ed3720-5254-46fc-981a-b6ddc9b19bcf
\ No newline at end of file
diff --git a/pages/hls__Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.md b/pages/hls__Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.md
index eab2ba05..83fe0d74 100644
--- a/pages/hls__Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.md
+++ b/pages/hls__Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.md
@@ -151,4 +151,9 @@ file-path:: ../assets/Decreto_Ministeriale_n.226_del_14-12-2021_1711484078266_0.
ls-type:: annotation
hl-page:: 7
hl-color:: green
- id:: 6831df2a-df4b-430c-88c6-f5a74b3504c8
\ No newline at end of file
+ id:: 6831df2a-df4b-430c-88c6-f5a74b3504c8
+- ls-type:: annotation
+ hl-page:: 10
+ hl-color:: green
+ id:: 68ab4d45-dcd9-4e6a-a204-2cff1e9989bc
+ 6. Gli oneri per il finanziamento delle borse di studio di cui al comma 5 possono essere coperti mediante convenzione con soggetti estranei all’amministrazione universitaria, secondo modalità e procedure deliberate dagli organi competenti delle università
\ No newline at end of file
diff --git a/pages/hls__Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.md b/pages/hls__Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.md
new file mode 100644
index 00000000..e8bab2e1
--- /dev/null
+++ b/pages/hls__Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.md
@@ -0,0 +1,43 @@
+file:: [Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.pdf](../assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.pdf)
+file-path:: ../assets/Ordine_del_giorno_CdA_04_12_2025_1764843281660_0.pdf
+
+- ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 693160b0-6a69-410b-a49a-a9cf06dd4073
+ 8. Contratto Prof. Alessandro Neri: Rinnovo;
+- Comunicazioni del Presidente
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 693160c3-b9e7-4673-8216-abeed18301cc
+- Preconsuntivo 2025 e Budget 2026;
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 6931623f-fe44-4f4b-b56a-9ba822711b5a
+- Piano triennale 2026-2028
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 69316743-c79e-4200-934d-85d152b86d60
+- Personale: adeguamento livelli, Buoni pasto, MBO, Regolamento Welfare, Destinazione TFR
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 69316f7e-d361-4907-af0e-82567bdde4d6
+- Regolamenti aziendali: Personale, Acquisti, Missioni;
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 69317290-2997-4b52-b2ad-552b40db9037
+- Comitato scientifico: nomina membri
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 693173af-8ba6-4ee8-8968-64ff8bad3023
+- ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 6931769f-99fd-4d86-bffc-52319c897578
+ 11. Modello 231/2001: aggiornamenti
\ No newline at end of file
diff --git a/pages/hls__Piano_2026-28_V1_1764843299066_0.md b/pages/hls__Piano_2026-28_V1_1764843299066_0.md
new file mode 100644
index 00000000..2aaae55b
--- /dev/null
+++ b/pages/hls__Piano_2026-28_V1_1764843299066_0.md
@@ -0,0 +1,2 @@
+file:: [Piano_2026-28_V1_1764843299066_0.pdf](../assets/Piano_2026-28_V1_1764843299066_0.pdf)
+file-path:: ../assets/Piano_2026-28_V1_1764843299066_0.pdf
diff --git a/pages/hls__REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.md b/pages/hls__REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.md
index d970d775..106b5a2c 100644
--- a/pages/hls__REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.md
+++ b/pages/hls__REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_2023_1705409017565_0.md
@@ -40,4 +40,44 @@ file-path:: ../assets/REGOLAMENTO_Dottorati_Ricerca_Modifica_DR_rep_597_01_06_20
ls-type:: annotation
hl-page:: 4
hl-color:: green
- id:: 6831e0f1-2fb6-4657-81e5-d5f1f849982d
\ No newline at end of file
+ id:: 6831e0f1-2fb6-4657-81e5-d5f1f849982d
+- due valutatori
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d620-5ee3-4aff-a09d-e806e025badc
+- istituzioni di due paesi europei diversi da quello in cui viene discussa
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d627-8af7-4b0d-ac36-603139ce7039
+- almeno un membro
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d637-b077-40c5-86e4-9d08fbad5a7e
+- paese europeo diverso
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d645-b4ba-445c-b2dc-d963a87efa00
+- lingua
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d652-0585-48bb-b3e2-cb038f9818f4
+- soggiorno di almeno tre mes
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d65b-fa58-46ef-b08f-21b0bb3ab7be
+- una o più delle condizioni di cui alle lettere a), b) c) e d)
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: green
+ id:: 6901d669-6055-4d90-868d-e9ae1a83a919
+- International Doctorate
+ ls-type:: annotation
+ hl-page:: 14
+ hl-color:: red
+ id:: 6901d687-84a6-4b31-8d15-967b5a2f925e
\ No newline at end of file
diff --git a/pages/hls__RELAZIONE_Nucleo_2024_1759759962335_0.md b/pages/hls__RELAZIONE_Nucleo_2024_1759759962335_0.md
new file mode 100644
index 00000000..eea58eb3
--- /dev/null
+++ b/pages/hls__RELAZIONE_Nucleo_2024_1759759962335_0.md
@@ -0,0 +1,33 @@
+file:: [RELAZIONE_Nucleo_2024_1759759962335_0.pdf](../assets/RELAZIONE_Nucleo_2024_1759759962335_0.pdf)
+file-path:: ../assets/RELAZIONE_Nucleo_2024_1759759962335_0.pdf
+
+- Si ribadisce che le autovalutazioni hanno lo scopo di sviluppare le capacità di auto-percezione e autocritica, nell’ottica di individuare margini di sviluppo e miglioramento
+ ls-type:: annotation
+ hl-page:: 97
+ hl-color:: green
+ id:: 68e3cec4-61ff-41f0-b1c6-5b38b38c2059
+- Per la selezione dei CdS, dei Dipartimenti e corsi di dottorato da audire il Nucleo ha proceduto a una preliminare analisi degli indicatori ANVUR per il monitoraggio annuale (con particolare riferimento al set minimo di indicatori della SMA) definendo un programma di audizioni che fosse rappresentativo delle diverse realtà dell’Ateneo.
+ ls-type:: annotation
+ hl-page:: 33
+ hl-color:: green
+ id:: 68e3cf06-8829-4450-9140-1c09232fa355
+- il NdV rileva che l’Ateneo non si accerta che i Dipartimenti e i Corsi di Dottorato di Ricerca definiscano con chiarezza e trasparenza i criteri e le modalità di distribuzione interna delle risorse (economiche, sia per i Dipartimenti e i Dottorati, e di personale per i Dipartimenti) assegnate a sostegno della ricerca (anche dottorale) e della terza missione/impatto sociale, coerentemente con il programma strategico proprio e dell'Ateneo e con le indicazioni dello stesso sull’utilizzazione delle risorse assegnat
+ ls-type:: annotation
+ hl-page:: 46
+ hl-color:: green
+ id:: 68e3cf51-64c1-44b1-ad53-e8f45b74c99b
+- Iscritti al primo anno di Corsi di dottorato che hanno conseguito il titolo di accesso in altro Ateneo
+ ls-type:: annotation
+ hl-page:: 52
+ hl-color:: green
+ id:: 68e3cf7d-9acb-4bb1-bbf7-14621a0dd805
+- La finalità che il NdV vuole conseguire è quella di offrire un contributo al processo di Assicurazione della Qualità nei Corsi dei Dottorato di Ricerca, tale processo ha infatti lo scopo di Relazione annuale 2023 96 identificare e segnalare i punti di forza e debolezza verso cui indirizzare le future azioni e si basa su una lettura indipendente dei documenti, dei processi e dell’opinione di studenti e colleghi
+ ls-type:: annotation
+ hl-page:: 95
+ hl-color:: green
+ id:: 68fb6fe9-147f-4605-a4d9-2bebe0ae339c
+- L’audizione del Dottorato si configura come una verifica condivisa tra il Nucleo e il Corso di Dottorato di Ricerca delle informazioni presenti nei documenti dell’AQ, ovvero:• scheda Anagrafe Dottorati• scheda valutazione ANVUR del Dottorato• indagine Almalaurea Dottorati• verbali Collegio docenti (ultimi 24 mesi);• griglia di autovalutazione Ambito D.PHD compilata;• sito web del Dottorato;• altri documenti ritenuti di interess
+ ls-type:: annotation
+ hl-page:: 96
+ hl-color:: green
+ id:: 68fb6ffa-898c-4f02-90bb-b6bed5be89c3
\ No newline at end of file
diff --git a/pages/hls__Radiolabs_2025-1_1766433218681_0.md b/pages/hls__Radiolabs_2025-1_1766433218681_0.md
new file mode 100644
index 00000000..12ec8ef7
--- /dev/null
+++ b/pages/hls__Radiolabs_2025-1_1766433218681_0.md
@@ -0,0 +1,2 @@
+file:: [Radiolabs_2025-1_1766433218681_0.pdf](../assets/Radiolabs_2025-1_1766433218681_0.pdf)
+file-path:: ../assets/Radiolabs_2025-1_1766433218681_0.pdf
diff --git a/pages/hls__Report_Assegno_2025_1760531396007_0.md b/pages/hls__Report_Assegno_2025_1760531396007_0.md
new file mode 100644
index 00000000..45a7ffd5
--- /dev/null
+++ b/pages/hls__Report_Assegno_2025_1760531396007_0.md
@@ -0,0 +1,2 @@
+file:: [Report_Assegno_2025_1760531396007_0.pdf](../assets/Report_Assegno_2025_1760531396007_0.pdf)
+file-path:: ../assets/Report_Assegno_2025_1760531396007_0.pdf
diff --git a/pages/hls__Report_JURI_RTDB_2025_2026_1760530960125_0.md b/pages/hls__Report_JURI_RTDB_2025_2026_1760530960125_0.md
new file mode 100644
index 00000000..5ad92ad6
--- /dev/null
+++ b/pages/hls__Report_JURI_RTDB_2025_2026_1760530960125_0.md
@@ -0,0 +1,2 @@
+file:: [Report_JURI_RTDB_2025_2026_1760530960125_0.pdf](../assets/Report_JURI_RTDB_2025_2026_1760530960125_0.pdf)
+file-path:: ../assets/Report_JURI_RTDB_2025_2026_1760530960125_0.pdf
diff --git a/pages/hls__SW-2025-10-0161_Proof_hi_1766502869265_0.md b/pages/hls__SW-2025-10-0161_Proof_hi_1766502869265_0.md
new file mode 100644
index 00000000..dba0b30f
--- /dev/null
+++ b/pages/hls__SW-2025-10-0161_Proof_hi_1766502869265_0.md
@@ -0,0 +1,8 @@
+file:: [SW-2025-10-0161_Proof_hi_1766502869265_0.pdf](../assets/SW-2025-10-0161_Proof_hi_1766502869265_0.pdf)
+file-path:: ../assets/SW-2025-10-0161_Proof_hi_1766502869265_0.pdf
+
+- (to which an explanation was previously assigned)
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 694ab342-364a-4c82-a537-695ff0a4bcb3
\ No newline at end of file
diff --git a/pages/hls__SW-2025-10-0163_Proof_hi_1766500604129_0.md b/pages/hls__SW-2025-10-0163_Proof_hi_1766500604129_0.md
new file mode 100644
index 00000000..8b5bed6c
--- /dev/null
+++ b/pages/hls__SW-2025-10-0163_Proof_hi_1766500604129_0.md
@@ -0,0 +1,2 @@
+file:: [SW-2025-10-0163_Proof_hi_1766500604129_0.pdf](../assets/SW-2025-10-0163_Proof_hi_1766500604129_0.pdf)
+file-path:: ../assets/SW-2025-10-0163_Proof_hi_1766500604129_0.pdf
diff --git a/pages/hls__SWEN_RTR_2025_Report-2_1752779890753_0.md b/pages/hls__SWEN_RTR_2025_Report-2_1752779890753_0.md
new file mode 100644
index 00000000..77565955
--- /dev/null
+++ b/pages/hls__SWEN_RTR_2025_Report-2_1752779890753_0.md
@@ -0,0 +1,24 @@
+file:: [SWEN_RTR_2025_Report-2_1752779890753_0.pdf](../assets/SWEN_RTR_2025_Report-2_1752779890753_0.pdf)
+file-path:: ../assets/SWEN_RTR_2025_Report-2_1752779890753_0.pdf
+
+- This report synthesizes the content and outcomes of the retreat, drawing from both formal sessions and transcripted discussion
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 68794d08-6e82-479c-a8e4-97e2e2a8a976
+- A proposed timeline set the completion of the first consolidated version by midSeptember 2025, aligning with the start of the academic year.
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68794d6d-38a0-4e39-81b5-394854f8310c
+ hl-stamp:: 1752780148675
+- SWEn
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: red
+ id:: 68794d9a-c21d-43b0-9256-74395ecb6d3a
+- SWEn’s
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: red
+ id:: 68794dc1-c7cd-4c49-8a54-59b7e592c43c
\ No newline at end of file
diff --git a/pages/hls__SWEN_RTR_2025_Report-3_1752780760755_0.md b/pages/hls__SWEN_RTR_2025_Report-3_1752780760755_0.md
new file mode 100644
index 00000000..522b96d4
--- /dev/null
+++ b/pages/hls__SWEN_RTR_2025_Report-3_1752780760755_0.md
@@ -0,0 +1,2 @@
+file:: [SWEN_RTR_2025_Report-3_1752780760755_0.pdf](../assets/SWEN_RTR_2025_Report-3_1752780760755_0.pdf)
+file-path:: ../assets/SWEN_RTR_2025_Report-3_1752780760755_0.pdf
diff --git a/pages/hls__UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.md b/pages/hls__UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.md
new file mode 100644
index 00000000..c3f1f16d
--- /dev/null
+++ b/pages/hls__UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.md
@@ -0,0 +1,38 @@
+file:: [UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.pdf](../assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.pdf)
+file-path:: ../assets/UNIVAQ_LG_audizioni_DOTTORATO_Agg_AVA3_febb_2025_1759759493525_0.pdf
+
+- scheda valutazione ANVUR del Dottorato
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68e3ccde-2685-4827-b67e-bb0117622f86
+- indagine Almalaurea Dottorati
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68e3cce5-1215-4d79-b582-64799d63b8e4
+- verbali Collegio docenti (ultimi 24 mesi
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68e3ccec-10c5-4e63-9fde-b8cb9befe103
+- griglia di autovalutazione Ambito D.PHD compilata
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68e3ccf1-bc03-450b-9602-7c5200b5d4d0
+- sito web del Dottorato
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68e3ccfa-c890-46a7-a245-333e0ce7a12f
+- Ambito D.PHD
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68e3cd12-1ce4-44e2-83ee-5cb6ffe4ede5
+- Prof. Bruno Moncharmont,
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 6922c6e5-3223-4b1d-83d7-39e6a443f9bc
\ No newline at end of file
diff --git a/pages/hls__UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.md b/pages/hls__UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.md
new file mode 100644
index 00000000..51fe0953
--- /dev/null
+++ b/pages/hls__UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.md
@@ -0,0 +1,129 @@
+file:: [UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.pdf](../assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.pdf)
+file-path:: ../assets/UniPg_Documento_di_intervento_multidisciplinare_rev_02_03_2023_1753711335783_0.pdf
+
+- Multi-disciplinary action aimed at supporting the gender equality education in Palestine
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: green
+ id:: 6887884d-9fdf-4135-b06d-65ed75c76950
+- la promozione della creazione di un sistema di formazione avanzata integrato che possa incidere sulle politiche di sviluppo e di crescita in Palestina, con uno particolare sguardo all’educazione all’uguaglianza di genere
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68878898-b744-41ae-8884-87c76b101040
+- vasta azione di mobilità di docenti italiani e palestinesi e di studenti palestinesi.
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 688788a1-18c3-48e8-ad14-c655a2aee1ee
+- scambio di competenze, conoscenze e buone prassi tra i partners
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 688788c8-e8d1-47c3-b67d-b3a5d212d4a2
+- Attività 1.2. Attivazione di posizioni di PhD espressamente destinate a studenti palestinesi
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 688789c4-2c00-4edb-bccc-dadb610a69b7
+- O.S.1. Promuovere lo scambio di conoscenze e buone prassi al fine di potenziare le competenze delle Università Palestinesi
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 688789cb-ce1d-4035-b90e-cc45405f4efb
+- O.S.2. Education/Formazione
+ ls-type:: annotation
+ hl-page:: 6
+ hl-color:: green
+ id:: 688789e0-2a51-4011-85ac-9669c875f419
+- Attività 2.3. Attivazione di posizioni di PhD espressamente destinate a studenti Palestinesi
+ ls-type:: annotation
+ hl-page:: 6
+ hl-color:: green
+ id:: 688789e5-28b2-4f1f-bd2d-226488786540
+- promuovere le capacità tecnologiche dei settori industriali e artigianali, garantendo un aumento significativo dell'accesso alle tecnologie dell'informazione e della comunicazione
+ ls-type:: annotation
+ hl-page:: 8
+ hl-color:: green
+ id:: 68878a05-28ab-4769-8b14-9e281d2c8ca1
+- Information and communication technology (ICT
+ ls-type:: annotation
+ hl-page:: 8
+ hl-color:: green
+ id:: 68878a0a-ee6a-4be8-9cb3-b8b4c151ca52
+- Attività 5.2. Attivazione di posizioni di PhD espressamente destinate a studenti palestinesi
+ ls-type:: annotation
+ hl-page:: 9
+ hl-color:: green
+ id:: 68878a2b-6ad1-4916-94d6-0b517999964e
+- Borse di Dottorato di ricerca
+ ls-type:: annotation
+ hl-page:: 9
+ hl-color:: green
+ id:: 68878a39-d9c4-48c4-be96-127479b92b8d
+- rete quattro Atenei italiani e cinque Atenei palestinesi (l’Università degli Studi di Perugia, l’Università Politecnica delle Marche, l’Università degli Studi dell’Aquila e la Scuola Superiore Sant'Anna di Pisa
+ ls-type:: annotation
+ hl-page:: 10
+ hl-color:: green
+ id:: 68878aa1-5fbc-4d5f-a6fd-ad7d5104090b
+- An-Najah National University; l’Al-Quds University, la Palestine Technical University – Kadoorie, Bethlehem University e l’Arab American University
+ ls-type:: annotation
+ hl-page:: 10
+ hl-color:: blue
+ id:: 68878aa8-eb37-43b1-b57f-7825e1066334
+ hl-stamp:: 1753713323818
+- l’educazione in senso ampio e la formazione degli insegnanti, la sensibilizzazione circa i diritti umani, l’implementazione delle scuole di diritto, la ricerca e le attività educative sul diritto comparato, nonché l’innovazione tecnologica.
+ ls-type:: annotation
+ hl-page:: 10
+ hl-color:: green
+ id:: 68878ac8-d4bc-4fc6-9213-9ed5d260fe91
+- Education, Government and Civil Society (Legal and judicial development, Human rights, Women’s equality organisations and institutions), Communications and Industry (Information and communication technology
+ ls-type:: annotation
+ hl-page:: 10
+ hl-color:: blue
+ id:: 68878b16-19d9-414b-9093-1e28a9f37ede
+- ICT, Industrial development,11 Engineering, Technological research and development)
+ ls-type:: annotation
+ hl-page:: 10
+ hl-color:: blue
+ id:: 68878b1e-0b73-4e45-8b75-815b01698b62
+- - Verranno attribuite 9 borse di dottorato espressamente riservate a studenti palestinesi altamente motivati a operare nella cooperazione internazionale e a svolgere ricerca nei settori di interesse negli ambiti sopra indicati
+ ls-type:: annotation
+ hl-page:: 11
+ hl-color:: blue
+ id:: 68878b2c-c434-4a11-b458-4989211b2880
+- L’intervento ha lo scopo di costruire un’infrastruttura resiliente e promuovere l'innovazione e uno sviluppo industriale e artigianale equo, responsabile e sostenibile. Ha altresì l’obiettivo di potenziare la ricerca scientifica, promuovere le capacità tecnologiche dei settori industriali e artigianali, garantendo un aumento significativo dell'accesso alle tecnologie dell'informazione e della comunicazione
+ ls-type:: annotation
+ hl-page:: 12
+ hl-color:: green
+ id:: 68878b48-c2d4-4f27-9752-076c6bfb6d9f
+- Attività 1.2. Attivazione di posizioni di PhD espressamente destinate a studenti palestinesi.1.2.1 Attivazione di n. 9 borse di dottorato (complessive per i 5 obiettivi specifici) presso le Università Italiane coinvolte nella rete progettuale espressamente destinate a studenti palestinesi nei main topics individuati.
+ ls-type:: annotation
+ hl-page:: 17
+ hl-color:: green
+ id:: 688790f6-a019-4418-9cee-d661457baf32
+- O.S.5. Communications&Industry/Innovazione tecnologica R.54.1. Lo sviluppo di infrastrutture di qualità, affidabili, sostenibili e resilienti, comprese le infrastrutture regionali e transfrontaliere, per sostenere lo sviluppo economico e il benessere umano, con particolare attenzione alla possibilità di accesso equo per tutti. R.5.2. La creazione di piccole o grandi imprese che favoriscano la resilienza dei giovani e la promozione del lavoro femminile. R.5.3. L’aggiornamento delle infrastrutture e l’ammodernamento delle industrie per renderle sostenibili, con maggiore efficienza delle risorse da utilizzare e una maggiore adozione di tecnologie pulite e rispettose dell'ambiente e dei processi industriali. R.5.4. Il potenziamento della ricerca scientifica, attraverso la promozione delle capacità tecnologiche dei settori industriali, anche incoraggiando l'innovazione e aumentando in modo sostanziale il numero dei lavoratori dei settori ricerca R.5.5. L’aumento significativo dell'accesso alle tecnologie dell'informazione e della comunicazion
+ ls-type:: annotation
+ hl-page:: 19
+ hl-color:: green
+ id:: 68879124-c8db-41bc-8409-2a088c52ae37
+- ’Università degli Studi dell’Aquila
+ ls-type:: annotation
+ hl-page:: 20
+ hl-color:: green
+ id:: 68879148-1f5d-48e5-beca-ffff96d1e76f
+- Communications&Industry/Innovazione tecnologica- La percentuale di incremento delle imprese dei settori ad alta e media tecnologia- L’incremento del numero delle piccole o grandi imprese che favoriscono la promozione del lavoro femminile.- La percentuale di incremento dell’adozione di tecnologie pulite e rispettose dell'ambiente e dei processi industriali.- La percentuale di incremento delle risorse finanziarie messe a disposizione per la ricerca scientifica sui settori dell’industria e10%15%10%20%- Determinazioni del piano operativo- Relazioni di valutazione intermedie e finale- Valutazioni a cura del Valuatore Esterno- Sviluppo di infrastrutture di qualità, affidabili, sostenibili e resilienti, comprese le infrastrutture regionali e transfrontaliere, per sostenere lo sviluppo economico e il benessere umano, con particolare attenzione alla possibilità di accesso equo per tutti.- Creazione di piccole o grandi imprese che
+ ls-type:: annotation
+ hl-page:: 32
+ hl-color:: green
+ id:: 68879172-c740-45b9-8533-44609dc624b6
+- Il numero dei giovani e delle giovani che accedono ai dottorati di ricerca in materie scientifiche e tecnologiche
+ ls-type:: annotation
+ hl-page:: 33
+ hl-color:: blue
+ id:: 6887917b-696a-43a6-99e2-f3afb2e36051
+- Attivazione di n. 9 borse di dottorato(complessive per i 5 obiettivi specifici) presso le Università Italiane coinvolte nella rete progettuale espressamente destinate a studenti palestinesi nei main topics individuat
+ ls-type:: annotation
+ hl-page:: 36
+ hl-color:: green
+ id:: 6887919d-a485-4913-849a-7f66214f0b8e
\ No newline at end of file
diff --git a/pages/hls__blob.md b/pages/hls__blob.md
index 268571e6..4d638d03 100644
--- a/pages/hls__blob.md
+++ b/pages/hls__blob.md
@@ -5,4 +5,9 @@ file-path:: file://C:/Users/david/Zotero/storage/MUBUR4J5/blob.pdf
ls-type:: annotation
hl-page:: 2
hl-color:: green
- id:: 6839d240-e828-4ebd-861e-2f97e1adb987
\ No newline at end of file
+ id:: 6839d240-e828-4ebd-861e-2f97e1adb987
+- ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 68d5408b-5055-4173-831e-7099bfe4931a
+ 2. Nel caso di progetti di ricerca di carattere nazionale, europeo ed internazionale, i contratti di ricerca hanno durata biennale prorogabile fino a un ulteriore anno, in ragione delle specifiche esigenze relative agli obiettivi e alla tipologia del progetto
\ No newline at end of file
diff --git a/pages/hls__blob.php.md b/pages/hls__blob.php.md
new file mode 100644
index 00000000..61a5e4c9
--- /dev/null
+++ b/pages/hls__blob.php.md
@@ -0,0 +1,43 @@
+file:: [blob.php.pdf](file://C:/Users/david/Zotero/storage/3NYMMVBB/blob.php.pdf)
+file-path:: file://C:/Users/david/Zotero/storage/7ZTPLJQC/blob.php.pdf
+
+- Gli incarichi di ricerca hanno durata minima di un anno e durata massima, compresi eventuali rinnovi o proroghe, di tre anni, anche non continuativi
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 69297277-2ddf-4104-81a8-83ee8c65a9e2
+- Il conferimento di incarichi di ricerca avviene previo espletamento di procedure selettive che assicurano la valutazione comparativa dei candidati mediante esame dei titoli e delle pubblicazioni ed eventuale colloquio a opera di una commissione
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 6929728b-7242-4b4d-8808-7f8f3ebfc9ff
+- l’Università può attivare procedure di conferimento diretto, mediante avvisi pubblicati nel proprio sito internet ai fini della raccolta delle manifestazioni di interesse da parte dei candidati.
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 692972a5-a982-42c6-986c-82044e13290c
+- l'incarico di ricerca è conferito direttamente al candidato con un profilo scientifico-professionale ritenuto idoneo allo svolgimento del progetto stesso.
+ ls-type:: annotation
+ hl-page:: 1
+ hl-color:: green
+ id:: 692972b0-1a4a-4c28-ad55-ad14d7f33550
+- . Incarichi di ricerca finanziati con altre risorse disponibili sul bilancio dei Dipartimenti.
+ ls-type:: annotation
+ hl-page:: 2
+ hl-color:: green
+ id:: 6929737c-0fb3-4f8c-be41-d8b3020a00ad
+- , di titolo di laurea magistrale o a ciclo unico o di titolo conseguito all’estero valutato equivalente al solo fine del conferimento dell’incarico di ricerca dalla Commissione giudicatrice da non più di sei anni e di un curriculum idoneo all'assistenza allo svolgimento di attività di ricerca.
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 6929739f-0a0e-4212-9cb5-3d305f007b67
+- potrà esser
+ ls-type:: annotation
+ hl-page:: 4
+ hl-color:: green
+ id:: 692973b7-5e82-4927-b113-d2a0e73987a5
+- l’indicazione del trattamento economico complessivo
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 692973ea-228f-46b4-8c0f-dc8223c38e5f
\ No newline at end of file
diff --git a/pages/hls__brogliaccio_seduta_del_12.03.2025_1764771297422_0.md b/pages/hls__brogliaccio_seduta_del_12.03.2025_1764771297422_0.md
new file mode 100644
index 00000000..4b0da42c
--- /dev/null
+++ b/pages/hls__brogliaccio_seduta_del_12.03.2025_1764771297422_0.md
@@ -0,0 +1,2 @@
+file:: [brogliaccio_seduta_del_12.03.2025_1764771297422_0.pdf](../assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.pdf)
+file-path:: ../assets/brogliaccio_seduta_del_12.03.2025_1764771297422_0.pdf
diff --git a/pages/hls__brogliaccio_seduta_del_20250910_1757508393988_0.md b/pages/hls__brogliaccio_seduta_del_20250910_1757508393988_0.md
new file mode 100644
index 00000000..ad4f27cb
--- /dev/null
+++ b/pages/hls__brogliaccio_seduta_del_20250910_1757508393988_0.md
@@ -0,0 +1,8 @@
+file:: [brogliaccio_seduta_del_20250910_1757508393988_0.pdf](../assets/brogliaccio_seduta_del_20250910_1757508393988_0.pdf)
+file-path:: ../assets/brogliaccio_seduta_del_20250910_1757508393988_0.pdf
+
+- Gruppo di Riesame di Dipartimento
+ ls-type:: annotation
+ hl-page:: 7
+ hl-color:: green
+ id:: 68c1772a-c6e9-420f-a505-a7d8a5ea6fe2
\ No newline at end of file
diff --git a/pages/hls__brogliaccio_seduta_del_20251015_1760531243507_0.md b/pages/hls__brogliaccio_seduta_del_20251015_1760531243507_0.md
new file mode 100644
index 00000000..77cbea55
--- /dev/null
+++ b/pages/hls__brogliaccio_seduta_del_20251015_1760531243507_0.md
@@ -0,0 +1,13 @@
+file:: [brogliaccio_seduta_del_20251015_1760531243507_0.pdf](../assets/brogliaccio_seduta_del_20251015_1760531243507_0.pdf)
+file-path:: ../assets/brogliaccio_seduta_del_20251015_1760531243507_0.pdf
+
+- Blended Modeling per piattaforme low-code, in quanto introduce un approccio innovativo che supera la tradizionale separazione tra modelli logici e rappresentazioni grafiche
+ ls-type:: annotation
+ hl-page:: 299
+ hl-color:: green
+ id:: 68efa542-26fa-411a-be99-256bcc532ce6
+- .Nonostante il lavoro svolto dal dott. Damiano Di Vincenzo abbia soddisfatto in maniera eccellente tutti i requisiti ed i problemi posti, si ritiene che ulteriori sviluppi ed approfondimenti siano necessari in particolare rispetto alle nuove opportunità di sperimentazione che il progetto sta dando luog
+ ls-type:: annotation
+ hl-page:: 299
+ hl-color:: blue
+ id:: 68efa560-d65e-42cc-bd5c-c6463280e3f5
\ No newline at end of file
diff --git a/pages/hls__brogliaccio_seduta_del_20251112_1762955181674_0.md b/pages/hls__brogliaccio_seduta_del_20251112_1762955181674_0.md
new file mode 100644
index 00000000..0278129d
--- /dev/null
+++ b/pages/hls__brogliaccio_seduta_del_20251112_1762955181674_0.md
@@ -0,0 +1,2 @@
+file:: [brogliaccio_seduta_del_20251112_1762955181674_0.pdf](../assets/brogliaccio_seduta_del_20251112_1762955181674_0.pdf)
+file-path:: ../assets/brogliaccio_seduta_del_20251112_1762955181674_0.pdf
diff --git a/pages/hls__brogliaccio_seduta_del_20251112_1762956046474_0.md b/pages/hls__brogliaccio_seduta_del_20251112_1762956046474_0.md
new file mode 100644
index 00000000..c0fb6cc2
--- /dev/null
+++ b/pages/hls__brogliaccio_seduta_del_20251112_1762956046474_0.md
@@ -0,0 +1,2 @@
+file:: [brogliaccio_seduta_del_20251112_1762956046474_0.pdf](../assets/brogliaccio_seduta_del_20251112_1762956046474_0.pdf)
+file-path:: ../assets/brogliaccio_seduta_del_20251112_1762956046474_0.pdf
diff --git a/pages/hls__icse2025-paper1580.md b/pages/hls__icse2025-paper1580.md
new file mode 100644
index 00000000..d4ae61a3
--- /dev/null
+++ b/pages/hls__icse2025-paper1580.md
@@ -0,0 +1,2 @@
+file:: [icse2025-paper1580.pdf](file://C:/Users/david/Zotero/storage/TRUCG6BD/icse2025-paper1580.pdf)
+file-path:: file://C:/Users/david/Zotero/storage/TRUCG6BD/icse2025-paper1580.pdf
diff --git a/pages/hls__presentation_1756721524484_0.md b/pages/hls__presentation_1756721524484_0.md
new file mode 100644
index 00000000..12f0932d
--- /dev/null
+++ b/pages/hls__presentation_1756721524484_0.md
@@ -0,0 +1,38 @@
+file:: [presentation_1756721524484_0.pdf](../assets/presentation_1756721524484_0.pdf)
+file-path:: ../assets/presentation_1756721524484_0.pdf
+
+- Open weight mode
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68b572ad-6444-494c-8929-43d2665321e6
+- Open source model
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68b572d4-f669-47ca-b942-f3a52b9e0683
+- Reproducible (libre) model
+ ls-type:: annotation
+ hl-page:: 3
+ hl-color:: green
+ id:: 68b57311-0b75-4a2a-86a9-b7236e7d2611
+- Classes of "openess" https: //arxiv.org/abs/2403.13784 55
+ ls-type:: annotation
+ hl-page:: 5
+ hl-color:: green
+ id:: 68b5737f-d5d0-41fd-bdc5-e574964d08ed
+- Reproducibility in AI research
+ ls-type:: annotation
+ hl-page:: 36
+ hl-color:: green
+ id:: 68b57a82-c115-4a56-a85b-4241b54bda29
+- Finetuning
+ ls-type:: annotation
+ hl-page:: 53
+ hl-color:: green
+ id:: 68b57e64-b29f-42ea-9620-be4bbfa7edc2
+- Benchmarks
+ ls-type:: annotation
+ hl-page:: 73
+ hl-color:: green
+ id:: 68b57fc1-5214-405c-b4f7-58296590c06d
\ No newline at end of file
diff --git a/pages/hls__rinunciaAssegnoRubei_1760531403155_0.md b/pages/hls__rinunciaAssegnoRubei_1760531403155_0.md
new file mode 100644
index 00000000..41a124bd
--- /dev/null
+++ b/pages/hls__rinunciaAssegnoRubei_1760531403155_0.md
@@ -0,0 +1,2 @@
+file:: [rinunciaAssegnoRubei_1760531403155_0.pdf](../assets/rinunciaAssegnoRubei_1760531403155_0.pdf)
+file-path:: ../assets/rinunciaAssegnoRubei_1760531403155_0.pdf
diff --git a/pages/people___AlfonsoPierantonio.md b/pages/people___AlfonsoPierantonio.md
new file mode 100644
index 00000000..504c651e
--- /dev/null
+++ b/pages/people___AlfonsoPierantonio.md
@@ -0,0 +1,4 @@
+title:: people/AlfonsoPierantonio
+
+-
+-
\ No newline at end of file
diff --git a/pages/people___FortunatoSantucci.md b/pages/people___FortunatoSantucci.md
new file mode 100644
index 00000000..6ee1cca9
--- /dev/null
+++ b/pages/people___FortunatoSantucci.md
@@ -0,0 +1,3 @@
+title:: people/FortunatoSantucci
+
+-
\ No newline at end of file
diff --git a/pages/people___alfonso.md b/pages/people___alfonso.md
deleted file mode 100644
index a300ad94..00000000
--- a/pages/people___alfonso.md
+++ /dev/null
@@ -1,4 +0,0 @@
-title:: people/alfonso
-
--
--
\ No newline at end of file
diff --git a/pages/people___santucci.md b/pages/people___santucci.md
deleted file mode 100644
index 4d7f6c2f..00000000
--- a/pages/people___santucci.md
+++ /dev/null
@@ -1,3 +0,0 @@
-title:: people/santucci
-
--
\ No newline at end of file
diff --git a/pages/status.md b/pages/status.md
new file mode 100644
index 00000000..50c2753e
--- /dev/null
+++ b/pages/status.md
@@ -0,0 +1,2 @@
+-
+-
\ No newline at end of file
diff --git a/pages/url.md b/pages/url.md
index 3cf20d57..40710f40 100644
--- a/pages/url.md
+++ b/pages/url.md
@@ -1 +1 @@
--
\ No newline at end of file
+- cards
\ No newline at end of file
diff --git a/pages/🗓 TIASSISTO24 - MEETING BANDO REGIONE ABRUZZO 1.1.1.2.md b/pages/🗓 TIASSISTO24 - MEETING BANDO REGIONE ABRUZZO 1.1.1.2.md
index 48f0e1bc..e2a2e29f 100644
--- a/pages/🗓 TIASSISTO24 - MEETING BANDO REGIONE ABRUZZO 1.1.1.2.md
+++ b/pages/🗓 TIASSISTO24 - MEETING BANDO REGIONE ABRUZZO 1.1.1.2.md
@@ -9,7 +9,7 @@ link:: [1.1) Documenti tecnici in preparazione - Google Drive](https://drive.goo
- ### Meetings
- [[02-07-2025]]
- DONE Da parlare con Marco Barile e Laura
-id:: 685e49d2-2419-400e-99ae-66426632b820
+ id:: 685e49d2-2419-400e-99ae-66426632b820
:LOGBOOK:
CLOCK: [2025-06-29 Sun 09:30:54]--[2025-06-29 Sun 09:30:55] => 00:00:01
:END:
@@ -25,7 +25,7 @@ id:: 685e49d2-2419-400e-99ae-66426632b820
id:: 68584f65-1fb3-44d5-8df6-eff29bbb2ed1
- Rivedere quanto specificato nel documento ((685521de-7d0e-431f-801a-a3f836d10c8b))
- DONE WBS ed Obiettivi progettuali di ciascun partner, necessari anche per la costituzione dell'ATS.
-id:: 68584f65-059e-497a-b44b-fbe9081c7b12
+ id:: 68584f65-059e-497a-b44b-fbe9081c7b12
:LOGBOOK:
CLOCK: [2025-06-20 Fri 11:14:14]--[2025-06-29 Sun 09:31:15] => 214:17:01
:END:
@@ -41,7 +41,7 @@ id:: 68584f65-059e-497a-b44b-fbe9081c7b12
id:: 6855232a-08da-43da-9147-2012a583dc21
- [Allegato ATS.doc](../assets/Allegato_ATS_1750410047925_0.doc)
- DONE **Piano di ampia diffusione dei risultati**, necessario per incrementare % intensità dell'agevolazione
-id:: 68584f65-2e7c-411e-ab67-9159bf073567
+ id:: 68584f65-2e7c-411e-ab67-9159bf073567
- Attività in capo al Polo di innovazione Inoltra. Sarà un costo di consulenza che, insieme all’attività in corso e quelle che svolgeremo a supporto della implementazione del progetto, potrà essere rendicontata da tutte le aziende. Le università non sono coinvolte nel contratto di collaborazione. Per i termini dell’accordo abbiamo già discusso con Michele, ma possiamo sentirci quando volete. A breve riceverete dal Polo la proposta economica mandato.
- **RICHIESTA DOCUMENTAZIONE - BANDO REGIONE ABRUZZO 1.1.1.2**
email:: ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgKbCesAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)