Right! I did think to look for a 'share this cluster' command, I just
failed to find it. It all makes sense now, thanks.
On Thu, Dec 1, 2011 at 7:34 PM, Enis Afgan wrote:
> Hi Clare,
> The share string is generated when you share a cluster. The string is
> accessible on the shared cluster, when y
Hi Clare,
The share string is generated when you share a cluster. The string is
accessible on the shared cluster, when you click the green 'Share a
cluster' icon next to the cluster name and then the top link "Shared
instances". You will get a list of the point in time shares of the cluster
you hav
Hi Enis, Jeremy, and all,
Thanks so much for all your help. I have another question which I
suspect is just me missing something obvious.
I'm guessing that when you cloned the cluster for your workshop, you
used CloudMan's 'share-an-instance' functionality?
When I launch a new cluster which I wan
Hi Clare,
I don't recall what instance type we used earlier, but I think an Extra
Large Instance is going to be fine. Do note that the master node is also
being used to run jobs. However, if it's loaded by just the web server, SGE
will typically just not schedule jobs to it.
As far as the core/thr
Hi Jeremy,
Also if you do remember what kind of Amazon node you used,
particularly for the cluster's master node (e.g. an 'xlarge' 4-core
15GB or perhaps one of the 'high-memory' nodes?), that would be a
reassuring sanity chech for me!
Cheers,
Clare
On Mon, Nov 21, 2011 at 10:37 AM, Clare Slogge
Hi Jeremy, Enis,
That makes sense. I know I can configure how many threads BWA uses in
its wrapper, with bwa -t. But, is there somewhere that I need to tell
Galaxy the corresponding information, ie that this command-line task
will make use of up to 4 cores?
Or, does this imply that there is alway
