cc_staff
156
edits
Materials Studio: Difference between revisions
→Team Installation
| Line 13: | Line 13: | ||
== Team Installation == | == Team Installation == | ||
If you are a PI holding the Materials Studio licence, you can install Materials Studio once so those working under you can use that installation. Since normally team work is stored in <code>/project</code> space, determine which project directory you want to use. Suppose it is <code>~/projects/A_DIRECTORY</code>, then you'll need to know these two values: | |||
# Determine the actual path of A_DIRECTORY as follows: {{Commands|PI_PROJECT_DIR{{=}}$(readlink -f ~/projects/A_DIRECTORY)|echo $PI_PROJECT_DIR}} | # Determine the actual path of A_DIRECTORY as follows: {{Commands|PI_PROJECT_DIR{{=}}$(readlink -f ~/projects/A_DIRECTORY)|echo $PI_PROJECT_DIR}} | ||
# Determine the group of A_DIRECTORY as follows: {{Commands|PI_GROUP{{=}}$(stat -c%G $PI_PROJECT_DIR)|echo $PI_GROUP}} | # Determine the group of A_DIRECTORY as follows: {{Commands|PI_GROUP{{=}}$(stat -c%G $PI_PROJECT_DIR)|echo $PI_GROUP}} | ||
With these values known, install Materials Studio as follows: | With these values known, install Materials Studio as follows: | ||
| Line 26: | Line 27: | ||
Before the software can be run, the following must be run first: | Before the software can be run, the following must be run first: | ||
# Change your default group to the team <code>def-</code> group, e.g., {{Command|newgrp $PI_GROUP}} | # Optional: Change your default group to the team <code>def-</code> group, e.g., {{Command|newgrp $PI_GROUP}} | ||
# Load the module information for the installed software, e.g., {{Command|module use $PI_PROJECT_DIR/MatStudio2018/modules/2017/Core/}} | # Load the module information for the installed software, e.g., {{Command|module use $PI_PROJECT_DIR/MatStudio2018/modules/2017/Core/}} | ||
#* Your team members may wish to add this to your <code>~/.bashrc</code> file. | #* Your team members may wish to add this to your <code>~/.bashrc</code> file. | ||