When the distance is calculated between the observed peaks and the forward simulation, the result is about an order of magnitude larger than expected. As far as I can tell, the actual indexations are correct; they match up with those found in the old version of the code.

There's already a function that creates a new analysis from the command line, but it would be nice to have something in the GUI as well.

At some point, I need to go through and add docstrings to all of the major functions and files. That would help with collaboration.

We should be able to handle a 1D scan as well as a mesh

It would be easier to run the spec macros if they were all in the experiment directory. However, they will have to be renamed so that they don't overwrite each other (something like scan0023grain001.mac or something)

Finding all the peaks in every frame makes it harder to differentiate which peaks belong together. A single peak which appears in N frames is flagged N times, regardless of whether it's actually "peaking" at that position. This makes it hard to determine the boundaries of a single grain, and causes fading peaks to spill into the spaces of other grains.

It would be better to mark each peak based on where it is brightest. This would require a 4D peak-finding optimization, and would probably need a slightly different image pre-processing routine.

Right now most of the function calls take just the config dictionary as a parameter. That abstraction is nice for concision, but prevents the functions from being useful outside of the rigid framework of my main working routine. It would be more useful to have the functions take actual parameters (which can be read in by the config dict). Then they could be cherry picked by anyone else wanting to use parts and pieces of this software.

When a config file is run, it should save something to the source code so that it opens to that same file the next time you run gui.py

The code needs a front page.

When we do a Laue scan using the px/py motors, everything gets stretched out on the map because it's trying to compensate for an angle that isn't actually needed.

We'd like to be able to run Laue analysis on a single image as well as a scan

It would be great if there were a way to check whether a certain command would produce valid results. In other words, it would disable a button if any of the following are true:

• An upstream config parameter has been changed.
• A command is run at least two levels upstream.

I can't think of any other reasons right now. This is a low-priority task, but a good one to keep in the back of my mind.

We should have a script that calls the detector calibration routine. There should also be a button to call the same routine from the GUI.

It would be great at some point to put in unit tests to ensure future compatibility.

Place a button in the GUI that toggles an extremely verbose mode

It should be able to handle a scan containing only a single substrate image.

Many of the parameters are highly unintuitive, so the user would benefit from rapid feedback. Probably a good idea to include more plots and printed output so the user doesn't need to just guess blindly.

The axes on the plot of grain positions should probably just extend to the full range of the scan