<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Getting started — C-Munipack 2.0.8 documentation</title>
<link rel="stylesheet" href="_static/default.css" type="text/css" />
<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '',
VERSION: '2.0.8',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<link rel="top" title="C-Munipack 2.0.8 documentation" href="index.html" />
<link rel="next" title="Using Muniwin" href="using_muniwin.html" />
<link rel="prev" title="Installation and uninstallation" href="installation.html" />
</head>
<body>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="using_muniwin.html" title="Using Muniwin"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="installation.html" title="Installation and uninstallation"
accesskey="P">previous</a> |</li>
<li><a href="index.html">C-Munipack 2.0.8 documentation</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<div class="section" id="getting-started">
<span id="id1"></span><h1>Getting started<a class="headerlink" href="#getting-started" title="Permalink to this headline">¶</a></h1>
<p>The following text describes the basic procedure for processing an
observation of a short-periodic variable stars by means of the Muniwin.</p>
<p>The package with demo data used in the example is available on the project’s
web pages. Download and unzip the archive to an empty folder at your hard disk
(e.g. <tt class="file docutils literal"><span class="pre">~/c-munipack/sample</span></tt>. The archive has the following structure:</p>
<dl class="object">
<dt>
<tt class="descname">dark / 20s / masterdark.fts</tt></dt>
<dd><p>master-dark frame (20 seconds exposure)</p>
</dd></dl>
<dl class="object">
<dt>
<tt class="descname">dark / 20s / raw / dark*.fts</tt></dt>
<dd><p>set of raw dark frames (20 seconds exposure)</p>
</dd></dl>
<dl class="object">
<dt>
<tt class="descname">flat / v / masterflat.fts</tt></dt>
<dd><p>master-flat frame (optical filter V)</p>
</dd></dl>
<dl class="object">
<dt>
<tt class="descname">flat / raw / flat-v*.fts</tt></dt>
<dd><p>set of raw flat frames (optical filter V)</p>
</dd></dl>
<dl class="object">
<dt>
<tt class="descname">data / v / frame*.fts</tt></dt>
<dd><p>sample CCD frames (optical filter V)</p>
</dd></dl>
<div class="section" id="general-overview">
<h2>General overview<a class="headerlink" href="#general-overview" title="Permalink to this headline">¶</a></h2>
<p>In general, the reduction of CCD data consists of the several steps:</p>
<ol class="arabic simple">
<li>Creating a new project and populating it with input files (source CCD frames)</li>
<li>Calibration of the source frames</li>
<li>Photometry and matching</li>
<li>Selection of stars</li>
<li>Selection of aperture</li>
</ol>
</div>
<div class="section" id="creating-a-new-project">
<h2>Creating a new project<a class="headerlink" href="#creating-a-new-project" title="Permalink to this headline">¶</a></h2>
<p>Launch the <strong class="program">Muniwin</strong> program - a way how to launch an application depends on your operating system and desktop environment.
For example, on the MS Windows platform, the Muniwin program can be run from the menu <em class="menuselection">Start ‣ Programs ‣ C-Munipack 2.0</em>
folder.</p>
<p>Using the main menu, select item <em class="menuselection">Project ‣ New</em>. A new dialog appears.</p>
<div class="figure align-center">
<img alt=""New project" dialog" src="_images/newproject.png" />
<p class="caption">The dialog for making a new project.</p>
</div>
<p>Fill in a name that will be assigned to the project. Because the name of the file that keeps track of the data related
to the project, the project file, is derived from the name, some characters cannot appear in the project name, do not use: / ? % * : | ” < and >
In our example, let us use the designation of the variable star <tt class="docutils literal"><span class="pre">CR</span> <span class="pre">Cas</span></tt>.</p>
<p>The field <em class="guilabel">Location</em> shows a path to the directory where a new project will be created. Edit the path to
change the location, you can also click the <em class="guilabel">Browse</em> button to select a directory in a separate dialog.</p>
<p>The dialog also displays a list of available project types. Project types were designed to limit the amount of control
that are shown in application. Select the <em class="guilabel">Variable star observation</em>, please.</p>
<p>Confirm the dialog, yet another dialog appears.</p>
<div class="figure align-center">
<img alt=""Load profile" dialog" src="_images/newproject2.png" />
<p class="caption">The dialog for specifying an initial set of configuration parameters</p>
</div>
<p>Using the second dialog, you can load an intial set of configuration parameters into a new project. If this is a fresh
installation, you have one choice only - use factory defaults. The choice <em class="guilabel">Load factory defaults</em> should be
automatically selected and make sure that the options below are unchecked. Confirm the dialog.</p>
<p>You should be in the main window again now. The table of input files shown there is empty.</p>
<div class="figure align-center">
<img alt="Main application window" src="_images/main.png" />
<p class="caption">The main application window with the table of input files, now empty.</p>
</div>
</div>
<div class="section" id="selecting-source-frames">
<h2>Selecting source frames<a class="headerlink" href="#selecting-source-frames" title="Permalink to this headline">¶</a></h2>
<p>Now, we’re going to populate the project with source files. Open the <em class="guilabel">Frames</em> menu and click on <em class="guilabel">Add frames from folder</em>.
Go to the folder which contains the source CCD frames. The demo data is stored in the <tt class="file docutils literal"><span class="pre">data/v</span></tt> subfolder. You should
see the list of files in the center navigation pane. This dialog allows you to add all frames from folders and subfolders.
If you need to specify only a subset of files from a particular folder, you the <em class="guilabel">Add individual frames</em> choice.</p>
<div class="figure align-center">
<img alt=""Add folder" dialog" src="_images/addfolder1.png" />
<p class="caption">The dialog with the place selection box (left), the file selection box (middle)
and the preview panel (right).</p>
</div>
<p>Push the <em class="guilabel">Add</em> button. If you want to process data taken in several nights at once, use the same procedure to add
those files to the table. After inserting all the files you want to process, close the dialog by pushing the <em class="guilabel">Close</em>
button.</p>
<div class="figure align-center">
<img alt="Main application window" src="_images/inputfiles.png" />
<p class="caption">The main application window with the sample frames inserted.</p>
</div>
</div>
<div class="section" id="frame-reduction">
<h2>Frame reduction<a class="headerlink" href="#frame-reduction" title="Permalink to this headline">¶</a></h2>
<p>Reduction of CCD frames is a process that takes source CCD frames, performs their conversion and calibration,
detects stars on each frame and mearures their intensity and finally finds correlation (match) between objects
that were found in the data set. The process of reduction prepares the data that are necessary for making a light
curve or a variable star.</p>
<p>The reduction consists of several steps - conversion, calibration, photometry and matching. They can be invoked
step-by-step manually. The preferred way is to use the <em class="guilabel">Express reduction</em> dialog that allows to perform
these steps in a batch. Using the menu, activate the <em class="menuselection">Reduce ‣ Express reduction</em> item.
A new dialog appears. The dialog has several options aligned to the left, Each of them relates to an optional
step in the reduction process.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express.png" />
<p class="caption">The dialog for setting parameters of the reduction process</p>
</div>
<p>Check the <em class="guilabel">Fetch/convert files</em>.
In this step, the program makes copy of the source CCD frames. This is necessary, because the following
calibration steps will modify them and we don’t want the program to change our precious source data.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_convert.png" />
</div>
<p>A raw CCD frame consists of several components. By the calibration process, we get rid of those
which affect the result of the photometry. In some literature, the calibration is depicted as the
peeling of an onion. There are three major components which a raw frame consists of - the current
made by incident light, current made thermal drift of electrons (so-called dark current) and
constant bias level. In standard calibration scheme, which we will demonstrate here, the dark-frame
correction subtracts the dark current and the also the bias. Because of the nature of the dark current,
it is necessary to use a correction frame of the same exposure duration as source files and it must
be carried out on the same CCD temperature, too. Thus, the properly working temperature regulation
on your CCD camera is vital. Our sample data needs to perform the dark-frame correction, so check
the <em class="guilabel">Dark-frame correction</em> option. Click the <em class="guilabel">Browse</em> button and find the file
with the dark frame. For the sample data, use the file <tt class="file docutils literal"><span class="pre">dark</span> <span class="pre">/</span> <span class="pre">20s</span> <span class="pre">/</span> <span class="pre">masterdark.fts</span></tt>.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_dark.png" />
</div>
<p>Then, we have to compensate the spatial non-uniformity of a detector and whole optical
system. These non-uniformities are due to the fabrication process of a CCD chip and they are
also natural properties of all real optical components, lenses in particular. The flat-frame
correction uses a flat-frame to smooth them away. The flat-frame is a frame carried out
while the telescope is pointed to uniformly luminous area. In practice, this condition is
very difficult to achieve, the clear sky before dusk is usually used instead. Our sample data
needs to perform the flat-frame correction too, so check the <em class="guilabel">Flat-frame correction</em>
option. Click the <em class="guilabel">Browse</em> button and find the file with the flat frame. For the sample data,
use the file <tt class="file docutils literal"><span class="pre">flat</span> <span class="pre">/</span> <span class="pre">V</span> <span class="pre">/</span> <span class="pre">masterflat.fts</span></tt>.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_flat.png" />
</div>
<p>The photometry is a process that detects stars on a CCD frame and measures their brightness. Unlike the previous
steps, the result is saved to a special file, so-called the photometry file. There are a lot of parameters which
affect the star detection and also the brightness computation. In this example, the default values work fine,
but I would suggest you to become familiar with at least two of them - FWHM and Threshold - before
you start a real work. Check the <em class="guilabel">Photometry</em> option.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_photometry.png" />
</div>
<p>The previous command treated all source files independently. As a result of this, a star #1
in one file is not necessarily the same as a star #1 in another file. The matching is a process
which finds corresponding stars on source frames and assigns an unique identifier. Check the
<em class="guilabel">Matching</em> option.</p>
<p>It is necessary to select one frame from the set of source frames that all other frames are matched
to, this frame is called a reference frame. In my experience, the frame with the greatest number of
stars works the best. Back to our example, let’s pick up the first one.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_matching.png" />
</div>
<p>In previous steps, we have configured parameters of the reduction process and we are ready to start
it. Click the <em class="guilabel">OK</em> button. During the execution a new window appears displaying the state
of the process; all the information is also presented there. This window will be automatically
closed after finishing the process. Wait for the process to finish.</p>
<div class="figure align-center">
<img alt="Progress dialog" src="_images/progress.png" />
<p class="caption">The dialog displayed during time demanding operations.</p>
</div>
<p>After finishing, the icon in the file table changes; the information about the time of observation,
the length of the exposition and the used filter is filled in. In case some of the frames could not be
processed successfully, the entry is be marked with a special icon and in the <em class="guilabel">Status</em> column
the error message is indicated.</p>
<div class="figure align-center">
<img alt="Main application window" src="_images/inputfiles3.png" />
<p class="caption">The main application window after the recution.</p>
</div>
</div>
<div class="section" id="making-a-light-curve">
<h2>Making a light curve<a class="headerlink" href="#making-a-light-curve" title="Permalink to this headline">¶</a></h2>
<p>The sample data is the observation of an eclipsing binary star. For most of such observers,
the goal is to make a light curve. A light curve is usually represented as a table, which consists
of at least two columns - time stamps expressed as Julian dates and differential instrumental
brightness of a variable star in magnitudes. The magnitudes are called differential, because they
are differences between two stars - a variable star and a comparison star. A variable star is a
star that is subject of brightness variation and a comparison star is supposed to be constant.
To check that the comparison star is really constant, it’s advisory to use one or two additional
stars, so-called check stars. They are supposed to be constant too and thus the difference between
any check star and the comparison star should be constant.</p>
<p>The Muniwin program is designed to guide you through the process of making a light curve.
Open the <em class="guilabel">Make</em> menu and select the <em class="guilabel">Light curve</em> item. A new dialog appears, all
fields in this dialog are optional, they allows you to include only subset of frames to the curve,
apply the heliocentric correction or include the air mass coefficients to the output. Let all options
unchecked and just confirm the dialog by the OK button.</p>
<div class="figure align-center">
<img alt="Make light curve" src="_images/makelightcurve.png" />
<p class="caption">The dialog for making a light curve.</p>
</div>
<p>Another dialog appears. The next dialog allows you to pick up a variable star, a comparison star and one or more
check stars. In this dialog, the reference frame is displayed. Find a variable star and click on
it using the left mouse button. A context menu appears. Select the <em class="guilabel">Variable</em>
item. The star is drawn in red color now and the label <tt class="docutils literal"><span class="pre">var</span></tt> is placed near to it. Using
the same procedure, select one comparison star and one or more check stars. I would recommend
you to use two check stars. If you are using the sample data, use the stars according to the
following screenshot. Confirm the selection by the <em class="guilabel">OK</em> button.</p>
<div class="figure align-center">
<img alt="Choose stars" src="_images/stars.png" />
<p class="caption">The dialog for selection of a variable star (red), a comparison star (green)
and check stars (blue).</p>
</div>
<p>In the next dialog, we have to choose the aperture. You can image the aperture as a virtual circular pinhole,
placed on each star on a frame to measure its brightness. All pixels that are inside
the pinhole are included in computation leaving out the background pixels. The best
aperture should be big enough to include most of the star’s light, on the other hand,
the bigger aperture is used the more background is included and the more noisy the
result is. Because of this, the photometry process computes the brightness of each
star in a set of predefined apertures of radius in the range of 2 and 30 pixels.</p>
<p>The programs allows you to select an aperture in the following dialog, the program
displays a graph of standard deviation of data for each aperture. The curve has U-like
shape usually and the best aperture is in the minimum of the curve. For the sample data,
select the aperture #2 and confirm the dialog by the <em class="guilabel">OK</em> button.</p>
<div class="figure align-center">
<img alt="Choose aperture" src="_images/aperture.png" />
<p class="caption">The dialog for selection of an aperture.</p>
</div>
<p>Now the program has got enough information to make a light curve of the
selected variable star. The light curve is presented in a new window. Please keep
in mind that the magnitudes displayed in the light curve are differential with
respect to the selected comparison star.</p>
<div class="figure align-center">
<img alt="Light curve graph" src="_images/lightcurve.png" />
<p class="caption">The dialog with a light curve graph.</p>
</div>
<p>In the light curve window, open the <em class="guilabel">File</em> menu and select
the <em class="guilabel">Save</em> item. A new dialog appears. Locate the folder
where you want to save the results and fill in the name of the output file. Confirm
the dialog by the <em class="guilabel">Save</em>.</p>
<p>The light curve is saved to a text-based file. On its first line, the
names of the columns are stored. The second line shows the aperture and color
filter used. The data are stored on the followin lines. Each line corresponds
to a single source frame. In the first column, there is a time of observation
(center of exposure) expressed as a Julian date. The second column consists
of differential instrumental brightness of the variable stars with respect
to the comparison star in magnitudes (V-C). The error estimation is stored
in the next column. Following columns consist of differential magnitudes
of comparison star and check stars and their error estimations.</p>
<div class="figure align-center">
<img alt="Output file" src="_images/output.png" />
<p class="caption">The light curve of a variable from the sample data stored to a file.</p>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar">
<div class="sphinxsidebarwrapper">
<h3><a href="index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">Getting started</a><ul>
<li><a class="reference internal" href="#general-overview">General overview</a></li>
<li><a class="reference internal" href="#creating-a-new-project">Creating a new project</a></li>
<li><a class="reference internal" href="#selecting-source-frames">Selecting source frames</a></li>
<li><a class="reference internal" href="#frame-reduction">Frame reduction</a></li>
<li><a class="reference internal" href="#making-a-light-curve">Making a light curve</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="installation.html"
title="previous chapter">Installation and uninstallation</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="using_muniwin.html"
title="next chapter">Using Muniwin</a></p>
<div id="searchbox" style="display: none">
<h3>Quick search</h3>
<form class="search" action="search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="related">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="genindex.html" title="General Index"
>index</a></li>
<li class="right" >
<a href="using_muniwin.html" title="Using Muniwin"
>next</a> |</li>
<li class="right" >
<a href="installation.html" title="Installation and uninstallation"
>previous</a> |</li>
<li><a href="index.html">C-Munipack 2.0.8 documentation</a> »</li>
</ul>
</div>
<div class="footer">
© Copyright 2012, David Motl.
Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
</div>
</body>
</html>
