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

Optimization of the construction of SFC #1227

Merged
merged 1 commit into from
Aug 4, 2020

Conversation

WeiqunZhang
Copy link
Member

Summary

The Morton numbers are explicitly computed and stored in SFCTokens. This
speeds up the sorting in making space filling curve significantly.

Checklist

The proposed changes:

  • fix a bug or incorrect behavior in AMReX
  • add new capabilities to AMReX
  • changes answers in the test suite to more than roundoff level
  • are likely to significantly affect the results of downstream AMReX users
  • are described in the proposed changes to the AMReX documentation, if appropriate

@WeiqunZhang WeiqunZhang requested a review from atmyers August 4, 2020 16:48
@WeiqunZhang WeiqunZhang force-pushed the morton branch 4 times, most recently from 4908ede to 622f63b Compare August 4, 2020 20:17
The Morton numbers are explicitly constructed and stored in SFCTokens.  This
speeds up the sorting in making space filling curve significantly.
@WeiqunZhang
Copy link
Member Author

I wrote a test code to compare the old and new approaches by sorting a vector of 1e8 tokens. The results agree with each other. https://github.com/WeiqunZhang/random/tree/main/sfc

@WeiqunZhang WeiqunZhang marked this pull request as ready for review August 4, 2020 21:45
@WeiqunZhang WeiqunZhang merged commit e2dac9c into AMReX-Codes:development Aug 4, 2020
@WeiqunZhang WeiqunZhang deleted the morton branch August 4, 2020 23:13
dwillcox pushed a commit to dwillcox/amrex that referenced this pull request Oct 3, 2020
## Summary

The Morton numbers are explicitly computed and stored in SFCTokens.  This
speeds up the sorting in making space filling curve significantly.

## Checklist

The proposed changes:
- [ ] fix a bug or incorrect behavior in AMReX
- [ ] add new capabilities to AMReX
- [ ] changes answers in the test suite to more than roundoff level
- [ ] are likely to significantly affect the results of downstream AMReX users
- [ ] are described in the proposed changes to the AMReX documentation, if appropriate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants