You can always fetch it from the master process. @everywhere println(remotecall_fetch(1, ()->ARGS))
On Thu, Sep 4, 2014 at 8:38 AM, Thomas Covert <thom.cov...@gmail.com> wrote: > that also doesn't work. here is the output: > > UTF8String[ From worker 2: UTF8String["--worker","--bind-to","10.0.0.6"] > > "1","2","3"] > > From worker 3: UTF8String["--worker","--bind-to","10.0.0.6"] > > On Wednesday, September 3, 2014 9:59:30 PM UTC-5, Isaiah wrote: > >> The ARGS you see there are what is passed to each worker on startup. Try >> something like: >> >> @everywhere myargs = ARGS >> @everywhere println(myargs) >> >> >> On Wed, Sep 3, 2014 at 10:33 PM, Thomas Covert <thom....@gmail.com> >> wrote: >> >>> Is it possible to retrieve the contents of command line arguments in >>> parallel processing mode? I'm having trouble making it work. For example, >>> if the file temp.jl contains: >>> >>> addprocs(2) >>> @everywhere println(ARGS) >>> >>> Then when I type >>> >>> bash$ julia temp.jl 1 2 3 >>> >>> I get: >>> >>> UTF8String["1","2","3"] >>> From worker 2: UTF8String["--worker","--bind-to","10.0.0.6"] >>> From worker 3: UTF8String["--worker","--bind-to","10.0.0.6"] >>> >>> Whereas I would have expected it to give me: >>> UTF8String["1","2","3"] >>> From worker 2: UTF8String["1","2","3"] >>> From worker 3: UTF8String["1","2","3"] >>> >>> Is @everywhere not the way to do this? >>> >>> -thom >>> >>> >>
