| 335 | |
| 336 | |
| 337 | |
| 338 | |
| 339 | |
| 340 | |
| 341 | |
| 342 | |
| 343 | |
| 344 | |
| 345 | |
| 346 | |
| 347 | |
| 348 | |
| 349 | |
| 350 | |
| 351 | |
| 352 | |
| 353 | |
| 354 | [=#part_6 '''6. Output of user-defined flight measurements'''] \\\\ |
| 355 | This example shows the output of two user-defined quantities for the absolute values of the horizontal velocities u and v captured by virtual flight measurements. The given quantities will be captured for each leg. \\\\ |
| 356 | |
| 357 | 1. At first, the number of user-defined quantities has to be given in [../int#user_init_flight user_init_flight] by |
| 358 | |
| 359 | {{{num_var_fl_user = num_var_fl_user + 2}}} |
| 360 | |
| 361 | 2. In the following, for each user-defined quantity you have to give a label and a unit (subroutine [../int#user_init_flight user_init_flight]), which will be used for the netCDF file. They must not contain more than '''13''' characters. |
| 362 | |
| 363 | {{{CASE ( 1 )}}} |
| 364 | {{{dofl_label(k) = TRIM(label_leg) // '_' // 'abs_u'}}}\\ |
| 365 | {{{dofl_unit(k) = 'm/s'}}}\\ |
| 366 | {{{k = k + 1}}} \\\\ |
| 367 | |
| 368 | {{{CASE ( 2 )}}} |
| 369 | {{{dofl_label(k) = TRIM(label_leg) // '_' // 'abs_v'}}}\\ |
| 370 | {{{dofl_unit(k) = 'm/s'}}}\\ |
| 371 | {{{k = k + 1}}}\\ |
| 372 | |
| 373 | |
| 374 | 3. The user-defined quantities are calculated in subroutine [../int#user_flight user_flight] at every timestep. Note, the identifier in the {{{CASE()}}} argument must be set accordingly to the settings used in [../int#user_init_flight user_init_flight]. |
| 375 | |
| 376 | {{{CASE ( 1 )}}} |
| 377 | {{{DO i = nxl-1, nxr+1}}} |
| 378 | {{{DO j = nys-1, nyn+1}}} |
| 379 | {{{DO k = nzb, nzt}}} |
| 380 | {{{var(k,j,i) = ABS( u(k,j,i )}}} |
| 381 | {{{ENDDO}}} |
| 382 | {{{ENDDO}}} |
| 383 | {{{ENDDO}}} |
| 384 | |
| 385 | {{{CASE ( 2 )}}} |
| 386 | {{{DO i = nxl-1, nxr+1}}} |
| 387 | {{{DO j = nys-1, nyn+1}}} |
| 388 | {{{DO k = nzb, nzt}}} |
| 389 | {{{var(k,j,i) = ABS( v(k,j,i )}}} |
| 390 | {{{ENDDO}}} |
| 391 | {{{ENDDO}}} |
| 392 | {{{ENDDO}}} \\\\ |
| 393 | |
| 394 | Flight measurements as well as data output of the respective user-defined quantities is done automatically. |
| 395 | |
| 396 | |
| 397 | |
| 398 | |
| 399 | |
| 400 | |
| 401 | |
| 402 | |
| 403 | |
| 404 | |