You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
max_hdims appears to be used before defined. The only usage is
! Determine the maximum number of dimensions
do field_index =1, size(this%field_list)
max_mdims =max(max_mdims, size(this%field_list(field_index)%dimensions()))
end do
! Allocate dimindex to the maximum possible dimensions (plus 1 for time)
allocate(dimindex(max_hdims + max_mdims +1), stat=ierr)
On the first loop iteration max_mdims is undefined but used in the max() statement.
I think setting max_mdims = 0 above the loop should fix the issue? Not sure if this is related to #302 as the variable name mentioned there (maxmdims) is suspiciously similar to the problematic one here (max_mdims), but this appears to be just a local variable in the subroutine.
The text was updated successfully, but these errors were encountered:
… with history output (#333)
Tag name (required for release branches):
Originator(s): @jimmielin
Description (include the issue title, and the keyword ['closes',
'fixes', 'resolves'] followed by the issue number):
- Fixes#332 (`max_mdims` used before defined)
- Fixes#331 (unassociated `of%file_desc` in `cam_register_open_file`
leading to crash with >2 history files)
Describe any changes made to build system: N/A
Describe any changes made to the namelist: N/A
List any changes to the defaults for the input datasets (e.g. boundary
datasets): N/A
List all files eliminated and why: N/A
List all files added and what they do: N/A
List all existing files that have been modified, and describe the
changes:
(Helpful git command: `git diff --name-status
development...<your_branch_name>`)
```
Fixes#331
M src/history/cam_hist_file.F90
Fixes#332
M src/utils/cam_abortutils.F90
```
If there are new failures (compared to the
`test/existing-test-failures.txt` file),
have them OK'd by the gatekeeper, note them here, and add them to the
file.
If there are baseline differences, include the test and the reason for
the
diff. What is the nature of the change? Roundoff?
derecho/intel/aux_sima:
derecho/gnu/aux_sima:
If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced:
CAM-SIMA date used for the baseline comparison tests if different than
latest:
What happened?
Run CAM-SIMA with
DEBUG=true
The model fails with a run-time check failure:
What are the steps to reproduce the bug?
FKESSLER
)./xmlchange DEBUG=true
./case.setup
and buildWhat CAM-SIMA hash were you using?
f999707
What machine were you running CAM-SIMA on?
CISL machine (e.g. cheyenne)
What compiler were you using?
Intel
Path to a case directory, if applicable
No response
Will you be addressing this bug yourself?
Any Software Engineer can do this
Extra info
max_hdims
appears to be used before defined. The only usage isOn the first loop iteration
max_mdims
is undefined but used in themax()
statement.I think setting
max_mdims = 0
above the loop should fix the issue? Not sure if this is related to #302 as the variable name mentioned there (maxmdims
) is suspiciously similar to the problematic one here (max_mdims
), but this appears to be just a local variable in the subroutine.The text was updated successfully, but these errors were encountered: