Hi Albert,
yes you can. That's exactly the function of the qfluka.sh template which I
mentioned.
f you click on the (i) icon in Flair you will open the manual and
searching for 'spawn' will result in a very clear self-explanatory picture:
clicking on the 'spawn' column on the side of the job will allow you to
enter the number of desired child jobs. Each will have its own
random seed.
The jobs are launched through a script and are left running in the system
also if you close flair. If you run a local job through Flair it will be
executed a separate process with *nohup* . Flair will store the
information about the job folder such that it can fetch the information
about the status of the job. In case the job folder is on remote machine
handled by you queuing/batch system you will not see any information about
the running jobs,
Jobs status can be controlled using the specific command of your
queuing/batch system.
In the same way from the manual you can access the information about how to
configure a custom queuing/batch system
Search for 'Preference' and select the 'F6.8 } Run' entry.
You can add a queue by right-clicking on the 'Queues/Submit' table. For
each queue you need to specify a name and a submission script, the template
of which you find in my previous email.
Different queuing system have different capabilities and feature therefore
it's really difficult to help you as you don't specify which batch system
you are using.
Best
Vittorio
On Fri, Apr 29, 2016 at 9:24 PM, Hanson, Albert L <alh_at_bnl.gov> wrote:
> Vittorio,
>
>
>
> Thanks for the speedy reply. I think you did not quite understand what we
> are puzzled with. We run FLUKA from FLAIR, but there are long runs that we
> need to do and do not want to do them interactively, so once everything is
> set up, we would like to submit a job to a batch queue. So the question is
> really, can we send a batch job directly from FLAIR? It would appear to be
> so looking at the CONFIG file, but we haven’t found the right combination
> of commands.
>
>
>
> Thanks again,
>
> Albert Hanson
>
>
>
> *From:* Vittorio Boccone [mailto:dr.vittorio.boccone_at_ieee.org]
> *Sent:* Friday, April 29, 2016 7:39 AM
> *To:* Hanson, Albert L
>
> *Subject:* Re: [fluka-discuss]: batching a run from FLAIR
>
>
>
> in the run left panel you can add new jobs (“+” button), then click on
> column right of the job name and add the number of desired job.
>
> The job will be spawned as requested and many sub-jobs will be created
> with {JOB_NAME}_XX where XX is aa, ab…. etc.
>
>
>
> Best
>
> Vittorio
>
>
>
> This is also explained in Flair’s manual.
>
> On 29 Apr 2016, at 13:35, Hanson, Albert L <alh_at_bnl.gov> wrote:
>
>
>
> Hi Vittorio,
>
>
>
> Thank you for this. I have been running in batch mode using rfluka. I
> was wondering how to spawn a batch process from within FLAIR. It seems
> like one can do it, but that is not obvious.
>
>
>
> Regards,
>
> Albert
>
>
>
> *From:* Dr. Vittorio Boccone [mailto:dr.vittorio.boccone_at_ieee.org
> <dr.vittorio.boccone_at_ieee.org>]
> *Sent:* Friday, April 29, 2016 1:32 AM
> *To:* Hanson, Albert L
> *Cc:* fluka-discuss_at_fluka.org
> *Subject:* Re: [fluka-discuss]: batching a run from FLAIR
>
>
>
> Dear Albert,
>
> a qfluka.sh script which provides a template job submission script for the
> PBS batching system, is included in the flair packages. You can also fetch
> it from the SVN repo directly.
>
> http://svnweb.cern.ch/world/wsvn/flair/trunk/flair/utils/qfluka.sh
>
>
>
> You can add a submission script to the already existing one (local
> execution), in the Flair preference panel.
>
>
>
> Best,
>
> Vittorio
>
> Sent from my iPad
>
>
> On 29 apr 2016, at 00:29, Hanson, Albert L <alh_at_bnl.gov> wrote:
>
> I am not quite understanding how to send a batch run from FLAIR, which is
> running on a cluster. Can anybody provide me with a set of commands that
> will work?
>
>
>
> Thanks,
>
> Albert Hanson
>
>
>
__________________________________________________________________________
You can manage unsubscription from this mailing list at
https://www.fluka.org/fluka.php?id=acc_info
Received on Sat Apr 30 2016 - 00:19:53 CEST