Rachel GUI

Revision as of 13:05, 28 April 2011 (view source)

(→Experiment planning and accuracy testing tools: Notes added on upgrades of simulation tools since the videos were recorded.)

← Older edit

Revision as of 13:23, 28 April 2011 (view source)

128.151.144.176 (Talk)

(→General description)

Newer edit →

Line 3:

[[File:Guisnapshot.png|thumb|right|A snapshot of the alpha version GUI.]]

-

The Rachel interface facilitates [http://www.pas.rochester.edu/~hayes/beta_rachel/calculation_in_2_minutes.html fast setup of Gosia calculations] and data analysis using push-button controls with guided input and 'plain language' warnings during setup. The GUI ~~(Graphical User Interface) has been developed for~~ a modified Gosia version based on release 20081208.10, called 20081208.10.a. It is ~~currently undergoing beta-testing~~. ~~The latest beta-test version can be [downloaded here]. [http://www.students.yorku.ca/~rachelo/~~ Rachel] is written in Python 2.6 and is expected to be Python 2.7 compliant. It runs under Linux and Unix (OS X) machines, but is ''not'' Windows compatible.

+

The Rachel interface facilitates [http://www.pas.rochester.edu/~hayes/beta_rachel/calculation_in_2_minutes.html fast setup of Gosia calculations] and data analysis using push-button controls with guided input and 'plain language' warnings during setup. It is currently undergoing beta-testing. The GUI ''optionally'' uses a modified Gosia version based on release 20081208.10, called 20081208.10.a. This modified Gosia source code is distributed with the Rachel package. Rachel is written in Python 2.6 and is expected to be Python 2.7 compliant. It runs under Linux and Unix (OS X) machines, but is ''not'' Windows compatible.

-

A 64-bit processor is ~~desirable~~, because Gosia runs fastest and most accurately on 64-bit machines. The release-candidate version, expected in ~~early~~ 2011, will have many structural changes in the code, allowing more automation, more general particle detector options and fewer user prompts for standard operations.

+

A 64-bit processor is essential, because Gosia runs fastest and most accurately on 64-bit machines. The release-candidate version, expected in the summer of 2011, will have many structural changes in the code, allowing more automation, more general particle detector options and fewer user prompts for standard operations. It is expected that the release candidate will make more use of push-button control panels and less input and output to the terminal.

[[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.

From GOSIA

Revision as of 13:23, 28 April 2011

Views

Personal tools

Navigation

Search

Toolbox

@@ Line 3: / Line 3: @@
 [[File:Guisnapshot.png|thumb|right|A snapshot of the alpha version GUI.]]
-The Rachel interface facilitates [http://www.pas.rochester.edu/~hayes/beta_rachel/calculation_in_2_minutes.html fast setup of Gosia calculations] and data analysis using push-button controls with guided input and 'plain language' warnings during setup.  The GUI (Graphical User Interface) has been developed for a modified Gosia version based on release 20081208.10, called 20081208.10.a.  It is currently undergoing beta-testing.  The latest beta-test version can be [downloaded here].  [http://www.students.yorku.ca/~rachelo/ Rachel] is written in Python 2.6 and is expected to be Python 2.7 compliant.  It runs under Linux and Unix (OS X) machines, but is ''not'' Windows compatible.
+The Rachel interface facilitates [http://www.pas.rochester.edu/~hayes/beta_rachel/calculation_in_2_minutes.html fast setup of Gosia calculations] and data analysis using push-button controls with guided input and 'plain language' warnings during setup.  It is currently undergoing beta-testing.  The GUI ''optionally'' uses a modified Gosia version based on release 20081208.10, called 20081208.10.a.  This modified Gosia source code is distributed with the Rachel package.  Rachel is written in Python 2.6 and is expected to be Python 2.7 compliant.  It runs under Linux and Unix (OS X) machines, but is ''not'' Windows compatible.
-A 64-bit processor is desirable, because Gosia runs fastest and most accurately on 64-bit machines.  The release-candidate version, expected in early 2011, will have many structural changes in the code, allowing more automation, more general particle detector options and fewer user prompts for standard operations.
+A 64-bit processor is essential, because Gosia runs fastest and most accurately on 64-bit machines.  The release-candidate version, expected in the summer of 2011, will have many structural changes in the code, allowing more automation, more general particle detector options and fewer user prompts for standard operations.  It is expected that the release candidate will make more use of push-button control panels and less input and output to the terminal.
 [[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.