Package: harvesters-util
Even though we just wanted to research image processing algorithms, why did we have to change our image acquisition library every time we change the camera that we use for the research?
- AnonymousTable of ContentsAbout HarvesterWhere is the name from?Asking questionsExternal linksFriendly collaboratorsGenTL ProducersTerminologyInstallationSystem RequirementsSupported operating systemsInstalling Harvester CoreInstalling Harvester GUILaunching Harvester GUIHow does Harvester help us?Harvester CoreHarvester GUIScreenshotsImage data visualizer windowAttribute controller windowHarvester Core on IPythonUsing HarvesterUsing Harvester CoreUsing Harvester GUIAcknowledgementsOpen source resourcesCreditsAbout HarvesterHarvester was created to be a friendly image acquisition library for all people who those want to learn computer/machine vision. Technically speaking, Harvester is a Python library which is responsible for the following tasks:Image acquisitionDevice manipulationImage data visualization (optional)Harvester consumes image acquisition libraries, so-called GenTL Producers. If you have an officially certified GenTL Producer and GenICam compliant machine vision cameras, then Harvester supplies you the acquired image data asnumpyarray to make your image processing task productive.You can freely use, modify, distribute Harvester underApache License-2.0without worrying about the use of your software: personal, internal or commercial.Currently, Harvester is being developed by the motivated contributors from all over the world.Where is the name from?Harvester’s name was coming from the great Flemish painter, Pieter Bruegel the Elder’s painting so-called “The Harvesters”. Harvesters harvest a crop every season that has been fully grown and the harvested crop is passed to the consumers. On the other hand, image acquisition libraries acquire images as their crop and the images are passed to the following processes. We found the similarity between them and decided to name our library Harvester.Apart from anything else, we love its peaceful and friendly name. We hope you also like it ;-)Pieter Bruegel the Elder, The Harvesters, 1565, (c) 2000–2018 The Metropolitan Museum of ArtAsking questionsWe have prepared a chat room in Gitter. Please don’t hesitate to drop your message when you get a question regarding Harvester!https://gitter.im/genicam-harvester/chatroomExternal linksGitHub: This is the main repository of HarvesterPyPI: This is the package distribution page of Harvester which is located in PyPIRead the Docs: You can find the API reference of Harvester Core and Harvester GUIFriendly collaboratorsSo far, Harvester has tested GenTL Producers and GenICam compliant devices from the following companies and they gave Harvester opportunities to improve its quality:Company NameCoaXPressGigE VisionUSB3 VisionCamerasActive SiliconTested--N/AAdimecN/AN/AN/ATestedAllied Vision----Automation TechnologyN/AN/AN/ATestedBaslerN/AN/AN/ATestedBaumer OptronicN/ATestedTestedTestedDAHENG VISIONN/A-TestedTestedEuresysTested--N/AFLIRN/AN/AN/ATestedGardasoftN/AN/AN/ATestedJAI--Tested-Lucid Vision LabsN/A-N/A-MATRIX VISIONN/ATestedTested-OMRON SENTECH--TestedTestedPCON/AN/AN/A-RoboceptionN/AN/AN/ATestedSICKN/A-N/A-Silicon Software---N/ASTEMMER IMAGING-TestedTestedN/AVieworks----XIMEA----Please don’t hesitate to tell us if you have tested Harvester with your GenTL Producer or GenICam compliant device. We will add your company/organization name to the list.GenTL ProducersAs of today, we have tested Harvester with the following GenTL Producers and it definitely is the shortest way to get one from the following list to get Harvester working with tangible machine vision cameras:Company NameSDK NameCamera Manufacture FreeBaumer OptronicBaumer GAPI SDKNoDAHENG VISIONMER Galaxy ViewNoJAIJAI SDKYesMatrix VisionmvIMPACT_AcquireYesOMRON SENTECHStCamUSBPackNoSTEMMER IMAGINGCommon Vision BloxYesYou might be able to directly download one at their website but please note that perhaps some of them could require you to register your information to get one. In addition, some GenTL Producers might block you to connect other competitors’ cameras.TerminologyBefore start talking about the detail, let’s take a look at some important terminologies that frequently appear in this document. These terminologies are listed as follows:The GenApi-Python Binding: A Python module that communicates with the GenICam reference implementation.A GenTL Producer: A library that has C interface and offers consumers a way to communicate with cameras over physical transport layer dependent technology hiding the detail from the consumer.The GenTL-Python Binding: A Python module that communicates with GenTL Producers.Harvester: A Python module that consists of Harvester Core and Harvester GUI.Harvester Core: A part of Harvester that works as an image acquisition engine.Harvester GUI: A part of Harvester that works as a graphical user interface of Harvester Core.A GenICam compliant device: It’s typically a camera. Just involving the GenICam reference implementation, it offers consumers a way to dynamically configure/control the target devices.The following diagram shows the hierarchy and relationship of the relevant modules:InstallationIn this section, we will learn how to instruct procedures to get Harvester work.System RequirementsThe following software modules are required to get Harvester working:Either of Python 3.4, 3.5, or 3.6In addition, you will need the following items to let Harvester make something meaningful:GenTL ProducersGenICam compliant machine vision camerasSupported operating systemsHarvester has been tested with the following operating systems:macOS 10.13Ubuntu 14.04Red Hat Enterprise Linux Workstation 7.4Windows 7Installing Harvester CoreYou can install Harvester via PyPI invoking the following command; note that the package name isharvestersbut notharvester; unfortunately, the latter word had been reserved:$pipinstallharvestersFor people who those have already installed it:$pipinstall--upgradeharvestersPerhapspipcould install cached package. If you want to install the newly dowloaded package, you should invoke the following command:$pipinstallharvesters--no-cache-dirThese commands will automatically install the required modules such asnumpyorgenicam2(the Python Binding for the GenICam GenApi & the GenTL Producers) if the module has not yet installed on your environment.Getting back to the original topic, you could install the latest development version it usingsetup.pycloning Harvester from GitHub:$gitclonehttps://github.com/genicam/harvesters.git&&cdharvesters&&pythonsetup.pyinstallInstalling Harvester GUIIf you want to use Harvester GUI, then please additionally install the following modules. Note thatPyQtis provided under LGPL and it may not be ideal for your purpose:$pipinstallPyQt5vispyIn the future, we might support other GUI frameworks which are more or less open and free.Launching Harvester GUITo launch Harvester GUI, let’s create a Python script file, namingharvester.py, that contains the following code:importsysfromPyQt5.QtWidgetsimportQApplicationfromharvesters.frontend.pyqt5importHarvesterif__name__=='__main__':app=QApplication(sys.argv)h=Harvester()h.show()sys.exit(app.exec_())Then launchharvester.py:$pythonpath/to/harvester.pyYou will see Harvester GUI pops up.How does Harvester help us?Harvester mainly consists of the following two Python modules:Harvester Core: An image acquisition engineHarvester GUI: Graphical user interface between users & Harvester CoreIn this section, we will learn what Harvester offers us through these components.Harvester CoreHarvester Core is an image acquisition engine. No GUI. You can use it as an image acquisition library which acquires images from GenTL Producers through the GenTL-Python Binding and controls the target device (it’s typically a camera) through the GenApi-Python Binding.Harvester Core works as a minimalistic front-end for image acquisition. Just importing it from your Python script, you should immediately be able to set images on your table.You’ll be able to download the these language binding runtime libraries from theEMVA website, however, it’s not available as of May 2018, because they have not officially released yet. Fortunately they are in the final reviewing process so hopefully they’ll be released by the end of 2018.If you don’t have to care about the display rate for visualizing acquired images, the combination of Harvester Core andMatplotlibmight be a realistic option for that purpose.Tasks Harvester Core does for youThe main features of Harvester Core are listed as follows:Image acquisition through GenTL ProducersMultiple loading of GenTL Producers in a single Python scriptGenICam feature node manipulation of the target deviceNote that the second item implies you can involve multiple types of transport layers in your Python script. Each transport layer has own advantages and disadvantages and you should choose appropriate transport layers following your application’s requirement. You just need to acquire images for some purposes and the GenTL Producers deliver the images somehow. It truly is the great benefit of the GenTL Standard! And of course, not only GenTL Producers but Harvester Core offer you a way to manipulate multiple devices in a single Python script with an intuitive manner.On the other hand, Harvester Core could be considered as a simplified version of the GenTL-Python Binding; actually, Harvester Core hides it in its back and shows only intuitive interfaces to its clients. Harvester Core just offers you a relationship between you and a device. Nothing more. We say it again, just you and a device. If you need to manipulate more relevant GenTL modules or have to achieve something over a hardcore way, then you should directly work with the GenTL-Python Binding.Pixel formats that Harvester Core supportsCurrently, Harvester Core supports the following pixel formats that are defined by the Pixel Format Naming Convention:Mono8,Mono10,Mono12,Mono16,RGB8,RGBa8,BayerRG8,BayerGR8,BayerBG8,BayerGB8,BayerRG16,BayerGR16,BayerBG16,BayerGB16Harvester GUIHarvester GUI works on the top of Harvester Core and offers you high-performance image data visualization on the fly. It involves VisPy for controlling OpenGL functionality and PyQt for providing GUI.Tasks Harvester GUI does for youThe main features of Harvester GUI are listed as follows:Image data visualization of the acquired imagesImage magnification using a mouse wheel or a trackpadImage dragging using a mouse or a trackpadAn arbitrary selection of image displaying point in the data path (Not implemented yet)Unlike Harvester Core, Harvester GUI limits the number of GenTL Producers to load just one. This is just a limitation to not make the GUI complicated. In general, the user should know which GenTL Producer should be loaded to control his target device. It’s not necessary to load multiple GenTL Producers for this use case. However, this is just an idea in an early stage. We might support multiple loading on even Harvester GUI in the future.Pixel formats that Harvester GUI supportsCurrently, Harvester GUI supports the following pixel formats that are defined by the Pixel Format Naming Convention:Mono8,Mono10,Mono12,Mono16,RGB8,RGBa8,BayerRG8,BayerGR8,BayerBG8,BayerGB8,BayerRG16,BayerGR16,BayerBG16,BayerGB16Note that Harvester GUI has not yet supported demosaicing.ScreenshotsIn this section, we see some useful windows which Harvester offers you.Image data visualizer windowThe image data visualizer window (below) offers you a visualization of the acquired images. In this screenshot, Harvester is acquiring a 4000 x 3000 pixel of RGB8 image at 30 fps; it means it’s acquiring images at 8.6 Gbps. It’s quite fast, isn’t it?Attribute controller windowThe attribute controller window (below) offers you to manipulate GenICam feature nodes of the target device. Changing exposure time, triggering the target device for image acquisition, storing a set of camera configuration so-called User Set, etc, you can manually control the target device anytime when you want to. It supports the visibility filter feature and regular expression feature. These features are useful in a case where you need to display only the features you are interested in.Harvester Core on IPythonThe following screenshot shows Harvester Core is running on IPython. Harvester Core returns the latest image data at the moment as a Numpy array every time its user call theget_image()method. Once you get an image you should be able to immediately start image processing. If you’re running on the Jupyter notebook, you should be able to visualize the image data using Matplotlib. This step should be helpful to check what’s going on your trial in the image processing flow.In[1]:fromharvesters.coreimportHarvesterIn[2]:importnumpyasnpIn[3]:h=Harvester()In[4]:h.add_cti_file('/Users/kznr/dev/genicam/bin/Maci64_x64/TLSimu.cti')In[5]:h.update_device_info_list()In[6]:h.device_info_listOut[6]:[(id_='TLSimuMono',vendor='EMVA_D',model='TLSimuMono',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceA_0',version='1.2.3'),(id_='TLSimuColor',vendor='EMVA_D',model='TLSimuColor',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceA_1',version='1.2.3'),(id_='TLSimuMono',vendor='EMVA_D',model='TLSimuMono',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceB_0',version='1.2.3'),(id_='TLSimuColor',vendor='EMVA_D',model='TLSimuColor',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceB_1',version='1.2.3')]In[7]:iam=h.create_image_acquisition_manager(serial_number='SN_InterfaceA_0')In[8]:iam.device.node_map.Width.value,iam.device.node_map.Height.value=8,8In[9]:iam.device.node_map.PixelFormat.value='Mono8'In[10]:iam.start_image_acquisition()In[11]:buffer=iam.fetch_buffer()In[12]:type(buffer)Out[12]:harvesters.core.BufferIn[13]:type(buffer.payload)Out[13]:harvesters.core.PayloadImageIn[14]:len(buffer.payload.components)Out[14]:1In[15]:type(buffer.payload.components[0])Out[15]:harvesters.core.Component2DIn[16]:type(buffer.payload.components[0].data)Out[16]:numpy.ndarrayIn[17]:buffer.payload.components[0].dataOut[17]:array([[153,154,155,156,157,158,159,160],[154,155,156,157,158,159,160,161],[155,156,157,158,159,160,161,162],[156,157,158,159,160,161,162,163],[157,158,159,160,161,162,163,164],[158,159,160,161,162,163,164,165],[159,160,161,162,163,164,165,166],[160,161,162,163,164,165,166,167]],dtype=uint8)In[18]:buffer.queue()In[19]:withiam.fetch_buffer()asbuffer:...:image=buffer.payload.components[0].data...:print('Average:{0}'.format(np.average(image)))...:print(image)...:Average:218.0[[211212213214215216217218][212213214215216217218219][213214215216217218219220][214215216217218219220221][215216217218219220221222][216217218219220221222223][217218219220221222223224][218219220221222223224225]]In[20]:iam.stop_image_acquisition()In[21]:iam.destroy()Using HarvesterUsing Harvester CoreFirst, let’s import Harvester:fromharvesters.coreimportHarvesterThen instantiate a Harvester object; we’re going to usehthat stands for
Harvester as its identifier.h=Harvester()And load a CTI file; loading a CTI file, you can communicate with the GenTL
Producer:h.add_cti_file('path/to/gentl_producer.cti')Note that you can addone or more CTI fileson a single Harvester Core object. To add another CTI file, just repeat callingadd_cti_filemethod passing another target CTI file:h.add_cti_file('path/to/another_gentl_producer.cti')And the following code will let you know the CTI files that have been loaded
on the Harvester object:h.cti_filesIn a contrary sense, you can remove a specific CTI file that you have added with the following code:h.remove_cti_file('path/to/gentl_producer.cti')And now yol have to update the list of devices; it fills up your device
information list and you’ll select a device to control from the list:h.update_device_info_list()The following code will let you know the devices that you can control:h.device_info_listOur friendly GenTL Producer, so called TLSimu, gives you the following information:[(unique_id='TLSimuMono',vendor='EMVA_D',model='TLSimuMono',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceA_0',version='1.2.3'),(unique_id='TLSimuColor',vendor='EMVA_D',model='TLSimuColor',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceA_1',version='1.2.3'),(unique_id='TLSimuMono',vendor='EMVA_D',model='TLSimuMono',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceB_0',version='1.2.3'),(unique_id='TLSimuColor',vendor='EMVA_D',model='TLSimuColor',tl_type='Custom',user_defined_name='Center',serial_number='SN_InterfaceB_1',version='1.2.3')]And you create an image acquisition manager object specifying a target device. The image acquisition manager does the image acquisition task for you. In the following example it’s trying to create an manager object of the first candidate device in the device information list:iam=h.create_image_acquisition_manager(0)Or equivalently:iam=h.create_image_acquisition_manager(list_index=0)You can connect the same device passing more unique information to the method such as:mono_a=h.create_image_acquisition_manager(serial_number='SN_InterfaceA_0')We named the manager objectiamin the above example but in a practical occasion, you may name it like justcamera,mono_cam, orface_detection_cammore specifically even though those entities don’t acquire images by themselves but they transfer images that will be acquired by their image acquisition manager.Anyway, then now we start image acquisition:iam.start_image_acquisition()Once you started image acquisition, you should definitely want to get an image. An image is delivered to a buffer manager object. To fetch a buffer that has been filled up with an image, you can have 2 options; the first option is to use thewithstatement:withiam.fetch_buffer()asbuffer:# Work with the Buffer object. It consists of everything you need.print(buffer)# The buffer will automatically be queued.Having that code, the fetched buffer is automatically queued once the code step out from the scope of thewithstatement. It’s prevents you to forget queueing it by accident. The other option is to manually queue the fetched buffer by yourself:buffer=iam.fetch_buffer()print(buffer)# Don't forget to queue the buffer.buffer.queue()In this option, again, please do not forget that you have to queue the buffer by yourself. If you forget queueing it, then you’ll lose a buffer that could be used for image acquisition. Everything is up to your design, so please choose an appropriate way for you. In addition, once you queued the buffer, the Buffer object will be obsolete. There’s nothing to do with it.Okay, then you would stop image acquisition with the following code:iam.stop_image_acquisition()And the following code disconnects the connecting device from the image acquisition manager; you’ll have to create an image acquisition manager object again when you have to work with a device:iam.destroy()Now you can quit the program! Please not that the image acquisition manager also supports thewithstatement. So you may write program as follows:withh.create_image_acquisition_manager(0)asiam:# Work, work, and work with the iam object.# the iam object will automatically call the destroy method.Using Harvester GUIHarvester GUI :: Image data visualizer windowImage data visualizer window :: ToolbarMost of Harvester GUI’s features can be used through its toolbox. In this section, we describe each button’s functionality and how to use it. Regarding shortcut keys, replaceCtrlwithCommandon macOS.Selecting a CTI fileThis button is used to select a GenTL Producer file to load. The shortcut key isCtrl+o.Updating the device information listThis button is used to update the device information list; the list will be filled up with the devices that are handled by the GenTL Producer that you have loaded on Harvester GUI; sometime it might be empy if there’s no device is available. The shortcut key isCtrl+u. It might be useful when you newly connect a device to your system.Selecting a GenICam compliant deviceThis combo box shows a list of available GenICam compliant devices. You can select a device that you want to control. The shortcut key isCtrl+D, i.e.,Ctrl+Shift+d.Connecting a selected device to HarvesterThis button is used to connect a device which is being selected by the former combo box. The shortcut key isCtrl+c. Once you connect the device, the device is exclusively controlled.Disconnecting the connecting device from HarvesterThis button is used to disconnect the connecting device from Harvester. The shortcut key isCtrl+d.Starting image acquisitionThis button is used to start image acquisition. The shortcut key isCtrl+j. The acquired images will be drawing in the following canvas pane.Pausing/Resuming image drawingThis button is used to pausing/resuming drawing images on the canvas pane while it’s keep acquiring images in the background. The shortcut key isCtrl+k. If you want to resume drawing images, just click the button again. You can do the same thing with the start image acquisition button (Ctrl+j).Stopping image acquisitionThis button is used to stop image acquisition. The shortcut key isCtrl+l.Showing the device attribute dialogThis button is used to show the device attribute dialog. The shortcut key isCtrl+a. The device attribute dialog offers you to a way to intuitively control device attribute over a GUI.Showing the about dialogThis button is used to show the about dialog.Image data visualizer window :: CanvasThe canvas of Harvester GUI offers you not only image data visualization but also some intuitive object manipulations.Zooming into the displayed imageIf you’re using a mouse, spin the wheel to your pointing finger points at. If you are using a trackpad on a macOS, slide two fingers to the display side.Zooming out from the displayed imageIf you’re using a mouse, spin the wheel to your side. If you are using a trackpad on a macOS, slide two fingers to your side.Changing the part being displayedIf you’re using a mouse, grab any point in the canvas and drag the pointer as if you’re physically grabbing the image. The image will follow the pointer. If you are using a trackpad on a macOS, it might be useful if you assign the three finger slide for dragging.Harvester GUI :: Attribute controller windowThe attribute controller offers you an interface to each GenICam feature node that the the target device provides.Attribute controller window :: ToolbarFiltering GenICam feature nodes by visibilityThis combo box offers you to apply visibility filter to the GenICam feature node tree. The shortcut key isCtrl+vGenICam defines the following visibility levels:Beginner: Features that should be visible for all users via the GUI and API.Expert: Features that require a more in-depth knowledge of the camera functionality.Guru: Advanced features that might bring the cameras into a state where it will not work properly anymore if it is set incorrectly for the cameras current mode of operation.Invisible: Features that should be kept hidden for the GUI users but still be available via the API.The following table shows each item in the combo box and the visibility status of each visibility level:Combo box itemBeginnerExpertGuruInvisibleBeginnerVisibleInvisibleInvisibleInvisibleExpertVisibleVisibleInvisibleInvisibleGuruVisibleVisibleVisibleInvisibleAllVisibleVisibleVisibleVisibleFiltering GenICam feature nodes by regular expressionThis text edit box offers you to filter GenICam feature nodes by regular expression.Expanding the feature node treeThis button is used to expand the feature node tree. The shortcut key isCtrl+e.Collapsing the feature node treeThis button is used to collapse the feature node tree. The shortcut key isCtrl+c.AcknowledgementsOpen source resourcesHarvester Core uses the following open source libraries/resources:PymplerLicense:Apache License, Version 2.0Copyright (c) Jean Brouwers, Ludwig Haehne, Robert Schuppenieshttps://pythonhosted.org/Pympler/https://github.com/pympler/pymplerhttps://pypi.org/project/Pympler/VersioneerLicense:The Creative Commons “Public Domain Dedication” license  (CC0-1.0)Copyright (c) 2018 Brian Warnerhttps://github.com/warner/python-versioneerHarvester GUI uses the following open source libraries/resources:VisPyLicense:BSD 3-ClauseCopyright (c) 2013-2018 VisPy developershttp://vispy.orghttps://github.com/vispy/vispyPyQt5License:GPLv3Copyright (c) 2018 Riverbank Computing Limitedhttps://www.riverbankcomputing.comhttps://pypi.org/project/PyQt5/Icons8License:Creative Commons Attribution-NoDerivs 3.0 UnportedCopyright (c) Icons8 LLChttps://icons8.comCreditsThe initial idea about Harvester suddenly came up to a software engineer, Kazunari Kudo’s head in the early April of year 2018 and he immediately decided to bring the first prototype to the International Vision Standards Meeting, IVSM in short, that was going to be held in Frankfurt am Main in the following early May. During the Frankfurt IVSM, interested engineers tried out Harvester and confirmed it really worked using commercial machine vision cameras provided by well-known machine vision camera manufacturers in the world. Having that fact, the attendees of the IVSM warmly welcomed Harvester.The following individuals have directly or indirectly contributed to the development activity of Harvester or encouraged the developers by their thoughtful warm words; they are our respectable wonderful colleagues:Rod Barman, Stefan Battmer, David Beek, Jan Becvar, David Bernecker, Chris Beynon, Eric Bourbonnais, Benedikt Busch, George Chamberlain, Thomas Detjen, Friedrich Dierks, Dana Diezemann, Emile Dodin, Reynold Dodson, Sascha Dorenbeck, Erik Eloff, Katie Ensign, Andreas Ertl, James Falconer, Werner Feith, Maciej Gara, Andreas Gau, Sebastien Gendreau, Francois Gobeil, Werner Goeman, Jean-Paul Goglio, Markus Grebing, Eric Gross, Ioannis Hadjicharalambous, Uwe Hagmaier, Tim Handschack, Christopher Hartmann, Reinhard Heister, Gerhard Helfrich, Jochem Herrmann, Heiko Hirschmueller, Tom Hopfner, David Hoese, Karsten Ingeman Christensen, Severi Jaaskelainen, Mattias Johannesson, Mark Jones, Mattias Josefsson, Martin Kersting, Stephan Kieneke, Tom Kirchner, Lutz Koschorreck, Frank Krehl, Maarten Kuijk, Max Larin, Ralf Lay, Min Liu, Sergey Loginonvskikh, Thomas Lueck, Alain Marchand, Rocco Matano, Masahide Matsubara, Stephane Maurice, Robert McCurrach, Mike Miethig, Thies Moeller, Roman Moie, Marcel Naggatz, Hartmut Nebelung, Damian Nesbitt, Quang Nhan Nguyen, Klaus-Henning Noffz, Neerav Patel, Jan Pech, Merlin Plock, Joerg Preckwinkel, Benjamin Pussacq, Dave Reaves, Thomas Reuter, Andreas Rittinger, Ryan Robe, Nicolas P. Rougier, Felix Ruess, Matthias Schaffland, Michael Schmidt, Jan Scholze, Martin Schwarzbauer, Rupert Stelz, Madhura Suresh, Chendra Hadi Suryanto, Timo Teifel, Albert Theuwissen, Laval Tremblay, Tim Vlaar, Silvio Voitzsch, Stefan Von Weihe, Frederik Voncken, Roman Wagner, Ansger Waschki, Anne Wendel, Jean-Michel Wintgens, Manfred Wuetschner, Jang Xu, Christoph Zierl, and Juraj Zopp