krc not running

From krc
(Difference between revisions)
Jump to: navigation, search
(Created page with 'krc usually runs OK. Using the provided input file, krc does not run (see what is printed to the screen) and does not write even an empty *.tdb file or moving past the first set …')
 
 
(3 intermediate revisions by one user not shown)
Line 13: Line 13:
 
  IG=          1  RBUF=1 3 61.0  'Inertia, dust'                                                   
 
  IG=          1  RBUF=1 3 61.0  'Inertia, dust'                                                   
 
  IG=          8  RBUF=8 0 0 '/work/users/rfergason/2_layer_AGU/1_layer_dust.tdb
 
  IG=          8  RBUF=8 0 0 '/work/users/rfergason/2_layer_AGU/1_layer_dust.tdb
 +
 +
[[Media:2layer_broken.inp | Broken Input File]]<br />
 +
[[Media:krc_broken_1 | Empty Output File]]<br />
 +
 +
Solution:
 +
You need a single trailing quote on the output file names (several places).
 +
A general assurance is to put a  single  /  after the new values on each line.
 +
as this tells FORTRAN to look no further.
 +
For example if your second change card was >  1 3 61.0  / < then

Latest revision as of 14:04, 18 December 2013

krc usually runs OK. Using the provided input file, krc does not run (see what is printed to the screen) and does not write even an empty *.tdb file or moving past the first set of change cards.

Printed to the screen:

ast{658}> ./krc
This is KRCv2.2.4
?* Input file name or / for default =krc.inp                                                      
2layer.inp
 ?* Print file name or / for default =krc.prt                                                     
/
TCARD:notice N4,MAXN4=          13          37
IG=           1   RBUF=1 1 0.30  'Albedo, dust'                                                   
IG=           1   RBUF=1 3 61.0  'Inertia, dust'                                                  
IG=           8   RBUF=8 0 0 '/work/users/rfergason/2_layer_AGU/1_layer_dust.tdb

Broken Input File
Empty Output File

Solution: You need a single trailing quote on the output file names (several places). A general assurance is to put a single / after the new values on each line. as this tells FORTRAN to look no further. For example if your second change card was > 1 3 61.0 / < then

Personal tools