User Tools

Site Tools


mesa

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
mesa [2025/04/30 11:01] – created jansenmesa [2025/04/30 11:37] (current) – [No setup needed, nor wanted!!] jansen
Line 33: Line 33:
 or in ''.tcshrc'': or in ''.tcshrc'':
   alias mesainit "module load mesa/r24.08.1"   alias mesainit "module load mesa/r24.08.1"
-For your personal MESA installes, the same method can be used, with the alias pointing to the ''source'' command needed to initialize the setup. As mentioned earlier, setting environment variables is safe to do, so that can be done here as well:+For your personal MESA installs, the same method can be used, with the alias pointing to the ''source'' command needed to initialize the setup. As mentioned earlier, setting environment variables is safe to do, so that can be done here as well:
 For users of the bash shell: For users of the bash shell:
-  export MESASDK_ROOT==/net/vdesk/data2/your_username/MESA/mesasdk+  export MESASDK_ROOT=/net/vdesk/data2/your_username/MESA/mesasdk
   export MESA_DIR=/net/vdesk/data2/your_username/MESA/mesa-r10398   export MESA_DIR=/net/vdesk/data2/your_username/MESA/mesa-r10398
   alias mesainit "source $MESASDK_ROOT/bin/mesasdk_init.sh"   alias mesainit "source $MESASDK_ROOT/bin/mesasdk_init.sh"
Line 45: Line 45:
 Of course, make sure you replace the path names from this example with the actual location where you have installed the software! Of course, make sure you replace the path names from this example with the actual location where you have installed the software!
  
-And, when editing session startup files like ''.bashrc'' or ''..tcshrc'', it is always a good idea to test them in your current session, before logging out to have them in effect for your next login. The reason is, that mstakes are easy to make, and many login environments are not very forgiving, ending the login eattempt with an error if there is an error in the startup files.  +And, when editing session startup files like ''.bashrc'' or ''.tcshrc'', it is always a good idea to test them in your current session, before logging out to have them in effect for your next login. The reason is, that mistakes are easy to make, and many login environments are not very forgiving, ending the login attempt with an error if there is an error in the startup files.  
-A simple way to test your setup is to run the shell from the commandline with the ''-l'' option to process login files: +A simple way to test your setup is to run the shell from the command line with the ''-l'' option to process login files: 
   ''tcsh -l''   ''tcsh -l''
 or or
   ''bash -l''   ''bash -l''
 Any errors will be displayed in your terminal, so you can fix them before they block you from further logins. Any errors will be displayed in your terminal, so you can fix them before they block you from further logins.
 +
 +Yet another methoud would be, to include the setenv (or export) commands and the source command into a small text file or script, and load that file when you want to activate the MESA environment, e.g create file ''mymesa'' containing:
 +  setenv MESASDK_ROOT /net/vdesk/data2/your_username/MESA/mesasdk
 +  setenv MESA_DIR /net/vdesk/data2/your_username/MESA/mesa-r10398
 +  source $MESASDK_ROOT/bin/mesasdk_init.csh
 +And when you want to active your MESA environment, type ''source mymesa''. Like the method with the ''alias'', this method makes sure the environment is only loaded when needed, so it will not interfere with normal logins or with other programs.
 +
  
 ====== Links ====== ====== Links ======
mesa.1746010908.txt.gz · Last modified: by jansen