Thanks for your reply, but that doesn't work for me.  All of my code is run 
from functions, and when I try 'using' inside a function, I get this:

ERROR: error compiling fitdata: error compiling fitdata: unsupported or 
misplaced expression "using" in function fitdata
 in demo at /home/dss/.julia/v0.4/DCEMRI/src/demo.jl:7
 in demo at /home/dss/.julia/v0.4/DCEMRI/src/demo.jl:2


On Friday, October 16, 2015 at 3:15:25 PM UTC-5, Christopher Fisher wrote:
>
> Hi David-
>
> I've been having similar difficulties. I do not know how to avoid 
> modifying LOAD_PATH, but last code I attached provides a working example: 
> https://groups.google.com/forum/#!searchin/julia-users/christopher$20fisher%7Csort:date/julia-users/jgT47LBBtWk/Caje1PhiAwAJ
>
> My best guess is that you are not doing this after initializing the procs:
>
> using MyModule
>
> @everywhere using MyModule
>
> It seems odd to call using twice but it seems to work. 
>
> Nonetheless, I also would be interested in alternative methods that do not 
> require modifying LOAD_PATH.
>
>
>
> On Friday, October 16, 2015 at 4:07:49 PM UTC-4, David Smith wrote:
>>
>> I'm also wondering how to replace 'require' without modifying the 
>> LOAD_PATH.  I can't expect my users to know how to make any path changes.
>>
>> 'using' and 'import' doesn't work for my parallel processes even though 
>> I'm loading a registered package ("DCEMRI").  I get this error.
>>
>> WARNING: Module DCEMRI not defined on process 2
>> fatal error on 2: ERROR: UndefVarError: DCEMRI not defined
>>
>>
>> I have just a small bit of code in a separate file in the DCEMRI package 
>> directory that I need each worker to load.  What is the preferred way to 
>> enable this in 0.4?
>>
>>
>> On Thursday, September 17, 2015 at 7:18:54 AM UTC-5, Christopher Fisher 
>> wrote:
>>>
>>> I am using .4.0-rc1 and have encountered a similar situation and have 
>>> fairly basic questions about the way .4 loads files. I normally use require 
>>> to load a file of functions from my working directory in to Julia on a 
>>> local computer or a cluster of computers. I was hoping someone would be 
>>> willing to answer a few related questions. 
>>>
>>> First, where can I find the .juliarc.jl file?
>>>
>>> Second, is there an easier way to load a .jl file from my working 
>>> directory into Julia onto a local computer or cluster of computers that 
>>> does not require editing the .juliarc.fil file? (Editing this file for 
>>> every project seems a little inconvenient). 
>>>
>>> Third, will the code loaded from a .jl  always be precompiled in .4? If 
>>> not, how do I choose whether it is precompiled or not?
>>>
>>> Thanks in advance (and my apologies for the basic questions;I'm not a 
>>> programmer per se)
>>>
>>> Chris 
>>>
>>> On Friday, July 31, 2015 at 7:30:44 AM UTC-4, Tim Holy wrote:
>>>>
>>>> If MyModule.jl is on your LOAD_PATH, 
>>>>
>>>>     @everywhere import MyModule 
>>>>
>>>> should work. You can add 
>>>>
>>>>     push!(LOAD_PATH,"/my/code/repository") 
>>>>
>>>> to your .juliarc.jl file. 
>>>>
>>>> This has been deprecated because of precompilation; it was felt that 
>>>> the 
>>>> string version left it too ambiguous about whether you wanted to load 
>>>> the raw 
>>>> file or the cached version. 
>>>>
>>>> Best, 
>>>> --Tim 
>>>>
>>>> On Thursday, July 23, 2015 11:58:58 AM Eduardo Lenz wrote: 
>>>> > Hi 
>>>> > I just downloaded the last nightly build  and I am receiving a new 
>>>> > deprecation message: 
>>>> > 
>>>> > Warning, "require" is deprecated, use "using" or "import" instead. 
>>>> > 
>>>> > My question is: I am using "require" due to the need to automatically 
>>>> > import these functions for all workers in a cluster. As long as I 
>>>> know, to 
>>>> > accomplish this task I have to use "require" and also provide the 
>>>> correct 
>>>> > path of the corresponding .jl files. How can I do this same thing 
>>>> using 
>>>> > "using" or "import" ? I tried to use it as I was using "require" and 
>>>> it is 
>>>> > not working as expected. 
>>>> > 
>>>> > Thanks for your help and sorry for the dumb question. 
>>>>
>>>>

Reply via email to