<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tools on Kailas Venkitasubramanian</title>
    <link>/tags/tools/</link>
    <description>Recent content in Tools on Kailas Venkitasubramanian</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 06 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying AI across the Research Life Cycle</title>
      <link>/blog/posts/2026-02-06-deploying-ai-across-the-research-life-cycle/</link>
      <pubDate>Fri, 06 Feb 2026 00:00:00 +0000</pubDate>
      <guid>/blog/posts/2026-02-06-deploying-ai-across-the-research-life-cycle/</guid>
      <description>&lt;h1 id=&#34;deploying-ai-across-the-research-life-cycle&#34;&gt;Deploying AI across the research life cycle&#xA;  &lt;a href=&#34;#deploying-ai-across-the-research-life-cycle&#34;&gt;&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;Last summer, I gave a workshop to the staff on augmenting the research proposal process with AI. Thought I&amp;rsquo;ll sketch out what an AI-assisted research workflow might actually look like for both quantitative and qualitative work.&#xA;One caveat before we get into it. This is a map of possibilities, not a prescription. What you can actually do depends on your data, your project, and what UNC Charlotte currently permits. Before trying any of this, check what the university&amp;rsquo;s Office of OneIT has published on approved tools and data classification. That guidance sets the real boundaries. This is more of a documentation of experiments that hopefully will be part of how our AI strategy takes shape.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
