Rachel GUI
From GOSIA
(→GUI version backward compatibility) |
(updating for planned release candidate) |
||
| Line 3: | Line 3: | ||
[[File:Guisnapshot.png|thumb|right|A snapshot of the alpha version GUI.]] | [[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. 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 | + | 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 it has ''not'' been tested under Windows. |
| - | A 64-bit processor is essential, because Gosia runs fastest and most accurately on 64-bit machines. The release-candidate version, expected in the | + | A 64-bit processor is essential, because Gosia runs fastest and most accurately on 64-bit machines. The release-candidate version, expected in the September 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. |
| - | [[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 | + | [[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 of matrix elements. For collective systems, where the matrix definition often includes several hundred lines of matrix elements, rotor parameters can be given to reduce the setup time for the initial guesses of matrix element values. This also eliminates the need for the user to re-index the reduced matrix elements by hand as changes are made to the matrix or level scheme. |
==How to get the Rachel package== | ==How to get the Rachel package== | ||
| - | Version 2.0.8.beta is completely compatible with version 2.0.4.beta—2.0. | + | Version 2.0.8.beta is completely compatible with version 2.0.4.beta—2.0.8.beta and has the same backward-compatibility for session files older than 2.0.4.beta. Refer to the [[gui_release_notes | release notes]] for the change in this version. |
| - | The Rachel tar archive of version 2.0.8.beta is available on a [http://www.pas.rochester.edu/~hayes/beta_rachel/rachel.2.0.8.beta.tar temporary download site]. This includes an ''extended'' version of Gosia that makes use of file number 99 for amplitude vs. time data [[File:Amplitudes.png|thumb|right|Excitation amplitude as a function of the time-like variable 'w' generated by Gosia via the Rachel GUI.]] and collision function output for optional plotting functions in the GUI. Except for these two functions, the GUI can be run with the current version of Gosia | + | The Rachel tar archive of version 2.0.8.beta is available on a [http://www.pas.rochester.edu/~hayes/beta_rachel/rachel.2.0.8.beta.tar temporary download site]. This includes an ''extended'' version of Gosia that makes use of file number 99 for amplitude vs. time data [[File:Amplitudes.png|thumb|right|Excitation amplitude as a function of the time-like variable 'w' generated by Gosia via the Rachel GUI.]] and collision function output for optional plotting functions in the GUI. Except for these two functions, the GUI can be run with the current version of Gosia. |
==Installation notes== | ==Installation notes== | ||
| Line 104: | Line 104: | ||
==Upgrade strategy== | ==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 [[software upgrade voting|votes]] cast by the user community. 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.'' | + | 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 eventually will be directed primarily by [[software upgrade voting|votes]] cast by the user community. 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.'' |
| + | |||
| + | This voting plan has not been implemented yet. Users are encouraged to suggest desired upgrades through the Forum or the [[rachel_desired_upgrades | desired upgrades]] page to steer the software development. | ||
| - | |||
| - | |||
===Planned upgrades=== | ===Planned upgrades=== | ||
| - | There are a number of planned upgrades, some of which will be incorporated in the first [ | + | There are a number of planned upgrades, ''some'' of which will be incorporated in the first [[rachel_release_candidate | release candidate] version. The upgrade plan and priorities will be changed based on user feedback and bug reports. |
# More accurate stopping power calculations for low-Z beams. | # More accurate stopping power calculations for low-Z beams. | ||
| Line 116: | Line 116: | ||
## a transition from matplotlib graphics to pyGtk in the level scheme window | ## a transition from matplotlib graphics to pyGtk in the level scheme window | ||
## clickable objects in the level scheme diagram | ## clickable objects in the level scheme diagram | ||
| - | # Addition of Ge clusters with libraries of array geometries (Gammasphere, Agata, etc.) | + | # Addition of Ge clusters with libraries of array geometries (Gammasphere, Agata, Miniball etc.) |
# Plot functions to visualize fit conflicts in the data | # Plot functions to visualize fit conflicts in the data | ||
| - | # Improved object structure for Ge detectors. This will reduce the burden on the user by automatically updating the data set as the level scheme and matrix change. | + | # Improved object structure for Ge detectors. This will reduce the burden on the user by automatically updating the data set passed to Gosia as the level scheme and matrix change. |
# Optional setting of symbolic matrix definitions, whereas now the matrix is stored numerically. This will allow greater user control by allowing tuning of model parameters, e.g. <gam|E2|gsb> = M1 + a*M2, where 'a' can be adjusted by the user. | # Optional setting of symbolic matrix definitions, whereas now the matrix is stored numerically. This will allow greater user control by allowing tuning of model parameters, e.g. <gam|E2|gsb> = M1 + a*M2, where 'a' can be adjusted by the user. | ||
# Optional simple distributed processing of some functions. This will allow the user to set a maximum number of independent processes to speed up separable calculations (integrated yields, corrected yields and experiment simulations) by issuing a separate call to Gosia for each process<ref>True distributed computing is not handled by the current version of Gosia</ref>. | # Optional simple distributed processing of some functions. This will allow the user to set a maximum number of independent processes to speed up separable calculations (integrated yields, corrected yields and experiment simulations) by issuing a separate call to Gosia for each process<ref>True distributed computing is not handled by the current version of Gosia</ref>. | ||
| Line 129: | Line 129: | ||
Run-time help is available using the Help button. Users are encouraged to submit suggestions for additional help data. | Run-time help is available using the Help button. Users are encouraged to submit suggestions for additional help data. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
===Experiment planning and accuracy testing tools=== | ===Experiment planning and accuracy testing tools=== | ||
