Changeset 797 for XIOS/trunk/doc/inputs/user
- Timestamp:
- 11/26/15 10:56:17 (9 years ago)
- Location:
- XIOS/trunk/doc/inputs/user
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
XIOS/trunk/doc/inputs/user/Axis.lyx
r669 r797 287 287 \end_layout 288 288 289 \begin_layout Itemize 290 inverse_axis: Inverse an axis 291 \end_layout 292 289 293 \begin_layout Standard 290 294 It is not difficult to define a transformation: Include type of transformation … … 315 319 \begin_layout Plain Layout 316 320 317 <zoom_axis zoom_begin="1" zoom_ size="3"/>321 <zoom_axis zoom_begin="1" zoom_n="3"/> 318 322 \end_layout 319 323 … … 334 338 335 339 \begin_layout Standard 336 The concrete example above says many things: the axis named axis_A_zoom337 is transformedfrom axis name axis_A with a zoom activity.340 The concrete example is translated as: the axis named axis_A_zoom is transformed 341 from axis name axis_A with a zoom activity. 338 342 The detailed attributes of zoom_axis can be found in reference document, 339 343 but simply it contains the begining and size of zoomed region. -
XIOS/trunk/doc/inputs/user/Domain.lyx
r669 r797 321 321 \end_layout 322 322 323 \begin_layout Itemize 324 generate_rectilinear_domain: auto generating, distributing a rectilinear 325 domain then filling all mandatory attributes. 326 \end_layout 327 323 328 \begin_layout Standard 324 329 It is not difficult to define a transformation: Include type of transformation … … 368 373 369 374 \begin_layout Standard 370 The concrete example above says many things: a domain named domain_A_zoom375 The concrete example above tells many things: a domain named domain_A_zoom 371 376 is transformed from domain name domain_A with a zoom activity. 377 The domain_A_zoom is the zoomed region of domain_A. 372 378 The detailed attributes of zoom_domain can be found in reference document, 373 379 but simply it contains the begining and size of zoomed region. … … 475 481 476 482 \begin_layout Standard 477 Although xml is helpful to define several configurations, it can not be478 usedto customize attributes of domain.483 Although xml is helpful to define several configurations, it is not convenient 484 to customize attributes of domain. 479 485 So it's the turn of Fortran interface. 480 486 \end_layout … … 772 778 In case of one-dimensional data, it is only necessary to determine data_ibegin 773 779 and data_ni. 774 Although the valid data must be inside a domain, it is not neccessary for775 data to have same size asdomain.780 Although the valid data must be inside a local domain, it is not neccessary 781 for data to have same size as local domain. 776 782 In fact, data can have larger size than domain on each dimension, this 777 783 is often the case of … … 844 850 \end_inset 845 851 846 , local domain occupies the center of the global domain, where asreal data852 , local domain occupies the center of the global domain, where real data 847 853 fill up a larger region. 848 854 Only data inside the local domain, represented by blue cells, are valid. … … 938 944 939 945 \begin_layout Standard 940 With the same domain_A, we can have longitude and latitudeby calling:946 With the same domain_A, we can set longitude and latitude values by calling: 941 947 \end_layout 942 948
Note: See TracChangeset
for help on using the changeset viewer.