Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Fix 1 or 2 typos, and clarify the installation options.
  • Loading branch information
TomLav authored May 11, 2021
1 parent da66475 commit 156411d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,19 +25,19 @@ Oslo (cmcrameri)

There are two ways for getting `ncview` to use the scientific colormaps:

*Option 1: (easiest)*
*Option 1: (recommended, easiest)*
1. Fetch this repo from github;
2. Define (export) a shell environment variable to the sub-directory `ncmaps/`: `export NCVIEWBASE=</path/to/local/ncmaps/copy>/ncmaps/`.
2. Copy `ncmaps/.ncviewrc` to your HOME: `cp </path/to/local/ncmaps/copy>/ncmaps/.ncviewrc ${HOME}`.
3. Copy `ncmaps/.ncviewrc` to your HOME: `cp </path/to/local/ncmaps/copy>/ncmaps/.ncviewrc ${HOME}`.

For example: `export NCVIEWBASE=/home/tomlav/software/ncmaps/ncmaps/` (note `ncmaps` twice) and `cp /home/tomlav/software/ncmaps/ncmaps/.ncviewrc /home/tomlav/`.
You should add the export to your `.profile`.

*Option 2: (requires python3)*
*Option 2: (for developers)*
1. Fetch this repo from github;
2. Run `python3 write_ncmaps` in the terminal;
3. Define (export) a shell environment variable: `export NCVIEWBASE=${HOME}/.ncmaps`;
2. Copy `${HOME}/.ncmaps/.ncviewrc` to your HOME: `cp ${HOME}/.ncmaps/.ncviewrc ${HOME}/`.
4. Copy `${HOME}/.ncmaps/.ncviewrc` to your HOME: `cp ${HOME}/.ncmaps/.ncviewrc ${HOME}/`.

Here again, you should put the `export` command in your `.profile`.

Expand Down

0 comments on commit 156411d

Please # to comment.