Help needed to reproduce paper's experiments
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kubernetes, ollama
- Domain
- ai, distributed-systems
Research direction
Start with self_managing_systems/microservice/AutoKube and its missing cloudgpt_aoai.py reference, then compare the README examples in paper_artifact_arXiv_2407_14402 with the prompts directory. Run the working_mechanism_1 and working_mechanism_2 examples using the stated local models; done means documenting whether the paper behavior can be reproduced and what setup, model, or prompt differences explain the divergence.
Written by the indexing model from the issue text.
Description
Hello, @MikukuOvO I'm PhD in autonomic computing and runtime adaptation and I got super interested in your work. I read the paper "The Vision of Autonomic Computing: Can LLMs Make It a Reality?" and watched the video. I tried to experiment with the LLM-based multi-agents. However, I couldn't reproduce the experiments, the outcomes are quite different from the paper and video.
I tried to run auto-kube against my local LLM (Ollama -- deepseekr1-1.4 and llama3.2) and it didn't worked, it is missing cloudgpt_aoai.py. Then, I tried the code from paper_artifact_arXiv_2407_14402 and this one seems to work.
I tried a few examples as in the README:
- on
working_mechanism_1:report CPU from your component --component catalogue,scale your component to three replicas --component catalogue, - on
working_mechanism_2:Reduce the total P99 latency of catalogue and front-end to under 400 ms --components catalogue,front-end
In all cases, I observed the agents reasoning and trying many different things, but they never converge to what I've asked. For example, when I request for working_mechanism_1 report CPU from your component --component catalogue, the agent diverge after a dozen of iterations and start trying to fetch the response time of the service instead of CPU. Stopping after 50 iterations with no results.
I've tried different models (deepseek-r1:32b, deepseek-r1:14b, llama3.2, etc), and in all cases the outcome diverges from the original task. I'm not sure if it is an issue with the models that are very generic or the setup prompts that need to be fine tuned.
Could you provide some guidance, am I missing anything?
Besides GPT, do you have any suggestion about which other model could perform better? -- I don't have access to GPT model.
In regarding to the prompts, have you tried variations on them? Do you have any hint on how could I customize them to achieve better results?
Thx!
- Dominant language
- Jupyter Notebook
- Stars
- 41
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/ACV
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
area/sessions comp/cron comp/gateway P2 sweeper:risk-message-delivery sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#118863 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
model-catalog
Difficulty 1/5 Under an hour Newbie friendliness 88/100
braintrustdata/braintrust-proxy#1279 ·