[GUI] Enhancements

[DavidLP]

Needed features for the first release are summarized here (excluding bugs, for this we have other issues!)

• [x] Files: Drag and drop area for data files
• [x] Setup:
  • [x] Show set angles x 10 in plot
  • [x] Show correct relative distances
  • [x] Add material budget per plane, std. setting is 0
  • [x] Add the ability to add scatter planes in the beam (e.g. = not used devices). These planes just have a material budget, z position and alpha, beta rotation. Then these info can be used in the Kalman enabled track fitter
  • [x] Make scatter plane tabs closable and remove respective scatter plane from setup plotter
• [x] All tabs: Fixed parameter lists should be shown with a new line for each parameter for readability
• [x] Noisy Pixels Tab:
  • [x] Make optional per plane and not mandatory
• [x] Alignment: Should be optional but not mandatory
• [x] Track fitting: Ability to use pre-aligned tracks, since Alignment step should not be mandatory
• [x] Result: Should be split into optional result analysis steps (residuals, efficiency, ...)
• [x] All tabs: Ability to open created h5 files(s) with ViTables
• [x] Multi-threading/-processing to keep GUI responsive when performing analysis:
  • [x] Multi-threading when opening ViTables from GUI
  • [x] Multi-threading when performing analysis
• [x] Add plotting analysis results into GUI
• [x] Add option to run a consecutive analysis from first to last analysis step without user interaction
• [x] Add subclass of QDialog to improve pop-up dialog for exceptions (scroll text, save traceback to file, etc.)
• [x] Catch plotting exceptions
• [x] Show iterable of iterable in GUI
• [x] Improve option widgets
• [x] Show all plots: (added in 67e34132d6f67f6b4e577c38605f6326fd2aa2da)
  • [x] Show Pre alignment plots
  • [x] Show residual plots
  • [x] Show efficiency plots
• [x] Use plotting functions as they were defined before. Delete the quick copy&paste blob, fixed in 67e34132d6f67f6b4e577c38605f6326fd2aa2da
• [x] Implement saving and loading analysis sessions, added in e5999dffded2e444d1bbff9e9866b93f7a14e503
  • [x] Completely restore FilesTab, SetupTab, added in e5999dffded2e444d1bbff9e9866b93f7a14e503
  • [x] Completely restore Parallel/AnalysisTabs, added in 21e6a398ac42e3c77d80fed716afd3357c1149b5
• [x] Multi-threaded plotting
• [ ] Use QThreadPool and QRunnable for GUI-multithreading (see here)
• [x] Allow users to rerun tabs. Deactivate all preceding tabs that depend on the rerun, fixed in b46c4f625b1c5f014cf97dbe2a8e2e5119a92ffd
• [x] While the traceback window is very usefull, the user can be scared. The most usefull information is usually the last line of the traceback. Maybe one can show this info more prominent? Fixed in 6d1e457c173bc3e2898b53433cfd3df103f06f45
• [ ] Add generic class for data tab that recognizes the input data type (e.g. ROOT tree) and converts to HDF5
• [x] Load configuration for DUT setup from file #117
• [x] Add button to keep selection on widget upon error instead of always resetting entire tab #111
• [ ] Add nicer QTabBar for easier navigation for large amounts of DUTs #122

[leloup314]

Traceback (most recent call last): File "/home/leloup/miniconda2/bin/vitables", line 37, in <module> from PyQt4 import QtGui ImportError: No module named PyQt4 ViTables does not support PyQt5 but only PyQt4; cannot use ViTables with PyQt5 see

[DavidLP]

True. That's why I recommended to just issue the command vitables file.h4 in a console process when clicking the button:

from subprocess import call
call("vitables file.h5")

This allows to start system installations of vitables and vitables installations in other environments.

[leloup314]

Like this? This does not work for me even though the file exists in the cwd

[DavidLP]

Do sudo apt-get install vitables first. Should work

[leloup314]

Is the material budget a DUT property? What's the unit and how is it different from the thickness?

[DavidLP]

Is the material budget a DUT property?

Yes

What's the unit

@YannickDieter You did the calculation recently. Can you answer? I guess it is g / cm³

how is it different from the thickness

You can have different materials and the material budget also accounts for passive material (PCB, readout) etc.

[YannickDieter]

Yes but for the Kalman Filter we need matrial budget (radiation length) in um. So you need to divide it by the density of the material.

[YannickDieter]

At the moment, the kalman filter needs for every DUT the whole thickness (sensor + other materials) and the corresponding radiation lengths in um for the material (or compound).

[YannickDieter]

@YannickDieter You did the calculation recently. Can you answer? I guess it is g / cm³

sorry, it is g / cm². This gives cm if you divide it by the density.

[leloup314]

So you would need not only a material budget input but also a one for the density and radiation length of the material? Or should the correctly calculated quantity be put in directly?

[YannickDieter]

I dont know how we should do this in the future. But at the moment I only need radiation length (which is the same as material budget for me) in um + the whole thickness. So the user has to calculate the radiation length. Maybe it is better to this automatically, but then we need to pass the matrial as well.

[leloup314]

As far as I understood, we also want to consider two different materials e.g. sensor and PCB or housing. Does the Kalman filter take these also into account e.g. we would need: thickness_sensor + X_0_sensor + thickness_PCB + X_0_PCB?

[YannickDieter]

No not really. But e.g. for M26 (where I consider different materials: 50 um Si + 50 um Kapton), the user should take 100 um as total thickness and a radiation length of 125390 um. This follows from this formula: https://cds.cern.ch/record/1279627/files/PH-EP-Tech-Note-2010-013.pdf (radiation length of compounds)

[leloup314]

Okay, so we need one field for total thickness and one for the overall radiation length?

[YannickDieter]

Yes, but for each DUT ;)

[leloup314]

This occurred while testing. Does anyone know why?

[YannickDieter]

I also had this problem when calculating the residuals of the eutelescope example for Kalman tracks. The residuals for the first plane were all very close to zero (I think I know the reason now) and then the histogram function causes the error since if no bins are specified nbins is set to 'auto'. Specifying npixels_per_bin, nbins_per_pixel in the residual calculation should fix it.

[DavidLP]

Added a new issue. Related observations please add there. Also please always report issues, spotting and describing bugs is halve the work!

[leloup314]

This error has been occurring quite some times during testing. Especially when having mixed DUT types e.g. one FE-I4 and rest M26

[DavidLP]

This is another bug. Please open a bug report with info how to reproduce it.

[DavidLP]

@YannickDieter Can you upload your scattering plane track fitting, that we can see the API?

[YannickDieter]

Do you mean the option to add a additional scattering plane? Is it possible to push again into developement?

[leloup314]

@YannickDieter Do we really need an index_scatter for the scatter planes since we have the z positions which determine the index already, I guess. See here Is it possible to process more than one scatter plane? Right now one can add multiple scatter planes in the setup. @DavidLP Should we support multiple scattering planes or just one?

[DavidLP]

I think index_scatter should be removed.

[leloup314]

Is it implemented in cluster_hits function to have an input_noisy_pixel_mask_file which does not have a mask for all DUTs e.g. 4 DUTs and only 1 noisy pixel mask for one of the DUTs in input_noisy_pixel_mask_file?

[YannickDieter]

For support of multiple scattering planes and changes related to this option, see #78.

[leloup314]

@DavidLP should I keep track of every enhancement here or just close?

[DavidLP]

Looks good. Is the last point implemented?

[leloup314]

It's not yet implemented but I'm asking in general. Should I keep this list updated with every enhancement I implement or should I at some point close this 'issue' and resume to announce the enhancements just in the commit messages?

[DavidLP]

I would say we summarize all needed features for the first release here. For other not mandatory features we can create a new issue then.

[DavidLP]

I think drag and drop does not work for the file selection?

[leloup314]

Drag and drop works since May (678fae6d1d40d77db9b93258632f3a091f1feb59). I'm also very sure I showed you this feature then.

[DavidLP]

True, thought it was not working on Friday, but when I checked on Windows now it was working.

[DavidLP]

This should be just a tick box for every DUT, no?

[leloup314]

Yes, this should be just tick boxes, but I haven't changed this yet, since this is handled in here and I only fixed the option widget for multiple boxes. This should work for now, but I'm on it ("Improve option widgets"). There are several things that work, but should be improved.

[leloup314]

Set as fixed parameter in 6c251b9b1253d137bb261050ea8d6df7a304c5a8

[leloup314]

Fixed in 35b57e082ca69befdb474ee12c0d9b8797c7e57e

[leloup314]

@DavidLP Plotting is now done for all tab (except alignment, since I dont know what to plot there). Please have a look at 67e34132d6f67f6b4e577c38605f6326fd2aa2da. I changed plot_utils so it doesn't cointain code dublicates anymore, overall I had to change several files slightly to enable plotting of prealignment, efficiency and residuals since there are no standalone plotting functions for them and to implement them doesn't seem trivial at all without dublicating code. Does this look okay to you?