Rachel GUI
From GOSIA
m |
(Added an image of a typical gosia input for a collective system.) |
||
| Line 9: | Line 9: | ||
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 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. | ||
| - | 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. [[picture]] This also eliminates the need for the user to re-index the reduced matrix elements by hand as changes are made to the matrix. | + | 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 [[File:Typicalgosiainput.png|thumb|right|Excerpt of a typical Gosia input for a collective system.]] 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. [[picture]] 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=== | ===Upgrade strategy=== | ||
