-
-
Notifications
You must be signed in to change notification settings - Fork 62
Use picard-tools script rather than full path to Picard jar #78
Comments
Howdy @samuell, that is a great find. Can you send a pull request to switch to that usage? |
@mr-c Sure, will make a try as soon as I start to grok all the details of the syntax :) |
@mr-c and @samuell, If you use those picard tools without docker and natively on ubuntu then yes you solution is better, but what if someone runs it somewhere else SuSE, Centos, MacOS, etc... The particular solution that we have involves docker image, and in that image a particular version of picard is installed in /usr/local/bin... |
CWL tool descriptions in this repository shouldn't require the use of Docker; frankly there shouldn't be any hard coded paths. The Java does present a particular problem as there isn't a standard place to install jars. A more portable approach to running Java programs that don't install a wrapper is for the user (or docker image) to set the baseCommand: [ java, picard.cmdline.PicardCommandLine, BuildBamIndex ] Equivalent to the following at the command line using the Debian paths: user@host:~$ CLASSPATH=/usr/share/java/picard.jar java picard.cmdline.PicardCommandLine BuildBamIndex |
(I commented also here about this.)
This is relevant to the Picard sub-tools.
I noticed that at least when intalling via apt-get on Ubuntu, you get a
picard-tools
script in/usr/bin
, which is executable from everywhere, that basically replaces thejava -jar [...path...]/picard.jar
part.Calling that script instead of using
java
and the full path to the jar would be more portable as it is not specific to a given path for the jar. It should also be easy to create a custom such script in one's/usr/bin/
or other folders set in one'sPATH
, if installing in a custom location.(For java options, I checked in the
picard-tools
script that it sends theJAVA_OPTIONS
env variable to java, in case that is needed, for setting the memory usage and the like.)The text was updated successfully, but these errors were encountered: