forums.silverfrost.com

[simon]

I am trying to read an external formatted input file. The first column of data in the file contains a representation of the date using a combination of numbers '-' and '/' and then follows a set of columns with data in unknown, and possibly variable, format. For example, a line in the file may look something like:

2010-10/12 12.3 45678.90

It is possible that the first field (the date) can change in width in the file.

Unfortunately, because of the '/' in the date, the line does not seem to be easily read in using FMT='*' in a READ statement. Therefore, the approach I have been taking is:
1. read each line in using FMT='(A)'
2. work out how many characters (n) there are in the date
3. BACKSPACE
4. read only the date using FMT='(An)', and ADVANCE='no'
5. read the data in the rest of the line using another READ statement with FMT='*', and ADVANCE='yes'

Assume that I have a subroutine width_date that takes a character input determines how wide the date is, and outputs a format statement, then the code is as follows:

[JohnCampbell]

Simon,

If in step 1, you have read in the record into a character string C, is there a reason that you can't skip step 3 and apply steps 4 and 5 to the character string C.

From your sample code, it apprears that steps 4 and 5 are operating on a single line, which is fully contained in string C.

You could even replace step 2 with "Parse string C and return 2 strings, being the date string and the rest of the data.

I must admit that I go back to when you could only backspace on a binary file. Even then variable length binary files were trouble to backspace, which lead me to write a library for variable length binary record file that was based on a fixed length direct access file.
I'm always cautious of using approaches that were considered inefficient 30 years ago.

John

[simon]

Hi John,

I cannot go back to reading the data from c because I don't know whether c has been long enough to contain all the data.

[JohnCampbell]

There have been a few examples of stream input lately. Could you open the file as:
OPEN (unit=22, file='file_name', access='transparent',
form='unformatted', iostat=iostat)

With this you could write a few access routines.
subroutine get_next_character
subroutine get_next_n_characters
subroutine get_rest_of_line
subroutine get_next_line
subroutine get_start_date

Alternatively, how big could a single record be ? 2k, 20k ..
I don't like data files with excessively long records. ( I don't think formatted I/O does either)
Redefine the record structure to allow for & continuation.

Some hopefully helpful ideas ?

John

[IanLambley]

John,
You are right about formatted I/O not being happy with long lines, but in the past, when lines get quite long I have used a RECL= with a large number which seems as though it might allocate a longer buffer than the normal. Now, I know that is really only for direct access, but it seemed to work. I'n not sure which compiler, it might be VAX-11 Fortran, but I think it worked on the FTN77/FTN95 series of compilers as well. Of course all that was a long time ago when I was younger!
Ian

[davidb]

RECL may be used legitimately with Seqeuntial files in Fortran 95 (Section 9.3.4.5 of draft standard).

With Sequential files, it specifies the maximum record size in characters.

The default maximum record length is processor/compiler dependent.

What is the default maximum record length with FTN95? (Paul?)

This could be being exceeded causing simon's problem with wide files.
_________________
Programmer in: Fortran 77/95/2003/2008, C, C++ (& OpenMP), java, Python, Perl

[simon]

The simple program below can be used to generate the BACKSPACE problem. It seems that the program fails as soon as the length of the line exceeds 2**13. If the file width exceeds 2*13, backspace will only move back 8192 (2**13) spaces in the file.

If I open the file (line 21) with the RECL specified, the BACKSPACE seems unaffected - the program still moves back only 8192 spaces in the file.

[JohnCampbell]

Simon,

I have probably said this before, but why would you require such long text records ?

I'd change:
WRITE (UNIT=iout,FMT='(A,32768I5)') 'B',(r(i),i=1,n)
to:
WRITE (UNIT=iout,FMT='(A,2I5)') 'B',n
WRITE (UNIT=iout,FMT='(A,2I5)') ('B',i,r(i),i=1,n)
or:
WRITE (UNIT=iout,FMT='(A,2I5)') 'B',n
WRITE (UNIT=iout,FMT='(1x,10I5)') (r(i),i=1,n)

When you go to read this, there would be no need for backspace and the overhead for file size or I/O time is not significant.
Provide a file data structure that is easy to manage. I work with survey points files with up to 100 million points and a simple text format that is easy to review saves a lot of time.

There are alternatives to notepad for large files. I even have my own line editor that displays the first 1gb of a text file.
You might claim to have no control of the input file format, but if I received a file as you show, the first thing I would do (have actually done) is write a conversion to a more manageable format and archive the originals. Puting in a few extra <CR><LF> won't cost you much.

John

[simon]

Thanks John,

The basic principle I am applying here is that the software I am trying to create should be able to read somebody else's file without me imposing limits on the user. I don't want to have to say to the user "sorry, if your file is wider than 8192 characters then you will have to reformat it somehow." The point is not so much that I want to be able to read or create wide files, the point is IF one has a wide file, how do you read it?

I agree that here is a strong case for using a more sensible file format. But it would be helpful to at least get an error message from BACKSPACE if it has not worked. Anyway, perhaps Paul could include in the maunal somewhere a comment that there is a limit of 8192.

One bonus is that FTN95 can at least read wider files than NAGWare, for example. NAGWare baulks beyond 1024, but it complains at the stage of trying to read the line whereas FTN95 keeps going and you don't immediately realise that there has been an error.

[JohnCampbell]

Simon,

You could look at FORM="UNFORMATTED",ACCESS='TRANSPARENT"
I have found this to provide a good solution, as you can manage what ever character buffer you require. It is easy to write subroutines to read or write characters and built up strings and records.
I am not sure if you can use an internal formatted read on a very long character, such as
character buffer*20000

I read the next record into a large character array (1 character at a time) and do my own parsing for numbers etc. It works very well.
The line editor I mentioned has the following declarations which provide for large records and files:

[PaulLaidler]

At a quick glance the limit looks like 32K.