-
Notifications
You must be signed in to change notification settings - Fork 39
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
Difference between project Riemann1 and Shocktest? #647
Comments
I suppose the one using the TriAxisSearch will be more recent, as that's the optimised block initialisation version. Now you will have the most recent shock code in the IPShock project, that should easily be "simplified" to do a shock tube if the perturbations are set to zero and the shock width is made small. |
Indeed recent shock tests have been made with the IPshock class, but that one makes some assumptions about the frame of reference. So I think there is merit in perhaps keeping a simpler shocktest version alive as well. |
The two projects Riemann1 and Shocktest has very similar setups. The required input parameters for the two projects are identical. The differences seem to be
Shocktest
is a subclass ofTriAxisSearch
(which is a subclass ofProject
), whereasRiemann1
is a direct subclass ofProject
.I then check what makes the class
TriAxisSearch
different from a baseProject
class. It seems that forTriAxisSearch
an optimizedfindBlocksToInitialize()
is defined to start the loop from the initial bulk velocity, which makes it faster.The
findBlocksToInitialize()
method for baseTriAxisSearch
has the following commentvlasiator/projects/projectTriAxisSearch.cpp
Lines 32 to 34 in af6b9b6
but inside the function the vspace resolutions
dvx, dvy, dvz
seems to be completely decoupled such that different resolutions in the vx, vy, vz dimension are allowed?vlasiator/projects/projectTriAxisSearch.cpp
Lines 47 to 49 in af6b9b6
Should we keep both projects? Which one should we use to perform a 1D shock tube test?
The text was updated successfully, but these errors were encountered: