Recent changes to tickets

#10 Crystallographic color map in GtGrainsManager

Laura Nervo — Fri, 13 Dec 2013 14:20:07 -0000

status: accepted --> closed
assigned_to: Yoann Guilhem --> Laura Nervo

#12 Automatic reload volume in GtGrainsManager

Laura Nervo — Fri, 13 Dec 2013 14:18:37 -0000

status: accepted --> closed
assigned_to: Nicola Vigano --> Laura Nervo

#12 Automatic reload volume in GtGrainsManager

Laura Nervo — Tue, 22 Oct 2013 08:43:13 -0000

GtGrainsManager now allows the automatic loading of a volume when changing type in the GUI.

See the commit's link http://sourceforge.net/p/dct/code-git/ci/6c36b73e16b50eb98fc39b46967518eda6caded3/

#9 Check parameters consistency at each analysis step

Laura Nervo — Fri, 04 Oct 2013 12:40:02 -0000

status: open --> closed

#9 Check parameters consistency at each analysis step

Laura Nervo — Fri, 04 Oct 2013 12:39:43 -0000

I have implemented the check of parameters at each analysis step, by using gtCheckParameters. It is now possible to use a flag "checkType" to select the type of parameters to be checked: it can be 'used','default','extra','all'.
Now it handles the sub-structures for 'cryst' and 'index'.

The ticket now should be closed.

#9 Check parameters consistency at each analysis step

Laura Nervo — Tue, 03 Sep 2013 08:10:35 -0000

Modified the function gtModifyStructure in order to be able to add/remove parameters which are not saved and for which we should set the type properly. In the description field, the function(s) which use the parameter are displayed (like a listbox).

TO DO LIST: - check existence of pattern "\ "
(one space after the section name).
maybe there are some suggestions to improve that part.
I'm using the find command and then regexp in matlab.
- Chek each function with name gt

DefaultParameters to
have the right number of parameters and the right value...
I don't know how to do that :-)
- Check the parameters for sub-structures (i.e. index.strategy).
The suggestion is to use the method used in build_structure from the list

#9 Check parameters consistency at each analysis step

Laura Nervo — Mon, 26 Aug 2013 14:25:18 -0000

Legend:

 USED = Used in the code
SAVED = Saved in the parameters.mat file

DEFAULT = Listed with complete info in build_list_v2.m
ADDED_P = Added to parameters.mat
ADDED_D = Added to default_list and default_parameters, outputs from make_parameters(2)
GUI = Editable with the GUI in gtModifyStructure.m
REMOVED_P = Removed from parameters.mat
REMOVED_D = Removed from default_list and default_parameters

Parameter status and action used:

DEFAULT + USED + NOT SAVED -> ADDED_P + GUI
NOT DEFAULT + USED + NOT SAVED -> ADDED_P + GUI + ADDED_D
NOT DEFAULT + USED + SAVED -> ADDED_D

DEFAULT + NOT USED + SAVED -> REMOVED_P + REMOVED_D
NOT DEFAULT + NOT USED + SAVED -> REMOVED_P
DEFAULT + NOT USED + NOT SAVED -> REMOVED_D

#9 Check parameters consistency at each analysis step

Laura Nervo — Mon, 26 Aug 2013 14:09:38 -0000

Working on gtCheckParameters function. I'm using gtModifyStructure that shows names, descriptions, classes and usertypes for each parameter.

The check on the parameters for each section is concerning the parameters saved in the mat file, the defaults parameters in build_list_v2 and the used parameters in the code.

#9 Check parameters consistency at each analysis step

Laura Nervo — Mon, 26 Aug 2013 14:06:47 -0000

status: accepted --> open

#26 Store DCT branch/version in parameters file

Yoann Guilhem — Thu, 01 Aug 2013 12:41:40 -0000

status: open --> accepted