... The routine processing of STIS data in the calibration ``pipeline" requires an interrelated set of software tasks and databases developed and maintained by many groups at STScI. We present the systems-level design of this calibration pipeline from the perspective of the STIS instrument group at STScI. We describe the multiple interfaces to the pipeline processes that the STIS group works across in an effort to provide for the routine calibration of STIS data. ... For example, the STIS group: . ...

... Package . ... ImageJ bit blitting classes must implement this interface. ... This class processes binary images. ... This class does bit blitting of byte images. ... 8-bit image statistics, including histogram. ... RGB image statistics, including histogram. ... This class does bit blitting of 32-bit floating-point images. ... 32-bit (float) image statistics, including histogram. ... Statistics, including the histogram, of an image or selection. ... This class does bit blitting of 16-bit images. ...

... casa::LineCollapser< T, U > . ... Can the process function in the derived class handle a null mask? If not, LatticeApply ensures that it'll always pass a filled mask vector, even if the lattice does not have a mask (in that case that mask contains all True values). virtual void . process (U &result, Bool &resultMask, const Vector < T > &line, const Vector < Bool > &mask, const IPosition &pos)=0 . ... The class is Doubly templated. ... virtual casa::LineCollapser < T, U >::~ LineCollapser . ...

... ESO's Data Management Operations Division and California Institute of Technology, CACR are cooperating to investigate the appropriateness and means of applying Beowulf-class computing technology to the computing requirements of the ESO Very Large Telescope Data Flow System. ... The one year program was to assess the usefullness of Beowulf technology to the data processing needs of the European Southern Observatory for the Very Large Telescope (VLT) project. ... Who is Beowulf? ...

rcslib (version 01/28/04) . ... RCS interface module. ... files and (possibly) corresponding work files. ... Constructor. checkfile (self, name_rev) . ... Raise an exception if there is no corresponding version file. checkin (self, name_rev, message =None , otherflags ='' ) . ... Return a list of all version files matching optional PATTERN. lock (self, name_rev) . Set an rcs lock on NAME_REV. log (self, name_rev, otherflags ='' ) . ... The argument can be a work file name or a version file name. ...

Next: Introduction Up: Linux System Administrators' Guide Previous: Linux System Administrators' Guide . Overview of a Linux System . ... Logins from terminals . ... The filesystem layout . ... The root filesystem . ... The /usr filesystem . ... Using Disks and Other Storage Media . ... Filesystems . ... Disks without filesystems . Allocating disk space . ... Adding more disk space for Linux . ... Creating a swap space . ... Sharing swap spaces with other operating systems . ... Backups . ...

In Actor Prolog a resident is a special mechanism that helps processes to inspect state of other processes. A resident observes the state of a specified (target) process and if the state of the process changes (for instance, after message handling) it proves a specified predicate of the process. ... Work of the resident. ... Any change of the list of target processes or arguments of resident function results in activation of the resident and repeated collection of information in the target worlds. ...

... Classes . ... gTime Class Reference . This class implements time calculations. ... gTime (double ai_jDays=0) . ... gTime (const gTime &timeSrc) . ... Set the time value of the time object to the julian day of year, day. ... operator= (const gTime &timeSrc) . ... Returns the time GMT value in Julian days. ... Returns the time_t value of the gTime Object. ... Returns a gTime object setted with the actual machine time. ... gTime Object assigned with real machine time. double gTime::getGmtTm . ...

... Forum: A tour of the Linux VFS . ... Inodes represent entities on disks: there's one (and only one) for each file, directory, symlink, device and FIFO on the filesystem. When a user process does an open() syscall, it does a couple of things: - it looks up the inode for the pathname - it puts the inode into the inode cache - it allocates a new file structure - it allocates a filedescriptor slot, and points it it at the file structure The number of the file descriptor slot is what is returned. ...