next up previous
Next: Structures
Up: Examples
Previous: Getting Started

Formatting

If you wish to use the output for some documentation you might like to align the trace into neat columns. In the above examples the type of the DATA_ARRAY is displaced because of the dimensions. The indentation of the type with respect to the start of the name, and the values with respect to the start of the type may be controlled by parameters TYPIND and VALIND respectively. For example,

    % hdstrace beq typind=20
 
    BEQ  <IMAGE>
       TITLE               <_CHAR*72>      'KAPPA - Glitch'
       DATA_ARRAY(109,64)  <_REAL>         124,92,98,156,171,166,171,181,190,
                                           ... 127.56,128.36,129.4,130.08,130.44
       DATA_MIN            <_REAL>         12
       DATA_MAX            <_REAL>         254

    End of Trace.
indents the type five characters more than the default.

There is another way to format the output, and that it to place the values on a new line rather than appending them to the name and type. This can help when dealing with moderate-sized arrays.

    % hdstrace beq newline
 
    BEQ  <IMAGE>
       TITLE          <_CHAR*72>   
        'KAPPA - Glitch'
       DATA_ARRAY(109,64)  <_REAL>   
        124,92,98,156,171,166,171,181,190,180,196,205,217,211,204,210,202,197,
        ... 127.16,126.2,126.36,126.6,127.32,127.56,128.36,129.4,130.08,130.44
       DATA_MIN       <_REAL>   
        12
       DATA_MAX       <_REAL>   
        254

    End of Trace.
A record of the trace may be stored in an text file given by the parameter LOGFILE. The width of the output may be altered to 132 characters instead of 80 via parameter WIDEPAGE.

next up previous
Next: Structures
Up: Examples
Previous: Getting Started

HDSTRACE --- Listing HDS Data Files
Starlink User Note 102
Malcolm J. Currie
1993 November 5
E-mail:ussc@star.rl.ac.uk

Copyright © 2009 Science and Technology Facilities Council