section d of routines in global.i

all functions - d

data_align


    data_align, file, alignment  


in binary file FILE, align new variables to begin at a byte address  
which is a multiple of ALIGNMENT.  (This affects placement of data  
declared using save and add_variable.  For add_variable, data_align  
has an effect only if the address is not specified.)  If ALIGNMENT  
is <=0, new variables will be aligned as they would be if they were  
data structure members.  The default value is 0.  
Builtin function, documented at i0/std.i   line 3402

SEE ALSO: erf, erfc

day2000


    day2000  


  
     Interpreted function, defined at i/kepler.i   line 421

dbauto


    dbauto  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dbcont


    dbcont  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dbdis


    dbdis  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dbexit


    Debug mode.  


Yorick errors fall into two general categories: Syntax errors discovered  
during parsing, and runtime errors discovered when a Yorick program is  
actually running.  When a runtime error occurs, Yorick offers the  
choice of entering "debug mode", which you can do by typing the   
key immediately after the error occurs.  Typing a non-blank line exits  
debug mode automatically by default.  In debug mode, the Yorick prompt  
becomes "dbug>" instead of the usual ">".  When you see this prompt,  
Yorick has halted "in the middle of" the function in which the error  
occurred, and you can print, plot, modify, or save the local variables  
in that function by means of ordinary Yorick commands.  Debug mode is  
recursive; that is, you can debug an error which occurred during  
debugging to any number of levels.  
You can exit from debug mode in several ways:  
   dbexit            -- exit current debug level, discarding all  
                        active functions and their local variables  
   dbexit, 0         -- exit all debug levels  
   dbexit, n         -- exit (at most) N debug levels  
   dbcont            -- continue execution of the current function  
      Continuing is useful if you have managed to repair the  
      problem which caused the error.  The expression in which the  
      error occurred will be evaluated a second time, so beware of  
      side effects.  
   dbret, value      -- continue execution by returning VALUE (which  
                        may be nil or omitted) to the caller of the  
                        function in which the error occurred.  
      This is useful if the function in which the error occurred is  
      hopelessly confounded, but you know the value it should return.  
Yorick does not allow "single stepping" directly, although you can  
execute the statements in a function by copying them, then tell  
Yorick to skip those statements you have executed "by hand".  There  
are two functions for skipping execution:  
   dbskip            -- skip the next logical line (This will be only  
                        a portion of a source line if several statements  
                        are stacked on the source line.)  
   dbskip, n         -- skip next N (positive or negative) logical lines  
   dbup              -- discard the current function, so that you are  
                        debugging its caller -- there is no way to go  
                        back "down", so be careful  
There are two functions which print information (like other print  
functions, if called as functions instead of subroutines, their  
result is returned as a string array with one line per string):  
   dbinfo            -- returns current function and source line  
   dbdis             -- returns disassembled virtual machine code  
                        for the next line (use the disassemble function  
                        to get the entire function)  
      This allows you to see exactly where in a line the error occurred.  
Finally,  
   dbauto            -- toggles whether debug mode will be entered  
                        automatically when a runtime error occurs  
   dbauto, 1         -- enter debug mode automatically after an error  
   dbauto, 0         -- type  after error to enter debug mode  
  Builtin function, documented at i0/std.i   line 3760

dbinfo


    dbinfo  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dbret


    dbret  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dbskip


    dbskip  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dbup


    dbup  


Builtin function, documented at i0/std.i   line 3760

SEE dbexit

dec_primitives


    dec_primitives, file  


sets FILE primitive data types to be native to DEC (MIPS) workstations.  
Interpreted function, defined at i0/std.i   line 2881

default_gate


    default_gate(times)  


initial value of drat_gate.  Refer to the source code  
to learn how to write your own gate function, making proper use  
of drat_start and drat_stop options in addition to the input times.  
Interpreted function, defined at i0/drat.i   line 774

SEE ALSO: streak

default_ocompute


    default_ocompute(f, time)  


initial value of drat_ocompute.  Extracts drat_akap and drat_ekap  
from file F, possibly using the subset drat_glist.  TIME is unused.  
Interpreted function, defined at i0/drat.i   line 719

digit2


    digit2(y0,x0, y,x)  


  -or- digit2(y0,x0, y,x,reg)  
return the index of the zone of the point or points (X0,Y0)  
in the quadrilateral mesh (X,Y) with the optional region  
array REG.  The result has the same dimensions as the input  
X0 and Y0 arrays.  The result is <=0 at points outside the mesh.  
By default, the zone index is an index into an (M-1)-by-(N-1)  
array, if X and Y are M-by-N.  However, if the keyword pt= is  
non-nil and non-zero, the return value is the index into an  
M-by-N array in which the first row and column are non-existent  
(like the optional REG array).  
Interpreted function, defined at i/digit2.i   line 10

SEE ALSO: digitize, interp2, mesh_loc, plm

digitize


    digitize(x, bins)  


returns an array of longs with dimsof(X), and values i such that  
BINS(i-1) <= X < BINS(i) if BINS is monotonically increasing, or  
BINS(i-1) > X >= BINS(i) if BINS is monotonically decreasing.  
Beyond the bounds of BINS, returns either i=1 or i=numberof(BINS)+1  
as appropriate.  
Builtin function, documented at i0/std.i   line 1125

SEE ALSO: histogram, interp, integ, sort, where, where2

dimsof


    dimsof(object)  
 or dimsof(object1, object2, ...)  


returns a vector of integers describing the dimensions of OBJECT.  
The format of the vector is [number of dims, length1, length2, ...].  
The orgsof function returns the origin of each dimension (normally 1).  
If more than one argument is given, dimsof returns the dimension  
list of the result of binary operations between all the objects,  
or nil if the objects are not conformable.  
Builtin function, documented at i0/std.i   line 375

SEE ALSO: typeof, structof, numberof, sizeof, orgsof

dirt_rays


    dirt_rays(rays)  


returns 3-element (x,y,theta) representation of RAYS.  
The first dimension of RAYS may be length 3, 5, or 6 to represent  
the ray(s) in TDG/DIRT coordinates (x,y,theta), "best" coordinates  
(x,y,z,theta,phi), or internal coordinates (cos,sin,y,z,x,r),  
respectively.  The first dimension of the result always has length 3.  
The TDG/DIRT coordinate system is based on the coordinates (x,y)  
in a plane normal to the ray.  Unfortunately, the old TDG and DIRT  
codes used an angle theta which has the opposite sense from the  
"best" and internal coordinates.  Therefore, conversion from  
TDG/DIRT coordinates to internal coordinates will reverse the  
sign of theta.  Conversion from TDG/DIRT coordinates to "best"  
coordinates always results in positive theta, but the angle phi  
will be pi for positive input theta.  
The slimits parameter -- used to specify the points along  
a ray where the transport integration starts and stops -- is  
measured from the point of closest approach of the ray described  
by (x,y,theta) to the origin x=y=z=0.  Therefore, slimits is  
independent of the TDG/DIRT ray coordinate representation.  
Interpreted function, defined at i/rays.i   line 97

SEE ALSO: form_rays, best_rays, internal_rays, get_s0, picture_rays

disassemble


    disassemble(function)  
 or disassemble, function  


Disassembles the specified function.  If called as a function, the  
result is returned as a vector of strings; if called as a subroutine,  
the disassembly is printed at the terminal.  If the function is nil,  
the current *main* program is disassembled -- you must include the  
call to disassemble in the main program, of course, NOT on its own  
line as a separate main program.  
Builtin function, documented at i0/std.i   line 267

display


    display

display


    display

display_pl3


    display_pl3  


  
     Interpreted function, defined at i/demo2.i   line 144

display_plf


    display_plf  


  
     Interpreted function, defined at i/demo2.i   line 108

display_plm


    display_plm  


  
     Interpreted function, defined at i/demo2.i   line 130

distill_interp


    distill_interp  


  
     Interpreted function, defined at i/ylmdec.i   line 350

dn_


    dn_(ell_am(u,m))  


return the Jacobian elliptic function dn(u|m).  The external  
variable ell_m must be set properly before calling dn_.  
Interpreted function, defined at i/elliptic.i   line 166