New feature

Ability to specify the Compute Engine disk type (pd-standard or local-SSD) found in the new Cloud Life Sciences API (https://cloud.google.com/life-sciences/docs/reference/rpc/google.cloud.lifesciences.v2beta#disk).

Usage scenario

Job's that require a high input/output operations per second and lower latency (https://cloud.google.com/compute/docs/disks/local-ssd).

S

With future.batchtools and other wrappers, it become a bit tricky to track down where errors are coming from when running in batch mode. For instance, I got some:

Error : BatchtoolsError in BatchtoolsFuture ('future_lapply-1'): 'Work dir does not exist'

I wasn't sure if that was from the scheduler or batchtools, but it turns out it's from here:

https://github.com/mllg/batchtools/bl

Just like parallel::makePSOCKCluster() sets up a SOCKcluster object of SOCKnode workers, I think it would not be too complicated(*) to provide CMQcluster and CMQnode alternatives for clustermq.
For instance,

cl <- clustermq::makeClusterMCQ("sge")
y <- parallel::parLapply(1:10, FUN = sqrt)
parallel::stopCluster(cl)

(*) Roughly, S3 methods for generic functions such a

In order to help others understand how our package works, we have set goals for the way our package is organized, branded, documented, and produces output. This epic will hopefully bring some of those ideas together.

Add support for dl_poly users

therefore if the config hasn't changed, the job name should stay the same if cptools2 is run on the file again.

It has several similar (and apparently unused?) methods, maybe some of them could be removed.

For some methods it's not obvious how to implement them, so it would be nice if there was some documentation.