Skip to content

Commit

Permalink
Added Harshula's suggestions.
Browse files Browse the repository at this point in the history
  • Loading branch information
atteggiani committed Oct 13, 2024
1 parent cc82fe5 commit 260fa6d
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/models/run-a-model/build_a_model.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ spack env activate -p mom5_dev

## Compile Spack environment packages (optional)

It is recommended to first compile all the packages in the newly created _Spack_ environment as is without making any changes.
It is recommended to first compile all the packages in the newly created _Spack_ environment as is, without making any changes.

Compiling all the packages present in a _Spack_ environment is referred to as [installing the environment](https://spack.readthedocs.io/en/latest/environments.html#installing-an-environment).

Expand Down Expand Up @@ -504,11 +504,11 @@ spack install
The full output has been truncated for brevity.

!!! tip
From now on, the source code can be modified and the _Spack_ environment installed without repeating the concretization step.<br>
The _Spack_ environment will need to be re-concretized only if further changes occur in the `spack.yaml` file.
From now on, the source code can be modified and the _Spack_ environment installed without repeating the concretization step.<br>
The _Spack_ environment will need to be re-concretized only if further changes occur in the `spack.yaml` file.

## Output directory for compiled packages
For the Spack instance obtained through the [Spack setup instructions]({{spack_setup}}), all compiled packages will be placed in directories having the following format: `<install_tree.root>/{architecture}/{compiler.name}-{compiler.version}/{name}-{version}-{hash}`.
For the Spack instance obtained through the [Spack setup instructions]({{spack_setup}}), all compiled packages will be placed in directories having the following format: `<install_tree.root>/<architecture>/<compiler.name>-<compiler.version>/<name>-<version>-<hash>`.

`<install_tree.root>` depends on the [`install_tree.root`](https://spack.readthedocs.io/en/latest/config_yaml.html#install-tree-root) configuration field. _Spack_ reads this configuration field from files in several directories, following [Spack's configuration scopes](https://spack.readthedocs.io/en/latest/configuration.html#configuration-scopes).

Expand All @@ -524,7 +524,7 @@ config:
!!! tip
For the _Spack_ instance obtained through the [Spack setup instructions]({{spack_setup}}), `$spack` (referred to as `$(prefix)` in _Spack_ configuration scopes documentation above) corresponds to the `/g/data/$PROJECT/$USER/spack/0.22/spack` directory.

This means the packages built in this example can be found in `/g/data/$PROJECT/$USER/spack/0.22/spack/../restricted/ukmo/release/<architecture>/<compiler>/<package-name>`.
This means the packages built in this example can be found in `/g/data/$PROJECT/$USER/spack/0.22/spack/../restricted/ukmo/release/<architecture>/<compiler.name>-<compiler.version>/<name>-<version>-<hash>`.

## Troubleshooting build errors

Expand Down

0 comments on commit 260fa6d

Please sign in to comment.