AIDC-AI/Marco-o1
Text Generation
•
Updated
•
5.66k
•
503
billo
b1ka
AI & ML interests
None yet
Recent Activity
liked
a model
6 days ago
AIDC-AI/Marco-o1
liked
a model
about 2 months ago
nvidia/NVLM-D-72B
liked
a model
about 2 months ago
meta-llama/Llama-3.2-11B-Vision-Instruct
Organizations
None yet
b1ka's activity
liked
a
model
6 days ago
liked
2
models
about 2 months ago
Reacted to
nroggendorff's
post with 🔥
2 months ago
liked
a
Space
2 months ago
Reacted to
vincentg64's
post with 👀
2 months ago
Post
1817
No-Code LLM Fine-Tuning and Debugging in Real Time: Case Study
Full doc at https://mltblog.com/47DisG5
Have you tried the xLLM web API? It allows you to fine-tune and debug an agentic multi-LLM in real time. The input data is part of the anonymized corporate corpus of a Fortune 100 company, dealing with AI policies, documentation, integration, best practices, references, onboarding, and so on. It features one sub-LLM. The full corpus is broken down into 15 sub-LLMs.
One of the goals is to return concise but exhaustive results, using acronyms (a specific table for each sub-LLM) to map multi-tokens found in prompts but not in the corpus, with multi-tokens in the corpus. Exhaustivity is the most overlooked metric when evaluating LLMs designed for search / retrieval. Using xLLM in combination with another LLMs is one of the best approaches, and both can be used to evaluate each other. Yet, thanks to fast in-memory processing, no weight, and no training, the xLLM web API is one of its kind, with capabilities not found in any competing product, free or not.
Read more at https://mltblog.com/47DisG5
Full doc at https://mltblog.com/47DisG5
Have you tried the xLLM web API? It allows you to fine-tune and debug an agentic multi-LLM in real time. The input data is part of the anonymized corporate corpus of a Fortune 100 company, dealing with AI policies, documentation, integration, best practices, references, onboarding, and so on. It features one sub-LLM. The full corpus is broken down into 15 sub-LLMs.
One of the goals is to return concise but exhaustive results, using acronyms (a specific table for each sub-LLM) to map multi-tokens found in prompts but not in the corpus, with multi-tokens in the corpus. Exhaustivity is the most overlooked metric when evaluating LLMs designed for search / retrieval. Using xLLM in combination with another LLMs is one of the best approaches, and both can be used to evaluate each other. Yet, thanks to fast in-memory processing, no weight, and no training, the xLLM web API is one of its kind, with capabilities not found in any competing product, free or not.
Read more at https://mltblog.com/47DisG5
liked
3
models
2 months ago
liked
a
model
3 months ago
upvoted
a
collection
3 months ago
updated
a
collection
4 months ago