vision.cs.tut.fi

In a nutshell:
  • Our Web pages are in Lintula Subversion repo: read more
    • Accessible via SVN at svn+ssh://kaarne.cs.tut.fi/share/sgnprojects/vision/visionwww/
  • You need to be a member of the "vision" group to checkout the repo - contact Joni and he will add you
  • The pages are automatically updated after each commit using a special ("hack") Subversion post-commit hook (read about the post-commit hooks: a breaf intro)
  • The hook updates changed files and copies them to our Web server. In order to make copying automatic, you must enable password free ssh login from kaarne.cs.tut.fi to vision.cs.tut.fi
All modifications to the new website is done through SVN. SVN commits will be automatically copied to the web server. All external modifications are more or less moderated by Joni (joni.kamarainen@tut.fi). Please keep information about staff, publication/news and research topics up-to-date.

The whole website is written in XHTML 1.0. Please try to respect this.

Table of contents:

SSH configuration

Before committing changes to SVN repository, it is important that you've enabled keyless authentication between kaarne.cs.tut.fi (SVN repository) and vision.cs.tut.fi (public web server).
$ ssh kaarne.cs.tut.fi
$ ssh-keygen
$ ssh-add
$ ssh-copy-id vision.cs.tut.fi

In ssh-keygen give blank as the password. It will generate your private and public (RSA) keys. ssh-copy-id adds your public key to the list of trusted sites in vision.cs.tut.fi. You may check the contens of ~/.ssh/ directory to understand what's going on. Note: if the ssh-copy-id is missing, then you need to copy the public key manually (<a href="http://www.linuxproblem.org/art_9.html" target="_top">example</a>).

Directory structure

include/ PHP scripts used by the MVPR webpage (do not edit!)
images/ All images used by included pages (excluding the portraits)
news_data/ Files for news items
people_data/ Files for people info and images
pages/ All different pages shown on the website
data/ Bibliography and PDF publications

Updating people/staff

To add a new staff member you need to create a person file under appropriate subdirectory under the people_data/ directory. It's suggested to name it by "lastnamefirstname.txt"

e.g. to add a new Phd. student, go under the people_data/phdstuds/ and create a txt file with the following contents:
<name>Matti Meikäläinen</name>
<title></title>
<room>666</room>
<email>matti.meikalainen@lut.fi</email>
<phone>+358 1 23456789</phone>
<homepage>http://www.matinsivut.com</homepage>

All fields are not required to be filled or added. For title, use "Prof." for professors, "Dr." for doctors, otherwise leave the title empty. Please, create a jpg file with same basename to have a portrait on the webpage. The height of the portrait should be 100 px, width 75-85 px. The image will be rescaled to 100 px height.

Updating news item

To add news items, just add a news file under the news_data/ directory. It's suggested to name it by "yyyy-mm-dd_title.txt". The file requires following contents:
<date>2011-02-14</date>
<title>News!</title>
<abstract>One sentence description</abstract>
<body>A lot of new stuff. See here!</body>
 

Title and abstract are shown on the MVPR front page while the news page will show also the body. The body can contain HTML markup. For style reasons, avoid HTML in title and abstract.

Updating bibliography

Bibliography is in BibTeX? format and can be accessed as data/bibliography.bib. Everybody is responsible for updating their own publications.

Use the following style:
  • Do not leave any empty or unused fields such as OPT fields generated by Emacs.
  • Field url is used to link to the PDF of the publication. The link will be shown with text "pdf".
    • Place the PDFs under data/. For example, see Laaksonen et al., Humanoids 2010.
  • For Scandinavian letters etc. do not use utf-8 or Latin-1 encodings but instead use LaTeX? markup.
Note that the whole BibTeX? entry is visible to the user by clicking at the [bib] button so do not leave comments and such.

Updating research pages

The research pages can be accessed under the pages/ directory by modifying the appropriate .inc.php file. For example: object.inc.php (Scene understanding). Each research topic has one 150x150 image on the research main page.

If you add any images, please place them under the images/ directory. Alignment and presentation of images can be manipulated with styles. Unaligned image with default borders:
<img src="" alt="" />

Right-aligned image with default borders:
<img src="" alt="" class="right" />

Left-aligned image with default borders:
<img src="" alt="" class="left" />

Image with no borders:
<img src="" alt="" class="noborder" />

Note that you can apply these styles simultaneously. E.g.
<img src="" alt="" class="right,noborder" />

Additionally, try to write valid XHTML markup. E.g. Remember to add quatation marks around values and alt parameters with value for images. Remember to close every opened tag and validate your pages with Validator from now and then.

Testing Web pages on your own computer

If you are making big changes it might be convenient to write and test the html and php code on your own desktop or laptop before committing to the repository that makes everything public. That, however, needs some preparation since you need to run a http server on your computer and enable the required modules (php).

First, you need to install the server
$ sudo apt-get install apache2

After that you should be able to connect to the server, try with your browser by giving the address "localhost".

For safety, let's access the group Web pages from your home directory. Let's first enable userdir module and make a test page for you:
$ sudo a2enmod userdir
$ sudo service apache2 restart
$ mkdir ~/public_html
$ chmod 0755 ~/public_html
$ echo "foo" > ~/public_html/index.html

Now, entering the address localhost/~YOURUSERNAME should provide you the contents of the index.html file. Next, we make a symbolic link to the visionwww directory and enable the RewriteEngine? module
$ sudo a2enmod userdir
$ sudo service apache2 restart
$ cd ~/public_html
$ ln -s <WHEREVER_YOU_HAVE_VISIONWWW_REPO>/visionwww
$ cd visionwww & ln -s dothtaccess_userdir .htaccess

Now, entering the address localhost/~YOURUSERNAME/visionwww follows the symbolic link, but does not quite do what you want and that's because visionwww requires php5 processing, so let's
$ sudo apt-get install php5
EDIT /etc/apache2/mods-available/php5.conf and comment out the part preventing php in user dirs
$ sudo service apache2 restart

And that's it, now visionwww at your localhost should look exactly the same as vision.cs.tut.fi. Moreover, note that in visionwww there is the important access file ".htaccess" which needs to point to dothtaccess_userdir if you're running on your own computer and dothtaccess_wwwserver in vision.cs.tut.fi - this is the file that defines the RewriteEngine? rules that tries to secure our www server from sniffing attacks.

-- JoniKaemaeraeinen - 15 May 2014
Print version |  PDF  | History: r4 < r3 < r2 < r1 | 
Topic revision: r4 - 15 May 2014 - 13:50:13 - JoniKaemaeraeinen
 

TUTWiki

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TUTWiki? Send feedback