<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bschmidt on Journal of Digital Humanities</title><link>https://journalofdigitalhumanities.org/author/bschmidt/</link><description>Recent content in Bschmidt on Journal of Digital Humanities</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 01 Dec 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://journalofdigitalhumanities.org/author/bschmidt/index.xml" rel="self" type="application/rss+xml"/><item><title>Theory First</title><link>https://journalofdigitalhumanities.org/1-1/conversations/theory-first-by-ben-schmidt/</link><pubDate>Thu, 01 Dec 2011 00:00:00 +0000</pubDate><guid>https://journalofdigitalhumanities.org/1-1/conversations/theory-first-by-ben-schmidt/</guid><description>&lt;p&gt;It’s easy to be reasonable about the relationship we’d like to see between digital humanities and “Theory.” Each should inform the other. After all, humanists who put big-T Theory before any empirical data foolishly close their ears to the new evidence digital can create; digital humanists who ignore theory entirely jeopardize not only their careers but the soundness of their conclusions. To take two examples from the theory-friendly side of the spectrum in digital humanities; we should heed Natalia Cecire’s &lt;a href="http://nataliacecire.blogspot.com/2011/10/when-dh-was-in-vogue-or-thatcamp-theory.html" title="Natalia Cecire, 'When DH was in Vogue; or THATCamp Theory'"&gt;call&lt;/a&gt; to treat digital humanities as important because it transforms humanistic practice; but we should also be mindful of Ted Underwood’s concerns &lt;a href="http://tedunderwood.wordpress.com/2011/10/22/on-transitive-and-intransitive-uses-of-the-verb-to-theorize/" title="Ted Underwood, 'On transitive and intransitive uses of the verb 'theorize''"&gt;that claims for the primacy of theory often amount to little more than a power play&lt;/a&gt;, serving to reify existing class distinctions inside the academy. In practice, this probably means digital humanists can keep calm and carry on, with greater tolerance for the occasional French name tossed into the discussion; meanwhile the theory-inclined should know they have a seat at the new table, though not necessarily at the head. Even more hack, better yack. What’s not to love?&lt;/p&gt;</description></item><item><title>Words Alone: Dismantling Topic Models in the Humanities</title><link>https://journalofdigitalhumanities.org/2-1/words-alone-by-benjamin-m-schmidt/</link><pubDate>Sat, 01 Dec 2012 00:00:00 +0000</pubDate><guid>https://journalofdigitalhumanities.org/2-1/words-alone-by-benjamin-m-schmidt/</guid><description>&lt;p&gt;As this issue shows, there is no shortage of interest among humanists in using topic modeling. An entire genre of introductory posts has emerged encouraging humanists to try LDA.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; So many scholars in humanities departments are turning to the tool in their research that it is sometimes described as part of the digital humanities in itself. Last fall, the NEH sponsored a workshop at Maryland which expressed concern that “&lt;a href="http://mith.umd.edu/topicmodeling/about/" title="MITH Workshop, 'Topic Modeling'"&gt;the most promising work in topic modeling is being done not by humanists exploring literary or historical corpora but instead by scholars working in natural language processing and information retrieval&lt;/a&gt;.” There is not, it seems safe to say, another machine-learning algorithm in the world anyone would expect humanists to lead the progress of. Newcomers to the field could be forgiven for thinking that digital humanists need to topic model to prove their mettle; analog humanists could be forgiven for assuming that the computational interests of literary scholars and historians are particularly focused on the sorts of questions that topic models answer.&lt;/p&gt;</description></item><item><title>Code Appendix for “Words Alone: Dismantling Topic Models in the Humanities”</title><link>https://journalofdigitalhumanities.org/2-1/code-appendix-for-words-alone-by-benjamin-m-schmidt/</link><pubDate>Sat, 01 Dec 2012 00:00:00 +0000</pubDate><guid>https://journalofdigitalhumanities.org/2-1/code-appendix-for-words-alone-by-benjamin-m-schmidt/</guid><description>&lt;h3 id="topic-modeling-ships"&gt;Topic Modeling Ships&lt;/h3&gt;
&lt;p&gt;Begin by getting the data in order. (This data is available on request.)&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;# Oceans2
rm(list = ls())
require(ggplot2)
require(plyr)
require(lubridate)
source(&amp;#34;ICOADS parsing.R&amp;#34;)
source(&amp;#34;../Map Functions.R&amp;#34;)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;This step pulls in the Maury data and splits it. This is not fully documented as part of this article, since the purpose is to show general geodata parsing.&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;data = loadInData(&amp;#34;~/shipping/ICOADS/maury.txt&amp;#34;)
data = splitDataByVoyage(data)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Next, save the R data.frame into a directory that MALLET will be able to interpret as a text, and run a topic model on it. The rounding gives the resolution at which the topic will be run.&lt;/p&gt;</description></item></channel></rss>