Difference between revisions of "MAS OS setup"

From MCEWiki
(Permissions and umask)
 
(97 intermediate revisions by 14 users not shown)
Line 1: Line 1:
= Install additional ubuntu packages =
+
{{Related|MAS}}
 +
= Supported operating systems =
  
== Disable CDROM seeking ==
+
We use Ubuntu.
  
The package manager knows that you have the Ubuntu disk and will say things like
+
* We only support LTS releases. Currently, we support:
  Media change: please insert the disc labeled
+
** 18.04
'Ubuntu-Server 6.06.1 _Dapper Drake_ - Release i386 (20060807.1)'
+
** 16.04
 +
** 14.04
  
To disable this (and download packages from the internet instead), open /etc/apt/sources.list
+
= Ubuntu 16.04 and later =
sudo gedit /etc/apt/sources.list
 
and remove (comment) the line
 
deb cdrom:[Ubuntu-Server 6.06.1 _Dapper Drake_ - Release i386 (20060807.1)]/ dapper main restricted
 
  
== Install required packages ==
+
The removal of the bigphysarea requirement from the kernel module means it's much easier to install MAS now.  Because you don't need to rebuild your kernel, it should be possible to simply checkout the MAS trunk.  Start by skipping down to the [[#Download (checkout) MAS and mce_script|Download (checkout) MAS and mce_script]] step, and then continue with installing MAS and MCE script.
  
sudo apt-get update
+
= Ubuntu 14.04 =
sudo apt-get install build-essential subversion emacs21 libreadline5-dev
 
  
== Try to install packages that don't work properly (impossible) ==
+
The automated installation package is tested, but as Ubuntu tweaks its packages the install script may fall slightly out of sync.  It's worth a shot though.
  
sudo apt-get install gnome-gv
+
After installing Ubuntu 14.04, get the install tarball:
  
== Install packages that you shouldn't even want to install (soon to be optional) ==
+
wget http://e-mode.phas.ubc.ca/mce/pc_install/install_tools/mce_install_ubuntu_14.04.tar.gz
  sudo apt-get install tcsh
+
  tar -xzf ubuntu_14.04_install.tar.gz
 +
cd install/
  
== Install desktop manager (optional) ==
+
== Install additional ubuntu packages ==
sudo apt-get install ubuntu-desktop gdm
 
  
= Download and install MAS kernel patch =
+
From that install folder, run
 +
bash install.bash
  
== Download ==
+
It can't hurt to run this a couple of times to make sure all dependencies are resolved.
  
If you're not compiling the kernel from scratch, download the binary packages from UBC:
+
== Bigphysarea kernel patch ==
wget http://e-mode.phas.ubc.ca/~mhasse/mce/kernel-headers-2.6.15.7-bigphys_10.00.Custom_i386.deb
 
wget http://e-mode.phas.ubc.ca/~mhasse/mce/kernel-image-2.6.15.7-bigphys_10.00.Custom_i386.deb
 
wget http://e-mode.phas.ubc.ca/~mhasse/mce/extras.patch
 
  
== Install ==
+
You can either download the compiled kernels or build them from scratch.
  
Then, install the packages using dpkg:
+
From install folder, run EITHER
  sudo dpkg -i kernel-headers-2.6.15.7-bigphys_10.00.Custom_i386.deb
+
  bash kernel_download.bash
  sudo dpkg -i kernel-image-2.6.15.7-bigphys_10.00.Custom_i386.deb
+
or
The "image" file might complain about symbolic links, no big deal.
+
  bash kernel_build.bash
  
== Patch ==
+
Compiled kernels currently exist for the x64 architecture.
  
This makes it possible to compile against the kernel package as though it had been locally compiled originally.
+
Then when one or the other of those has succeeded, install them:
cd /usr/src/kernel-headers-2.6.15.7-bigphys/
+
  bash kernel_install.bash
  sudo patch -p1 < ~/extras.patch
 
  
== Boot menu ==
+
You can now proceed to the section below titled "[[#Configure_the_system_for_MCE_users|Configure the system for MCE users]]".
  
Once you install the "image", the kernel should show up in the boot loader (grub)'s kernel list.  It's probably a good idea to test it first before setting it as the default kernel (see next step). Also *do not issue MCE or DSP commands until the acpi=off boot parameter has been configured!*
+
= Ubuntu 12.04 and earlier =
  
As root (or using sudo), edit the file /boot/grub/menu.lst . 
+
See [[MAS OS setup on obsolete systems]]
sudo gedit /boot/grub/menu.lst
 
Go to the list of kernels, below the line "## ## End Default Options ##", and find the kernel block with title "Ubuntu, kernel 2.6.15.7-bigphys".  It should be the third block in the list, i.e. index 2.  You must change the kernel line to turn "acpi=off".  Almost all systems crash hard if you don't do this.
 
kernel          /vmlinuz-2.6.15.7-bigphys root=/dev/sda3 ro quiet splash acpi=off bigphysarea=8192
 
  
Go back to the top of the file and set the value of the "default" option to 2 once you're ready to boot this kernel by default.
+
= Configure the system for MCE users =
default    2
 
  
= Configure the system for mce users =  
+
== Setup environment for MCE user ==
  
== Permissions and umask ==
+
We tend to assume that a single user and group will have dominion over the MCE software, scripts, and data.  We often assume that this user will be called "mce".  But it doesn't need to be.  Even if multiple users are running things through their own accounts it is likely useful to have a single group that can be used to manage access to the data.
  
 +
Anyway, to set up a reasonable MCE user, see [[MAS user setup]].
 +
 +
All users using the MCE will need to define some environment variables to use the scripts.  See the above link for lines to add to your '''.bashrc'''.
 +
 +
== System umask ==
 +
 +
You may want to set the system umask to make for a system where it's easier to share
 
Set the umask for all users to give write access for their group by default.
 
Set the umask for all users to give write access for their group by default.
  
Line 73: Line 71:
 
  UMASK          002
 
  UMASK          002
  
Any users wishing to use MCE under their own accounts should be added to the "mce" group and should have "mce" as their primary group.  Their umask must be set properly, or other users will not be free to manipulate shared files.
+
== Folders ==
  
== Folders ==
+
mce_script assumes that /data/cryo/ exists and can be manipulated.  To create something reasonable:
  
 +
MCE_USER=mce
 +
MCE_GROUP=mce
 
  sudo mkdir /data
 
  sudo mkdir /data
  sudo chown mce:mce /data
+
  sudo chown $MCE_USER:$MCE_GROUP /data
 
  sudo chmod g+ws /data
 
  sudo chmod g+ws /data
 
  mkdir /data/cryo/
 
  mkdir /data/cryo/
 
mkdir /home/mce/tmp
 
chmod g+ws /home/mce/tmp
 
  
Folder permissions are annoying.  Basically, any place you're going to be creating files has to have the g+s bit set.  svn folders are particularly bad...
 
  
  chmod g+ws /home/mce
+
= Download (checkout) MAS and mce_script =
  mkdir /home/mce/script
+
 
  chmod g+ws /home/mce/script
+
See [[MAS svn repository]].
  chmod g+ws /home
+
 
 +
= Compile and install MAS =
 +
 
 +
The following procedure outlines the default situation, where MAS is being installed on a computer containing only one fibre card. For information on running MAS with multiple fibre cards in one computer, see [[Multicard MAS]].
 +
 
 +
== Makefile.svn ==
 +
 
 +
MAS uses autoconf for some basic configuration stuff. After checking out MAS from the SVN repository the ''first'' time, you need to bootstrap the autoconf process.  To simplify this, the Makefile.svn file will automate the process.  From the MAS source folder run
 +
 
 +
  make -f Makefile.svn
 +
 
 +
If successful, this will create the "./configure" script.  This step is only required on fresh check-outs of the repository. If you already have a ./configure script, even if it's out of date, you can skip this step.  (After having been bootstrapped the
 +
first time, the build system is smart enough to know when it needs to regenerate itself.)
 +
 
 +
Note: this procedure requires autoconf. If it's not installed, install it with:
  
= Install external libraries =
+
  sudo apt-get install autoconf
  
MAS uses libconfig to manage its configuration files. The webpage is here: [ http://www.hyperrealm.com/libconfig/ ].  To install libconfig run the following:
+
== ./configure ==
  
  wget http://www.hyperrealm.com/libconfig/libconfig-1.2.1.tar.gz
+
Once the configure script exists, run it to generate the build system (ie. the Makefiles). The biggest thing you usually need to tell it is what the basic username and group should be for mce data. Also, there are a few options for the driver and some stupid python stuff.
  tar -xzf libconfig-1.2.1.tar.gz
 
  cd libconfig-1.2.1
 
  ./configure
 
  make
 
  sudo make install
 
  
To make the system aware of this library, add "/usr/local/lib" to /etc/ld.so.conf and run "sudo ldconfig".  i.e.
+
From the MAS source folder, run
  echo /usr/local/lib | sudo tee /etc/ld.so.conf
 
  sudo ldconfig
 
  
= If necessary, branch MAS and mce_script =
+
./configure
  
From a complete (or somewhat complete) mas source tree (i.e. the repository root) do:
+
Some useful options:
 +
  --disable-driver        suppress driver compilation/installation
 +
  --disable-bigphysarea  compile driver without bigphysarea support
 +
  --disable-config2      suppress mas.cfg and mce.cfg generation/installation
 +
  --enable-multicard      build a version of MAS which can drive multiple fibre cards.  (See [[Multicard MAS]] for specifics.)
 +
  --with-user=USER        set default MCE user
 +
  --with-group=GROUP      set default MCE group
 +
  --with-kernel-dir=DIR  set kernel build directory (typically automatically determined)
  
  svn copy trunk branch/new_project
+
Run
  svn commit branch/new_project
 
  
Then check out the appropriate branch (or the whole tree) on the new machine.
+
./configure --help
  
= Download (checkout) MAS and mce_script =
+
for a full list.  When running, configure will complain if it cannot find something, and even suggest what package you need to install.
  
See the page on [[ MAS svn repository ]]
+
== mce.cfg ==
  
= Compile and install MAS =
+
After running configure, but before running make, you must specify a template file (mce.cin) which will be used to generate  the hardware configuration file (mce.cfg).  Full details of this procedure are given in the [[mce.cfg]] page, but briefly:
  
== Build the driver ==
+
# copy an appropriate template from <code>config2/templates</code> to <code>config2/mce.cin</code>
 +
# edit the <code>config2/mce.cin</code> file to describe your MCE.
  
By default, the driver will build with bigphysarea support enabledTo override build options, create a file Makefile.local in the "driver" folder, and add lines like
+
The configuration file will be installed automatically when <code>make install</code> is run belowThis entire step can be skipped if you passed --disable-config2 to configure above, but note that MAS will not function without mce.cfg and mas.cfg installed.
  
BIGPHYS = 1    # use bigphysarea for frame buffering
+
== make ==
or
 
FAKEMCE = 1    # enable software MCE emulator in driver
 
or
 
REALTIME = 1  # use rtai interrupt handling
 
  
On a real system, just leave Makefile.local empty.
+
This often works.
  
Anyway, once Makefile.local is setup, type
 
cd mas
 
 
  make clean; make
 
  make clean; make
  
From the driver folder we can test the driver:
+
=== Troubleshooting ===
 +
Sometimes after doing an SVN update <code>make</code> doesn't work but instead returns the cryptic message:
 +
 
 +
*** No rule to make target `defaults/masdefault.m4', needed by `aclocal.m4'.
 +
 
 +
In this case, it's necessary to force a rebuild of the build system manually by running
 +
 
 +
make -f Makefile.svn
 +
./configure
 +
 
 +
See the [[#Makefile.svn|Makefile.svn section]] above for further details.
 +
 
 +
== Test the driver ==
 +
 
 +
It is wise to test that the driver does not kill your machine before installing it to load on boot.  After compiling do:
 +
 
 
  cd driver
 
  cd driver
  ./reload
+
  sudo ./reload
./mknodes
 
  
Note that since "reload" first unloads the driver if it is present, and then loads the driver from the current folder, it may report an "ERROR" message if the first step fails, even though the driver is successfully loaded.  The definitive way to check that the driver is loaded is
+
This will load the driver, which should then try to talk to the SDSU PCI card if it is installed.  Note that since "reload" first unloads the driver if it is present, and then loads the driver from the current folder, it may report an "ERROR" message if the first step fails, even though the driver is successfully loaded.  The definitive way to check that the driver is loaded is
   cat /proc/mce_dsp
+
   cat [[/proc/mce_dsp]]
  
 
If this file does not exist, the driver isn't loaded.  If the cat prints out a bunch of low-level driver information, you're in good shape.
 
If this file does not exist, the driver isn't loaded.  If the cat prints out a bunch of low-level driver information, you're in good shape.
  
If you're satisfied that the driver works, install the driver with the command
+
== sudo make install ==
 +
 
 +
If you're satisfied that the driver works, install the whole thing.  Go back up to the MAS base folder and run
  
 
  sudo make install
 
  sudo make install
  
This should put mce_dsp.ko into /lib/modules/2.6.15.7-bigphys/kernel/drivers/misc/, and re-scan the module dependencies.  To get the driver to load on boot you must add manually the following lines to /etc/rc.local:
+
This will do the following:
  
modprobe mce_dsp
+
*install the kernel driver, <code>driver/mce_dsp.ko</code>, into <code>/lib/modules/$(uname -r)/kernel/drivers/misc/</code>, and re-scan the module dependencies.
/home/mce/mas/driver/mknodes
+
*install the MAS binaries from <code>applications/</code> and the scripts from <code>script/</code> into <code>/usr/mce/bin</code>
sudo -u mce /usr/mce/bin/maslog_server
+
*install the MAS udev ruleset <code>scripts/91-mas.rules</code> into <code>/etc/udev/rules.d/</code>.  These udev rules will ensure that the mce_dsp module is loaded and the MAS device nodes are created at boot time.  You can get udev to run these rules immediately, which will result in /dev being populated with the mce devices, by running:
  
== Install MAS binaries ==
+
  sudo udevadm trigger
  
To install the mas binaries, go to the top level mas folder and do a make:
+
:or, else, you can make the nodes yourself by running mas_mknodes.
 +
*install the mas logging daemon script <code>/etc/init.d/mas</code> init script.  The driver can then be started/restarted as desired through this script:
  
  cd /home/mce/mas
+
  /etc/init.d/mas restart
make clean ; make
 
sudo make install
 
  
 +
:The driver will automatically be set to load on boot.  To disable this, remove the symbolic link "/etc/rc2.d/S99mas".
 +
*install the hardware configuration file, <code>config2/mce.cfg</code>, and the MAS configuration file, <code>config2/mas.cfg</code> to <code>/etc/mce/</code>, assuming there aren't versions already there.
  
== Install MAS config files ==
+
= Install mce_script =
  
  sudo mkdir /etc/mce
+
Users have the option of running the MCE scripts from an svn working copy, or of running the MCE scripts from an "installed" copy. Talk to your MAS technician about which option is best for you.
sudo chown root:mce /etc/mce
 
sudo chmod g+ws /etc/mce
 
  
Make sure you use the hardware config (mce_*.cfg) file appropriate for your system.  Racks with 4 readout cards should use mce_v1.cfg; small sub-racks with readout card slots should use mce_v2.cfg. 
+
== Running from an svn working copy ==
  
cd ~/src/mas/config
+
Checkout the tree directly into /usr/mce:
cp mce_v1.cfg /etc/mce/mce.cfg
 
cp mas.cfg /etc/mce/mas.cfg
 
  
= Install mce_script =
+
cd /usr/mce
 +
svn checkout svn://e-mode.phas.ubc.ca/mce_script/trunk mce_script
  
The mce_script files are designed so that users can fairly easily run a different set of scripts.  We will install a system default set in /usr/mce/mce_script.
+
== Running from an installed copy ==
  
cd /usr/mce
+
Checkout the tree into your code folder; then make and install:
svn checkout svn://e-mode.phas.ubc.ca/mce_script/branch/{experiment} mce_script
 
  
== mas_env.bash ==
+
cd code
 +
svn checkout svn://e-mode.phas.ubc.ca/mce_script/trunk mce_script
 +
make
 +
sudo make install
  
To set up the environment and path to use these scripts and idl codes, a user should do "source mas_env.bash".  (This file used to live in mas/config, but has been moved into mce_script/template.)  Non-developer users can source /usr/mce/mce_script/template/mas_env.bash directly; advanced users may want to keep their own copy (or several different copies) in their home folder.
 
 
Note that MAS/mce_script scripts should *not* source mas_env.bash!  The whole point of it is that paths should be flexible.
 
  
 
== .bashrc ==
 
== .bashrc ==
  
To have bash start up with the MAS variables defined, and the paths ready, add the following lines to .bashrc :
+
Add a few lines to .bashrc to update your PATH, PYTHONPATH, and to define the MAS_* variables.  The new way, using [[mas_var]], is:
 +
eval `/usr/mce/bin/mas_var -e -s`
  
 +
The old way, which will probably still work for a while:
 +
 
  export MAS_ROOT=/usr/mce/mce_script/
 
  export MAS_ROOT=/usr/mce/mce_script/
 
  source $MAS_ROOT/template/mas_env.bash
 
  source $MAS_ROOT/template/mas_env.bash
  IDL_PATH="<IDL_DEFAULT>:$MAS_IDL/mas"
+
  export IDL_PATH="<IDL_DEFAULT>:$MAS_IDL/mas"
 +
 
 +
== Configuration data ==
 +
 
 +
Example configuration files (especially [[experiment.cfg]]) are kept in mce_script/template.  MAS, by default, expects user configuration data to be in /usr/mce/config.  Users should copy the template/ files to /usr/mce/config/, and then make configuration adjustments.  After install mce_script, you can copy the template config from it with:
 +
 
 +
sudo cp -r /usr/mce/mce_script/template /usr/mce/config
 +
sudo chown -R mce /usr/mce/config
  
While you're in there, you may want to define a few aliases.  In particular, I always uncomment the alias ll='ls-l' line.
+
[[Category:MAS]]

Latest revision as of 15:05, 26 September 2019

Related topics:

Supported operating systems

We use Ubuntu.

  • We only support LTS releases. Currently, we support:
    • 18.04
    • 16.04
    • 14.04

Ubuntu 16.04 and later

The removal of the bigphysarea requirement from the kernel module means it's much easier to install MAS now. Because you don't need to rebuild your kernel, it should be possible to simply checkout the MAS trunk. Start by skipping down to the Download (checkout) MAS and mce_script step, and then continue with installing MAS and MCE script.

Ubuntu 14.04

The automated installation package is tested, but as Ubuntu tweaks its packages the install script may fall slightly out of sync. It's worth a shot though.

After installing Ubuntu 14.04, get the install tarball:

wget http://e-mode.phas.ubc.ca/mce/pc_install/install_tools/mce_install_ubuntu_14.04.tar.gz
tar -xzf ubuntu_14.04_install.tar.gz
cd install/

Install additional ubuntu packages

From that install folder, run

bash install.bash

It can't hurt to run this a couple of times to make sure all dependencies are resolved.

Bigphysarea kernel patch

You can either download the compiled kernels or build them from scratch.

From install folder, run EITHER

bash kernel_download.bash

or

bash kernel_build.bash

Compiled kernels currently exist for the x64 architecture.

Then when one or the other of those has succeeded, install them:

bash kernel_install.bash

You can now proceed to the section below titled "Configure the system for MCE users".

Ubuntu 12.04 and earlier

See MAS OS setup on obsolete systems

Configure the system for MCE users

Setup environment for MCE user

We tend to assume that a single user and group will have dominion over the MCE software, scripts, and data. We often assume that this user will be called "mce". But it doesn't need to be. Even if multiple users are running things through their own accounts it is likely useful to have a single group that can be used to manage access to the data.

Anyway, to set up a reasonable MCE user, see MAS user setup.

All users using the MCE will need to define some environment variables to use the scripts. See the above link for lines to add to your .bashrc.

System umask

You may want to set the system umask to make for a system where it's easier to share Set the umask for all users to give write access for their group by default.

Edit /etc/profile and change the "umask 022" line to

umask 002

Edit /etc/login.defs and find the line that start "# UMASK" and change it to

UMASK           002

Folders

mce_script assumes that /data/cryo/ exists and can be manipulated. To create something reasonable:

MCE_USER=mce
MCE_GROUP=mce
sudo mkdir /data
sudo chown $MCE_USER:$MCE_GROUP /data
sudo chmod g+ws /data
mkdir /data/cryo/


Download (checkout) MAS and mce_script

See MAS svn repository.

Compile and install MAS

The following procedure outlines the default situation, where MAS is being installed on a computer containing only one fibre card. For information on running MAS with multiple fibre cards in one computer, see Multicard MAS.

Makefile.svn

MAS uses autoconf for some basic configuration stuff. After checking out MAS from the SVN repository the first time, you need to bootstrap the autoconf process. To simplify this, the Makefile.svn file will automate the process. From the MAS source folder run

 make -f Makefile.svn

If successful, this will create the "./configure" script. This step is only required on fresh check-outs of the repository. If you already have a ./configure script, even if it's out of date, you can skip this step. (After having been bootstrapped the first time, the build system is smart enough to know when it needs to regenerate itself.)

Note: this procedure requires autoconf. If it's not installed, install it with:

 sudo apt-get install autoconf

./configure

Once the configure script exists, run it to generate the build system (ie. the Makefiles). The biggest thing you usually need to tell it is what the basic username and group should be for mce data. Also, there are a few options for the driver and some stupid python stuff.

From the MAS source folder, run

./configure

Some useful options:

 --disable-driver        suppress driver compilation/installation
 --disable-bigphysarea   compile driver without bigphysarea support
 --disable-config2       suppress mas.cfg and mce.cfg generation/installation
 --enable-multicard      build a version of MAS which can drive multiple fibre cards.  (See Multicard MAS for specifics.)
 --with-user=USER        set default MCE user
 --with-group=GROUP      set default MCE group
 --with-kernel-dir=DIR   set kernel build directory (typically automatically determined)

Run

./configure --help

for a full list. When running, configure will complain if it cannot find something, and even suggest what package you need to install.

mce.cfg

After running configure, but before running make, you must specify a template file (mce.cin) which will be used to generate the hardware configuration file (mce.cfg). Full details of this procedure are given in the mce.cfg page, but briefly:

  1. copy an appropriate template from config2/templates to config2/mce.cin
  2. edit the config2/mce.cin file to describe your MCE.

The configuration file will be installed automatically when make install is run below. This entire step can be skipped if you passed --disable-config2 to configure above, but note that MAS will not function without mce.cfg and mas.cfg installed.

make

This often works.

make clean; make

Troubleshooting

Sometimes after doing an SVN update make doesn't work but instead returns the cryptic message:

*** No rule to make target `defaults/masdefault.m4', needed by `aclocal.m4'.

In this case, it's necessary to force a rebuild of the build system manually by running

make -f Makefile.svn
./configure

See the Makefile.svn section above for further details.

Test the driver

It is wise to test that the driver does not kill your machine before installing it to load on boot. After compiling do:

cd driver
sudo ./reload

This will load the driver, which should then try to talk to the SDSU PCI card if it is installed. Note that since "reload" first unloads the driver if it is present, and then loads the driver from the current folder, it may report an "ERROR" message if the first step fails, even though the driver is successfully loaded. The definitive way to check that the driver is loaded is

 cat /proc/mce_dsp

If this file does not exist, the driver isn't loaded. If the cat prints out a bunch of low-level driver information, you're in good shape.

sudo make install

If you're satisfied that the driver works, install the whole thing. Go back up to the MAS base folder and run

sudo make install

This will do the following:

  • install the kernel driver, driver/mce_dsp.ko, into /lib/modules/$(uname -r)/kernel/drivers/misc/, and re-scan the module dependencies.
  • install the MAS binaries from applications/ and the scripts from script/ into /usr/mce/bin
  • install the MAS udev ruleset scripts/91-mas.rules into /etc/udev/rules.d/. These udev rules will ensure that the mce_dsp module is loaded and the MAS device nodes are created at boot time. You can get udev to run these rules immediately, which will result in /dev being populated with the mce devices, by running:
 sudo udevadm trigger
or, else, you can make the nodes yourself by running mas_mknodes.
  • install the mas logging daemon script /etc/init.d/mas init script. The driver can then be started/restarted as desired through this script:
/etc/init.d/mas restart
The driver will automatically be set to load on boot. To disable this, remove the symbolic link "/etc/rc2.d/S99mas".
  • install the hardware configuration file, config2/mce.cfg, and the MAS configuration file, config2/mas.cfg to /etc/mce/, assuming there aren't versions already there.

Install mce_script

Users have the option of running the MCE scripts from an svn working copy, or of running the MCE scripts from an "installed" copy. Talk to your MAS technician about which option is best for you.

Running from an svn working copy

Checkout the tree directly into /usr/mce:

cd /usr/mce
svn checkout svn://e-mode.phas.ubc.ca/mce_script/trunk mce_script

Running from an installed copy

Checkout the tree into your code folder; then make and install:

cd code
svn checkout svn://e-mode.phas.ubc.ca/mce_script/trunk mce_script
make
sudo make install


.bashrc

Add a few lines to .bashrc to update your PATH, PYTHONPATH, and to define the MAS_* variables. The new way, using mas_var, is:

eval `/usr/mce/bin/mas_var -e -s`

The old way, which will probably still work for a while:

export MAS_ROOT=/usr/mce/mce_script/
source $MAS_ROOT/template/mas_env.bash
export IDL_PATH="<IDL_DEFAULT>:$MAS_IDL/mas"

Configuration data

Example configuration files (especially experiment.cfg) are kept in mce_script/template. MAS, by default, expects user configuration data to be in /usr/mce/config. Users should copy the template/ files to /usr/mce/config/, and then make configuration adjustments. After install mce_script, you can copy the template config from it with:

sudo cp -r /usr/mce/mce_script/template /usr/mce/config
sudo chown -R mce /usr/mce/config