ddiruscio/logseq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[logseq-plugin-git:commit] 2026-01-29T08:23:47.364Z

Browse Source
This commit is contained in:
Davide Di Ruscio
2026-01-29 09:23:47 +01:00
parent 64dc30802b
commit e6a634e7f0
1 changed files with 16 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
journals/2026_01_29.md
+16 -15
View File
@@ -34,21 +34,22 @@ boox-notes:: ![BOOX Notes](../assets/../../onyx/TabUltraCPro/Notepad/JOURNALING.
- You said that the datasets are necessary to train the model. But it is sure that the existing models are nothing to do with agents or multi-agent systems. Isn't it? [[question]]
- ![image.png](../assets/image_1769673122545_0.png)
- I think you should focus on the workflow benchmarks [[question]]
- ![image.png](../assets/image_1769673209665_0.png)
- This should be looked also for our [[Benchmarking framework]]
- How do you see this linked with the benchmarking functionalities of the repository? [[question]]
- https://zjunlp.github.io/project/WorFBench/
- ![image.png](../assets/image_1769673564213_0.png){:height 538, :width 921}
- ![image.png](../assets/image_1769673870219_0.png)
- ![image.png](../assets/image_1769673930716_0.png)
- ![image.png](../assets/image_1769674026611_0.png)
- ![image.png](../assets/image_1769674068587_0.png)
- ![image.png](../assets/image_1769674158359_0.png)
- ![image.png](../assets/image_1769674200531_0.png)
- How would you expect the query shown at slides 36 from working w.r.t. what we have seen yesterday? [[question]]
- This needs to be discusssed but the constraint based specifications will be trasleted as requests to the repository API
- ![image.png](../assets/image_1769674423475_0.png)
- For the consensus at certain point, humans might be involved. The reference agents will take care of this human-in-the-loop step
- ![image.png](../assets/image_1769673209665_0.png)
- This should be looked also for our [[Benchmarking framework]]
- How do you see this linked with the benchmarking functionalities of the repository? [[question]]
- https://zjunlp.github.io/project/WorFBench/
- ![image.png](../assets/image_1769673564213_0.png){:height 538, :width 921}
- ![image.png](../assets/image_1769673870219_0.png)
- ![image.png](../assets/image_1769673930716_0.png)
- ![image.png](../assets/image_1769674026611_0.png)
- ![image.png](../assets/image_1769674068587_0.png)
- ![image.png](../assets/image_1769674158359_0.png)
- ![image.png](../assets/image_1769674200531_0.png)
- How would you expect the query shown at slides 36 from working w.r.t. what we have seen yesterday? [[question]]
- This needs to be discusssed but the constraint based specifications will be trasleted as requests to the repository API
- ![image.png](../assets/image_1769674423475_0.png)
- For the consensus at certain point, humans might be involved. The reference agents will take care of this human-in-the-loop step
-
- ### **Questions**
- {{query (and [[question]] [[29-01-2026]] )[[question]]}}
query-table:: true