Maciej Bartkowiak

This problem does not occur anymore with the current code from the main branch.

I tried to implement all the changes you recommended. 1. Input checks should prevent the GUI from crashing, 2. There are 3 actions in the instrument context menu. 3. The...

With the latest changes, the following happens: 1. The normal starting point is "No instrument", which makes the widgets use the same parameters as always, 2. If an instrument is...

After the latest changes, only the input fields for q vectors and instrument resolution are affected by changes to the instrument definition. So, it is now possible to configure a...

I think that the discussion now has moved towards comparing the current functionality of the "instrument profiles" to user expectations. If users want to be stopped from making changes to...

This PR has now reached the stage where: 1. The GUI does not crash if the trajectory has no unit cell, 2. The Molecular Viewer / Trajectory Info shows a...

Following your recommendation, different analysis types now fail if unit cell is not defined, **but** they recommend TrajectoryEditor as a backup solution, which allows adding a unit cell definition to...

Is it possible that the first problem was in fact not related to the cell definition, but instead this: https://github.com/ISISNeutronMuon/MDANSE/issues/520 ? As for the way the velocities are handled, thanks...

With the current version, I was able to run TrajectoryEditor with atom selection, and run Static Structure Factor calculations on the resulting trajectory afterwards. If the trajectory you tried to...

Distinct van Hove function calculation now has a test for the presence of a valid unit cell. The job will fail if the unit cell is missing or set to...