Install libgr with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• gksqt
• grplot

Project history

The GR documentation says the framework was developed by the Scientific IT-Systems group at the Peter Grunberg Institute, Forschungszentrum Juelich, with Josef Heinen as the main developer and maintainer. It positions GR as a self-contained visualization library suited to real-time and signal-processing environments.

GR combines an implementation of GKS with OpenGL-backed rendering and related components such as GR3 for simple 3D scenes. The documentation records GR3 as work by Florian Rhiem and describes the library as usable directly from C or through Python ctypes and Julia ccall interfaces.

Adoption history

GR spread through scientific Python and Julia more than through a standalone desktop-app story. The project references presentations at PyCon DE 2012 and 2013, PyCon US 2013, EuroPython 2014 and 2015, EuroSciPy 2015, JuliaCon 2015 and 2016, and SciPy 2016.

The project documentation says release 0.6 added Matplotlib backend support, and version 0.10.0 added inline graphics for IPython, Jupyter, and Julia-style interactive workflows. That made GR attractive as a fast plotting backend in notebooks and numerical environments.

How it is used

Users install libgr for the native GR libraries and tools such as gksqt and grplot. Developers call the C API or use language packages to produce 2D graphs, 3D scenes, inline notebook graphics, and GUI-integrated scientific visualizations.

Because GR is self-contained and portable, it is often packaged as a native dependency below higher-level plotting packages. The Homebrew libgr formula gives macOS users the C-level runtime expected by language bindings and plotting frontends.

Why package nerds care

GR is package-manager interesting because many users meet it indirectly through plotting stacks: a Python or Julia plotting package suddenly depends on a native graphics runtime, Qt terminal, fonts, OpenGL behavior, and platform-specific display plumbing.

The package name libgr highlights the native-library layer beneath the friendlier GR Framework name. For maintainers, this means tracking not only source releases but also binary artifacts, shared-library search paths, and GUI terminal behavior.

Timeline

• 2011: GR references include Neutron Science Visualization Software work at Juelich.
• 2012: GR was presented at PyCon DE and described as a universal framework for visualization applications.
• 2013: GR was presented at PyCon US and PyCon DE.
• 2015-03-09: The v0.10.0 tag was created; the documentation associates 0.10.0 with inline graphics support for IPython and Jupyter-style environments.
• 2016: GR was presented at JuliaCon and SciPy, showing adoption in Julia and Python scientific-computing communities.

Related projects

• GKS and OpenGL are the graphics foundations named by the GR documentation.
• Matplotlib, IPython, Jupyter, and Julia are major environments described by GR's documentation and references.
• GR3, GR.jl, python-gr, ruby-gr, and grplot are related components or bindings around the native library.

Sources

• https://github.com/sciapp/gr
• https://github.com/sciapp/gr/blob/master/README.md
• https://gr-framework.org/
• https://gr-framework.org/about.html
• https://gr-framework.org/references.html