Projet

Général

Profil

YoGA Ao features » Historique » Version 2

Damien Gratadour, 11/11/2013 11:16

1 2 Damien Gratadour
h1. YoGA AO features
2 1 Damien Gratadour
3 2 Damien Gratadour
The YoGA_AO extension contains routines to simulate the whole process of image formation through the atmosphere, a telescope and an adaptive optics (AO) system.
4 1 Damien Gratadour
5
There are two ways to use YoGA_Ao, either through the GUI or through the command line possibly using predefined scripts. The following description is valid for both ways but is probably more relevant to command line users. The main difference between the GUI and the command line interface is the way the simulation parameters are imported. In the latter case, the simulation parameters are centralized into a parameter file (.par). Examples of .par files are given in the data/par directory and can be used as templates. The high-level API contains a dedicated routine to read the parameters from this file and import them in the simulation environment.
6
7
[[YoGA Ao features#List-of-features|List of features]]
8
9
* [[YoGA Ao features#Simulation-geometry|Simulation geometry]]
10
* [[YoGA Ao features#Turbulence-generation|Turbulence generation]]
11
* [[YoGA Ao features#Wavefront-Sensing|Wavefront Sensing]]
12
* [[YoGA Ao features#Image-formation|Image formation]]
13
14
[[YoGA Ao features#List-of-routines|List of routines]]
15
16
* [[YoGA Ao features#High-level-routines|High-level routines]]
17
* [[YoGA Ao features#Advanced-routines|Advanced routines]]
18
19
h2. List of features
20
21
Each API comes with a set of structures concentrating the configuration parameters for the simulation as well as various data used for computation and diagnostics. For the Yorick API, the list of structures can be found in the file yoga_ao_ystruct.i. Concerning the CUDA-C API, please refer to the file yoga_ao.cpp. Available features include:
22
23
* Kolmogorov-type turbulence generation over an arbitrary number of layers with arbitrary properties.
24
* Shack-Hartmann wavefront sensing including Laser Guide Stars (LGS)
25
* Short and long exposure imaging under the turbulence
26
27
h3. Simulation geometry
28
29
The main parameter that drives most of the choices for the simulation geometry is the Fried parameter r0. Typically, for an adequate sampling, the equivalent size of the pixels we use to simulate the turbulent phase screens should be less than half r0. To ensure a good sampling, in YoGA_Ao, r0 is simulated on about 6 pixels. This ratio defines the size of the "quantum" pixels and thus the size of the phase screens to simulate (as compared to the telescope size). From this screen size, the full images size is defined, taking into account the sampling required for imaging.
30
31
As an example, in the case of an ELT, the linear size of the phase screen support (and thus of the pupil) is of the order of 1.5k to 2k pixels. This means that the linear size of the image will be at least 4k (for a minimum Shannon sampling). This is a very large number which will imply heavy computations.
32
33
To cope for these various requirements we can define 3 different pupils: 
34
35
* the large pupil (called ipupil) defined on the largest support (4kx4k in our previous example) more than half of which being 0
36
37
* the small pupil (spupil) defined only on the pupil size (2kx2k in our previous example) most of it being 1
38
39
* the medium pupil (mpupil) defined on a slightly larger support: typically 4 additional pixels as a guard band on each size. This guard band is useful for manipulations on phase screens like raytracing. This is also the actual size of the ground layer phase screen.
40
41
The image below helps to understand the various pupil sizes. White is the pupil, green is the support of spupil, blue the support of mpupil et black the support of ipupil.
42
43
!https://dev-lesia.obspm.fr/projets/attachments/download/570/pupil.png!
44
45
All these pupils are contained in arrays accessible as internal keywords of the following geom structure available from the Yorick API : 
46
47
<pre>
48
<code class="c">
49
struct geom_struct
50
{
51
   long  ssize;       // linear size of full image (in pixels)
52
   float zenithangle; // observations zenith angle (in deg)
53
   // internal keywords
54
   long  pupdiam;     // linear size of total pupil (in pixels)
55
   float cent;        // central point of the simulation
56
   pointer _ipupil;   // total pupil (include full guard band)
57
   pointer _mpupil;   // medium pupil (part of the guard band)
58
   pointer _spupil;   // small pupil (without guard band)
59
   ...
60
};
61
62
</code>
63
</pre>
64
65
some keywords have not been reported. Please check yoga_ao_ystruct.i for more details.
66
67
In this structure pupdiam (the diameter in pixels of the pupil is considered as an internal keyword). Two other structures contain the rest of the configuration parameters : 
68
69
<pre>
70
<code class="c">
71
struct tel_struct
72
{
73
    float diam;        // telescope diameter (in meters)
74
    float cobs;        // central obstruction ratio
75
};
76
</code>
77
</pre>
78
79
<pre>
80
<code class="c">
81
struct loop_struct
82
{
83
    long  niter;      // number of iterations
84
    float ittime;     // iteration time (in sec)
85
};
86
</code>
87
</pre>
88
89
There is one high-level routines to init the geometry with only one parameter: the pupil diameter in pixels. 
90
91
<pre>
92
<code class="c">
93
func geom_init(pupdiam)
94
    /* DOCUMENT geom_init
95
      geom_init,pupdiam
96
      inits simulation geometry, depending on pupdiam
97
      the linear number of pixels in the pupil
98
    */
99
100
</code>
101
</pre>
102
103
104
105
106
107
h3. Turbulence generation
108
109
The turbulence generation is done through the process of extruding infinite ribbons of Kolmogorov turbulence (see [[Model Description]]). An arbitrary number of turbulent layers can be defined at various altitude and various fraction of r0, wind speed and directions (in the range 0°-90°).
110
111
<pre>
112
<code class="c">
113
struct atmos_struct
114
{
115
    long    nscreens;    // number of turbulent layers
116
    float   r0;          // global r0 @ 0.5µm
117
    float   pupixsize;   // pupil piwel size (in meters)
118
    pointer dim_screens; // linear size of phase screens
119
    pointer alt;         // altitudes of each layer
120
    pointer winddir;     // wind directions of each layer
121
    pointer windspeed;   // wind speeds of each layer
122
    pointer frac;        // fraction of r0 for each layer
123
    pointer deltax;      // x translation speed (in pix / iteration) for each layer
124
    pointer deltay;      // y translation speed (in pix / iteration) for each layer
125
};
126
127
128
</code>
129
</pre>
130
131
The phase screens size is computed in agreement with the system components. The positions of the various targets (imaging targets or wavefront sensing guide stars) in the simulation define the required field of view and thus the size of the altitude phase screens.
132
133
To create a dynamic turbulence, the phase screens are extruded in columns and rows. The number of rows and columns extruded per iteration is computed using the specified wind speed and direction. Because extrusion is an integer operation (can't extrude a portion of a column), additional interpolation is required to provide an accurate model (with non integer phase shifts). In YoGA_Ao, a combination of integer extrusion and linear interpolation (in between four pixels) is used for each layer. The phase is integrated along specified directions across the multiple layers with the positions of light rays being re-evaluated for each iteration and screen ribbons being extruded when appropriate. This explains the need for a guard band around the ground layer phase screen as light rays can partly cross the pupil pixels depending on the iteration number.
134
135
The overall turbulence generation is done on the GPU and rely on a C++ class:
136
137
138
<pre>
139
<code class="c">
140
class yoga_tscreen
141
</code>
142
</pre>
143
144
This object contains all the elements to generate an infinite length phase screen including the extrusion method. All the screens for a given atmospheric configuration are centralized in another class:
145
146
147
148
<pre>
149
<code class="c">
150
class yoga_atmos
151
152
</code>
153
</pre>
154
155
In this object phase screens can be added dynamically thanks to the use of a map of yoga_tscreen This has many advantages the first of which being the indexation: screens are indexed by altitude (float) and the use of iterators greatly simplifies the code.
156
157
The corresponding Yorick opaque object is: 
158
159
<pre>
160
<code class="c">
161
 static y_userobj_t yAtmos
162
</code>
163
</pre>
164
165
and there are several Yorick wrappers to manipulate this object:
166
167
<pre>
168
<code class="c">
169
extern yoga_atmos;
170
    /* DOCUMENT yoga_atmos
171
       obj = yoga_atmos(nscreens,r0,size,size2,alt,wspeed,wdir,deltax,deltay,pupil[,ndevice])
172
       creates an yAtmos object on the gpu
173
    */
174
</code>
175
</pre>
176
177
178
<pre>
179
<code class="c">
180
extern init_tscreen;
181
    /* DOCUMENT init_tscreen
182
       init_tscreen,yoga_atmos_obj,altitude,a,b,istencilx,istencily,seed
183
       loads on the gpu in an yAtmos object and for a given screen data needed for extrude
184
    */
185
</code>
186
</pre>
187
188
189
<pre>
190
<code class="c">
191
extern get_tscreen;
192
    /* DOCUMENT get_tscreen
193
       screen = get_tscreen(yoga_atmos_obj,altitude)
194
       returns the screen in an yAtmos object and for a given altitude
195
    */
196
</code>
197
</pre>
198
199
<pre>
200
<code class="c">
201
extern get_tscreen_update;
202
    /* DOCUMENT get_tscreen_update
203
       vect = get_tscreen_update(yoga_atmos_obj,altitude)
204
       returns only the update vector in an yAtmos object and for a given altitude
205
    */
206
</code>
207
</pre>
208
209
<pre>
210
<code class="c">
211
extern extrude_tscreen;
212
    /* DOCUMENT extrude_tscreen
213
       extrude_tscreen,yoga_atmos_obj,altitude[,dir]
214
       executes one col / row screen extrusion for a given altitude in an yAtmos object 
215
    */
216
</code>
217
</pre>
218
219
220
Additionally there is a high-level routine to initialize the whole structure on the GPU from Yorick:
221
222
<pre>
223
<code class="c">
224
func atmos_init(void)
225
    /* DOCUMENT atmos_init
226
       atmos_init
227
       inits a yAtmos object on the gpu
228
       no input parameters
229
       requires 2 externals + 2 optional : y_atmos and y_geom + y_target and y_wfs
230
       y_atmos  : a y_struct for the atmosphere
231
       y_geom   : a y_struct for the geometry of the simulation
232
       y_target : a y_struct for the targets
233
       y_wfs    : a y_struct for the sensors
234
       creates 1 external :
235
       g_atmos : a yAtmos object on the gpu
236
    */
237
238
</code>
239
</pre>
240
241
242
243
244
h3. Wavefront Sensing
245
246
Wavefront sensing is done in two steps: first compute the Shack-Hartmann sub-images including diffraction effect and noise and then from these images, compute the centroids. The overall model is described here [[Model Description]].
247
248
The pixel size requested by the user for the sub-apertures images are approximated following a rather robust approach to cope for any kind of dimensioning. We used an empirical coefficient to set the simulated subaps field of view (FoV) to 6 times the ratio of the observing wavelength over r_0 at this wavelength. This provides sufficient FoV to include most of the turbulent speckles. The same empirical coefficient is used to define de number of phase points per subaps as 6 times the ratio of the subaps diameter over r_0. This ensures a proper sampling of r_0. From this number of phase points we compute the size of the support in the Fourier domain. The "quantum pixel size" is then deduced from the ratio of the wavelength over r_0 over the size of the Fourier support. Then the pixel size actually simulated is obtained using the product of an integer number by this quantum pixel size as close as possible to the requested pixel size.
249
250
The wavefront sensor model description is stored in the following Yorick structure. 
251
252
<pre>
253
<code class="c">
254
struct wfs_struct
255
{
256
  long  nxsub;          // linear number of subaps
257
  long  npix;           // number of pixels per subap
258
  float pixsize;        // pixel size (in arcsec) for a subap
259
  float lambda;         // observation wavelength (in µm) for a subap
260
  float optthroughput;  // wfs global throughput
261
  float fracsub;        // minimal illumination fraction for valid subaps
262
  
263
  //target kwrd
264
  float xpos;      // guide star x position on sky (in arcsec) 
265
  float ypos;      // guide star x position on sky (in arcsec) 
266
  float gsalt;     // altitude of guide star (in m) 0 if ngs 
267
  float gsmag;     // magnitude of guide star
268
  float zerop;     // detector zero point
269
  
270
  // lgs only
271
  float lgsreturnperwatt;  // return per watt factor (high season : 10 ph/cm2/s/W)
272
  float laserpower;        // laser power in W
273
  float lltx;              // x position (in meters) of llt
274
  float llty;              // y position (in meters) of llt
275
  string proftype;         // type of sodium profile "gauss", "exp", etc ...
276
  float beamsize;          // laser beam fwhm on-sky (in arcsec)
277
...
278
};
279
280
</code>
281
</pre>
282
283
284
285
h3. Image formation
286
287
<pre>
288
<code class="c">
289
struct target_struct
290
{
291
  long    ntargets;  // number of targets
292
  pointer lambda;    // observation wavelength for each target
293
  pointer xpos;      // x positions on sky (in arcsec) for each target
294
  pointer ypos;      // y positions on sky (in arcsec) for each target
295
  pointer mag;       // magnitude for each target
296
};
297
</code>
298
</pre>
299
300
301
302
303
304
h2. List of routines
305
306
h3. High-level routines
307
308
h3. Advanced routines
309
310
311
<pre>
312
<code class="c">
313
extern _GetMaxGflopsDeviceId  //get the ID of the best CUDA-capable device on your system
314
</code>
315
</pre>