Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

segmentation fault when writing restart file #1158

Closed
yfang-repo opened this issue Feb 9, 2024 · 4 comments
Closed

segmentation fault when writing restart file #1158

yfang-repo opened this issue Feb 9, 2024 · 4 comments

Comments

@yfang-repo
Copy link
Contributor

yfang-repo commented Feb 9, 2024

FATES-SP:
I see negative lb1/ub1 values
when adding print statements here for a large size problem: (

this%r81d(:) = flushval
)

It can not be reproduced with a small size problem. Can anyone point to me where the lb and ub set? Thanks!

@yfang-repo
Copy link
Contributor Author

yfang-repo commented Feb 9, 2024

It is still related to #986

@ckoven
Copy link
Contributor

ckoven commented Feb 9, 2024

@yfang-repo seems like it is trying to make too big of an array in the cohort dimension? In SP mode, the size of that vector is determined by num_swb here I think?

fates_maxElementsPerPatch = num_swb

Is the product of the number of gridcells and num_swb too big for the integer type that is being used?

@yfang-repo
Copy link
Contributor Author

@ckoven I suspect fates_maxElementsPerSite is too big. Still doing some testing.

@yfang-repo
Copy link
Contributor Author

I was using an older version. Reducing fates_maxElementsPerPatch helps.

@github-project-automation github-project-automation bot moved this from ❕Todo to ✔ Done in FATES issue board Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants