Hello Nick Let me put some words.. (Hello ,Suzanne Panacek , I do not understand why this is not cleared in the ROOT manual..) I suggest the following way to run jobs (it is much faster) : 1) .L my_code.C++ 2) root -b -q my_code.so > my_code.log >Hi Prasad, >You can do > >root -b -q myTest.C >myTest.log > >from within a 'shell script' that you have submitted in batch >(e.g. via NQS or something similar). >The job will then run as a usual batch job and the produced >printout will be put in the file myTest.log. > > Cheers, > Nick. > > >"B.V.L.S.Prasad" wrote: > > Hi Rene, Masa and Others, > > I think my question is mis-INTERPRETED: as an example: > > as everybody knows, in a shell we can give a background job: > suppose say minimization problem, which takes days to come to a stop.. > (especially if its a simulated annealing method). > > >>@user>>mimimize < someinput.file >somelog.file & //'&' is for backgrounding > >>@user>>bla!bla //I can start doing some other work here without > // waiting for the minimization results... > > Now, my wish in CINT/ROOT:-- > > Root[0] .x myTest.C // this will execute the program/script and only > // then the prompt will be offered for the next command... > Root[1] > .......... Volodja Babintsev
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:43 MET