AIRWiki - User contributions [en]

Ovarian Cancer Detection by an Electronic Nose

2011-01-05T18:02:30Z

AlessandroMariaMauri:

{{Project
|title=Ovarian Cancer Detection by an Electronic Nose
|coordinator=AndreaBonarini; MatteoMatteucci
|tutor=RossellaBlatt;
|students=AlessandroMariaMauri; NiccoloMoretti
|restopic=Early cancer detection
|start=2009/10/01
|status=Active
|level=Ms
|type=Course
}}

=== Short description ===

The project aims at evaluating the possibility of diagnosing ovarian cancer using an electronic nose, already used with success in the lung cancer detection ( [[Lung Cancer Detection by an Electronic Nose]] ).

=== Laboratory work and risk analysis ===

Laboratory work for this project will be mainly performed at the Istituto Nazionale dei Tumori di Milano, where the acquisistion of subjects' breath, both sick and healthy will be done.
For this kind of work, there are not potential risks.

=== Project description ===

The electronic nose is an instrument able to detect and recognize odors, that is the volatile substances in the atmosphere or emitted by the analyzed substance. This device can react to a gas substance by providing signals that can be analyzed to classify the input. It is composed of a sensor array (MOS sensors, in our case) and a pattern classification process based on machine learning techniques. Each sensor reacts in a different way to the analyzed substance, providing multidimensional data that can be considered as a unique olfactory blueprint of the analyzed substance. In our work, we used an array composed of six Metal Oxide Semiconductor (MOS) sensors.
In this project, we have been using an electronic nose based on an array of six MOS sensors, to recognize the presence of ovarian cancer in breaths' subjects, diagnosing the disease with a non invasive and low cost method.

=== Progress ===

==Acquisition phase==

In 23 days 29 samples were acquired, 16 sick and 13 sane.
Only one type(either sane or sick) was acquired per day (due to problems related to the "rarity" of ovarian cancer) and this could bring some problems in the next phase, even if the only features used will be the one called EOS, that should be independent to time.
Moreover the acquisition of samples coming from sane subjects was done mainly at the beginning of the project (2009) while samples coming from sick subjects have been taken for the biggest part after spring 2010.
Analysing the response of the 6 MOS sensors for every acquisition no anomaly were discovered, so it is possibile to use all the samples.
No blinds were acquired.

==Data analysis phase==

In progress..
At the moment good results have been achieved, but they will not published yet because we're probably victim of overfitting.

User:AlessandroMariaMauri

2010-10-14T14:00:23Z

AlessandroMariaMauri:

== ''Alessandro Mauri'' ==

----

{{User
|firstname=Alessandro Maria
|lastname=Mauri
|id=739272 (676677)
|email=[mailto:alessandromaria.mauri@polimi.com alessandromaria.mauri@polimi.it]
|advisor=AndreaBonarini
|projectpage=Ovarian Cancer Detection by an Electronic Nose
|photo=Alessandromauri.jpeg
}}

external e-mail: papamoretti(AT)hotmail(DOT)com 
matricola: 739272

I am a Master Student in Computer Engineering at Politecnico di Milano. 
I worked on [[BehaviorTiltingRobot]] Project to implement a high level behaviour on [[Balancing robots: Tilty, TiltOne | Tilty]], with [[User:AndreaBonarini | Andrea Bonarini]]. 
I am working on [[Ovarian Cancer Detection by an Electronic Nose]] with [[User:AndreaBonarini | Andrea Bonarini]].

User:AlessandroMariaMauri

2010-10-14T13:58:31Z

AlessandroMariaMauri:

== ''Alessandro Mauri'' ==

----

{{User
|firstname=Alessandro Maria
|lastname=Mauri
|id=739272 (676677)
|email=[mailto:alessandromaria.mauri@polimi.com alessandromaria.mauri@polimi.it]
|advisor=AndreaBonarini
|projectpage=BehaviorTiltingRobot / Ovarian Cancer Detection by an Electronic Nose
|photo=Alessandromauri.jpeg
}}

external e-mail: papamoretti(AT)hotmail(DOT)com 
matricola: 739272

I am a Master Student in Computer Engineering at Politecnico di Milano. 
I worked on [[BehaviorTiltingRobot]] Project to implement a high level behaviour on [[Balancing robots: Tilty, TiltOne | Tilty]], with [[User:AndreaBonarini | Andrea Bonarini]]. 
I am working on [[Ovarian Cancer Detection by an Electronic Nose]] with [[User:AndreaBonarini | Andrea Bonarini]].

Ovarian Cancer Detection by an Electronic Nose

2010-10-14T13:55:17Z

AlessandroMariaMauri:

Ovarian Cancer Detection by an Electronic Nose

2010-10-14T13:48:09Z

AlessandroMariaMauri: New page: {{Project |title=Ovarian Cancer Detection by an Electronic Nose |short_descr=The project aims at evaluating the possibility of diagnosing ovarian cancer using an electronic nose, already u...

{{Project
|title=Ovarian Cancer Detection by an Electronic Nose
|short_descr=The project aims at evaluating the possibility of diagnosing ovarian cancer using an electronic nose, already used with success in the lung cancer detection ( [[Lung Cancer Detection by an Electronic Nose]] ).
|coordinator=AndreaBonarini; MatteoMatteucci
|tutor=RossellaBlatt;
|students=AlessandroMariaMauri; NiccoloMoretti
|restopic=Early cancer detection
|start=2009/10/01
|status=Active
|level=Ms
|type=Course
}}
The electronic nose is an instrument able to detect and recognize odors, that is the volatile substances in the atmosphere or emitted by the analyzed substance. This device can react to a gas substance by providing signals that can be analyzed to classify the input. It is composed of a sensor array (MOS sensors, in our case) and a pattern classification process based on machine learning techniques. Each sensor reacts in a different way to the analyzed substance, providing multidimensional data that can be considered as a unique olfactory blueprint of the analyzed substance. In our work, we used an array composed of six Metal Oxide Semiconductor (MOS) sensors.
In this project, we have been using an electronic nose based on an array of six MOS sensors, to recognize the presence of lung cancer in breaths' subjects, diagnosing the disease with a non invasive and low cost method.

BehaviorTiltingRobot

2010-03-17T15:05:43Z

AlessandroMariaMauri: /* Dates */

== '''Part 1: project profile''' ==

=== Project name ===

Editing Behavior Tilting Robot

=== Project short description ===

The purpose of this project is to implement some behaviors for a balancing robot, by integrating a camera on board with face detection and blob tracking (using Laurenzano-Merlin thesis).

=== Dates ===
Start date: 2009/05/15

End date: 2010/02/15

=== People involved ===

==== Project leader ====

[[User:AndreaBonarini | Andrea Bonarini]]


==== Students ====

'''Students currently working on the project'''

[[User:AlessandroMariaMauri| Alessandro Mauri]] [[User:NiccoloMoretti | Niccolo' Moretti]] [[BehaviorTiltingRobot | High level behavior]] (tracking)

=== Laboratory work and risk analysis ===
A list of potentially dangerous (if not correctly performed) activities is included into the [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] of the AIRLab, which everybody MUST know to work at the AIRLab.

Laboratory work for this project is mainly performed at AIRLab/Lambrate. It includes some mechanical work as well as electrical and electronic activity. Potentially risky activities are the following:

* Robot testing. Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.
* Death ray testing: on the robot will be mounted professor Azzoide's death ray projector. When testing it on live animals (e.g. voltures, pigs, camels, dwarf elephants) we will make sure that people stand clear of the test area.

== '''Part 2: project description''' ==
* First Step: writing a controller (using the Modular Robotic Toolkit) to handle the movement of the camera, in order to counterbalance the oscillations made by the robot to move and keep the balance. Implementation of high level behaviour related to the camera.
* Further Steps: to do ...

BehaviorTiltingRobot

2010-03-17T15:04:58Z

AlessandroMariaMauri: /* Students */

== '''Part 1: project profile''' ==

=== Project name ===

Editing Behavior Tilting Robot

=== Project short description ===

The purpose of this project is to implement some behaviors for a balancing robot, by integrating a camera on board with face detection and blob tracking (using Laurenzano-Merlin thesis).

=== Dates ===
Start date: 2009/05/15

End date:

=== People involved ===

==== Project leader ====

[[User:AndreaBonarini | Andrea Bonarini]]


==== Students ====

'''Students currently working on the project'''

[[User:AlessandroMariaMauri| Alessandro Mauri]] [[User:NiccoloMoretti | Niccolo' Moretti]] [[BehaviorTiltingRobot | High level behavior]] (tracking)

=== Laboratory work and risk analysis ===
A list of potentially dangerous (if not correctly performed) activities is included into the [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] of the AIRLab, which everybody MUST know to work at the AIRLab.

Laboratory work for this project is mainly performed at AIRLab/Lambrate. It includes some mechanical work as well as electrical and electronic activity. Potentially risky activities are the following:

* Robot testing. Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.
* Death ray testing: on the robot will be mounted professor Azzoide's death ray projector. When testing it on live animals (e.g. voltures, pigs, camels, dwarf elephants) we will make sure that people stand clear of the test area.

== '''Part 2: project description''' ==
* First Step: writing a controller (using the Modular Robotic Toolkit) to handle the movement of the camera, in order to counterbalance the oscillations made by the robot to move and keep the balance. Implementation of high level behaviour related to the camera.
* Further Steps: to do ...

BehaviorTiltingRobot

2010-03-17T15:04:32Z

AlessandroMariaMauri: /* Project short description */

== '''Part 1: project profile''' ==

=== Project name ===

Editing Behavior Tilting Robot

=== Project short description ===

The purpose of this project is to implement some behaviors for a balancing robot, by integrating a camera on board with face detection and blob tracking (using Laurenzano-Merlin thesis).

=== Dates ===
Start date: 2009/05/15

End date:

=== People involved ===

==== Project leader ====

[[User:AndreaBonarini | Andrea Bonarini]]


==== Students ====

'''Students currently working on the project'''

[[User:AlessandroMariaMauri| Alessandro Mauri]] [[User:NiccoloMoretti | Niccolo' Moretti]] [[BehaviorTiltingRobot | High level behavior]] (tracking, obstacle avoidance)

=== Laboratory work and risk analysis ===
A list of potentially dangerous (if not correctly performed) activities is included into the [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] of the AIRLab, which everybody MUST know to work at the AIRLab.

Laboratory work for this project is mainly performed at AIRLab/Lambrate. It includes some mechanical work as well as electrical and electronic activity. Potentially risky activities are the following:

* Robot testing. Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.
* Death ray testing: on the robot will be mounted professor Azzoide's death ray projector. When testing it on live animals (e.g. voltures, pigs, camels, dwarf elephants) we will make sure that people stand clear of the test area.

== '''Part 2: project description''' ==
* First Step: writing a controller (using the Modular Robotic Toolkit) to handle the movement of the camera, in order to counterbalance the oscillations made by the robot to move and keep the balance. Implementation of high level behaviour related to the camera.
* Further Steps: to do ...

Balancing robots: Tilty, TiltOne

2010-03-17T15:03:02Z

AlessandroMariaMauri: /* Students */

{{Project
|title=BalancingRobots
|image=Tiltone 2.png
|short_descr=Meta-project about balancing robots.
|coordinator=AndreaBonarini
|tutor=MartinoMigliavacca
|resarea=Robotics
|restopic=Robot development
|start=2006/01/01
|end=2010/12/31
|status=Active
}}
=== Project short description ===

This project is aimed at designing and implementing autonomous balancing robots, i.e. robots able to move on two wheels while keeping equlibrium. Characteristic features of the robots implemented at AIRLab are the possibility to drive on slopes and small obstacles and the ability to rise again in case of fall. [[Tilty]] has an A4 footprint, while [[TiltOne]], is based on cross-bike wheels.

==== Students ====

'''Students currently working on the project'''

[[User:MartinoMigliavacca | Martino Migliavacca]] TiltOne Implementation and controller

[[User:AlessandroMariaMauri| Alessandro Mauri]] [[User:NiccoloMoretti | Niccolo' Moretti]] [[BehaviorTiltingRobot | High level behavior]] (tracking)

'''Students working on the project in the past'''

Michele Antolini michele.antolini (at) tiscali (dot) it

Marco Bolognino m.bolognino (at) libero (dot) it

[[User:RiccardoChiappa | Riccardo Chiappa]]

[[User:JoseContador | Jose Contador]] Tilty Fuzzy controller

==== External personnel ====

[[User:Claudio Caccia | Claudio Caccia]], the Tilty designer.

== TiltOne Youtube video ==
{{#ev:youtube|4FrA73Cxljs}}
*[http://www.youtube.com/watch?v=4FrA73Cxljs External link]

=== Useful internet links ===
[http://www.balbots.com/ Balbot], [http://www.geology.smu.edu/~dpa-www/robo/nbot/ nBot], [http://www.tedlarson.com/robots/balancingbot.htm Bender], [http://www.dprg.org/projects/2003-01a/ DPRG gyro], [http://www.youtube.com/watch?v=V40ScvJeFxg Lego balancing robot], [http://www.barello.net/Papers/Balancing%20Robot%20Seminar.pdf Devil]

=== Laboratory work and risk analysis ===
A list of potentially dangerous (if not correctly performed) activities is included into the [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] of the AIRLab, which everybody MUST know to work at the AIRLab.

Laboratory work for this project is mainly performed at AIRLab/Lambrate. It includes some mechanical work as well as electrical and electronic activity. Potentially risky activities are the following:
* Use of mechanical tools. Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.
* Use of soldering iron. Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.
* Use of high-voltage circuits. Special gloves and a current limiter will be used.
* Transportation of heavy loads (e.g. robot parts). Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.
* Robot testing. Standard safety measures described in [http://airlab.elet.polimi.it/index.php/airlab/content/download/461/4110/file/documento_valutazione_rischi_AIRLab.pdf Safety norms] will be followed.

Cameras, lenses and mirrors

2010-03-02T16:50:09Z

AlessandroMariaMauri:

==IMPORTANT NOTES==
'''Never touch the sensor element (CCD or CMOS) of a camera with anything!''' It can very easily be scratched.

'''Never touch the glass elements of a lens with your hands!''' The oil from human skin will cause damage.

==Cameras==
In the AIRLab you can find different kind of cameras. These are the main groups:
*'''Analogue cameras'''. Video output is given as an electrical signal, which needs analogue-to-digital conversion to be processed by a computer; this is done by a specific card called ''frame grabber'' or ''video capture card'' (the latter tend to be the lowest-performance items; see [[Cameras, lenses and mirrors#Frame grabbers]] for details). Analogue video is outdated for computer vision and robotics applications, due to its cost, low performance and complexity; nowadays digital camera systems (such as all the ones listed below) are always preferred.
*'''USB cameras'''. Usually very cheap, they are suitable for low-performance applications (i.e. those where low frame rate is needed and low image quality can be accepted). Their main advantage (along with cost) is the fact that every modern computer has USB ports. The fact that the USB standard includes 5V DC power supply lines helps simplifying camera design and use.
*'''FireWire cameras'''. The FireWire (or IEEE1394) bus is generally used for low-end industrial cameras, i.e. devices with technical characteristics much superior to those typical of USB cameras but low-performance according to typical machine vision standards. Industrial cameras usually give to the user a much wider control over the acquisition parameters compared to consumer cameras, and therefore they are usually preferred in robotics; their downside is the higher cost. There are different versions of IEE1394 link (see http://en.wikipedia.org/wiki/Firewire for details), with different bitrates, starting from the 400Mbit/s FireWire 400. Generally they are all considered superior to USB 2.0, even if theoretical bandwidth is lower for FireWire 400. Firewire ports can include power supply lines, but some interfaces (and in particular those on portable computers) omit them. Although the use of FireWire interfaces has expanded in recent years, they are not yet considered a standard feature for motherboards.
*'''GigE Vision cameras'''. GigE Vision (or Gigabit Ethernet Vision) is a rather new connection standard for machine vision, based upon the established Ethernet protocol in its Gigabit (i.e. 1000Mbps) version. It is very interesting, as complex multiple-camera systems can be easily built using existing (Gigabit) Ethernet hardware, such as cables and switches. Vision data is acquired simply through a generic Ethernet port, commonly found on motherboards or easily added. However, 100Mbps (or ''fast Ethernet'') ports are not guaranteed to work and can sustain only modest video streams; on the other hand, 1000Mbps ports are now standard on motherboards, so this will not be a problem anymore in a few years. It seems that GigE Vision is becoming the most common interface for low- to medium-performance industrial cameras.
*'''CameraLink cameras'''. Cameralink is a high-speed interface expressly developed for high-performance machine vision applications. It is a point-to-point link, i.e. a CameraLink connection is used to connect a single camera to a digital acquisition card (''frame grabber''). Its diffusion is limited to applications where extreme frame rates ''and'' resolutions are needed, because CameraLink gear is very expensive.
*'''ST Camera boards'''. Cameras with cell phone sensor and ARM processor for onboard computation.

The following is a list of the cameras available in the AIRLab. (To be precise, it is a list of the cameras that are modern enough to be useful.) For each of them the main specifications (and a link to the full specifications) are given. Details on the different types of lens mount are given below in [[Cameras, lenses and mirrors#Lenses]]. The 'how many?' field tells if multiple, identical items are available. Finally, the 'where?' field tells you in which of the AIRLab sites (listed in [[The Labs]]) you can find an item, and the 'project' field is used to specify which project (if any) is using it.

Ah, one last thing. People like to actually ''find'' things when they look for them, so '''don't forget to update the table when you move something away from its current location'''. If you don't know where you are taking it, just put your name in the table.

{| border="1" cellpadding="5" cellspacing="0"
!resolution
!B/W, color
!max. frame rate
!sensor size
!interface
!maker
!model
!lens mount
!how many?
!where?
!project
!link to full specifications and/or manuals
|-
|1628x1236
|B/W
|24fps
|1/1.8"
|CameraLink
|Hitachi
|KP-F200CL
|C-mount
|1
|DEI
|
|[[media:KP-F200-Op_Manual.pdf]]
|-
|752x480
|color
|70fps
|1/3"
|GigE
|Prosilica
|GC750C
|C-mount
|3
|Lambrate (1/3), [[User:SimoneTognetti| Simone Tognetti]](from 19/05/2009, dal 14/12/2009 sono impiegate per esperimenti Affective nell'Airlab del DEI)(2/3)
|RAWSEEDS (1/3), Driving companions (2/3)
|http://www.prosilica.com/products/gc_series.html
|-
|659x493
|color
|90fps
|1/3"
|GigE
|Prosilica
|GC650C
|C-mount
|1
|Lambrate
|RAWSEEDS
|http://www.prosilica.com/products/gc_series.html
|-
|1024x768
|color
|30fps
|1/3"
|GigE
|Prosilica
|GC1020C
|C-mount
|2
|Lambrate (2/2)
|RAWSEEDS (2/2)
|http://www.prosilica.com/products/gc_series.html
|-
|CCIR (625 lines)
|B/W
|CCIR (50fps, interlaced)
|2/3"
|analogue
|Sony
|XC-ST70CE
|C-mount
|2
|DEI (2/2)
|
|[[media:XCST70E_manual.pdf]]
|-
|659x494
|color
|30fps
|1/4"
|FireWire 400
|Unibrain
|Fire-i 400 industrial
|C-mount
|3
|Lambrate (3/3)
|RAWSEEDS (3/3)
|http://www.unibrain.com/Products/VisionImg/Fire_i_400_Industrial.htm
|-
|659x494
|color
|30fps
|1/4"
|FireWire 400
|Unibrain
|Fire-i board camera
|proprietary
|8
|Lambrate (3/8), Bovisa (2/8), [[User:PaoloCalloni]] (1/8), [[User:DavideMigliore]] (1/8), [[User:CristianoAlessandro]] (1/8)
|RAWSEEDS (2/8), MRT (?/8)
queste sono quelle "nuove"? se si una e' su rabbiati, portiere di mrt, sin da cuvio, e' nella testa omnidir Domenicogsorrenti 21.04.09

1 nuova e' la frontale di recam

1 nuova sulla testa omnidir di ridan

|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|640x480
|color
|30fps
|1/4"
|FireWire 400
|Unibrain
|Fire-i digital camera
|fixed optics (4.3mm, f2.0)
|4
|
1 e' sulla testa omnidir di rigo

1 e' sulla testa omnidir di recam

1 e' sulla testa omnidir mrt05-03 (armadio domenico@unimib)

1 e' sulla testa omnidir mrt05-04 (armadio domenico@unimib)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_DC.htm
|-
|640x480 dual sensor, 9cm baseline
|color
|30fps
|1/3"
|FireWire 400
|Videre Design
|STOC stereo-on-a-chip stereo camera
|C-mount, fitted with two 3.5mm, f1.6, 1/2" lenses
|1
|Lambrate => li lin office => Domenicogsorrenti 13.01.09 => giulio fontana 23.01.09
|
|http://www.videredesign.com/vision/stoc.htm
|-
|640x480
|color
|60fps
|1/3"
|FireWire 400
|Videre Design
|DCSG (associated with STOC)
|C-mount, fitted with one 3.5mm, f1.6, 1/2" lens
|1
|Lambrate
|
|http://www.videredesign.com/vision/dcsg.htm
|-
|?
|color
|?
|?
|?
|ST Microelectronics
|ST1-Cam + ST2-Cam
|integrated
|2
|ST1-Cam [[User:AndreaBonarini| Andrea Bonarini]], ST2-Cam [[User:LorenzoConsolaro | Lorenzo Consolaro]] and [[User:DarioCecchetto | Dario Cecchetto]]
|
|
|-
|?
|color
|?
|?
|?
|ST Microelectronics
|ST5-CamMic + ST6-CamMic
|integrated with microphone
|2
|ST1-CamMic [[User:AndreaBonarini| Andrea Bonarini]], ST2-CamMic [[User:AndreaBonarini|Andrea Bonarini]]
|
|
|-
|?
|color
|?
|?
|?
|ST Microelectronics
|ST4-DC (Demo board)
|integrated
|1
|[[User:RaffaelePetta|Raffaele Petta]]
|
|
|}
 

==Lenses==
Be aware that sensor dimension (i.e. its diagonal, measured in fractions of an inch) is ''not'' the same for all cameras. Therefore one of the key specifications for a lens is the maximum sensor dimension supported. If you use a given lens with too big a sensor, the edges of the image will be black as they lie outside the circle of the projected image. Also beware of the strange convention used for sensor diagonals, i.e. a fraction in the form A/B" where A and B are integer ''or non-integer'' numbers. For instance an 1/2" sensor is smaller than an 1/1.8" one.
The variability of sensor dimensions has another side effect: the same lens has a different angle of view if you change the sensor size. Therefore the same lens can behave as a wide-angle with a large sensor and as a telephoto with a small sensor.

An useful guide to lenses (in Italian or English) can be found at http://www.rapitron.it/guidaob.htm.

The following is a list of the actual lenses available in the AIRLab. For each of them the main specifications (and a link to the maker's or vendor's page for full specifications) are given. A '?' means an unknown parameter: if you know its value or experimentally find out it when using the lens (e.g. the maximum sensor size), please ''update the table'' before the information is lost again! Lenses having 'M12x0.5' in Column 'mount type' are only usable with Unibrain's Fire-i board cameras. A 'YES' in the 'Mpixel' column indicates a so-called ''Megapixel lens'', i.e. a high quality, low-distortion lens designed for high-resolution industrial cameras (typically having large sensors); please note that some of these are specifically designed for B/W (i.e. black and white) cameras. The 'how many?' field tells if multiple, identical items are available. Finally, the 'where?' field tells you in which of the AIRLab sites (listed in [[The Labs]]) you can find an item, and the 'project' field is used to specify which project (if any) is using it.

Ah, one last thing. People like to actually ''find'' things when they look for them, so '''don't forget to update the table when you move something away from its current location'''. If you don't know where you are bringing it, just put your name in the table.

===C-mount and CS-mount lenses===
Industrial cameras usually have interchangeable lenses. This allows for the choice of the lens that is more suitable to the considered application. There are two main standards for industrial camera lenses: '''C-mount''' and '''CS-mount'''. Both are screw-type mounts. CS-mount is simply a modified C-mount where the distance between the back of the lens and the sensor element (CCD or CMOS) is shorter: therefore a CS-mount lens can be mounted on a C-mount camera if an ''adapter ring'' (i.e. a distancing cylinder with suitable threads) is placed between them. It is impossible, though, to use a C-mount lens on a CS-mount camera: if you try you will almost certainly break the sensor, scratch the lens, or both. Just because a lens fits a camera, it doesn't mean it can be actually mounted on it!

{| border="1" cellpadding="5" cellspacing="0"
!focal length
!max. aperture
!max. sensor size
!mount type
!maker
!model
!Mpixel
!how many?
!where?
!project
!link to full specifications
|-
|3.5mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|Lambrate
|LURCH
|?
|-
|4.0mm
|f2.0
|1/2"
|C-mount
|Microtron
|FV0420
|YES (B/W only)
|2
|DEI
|
|http://www.rapitron.it/obmegpxman1.htm
|-
|4.5mm
|f1.4
|1/2"
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|-
|4.8mm
|f1.8
|2/3"
|C-mount
|Computar
|M0518
|NO
|1
|DEI
|
|http://www.computar.com/cctvprod/computar/mono/048.html
|-
|6mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|-
|6mm
|f1.4
|1/2"
|C-mount
|Goyo
|GMHR26014MCN
|YES
|4
|DEI
|RAWSEEDS (4/4)
|http://www.goyooptical.com/products/industrial/hrmegapixel.html
|-
|8mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|-
|8mm
|f1.4
|2/3"
|C-mount
|Goyo
|GMHR38014MCN
|YES
|2
|DEI
|RAWSEEDS (2/2)
|http://www.goyooptical.com/products/industrial/hrmegapixel.html
|-
|8.5mm
|f1.3
|2/3"
|C-mount
|Computar
|?
|?
|2
|DEI
|
|(old model)
|-
|12mm
|f1.8
|2/3"
|C-mount
|?
|?
|?
|2
|DEI
|
|
|-
|12mm
|f1.4
|2/3"
|C-mount
|Goyo
|GMHR31214MCN
|YES
|1
|DEI
|
|http://www.goyooptical.com/products/industrial/hrmegapixel.html
|-
|15mm
|f2.0
|2/3"
|C-mount
|Microtron
|FV1520
|YES
|1
|DEI
|
|http://www.rapitron.it/obmegpxman1.htm
|-
|6-15mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|Lambrate
|
|?
|-
|12.5-75mm
|f1.8
|?
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|}
 

===M12 lenses===
We also use M12 lenses. These lenses are very simple, with no iris, and very small. Their mounting system is an M12x0.5 metric screw thread. They are commonly used for webcams, and usually do not provide the top optical quality.

{| border="1" cellpadding="5" cellspacing="0"
!focal length
!max. aperture
!max. sensor size
!mount type
!maker
!model
!Mpixel
!how many?
!where?
!project
!link to full specifications
|-
|2.1mm
|f2.0, with IR coating
|1/4"
|M12x0.5
|Unibrain
|2042
|NO
|6
|
1 e' a bovisa nelle mani di marcello

1 e' a lambrate su un giano riusato come robowii

1 e' a bovisa sulla frontale del triskar recam

1 e' in mano a martino per fare una frontale => 06.05.09 E' in bovisa montata sul triskar #3

1 l'ha Davide Migliore per acquisizioni monoslam

1 e' sulla testa omnidir di rabbiati

Domenicogsorrenti 04.05.09
|MRT midsize, robowii, monoslam
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|4.3mm, no IR filter
|f2.0
|1/4"
|M12x0.5
|Unibrain
|2046
|NO
|1
|Lambrate (1/1)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|4.3mm
|f2.0
|1/4"
|M12x0.5
|Unibrain
|2043
|NO
|3
|Bovisa (1/3), Lambrate (2/3)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|8mm
|f2.0
|1/4"
|M12x0.5
|Unibrain
|2044
|NO
|1
|Lambrate (1/1)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|}
 

==Frame grabbers==
As previously said, a '''frame grabber''' is an electronic board that connects to one or more cameras, and converts the signals from the cameras into a data stream that can be elaborated by a computer. They are usually designed as expansion boards to be fitted into the computer case. Frame grabbers are necessary for ''analogue cameras'' (as they include the analogue/digital converters) or for CameraLink digital cameras (in this case the frame grabber is essentially a high speed dedicated digital interface). Other kinds of digital cameras don't need a frame grabber: this is one of the main advantages of digital cameras over analogue ones in machine vision applications, where the processing is almost always performed by computers.
In the AIRLab two models of frame grabber are available:
*a digital frame grabber from Euresys, model Expert 2, having two CameraLink inputs (http://www.euresys.com/Products/grablink/GrablinkSeries.asp). ''Notes: needs a PCI-X slot; one of the inputs is not working due to a fault.''
*two multichannel analogue frame grabbers from Matrox, model Meteor II/Multi-Channel, having three analogue inputs that can be combined into a single three-channel RGB analogue input (http://www.matrox.com/imaging/support/old_products/home.cfm). ''Note: one item is permanently mounted on the MO.RO.1 robot: see [[The MO.RO. family]] for details.''
*two multichannel analogue frame grabbers from Matrox, model Meteor II/Multi-Channel, having three analogue inputs that can be combined into a single three-channel RGB analogue input (http://www.matrox.com/imaging/support/old_products/home.cfm). ''Note: one item is permanently mounted on the MO.RO.1 robot: see [[The MO.RO. family]] for details.''
*two single-channel analogue frame grabbers from Matrox, models Meteor and Meteor Pro (http://www.matrox.com/imaging/support/old_products/home.cfm).
All the frame grabbers (except the one on the MO.RO.1) are currently in AIRLab/DEI. If you move one of them, please '''write it down here'''... and do it NOW!

==Mirrors==
Much work has been done and is being done at the AIRLab on the topic of '''omnidirectional (machine) vision''' (sometimes referred to as ''omnivision''). Omnidirectional vision systems use special hardware to overcome the limitations of conventional vision systems in terms of field of view. The approach to this problem that we generally adopt is the use of conventional cameras in association with convex '''mirrors''', i.e. the capturing of the image reflected by a suitably-shaped mirror with a camera. The possibility of designing mirrors with specific geometric properties gives a very useful means to control the geometric behaviour of the whole camera+mirror system.

TODO for someone who knows better ;-) : mirror list

==Cable==
The complete list of cable for camera connection and/or power is under construction. You can partecipate listing below which cables are you using...

{| border="1" cellpadding="5" cellspacing="0"
!Type
!length
!how many?
!where?
!project
|-
|FireWire 6-6
|?
|2
|Bicocca (refer to Domenico G. Sorrenti, 2009-11-11)
|?
|-
|FireWire 6-6
|?
|1
|on LURCH wheelchair
|LURCH
|}

Cameras, lenses and mirrors

2010-01-21T09:39:42Z

AlessandroMariaMauri:

==IMPORTANT NOTES==
'''Never touch the sensor element (CCD or CMOS) of a camera with anything!''' It can very easily be scratched.

'''Never touch the glass elements of a lens with your hands!''' The oil from human skin is harmful.

==Cameras==
In the AIRLab you can find different kind of cameras. These are the main groups:
*'''Analogue cameras'''. Video output is given as an electrical signal, which needs analogue-to-digital conversion to be processed by a computer; this is done by a specific card called ''frame grabber'' or ''video capture card'' (the latter tend to be the lowest-performance items; see [[Cameras, lenses and mirrors#Frame grabbers]] for details). Analogue video is outdated for computer vision and robotics applications, due to its cost, low performance and complexity; nowadays digital camera systems (such as all the ones listed below) are always preferred.
*'''USB cameras'''. Usually very cheap, they are suitable for low-performance applications (i.e. those where low frame rate is needed and low image quality can be accepted). Their main advantage (along with cost) is the fact that every modern computer has USB ports. The fact that the USB standard includes 5V DC power supply lines helps simplifying camera design and use.
*'''FireWire cameras'''. The FireWire (or IEEE1394) bus is generally used for low-end industrial cameras, i.e. devices with technical characteristics much superior to those typical of USB cameras but low-performance according to typical machine vision standards. Industrial cameras usually give to the user a much wider control over the acquisition parameters compared to consumer cameras, and therefore they are usually preferred in robotics; their downside is the higher cost. There are different versions of IEE1394 link (see http://en.wikipedia.org/wiki/Firewire for details), with different bitrates, starting from the 400Mbit/s FireWire 400. Generally they are all considered superior to USB 2.0, even if theoretical bandwidth is lower for FireWire 400. Firewire ports can include power supply lines, but some interfaces (and in particular those on portable computers) omit them. Although the use of FireWire interfaces has expanded in recent years, they are not yet considered a standard feature for motherboards.
*'''GigE Vision cameras'''. GigE Vision (or Gigabit Ethernet Vision) is a rather new connection standard for machine vision, based upon the established Ethernet protocol in its Gigabit (i.e. 1000Mbps) version. It is very interesting, as complex multiple-camera systems can be easily built using existing (Gigabit) Ethernet hardware, such as cables and switches. Vision data is acquired simply through a generic Ethernet port, commonly found on motherboards or easily added. However, 100Mbps (or ''fast Ethernet'') ports are not guaranteed to work and can sustain only modest video streams; on the other hand, 1000Mbps ports are now standard on motherboards, so this will not be a problem anymore in a few years. It seems that GigE Vision is becoming the most common interface for low- to medium-performance industrial cameras.
*'''CameraLink cameras'''. Cameralink is a high-speed interface expressly developed for high-performance machine vision applications. It is a point-to-point link, i.e. a CameraLink connection is used to connect a single camera to a digital acquisition card (''frame grabber''). Its diffusion is limited to applications where extreme frame rates ''and'' resolutions are needed, because CameraLink gear is very expensive.
*'''ST Camera boards'''. Cameras with cell phone sensor and ARM processor for onboard computation.

The following is a list of the cameras available in the AIRLab. (To be precise, it is a list of the cameras that are modern enough to be useful.) For each of them the main specifications (and a link to the full specifications) are given. Details on the different types of lens mount are given below in [[Cameras, lenses and mirrors#Lenses]]. The 'how many?' field tells if multiple, identical items are available. Finally, the 'where?' field tells you in which of the AIRLab sites (listed in [[The Labs]]) you can find an item, and the 'project' field is used to specify which project (if any) is using it.

Ah, one last thing. People like to actually ''find'' things when they look for them, so '''don't forget to update the table when you move something away from its current location'''. If you don't know where you are taking it, just put your name in the table.

{| border="1" cellpadding="5" cellspacing="0"
!resolution
!B/W, color
!max. frame rate
!sensor size
!interface
!maker
!model
!lens mount
!how many?
!where?
!project
!link to full specifications and/or manuals
|-
|1628x1236
|B/W
|24fps
|1/1.8"
|CameraLink
|Hitachi
|KP-F200CL
|C-mount
|1
|DEI
|
|[[media:KP-F200-Op_Manual.pdf]]
|-
|752x480
|color
|70fps
|1/3"
|GigE
|Prosilica
|GC750C
|C-mount
|3
|Lambrate (1/3), [[User:SimoneTognetti| Simone Tognetti]](from 19/05/2009, dal 14/12/2009 sono impiegate per esperimenti Affective nell'Airlab del DEI)(2/3)
|RAWSEEDS (1/3), Driving companions (2/3)
|http://www.prosilica.com/products/gc_series.html
|-
|659x493
|color
|90fps
|1/3"
|GigE
|Prosilica
|GC650C
|C-mount
|1
|Lambrate
|RAWSEEDS
|http://www.prosilica.com/products/gc_series.html
|-
|1024x768
|color
|30fps
|1/3"
|GigE
|Prosilica
|GC1020C
|C-mount
|2
|Lambrate (2/2)
|RAWSEEDS (2/2)
|http://www.prosilica.com/products/gc_series.html
|-
|CCIR (625 lines)
|B/W
|CCIR (50fps, interlaced)
|2/3"
|analogue
|Sony
|XC-ST70CE
|C-mount
|2
|DEI (2/2)
|
|[[media:XCST70E_manual.pdf]]
|-
|659x494
|color
|30fps
|1/4"
|FireWire 400
|Unibrain
|Fire-i 400 industrial
|C-mount
|3
|Lambrate (2/3), [[User:AlessandroMariaMauri| Alessandro Mauri]](from 20/01/10)(1/3)
|RAWSEEDS (3/3)
|http://www.unibrain.com/Products/VisionImg/Fire_i_400_Industrial.htm
|-
|659x494
|color
|30fps
|1/4"
|FireWire 400
|Unibrain
|Fire-i board camera
|proprietary
|8
|Lambrate (3/8), Bovisa (2/8), [[User:PaoloCalloni]] (1/8), [[User:DavideMigliore]] (1/8), [[User:CristianoAlessandro]] (1/8)
|RAWSEEDS (2/8), MRT (?/8)
queste sono quelle "nuove"? se si una e' su rabbiati, portiere di mrt, sin da cuvio, e' nella testa omnidir Domenicogsorrenti 21.04.09

1 nuova e' la frontale di recam

1 nuova sulla testa omnidir di ridan

|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|640x480
|color
|30fps
|1/4"
|FireWire 400
|Unibrain
|Fire-i digital camera
|fixed optics (4.3mm, f2.0)
|4
|
1 e' sulla testa omnidir di rigo

1 e' sulla testa omnidir di recam

1 e' sulla testa omnidir mrt05-03 (armadio domenico@unimib)

1 e' sulla testa omnidir mrt05-04 (armadio domenico@unimib)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_DC.htm
|-
|640x480 dual sensor, 9cm baseline
|color
|30fps
|1/3"
|FireWire 400
|Videre Design
|STOC stereo-on-a-chip stereo camera
|C-mount, fitted with two 3.5mm, f1.6, 1/2" lenses
|1
|Lambrate => li lin office => Domenicogsorrenti 13.01.09 => giulio fontana 23.01.09
|
|http://www.videredesign.com/vision/stoc.htm
|-
|640x480
|color
|60fps
|1/3"
|FireWire 400
|Videre Design
|DCSG (associated with STOC)
|C-mount, fitted with one 3.5mm, f1.6, 1/2" lens
|1
|Lambrate
|
|http://www.videredesign.com/vision/dcsg.htm
|-
|?
|color
|?
|?
|?
|ST Microelectronics
|ST1-Cam + ST2-Cam
|integrated
|2
|ST1-Cam [[User:AndreaBonarini| Andrea Bonarini]], ST2-Cam [[User:LorenzoConsolaro | Lorenzo Consolaro]] and [[User:DarioCecchetto | Dario Cecchetto]]
|
|
|-
|?
|color
|?
|?
|?
|ST Microelectronics
|ST5-CamMic + ST6-CamMic
|integrated with microphone
|2
|ST1-CamMic [[User:AndreaBonarini| Andrea Bonarini]], ST2-CamMic [[User:AndreaBonarini|Andrea Bonarini]]
|
|
|-
|?
|color
|?
|?
|?
|ST Microelectronics
|ST4-DC (Demo board)
|integrated
|1
|[[User:RaffaelePetta|Raffaele Petta]]
|
|
|}
 

==Lenses==
Be aware that sensor dimension (i.e. its diagonal, measured in fractions of an inch) is ''not'' the same for all cameras. Therefore one of the key specifications for a lens is the maximum sensor dimension supported. If you use a given lens with too big a sensor, the edges of the image will be black as they lie outside the circle of the projected image. Also beware of the strange convention used for sensor diagonals, i.e. a fraction in the form A/B" where A and B are integer ''or non-integer'' numbers. For instance an 1/2" sensor is smaller than an 1/1.8" one.
The variability of sensor dimensions has another side effect: the same lens has a different angle of view if you change the sensor size. Therefore the same lens can behave as a wide-angle with a large sensor and as a telephoto with a small sensor.

An useful guide to lenses (in Italian or English) can be found at http://www.rapitron.it/guidaob.htm.

The following is a list of the actual lenses available in the AIRLab. For each of them the main specifications (and a link to the maker's or vendor's page for full specifications) are given. A '?' means an unknown parameter: if you know its value or experimentally find out it when using the lens (e.g. the maximum sensor size), please ''update the table'' before the information is lost again! Lenses having 'M12x0.5' in Column 'mount type' are only usable with Unibrain's Fire-i board cameras. A 'YES' in the 'Mpixel' column indicates a so-called ''Megapixel lens'', i.e. a high quality, low-distortion lens designed for high-resolution industrial cameras (typically having large sensors); please note that some of these are specifically designed for B/W (i.e. black and white) cameras. The 'how many?' field tells if multiple, identical items are available. Finally, the 'where?' field tells you in which of the AIRLab sites (listed in [[The Labs]]) you can find an item, and the 'project' field is used to specify which project (if any) is using it.

Ah, one last thing. People like to actually ''find'' things when they look for them, so '''don't forget to update the table when you move something away from its current location'''. If you don't know where you are bringing it, just put your name in the table.

===C-mount and CS-mount lenses===
Industrial cameras usually have interchangeable lenses. This allows for the choice of the lens that is more suitable to the considered application. There are two main standards for industrial camera lenses: '''C-mount''' and '''CS-mount'''. Both are screw-type mounts. CS-mount is simply a modified C-mount where the distance between the back of the lens and the sensor element (CCD or CMOS) is shorter: therefore a CS-mount lens can be mounted on a C-mount camera if an ''adapter ring'' (i.e. a distancing cylinder with suitable threads) is placed between them. It is impossible, though, to use a C-mount lens on a CS-mount camera: if you try you will almost certainly break the sensor, scratch the lens, or both. Just because a lens fits a camera, it doesn't mean it can be actually mounted on it!

{| border="1" cellpadding="5" cellspacing="0"
!focal length
!max. aperture
!max. sensor size
!mount type
!maker
!model
!Mpixel
!how many?
!where?
!project
!link to full specifications
|-
|3.5mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|Lambrate
|LURCH
|?
|-
|4.0mm
|f2.0
|1/2"
|C-mount
|Microtron
|FV0420
|YES (B/W only)
|2
|DEI
|
|http://www.rapitron.it/obmegpxman1.htm
|-
|4.5mm
|f1.4
|1/2"
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|-
|4.8mm
|f1.8
|2/3"
|C-mount
|Computar
|M0518
|NO
|1
|DEI
|
|http://www.computar.com/cctvprod/computar/mono/048.html
|-
|6mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|-
|6mm
|f1.4
|1/2"
|C-mount
|Goyo
|GMHR26014MCN
|YES
|4
|DEI
|RAWSEEDS (4/4)
|http://www.goyooptical.com/products/industrial/hrmegapixel.html
|-
|8mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|-
|8mm
|f1.4
|2/3"
|C-mount
|Goyo
|GMHR38014MCN
|YES
|2
|DEI
|RAWSEEDS (2/2)
|http://www.goyooptical.com/products/industrial/hrmegapixel.html
|-
|8.5mm
|f1.3
|2/3"
|C-mount
|Computar
|?
|?
|2
|DEI
|
|(old model)
|-
|12mm
|f1.8
|2/3"
|C-mount
|?
|?
|?
|2
|DEI
|
|
|-
|12mm
|f1.4
|2/3"
|C-mount
|Goyo
|GMHR31214MCN
|YES
|1
|DEI
|
|http://www.goyooptical.com/products/industrial/hrmegapixel.html
|-
|15mm
|f2.0
|2/3"
|C-mount
|Microtron
|FV1520
|YES
|1
|DEI
|
|http://www.rapitron.it/obmegpxman1.htm
|-
|6-15mm
|f1.4
|?
|C-mount
|?
|?
|?
|1
|Lambrate
|
|?
|-
|12.5-75mm
|f1.8
|?
|C-mount
|?
|?
|?
|1
|DEI
|
|?
|}
 

===M12 lenses===
We also use M12 lenses. These lenses are very simple, with no iris, and very small. Their mounting system is an M12x0.5 metric screw thread. They are commonly used for webcams, and usually do not provide the top optical quality.

{| border="1" cellpadding="5" cellspacing="0"
!focal length
!max. aperture
!max. sensor size
!mount type
!maker
!model
!Mpixel
!how many?
!where?
!project
!link to full specifications
|-
|2.1mm
|f2.0, with IR coating
|1/4"
|M12x0.5
|Unibrain
|2042
|NO
|6
|
1 e' a bovisa nelle mani di marcello

1 e' a lambrate su un giano riusato come robowii

1 e' a bovisa sulla frontale del triskar recam

1 e' in mano a martino per fare una frontale => 06.05.09 E' in bovisa montata sul triskar #3

1 l'ha Davide Migliore per acquisizioni monoslam

1 e' sulla testa omnidir di rabbiati

Domenicogsorrenti 04.05.09
|MRT midsize, robowii, monoslam
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|4.3mm, no IR filter
|f2.0
|1/4"
|M12x0.5
|Unibrain
|2046
|NO
|1
|Lambrate (1/1)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|4.3mm
|f2.0
|1/4"
|M12x0.5
|Unibrain
|2043
|NO
|3
|Bovisa (1/3), Lambrate (2/3)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|-
|8mm
|f2.0
|1/4"
|M12x0.5
|Unibrain
|2044
|NO
|1
|Lambrate (1/1)
|
|http://www.unibrain.com/Products/VisionImg/Fire_i_BC.htm
|}
 

==Frame grabbers==
As previously said, a '''frame grabber''' is an electronic board that connects to one or more cameras, and converts the signals from the cameras into a data stream that can be elaborated by a computer. They are usually designed as expansion boards to be fitted into the computer case. Frame grabbers are necessary for ''analogue cameras'' (as they include the analogue/digital converters) or for CameraLink digital cameras (in this case the frame grabber is essentially a high speed dedicated digital interface). Other kinds of digital cameras don't need a frame grabber: this is one of the main advantages of digital cameras over analogue ones in machine vision applications, where the processing is almost always performed by computers.
In the AIRLab two models of frame grabber are available:
*a digital frame grabber from Euresys, model Expert 2, having two CameraLink inputs (http://www.euresys.com/Products/grablink/GrablinkSeries.asp). ''Notes: needs a PCI-X slot; one of the inputs is not working due to a fault.''
*two multichannel analogue frame grabbers from Matrox, model Meteor II/Multi-Channel, having three analogue inputs that can be combined into a single three-channel RGB analogue input (http://www.matrox.com/imaging/support/old_products/home.cfm). ''Note: one item is permanently mounted on the MO.RO.1 robot: see [[The MO.RO. family]] for details.''
*two multichannel analogue frame grabbers from Matrox, model Meteor II/Multi-Channel, having three analogue inputs that can be combined into a single three-channel RGB analogue input (http://www.matrox.com/imaging/support/old_products/home.cfm). ''Note: one item is permanently mounted on the MO.RO.1 robot: see [[The MO.RO. family]] for details.''
*two single-channel analogue frame grabbers from Matrox, models Meteor and Meteor Pro (http://www.matrox.com/imaging/support/old_products/home.cfm).
All the frame grabbers (except the one on the MO.RO.1) are currently in AIRLab/DEI. If you move one of them, please '''write it down here'''... and do it NOW!

==Mirrors==
Much work has been done and is being done at the AIRLab on the topic of '''omnidirectional (machine) vision''' (sometimes referred to as ''omnivision''). Omnidirectional vision systems use special hardware to overcome the limitations of conventional vision systems in terms of field of view. The approach to this problem that we generally adopt is the use of conventional cameras in association with convex '''mirrors''', i.e. the capturing of the image reflected by a suitably-shaped mirror with a camera. The possibility of designing mirrors with specific geometric properties gives a very useful means to control the geometric behaviour of the whole camera+mirror system.

TODO for someone who knows better ;-) : mirror list

==Cable==
The complete list of cable for camera connection and/or power is under construction. You can partecipate listing below which cables are you using...

{| border="1" cellpadding="5" cellspacing="0"
!Type
!length
!how many?
!where?
!project
|-
|FireWire 6-6
|?
|2
|Bicocca (refer to Domenico G. Sorrenti, 2009-11-11)
|?
|-
|FireWire 6-6
|?
|1
|on LURCH wheelchair
|LURCH
|}

User:AlessandroMariaMauri

2009-11-01T14:29:41Z

AlessandroMariaMauri:

== ''Alessandro Mauri'' ==

----

{{User
|firstname=Alessandro Maria
|lastname=Mauri
|id=739272 (676677)
|email=[mailto:alessandromaria.mauri@polimi.com alessandromaria.mauri@polimi.it]
|advisor=AndreaBonarini
|projectpage=BehaviorTiltingRobot
|photo=Alessandromauri.jpeg
}}

external e-mail: papamoretti(AT)hotmail(DOT)com 
matricola: 739272

I am a Master Student in Computer Engineering at Politecnico di Milano. 
I'm working on [[BehaviorTiltingRobot]] Project to implement a high level behaviour on [[Balancing robots: Tilty, TiltOne | Tilty]], with [[User:AndreaBonarini | Andrea Bonarini]]. 
This project is in correspondence with Laboratorio Software course.

User:AlessandroMariaMauri

2009-05-15T12:02:47Z

AlessandroMariaMauri: /* Alessandro Mauri */

== ''Alessandro Mauri'' ==

----

{{User
|firstname=Alessandro Maria
|lastname=Mauri
|id=739272 (676677)
|email=[mailto:alessandromaria.mauri@polimi.com alessandromaria.mauri@polimi.com]
|advisor=AndreaBonarini
|projectpage=BehaviorTiltingRobot
|photo=Alessandromauri.jpeg
}}

external e-mail: papamoretti(AT)hotmail(DOT)com 
matricola: 739272

I am a Master Student in Computer Engineering at Politecnico di Milano. 
I'm working on [[BehaviorTiltingRobot]] Project to implement a high level behaviour on [[Balancing robots: Tilty, TiltOne | Tilty]], with [[User:AndreaBonarini | Andrea Bonarini]]. 
This project is in correspondence with Laboratorio Software course.

User:AlessandroMariaMauri

2009-04-28T17:11:23Z

AlessandroMariaMauri: New page: == ''Alessandro Mauri'' == ---- {{User |firstname=Alessandro Maria |lastname=Mauri |id=739272 (676677) |email=[mailto:alessandromaria.mauri@polimi.com alessandromaria.mauri@polimi.com]...

== ''Alessandro Mauri'' ==

----

{{User
|firstname=Alessandro Maria
|lastname=Mauri
|id=739272 (676677)
|email=[mailto:alessandromaria.mauri@polimi.com alessandromaria.mauri@polimi.com]
|advisor=AndreaBonarini
|projectpage=BehaviorTiltingRobot
|photo=Alessandromauri.jpeg
}}

external e-mail: papamoretti@hotmail.com 
matricola: 739272

I am a Master Student in Computer Engineering at Politecnico di Milano. 
I'm working on [[BehaviorTiltingRobot]] Project to implement a high level behaviour on [[Balancing robots: Tilty, TiltOne | Tilty]], with [[User:AndreaBonarini | Andrea Bonarini]]. 
This project is in correspondence with Laboratorio Software course.

File:Alessandromauri.jpeg

2009-04-28T17:04:27Z

AlessandroMariaMauri: