{"id":3795,"date":"2026-03-31T19:30:24","date_gmt":"2026-03-31T17:30:24","guid":{"rendered":"https:\/\/wp.unil.ch\/iaunil\/dcsr-llm-using-artificial-intelligence-for-research-at-unil\/"},"modified":"2026-04-01T14:53:43","modified_gmt":"2026-04-01T12:53:43","slug":"dcsr-llm-using-artificial-intelligence-for-research-at-unil","status":"publish","type":"post","link":"https:\/\/wp.unil.ch\/iaunil\/en\/dcsr-llm-using-artificial-intelligence-for-research-at-unil\/","title":{"rendered":"DCSR-LLM: using artificial intelligence to support research at UNIL"},"content":{"rendered":"\n

Article written by Dr. Philippe Jacquet, Data Scientist, Division Calcul et Soutien \u00e0 la Recherche (DCSR).<\/em><\/p>\n\n

\"dcsr<\/figure>\n\n

Have you ever wanted to ask the same questions to thousands of documents, compare several AI models, or turn a large collection of texts into structured research data?<\/p>\n\n

These are precisely the kind of research tasks for which DCSR-LLM<\/strong> was developed at UNIL.<\/p>\n\n

What is the DCSR?<\/h2>\n\n

The DCSR<\/strong> stands for Division Calcul et Soutien \u00e0 la Recherche<\/strong>, or Scientific Computing and Research Support Unit in English. We are part of the Centre Informatique at UNIL. We are a team of about 20 people. Our role is to help the UNIL research community with computing, data storage, and technical support for research projects.<\/p>\n\n

Some members of the team manage the computing infrastructure used at UNIL. Others work directly with researchers and provide scientific and technical consulting.<\/p>\n\n

What kind of support does the DCSR provide?<\/h2>\n\n

The DCSR provides two main kinds of support.<\/p>\n\n

The first is infrastructure<\/strong>: computers, storage space, and technical systems that researchers can use for demanding research tasks. The second is expertise<\/strong>: DCSR staff help researchers with topics such as scientific programming, machine learning, databases, and web development.<\/p>\n\n

So the DCSR is not only a place with machines. It is also a support unit with people who help researchers use these tools in a useful way.<\/p>\n\n

What are HPC clusters?<\/h2>\n\n

The term HPC<\/strong> means High-Performance Computing<\/strong>. It refers to powerful computing systems used for tasks that are too large, too slow, or too demanding for an ordinary laptop. An HPC cluster is a group of computers working together. Instead of doing everything on one machine, a cluster can distribute the work across many machines.<\/p>\n\n

At UNIL, there are two HPC clusters: Curnagl<\/strong> and Urblauna<\/strong>. Their names are derived from Romansh bird names. They are used for demanding research tasks such as simulations, data analysis, machine learning, and AI workflows.<\/p>\n\n

A simple way to think about it is this: if your laptop is enough, you use your laptop. If your work becomes too heavy, too slow, or needs more memory, the cluster becomes useful.<\/p>\n\n

What are Large Language Models?<\/h2>\n\n

Large Language Models<\/strong>, or LLMs<\/strong>, are AI systems trained on very large amounts of text. They can answer questions, summarize documents, rewrite text, classify information, or extract facts from written material. Most people know them through tools such as ChatGPT, Claude, or Gemini.<\/p>\n\n

What is Hugging Face?<\/h2>\n\n

Hugging Face<\/strong> is a platform where people share AI models and datasets. A simple comparison is that it is a bit like GitHub, but for machine learning models and data. It also provides software tools that make it easier to download and run open-source language models on a computer or a server.<\/p>\n\n

What is LM Studio?<\/h2>\n\n

LM Studio<\/strong> is an application that lets people run some language models locally through a chat interface. In practice, it feels a bit like using ChatGPT, except that the model can run on your own computer. This is useful for simple local experiments.<\/p>\n\n

Why did the DCSR create DCSR-LLM?<\/h2>\n\n

Because many researchers want to use AI, but their needs often go beyond a simple chatbot<\/strong>.<\/p>\n\n

A chatbot is useful for asking a question or drafting a paragraph. But research often requires something more structured. Researchers may want to:<\/p>\n\n

\u2013 test several models on the same task;
\u2013 work with a large collection of documents;
\u2013 keep data on UNIL infrastructure;
\u2013 save the exact settings used in an analysis;
\u2013 repeat the same workflow later.<\/p>\n\n

This is why the DCSR developed DCSR-LLM.<\/p>\n\n

What is DCSR-LLM?<\/h2>\n\n

DCSR-LLM is a toolkit<\/strong> developed at UNIL for working with large language models in a more structured way.<\/p>\n\n

It allows researchers to download open-source models from Hugging Face<\/strong>, run them locally or on UNIL servers, compare them, evaluate them on specific tasks, extract structured information from text, adapt some models to more specialized uses, and export models to GGUF format for use with LM Studio<\/strong>.<\/p>\n\n

It is not just a chatbot. It is a tool designed for research workflows<\/strong>.<\/p>\n\n

Why not just use ChatGPT or Claude?<\/h2>\n\n

For many everyday uses, ChatGPT or Claude are very useful. But in research, three extra questions often matter.<\/p>\n\n

The first is: where does the data go<\/strong>?
Some projects involve sensitive, unpublished, or internal material. In such cases, researchers may want a more controlled environment.<\/p>\n\n

The second is: which model am I using<\/strong>?
Different models behave differently. In research, it is often useful to compare them rather than rely on only one assistant.<\/p>\n\n

The third is: can I repeat the same workflow clearly<\/strong>?
If an AI result matters for a project, researchers usually need to document how it was produced.<\/p>\n\n

DCSR-LLM is useful because it helps with these three points<\/strong>.<\/p>\n\n

What does “reproducible” mean here?<\/h2>\n\n

It means that the work is done in a way that can be repeated and documented<\/strong>. If you use the same model, the same data, and the same settings, you should be able to rerun the workflow and understand what happened. This matters in research because methods need to be described clearly.<\/p>\n\n

What can DCSR-LLM do in practice?<\/h2>\n\n

DCSR-LLM can do several practical things. It can help a researcher inspect and download models<\/strong> from Hugging Face, run<\/strong> some of these models locally, compare<\/strong> several models on the same benchmark, turn unstructured text<\/strong> into structured data, and adapt a model<\/strong> for a more specific task.<\/p>\n\n

These ideas become easier to understand with examples.<\/p>\n\n

Can you give a first concrete example?<\/h2>\n\n

Imagine a researcher in the social sciences has 2,000 interview transcripts<\/strong> and wants to organize them.<\/p>\n\n

Each interview is written in free text. The researcher wants, for each transcript, to extract a small set of clearly defined fields such as:<\/p>\n\n

\u2013 the title or identifier of the interview;
\u2013 the date of the interview;
\u2013 the location;
\u2013 the name or profile of the person interviewed;
\u2013 the institution or organization mentioned;
\u2013 the main topic discussed;
\u2013 a short quotation supporting the extraction.<\/p>\n\n

A normal chatbot can help with a few interview transcripts, one by one. But this becomes difficult if there are thousands of texts and the researcher wants the same structure every time.<\/p>\n\n

With DCSR-LLM, the team can define the fields they want, run the same extraction process on the whole collection, save the results in a structured format, and then review them. The AI does not replace the researcher. But it can help turn a large collection of text into something easier to inspect and analyze.<\/p>\n\n

Can you give a second concrete example?<\/h2>\n\n

Imagine a biology or medical research team wants to use AI to answer a set of domain-specific questions<\/strong>.<\/p>\n\n

Before choosing a model, the team wants to know which one performs best on its task. If they only use chatbots manually, comparison is difficult. One person may ask slightly different questions. Another may use different wording. Results are harder to compare fairly.<\/p>\n\n

With DCSR-LLM, the team can prepare one fixed list of questions<\/strong> and run the same evaluation on several models. They can then compare the outputs more systematically. Instead of saying, “this model feels better,” they can say, “we tested these models on the same task under the same conditions.” That is much closer to a research approach<\/strong>.<\/p>\n\n

Can you give a third concrete example?<\/h2>\n\n

Imagine a researcher has a very large collection of texts, for example 10,000 journal articles<\/strong> or 10,000 YouTube transcripts<\/strong>.<\/p>\n\n

The researcher may want to ask questions such as:<\/p>\n\n

\u2013 Does this article discuss climate change, migration, or public policy?
\u2013 Is this speaker talking positively or negatively about artificial intelligence?
\u2013 Does this text mention a specific concept, author, or method?
\u2013 Is the main purpose of this article to explain, criticize, or compare?
\u2013 Does this transcript contain personal testimony, expert opinion, or political argument?
\u2013 Which passages talk about ethics, cost, or risk?<\/p>\n\n

A normal chatbot can help with one article or one transcript at a time. But this becomes impractical when the collection contains thousands of texts.<\/p>\n\n

With DCSR-LLM, the researcher can run the same workflow across the whole corpus in a more systematic way. Instead of manually copying text into a chatbot, they can process the collection in a structured manner and save the results for later analysis.<\/p>\n\n

The value here is not just that the AI can answer questions. The value is that it becomes possible to ask the same research questions at scale<\/strong>, on a large body of text, in a way that is more organized and reproducible.<\/p>\n\n

Can you give a fourth concrete example?<\/h2>\n\n

Imagine a team has found a model that works reasonably well, but not quite well enough<\/strong> for its own field. For example, the model may struggle with the vocabulary of a specific discipline, or with the exact format of answers needed for a project.<\/p>\n\n

In that case, the team may want to adapt the model<\/strong> to a specific task or field and then measure whether the adaptation actually helped.<\/p>\n\n

DCSR-LLM can support this kind of before-and-after workflow<\/strong>. A team can test the original model, adapt it for the task, and then test it again on the same benchmark. This gives a clearer answer than a simple impression such as “the new version seems better.”<\/p>\n\n

So DCSR-LLM is not mainly for chatting?<\/h2>\n\n

Exactly. It can be used for chat, but that is not its main purpose. Its main purpose is to support structured work<\/strong> with language models: evaluation, extraction, comparison, and adaptation. That is why it is more useful to think of it as a research tool<\/strong> than as a chatbot.<\/p>\n\n

Do I need to know how to code?<\/h2>\n\n

Not necessarily in depth, but some technical support is helpful.<\/p>\n\n

DCSR-LLM is a command-line tool<\/strong>. This means it is used through a terminal rather than through a point-and-click web interface. Users do not need to be expert programmers, but they should be comfortable with a basic technical environment, or work with support from the DCSR or from technically experienced colleagues.<\/p>\n\n

The important point is that DCSR-LLM is not reserved to AI specialists. But it is also not intended as a consumer product for completely casual use.<\/p>\n\n

Where can DCSR-LLM run?<\/h2>\n\n

It can run on a personal computer<\/strong> for small experiments. It is also designed to run on UNIL infrastructure<\/strong>, including Curnagl and Urblauna.<\/p>\n\n

This matters because a project can start small and then grow. A researcher may first test an idea on a laptop, then later run a larger workflow on the UNIL clusters.<\/p>\n\n

Why is that useful?<\/h2>\n\n

Because many projects do not start with a huge investment. Researchers often begin with a simple question: “Can this model help with my material?”<\/p>\n\n

If the first results are promising, they may then want to scale up: more documents, more models, more comparisons, more demanding computations. DCSR-LLM supports this gradual scaling<\/strong>.<\/p>\n\n

What is the main idea behind DCSR-LLM?<\/h2>\n\n

The main idea is simple. DCSR-LLM helps researchers move from informal chatbot use to a more controlled<\/strong> way of working with AI. That means more clarity about the model used<\/strong>, where the data is processed<\/strong>, how the results are generated<\/strong>, and how the workflow can be repeated<\/strong>.<\/p>\n\n

Does AI replace the researcher?<\/h2>\n\n

No. AI can help with some tasks, sometimes very effectively. But researchers still need to define the question<\/strong>, choose the method<\/strong>, review the outputs<\/strong>, and interpret the results<\/strong>. DCSR-LLM is useful because it helps organize AI-based work. It does not remove the need for scientific judgment.<\/p>\n\n

So what is DCSR-LLM, in one sentence?<\/h2>\n\n

DCSR-LLM is a practical UNIL tool that helps researchers use large language models in a more concrete<\/strong>, controlled<\/strong>, and reproducible<\/strong> way than a simple chatbot interface.<\/p>\n\n

Useful links<\/h2>\n\n

– Repository: https:\/\/git.dcsr.unil.ch\/Scientific-Computing\/dcsr-llm<\/a>
– More information: https:\/\/wiki.unil.ch\/ci\/link\/2266<\/a>
– Contact: helpdesk@unil.ch (subject: DCSR-LLM)<\/p>\n","protected":false},"excerpt":{"rendered":"

Compare models, extract structured data, reproduce workflows: DCSR-LLM helps UNIL researchers use large language models in a more controlled and reproducible way.<\/p>\n","protected":false},"author":1002618,"featured_media":3793,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","footnotes":""},"categories":[22],"tags":[],"class_list":{"0":"post-3795","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-resources"},"_links":{"self":[{"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/posts\/3795","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/users\/1002618"}],"replies":[{"embeddable":true,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/comments?post=3795"}],"version-history":[{"count":5,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/posts\/3795\/revisions"}],"predecessor-version":[{"id":3824,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/posts\/3795\/revisions\/3824"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/media\/3793"}],"wp:attachment":[{"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/media?parent=3795"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/categories?post=3795"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wp.unil.ch\/iaunil\/en\/wp-json\/wp\/v2\/tags?post=3795"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}