Difference between revisions of "ZINC22:Singularity"

From DISI
Jump to navigation Jump to search
Line 33: Line 33:
 
  export OUTPUT
 
  export OUTPUT
 
  export LOGGING
 
  export LOGGING
  export LICENSE_DIR
+
  export OE_LICENSE
 +
export CHEMAXON_LICENSE_URL
 
  export JOB_ID
 
  export JOB_ID
 
  export SGE_TASK_ID
 
  export SGE_TASK_ID

Revision as of 22:00, 8 February 2021

Info on using ZINC-22 3D building in singularity.

how to use the singularity image

ok, the image is @ /nfs/home/xyz/soft/build3d.img so, to run it, do the following:

LICENSE_DIR= ((((whatever you want it to be))))
export OE_LICENSE=$LICENSE_DIR/oe-license.txt (((((or whatever it is called)))))
export CHEMAXON_LICENSE_URL=$LICENSE_DIR/jchem-license.cxl
export OUTPUT= ((((some directory on the nfs where output is going))))
export INPUT= ((((some directory on nfs where input resides))))
export LOGGING= ((((wherever logs should go))))
export SGE_TASK_ID=((((whatever you want, the script will evaluate the SGE_TASK_ID'th entry in $(find -type f $INPUT | sort) ))))
export SGE_JOB_ID=test
export SINGULARITY_BINDPATH=$LICENSE_DIR,$OUTPUT,$INPUT
singularity run build3d.img

how to build the singularity image

BKS uses centos7 for our operating system, which can cause issues when building with singularity, particularly if you are building on ubuntu. See https://singularity.lbl.gov/building-centos-image for more details.

The gist is, our singularity image needs to be built on a centos machine.

To build our image, simply pull the necessary files from dockerhub (link not yet here), chdir to the directory you just cloned and run the following command:

singularity build build3d.simg Singularity3D

The resulting build3d.simg can be used to run 3d building jobs with singularity.

export INPUT
export OUTPUT
export LOGGING
export OE_LICENSE
export CHEMAXON_LICENSE_URL
export JOB_ID
export SGE_TASK_ID
export 
singularity run build3d.simg