Default use of the q-catch feature, automatisation
Depending on the selected histogramming the effective Q-values within one histogramming Q-slot may have an exc essive variation, still within the box (always) but possibly adding excessive variation (pseudo noise) to the S(Q,t) curves. Even worse sometimes the values have a trend towards lower/higher Q correlated with t, this would lead to wrong decay constants or whatever. The q-catch feature was a first attempt to deal with this trap. The users MUST always be aware and pointed to these effects.
Currently one may discriminate more or less favorite histogrammings by visual inspection of the corresponding plots of the Q,t coverage in the reports.
TDB: Automatisation as follows: 1.) DrSpine automatically tries a larger number of possible histogrammings from the range of sensible settings (...we have to define that...). 2.) The histogrammings are sorted according to the Q-variation in each Q-table a.) globally for the whole Q, t range b.) locally, individually for each Q-box 3.) the best (lowest variation in Q) make it to the repost and results output a.) globally b.) mixed histogrammings, for echa Q-range the bests ??? (see how this would work)
....