Rachel GUI

Revision as of 13:36, 9 March 2011 (view source)

Hayes (Talk | contribs)

← Older edit

Revision as of 13:37, 9 March 2011 (view source)

Hayes (Talk | contribs)

(changed heading levels and organization)

Newer edit →

Line 8:

[[File:Typicalgosiainput.png|thumb|right|Excerpt of a typical Gosia input for a collective system.]]While gosia.20081208 incorporates the [[OP,BRIC]] command to read internal conversion data from BrIcc data files, removing the burden of entering ICC interpolation data by the user, the GUI allows the greatest possible automation by prompts for pre-defined or user-defined germanium detector crystals or arrays, calculation of Zeigler stopping power data, optimum meshpoint selection for yield calculations, transformation of rectilinear detector definition to laboratory-frame spherical-polar interpolation coordinates, etc. For standard problems, the burden on the user is reduced to entering nuclear level and matrix data for simulations (including optional data-set simulation) and real experimental data for fitting. For collective systems, where the matrix definition often includes several hundred lines of matrix elements, rotor parameters can be given to reduce the input definition considerably. This also eliminates the need for the user to re-index the reduced matrix elements by hand as changes are made to the matrix.

-

~~==Upgrade strategy==~~

-

Upgrades are being made to incorporate all of the capabilities of Gosia, with a focus on the most commonly used features. Prioritization of the upgrades will be directed primarily by Gosia user input on the [[Gosia forum]]. Users are encouraged to submit requested upgrades to handle present features of Gosia that are not already included, ''as well as new functions that Gosia does not handle, but which could be incorporated via the GUI.''

==GUI version backward compatibility==

Line 54:

Line 50:

For experiments that fit the capabilities above, the user can view the Gosia inputs to learn the format, but will not be required to type any input code. Experienced Gosia users can export a GUI-generated input skeleton file and abandon the GUI to use the more advanced capabilities of Gosia.

-

==Planned upgrades==

+

==Upgrade strategy==

+

Upgrades are being made to incorporate all of the capabilities of Gosia, with a focus on the most commonly used features. Prioritization of the upgrades will be directed primarily by Gosia user input on the [[Gosia forum]]. Users are encouraged to submit requested upgrades to handle present features of Gosia that are not already included, ''as well as new functions that Gosia does not handle, but which could be incorporated via the GUI.''

+

===Planned upgrades===

There are currently several planned upgrades that will likely be incorporated in the first [release candidate] version. The upgrade plan and priorities will be changed based on user feedback and bug reports.

From GOSIA

Revision as of 13:37, 9 March 2011

Views

Personal tools

Navigation

Search

Toolbox

@@ Line 8: / Line 8: @@
 [[File:Typicalgosiainput.png|thumb|right|Excerpt of a typical Gosia input for a collective system.]]While gosia.20081208 incorporates the [[OP,BRIC]] command to read internal conversion data from BrIcc data files, removing the burden of entering ICC interpolation data by the user, the GUI allows the greatest possible automation by prompts for pre-defined or user-defined germanium detector crystals or arrays, calculation of Zeigler stopping power data, optimum meshpoint selection for yield calculations, transformation of rectilinear detector definition to laboratory-frame spherical-polar interpolation coordinates, etc.  For standard problems, the burden on the user is reduced to entering nuclear level and matrix data for simulations (including optional data-set simulation) and real experimental data for fitting.  For collective systems, where the matrix definition often includes several hundred lines of matrix elements, rotor parameters can be given to reduce the input definition considerably.  This also eliminates the need for the user to re-index the reduced matrix elements by hand as changes are made to the matrix.
-==Upgrade strategy==
-Upgrades are being made to incorporate all of the capabilities of Gosia, with a focus on the most commonly used features.  Prioritization of the upgrades will be directed primarily by Gosia user input on the [[Gosia forum]].  Users are encouraged to submit requested upgrades to handle present features of Gosia that are not already included, ''as well as new functions that Gosia does not handle, but which could be incorporated via the GUI.''
 ==GUI version backward compatibility==
@@ Line 54: / Line 50: @@
 For experiments that fit the capabilities above, the user can view the Gosia inputs to learn the format, but will not be required to type any input code.  Experienced Gosia users can export a GUI-generated input skeleton file and abandon the GUI to use the more advanced capabilities of Gosia.
-==Planned upgrades==
+==Upgrade strategy==
+Upgrades are being made to incorporate all of the capabilities of Gosia, with a focus on the most commonly used features.  Prioritization of the upgrades will be directed primarily by Gosia user input on the [[Gosia forum]].  Users are encouraged to submit requested upgrades to handle present features of Gosia that are not already included, ''as well as new functions that Gosia does not handle, but which could be incorporated via the GUI.''
+===Planned upgrades===
 There are currently several planned upgrades that will likely be incorporated in the first [release candidate] version.  The upgrade plan and priorities will be changed based on user feedback and bug reports.