Last release (0.16.0) introduced a connection model between GêBR and the working servers, rooted through a new player, known as Maestro. That change was the key to allow many remarkable improvements (see the post). However, that also brought some annoying behaviors, like few more login password requirements to establish all inter-machine connections.
This release brings wizards to simplify all that connection process, turning it now almost painless. But 0.18.0 is not only about fixing 0.16.0 drawbacks. There are many more improvements to mention: (Click here to read the rest of this entry)
Seismic Un*x (SU), fully integrated with GêBR, is the major set of programs for seismic processing employed by GêBR users. However, to take full advantage of this package through GêBR, it is up to the users install SU properly in their systems.
Despite well documented, the whole install process of SU might be cumbersome to new users. To made this task easier, GêBR Project provides a script to carry out all necessary steps to install SU properly, at least on Ubuntu systems. The script, updated to install the latest version of SU (43R1), has been tested on Ubuntu LTS 10.04, but should work on newer ones too.
Follow these steps to install SU: (Click here to read the rest of this entry)
The release 0.16.1 of GêBR comes with astonishing new features. Up to now GêBR established direct connections with processing servers. From now on, there is a new player, the Maestro. GêBR connects to a Maestro and it provides the processing servers under its domain. Since the Maestro controls the processing servers, it has the right to select which one will be responsible for execute a job requested by the user. This selection takes many factors into account, like the working loads of each server and the speed of their CPU’s.
Better than that, the Maestro can put many servers together to cooperate to conclude a job. Whenever a job can be split into small independent parts, the Maestro can distribute them to several servers. The Maestro is still in charge of collecting all responses, merge them and send it back to GêBR, where the user can inspect it as a whole.
The user can still interfere in this process, choosing how agressive the Maestro will be in the hunting for resources.
