Philipp Grete

> > * (assuming a test dataset is desired), how to upload/handle/provide the dataset > > yes that would be a necessary step for us to merge this PR. The...

> I think that the reason CI is now failing is that #4344 was merged in between runs. Add `test_outputs.py` to the list of files that pytest should ignore to...

Looks like I'm stuck. How can I actually run tests? I first thought that the test are answer tests so that I should call them using a class (like `TestTipsy`...

I'm a little stuck here. I realized that the failing test was run with `py38` so I thought that my python environment may be too new (also wrt the nose...

So I'd call `python tests/nose_runner.py` (as that's the command being run by the `py38` GitHub check)? And, if yes, can I just run the Parthenon frontend or do I need...

I figured it out (for reference `nosetests -v --with-answer-testing --local --local-dir $HOME/src/yt-test-data --answer-store --answer-name=local-parthenon yt.frontends.parthenon`). Going back to the old doc helped. I just added a plain Parthenon 2D test...

In the process of adding data files of two other codes I'm currently wondering a) if (and how) yt might handle data from general relativistic simulations, i.e., data that might...

I'm back a little bit late to the show so I'm wondering why there may be merge conflicts? I regularly updated this branch with main and things have been working...

FWIW printing out a graph should be straightforward if an API similar to the one in Parthenon is used (as all information could be printed in a way understood by...

I think that sth on GitHub would be the option that has the lowest barrier (as everyone already has a GitHub account and knows how to use it). An awesome...