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

LAPD solver in 3D #221

Open
jwscook opened this issue Jan 17, 2024 · 20 comments
Open

LAPD solver in 3D #221

jwscook opened this issue Jan 17, 2024 · 20 comments
Assignees
Labels

Comments

@jwscook
Copy link
Member

jwscook commented Jan 17, 2024

DM has just fixed the outflow of the toy 1D model. This fix is being applied up the chain of codes and models.

@jwscook
Copy link
Member Author

jwscook commented Jan 24, 2024

Owen has found a problem in DM's 1D outflow - need to ask him this friday.
Ed to recheck that Firedrake implementation works with Mach number of 0.1

@jwscook
Copy link
Member Author

jwscook commented Apr 10, 2024

Ed has something going in FireDrake with sonic outflow

@jwscook
Copy link
Member Author

jwscook commented Apr 10, 2024

We still need Dave's help to get the NESO version working for the subsonic outflow case.

@jwscook
Copy link
Member Author

jwscook commented Apr 24, 2024

Dave is now back need to make a prioritised list:

1 DG or CG explicit time anisotropic diffusion (currently all examples use implicit timesteps e.g. https://github.com/ExCALIBUR-NEPTUNE/nektar-diffusion/blob/rfu_ambipolar/example/Unsteady_ring/ambipol.xml)
2 this sub-sonic outflow
3 nektar-waveeqn for implicit steps.

@jwscook
Copy link
Member Author

jwscook commented Jun 26, 2024

Back now as priority

@jwscook
Copy link
Member Author

jwscook commented Jul 3, 2024

Work has started in FireDrake over here

We need to decide on CG vs DG implementations where the dynamics aren't damped too quickly i.e. keep going as long as the Hermes3 simulations go.

@jwscook
Copy link
Member Author

jwscook commented Aug 14, 2024

Using Rogers & Ricci 2010 in Firedrake

@jwscook
Copy link
Member Author

jwscook commented Aug 14, 2024

@jwscook
Copy link
Member Author

jwscook commented Sep 4, 2024

Current activity is checking units and both @oparry-ukaea 's and @ethrelfall 's firedrake implementations for consistency.

@jwscook
Copy link
Member Author

jwscook commented Sep 18, 2024

3D runs with 1:1 mass ratio - investigating this to move to 1836 (R&R only use 400 in their paper).

@jwscook
Copy link
Member Author

jwscook commented Sep 25, 2024

3D is still a bit crashy. Jack's speed ups gives 20% improvement on the 2D version. 2D doesn't crash.

  • The 3D solution diverges when running with more than 1 node on Archer2 < big problem
  • 32 CPUs takes 15 hrs to get the crash point < way too slow.
  • Try periodic boundary conditions to see if it's the parallel +/- sound speed BCs causing the slow down.
  • Try turning on solver iteration counts via PETSc's logger

@jwscook
Copy link
Member Author

jwscook commented Oct 2, 2024

Struggling with proper BCs for electron velocity, https://github.com/ExCALIBUR-NEPTUNE/firedrake-lapd/blob/rogers-ricci_v1/docs/rogers-ricci.md#boundary-conditions: not sure if BCs are applied in Firedrake.

These BCs are a function of electron temperature in time, so one needs to apply this as an EquationBC https://www.firedrakeproject.org/firedrake.html#firedrake.bcs.EquationBC?

@jwscook
Copy link
Member Author

jwscook commented Oct 23, 2024

The new BC fixes the problem is ~10x slower than the version w/o BC.

@jwscook
Copy link
Member Author

jwscook commented Oct 30, 2024

Made simplifications to the 3D model but it's still not working despite the potential solver being the same as in 2D.

  • make sure the potential normalisation is adequate: $\phi \approx 1$.
  • loop in Romain to inspect the fine grained output
  • loop in the Firedrake developers on an MWE

@jwscook
Copy link
Member Author

jwscook commented Nov 13, 2024

This has morphed into a Rogers & Ricci solver...

@jwscook
Copy link
Member Author

jwscook commented Nov 20, 2024

Testing BCs in true 1D in Firedrake (Ed) and in Nektar (Owen) to then move to 3D.

@jwscook
Copy link
Member Author

jwscook commented Dec 4, 2024

Using 1D-in-3D version of equations to make finding the indices on trace points on boundaries more general so that the solver works in 3D for any number of expansion modes / mesh / MPI ranks.

@jwscook
Copy link
Member Author

jwscook commented Jan 8, 2025

Waiting for DM to implement the non-isothermal form in 1D. Difficulty writing non-conservative equations into Nektar++. Ed working on 3D version in Firedrake.

@jwscook
Copy link
Member Author

jwscook commented Jan 15, 2025

Still waiting

@jwscook
Copy link
Member Author

jwscook commented Jan 22, 2025

It works in 1D in Firedrake - not tried in 3D yet. Still waiting on DM to implement 1D version in conservative form.

Generally speaking, it is hard to solve non-conservative form equations in Nektar++'s DG solver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants