Remove VTK_cartesian config key and corresponding code #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in issue #33, the plan was to fix the Cartesian VTK output since it contained a few bugs. I realized that the fix is quite complex due to the transformation$t = \tau \cdot \cosh(\eta)$ and the resulting spread of values over multiple Cartesian time files (which is not considered in the code at the moment). Furthermore, this output is probably not used by anyone and since it is not useful because of the bugs, Niklas and I decided to simply remove it. A fortunate side point is that the removal decreased runtime when VTK output is used.
What I did
What I tested
eps
,mub
,muq
,mus
,nb
,nq
,ns
,p
,pi
, andT
with my changes and with thestable_ebe
branch (with the same config and IC) and compared the outputs. They were identical, so my changes shouldn't have changed anything output-wise.VTK_cartesian 1
in in one run and as expected it was not taken into account.@NGoetz, could you check the changes and comment or approve?
@yukarpenko, as soon as Niklas approved it would be nice if you could take a look and comment or merge.