Skip to main content

A trip to Rethimno (Greece)

Rethimno is a beautiful city of approximately 40000 people in Crete. One of the well preserved places is the Rethymnon Old Town. The town still maintains its old aristocratic appearance, with its buildings dating from the 16th century, arched doorways, stone staircases, Byzantine and Hellenic-Roman remains, small Venetian harbor and narrow streets.
Small road inside the old town of Rethimno in Crete, Greece.
Small road inside the old town of Rethimno in Crete, Greece.

One of the many small streets in Rethimno from the beautiful island of Crete in Greece.
One of the many small streets in Rethimno from the beautiful island of Crete in Greece.


View of the old port Rethimno, Crete, Greece.
View of the old port Rethimno, Crete, Greece.
View of the sea from Fortez, am old fortress in Rethimno, Crete, Greece.
View of the sea from Fortezza, an old fortress in Rethimno, Crete, Greece.
At the top of a low hill named "Palaiokastro" there is a small fortress (Fortezza). It was built in 1590 to protect the city from the pirates raids and the Turks. The name "Palaiokastro which means 'The old Castle" was in use even by the Venetians which demonstrates the existence of an even older castle at this place.  The interior of Fortezza contains different building including storerooms for canons and weapons were kept, the house of the Councillors, and the residence of the Rector.

Fortezza inner view, an old fortress in Rethimno, Crete, Greece.
 Fortezza inner view, an old fortress in Rethimno, Crete, Greece.

View of white mountains from Fortezza castle in Rethimno, Crete, Greece.
View of  white mountains from Fortezza castle in Rethimno, Crete, Greece.







View of the port Fortezza from old fortress in Rethimno, Crete, Greece.
 View of the port Fortezza from old fortress in Rethimno, Crete, Greece.





Labels:
Location: Rethimno, Greece

Popular posts from this blog

Static linking with gcc and g++

In this tutorial, we will explain what the static linking is, how this affect the size of final binary, and why statically linking with g++ sometimes is pain. By definition, a statically compiled binary is a group of programmer ‘s routines, external functions, and variables which are packed into the final binary executable. The compiler or the linker produces the final object and embeds all the functions and variables and the linking phase.  There are two reasons of using dynamic linking and shared libraries: 1) Avoid creating a huge binary, if all the programs use a standard set of libraries why not having the operating system providing to them 2) Compatibility on operating system and machine dependant characteristics: sometimes the libraries must be implemented based on the architecture or the operating system and using dynamic linking is an easy way to avoid this catch. On the other hand, static linking is the ideal way of distributing one software product, pay...
Read more

Processing Milky Way in RawTherapee

This text is an analysis of a video I did some months ago how to process photos of our Milky Way in RawTherapee. You can find the picture here . The photo was taken by wiegemalt. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Editing: Step 1: Fixing lighting The first thing someone notices when opening the picture is the extreme noise due to high ISO used (1600 - check the picture on the right). The first thought is to de-noise the picture, however, if you do that you are going to loose the details of the night sky. The main reason for the high noise is the additional exposure Rawtherapee adds when the 'Auto' button is pressed. In particular, the RT adds +2.4 EV to equalize the picture. This is Wrong! What we want is to keep the noise down and at the same time bring the stars up. That's why we are going to play with the Tone Curve of the RT. To adjust the light properly we increase the cont...
Read more

Auto - Vectorization with little help from GCC!

This tutorial helps the programmers to benefit the progress of the auto-vectorization algorithms that are implemented in modern compilers, such as gcc. Before you start playing with the vectorization of your code i assume that you don't have any bottleneck in you code (like dynamic memory allocation etc) in the critical path. In this tutorial we will use the gcc 4.4.1, but the same steps can be applied to newer or older versions.  First of all there are two issues with auto vectorization:  1) gcc must know the architecture (eg what SIMD instructions are available)  2) The data structures must by properly aligned in memory The first step is to find the architecture of your processor and point it to gcc using the flags -mtune=... / -march=... you specify the architecture.  For example, my laptop is core2Duo so i put -march=core2. You can find more more information  here .  The next problem we must solve is knowledge of memory alignment. ...
Read more