miriad 4.1.0.0

data/ext/miriad_ruby.c

@@ -0,0 +1,602 @@
+/*
+ * This file is just to document the classes/methods from the SWIG wrappers
+ * that we want to document.  It is for rdoc, not gcc.  At least for now.
+ * Eventually, it might be nice to dump SWIG since I seem to spend more time
+ * keeping it happy than it seems to save.
+ */
+
+#define static typedef
+#define VALUE int
+
+/*
+ * Document-class: Miriad
+ */
+
+/*
+ * Document-class: Miriad::Uvio
+ */
+
+/*
+ * Document-method: initialize
+ * 
+ * call-seq: Uvio.new(name, status)
+ * 
+ * <b>NOTE: This method provides lower-level access than the open() method.  It
+ * may disappear in future versions.</b>
+ *
+ * Opens a uv dataset and readies it for access.  Here +name+ is the dataset's
+ * name.  +status+ can be: <tt>'old'</tt> or <tt>'read'</tt> to open an
+ * existing dataset for reading, <tt>'new'</tt> or <tt>'write'</tt> to create a
+ * new dataset, or <tt>'append'</tt> to add to an existing dataset
+ */
+static VALUE uvio_initialize();
+
+/*
+ * Document-method: close
+ *
+ * call-seq: close() -> nil
+ *
+ * Closes the uv dataset.
+ */
+static VALUE uvio_close;
+
+/*
+ * Document-method: flush
+ *
+ * call-seq: flush() -> nil
+ *
+ * Flush buffers of the uv dataset to disk.
+ */
+static VALUE uvio_flush;
+
+/*
+ * Document-method: uvnext
+ *
+ * call-seq: uvnext() -> nil
+ *
+ * Skip to the next uv data record. When writing, this causes an end-of-record
+ * mark to be written. When reading, this causes data to be read up until the
+ * next end-of-record mark.
+ */
+static VALUE uvio_uvnext;
+
+/*
+ * Document-method: rewind
+ *
+ * call-seq: rewind() -> nil
+ *
+ * Rewind a uv file, readying it to be read from the begining again.
+ */
+static VALUE uvio_rewind;
+
+/*
+ * Document-method: probvr
+ *
+ * call-seq: probvr(var) -> [type, length, updated] or nil
+ *
+ * Checks whether a the uv variable +var+ exists. If it does, returns a three
+ * element array indicating the variable's type, (current) length, and whether
+ * it was updated on the last call to read or scan.  If it doesn't exist, it
+ * returns nil.
+ *
+ * +type+ can be one of...
+ *
+ * * <tt>'a'</tt> - ASCII data
+ * * <tt>'i'</tt> - Integer data
+ * * <tt>'r'</tt> - Single precision real data
+ * * <tt>'d'</tt> - Double precision real data
+ * * <tt>'c'</tt> - Single precision complex data
+ */
+static VALUE uvio_probvr;
+
+/*
+ * Document-method: putvr
+ *
+ * call-seq: putvr(var, data, type=-1) -> nil
+ *
+ * Writes +data+ as the value of a uv variable +var+.  +data+ can be a Ruby
+ * object, an Array of Ruby objects, or an NArray.
+ * 
+ * If +type+ is -1, the default, the MIRIAD type will be autodetected from
+ * +data+.  Generally, this works well only for Strings and NArrays, but not
+ * for Numeric types.  For full control, specify +type+ as one of...
+ *
+ * * <tt>?a</tt> - ASCII data
+ * * <tt>?i</tt> - Integer data
+ * * <tt>?r</tt> - Single precision real data
+ * * <tt>?d</tt> - Double precision real data
+ */
+static VALUE uvio_putvr;
+
+/*
+ * Document-method: scan
+ *
+ * call-seq: scan(var) -> nil
+ *
+ * Scan through the uv file until variable +var+ changes. This always reads to
+ * the end of the record in which +var+ was encountered (i.e. until all
+ * variables that change simultaneously are read).
+ */
+static VALUE uvio_scan;
+
+/*
+ * Document-method: write
+ *
+ * call-seq: write(preamble, data, flags) -> [preamble, data, flags]
+ *
+ * Write a visibility record to the uv dataset.  Please note +write+ closes the
+ * record. Any wideband data should have been written with +wwrite+ before this
+ * call.
+ *
+ * +preamble+ can be an Array or NArray of 4 or 5 elements giving _u_, _v_,
+ * optionally _w_ (see uvset()), _time_, and _baseline_ (in that order).  If
+ * +preamble+ is an NArray, it must be of type NArray::DFLOAT.
+ *
+ * +data+ is the complex correlation data.  It can be an Array or NArray.  If
+ * it is an Array, it must have the real and imaginary components in
+ * consecutive elemtents (specifically, Complex Array elements are not [yet]
+ * supported).  If it is an NArray, it must be of type NArray::SFLOAT (with
+ * real and imaginary components in consecutive elements) or NArray::SCOMPLEX
+ * (with complex elements).
+ *
+ * +flags+ can be an Array or NArray.  If it is an NArray, it must be of type
+ * NArray::LINT.  Note that +flags+ must have as many elements as +data+ has
+ * complex data points.  This will be either half as many elements as +data+
+ * (if +data+ has real and imaginary components in consecutive elements) or the
+ * same number of elements as +data+ (if +data+ is NArray::SCOMPLEX).
+ */
+static VALUE uvio_write;
+
+/*
+ * Document-method: wwrite
+ *
+ * call-seq: wwrite(preamble, data, flags) -> [preamble, data, flags]
+ *
+ * Write a wide-band visibility record to the data file. Make sure this routine
+ * is called before write(), since that closes the record.
+ *
+ * See write() for a discussion of preamble, data, and flags.
+ *
+ */
+static VALUE uvio_wwrite;
+
+/*
+ * Document-method: set
+ *
+ * call-seq: set(object, type, n=0, p1=0.0, p2=0.0, p3=0.0) -> nil
+ *
+ * Modifies the behavior of the read and write methods.
+ *
+ * ==== How set affects read
+ *
+ * The uvread routine can perform, at the programmer's request, extra
+ * processing steps on the visibility data. These steps consist of averaging
+ * and resampling frequency channels, uv coordinate conversion and some
+ * corrections for planet observations. The steps are requested by calls to
+ * set. In the call to set, +object+ (String) gives the general processing step
+ * that is being requested. The +type+ argument (String) gives more specific
+ * details, and the arguments +n+ (Integer) and <tt>p1</tt>, <tt>p2</tt> and
+ * <tt>p3</tt> (Floats) give any numerical values needed.
+ *
+ * Note that the setup given by set only becomes correctly activated during
+ * the next call to read. Before this next call, the setup is in a somewhat
+ * nebulous state.  You should not expect various other routines associated
+ * with read to work as expected until after the next call to read.
+ * Associated routines include flagwr and info [info not yet implemented].
+ *
+ * The possible values of the arguments to set are summarized below. Not all
+ * parameters are used in every case.  If a parameter is not mentioned for a
+ * particular usage, then it is ignored. While several processing steps can be
+ * performed simultaneously (several calls to set will be needed to specify
+ * them all), others are mutually inconsistent. When mutually inconsistent
+ * steps are requested, the last requested step is honored.
+ *
+ * * <tt>object='data'</tt> -> n=_nchan_, p1=_start_, p2=_width_, p3=_step_
+ *
+ *   This gives operations on the spectral data.
+ *
+ *   * <tt>type='channel'</tt> selects the channels to be returned, and
+ *     possible averaging together of the channel data. If the original
+ *     channels are numbers from 1 to _N_, then, by using
+ *     <tt>type='channel'</tt>, read will return _nchan_ massaged channels,
+ *     where the <em>i</em>th channel of the massaged channels is formed by
+ *     averaging _width_ channels of the original data, starting at channel
+ *     (_i_-1)*_step_+_start_. If set is called with _nchan_ being zero, all
+ *     channels are selected (note that this only makes sense if _start_,
+ *     _step_, and _width_ are all 1).
+ *
+ *   * <tt>type='wide'</tt> is similar, but uses the continuum data rather than
+ *     the spectral data.
+ *
+ *   * <tt>type='velocity'</tt> is also similar, returning a weighted sum of
+ *     the spectral data. However in this case _start_, _width_ and _step_ are
+ *     given in units of km/s (rather than channels). This is particularly
+ *     useful if the spectrometer setup is not constant throughout the data or
+ *     there is no Doppler tracking, and so the velocity of a given channel
+ *     changes.
+ *
+ *   * Note that 'channel', 'wide', and 'velocity' are mutually exclusive. The
+ *     default is 'channel' (or wide if there is no spectral data in the file),
+ *     with _start_, _width_, and _step_ of 1.
+ *
+ *   * If there are fewer than _nchan_ channels, then dummy channels, which are
+ *     flagged as bad, are added. If _nchan_ is specified as 0, then read will
+ *     return as many channels as possible.
+ *
+ * * <tt>object='reference'</tt> -> p1=_start_, p2=_width_
+ *
+ *   The "reference line" is a spectral channel, or an average of spectral
+ *   channels, which the main data is divided by. Typically the reference line
+ *   would be a strong point source (e.g. a maser). The resultant data is
+ *   essentially normalized and shifted, but it also has atmospheric-based and
+ *   instrument-base calibration problems removed. The extra parameters needed
+ *   to describe the reference line is the same as for <tt>object='data'</tt>,
+ *   except that the number of channels, and the increment is ignored (there is
+ *   only ever one reference line). The default is not to have a reference
+ *   line.
+ *
+ * * <tt>object='coord'</tt>
+ *
+ *   This sets the units of the u, v, and w coordinates returned in the
+ *   preamble.  Using <tt>type='wavelength'</tt> or <tt>type='nanosec'</tt>
+ *   sets the units of the returned coordinates. For <tt>'wavelength'</tt>, the
+ *   sky frequency used is that of the first channel returned. The default
+ *   value is <tt>'nanosec'</tt>.
+ *
+ * * <tt>object='planet'</tt> -> p1=_plmaj_, p2=_plmin_, p3=_plangle_
+ *
+ *   This causes the u and v coordinates to be scaled and rotated, and the
+ *   correlation values to be scaled, to adjust for changes when observing
+ *   planets. The parameters _plmaj_, _plmin_ and _plangle_ give the reference
+ *   size (arcseconds) and position angle (degrees) of the planet. If the
+ *   reference size is 0, then the size of the first selected data record is
+ *   used.
+ *
+ * * <tt>object='selection'</tt> -> n=_n_
+ *
+ *   This gives extra control over the uv selection process. Currently
+ *   there is only one possible type, <tt>'amplitude'</tt>, which enables or disables the
+ *   amplitude selection process. If the argument _n_ is positive, then amplitude
+ *   selection is applied (i.e. the normal action), otherwise amplitude
+ *   selection is not applied.
+ *
+ * * <tt>object='preamble'</tt>
+ *
+ *   * <tt>type='uv/time/baseline'</tt> - The preamble will be read as four
+ *     doubles: _u_, _v_, _time_, and _baseline_.  If the dataset was written with five
+ *     element preambles, _w_ will be discarded.
+ *
+ *   * <tt>type='uvw/time/baseline'</tt> - The preamble will be read as five
+ *     doubles: _u_, _v_, _w_, _time_, and _baseline_.  If the dataset was
+ *     written with four element preambles, _w_ will be set to 0.0.
+ *
+ * ==== How set affects write
+ *
+ * * <tt>object='corr'</tt>
+ *
+ *   The uv routines allow the correlation data to be stored on disk, either as
+ *   floating point numbers, or as 16 bit integers with an associated scale
+ *   factor. The 16 bit format roughly halves the disk space required, but
+ *   slows the read and write operation, and can cause precision problems. On
+ *   the first call to write, the uv routines decide on the format to use,
+ *   using a simple rule. The set method can be used to override this rule. To
+ *   be of use, it must be called before the first call to write. The type
+ *   argument is a single character, being <tt>'r'</tt> or <tt>'j'</tt>, which
+ *   instructs floating point or scaled integers, respectively, to be used.
+ *
+ * * <tt>object='data'</tt>
+ *
+ *   This controls whether write() writes the data to the +corr+ or +wcorr+
+ *   variable. The default is to write it to the +corr+ item (i.e. it assumes
+ *   that the data is spectral, rather than continuum data).
+ *
+ * * <tt>object='preamble'</tt>
+ *
+ *   * <tt>type='uv/time/baseline'</tt> - The preamble will be written as four
+ *     doubles: _u_, _v_, _time_, and _baseline_.
+ *
+ *   * <tt>type='uvw/time/baseline'</tt> - The preamble will be written as five
+ *     doubles: _u_, _v_, _w_, _time_, and _baseline_.
+ */
+static VALUE uvio_set;
+
+/*
+ * Document-method: uvread
+ *
+ * call-seq: uvread(preamble, data, flags) -> [nread, preamble, data, flags]
+ *
+ * <b>NOTE: This method provides lower-level access than the read() method.  It
+ * may disappear in future versions.</b>
+ *
+ * This reads a single visibility from the data file. This starts by scanning
+ * the uv data stream until a correlation record is found. The correlations are
+ * then converted to complex numbers if necessary, and returned to the caller.
+ * +read+ also performs some massaging and selection steps (see set() and
+ * select()).
+ *
+ * * +preamble+
+ *
+ *   The preamble is either [_u_,_v_,_time_,_baseline_] or
+ *   <tt></tt>[_u_,_v_,_w_,_time_,_baseline_] if
+ *   <tt>set('preamble','uvw/time/baseline')</tt> was called.  A 5 element
+ *   preamble will populate _w_ with 0.0 if the dataset was written with only a
+ *   4 element preamble.
+ *
+ *   * If a Fixnum is passed in as +preamble+, an NArray that long of type
+ *     NArray::DFLOAT is created and returned with the preamble data.
+ *
+ *   * Otherwise +preamble+ must be passed in as an Array or NArray (of type
+ *     NArray::DFLOAT) of suitable length (i.e.  either 4 or 5).  Its contents
+ *     will be overwritten with new premable data.
+ *
+ * * +data+
+ *
+ *   The complex valued correlation data are returned in +data+.
+ *
+ *   * If a Fixnum or Bignum is passed in as +data+, an NArray that long of
+ *     type NArray::SCOMPLEX is created, populated with +nread+ complex data
+ *     values, and returned.
+ *
+ *   * Otherwise, +data+ must be passed in as an Array or Narray (of type
+ *     NArray::SCOMPLEX).  Its contents will be overwritten with +nread+ data
+ *     values.  Note that an Array will be filled with real and imaginary
+ *     components in consecutive elements and must therefore contain twice as
+ *     many elements as the number of complex valued data points.  In general,
+ *     NArray +data+ will be preferred.
+ *
+ *   * In either of the above cases, the number of complex valued data points
+ *     (either +data+ or <tt>data.length</tt>) must be the same as the number
+ *     of flag values, otherwise an exception will be raised.  Note that the
+ *     length of an Array is twice the number of complex valued data points
+ *     that will fit in it.
+ *
+ * * +flags+
+ *
+ *   The flags indicate whether the corresponding data value has been deemed
+ *   good or bad.  A +1+ means good; a +0+ means bad.
+ *
+ *   * If a Fixnum or Bignum is passed in as +flags+, an NArray that long of
+ *     type NArray::LINT is created, populated with +nread+ flag values, and
+ *     returned.
+ *
+ *   * Otherwise, +flags+ must be passed in as an Array or Narray (of type
+ *     NArray::LINT).  Its contents will be overwritten with +nread+ flag
+ *     values.
+ *
+ *   * In either of the above cases, the number of complex valued data points
+ *     (either +data+ or <tt>data.length</tt>) must be the same as the number
+ *     of flag values, otherwise an exception will be raised.
+ *
+ * * +nread+
+ *
+ *   The number of complex data values and flag values actually read is
+ *   returned in the first element of the return Array.
+ */
+static VALUE uvio_uvread;
+
+/*
+ * Document-method: uvwread
+ *
+ * call-seq: uvwread(data, flags) -> [nread, data, flags]
+ *
+ * <b>NOTE: This method provides lower-level access than the wread() method.
+ * It may disappear in future versions.</b>
+ *
+ * This reads a single wideband visibility record from the data file.  This
+ * should generally be called after uvread(). It performs no scanning before
+ * returning the data. Thus it always returns any wideband data (even if
+ * uvread() has detected end-of-file). Although uvwread() is independent of the
+ * linetype set with set(), it otherwise generally performs the same massaging
+ * steps as uvread() (e.g. data selection, amplitude flagging and planet
+ * scaling).
+ *
+ * The parameters and return values are the same as for uvread(), minus the
+ * +preamble+ parameter and return value.
+ */
+static VALUE uvio_uvwread;
+
+/*
+ * Document-method: getvr
+ *
+ * call-seq: getvr(name) -> value or nil
+ *
+ * Returns the current value of uv variable named +name+ or +nil+ if the named
+ * variable does not (yet) exist.
+ *
+ * Note that complex uv variables are not [yet] supported.
+ */
+static VALUE uvio_getvr;
+
+/*
+ * Document-method: updated?
+ *
+ * call-seq: updated?() -> true or false
+ *
+ * This checks whether any "important variables" has been updated in the
+ * last call to uvread() or scan(). Important variables are those flagged
+ * with the 'u' flag in a call to track().
+ */
+static VALUE uvio_updated;
+
+/*
+ * Document-method: track
+ *
+ * call-seq: track(name, switches)
+ *
+ * Allows the programmer to set switches associated with uv variable +name+.
+ *
+ * There appears to be no way to "untrack" a variable.
+ *
+ * +swicthes+ is a String containing one or both of the following characters:
+ *
+ * <tt>u</tt>::
+ *   Remember if variable +name+ gets updated.  When it gets updated, updated?
+ *   returns true the next time it is called.
+ *
+ * <tt>c</tt>::
+ *   Remember if variable +name+ gets updated.  When it gets updated, cause it
+ *   to be copied during the next call to copyvr.  [copyvr not yet supported.]
+ */
+static VALUE uvio_track;
+
+/*
+ * Document-method: sela
+ *
+ * call-seq: sela(object, datasel, value) -> nil
+ *
+ * Select or reject uv data based on a String.  This specifies the portion of
+ * the data to be selected by calls to uvread.
+ *
+ * +object+ can be either <tt>'source'</tt> or <tt>'purpose'</tt>.
+ *
+ * +datasel+ is either 1 to select or 0 to reject.
+ *
+ * +value+ is a String that will be used as the search critereon.
+ *
+ * See also select().
+ */
+static VALUE uvio_sela;
+
+/*
+ * Document-method: select
+ *
+ * call-seq: select(object, datasel, p1=0.0, p2=0.0) -> nil
+ *
+ * Select or reject uv data based on numeric values.  This specifies the
+ * portion of the data to be selected by calls to uvread.  Generally uvselect
+ * will be called many times, each call giving a different selection or discard
+ * criterion.
+ *
+ * Normally data that are not selected, are not returned.  Exceptions are the
+ * "window" and "amplitude" objects, which cause the corresponding visibilities
+ * to be flagged as bad, but returned anyway.
+ *
+ * +object+ is a String giving the parameter on which a select/discard
+ * criterion is based.  See the list below for permissible values for +object+.
+ *
+ * +datasel+ is either 1 to select or 0 to reject.
+ *
+ * <tt>p1</tt> and <tt>p2</tt>, both Floats, give added numerical parameters.
+ * Generally <tt>p1</tt> and <tt>p2</tt> give a range of parameter values to
+ * select or discard.  Note that the units of the values are consistent with
+ * the units of the underlying uv variables.  These are not necessarily the
+ * most convenient units for the user.
+ *
+ * Here is a list of permissible values for +object+ along with the
+ * applicability of <tt>p1</tt> and </tt>p2</tt> and their units (in
+ * parentheses).  Only applicable parameters are shown; parameters not shown
+ * are ignored.
+ *
+ * <tt>time</tt>::         <tt>p1</tt>=min, <tt>p2</tt>=max (Julian date)
+ * <tt>on</tt>::           <tt>p1</tt>=state
+ * <tt>polarization</tt>:: <tt>p1</tt>=polval (FITS code)
+ * <tt>dazim</tt>::        <tt>p1</tt>=min, <tt>p2</tt>=max (radians?)
+ * <tt>delev</tt>::        <tt>p1</tt>=min, <tt>p2</tt>=max (radians?)
+ * <tt>dra</tt>::          <tt>p1</tt>=min, <tt>p2</tt>=max (radians)
+ * <tt>ddec</tt>::         <tt>p1</tt>=min, <tt>p2</tt>=max (radians)
+ * <tt>ra</tt>::           <tt>p1</tt>=min, <tt>p2</tt>=max (radians)
+ * <tt>dec</tt>::          <tt>p1</tt>=min, <tt>p2</tt>=max (radians)
+ * <tt>ha</tt>::           <tt>p1</tt>=min, <tt>p2</tt>=max (radians?)
+ * <tt>lst</tt>::          <tt>p1</tt>=min, <tt>p2</tt>=max (radians?)
+ * <tt>elevation</tt>::    <tt>p1</tt>=min, <tt>p2</tt>=max (radians?)
+ * <tt>uvrange</tt>::      <tt>p1</tt>=min, <tt>p2</tt>=max (wavelengths)
+ * <tt>uvnrange</tt>::     <tt>p1</tt>=min, <tt>p2</tt>=max (nanoseconds)
+ * <tt>frequency</tt>::    <tt>p1</tt>=min, <tt>p2</tt>=max (GHz)
+ * <tt>pointing</tt>::     <tt>p1</tt>=min, <tt>p2</tt>=max (arcseconds)
+ * <tt>seeing</tt>::       <tt>p1</tt>=min, <tt>p2</tt>=max (???)
+ * <tt>visibility</tt>::   <tt>p1</tt>=min, <tt>p2</tt>=max
+ * <tt>increment</tt>::    <tt>p1</tt>=incr
+ * <tt>shadow</tt>::       <tt>p1</tt>=min, <tt>p2</tt>=max (???)
+ * <tt>bin</tt>::          <tt>p1</tt>=min, <tt>p2</tt>=max
+ * <tt>amplitude</tt>::    <tt>p1</tt>=min, <tt>p2</tt>=max
+ * <tt>window</tt>::       <tt>p1</tt>=win
+ * <tt>antennae</tt>::     <tt>p1</tt>=ant1, <tt>p2</tt>=ant2
+ * <tt>auto</tt>::         <tt></tt>
+ * <tt>or</tt>::           <tt></tt>
+ * <tt>and</tt>::          <tt></tt>
+ * <tt>clear</tt>::        <tt></tt>
+ * 
+ * Notes:
+ *
+ * * For "antennae", a zero indicates "all antennae".
+ *
+ * * For "shadow", a zero indicates use "antdiam" variable.
+ *
+ * * The +clear+ object causes the selection criteria to be reset to its
+ *   default of selected everything.
+ *
+ * * *NB*: +select+ treates +and+ and +or+ as having <b>identical
+ *   precedence</b>, and handles these operators in the order in which they are
+ *   given.  Beware of this lack of precedence.
+ */
+static VALUE uvio_select;
+
+/*
+ * Document-method: flagwr
+ *
+ * call-seq: flagwr(flags) -> nil
+ *
+ * Write uv flags after a read.  This causes the flags associated with
+ * correlation data to be rewritten.  It is typically used by a flagging
+ * program to overwrite old flagging information. It will typically be called
+ * soon after uvread (which is used to get the old flags, and position the
+ * file), thus overwriting the old flags.
+ *
+ * +flags+ is either an Array or NArray (of type NArray::LINT) and will
+ * typically have been returned by uvread and subsequently modified.
+ */
+static VALUE uvio_flagwr;
+
+/*
+ * Document-method: wflagwr
+ *
+ * call-seq: wflagwr(flags) -> nil
+ *
+ * Write wideband flags after a uvwread.  This rewrites the flags associated
+ * with the last call to uvwread.  It will typically be called soon after
+ * uvwread, thus overwriting the old flags.
+ *
+ * +flags+ is either an Array or NArray (of type NArray::LINT) and will
+ * typically have been returned by uvread and subsequently modified.
+ */
+static VALUE uvio_wflagwr;
+
+/*
+ * Document-method: hiswrite
+ *
+ * call-seq: hiswrite(text) -> nil
+ *
+ * Write a line of text to the history file.  This writes a text string to the
+ * history file associated with the underlying dataset.
+ */
+static VALUE uvio_hiswrite;
+
+#if 0
+void Init_Uvio() {
+  VALUE mMiriad = rb_define_module("Miriad");
+  VALUE cUvio = rb_define_class_under(mMiriad,"Uvio",rb_cObject);
+  rb_define_method(cUvio, "initialize", uvio_initialize, 0);
+  rb_define_method(cUvio, "close", uvio_close, 0);
+  rb_define_method(cUvio, "flush", uvio_flush, 0);
+  rb_define_method(cUvio, "uvnext", uvio_uvnext, 0);
+  rb_define_method(cUvio, "rewind", uvio_rewind, 0);
+  rb_define_method(cUvio, "probvr", uvio_probvr, 0);
+  rb_define_method(cUvio, "putvr", uvio_putvr, 0);
+  rb_define_method(cUvio, "scan", uvio_scan, 0);
+  rb_define_method(cUvio, "write", uvio_write, 0);
+  rb_define_method(cUvio, "wwrite", uvio_wwrite, 0);
+  rb_define_method(cUvio, "set", uvio_set, 0);       
+  rb_define_method(cUvio, "uvread", uvio_uvread, 0);
+  rb_define_method(cUvio, "uvwread", uvio_uvwread, 0);
+  rb_define_method(cUvio, "getvr", uvio_getvr, 0);
+  rb_define_method(cUvio, "updated?", uvio_updated, 0);
+  rb_define_method(cUvio, "track", uvio_track, 0);
+  rb_define_method(cUvio, "sela", uvio_sela, 0);
+  rb_define_method(cUvio, "select", uvio_select, 0);
+  rb_define_method(cUvio, "flagwr", uvio_flagwr, 0);
+  rb_define_method(cUvio, "wflagwr", uvio_wflagwr, 0);
+  rb_define_method(cUvio, "hiswrite", uvio_hiswrite, 0);
+}
+#endif // 0
+
+/* vim: set expandtab ts=2 sw=2 smarttab syntax=c cindent fo+=tcroq : */