Jacob Wilkins

The other thing that might be useful is sticking a `version` flag into the JSON so we can check and update appropriately?

Given we have a lot of custom exceptions I see no real reason to not use some custom warnings if there's no relevant warning.

I guess the other question (and this is probably another issue in and of itself) is whether MDANSE needs its own database of atom properties, does something like [`periodictable`](https://periodictable.readthedocs.io/en/latest/) provide...

Periodictable does support compounds, but I see if these are abnormal physically (i.e. dummy atoms) a backup method might be valuable and complex to implement.

Some tools which enable some form of atom selection off the top of my head: - [Jmol](https://jmol.sourceforge.net/) - [Materials Studio](https://www.3ds.com/products/biovia/materials-studio) -- I think STFC have a license. - [OVITO](https://www.ovito.org/) -...

Suggest we might try adding a [global timeout](https://pypi.org/project/pytest-timeout/) to the test so we might actually get some debug information rather than GitHub killing the runner?

There're several tools available for reporting progress, particularly in CLI environments which provide e.g. progress bars, timing estimates, etc. - [`tqdm`](https://tqdm.github.io/) is probably the most commonly used. Provides both simple...

I don't think the original did this so I never put it in the rework, it's certainly very easy to add if we want it. Are there any other properties...

Issue occurs when selecting item from `RunTable` tab, due to `JobLogInfo` being a subclass of `TextInfo` and thus `type() is` checking exact types, but `isinstance` checking subclasses.

> One side problem is that the changes here will make the unit tests fail: `MDANSE_GUI/Tests/UnitTests/test_JobState.py` It is not a problem for now, but it will come back when #704...