<!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>Frame merging — 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="up" title="Using Muniwin" href="using_muniwin.html" />
<link rel="next" title="Incremental processing" href="incremental_processing.html" />
<link rel="prev" title="Catalog files" href="catalog_files.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="incremental_processing.html" title="Incremental processing"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="catalog_files.html" title="Catalog files"
accesskey="P">previous</a> |</li>
<li><a href="index.html">C-Munipack 2.0.8 documentation</a> »</li>
<li><a href="using_muniwin.html" accesskey="U">Using Muniwin</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<div class="section" id="frame-merging">
<span id="index-0"></span><span id="id1"></span><h1>Frame merging<a class="headerlink" href="#frame-merging" title="Permalink to this headline">¶</a></h1>
<p>The frame merging makes one or more resulting CCD frames by combining a set of source
frames. This function is usable for example when the very faint objects are observed,
thus demanding very long exposure durations to obtain desired accuracy. The exposure
duration is limited in practice due to inaccuracy of the telescope driving. The merging
can virtually extend the attainable exposure time, because the image shift can be corrected.</p>
<p>The implementation used in the current version of the C-Munipack project requires
calibratted source frames and corresponding photometry files with information about frame
offsets. These are produced by the matching process, no special option is required.</p>
<p>Corresponding pixels are summed and the result is divided by the total number of source frames.
Pixels, which are not covered by all source frames or which contain bad pixels, are set to zero.
The exposure duration is computed as sum of the durations of source frames. The observation time
is computed as arithmetic mean of times of source frames. The Muniwin program allows automatized
or manual splitting of the set of input files and making a single or a set of result frames.</p>
<div class="section" id="before-you-start">
<h2>Before you start<a class="headerlink" href="#before-you-start" title="Permalink to this headline">¶</a></h2>
<p>Before you start the reduction of your own CCD frames, you may
need to perform several pre-processing steps. Though it isn’t necessary,
combining the several correction frames into so-called “master” ones
is advisory, because it reduces the noise and makes the result more
precise. The method of making master correction frames is described in
separate chapters.</p>
</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>First of all, we will create a new <a class="reference internal" href="projects.html#projects"><em>project</em></a>. To begin with processing of a variable star observation,
we create a new project. To do so, open the <em class="guilabel">Project</em> menu and activate the <em class="guilabel">New</em> item. A new dialog
appears.</p>
<div class="figure align-center">
<img alt=""New project" dialog" src="_images/newproject_merge.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 >.</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">CCD frame merging</em> this time. 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. Later on, you have another choices - you can load
parameter from one of the recent projects you have been working on, or you can make load the parameters from a
template - called a “profile”.</p>
<p>When you confirm the dialog, 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="input-files">
<h2>Input files<a class="headerlink" href="#input-files" title="Permalink to this headline">¶</a></h2>
<p>Now, we are going to tell the program which files we are going to work on. These files are called the input
files. Their list is displayed in the table in the main application window. When the application is closed,
the list of files are saved to the disk and it is restored back when the program is launched again.</p>
<p>Supposing that the table now consists of files from your previous task, let’s get rid of them. Please, use
<em class="menuselection">Files ‣ Clear files</em> to start a new task instead of just removing the files from
the table. Besides the clearing the table of input files, this function resets all internal variables, too.</p>
<p>Now, we need to populate the table with the CCD frames we’re going to reduce. There are two methods how to
achieve that - adding a individual files or adding all files from a folder. Which way is the best for you
depends on organization of your observations on the disk. I’d suggest you to make a folder for each year,
a folder for each night in it, the a subfolder for a name of object or another view field identification and
finally a subfolder named upon the color filter (if you use more of them). In this case, the “Add frames from a folder”
method is more convenient.</p>
<p>Click on <em class="menuselection">Files ‣ Add frames from folder</em> in the main menu. A new dialog appears. In the dialog,
find a folder where the inputs files are stored in. Click on an entry in the <em class="guilabel">Places</em> pane to go to one
of a preselected folders, double click in the middle pane enters the folder. The buttons in the upper part
of the dialog shows your current position in the directory tree, you can use them to go to one of the parent
folders. Enter the folder with the input files - you should see them in the middle pane. Then, click on the
<em class="guilabel">Add</em> button to add files to the table of input files. The program shows the number of added files in
the separate dialog. The <em class="guilabel">Add frames from folder</em> dialog is not closed automatically and allows a user
to continue. Click on the <em class="guilabel">OK</em> button to close the dialog and return to the main window.</p>
<div class="figure align-center">
<img alt=""Add folder" dialog" src="_images/addfolder1.png" />
<p class="caption">The “Add folder” dialog with the place selection box (left), the file
selection box (middle) and the preview panel (right).</p>
</div>
<p>If you want to reduce only a subset of files from a folder, click on <em class="menuselection">Files ‣ Add individual frames</em>
in the main menu. A new dialog appears, similar to the previous one. In the dialog, find a folder where the inputs
files are stored in. Click on an entry in the <em class="guilabel">Places</em> pane to go to one of a preselected folders, double
click in the middle pane enters the folder. The buttons in the upper part of the dialog shows your current position
in the directory tree, you can use them to go to one of the parent folders. In the middle pane, select the files
using the <tt class="kbd docutils literal"><span class="pre">Ctrl</span></tt> modifier to include and exclude a single file and the <tt class="kbd docutils literal"><span class="pre">Shift</span></tt> modifier to include a range
of files. Then, click on the <em class="guilabel">Add</em> button to add selected files to the table of input files. The program
shows the number of added files in the separate dialog. The <em class="guilabel">Add individual frames</em> dialog is not closed
automatically and allows a user to continue. Click on the <em class="guilabel">OK</em> button to close the dialog and return to
the main window.</p>
<div class="figure align-center">
<img alt=""Add files" dialog" src="_images/addfiles1.png" />
<p class="caption">The “Add files” dialog with the place selection box (left), the file
selection box (middle) and the preview panel (right).</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>
<div class="section" id="fetch-convert-files">
<h3>Fetch/convert files<a class="headerlink" href="#fetch-convert-files" title="Permalink to this headline">¶</a></h3>
<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>
</div>
<div class="section" id="dark-frame-correction">
<h3>Dark-frame correction<a class="headerlink" href="#dark-frame-correction" title="Permalink to this headline">¶</a></h3>
<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.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_dark.png" />
</div>
</div>
<div class="section" id="flat-frame-correction">
<h3>Flat-frame correction<a class="headerlink" href="#flat-frame-correction" title="Permalink to this headline">¶</a></h3>
<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.</p>
<div class="figure align-center">
<img alt=""Express reduction" dialog" src="_images/express_flat.png" />
</div>
</div>
<div class="section" id="photometry">
<h3>Photometry<a class="headerlink" href="#photometry" title="Permalink to this headline">¶</a></h3>
<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>
<dl class="docutils">
<dt>FWHM</dt>
<dd>The FWHM parameter specify the expected width of stars on a frame.
The value is the Full Width at Half Maximum in pixels. The parameter
controls the behavior of the low-pass digital filter, which is used
in the star detection algorithm.</dd>
<dt>Threshold</dt>
<dd>The Threshold parameter specify the lowest brightness of detected
stars. Fainter objects are considered to be background artifacts and thus
sorted out. The value is dimensionless coefficient.</dd>
</dl>
<p>Once you tune up the parameter for your environment, usually it is not
necessary to adjust them for every task, unless the quality of your images
varies considerably. In the first iteration, you can use the default values
(FWHM = 3.0 and Threshold = 4.0) and do the photometry. Click on the
<em class="menuselection">Reduce ‣ Photometry</em> item in the main menu and confirm the new dialog by the <em class="guilabel">OK</em>.
Then, by double click on a frame in the main window open the preview window
and check the results. If there are stars which have been detected as a close
binary although it is not true, you should increase the <em>FWHM</em>
value. If the stars you are interested in are not detected, try decrease the
<em>Threshold</em> value. If it doesn’t help, decrease the
<em>FWHM</em>. If there is a lot of background artifacts detected
as a real stars, increase the <em>Threshold</em>. By several
iterations, adjust the parameters, so all the stars you are interested in are
detected and there are no false binaries.</p>
</div>
<div class="section" id="matching">
<h3>Matching<a class="headerlink" href="#matching" title="Permalink to this headline">¶</a></h3>
<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>
</div>
<div class="section" id="invoking-the-reduction-process">
<h3>Invoking the reduction process<a class="headerlink" href="#invoking-the-reduction-process" title="Permalink to this headline">¶</a></h3>
<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>
<div class="section" id="making-combined-frames">
<h2>Making combined frames<a class="headerlink" href="#making-combined-frames" title="Permalink to this headline">¶</a></h2>
<p>Open <em class="guilabel">Make</em> menu, select the <em class="guilabel">Merge frames</em> item.
A new dialog window appears. If you are going to make a set of resulting frames, select
the <em class="guilabel">Split frames and process each group separately</em> option. Set the parameters
for automatic splitting frames to groups; one resulting frame will be made for each particular
group. Fill the maximum number of frames in a group to the <em class="guilabel">Merge every ... frames</em>
field. Set the maximum time span between the first and the last frame in a group. Enter the
minimum number of frames (<em class="guilabel">Min. frames</em>). Confirm the dialog by
the <em class="guilabel">OK</em> button. The standard dialog for saving files is opened.
Find a directory, where the output files shall be stored to and enter the file name
prefix. For example, if you enter the crcas prefix, the resulting files will be named
<tt class="file docutils literal"><span class="pre">crcas00001.fts</span></tt>, <tt class="file docutils literal"><span class="pre">crcas00002.fts</span></tt>, etc. Close the dialog by the <em class="guilabel">Save</em> to start the merging.</p>
<p>It is possible to split the files manually. In the <cite>Input files</cite> table, select the
frames, which shall be combined to a single resulting frame. In the <em class="guilabel">Make</em>
menu, select the <em class="guilabel">Merge frames</em> item. The same dialog window as
in previous case is opened. In the upper part of the dialog, select the <em class="guilabel">Process
selected files only</em> option and in the lower part, select the <em class="guilabel">Merge
all source frames to a single output frame</em> item. Confirm the dialog by the
<em class="guilabel">OK</em> button. The standard dialog for saving files is opened. Find
a directory, where the output file shall be stored to and enter the its name. No numbers
are added to the name in this case. Close the dialog by the <em class="guilabel">Save</em>
to start the merging. Repeat the action subsequently for all input files.</p>
</div>
<div class="section" id="processing-merged-frames">
<h2>Processing merged frames<a class="headerlink" href="#processing-merged-frames" title="Permalink to this headline">¶</a></h2>
<p>Merged frames can be processed in the same way as common CCD frames with an exception
that no calibration (bias, dark and flat correction) is applied to them. Follow instructions
in the <a class="reference internal" href="light_curve.html#light-curve"><em>Light curve</em></a> section.</p>
<div class="admonition-see-also admonition seealso">
<p class="first admonition-title">See also</p>
<p class="last"><a class="reference internal" href="merge_frames_dialog.html#merge-frames-dialog"><em>Merge frames (dialog)</em></a></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="#">Frame merging</a><ul>
<li><a class="reference internal" href="#before-you-start">Before you start</a></li>
<li><a class="reference internal" href="#creating-a-new-project">Creating a new project</a></li>
<li><a class="reference internal" href="#input-files">Input files</a></li>
<li><a class="reference internal" href="#frame-reduction">Frame reduction</a><ul>
<li><a class="reference internal" href="#fetch-convert-files">Fetch/convert files</a></li>
<li><a class="reference internal" href="#dark-frame-correction">Dark-frame correction</a></li>
<li><a class="reference internal" href="#flat-frame-correction">Flat-frame correction</a></li>
<li><a class="reference internal" href="#photometry">Photometry</a></li>
<li><a class="reference internal" href="#matching">Matching</a></li>
<li><a class="reference internal" href="#invoking-the-reduction-process">Invoking the reduction process</a></li>
</ul>
</li>
<li><a class="reference internal" href="#making-combined-frames">Making combined frames</a></li>
<li><a class="reference internal" href="#processing-merged-frames">Processing merged frames</a></li>
</ul>
</li>
</ul>
<h4>Previous topic</h4>
<p class="topless"><a href="catalog_files.html"
title="previous chapter">Catalog files</a></p>
<h4>Next topic</h4>
<p class="topless"><a href="incremental_processing.html"
title="next chapter">Incremental processing</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="incremental_processing.html" title="Incremental processing"
>next</a> |</li>
<li class="right" >
<a href="catalog_files.html" title="Catalog files"
>previous</a> |</li>
<li><a href="index.html">C-Munipack 2.0.8 documentation</a> »</li>
<li><a href="using_muniwin.html" >Using Muniwin</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>
