Projet

Général

Profil

SUTrA features » Historique » Version 2

Damien Gratadour, 11/11/2013 10:39

1 2 Damien Gratadour
h1. SuTrA features
2 1 Damien Gratadour
3 2 Damien Gratadour
The SuTrA library 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
6
[List of features](#List) 
7
8
+ [Simulation geometry](#Geom)
9
10
+ [Turbulence generation](#Turbu)
11
12
+ [Wavefront Sensing](#WFS)
13
14
+ [Image formation](#Image)
15
16
[List of routines](#Routines)
17
18
+ [High-level routines](#High)
19
20
+ [Advanced routines](#Advanced) 
21
22
<a name="wiki-List"></a>
23
##List of features
24
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:
25
26
* Kolmogorov-type turbulence generation over an arbitrary number of layers with arbitrary properties.
27
28
* Shack-Hartmann wavefront sensing including Laser Guide Stars (LGS)
29
30
* Short and long exposure imaging under the turbulence
31
32
<a name="wiki-Geom"></a>
33
###Simulation geometry
34
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. 
35
36
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. 
37
38
To cope for these various requirements we can define 3 different pupils: 
39
40
* the large pupil (called ipupil) defined on the largest support (4kx4k in our previous example) more than half of which being 0
41
42
* the small pupil (spupil) defined only on the pupil size (2kx2k in our previous example) most of it being 1
43
44
* 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.
45
46
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.
47
48
[[http://github.com/dgratadour/yoga_ao/raw/master/pictures/pupil.png]]
49
50
All these pupils are contained in arrays accessible as internal keywords of the following geom structure available from the Yorick API :
51
```c
52
struct geom_struct
53
{
54
   long  ssize;       // linear size of full image (in pixels)
55
   float zenithangle; // observations zenith angle (in deg)
56
   // internal keywords
57
   long  pupdiam;     // linear size of total pupil (in pixels)
58
   float cent;        // central point of the simulation
59
   pointer _ipupil;   // total pupil (include full guard band)
60
   pointer _mpupil;   // medium pupil (part of the guard band)
61
   pointer _spupil;   // small pupil (without guard band)
62
   ...
63
};
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
```c
69
struct tel_struct
70
{
71
    float diam;        // telescope diameter (in meters)
72
    float cobs;        // central obstruction ratio
73
};
74
```
75
```c
76
struct loop_struct
77
{
78
    long  niter;      // number of iterations
79
    float ittime;     // iteration time (in sec)
80
};
81
```
82
83
There is one high-level routines to init the geometry with only one parameter: the pupil diameter in pixels.
84
```c
85
func geom_init(pupdiam)
86
    /* DOCUMENT geom_init
87
      geom_init,pupdiam
88
      inits simulation geometry, depending on pupdiam
89
      the linear number of pixels in the pupil
90
    */
91
```
92
93
<a name="wiki-Turbu"></a> 
94
###Turbulence generation
95
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°).
96
97
```c
98
struct atmos_struct
99
{
100
    long    nscreens;    // number of turbulent layers
101
    float   r0;          // global r0 @ 0.5µm
102
    float   pupixsize;   // pupil piwel size (in meters)
103
    pointer dim_screens; // linear size of phase screens
104
    pointer alt;         // altitudes of each layer
105
    pointer winddir;     // wind directions of each layer
106
    pointer windspeed;   // wind speeds of each layer
107
    pointer frac;        // fraction of r0 for each layer
108
    pointer deltax;      // x translation speed (in pix / iteration) for each layer
109
    pointer deltay;      // y translation speed (in pix / iteration) for each layer
110
};
111
```
112
113
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.
114
115
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.
116
117
The overall turbulence generation is done on the GPU and rely on a C++ class:
118
```c++
119
class yoga_tscreen
120
```
121
122
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:
123
124
```c++
125
class yoga_atmos
126
```
127
128
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. 
129
130
The corresponding Yorick opaque object is:
131
```c
132
    static y_userobj_t yAtmos
133
```
134
135
and there are several Yorick wrappers to manipulate this object:
136
137
```c
138
extern yoga_atmos;
139
    /* DOCUMENT yoga_atmos
140
       obj = yoga_atmos(nscreens,r0,size,size2,alt,wspeed,wdir,deltax,deltay,pupil[,ndevice])
141
       creates an yAtmos object on the gpu
142
    */
143
```
144
145
```c
146
extern init_tscreen;
147
    /* DOCUMENT init_tscreen
148
       init_tscreen,yoga_atmos_obj,altitude,a,b,istencilx,istencily,seed
149
       loads on the gpu in an yAtmos object and for a given screen data needed for extrude
150
    */
151
```
152
153
```c
154
extern get_tscreen;
155
    /* DOCUMENT get_tscreen
156
       screen = get_tscreen(yoga_atmos_obj,altitude)
157
       returns the screen in an yAtmos object and for a given altitude
158
    */
159
```
160
161
```c
162
extern get_tscreen_update;
163
    /* DOCUMENT get_tscreen_update
164
       vect = get_tscreen_update(yoga_atmos_obj,altitude)
165
       returns only the update vector in an yAtmos object and for a given altitude
166
    */
167
```
168
169
```c
170
extern extrude_tscreen;
171
    /* DOCUMENT extrude_tscreen
172
       extrude_tscreen,yoga_atmos_obj,altitude[,dir]
173
       executes one col / row screen extrusion for a given altitude in an yAtmos object 
174
    */
175
```
176
177
Additionally there is a high-level routine to initialize the whole structure on the GPU from Yorick:
178
179
```c
180
func atmos_init(void)
181
    /* DOCUMENT atmos_init
182
       atmos_init
183
       inits a yAtmos object on the gpu
184
       no input parameters
185
       requires 2 externals + 2 optional : y_atmos and y_geom + y_target and y_wfs
186
       y_atmos  : a y_struct for the atmosphere
187
       y_geom   : a y_struct for the geometry of the simulation
188
       y_target : a y_struct for the targets
189
       y_wfs    : a y_struct for the sensors
190
       creates 1 external :
191
       g_atmos : a yAtmos object on the gpu
192
    */
193
```
194
195
<a name="wiki-WFS"></a>
196
###Wavefront sensing
197
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]]. 
198
199
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.
200
201
The wavefront sensor model description is stored in the following Yorick structure.
202
```
203
struct wfs_struct
204
{
205
  long  nxsub;          // linear number of subaps
206
  long  npix;           // number of pixels per subap
207
  float pixsize;        // pixel size (in arcsec) for a subap
208
  float lambda;         // observation wavelength (in µm) for a subap
209
  float optthroughput;  // wfs global throughput
210
  float fracsub;        // minimal illumination fraction for valid subaps
211
  
212
  //target kwrd
213
  float xpos;      // guide star x position on sky (in arcsec) 
214
  float ypos;      // guide star x position on sky (in arcsec) 
215
  float gsalt;     // altitude of guide star (in m) 0 if ngs 
216
  float gsmag;     // magnitude of guide star
217
  float zerop;     // detector zero point
218
  
219
  // lgs only
220
  float lgsreturnperwatt;  // return per watt factor (high season : 10 ph/cm2/s/W)
221
  float laserpower;        // laser power in W
222
  float lltx;              // x position (in meters) of llt
223
  float llty;              // y position (in meters) of llt
224
  string proftype;         // type of sodium profile "gauss", "exp", etc ...
225
  float beamsize;          // laser beam fwhm on-sky (in arcsec)
226
...
227
};
228
```
229
230
<a name="wiki-Image">
231
###Image formation
232
```
233
struct target_struct
234
{
235
  long    ntargets;  // number of targets
236
  pointer lambda;    // observation wavelength for each target
237
  pointer xpos;      // x positions on sky (in arcsec) for each target
238
  pointer ypos;      // y positions on sky (in arcsec) for each target
239
  pointer mag;       // magnitude for each target
240
};
241
```
242
243
<a name="wiki-Routines">
244
##List of routines
245
246
<a name="wiki-High">
247
##High-level routines
248
249
<a name="wiki-Advanced">
250
##Advanced routines
251
* __**extern _GetMaxGflopsDeviceId**__ get the ID of the best CUDA-capable device on your system