Re: [ncl-install] Moving NCL installation directory

Hi Helen,

It seems to be a Unix problem. The line that you showed refers to a symbolic
link, which is similar to the shortcuts in Windows systems. So, you can
execute your program "powerpc-apple-darwin6.8-g95" located in your bin
directory only calling it by "g95" in Linux/Unix terminals.

If you only copied this program to your bin directory, you can easily move
it to another directory and it would work without problem. Suppose that you
have moved your program to another directory, say "/MyProgs/bin". To update
the link in your bin directory you can type the command below from inside
your bin directory:

ln -s /MyProgs/bin/powerpc-apple-darwin6.8-g95 g95

Please, for more information about links in Unix/Linux systems take a look
at the website bellow
http://www.cyberciti.biz/tips/understanding-unixlinux-symbolic-soft-and-hard-links.html

However, if you have compiled and have installed your fortran 95 compiler in
your bin directory, please, talk to your system administrator to see how to
do what you want. Maybe you have to recompile it.

I hope it can help you.

Best regards,

Mateus

PS.: Helen, when replying this or other e-mails from NCL's list, please,
reply also to the list. By doing so, you can help others that have similar
problems.

2010/6/17 Helen Parish <hparish@ess.ucla.edu>

> Hi Mateus,
>
> You are right. Once I found a way to rename the disk, I managed to get ncl
> working on the new disk. It seems that the problem was in the spaces in the
> disk name.
>
> I do have another question. This may be more of Unix problem ?. I want to
> be able to use g95 on the new disk. However, after my original installation
> of g95, a subdirectory was set up in my home directory called /bin. Within
> /bin all there is is the following line:
>
> g95 -> /Users/helenparish/g95-install/bin/powerpc-apple-darwin6.8-g95
>
> I am not sure what this is - some kind of pointer perhaps ?. In any case it
> does not seem to be something I can edit.
> If I cannot alter this line, I think it means that I have to run g95 from
> my original home directory, which I would rather not do as it might still
> cause me some space issues.
>
> Do you know of any way to change the g95 -> to point to another directory
> (given that I will move /g95-install to the location of the new directory)
> ?.
>
> Thanks,
> Helen.
>
>
>
> On Jun 15, 2010, at 7:54 PM, Mateus Teixeira wrote:
>
> Hi Helen,
>
> I made some tests in my system changing the location of the ncl files. In
> the first test, I changed their location to the directory /ncarg and
> everything worked well, but it didn't work when I moved them to a directory
> which name had blank spaces.
>
> I created a directory /pc test/ncarg, but the ncl didn't work with
>
> setenv NCARG_ROOT /"pc test"/ncarg
>
> or
>
> setenv NCARG_ROOT /pc\ test/ncarg
>
> However, when I moved the files to the directory /ncarg, setting NCARG_ROOT
> as
>
> setenv NCARG_ROOT /ncarg
>
> NCL has worked.
>
> So, try to change the name of the directory where you are copying NCL
> files.
>
> I'm really not sure if linux accepts, in environmental variables, directory
> names with blank spaces, but here, in my system, they didn't work.
>
> I hope it helps you!
>
> Best regards,
>
> Mateus
>
>
> 2010/6/15 Helen Parish <hparish@ess.ucla.edu>
>
>> Hi Mateus,
>>
>> Sorry - I probably should not have mentioned the memory issues, which was
>> not my question.
>>
>> (I have always been running with the data and script files in another
>> directory as they are far too large to fit into my home directory !. When
>> one runs ncl in the home directory one can watch it use up space in the home
>> directory as it runs. It doesnt matter where the files and scripts are kept.
>> My system administrator confirmed a few days ago that the only thing I could
>> do to help was move ncl out of my home directory onto another disk).
>>
>> Please could you tell me what I need to do to allow me to run ncl from
>> another directory?.
>>
>> Thanks,
>> Helen.
>>
>>
>>
>> On Jun 15, 2010, at 7:12 AM, Mateus Teixeira wrote:
>>
>> Hi Helen,
>>
>> If I have understood correctly, you want to move to another directory
>> because of memory. I think that the memory that you refer is about disk
>> space. As soon as I know, the directory of the ncl files does not affect it.
>>
>> If you are experiencing problems with your disk space executing your
>> scripts in your home directory, try to move only your data and script files
>> to another directory, keeping the ncl files in the initial location, i.e.,
>> the locations in your old .cshrc.
>>
>> If you are experiencing problems with memory, I think that you should talk
>> with your system administrator, since the location of a program does not
>> interfere in the memory usage.
>>
>> I hope have helped you.
>>
>> Best regards,
>>
>> Mateus
>>
>>
>> 2010/6/15 Helen Parish <hparish@ess.ucla.edu>
>>
>>> Mateus,
>>>
>>> Here are the lines from the old .cshrc file which work:
>>>
>>> setenv NCARG_ROOT /Users/helenparish/nc
>>> set path=(/Users/helenparish/nc/bin $path)
>>> set path=(/Users/helenparish/bin $path)
>>>
>>> Here are the lines from the new .cshrc:
>>>
>>> setenv NCARG_ROOT /Volumes/"HP Mac Disk 2"/nc
>>> set path=(/Volumes/"HP Mac Disk 2"/nc/bin $path)
>>> set path=(/Volumes/"HP Mac Disk 2"/bin $path)
>>>
>>> Note that the directory /bin simply contains the following:
>>>
>>> g95 -> /Users/helenparish/g95-install/bin/powerpc-apple-darwin6.8-g95
>>>
>>> I was not sure exactly how to alter that line when moving directories,
>>> even though I had copied the
>>> g95 directory to the new disk (as well as leaving a copy in the old home
>>> directory) so I also tried the following:
>>>
>>> setenv NCARG_ROOT /Volumes/"HP Mac Disk 2"/nc
>>> set path=(/Volumes/"HP Mac Disk 2"/nc/bin $path)
>>> set path=(/Users/helenparish/bin $path)
>>>
>>> keeping the /bin in its original location.
>>>
>>> I need to move ncl so that it will run from another directory, because it
>>> does not have sufficient memory
>>> when running from the home directory (especially given the sizes of the
>>> files that i need to process using
>>> ncl). I am not sure what happens even if I am still attempting to run g95
>>> from the home directory given that I cannot
>>> alter the g95 -> statement above, or whether this matters in terms of how
>>> much memory is used in the home
>>> directory. I am not sure if this has anything to do with the reason that
>>> the ncl command is not understood though. The
>>> command ncl is not recognised as soon as I type it in.
>>>
>>> Any help would be appreciated.
>>>
>>> Thanks,
>>> Helen.
>>>
>>>
>>> On Jun 12, 2010, at 3:07 PM, Mateus Teixeira wrote:
>>>
>>> Helen,
>>>
>>> Can you provide the lines in both new and old .cshrc files?
>>>
>>> One alternative is to set NCARG_ROOT and PATH in the /etc/profile or
>>> other general configuration file available in your system. To avoid problems
>>> with different users I usually set these environmental variables in the
>>> /etc/profile of the system.
>>>
>>> Mateus
>>>
>>>
>>>
>>> 2010/6/12 Helen Parish <hparish@ess.ucla.edu>
>>>
>>>> I have been using NCL successfully for a while, with it installed in
>>>> my home (login) directory. I now want to be able to run the code from
>>>> another directory on the same computer.
>>>>
>>>> I have moved the /nc directory to the disk where I want to use the
>>>> code from. In my home directory I have changed the statements in
>>>> the .cshrc file beginning "setenv NCARG_ROOT" and "set path =" , to
>>>> contain the new directory paths.
>>>> However, the command "ncl" is no longer recognised. If I move the /nc
>>>> directory back to its original location and replace the new .cshrc
>>>> with the old one then ncl works again.
>>>>
>>>> Does anyone know if there is something else I need to do in order to
>>>> get ncl working from a new directory ?.
>>>>
>>>> Thanks,
>>>> Helen.
>>>> _______________________________________________
>>>> ncl-install mailing list
>>>> List instructions, subscriber options, unsubscribe:
>>>> http://mailman.ucar.edu/mailman/listinfo/ncl-install
>>>>
>>>
>>>
>>>
>>> --
>>> Mateus da Silva Teixeira
>>>
>>> Registered Linux User #466740 (http://counter.li.org/)
>>>
>>> --
>>> This message has been scanned for viruses and
>>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
>>> is
>>> believed to be clean.
>>>
>>>
>>>
>>
>>
>> --
>> Mateus da Silva Teixeira
>>
>> Registered Linux User #466740 (http://counter.li.org/)
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
>>
>> believed to be clean.
>>
>>
>>
>
>
> --
> Mateus da Silva Teixeira
>
> Registered Linux User #466740 (http://counter.li.org/)
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
>
>

-- 
Mateus da Silva Teixeira
Registered Linux User #466740 (http://counter.li.org/)

_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Thu Jun 17 06:26:04 2010