This file is generated even when IDETL = 0 (zero). This is not ideal for multiple simulations (e.g. HiPerGator).
Currently @fabiooliveira72 is looking for options to edit/modify the code:
YCA_Runinit.f90
Line: 261-266
Code:
CALL Getlun('READS.OUT',fnumrea)
! Close and re-open Reads file
CLOSE (FNUMREA, STATUS = 'DELETE')
OPEN (UNIT = FNUMREA,FILE = 'READS.OUT', STATUS = 'NEW', ACTION = 'READWRITE')
WRITE(fnumrea,*)' '
WRITE(fnumrea,*)' File closed and re-opened to avoid generating huge file’
Description: This code is just getting the unit number (FNUMREA), after that the file is deleted if exists and a new one is reopened. Just one message is written in this subroutine nothing else. Similar previous file code.
Note that, first it is just creating the READS.OUT file and then the subroutines below write the outputs in the file:
CSREADS.for
Line: There are 138 lines using READS.OUT file.
The following subroutines are used as utilities for the CSCER,CSCAS,CSCRP and CSYCA models.
This file is generated even when IDETL = 0 (zero). This is not ideal for multiple simulations (e.g. HiPerGator). Currently @fabiooliveira72 is looking for options to edit/modify the code:
YCA_Runinit.f90 Line: 261-266 Code:
Description: This code is just getting the unit number (FNUMREA), after that the file is deleted if exists and a new one is reopened. Just one message is written in this subroutine nothing else. Similar previous file code.
Note that, first it is just creating the READS.OUT file and then the subroutines below write the outputs in the file:
CSREADS.for Line: There are 138 lines using READS.OUT file.
The following subroutines are used as utilities for the CSCER,CSCAS,CSCRP and CSYCA models.
Subroutine: XREADT Code:
Description: This pieces of code open the READS.OUT and use as debbuging file writing some variables values.
Subroutine: AREADT Code:
Description: This pieces of code open the READS.OUT and use as debbuging file writing some variables values.
Subroutine: CUREADT Code:
…
…
Description: This pieces of code open the READS.OUT and use as debbuging. The part that writes in READS.OUT is commented.
Subroutine: CUREADT Code:
Description: This pieces of code open the READS.OUT and use as debbuging file. This subroutine never writes in the output file.
Subroutine: SPREADT Code:
Description: This pieces of code open the READS.OUT and use as debbuging file writing some variables values.
Subroutine: SLREADT Code:
Description: This pieces of code open the READS.OUT and use as debbuging file writing some variables values.
Subroutine: SMREADT Code:
Description: This pieces of code open the READS.OUT and use as debbuging. The part that writes in READS.OUT is commented.