<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chris Miller &#187; 2006 &#187; January</title>
	<atom:link href="http://chris-miller.org/archives/2006/01/feed/" rel="self" type="application/rss+xml" />
	<link>http://chris-miller.org</link>
	<description>Life, and how to live it!</description>
	<lastBuildDate>Tue, 24 Jan 2012 14:41:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Project Management</title>
		<link>http://chris-miller.org/archives/2006/01/19/project-management/</link>
		<comments>http://chris-miller.org/archives/2006/01/19/project-management/#comments</comments>
		<pubDate>Thu, 19 Jan 2006 20:02:55 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[University]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[bib]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[journal]]></category>
		<category><![CDATA[MediaWiki]]></category>
		<category><![CDATA[research]]></category>
		<category><![CDATA[wiki]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://chris-miller.org/blog/archives/2006/01/19/project-management/</guid>
		<description><![CDATA[After looking at how to read, annotate and store papers you&#8217;ve read it&#8217;s useful to discuss how to organise your research in the scope of a project. Research Journal On the MSc course at Glasgow we have all been asked to buy a hardback ledger in which we are to keep a diary of what [...]]]></description>
			<content:encoded><![CDATA[<p>After looking at how to read, annotate and store papers you&#8217;ve read it&#8217;s useful to discuss how to organise your research in the scope of a project.</p>
<p><span id="more-137"></span></p>
<h3>Research Journal</h3>
<p>On the MSc course at Glasgow we have all been asked to buy a hardback ledger in which we are to keep a diary of what we are doing in our research. That&#8217;s fine, but I&#8217;m a computing scientist, writing things down goes against the grain &#8211; I want a computing related solution to this problem.</p>
<p>After a while contemplating I concluded that alternatives to having a hardback book would be:</p>
<ol>
<li>blogging software (i.e. WordPress)</li>
<li>wiki software (i.e. MediaWiki)</li>
</ol>
<h4>Blogs</h4>
<p>Blogs lend themselves to chronological recording of data, after-all they are in necessity online diaries. Blogs can be a simple way to record ideas, dates of events and so on.</p>
<h4>Wikis</h4>
<p>Wikis, although not strictly ordering entries by time and date, allow for very easy addition and formatting of new content. Most wikis will allow you to create <em>categorised</em> or <em>special</em> pages.  For example in MediaWiki pages can be prefixed when naming them, this can be used to categorise the pages.</p>
<h4>Combinations</h4>
<p>Both blogging software and wikis can be used in combination of course, blogs giving the chronological progression between different research papers and wikis showing the resulting thoughts, summaries and so on that you generate.</p>
<h3>Why do it?</h3>
<p>Keeping a digital version of this information means we don&#8217;t have any issue with loosing the research journal or spilling coffee over it (note: don&#8217;t spill coffee over your computer either).</p>
<p>Project co-ordinators can see how you are progressing, comment on what they think of your research via comment mechanisms in a blog and talk/discuss pages on a wiki.</p>
<h4>Collaborations</h4>
<p>Online versions of research journals can help in collaborative projects &#8211; the research journal becomes a platform for collective reasoning, interaction, and the sharing of ideas.</p>
<h3>If you don&#8217;t want to do it electronically</h3>
<p>The real lesson to take away from this post is that a research journal is a good thing to have, be it a bound book, wiki, blog or whatever combination.</p>
<h3>My Wiki usage</h3>
<p>I am currently doing research on my project for the year, which is what sparked this article, <abbr title="3D Sonification with Gestures">SonG</abbr>. For the project I use a wiki to manage my research, post ideas, and transcribe meeting minutes to mention a few things. I thought it may be useful to share the page title formats I use for doing so.</p>
<p><strong>Meetings</strong>:</p>
<ul>
<li>Index: <code>Meetings</code></li>
<li>Meeting: <code>Meeting:[YYYY][MM][DD]</code></li>
<li><code>YYYY</code> = year, <code>MM</code> = month and <code>DD</code> = day</li>
</ul>
<p><strong>Papers</strong>:</p>
<ul>
<li>Index: <code>Papers</code></li>
<li>Paper: <code>Paper:[KEY]</code></li>
<li><code>KEY</code> = the bibliography key for the paper</li>
</ul>
<p><strong>Project specific</strong>:</p>
<ul>
<li>Title: <code>[Project]:[Title]</code></li>
<li>I.e. <code>SonG:Links</code></li>
</ul>
<p>I hope this is useful to anyone doing a project involving any type of research, although this type of journal is not restricted to only research based projects.</p>
<p>- Chris</p>
]]></content:encoded>
			<wfw:commentRss>http://chris-miller.org/archives/2006/01/19/project-management/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Reading a Research Paper: A beginners guide</title>
		<link>http://chris-miller.org/archives/2006/01/19/reading-a-research-paper-a-beginners-guide/</link>
		<comments>http://chris-miller.org/archives/2006/01/19/reading-a-research-paper-a-beginners-guide/#comments</comments>
		<pubDate>Thu, 19 Jan 2006 00:58:20 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[University]]></category>
		<category><![CDATA[Work]]></category>
		<category><![CDATA[bib]]></category>
		<category><![CDATA[bibliography]]></category>
		<category><![CDATA[highlight]]></category>
		<category><![CDATA[papers]]></category>
		<category><![CDATA[reading]]></category>
		<category><![CDATA[research]]></category>

		<guid isPermaLink="false">http://chris-miller.org/blog/archives/2006/01/19/reading-a-research-paper-a-beginners-guide/</guid>
		<description><![CDATA[A small guide to reading research papers.]]></description>
			<content:encoded><![CDATA[<p>I am currently undertaking a masters in Advanced Computing Science at the University of Glasgow, which is heavily research based.  Due to this I&#8217;ve been reading a lot of research papers and have developed my own style for reading them which I will share with you here.</p>
<p><span id="more-136"></span><br />
<h3>Media</h3>
<p>First get a good <code>.PDF</code> or <code>.PS</code> copy of the paper in question.  <strong>Print the document</strong>, I usually go for double sided to save space and 2-up if it&#8217;s a particularly long paper.</p>
<p>If the paper has a lot of pictures or diagrams take the time and expense to print it in <span class="red">c</span><span class="red">o</span><span class="green">l</span><span class="green">o</span><span class="blue">u</span><span class="blue">r</span>.  You&#8217;d be amazed at how much more a colourful document will hold your attention over a grayscale one, also detail will not be obscured due to poor colour choice from the author.</p>
<h3>Meta</h3>
<p>If you&#8217;re using any sort of bibliography database, and you really should be &#8211; BibTeX is my preference, then you&#8217;ll be generating keys for all the documents you enter into it.  <strong>Write the paper&#8217;s key on the top of the paper along with the year it was published</strong>.</p>
<p>This saves time if you&#8217;re citing the paper later, rather than having to search though the database, usually a flat file, to find the title or author of the paper, you simply have to glance at the first page.</p>
<p>Leave space at the top of the paper for any general comments you have about the paper overall.  Don&#8217;t write a critical review, just a quick note which you will be able to use to identify the contents of the paper quickly.  Another useful thing to add to any paper is a list of keywords.  Many conferences and journals add these to papers but your own keywords will have more meaning to you than the general ones produced by the publishers.</p>
<p>Once you have read the paper <strong>look through the list of references</strong>, highlight any that you think are potentially useful and try and find them, this is possibly the path your research will follow and maybe the next paper you should read.  Once you have a copy and thus a key for the paper, due to your corresponding bibliography entry, note the key next to the reference.  This allows you to quickly find out if you have the paper at a later date for example when rereading the paper for other research and allows you to quickly assess which paper it is.</p>
<h3>Reading the paper</h3>
<p>Something we&#8217;ve had knocked into us on the MSc course at Glasgow is how to read a research paper.  The general consensus is a 5 stage process:</p>
<ol>
<li>
<em>Read the abstract</em> &#8211; this should roughly tell you what the paper is about, what the problem addressed is, what the authors did and what they found.
</li>
<li>
<em>Read the introduction and conclusion</em> &#8211; skipping to the end of a book usually gives away the plot, skipping to the end of a research paper will help you understand the ideas in the paper as it will contain a concise version of everything the author has said.  You should have a fair idea of what&#8217;s coming from reading the abstract anyway.  Reading the start and end of the paper will give a better insight into what the paper is about and help you decide if it applies to your area of research or not.
</li>
<li>
<em>Read the whole paper</em> &#8211; jumping past anything which you get stuck on.  Read all the details quickly, glance at figures, tables and equations but don&#8217;t over invest time in trying to understand them.  Reading the whole paper quickly will give you an overall feel for the argument put forward in the paper.
</li>
<li>
<em>Re-read the paper</em> &#8211; this time going into the fine details and trying to understand the parts of the paper which eluded you the first time round.  If necessary look at some of the supporting material, consult books, websites, peers, colleagues and so forth.</p>
<p>Make notes in the margins of the paper, most papers are typeset in either one or two columns, this gives space on either side of the text to annotate it &#8211; make<br />
notes, reference other works, point out problems e.t.c..  This is where it is useful to have a physical copy of the paper.  Highlight key areas of the paper using whatever means you wish, I will go on to talk about this in the next section.
</li>
<li>
<em>Summarise</em> &#8211; write your blurb on the front page of the paper and then try and write a page summary of the whole paper.  Aim to include the main points of the paper, the arguments, methodologies uses, results and conclusions which you feel relate to your research or may do in the future.</p>
<p>This is useful if you need to grasp the idea of the paper quickly at a later date, don&#8217;t rely on remembering about the paper &#8211; <strong>you will forget the details</strong>.
</li>
</ol>
<h3>Highlighting content</h3>
<p>Everyone has a different method for marking parts of the paper they are reading.  I prefer to use highlighter pens as they do not obscure the detail or text in the document unlike circling or underlining.</p>
<p>Most papers, I find, tend to break down into four main sections:</p>
<ol>
<li>
Introduction and related work
</li>
<li>
Problem definition and intended methodology
</li>
<li>
Experiment details and results
</li>
<li>
Discussion and conclusions
</li>
</ol>
<p>Each of these sections I match to a different coloured highlighter pen, the same for every paper to make it easier to find sections of the document.  I use:</p>
<dl>
<dt style="background-color: #ffff33; width: 10%; padding-left: 2px;">
Yellow
</dt>
<dd>
Introduction
</dd>
<dt style="background-color: #ffcc33; width: 10%; padding-left: 2px;">
Orange
</dt>
<dd>
Problem definition
</dd>
<dt style="background-color: #33cc66; width: 10%; padding-left: 2px;">
Green
</dt>
<dd>
Experiment details
</dd>
<dt style="background-color: #ff9999; width: 10%; padding-left: 2px;">
Red
</dt>
<dd>
Conclusion
</dd>
</dl>
<p>Obviously some papers don&#8217;t follow this general pattern, such as survey papers, in this case I use the yellow and red pens as before, for the introduction and conclusion.  I then alternate between the orange and green highlighters for different sections or ideas within the paper body.</p>
<h3>Storage</h3>
<p>I urge you to <strong>keep all research papers after you&#8217;ve read them</strong>.  Keep a digital copy, but also keep the printed copy which contains your annotations.  It is also useful to keep a printed copy of your page summaries with the corresponding papers for a quick reference to the paper.</p>
<p>As the physical copy of the paper is likely to be the <em>only</em> annotated version of the paper you have make sure you don&#8217;t loose it.  As I&#8217;ve mentioned you will forget the details and annotations can be a low cost solution to jogging the memory.</p>
<p>Get a box file, put the papers and summaries into it, organise them in any manner you wish but just keep them.</p>
<h3>Re-visiting</h3>
<p>All this seems a lot of work just for reading <em>one</em> research paper, but the this time is an investment which will be paid back in droves later.</p>
<p>Whenever you are required to cite papers or give related/supporting work sections in reports or your own papers the page summaries will provide you with the textual descriptions of the content that you will likely use.  Re-writing a section on a particular paper five times, and consequently re-reading the paper five times, will take up more time than annotating and summarising the paper originally.</p>
<h3>Enjoy!</h3>
<p>I enjoy reading research papers, as long as they&#8217;re not too technically heavy, but reading research papers can take a long time.  I&#8217;ve found that using a formulated and structured approach to reading, annotating and summarising the papers make the process easier and quicker, this is why I&#8217;m sharing my guide with you.</p>
<p>That&#8217;s all I have to say, if anyone has anything to add, or their own unique style for reading papers, feel free to add a comment detailing it.<br />
- Chris</p>
]]></content:encoded>
			<wfw:commentRss>http://chris-miller.org/archives/2006/01/19/reading-a-research-paper-a-beginners-guide/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

