Install Request: Schrödinger Maestro (via personal email)

Open
#518 38 comments 0 reactions 1 assignee View on GitHub

@owainkenwayucl is already working on this.

Since Mar 31, 2023.

Assessment

This issue has not been assessed yet.

Description

App install

Application: Schrödinger Maestro

Link: https://www.schrodinger.com/products/maestro

Cluster: Michael/Myriad/Kathleen

Description: Maestro is a suite of tools for doing molecular docking. It has a GUI (which uses QT) but can submit jobs into a cluster.

License: There are two license options - The ARUK DDI here at UCL has licenses, and there's a free Academic license which I'm using to test.

Ticket number: personal email

I got it to start in a container with GUI stuff - it needs:

INFO: This system was identified as "rhel".
required_packages for your platform are: fontconfig libX11 libxkbcommon-x11 xcb-util-renderutil libglvnd-egl libglvnd-opengl libxkbcommon
fontconfig-2.13.0-4.3.el7.x86_64
fontconfig-2.13.0-4.3.el7.i686
libX11-1.6.7-2.el7.x86_64
libX11-1.6.7-2.el7.i686
package libxkbcommon-x11 is not installed
package xcb-util-renderutil is not installed
libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64
libglvnd-opengl-1.0.1-0.8.git5baa1e5.el7.x86_64
libxkbcommon-0.7.1-3.el7.x86_64
(libxkbcommon-x11 xcb-util-renderutil) is/are required package/s to use Schrödinger suite. Please install them using:
        sudo yum install libxkbcommon-x11 xcb-util-renderutil

Which would need to be added to the image. I'm currently experimenting to see if I can make it work with those packages in modules.

So there are three options:

  1. Install the missing libs in the image
  2. Install it in a singularity container - this will cause problems for job submission
  3. Get it to work with important libraries in modules

Obviously, in increasing order of difficulty, decreasing order of neatness.

Dominant language
Shell
Stars
42
Forks
26
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UCL-ARC/rcps-buildscripts

All issues in UCL-ARC/rcps-buildscripts

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.