I/O on a cluster

Hi,

You can configure the file input/mg5_configuration.txt
and change the line

#! Path to a node directory to avoid direct writting on the central disk
#! Note that condor cluster avoid direct writting by default (therefore this
#! options didn't modify condor cluster)
# cluster_temp_path = None

to
#! Path to a node directory to avoid direct writting on the central disk
#! Note that condor cluster avoid direct writting by default (therefore this
#! options didn't modify condor cluster)
cluster_temp_path = /tmp

Cheers,

Olivier

On Sep 9, 2014, at 2:49 PM, Sean Wu <email address hidden> wrote:

> New question #254254 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/254254
>
> I've recently been talking with administrator of our cluster and he says there is an issue with the way our cluster is set up and the way I'm running MadGraph. Specifically he says that it does lots of tiny read and writes during the run and this is a problem for where it is that I am running. He says that this can be avoided if I do my runs in a /tmp folder and then transfer the files to the location I store them. Currently, I am just running out of a folder generated by madgraph using the ./generate_events command. Is there a simple way to redirect this run into another directory?
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.