07-14-2011
Fortran runtime error: Insufficient data descriptors in format after reversion
Hello,
I have some Fortran code that is providing the following error:
At line 1165 of lapc_shells_2.f
Fortran runtime error: Insufficient data descriptors in format after reversion
Here are the lines just above and including 1165:
WRITE (*,"('ATTEMPTING TO READ PLATE BOUNDARIES')")
READ (*,"(A)") TITLE5
OPEN (UNIT = IUNITM, FILE = TITLE5)
WRITE (IUNITT,2) IUNITM <---------------1165
It's reading a file that starts out like this:
AF-AN Mueller et al. [1987]
-4.37900E-01,-5.48518E+01
-3.88257E-02,-5.46772E+01
+4.43182E-01,-5.44512E+01
+9.64534E-01,-5.48322E+01
+1.69481E+00,-5.43990E+01
+2.35975E+00,-5.40374E+01
+3.02542E+00,-5.36507E+01
+3.36894E+00,-5.38341E+01
+3.95638E+00,-5.41267E+01
+4.41458E+00,-5.44303E+01
+4.82661E+00,-5.41616E+01
+5.08372E+00,-5.43093E+01
Any idea why this error is occurring?
Thanks
---------- Post updated at 03:51 PM ---------- Previous update was at 02:18 PM ----------
I forgot an important part to the above post.
The 2 refers to this line:
2 FORMAT (/' ATTEMPTING TO READ PLATE OUTLINES FROM UNIT', /)
Got it! For future reference the answer is to add more information at the end of line 2.
2 FORMAT (/' ATTEMPTING TO READ PLATE OUTLINES FROM UNIT', I3/)
Last edited by jm4smtddd; 07-14-2011 at 05:06 PM..
9 More Discussions You Might Find Interesting
1. Solaris
My interprise use a UNIX mainform for a instrumentation process control. The control use the FOXBORO INVENSYS system and they donīt gonna solve the problem the run time error. The run time error happen without logic explication. When everything itīs run perfectely and happenly appears the run time... (1 Reply)
Discussion started by: marpin
1 Replies
2. UNIX for Dummies Questions & Answers
My system did stay appears the error Run Time Library Error. What itīs? When the error appear, iīve to reboot my system and lost all I did. Is there the UNIX System problem? Please. I need help!!! (4 Replies)
Discussion started by: marpin
4 Replies
3. Solaris
First I would like to thank this forum for assisting me in setting up my 1st sunbox.
Could not have done it if it had not been for you guys and google :D
I have mirrored my box and have SUCCESSFULLY tested booting from the rootdisk and rootmirror successfully.
I am now looking at configuring... (2 Replies)
Discussion started by: mr_manny
2 Replies
4. UNIX for Dummies Questions & Answers
Hi,
Could anyone help me in changing a tabular format output to comma seperated file pls in K-sh. Its very urgent.
E.g : username empid
------------------------
sri 123
to
username,empid
sri,123
Thanks,
Hema:confused: (2 Replies)
Discussion started by: Hemamalini
2 Replies
5. Programming
Hi,
I am new to this forum and do not know whether this is the appropriate place to post this question. Anyway am trying my luck.
I have a fortran program swanhcat.ftn, which is part of a wave modelling system. There is also a file hcat.nml which is required to run this program. The program's... (9 Replies)
Discussion started by: sandhyakg
9 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I am using svnnotify (which is available on net) script to send svn commit notification.
Everything was working fine up to yesterday but from yesterday i started seeing error.
29CD01FCE44 7228 Thu Apr 5 11:11:51 apache@vm0001.host.com
(host mail.mailserver.com said: 452... (6 Replies)
Discussion started by: vishal_vsh1
6 Replies
7. Shell Programming and Scripting
I'm trying to crudely hack my way through some data processing.
I have file.txt with around 17,000 lines like this:
ACYPI002690-PA.aa.afa.afa.trim_phyml_tree_fullnames_fullhomolog.txt 3 72 71
ACYPI002690-PA.aa.afa.afa.trim_phyml_tree_fullnames_fullhomolog.txt 97 111 71... (1 Reply)
Discussion started by: pathunkathunk
1 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I'm doing aproximation of derivative called five-point stencil. For every value of x, in interval , in step... (0 Replies)
Discussion started by: antonija
0 Replies
9. Programming
I have a Fortran program and I am writing out to logical unit 7. The program is reading from a text file and writing to the new file formatted. It gets through the read and writes some to the file but then stops with the following error:
1525-013 The sequential WRITE statement cannot be... (5 Replies)
Discussion started by: KathyB148
5 Replies
LEARN ABOUT DEBIAN
mpi_alloc_mem
MPI_Alloc_mem(3) MPI MPI_Alloc_mem(3)
NAME
MPI_Alloc_mem - Allocate memory for message passing and RMA
SYNOPSIS
int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr)
INPUT PARAMETERS
size - size of memory segment in bytes (nonnegative integer)
info - info argument (handle)
OUTPUT PARAMETER
baseptr
- pointer to beginning of memory segment allocated
NOTES
Using this routine from Fortran requires that the Fortran compiler accept a common pointer extension. See Section 4.11 (Memory Allocation)
in the MPI-2 standard for more information and examples.
Also note that while baseptr is a void * type, this is simply to allow easy use of any pointer object for this parameter. In fact, this
argument is really a void ** type, that is, a pointer to a pointer.
THREAD AND INTERRUPT SAFETY
This routine is thread-safe. This means that this routine may be safely used by multiple threads without the need for any user-provided
thread locks. However, the routine is not interrupt safe. Typically, this is due to the use of memory allocation routines such as malloc
or other non-MPICH runtime routines that are themselves not interrupt-safe.
NOTES FOR FORTRAN
All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have an additional argument ierr at the end of the argument list. ierr
is an integer and has the same meaning as the return value of the routine in C. In Fortran, MPI routines are subroutines, and are invoked
with the call statement.
All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in Fortran.
ERRORS
All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error value; C routines as the value of the function and Fortran routines in
the last argument. Before the value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI
job. The error handler may be changed with MPI_Comm_set_errhandler (for communicators), MPI_File_set_errhandler (for files), and
MPI_Win_set_errhandler (for RMA windows). The MPI-1 routine MPI_Errhandler_set may be used but its use is deprecated. The predefined
error handler MPI_ERRORS_RETURN may be used to cause error values to be returned. Note that MPI does not guarentee that an MPI program can
continue past an error; however, MPI implementations will attempt to continue whenever possible.
MPI_SUCCESS
- No error; MPI routine completed successfully.
MPI_ERR_INFO
- Invalid Info
MPI_ERR_ARG
- Invalid argument. Some argument is invalid and is not identified by a specific error class (e.g., MPI_ERR_RANK ).
MPI_ERR_NO_MEM
- Insufficient memory available for allocation by MPI_Alloc_mem
LOCATION
alloc_mem.c
5/20/2010 MPI_Alloc_mem(3)