untested examples?

[dneise]

I believe none of the examples in ctapipe/example is currently tested in a pytest.

I think untested examples can easily outdate and then confuse more than they help.

[kosack]

agreed - eventually however I think they may all move to notebooks that get automatically inserted into the documentation (as we discussed), but that may take some time.

So for now, we could just execute them like we do the notebooks... They are sort of integration tests, so we could make a tests/ directory with a test-runner that marks them as pytest.mark.integration (so they can be easily deactivated for quick testing), and just have a single test that loops through them and runs each...)

[kosack]

We can also then identify which ones are outdated and should be removed. A few might be useful to turn into real Tools (and move to ctapipe/tools), like muon_reconstruction and display_summed_images, which are already somewhat useful.

[dneise]

Karl works on this in #941

[Tobychev]

@kosack I think this can be closed by now?

[kosack]

Let me check - I think we can probably remove the examples directory, but I would like to move a few into notebooks. The only example I use that i find very useful for debugging is load_one_event.py

[maxnoe]

The examples/ folder is still tehre and contains a lot of somewhat useful but unstructured example code.

This should be either moved to docstrings, example notebooks or removed.

In the current state of this repo, the issue is still valid.

[kosack]

yes, following what I said above - I will make a PR that moves anything useful to notebooks.

[maxnoe]

Could also be docstrings of classes (e.g. the load_one_event could either be in the docstring of ArrayEventContainer or of (SimTel)EventSource

[maxnoe]

This is basically a duplicate of #657, closing this one