Re: FCS file headers
MURPHY@A.CFR.CMU.EDU
Tue, 15 Jun 1993 15:57:43 -0400 (EDT)

* Messages sorted by: [ date ][ thread ][ subject ][ author ]
* Next message: Nick Viner: "FACSCAN -> PC"
* Previous message: MURPHY@A.CFR.CMU.EDU: "Re: FCS file headers"
* Maybe in reply to: Steve Kelley: "FCS file headers"

In response to a question from Alice Givan, there are three ways to
get
listings of keyword values for FCS files on VAX systems.

1. Use the DR command in DISP4 or DISP2D. This will give values for
some of the common FCS keywords.

2. Use the FCSDMP program to get a listing of all of the keywords
in one or more FCS files. If more than one file is specified
(wildcards and ranges allowed), only the DIFFERENCES between the
first file and the later files will be listed.

3. Use the FCSTAB program to generate a table or listing of specific
keyword values for each file in an input list, one line per file.
FCSTAB calculates a number of additional keywords, such as means
and s.d.'s for each parameter.

VMS versions of FCSDMP and FCSTAB can be obtained by anonymous FTP
from
a.cfr.cmu.edu. They are in subdirectories [.VMS.FCSDMP] and
[.VMS.FCSTAB]. Help files suitable for insertion in VMS help libraries
are included. Source files are in [.SOURCE] subdirectories (note that
only .OBJ files are included for some utility routines).

For users generating files on systems other than Consort/VAX, these
files may be analyzed using FCSDMP or FCSTAB as long as they adhere
to the FCS 1.0 or 2.0 standards and the FCS file identifier contains
the string "FCS1.0". FCS files created on other systems often have
different strings (such as "FCS 1.0") as the FCS file identifier.
The program FCSFIX (in [.VMS.FCSFIX]) can be used to modify these
files so that they can be read by FCSDMP and FCSTAB, as well as
Consort/VAX programs. We have successfully analyzed many ELITE
files with FCSTAB after running them through FCSFIX.

Comments welcome.

Bob Murphy

* Next message: Nick Viner: "FACSCAN -> PC"
* Previous message: MURPHY@A.CFR.CMU.EDU: "Re: FCS file headers"
* Maybe in reply to: Steve Kelley: "FCS file headers"