input
The input file format for fragment and lane
information are as the file example.in shows. Each line
(record) should define a band. The file must be sorted so
that the bands from a lane are together; the file must be
sorted by unique lane identifier (ULI). There must be
three fields (separated by white space -- that is,
seperated by any combination of spaces and tabs). The
first field must be the ULI. The second field is the gel
image identifier (GII). This is only critical for the
first fragment read in for the lane; for subsequent
fragments, the second field must simply be present. ULI
and GII names must not contain any spaces; I strongly
suggest that these fields contain only letters, numbers,
and underscore characters. The third field should contain
the fragment length or molecular weight data for the
fragment. Lines that cannot be parsed into these three
fields will be recored in acm.log. Check acm.log after
each run to see the number of lanes read in and to check
for lines from the input file that could not be parsed.
Lines must be no longer than 199 characters.