-
Notifications
You must be signed in to change notification settings - Fork 1
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
A little more installation hand holding #2
Comments
Dear Robert,
Thanks for your input. To clarify:
- The linux username in the example is `suntans`
- The name of this github tutorial is `suntans_tutorial`
- The name of the ocean model we are running is `suntans`
In hindsight I can see that this is confusing. I will update the README
instruction to make this clearer, and amend the other path issues you
mentioned above.
Matt
…On Thu, Apr 15, 2021 at 4:26 PM iosonobert ***@***.***> wrote:
Hello Professor Matt R.P. Rayson,
I was following your install instructions and I have a couple of thoughts
for changes to your readme. The instructions are fine, so this is not an
issue as such, just a couple of things that I wish I knew at the time.
1.
With the ParMetis install it could be good to advise changing (cd)
into a sensible directory before calling wget. I ended up putting mine in a
rather silly location. This will also help finding ParMetis again when
modifying Makefile.in.
2.
I now see that the variables MPIHOME and NETCDF4HOME know the relative
path from /usr. Really these variables are not so much asking for the
MPIHOME/NETCDF4HOME as much as they are the /usr folder [assuming this is
where aptget puts everything]. While your instructions are correct, this
was not clear to me at the time, so I was going into /usr to find the
actual libraries - similar to what you would do for the PYTHONEXEC variable
in the example shell scripts. A note on this would be great.
3.
It probably shouldn't have, but it took me a moment to realise that
your linux user is called suntans. Seeing suntans in the ParMetis path
threw me a bit.
Kind regards,
Andrew
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC73RFCS7YWUYBBNVTUH3CDTI2PKDANCNFSM4267GS2Q>
.
--
Matt Rayson
*Research Fellow*
*Australian Research Council Industrial Transformation Research Hub for
Offshore Floating Facilities*
*Oceans Graduate School and the UWA Oceans Institute*
*University of Western Australia*
*Ph: +61 8 6488 3083*
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello Professor Matt R.P. Rayson,
I was following your install instructions and I have a couple of thoughts for changes to your readme. The instructions are fine, so this is not an issue as such, just a couple of things that I wish I knew at the time.
With the ParMetis install it could be good to advise changing (cd) into a sensible directory before calling wget. I ended up putting mine in a rather silly location. This will also help finding ParMetis again when modifying Makefile.in.
I now see that the variables MPIHOME and NETCDF4HOME know the relative path from /usr. Really these variables are not so much asking for the MPIHOME/NETCDF4HOME as much as they are the /usr folder [assuming this is where aptget puts everything]. While your instructions are correct, this was not clear to me at the time, so I was going into /usr to find the actual libraries - similar to what you would do for the PYTHONEXEC variable in the example shell scripts. A note on this would be great.
It probably shouldn't have, but it took me a moment to realise that your linux user is called suntans. Seeing suntans in the ParMetis path threw me a bit.
Kind regards,
Andrew
The text was updated successfully, but these errors were encountered: