Hi Matthieu,
about the packages/installation procedure, Stephen has the list already,
anyway here it is again for the record.

Cheers
Fabio

sudo pip install zeroc-ice==3.6.3

sudo su
yum install qt-devel PyQt gmp-devel pyfits qt3-config kdelibs3-devel libXpm-devel cfitsio-devel lrzsz
yum install gcc-c++ subversion boost-devel ncurses-devel python-devel readline-devel armadillo-devel mysql++-devel openmotif-devel xterm
yum install bzip2-devel

wget https://pypi.python.org/packages/source/s/setuptools/setuptools-0.7.2.tar.gz --no-check-certificate
tar xf setuptools-0.7.2.tar.gz
cd setuptools-0.7.2
python setup.py install

yum install --downloadonly python-pip
rpm --nodeps -ivh /var/cache/yum/x86_64/6/epel/packages/python-pip-7.1.0-1.el6.noarch.rpm

cd /etc/yum.repos.d
wget https://zeroc.com/download/Ice/3.6/el6/zeroc-ice3.6.repo
yum install ice-all-runtime ice-all-devel
ln -s /usr/share/Ice-3.6.4 /usr/share/Ice

pip install zeroc-ice==3.6.4
echo /usr/local/qwt-5.1.2/lib > /etc/ld.so.conf.d/qwt.conf
echo /usr/local/exelisvis/idl71/bin/bin.linux.x86_64 > /etc/ld.so.conf.d/idl.conf
yum install tkinter
yum install tk-devel

# in the home directory of the user create the file .config/matplotlib/matplotlibrc containing backend: TkAgg
exit
printf "backend: TkAgg\n" > ~/.config/matplotlib/matplotlibrc
sudo su

pip install --upgrade numpy==1.8.1
pip install pillow==1.0.0
pip install scipy==0.17.1
pip install matplotlib==1.4.3
pip install scikit-learn==0.18.1
pip install scikit-image==0.10.1
pip install astropy==1.1
pip install pyfits
/sbin/ldconfig -v

mkdir /local
mkdir /local/aolog

mkdir /local/aomeas
chown AOeng /local/aolog

chown AOeng /local/aomeas

exit from root
# exit and be logged as normal user

svn checkout " https://svn.lbto.org/repos/aosupervisor/branches/SOUL "
cd SOUL/
python prepare.py make
source flao_environment.sh
cd $ADOPT_SOURCE/contrib
make
sudo make install
cd $ADOPT_SOURCE
make
make install
# Manual installation of the calibration


# Install Vimba
# 1. Download Vimba_v2.1.3_Linux.tgz from
tar -xzf ./Vimba.tgz -C /opt
cd [InstallDir]/Vimba_x_x/VimbaGigETL
sudo ./Install.sh
# Log off and log on again

# Install Pymba
# 1. Download a zip containing the package from https://github.com/morefigs/pymba
unzip pymba-master.zip
cd pymba-master
sudo python setup.py install






Il 2018-10-02 18:35 Matthieu Bec ha scritto:

Hi Alfio,
(cc. Xianyu who is back among us)
Sounds good, for October. Thanks for the update about the lab.
For computer, the one you / Fabio setup last time is already at the
summit, agreed it seems best we continue using it (and decommission
the old one if that makes sense). Do you want to keep the same name in
DNS?
By the way, there was an effort to capture all the installation steps
we could later reproduce and automate in a kickstart.
I don't recall if you sent us those instructions?
Thanks,
Matthieu

On Oct 2, 2018, at 4:01 AM, Alfio Puglisi <puglisi@arcetri.astro.it> wrote:
Hi Matthieu,
after some internal discussions, the result is that we prefer to use SOUL/FLAO AGW in the lab without jumbo frames: they are not needed for this run's lab activities (it's just optical alignment), and it will avoid the need to change all the IP addresses without Fabio or me on site, because we both arrive on the mountain some days after Enrico, who is instead starting the optomechanical alignment immediately.
Thus this is the ideal sequence of activities:
- 18-20 september: AGW in the clean room, driven from flao-sxwfs as usual, using the ordinary LBT network (no jumbo frames)
- 20 september: update of AGW IP addresses for the jumbo frames network (no further lab work)
- 21 september: AGW is mounted on the telescope and connected to the jumbo frames switch. Flao-sxwfs is switched to the jumbo frames network as well
- 22 september onward: we work on the telescope with jumbo frames like LBTI.
- after: if the AGW needs to go down in the lab for whatever reason, it will need to find the jumbo frames network in place.
Does this sequence make sense to you?
Another question is which computer are we going to use to drive the AGW. Will it be the same physical computer as before (flao-sxwfs)? In this case, we need to update remotely the SOUL software on it, before the start of the run. Or instead is it possible to use the box that was used in the Steward lab? If this computer is still available, it will make things easier at first, since we could just place it in the clean room next to the AGW, and everything is already installed and configured.
Alfio
On Mon, Oct 1, 2018 at 11:09 PM Matthieu Bec <mbec@lbto.org> wrote:
Hi Alfio,
Stephen is putting things in place for your upcoming FLOA/SOUL upgrade, primarily to make sure you have jumbo the few days you will be in the lab.
On the telescope, it's should be a simple matter of connecting to the new switch we have in ULTH.
I don't know who keeps these instructions - they should be updated somehow.
One thing when you come here, we would like to update SOUL/FLAO with a range of IPs consistent with the new Jumbo network, does that sound Ok?
Thanks,
Matthieu