It would be nice if the filter dialog gives sime hint of the values range in the dataset. e.g. the molecule weight is beween x and y. The JSpinner should have this borders too. The JSpinnter should select the step with by the range. e.g. if the range is between 0 and 1 the spinner should do steps of 0.1 and if the range is between 0 and 10 the spinner should do steps of 1.
Added minimum and maximum of the property to the spinner and adjusted the stepsize depending on the range([9240b6]).
Related
Commit: [9240b6]
Fixed some bugs and applied some improvements ([cd9de7] and preceding commits). Seems to work now.
Related
Commit: [cd9de7]
Last edit: Till Schäfer 2018-03-05
3) getAccNumPropertyDataset() does not take the current subset into account. Should a filtering be applied to the current subset?
When creating a new session there is a problem: getAccPropertyMinMax() needs the current subset, which can be the root subset. This subset is not present at this time, since the filtering is used to create just this subset. Is there any way to get the minimum and maximum o a scaffold property considering the current tree but not the current subset?
Last edit: Philipp Mewes 2018-03-09
(1) Added a hint below the combo box ([4b61a6], [701453])
(2) Fixed this bug ([51c74e]). It was caused by the subset beeing null at this time
(3) UPDATE: Removed the new method ([bb2cb3]), and replaced its calls with the proposed methods. With the correct parameters getAccPropertyMinMax() does not crash when the subset is null. However the minimum/maximum is not calculated in this case.
(4) The tree is used now for the calculation ([3c65be]).
Related
Commit: [3c65be]
Commit: [4b61a6]
Commit: [51c74e]
Commit: [701453]
Commit: [bb2cb3]
(3) Added a workaround which solves the problem ([06a631]). However this solution is not very clean. For some parameter values it is allowed for the subset to be null, for others it is not and will result in a crash.
More precisely spoken: It is allowed to set the subset to null, if the method is called with a scaffold property and subtreeCumulative is set to false.
For example:
The call
getAccPropertyMinMax(tree, someScafProp, null, null, false, false false)will return a correct result whilegetAccPropertyMinMax(tree, someScafProp, null, null, true, false, false)will result in a nullpointer-exception.
There already exist similiar cases with the AccumulationFunction. For some combinations of parameters this parameter is ignored, for others it is not.
Related
Commit: [06a631]
(3) Can you please open another bug report and precicely describe the parameter combinations, that crash or create unexpected results? We should fix the implementation.
(5) current implementation crashes with an NPE at
edu.udo.scaffoldhunter.model.db.Filter.getPropDef(Filter.java:79), when creating a new session and adding a numerical filter on a molecule property (reproducible on the tutorial dataset and the "Activity at 0.057mM_%" property) (see attached stracktrace)Last edit: Till Schäfer 2018-03-26
Since in BR 300 only the javadoc is changed this feature is not blocked any longer by this bug.
(5) Looks like this is fixed here: [9a3121]. The exception does not occur any longer.
Related
Commit: [9a3121]