Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review README.rst #108

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Review README.rst #108

wants to merge 4 commits into from

Conversation

fangohr
Copy link
Owner

@fangohr fangohr commented Mar 20, 2024

  • triggered by update to Octoput 14.0
  • simplify where possible

fangohr and others added 4 commits March 20, 2024 15:06
- triggered by update to Octoput 14.0
- simplify where possible
remove duplicated top heading as well.
was markdown, should be rst.

Unrelated to this merge request (but reduces re-runs of actions).
@fangohr fangohr requested a review from iamashwin99 March 20, 2024 15:59
Copy link
Collaborator

@iamashwin99 iamashwin99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few suggestions, but looks good.
Could take a look at #109




Octopus in spack
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular reason for removing the title?
If you just clone the repo into a folder, a title in the Readme would quickly let you know what the project is about.

Comment on lines 11 to +13
Mostly aimed for maintainers of the Octopus package in spack: to test changes to
the `octopus/spack.py` file before request merges in spack upstream.
Spack's `package.py file <https://github.com/fangohr/octopus-in-spack/blob/main/spack/package.py>`_ for Octopus, before requesting merges
in `spack upstream <https://raw.githubusercontent.com/spack/spack/develop/var/spack/repos/builtin/packages/octopus/package.py>`_.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds duplicated. How about a reworded and more explanative sentence like

This repository is mostly aimed at testing new features and bug fixes to the octopus spack package.
The `package.py file <https://github.com/fangohr/octopus-in-spack/blob/main/spack/package.py>`_ in this repository is taken from the `spack upstream <https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/octopus/package.py>`_ ,  which defines the steps involved in setting up octopus and its dependencies. 

(points to the file on github instead of raw source)
Or something similar ( git hub doesn't allow adding code suggestions to lines that have been deleted)

README.rst Show resolved Hide resolved
@@ -50,15 +42,19 @@ want to include netcdf support:

- ``spack install octopus +netcdf``

Ideally, there are no errors. This should install Octopus 12.2
This should install the last Octopus release available in spack. (Use ``spack info octopus`` to see available versions.)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest sounds better than last ( as in there is no more octopus)

Suggested change
This should install the last Octopus release available in spack. (Use ``spack info octopus`` to see available versions.)
This should install the latest Octopus release available in spack. (Use ``spack info octopus`` to see available versions.)


There are further *variants* you can install. For example:

- ``spack install octopus +netcdf+parmetis+arpack+cgal+pfft+python+likwid+libyaml+elpa+nlopt``

To see an overview of available variants, use ``spack show octopus``.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wops, No idea how this typo was sustained. Thanks for the correction


Octopus in Docker container
===========================
3. Use octopus (it should be in the ``$PATH``). You can check the octopus version using ``octopus --version``.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"It should be in PATH" might make users think they have to do something.

Suggested change
3. Use octopus (it should be in the ``$PATH``). You can check the octopus version using ``octopus --version``.
3. Use octopus (it should have been added to ``$PATH`` by the previous, `load` command). You can check the octopus version using ``octopus --version``.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants