Closed alexkrohn closed 5 months ago
Hey Alex,
Ok, this is a bit weird and isn't documented very well, but the --ipcluster
argument for tetrad doesn't actually accept an input value, it is hard coded to use the 'default' instance of ipcluster, so any values passed in with --ipcluster
are ignored. The preferred way to operate this is like this:
# No --cluster-id, uses 'default' ipcluster ID
ipcluster start -n 30 --daemonize
# No arguments for --ipcluster flag are necessary
tetrad -i no-low-loci-inds-or-cinereus.snps.hdf5 -b 1000 -n 5maxmissing-allinds -o tetrad-out --ipcluster
Hope that helps! -isaac
Ah, that works. Thanks for clarifying!
Running tetrad 0.9.14 downloaded from github
That outputs a lot of information, ending in:
Then when running tetrad, I get this error:
Confirming that the cluster did initiate:
This command got tetrad to work with 30 cores as expected:
Probably not super dire behavior, but I wasn't quite sure why it was failing.