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

Replace mutable structs using Adapt #2050

Closed
wants to merge 3 commits into from

Conversation

huiyuxie
Copy link
Member

@huiyuxie huiyuxie commented Aug 26, 2024

Mutable structs cannot be compiled to bits type on GPU. Using Adapt to translate the mutable structs to an immutable struct can be a good way to address this.

@huiyuxie huiyuxie self-assigned this Aug 26, 2024
Copy link
Contributor

Review checklist

This checklist is meant to assist creators of PRs (to let them know what reviewers will typically look for) and reviewers (to guide them in a structured review process). Items do not need to be checked explicitly for a PR to be eligible for merging.

Purpose and scope

  • The PR has a single goal that is clear from the PR title and/or description.
  • All code changes represent a single set of modifications that logically belong together.
  • No more than 500 lines of code are changed or there is no obvious way to split the PR into multiple PRs.

Code quality

  • The code can be understood easily.
  • Newly introduced names for variables etc. are self-descriptive and consistent with existing naming conventions.
  • There are no redundancies that can be removed by simple modularization/refactoring.
  • There are no leftover debug statements or commented code sections.
  • The code adheres to our conventions and style guide, and to the Julia guidelines.

Documentation

  • New functions and types are documented with a docstring or top-level comment.
  • Relevant publications are referenced in docstrings (see example for formatting).
  • Inline comments are used to document longer or unusual code sections.
  • Comments describe intent ("why?") and not just functionality ("what?").
  • If the PR introduces a significant change or new feature, it is documented in NEWS.md with its PR number.

Testing

  • The PR passes all tests.
  • New or modified lines of code are covered by tests.
  • New or modified tests run in less then 10 seconds.

Performance

  • There are no type instabilities or memory allocations in performance-critical parts.
  • If the PR intent is to improve performance, before/after time measurements are posted in the PR.

Verification

  • The correctness of the code was verified using appropriate tests.
  • If new equations/methods are added, a convergence test has been run and the results
    are posted in the PR.

Created with ❤️ by the Trixi.jl community.

@huiyuxie huiyuxie requested a review from ranocha August 26, 2024 06:03
@huiyuxie huiyuxie marked this pull request as draft August 26, 2024 06:15
src/callbacks_step/glm_speed.jl Outdated Show resolved Hide resolved
@huiyuxie huiyuxie requested a review from ranocha August 26, 2024 21:54
@huiyuxie huiyuxie added the refactoring Refactoring code without functional changes label Aug 26, 2024
@huiyuxie
Copy link
Member Author

Looks like it is still causing a bunch of errors😢

@vchuravy
Copy link
Member

An alternative would be to use Adapt to translate the mutable structs to an immutable struct that works on the GPU.
Might require introducing a new abstract type in the type hierarchy so that the dispatch still works out.

@huiyuxie
Copy link
Member Author

Thanks @vchuravy let me have a try :)

@huiyuxie
Copy link
Member Author

Not sure whether doing this on my repo or here would be better - let me try both ways and compare.

@huiyuxie huiyuxie reopened this Aug 27, 2024
Copy link

codecov bot commented Aug 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.32%. Comparing base (f9c9107) to head (7594e4e).
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2050   +/-   ##
=======================================
  Coverage   96.32%   96.32%           
=======================================
  Files         470      470           
  Lines       37447    37447           
=======================================
  Hits        36070    36070           
  Misses       1377     1377           
Flag Coverage Δ
unittests 96.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ranocha
Copy link
Member

ranocha commented Aug 28, 2024

Not sure whether doing this on my repo or here would be better - let me try both ways and compare.

You can also continue with your previous approach and make the semidiscretization mutable. Maybe it's worth comparing all three approaches to see what works best in terms of code complexity and performance.

@huiyuxie
Copy link
Member Author

@ranocha Sure

@huiyuxie huiyuxie changed the title Replace mutable structs Replace mutable structs using Adapt Aug 28, 2024
@huiyuxie
Copy link
Member Author

Temporary fix by #2052 - we will see whether that solution can be permanent.

@huiyuxie huiyuxie closed this Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Refactoring code without functional changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants