Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dirfile2ascii(1) [debian man page]

dirfile2ascii(1)						      GETDATA							  dirfile2ascii(1)

NAME

       dirfile2ascii -- output dirfile database vectors as ASCII text

SYNOPSIS

       dirfile2ascii [ OPTION ]... DIRFILE
	      [ [ -a | -A | -e | -E | -F | -g | -G | -o | -i | -u | -x | -X ] FIELD ]...

DESCRIPTION

       Fetches data from a dirfile(5) database specified by DIRFILE and writes it as ASCII to standard output.	Any number of vector FIELDs may be
       specified.  Each specified field is printed in a separate column.

       Mandatory arguments to long options are mandatory for short options too.

       -d, --delimeter=delim
	      separate columns by delim.  (Default: a single space.)

       -f, --first-frame=first_frame-last_frame
	      read from frame first_frame to frame last_frame (inclusive).

       -f, --first-frame=first_frame:nframes
	      equivalent to --first-frame=first_frame --num-frames=nframes.

       -f, --first-frame=first_frame
	      If first_frame >= 0, start reading at frame first_frame.	If first_frame is -1 and --num-frames=nframes is specified, read the  last
	      nframes frames.  If --first-frame is not specified, reading starts at frame zero.

       -n, --num-frames=nframes
	      read at most nframes frames.  If not specified, or if nframes = 0, all frames to the end-of-field are read.

       -p, --precision=format
	      use  format  to  format  output.	 format  may contain any of the flag characters, a field width, and/or a precision as specified in
	      printf(3).  It may not contain a length modifier.

       -q, --quiet
	      don't write diagnostic messages on standard error.  (This is the default behaviour).

       -s, --skip=frame_skip
	      if frame_skip > 0, output only one sample for every frame_skip frames.

       -v, --verbose
	      write diagnostic messages on standard error.

       -z, --fill=STRING
	      Fill columns which go past the end of their corresponding field with the string STRING.  The default behaviour is  to  fill  columns
	      with  floating-point  conversions  with NaN and columns with integer conversion with 0, which mirrors what occurs when an attempt is
	      made to print data from before the start of a field.  (Note: the default behaviour cannot be  reproduced	with  this  option,  since
	      STRING is applied to all columns, regardless of conversion type.)

       In  addition  to  the above, each FIELD argument may be preceded by a short option, one of: -a, -A, -e, -E, -F, -g, -G, -i, -o, -u, -x, -X,
       indicating the conversion to be used.  See printf(3) for the meaning of these conversion specifiers.  The output flags, width,  and  preci-
       sion may be specified by using --precision.  If no conversion specifier is given, %f is used.

       For  conversion specifiers %a, %A, %e, %E, %f, %F, %g, %G, data is read from the dirfile as double precision floats.  For conversion speci-
       fier %i, data is read as 64-bit signed integers.  For conversion specifiers %o, %u, %x, %X, data is read as 64-bit unsigned integers.

LIMITATIONS

       No native support for printing complex data is provided.  This may be worked around by using dirfile(5) representation suffixes.  For exam-
       ple, the command

	      $ dirfile2ascii DIRFILE FIELD.r FIELD.i

       will print the real and imaginary parts of the complex valued field FIELD in the first and second columns, respectively.

SEE ALSO

       dirfile(5), printf(3)

Version 0.7.1							 30 November 2010						  dirfile2ascii(1)

Check Out this Related Man Page

gd_bof(3)							      GETDATA								 gd_bof(3)

NAME

       gd_bof -- report the start of data in a field

SYNOPSIS

       #include <getdata.h>

       off_t gd_bof(DIRFILE *dirfile, const char *field_code);

DESCRIPTION

       The gd_bof() function queries a dirfile(5) database specified by dirfile and returns the sample number of the beginning-of-field marker for
       the vector field given by field_code.

       The caller should not assume that the beginning-of-field marker falls on a frame boundary.  The beginning-of-field marker  is  never  nega-
       tive.

       For  a RAW field, the beginning-of-field corresponds to the frame offset of that field (see gd_frameoffset(3)).	The beginning-of-field for
       all other vector field type is the same as the beginning-of-field of whichever of its input fields that starts latest.	The  beginning-of-
       field marker for the special field INDEX is always zero.

       The beginning-of-field marker for a field containing no data is in the same location as, or after, its end-of-field marker (see gd_eof(3)).
       For a RAW field, the difference between the locations of the beginning- and end-of-field markers indicates the number of  samples  of  data
       actually stored on disk.

       The dirfile argument must point to a valid DIRFILE object previously created by a call to gd_open(3).

RETURN VALUE

       Upon successful completion, gd_bof() returns the sample number of the end-of-field marker for the indicated field.  On error, it returns -1
       and sets the dirfile error to a non-zero error value.  Possible error values are:

       GD_E_BAD_CODE
	       The field specified by field_code or one of the fields it uses as input was not found in the database.

       GD_E_BAD_DIRFILE
	       The supplied dirfile was invalid.

       GD_E_BAD_REPR
	       The representation suffix specified in field_code, or in one of its inputs was not recognised.

       GD_E_DIMENSION
	       A scalar field was found where a vector field was expected in the definition of field_code or one of its inputs, or else field_code
	       itself specified a scalar field.

       GD_E_RECURSE_LEVEL
	       Too  many levels of recursion were encountered while trying to resolve field_code.  This usually indicates a circular dependency in
	       field specification in the dirfile.

       The dirfile error may be retrieved by calling gd_error(3).  A descriptive error string for the last error encountered can be obtained  from
       a call to gd_error_string(3).

SEE ALSO

       dirfile(5), dirfile-encoding(5), gd_open(3), gd_eof(3), gd_error(3), gd_error_string(3), gd_nframes(3)

Version 0.7.0							  15 October 2010							 gd_bof(3)
Man Page