This file is indexed.

/usr/share/doc/munipack/man_timeseries.html is in munipack-doc 0.5.10-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
<!DOCTYPE HTML>
<html lang="en">
<head>
<!-- meta -->
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta name="description" content="A general astronomical image processing software">
<meta name="author" content="Filip Hroch">
<link href="news_feed.xml" type="application/atom+xml" rel="alternate" title="Sitewide ATOM Feed" />
<link type="text/css" rel="stylesheet" href="munipack.css">
<link rel="shortcut icon" href="favicon.ico">
<title>Munipack ‒ Time Series</title>
</head>
<body>
<header>
<a href="munipack.html"><img src="title_logo.png" alt="Munipack's logo" class="head"></a>
<div class="headhead">
<div class="headtitle">
<a class="headtitle" href="munipack.html">Munipack</a>
<a class="headsubtitle" href="munipack.html">A general astronomical image processing software</a>
</div>
<ul class="menu">
  <li class="menu"><a href="docs.html" class="menu">Documents</a></li>
  <li class="menu"><a href="guide.html" class="menu">User guide</a></li>
</ul>
</div>
</header>

<h1>Time Series</h1>

<p class="abstract">
This routine is general purpose utility to list of selected
elements from calibrated files.
</p>

<h2>Command</h2>

<code>
munipack timeserie [...] file(s)
</code>

<h2>Description</h2>

<p>
This utility is designed for listing of time series of a various
quantities from a set of already processed frames.
Instrumental and calibrated data can be used. Full
calibrated data including astrometry and photometry calibration are preferred.
</p>

<p>
By listing of a set of processed files, this tool creates a time dependence of
a required quantity. The quantity is selected as a FITS-table column name
and stored in a time series table.
The time series of a light-like quantity is referenced as a light curve (LC).
</p>

<p>
The utility can be used to derive various kinds of times-like quantities.
</p>


<h2>Prerequisites</h2>
<p>
Needs astrometry and photometry. To get calibrated fluxes or magnitudes, needs
photometry calibration.
</p>

<h2>Input And Output</h2>

<p>
On input, list of frames containing both astrometric and photometric information
is expected.
</p>

<p>
On output, the FITS table representing the time series is created.
</p>


<h2>Parameters</h2>

<h3>Time:</h3>

<p>
The time can be specified for reference points:
</p>

<dl>
<dt>At Middle (--time-stamp=MID)</dt>
<dd>The time specifies exactly at middle of exposure duration. Computed
as begin time plus half of exposure. This is default.</dd>
<dt>At Begin (--time-stamp=BEGIN)</dt>
<dd>The time specifies exactly at begin of exposure.</dd>
<dt>At End (--time-stamp=END)</dt>
<dd>The time specifies exactly at end of exposure.</dd>
</dl>

<p>
Following types of time can be specified (<a href="http://en.wikipedia.org/wiki/Julian_day">Julian day on wiki</a>):
</p>

<dl>
<dt>Julian date (-T JD)</dt>
<dd>The time is specified in Julian dates in UT by default.</dd>
<dt>Modified Julian date (-T MJD)</dt>
<dd>The time is specified in modified Julian dates (JD − 2400000.5) in UT.</dd>
<dt>Heliocentric Julian date (-T HJD)</dt>
<dd>The time is specified in Julian dates at barycenter of solar system in UT.</dd>
<dt>Phase (-T PHASE)</dt>
<dd>The time is specified as phase in UT. The phase φ is computed from
a reference epoch <i>e<sub>0</sub></i> given by --epoch in Julian days and
period <i>P</i> given by --period in days: <i>φ = {(t - e<sub>0</sub>)/P}</i>
(where <i>{.}</i> operator provides fractional part (see
<a href="http://en.wikipedia.org/wiki/Floor_and_ceiling_functions">Floor and ceiling functions</a>).</dd>
</dl>

See also detailed description at
<a href="dataform_tmseries.html#tmtable">description of output table</a>.

<h3>Listing:</h3>

<dl>
<dt><samp>-c, --column</samp></dt><dd>column(s) to output list (must exactly
          match names of column(s) in images on input)</dd>
<dt><samp>-C, --coocolumn</samp></dt><dd>column(s) of quantities used as
         coordinates</dd>
<dt><samp>-x, --extname</samp></dt><dd>An identifier of FITS-extension</dd>
<dt><samp>-T, --time-type</samp></dt><dd>JD − Julian date (default), MJD − modified JD,
                                         HJD − heliocentric JD, PHASE, AIRMASS</dd>
<dt><samp>--time-stamp</samp></dt><dd>reference time point: mid (default), begin, end</dd>
<dt><samp>--diffmag</samp></dt><dd>differential magnitudes (with respect to a first object)</dd>
<dt><samp>--epoch</samp></dt><dd>reference time point of light curve elements in JD</dd>
<dt><samp>--period</samp></dt><dd>period light curve elements in days</dd>
<dt><samp>--tol</samp></dt><dd>search radius for object identification in degrees</dd>
<dt><samp>--stdout</samp></dt><dd>results print also to standard output</dd>
<dt><samp>--cat</samp></dt><dd>catalogue of coordinates from the FITS file</dd>
</dl>

<p>
When <samp>-c</samp> or <samp>-C</samp> are not specified,
the structure of the first file is discovered.
The coordinates are recognised automatically as rectangular
(equivalent to <samp>-C X,Y</samp>) or spherical (<samp>-C RA,DEC</samp>).
All other columns (except coordinates) are listed by default
(usually as <samp>-c COUNT,COUNTERR</samp>, <samp>-c PHOTON,PHOTONERR</samp>,
<samp>-c MAG,MARERR</samp>, etc.).
</p>



<h2>Stars Selection And Catalogue</h2>

<p>
By default, all stars on all frames are processed and stored to the output file.
To select stars, there are two ways:
</p>

<ul>
<li>specify coordinates on the command-line</li>
<li>use a catalogue</li>
</ul>

<p>
For a few stars request, the simpler way is specification of coordinates on the
command line. Use twices of equatorial coordinates (Right Ascension and Declination)
in degrees separated by commas (or semicolon).
For example:
</p>
<pre>
$ munipack timeseries 330.689,42.2765 330.667,42.2860  file.fits
</pre>

<p>More general way is use of a table with coordinates. Important
advantages over command line:
</p>
<ul>
<li>Very useful for passing of many stars and to use it repeatedly.</li>
<li>Proper motion can be specified. The file header can provide additional
    information (reference epoch) and units for all coordinates (complex
    info is crucial reason for use file).</li>
</ul>

<p>
The proper motion can be important for near and moving stars and should
by used for flying rocks.
</p>

<h2>Catalogue For Stars Selection</h2>

<p>
Format of the catalogue is very restrictive and must be carefully
followed. One is stored in FITS file with a just one table extension
(EXTNAME doesn't matter). The header must contain keyword EPOCH which
denotes the reference time <i>t</i><sub>0</sub> in Julian days for object coordinates.
The current positions at <i>t</i> are computed from reference coordinates
<i>α</i><sub>0</sub>, <i>δ</i><sub>0</sub>
and proper motions <i>μ</i><sub><i>α</i>0</sub>, <i>μ</i><sub><i>δ</i>0</sub> (in
degrees per century) as:<br>
&nbsp; α = <i>α</i><sub>0</sub> + <i>μ</i><sub><i>α</i>0</sub> /(<i>t</i> - <i>t</i><sub>0</sub>) / <i>T</i><br>
&nbsp; δ = <i>δ</i><sub>0</sub> + <i>μ</i><sub><i>δ</i>0</sub> /(<i>t</i> - <i>t</i><sub>0</sub>) / <i>T</i><br>
where <i>T</i> is the time unit given by TUNITS keywords in header.
One is one for deg/day and 365.25 for arcsec/year.
</p>

<p>
The most simple way how to create the catalogue,
<a href="timeserie_cat.lst">timeserie_cat.lst</a> can be directly used
as example and edited. The FITS file timeserie_cat.fits is created as
</p>
<pre>
$ munipack fits --restore timeserie_cat.lst
</pre>


<table>
<caption>Table structure</caption>
<tr><th>Column</th><th>Description</th><th>Units</th></tr>
<tr><td>RAJ2000</td><td>Right ascension <i>α</i><sub>0</sub></td><td>degrees</td></tr>
<tr><td>DEJ2000</td><td>Declination <i>δ</i><sub>0</sub></td><td>degrees</td></tr>
<tr><td>pmRA</td><td> proper motion in RA <i>μ</i><sub><i>α</i>0</sub></td><td>arcsec/year or deg/day<sup><a href="#pmu">[†]</a></sup></td></tr>
<tr><td>pmDEC</td><td>proper motion in DEC <i>μ</i><sub><i>δ</i>0</sub></td><td>arcsec/year or deg/day<sup><a href="#pmu">[†]</a></sup></td></tr>
</table>

<div class="notes">
<sup><a href="pmu">[†]</a></sup>
The string 'arcsec/year' or 'deg/day' must be present and specified exactly
via TUNIT3 and TUNIT3 keywords. Setting of proper motions to zeros will
usually satisfactory (except really fast moving objects).
</div>

<h2>Caveats</h2>

<p>
This utility is primary indented and designed for working with low
amount of data. The typical usage is listing of light curves
or positions of motion of objects during a night. Another example can be study
of any instrumental quantity. This routine is generic analysing tool.
</p>

<p>
Use on large archives of observations is not recommended.
Spidering over a complicated directory structure would be really
slow. To work with a large data archive, use Munipack to create
tables with photometry and astrometry data and keep the results in a database.
Much more better idea should be to import the data into some
Virtual Observatory engine. Popular VO-engines are
<a href="http://ia2.oats.inaf.it/index.php/vodance">VO-Dance</a>,
<a href="http://saada.unistra.fr/saada/">Saada</a> or
<a href="http://docs.g-vo.org/DaCHS/">GAVO DaCHS</a>.
</p>



<h2>Examples</h2>

<p>
Timeseries for all stars:
</p>
<code>
$ munipack timeseries M67_Blue.fits
</code>

<p>
Light curve for stars at coordinates:
</p>
<code>
$ munipack timeseries 256,156 258,88 0716_*R.fits
</code>



<h2>See Also</h2>
<p>
<a href="dataform_tmseries.html">Data format for timeseries</a>,
<a href="lctut.html">Light Curve Tutorial</a>,
<a href="man_com.html">Common options</a>.</p>

<footer>
<div style="float:left; margin-left:2em;">
Copyright &copy; 1997 – 2018
Filip Hroch (<a style="text-decoration: none" href="mailto:hroch@physics.muni.cz?Subject=Munipack" title="Author's Email"></a>), license <a href="http://www.gnu.org/licenses/gpl.html">GPLv3</a>.
</div>
<div style="float:right; margin-right:2em; margin-top:-0.2em;">
<a href="http://monteboo.blogspot.com/search/label/Munipack" title="Munipack on MonteBoo Blog"><img src="favicon-blogger.png" alt="Blogger"></a>
<a href="http://www.muni.cz/?lang=en" title="Masaryk University in Brno, Czech Republic"><img src="mu-logo.png" alt="Masaryk University"></a>
<a href="news_feed.xml" title="Munipack's Releases in Atom Syndication Format"><img src="Feed-icon.png" alt="Atom Feed"></a>
</div>
</footer>
</body>
</html>