Re: [ferret_users] GO files don't work from any directory

The Ferret/PyFerret environment variables are assigned in the miniconda install of PyFerret when you issue the command 'conda activate <PyFerretEnvName>' (where <PyFerretEnvName> is whatever environment name you installed PyFerret in). The values of these environment variables are assigned by the scripts under ..../minconda3/envs/<PyFerretEnvName>/etc/conda/activate.d/ (where ...../miniconda3/ is the installation directory of miniconda, and <PyFerretEnvName> is as mentioned previously). There is pyferret-activate.sh for Bourne-type shells (such as bash) and pyferret-activate.csh for C-type shells (such as tcsh). If you wish you could add any custom directories to the definitions of FER_DATA, FER_DESCR, FER_GRIDS, and/or FER_GO given in these files.

Kind regards,

Karl

On Thu, Mar 5, 2020 at 2:54 AM Olivier Marti <olivier.marti@xxxxxxxxxxxx> wrote:

Find the file <your anaconda root path>/envs/cdat81//bin/ferret_paths_template.sh , adapt it to your system, and source it before using pyferret

Olivier

Le 5 mars 2020 à 10:53, 'Manola, I.' via _OAR PMEL Ferret Users <ferret_users@xxxxxxxx> a écrit :

Hello ferret people,

I have just installed PyFerret on my Mac computer in order to carry on working in Ferret like used to in my good old Linux system.

My issue is that now some GO files do not work unless if I am in the exact directory where they are downloaded. For example, if I do from any directory:

yes? go land 0

**TMAP ERR: non-existent or not on line

Searched $FER_DESCR and $FER_DATA for geo_borders(.nc ,.cdf,.des,.agg)

SET DAT/FORM=CDF geo_borders

Command file, command group, or REPEAT execution aborted

While the geo_borders.cdf file exists and works well in my PyFerret/FerretDatasets-master/data/ directory.

Could you please tell me how could I make ferret see those files from any directory?

Thanks,

Iris

—
Olivier Marti - LSCE Bât 714 p. 1049
MERMAID Team
Tel : +33 1 69 08 77 27 / +33 6 45 36 43