-
Notifications
You must be signed in to change notification settings - Fork 41
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
shmesa #558
shmesa #558
Conversation
Should we add the suggestion of editing |
docs/source/installation.rst
Outdated
@@ -108,6 +108,9 @@ uses export to set variables): | |||
export MESASDK_ROOT=/Applications/mesasdk | |||
source $MESASDK_ROOT/bin/mesasdk_init.sh | |||
|
|||
# add shmesa (the MESA command line tool) to your PATH | |||
PATH=$PATH:$MESA_DIR/scripts/shmesa |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we want an export
here to get the path update into the user's environment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought $PATH is exported by default (so doesn't need to be re-exported). Nevertheless I've added it as there's no harm.
scripts/shmesa/shmesa
Outdated
fi | ||
|
||
# Create a zip file containing only inlists and models | ||
zip -r "$zip_name" "$dir_to_zip" -i '*inlist*' '*.mod' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we include src/
directories here too so that run_star_extras
get bundled up too? And maybe some other files like *.list
and *.net
would be helpful as well?
In playing with this just now, I also noticed that make/run_star.mod
and make/run_star_extras.mod
got picked up by this, but the mod files are fortran objects that we don't want to share. Is there an easy way to exclude those?
some extra planned features, including some suggestions from the summer school participants:
additional todo:
|
I love the |
Command line utilities for MESA. See the README for usage.
As per the suggestion in the Discussion, it is now to be run as a standalone program rather than to be sourced. Therefore, recommended usage will be to add
PATH=$PATH:$MESA_DIR/scripts/shmesa
to your~/.bashrc
, and then you can callshmesa
from anywhere.