File: dataform_proc.shtml

package info (click to toggle)
munipack 0.6.2-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 33,104 kB
  • sloc: cpp: 29,677; sh: 4,909; f90: 2,872; makefile: 278; python: 140; xml: 72; awk: 12
file content (266 lines) | stat: -rw-r--r-- 8,930 bytes parent folder | download | duplicates (3)
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
<!DOCTYPE HTML>
<html lang="en">
<head>
<!-- #include virtual="/meta.shtml" -->
<title>Munipack ‒ Processing File</title>
</head>
<body>
<!-- #include virtual="/head.shtml" -->
<section>

<h1 class="noindent">Processing File</h1>
<p class="abstract">
Description of the FITS structure file used to store of processing of instrumental
data ("proc" format). Proc-files are the essential core of data formats in Munipack.
Processing actions keeps their results in the extensions of this kind of file.
All other actions uses proc-file as input.
</p>

<p>
Proc-file is not created by only one action, but the extensions
are created by various ones.
Objects detection and aperture photometry is provided
by <samp>munipack find, munipack aphot</samp> modules.
The astrometry calibration
is determined by <samp>munipack astrometry</samp>.
The photometry calibration
is determined by <samp>munipack phcal</samp>.
</p>

<p>
Proc-file specification has been developed for internal use in Munipack
and follows rules introduced by original DAOPHOT.
Any backward compatibility is not guarantied.
</p>

<h1>File Structure</h1>

<p>
  The primary data array is followed by FIND, APERPHOT and GROWCURVE extensions.
  The order of the extensions can vary (use the name rather then index
  to access required extension).
</p>

<div class="table">
<table>
<caption>FITS file structure including photometry</caption>
<tr><th>HDU</th><th>EXTNAME</th><th>Description</th><th>Action</th></tr>
<tr><td>0</td><td></td><td>Primary array (frame)</td><td></td></tr>
<tr><td>1</td><td>FIND</td><td>Table of detected objects</td><td>find</td></tr>
<tr><td>2</td><td>APERPHOT</td><td>Aperture Photometry table</td><td>aphot</td></tr>
<tr><td>3</td><td>GROWCURVE</td><td>Growth curve table</td><td>aphot</td></tr>
</table>
</div>


<h2>Primary Array</h2>

<p>Data in primary array is untouched during objects detection (find)
and aperture photometry phase. GAIN, READNS and SATURATE keywords may by
modified on user request.
</p>


<h1>Object Detection Table: FIND</h1>

<p>
The table contains detected objects.
</p>

<div class="table">
<table>
<caption>Keywords</caption>
<tr><th>Keyword</th><th>Description</th><th>Units</th></tr>
<tr><td>EXTNAME</td><td>FIND as the identifier of this table</td><td></td></tr>
<tr><td>FWHM</td><td>typical full width at half of maximum for a detected object</td><td>pixels</td></tr>
<tr><td>THRESH</td><td>threshold for detection of peak of stars in sigmas of sky above sky mean level in a region</td><td></td></tr>
<tr><td>LOBAD</td><td>Lower good datum</td><td>ADU</td></tr>
<tr><td>HIBAD</td><td>Higher good datum</td><td>ADU</td></tr>
<tr><td>RNDLO</td><td>Round low</td><td></td></tr>
<tr><td>RNDHI</td><td>Round high</td><td></td></tr>
<tr><td>SHRPLO</td><td>Sharp low</td><td></td></tr>
<tr><td>SHRPHI</td><td>Sharp high</td><td></td></tr>
</table>
</div>

<h2>Header Comments</h2>

<p>
Header contains additional information in more human-readable format.
</p>

<pre>
Star detection parameters:
 Gain (e-/ADU)=   [..]      (see primary HDU)
 Saturation (ADU)=  [..]      (see primary HDU)
 Read noise (ADU)=   [..]      (see primary HDU)
 Lower threshold (sigma)=   [..]
 Levels range (ADU) =   [..]     ..   [..]
 Round range =  -1.00000000     ..   1.00000000
 Sharp range =  0.200000003     ..   1.00000000
 Approximate sky value =   [sky]     +-   [skysig]
 Pixels used for sky determination =       10000
</pre>

<div class="table">
<table>
<caption>Object detection table</caption>
<tr><th>Column</th><th>Description</th><th>unit</th></tr>
<tr><td>X</td><td>Horizontal coordinate</td><td>pix</td></tr>
<tr><td>Y</td><td>Vertical coordinate</td><td>pix</td></tr>
<tr><td>SHARP</td><td>sharp parameter</td><td></td></tr>
<tr><td>ROUND</td><td>round parameter</td><td></td></tr>
<tr><td>PEAKRATIO</td><td>Ratio of peak to background (sky level)</td><td></td></tr>
</table>
</div>

<p>
The table is sorted by PEAKRATIO column in decrease order (with bright stars on top).
</p>

<h1 id="aperphot">Aperture Photometry Table: APERPHOT</h1>

<p>
This extension contains aperture photometry of all object in a given set
of apertures. Also a sky level measured in a ring shaped neighbourhood of
every star is estimated.
</p>

<h2>Header Keywords</h2>

<div class="table">
<table>
<caption>Keywords</caption>
<tr><th>Keyword</th><th>Units</th><th>Description</th></tr>
<tr><td>EXTNAME</td><td></td><td>APERPHOT as the identifier of this table</td></tr>
<tr><td>HWHM</td><td></td><td>HWHM estimated by momentum method</td></tr>
<tr><td>NAPER</td><td></td><td>Count of apertures</td></tr>
<tr><td>APER<i>i</i></td><td>pix</td><td>Radius of <i>i</i>-th aperture, <i>i</i> = 1..NAPER</td></tr>
<tr><td>ANNULUS1</td><td>pix</td><td>inner sky annulus radius in pixels</td></tr>
<tr><td>ANNULUS2</td><td>pix</td><td>outer sky annulus radius in pixels</td></tr>
</table>
</div>

<!--
<p>Keyword CALIBR denotes calibration level. One can be potentially
expanded. For example onto more fine calibration, multinight-calibration, etc.
If the keyword is not presented, default is set to 'none'.
</p>

<p>
FOTOSYS designates the photometric system (Landolt UBVRI, Bessel ubvri,..).
The used filter of the system is indicated in FILTER keyword of primary header.
ZEROMAG is complete optional and is useful just only for magnitudes.
</p>
-->


<h2>Table</h2>

<p>
The aperture photometry table.
</p>

<div class="table">
<table>
<caption>Object detection table</caption>
<tr><th>Column</th><th>Description</th><th>unit</th></tr>
<tr><td>X</td><td>Horizontal coordinate<sup><a href="#prim">[§]</a></sup></td><td>pix</td></tr>
<tr><td>Y</td><td>Vertical coordinate<sup><a href="#prim">[§]</a></sup></td><td>pix</td></tr>
<tr><td>SKY</td><td>counts</td><td>Sky level</td></tr>
<tr><td>SKYERR</td><td>counts</td><td>Sky level error</td></tr>
<tr><td>APCOUNT<i>i</i></td><td>counts</td><td>Sum of counts in <i>i</i>-th aperture<sup><a href="#neg">[*]</a></sup></td></tr>
<tr><td>APCOUNTERR<i>i</i></td><td>counts</td><td>Statistical error of APCOUNT<i>i</i></td></tr>
</table>
</div>

<div class="notes">
<p id="prim">
<sup><a href="#prim">[§]</a></sup>
This column is a direct copy of one from FIND extension.
</p>
<p id="neg">
<sup><a href="#neg">[*]</a></sup>
Negative values means impossibility to determine the value.
Common reasons are: the high sky background level (for faint stars)
or a large aperture radius exceeding frame boundary (for stars near an edge)
or saturation (for very bright stars).
</p>
</div>


<h1>Growth-Curve Photometry Table: GROWPHOT</h1>

<p>
  This extension contains results of growth-curve
  photometry for all stars in APERPHOT table.
</p>


<h2>Header Keywords</h2>

<div class="table">
<table>
<caption>Keywords</caption>
<tr><th>Keyword</th><th>Units</th><th>Description</th></tr>
<tr><td>EXTNAME</td><td></td><td>GROWCURVE as the identifier of this table</td></tr>
<tr><td>HWHM</td><td>pix</td><td>HWHM estimated by growth curve in pixels</td></tr>
<tr><td>RADFLX90</td><td>pix</td><td>Radius containing 90% of energy</td></tr>
</table>
</div>

<h2>Table</h2>

<div class="table">
<table>
<caption>GROWPHOT extension</caption>
<tr><th>Column</th><th>Description</th><th>unit</th></tr>
<tr><td>X</td><td>Horizontal coordinate</td><td>pix</td></tr>
<tr><td>Y</td><td>Vertical coordinate</td><td>pix</td></tr>
<tr><td>SKY</td><td>Sky level<sup><a href="#sky">[^]</a></sup></td><td>count</td></tr>
<tr><td>SKYERR</td><td>Statistical error of sky level</td><td>count</td></tr>
<tr><td>GCOUNT</td><td>Growth curve estimated total sum of counts for an infinite
    aperture<sup><a href="#neg">[*]</a></sup></td><td>count</td></tr>
<tr><td>GCOUNTERR</td><td>Statistical error of APCOUNT</td><td>count</td></tr>
<tr><td>GROWFLAG</td><td>Classification: used (0), not used (1) for construction of
    growth-curve, non-stellar object (2).</td><td></td></tr>
</table>
</div>

<div class="notes">
<p id="sky">
  <sup><a href="#sky">[^]</a></sup>
  Values of sky will generall differ from those from the aperture photometry
  table APERPHOT. Growth-curve photometry gives corrections to the sky.
</p>
</div>

<h1>Growth-Curve Table: GROWCURVE</h1>

<p>
  This extension saves growth curve and derived radial profile
  in selected apertures.
</p>

<div class="table">
<table>
<caption>GROWCURVE extension</caption>
<tr><th>Column</th><th>Description</th><th>unit</th></tr>
<tr><td>R</td><td>Radius of the aperture</td><td>pix</td></tr>
<tr><td>GROWCURVE</td><td>growth curve value at R</td><td></td></tr>
<tr><td>GROWCURVEERR</td><td>Statistical error of growth curve</td><td></td></tr>
<tr><td>RADIALPROFILE</td><td>Radial profile at R</td><td></td></tr>
</table>
</div>

<h2>See Also</h2>
<p>
<a href="man_find.html">Detection of Stars</a>,
<a href="man_aphot.html">Aperture Photometry</a>,
<a href="grow.html">Growth Curve Overview</a>.
</p>

</section>
<!-- #include virtual="/foot.shtml" -->
</body>
</html>