1. I do not see save/load buttons in GêBR. How can I save my work?
    Every project, line or flow is automatically saved in GêBR. You can safely close GêBR. All your data will be restored next time you launch GêBR.
  2. What is the menu entity in GêBR/DéBR?
    Menu is the name given to the representation of a program (or set of programs) inside GêBR. To a program be available for use in GêBR, a menu for it must be provided. DéBR is the GUI used to create menus for GêBR.
  3. Where does GêBR look for menus?
    GêBR scans a list of predefined directories and merge all menus in those directories to assemble the list of menus presented in the interface. Those directories are:

    <the directory specified by the user at GêBR preferences' dialog>

  4. I have just installed GêBR and its menus for Seismic Un*x. Is that enough to start using Seismic Un*x to process seismic data?
    No. GêBR is an interface to Seismic Un*x (SU), as far as you have its menus installed. However, to de fato  use SU, it has to be installed too. The Seismic Un*x project does not provide binary packages, like GêBR project does. Therefore, you have to follow the step-by-step instructions to compile and install SU from source code.
  5. Step-by-step instructions to compile and install SU?! That sounds too hard for me. Is there an easier way to get SU working?
    Yes (or perhaps). The GêBR project, as a courtesy,  provides a shell script that goes through the whole download/compile/install process of the Seismic Un*x. This script is designed for Ubuntu / Debian systems. See this post.
  6. Why does not GêBR find programs I have installed in my home directory?
    GêBR looks for programs in paths specified by the PATH environment variable. To add a custom search path, edit .bash_profile file in your home directory and include a line like:

    export PATH=$PATH:/my/local/path/to/programs

    You will need to logout and login back so this change be take into account.

  7. Could program xyz be include in GêBR?
    Almost any program can be included in GêBR. But GêBR makes some assumptions:
    • The program must be executable as command line from a shell. This prohibits to port Fortran or C subroutines or even Matlab codes. However, it is possible to encapsulate a C or Fortran subroutine into a program in such a way it turns to be executable directly from a command line.
    • The program’s behavior should be controlled by command line options.
    • The program should read its input data from standard input and send its output to the standard output. Programs with this feature can be chained to build flow processes.
    • Once the program starts it should not ask the user for further information interactively.
  8. How do I include the program xyz into GêBR?
    You should employ the DéBR, which is the interface designed to accomplish this task. It is part of the GêBR suite.

no comment until now

Sorry, comments closed.