diff --git a/PlusLib/src/DataCollection/ICCapturing/DeviceICCapturing.dox b/PlusLib/src/DataCollection/ICCapturing/DeviceICCapturing.dox index 8317a1603..09b4042ab 100644 --- a/PlusLib/src/DataCollection/ICCapturing/DeviceICCapturing.dox +++ b/PlusLib/src/DataCollection/ICCapturing/DeviceICCapturing.dox @@ -1,9 +1,10 @@ /*! -\page DeviceICCapturing +\page DeviceICCapturing Imaging controls analog USB framegrabber \section ICCapturingSupportedHwDevices Supported hardware devices +Supported model: DFG/USB2pro analog framegrabbers with USB interface -- Link to manufacturer's website: +- Link to manufacturer's website: http://www.theimagingsource.com/en_US/products/converters/ \section ICCapturingSupportedPlatforms Supported platforms - \ref PlatformWin32 @@ -24,7 +25,7 @@ - \xmlElem \ref DataSources: - \xmlElem \ref DataSource: there must be one child element - \xmlAtt \ref PortUsImageOrientation \RequiredAtt - - \xmlAtt \ref ImageType \OptionalAtt{BRIGHTNESS} + - \xmlAtt \ref ImageType. Color image acquisition is supported. \OptionalAtt{BRIGHTNESS} - \xmlAtt \ref BufferSize \OptionalAtt{150} - \xmlAtt \ref AveragedItemsForFiltering \OptionalAtt{20} diff --git a/PlusLib/src/DataCollection/Interson/DeviceInterson.dox b/PlusLib/src/DataCollection/Interson/DeviceInterson.dox index ef8807d80..5fa8e578c 100644 --- a/PlusLib/src/DataCollection/Interson/DeviceInterson.dox +++ b/PlusLib/src/DataCollection/Interson/DeviceInterson.dox @@ -1,9 +1,11 @@ /*! -\page DeviceInterson +\page DeviceInterson Interson USB ultrasound probes \section IntersonSupportedHwDevices Supported hardware devices +SeeMore probes -- Link to manufacturer's website: + +- Link to manufacturer's website: http://www.interson.com/products/seemore-153-usb-probes \section IntersonSupportedPlatforms Supported platforms - \ref PlatformWin32 @@ -14,17 +16,20 @@ \section IntersonInstallation Installation +Limitations: imaging parameters are hardcoded, makeing them configurable is a work in progress, see details in #864 +Requires SDK provided by Interson for compilation and USB drivers provided by Interson for running (otherwise Plus application will not start due to missing WDAPI1010.dll). + \section IntersonConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "Interson" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "IntersonVideo" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{125} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} - \xmlElem \ref DataSources: - \xmlElem \ref DataSource: there must be one child element - \xmlAtt \ref PortUsImageOrientation \RequiredAtt - - \xmlAtt \ref ImageType \OptionalAtt{BRIGHTNESS} + - \xmlAtt \ref ImageType Supported imaging modes: B-mode \OptionalAtt{BRIGHTNESS} - \xmlAtt \ref BufferSize \OptionalAtt{150} - \xmlAtt \ref AveragedItemsForFiltering \OptionalAtt{20} diff --git a/PlusLib/src/DataCollection/MicrosoftMediaFoundation/DeviceMicrosoftMediaFoundation.dox b/PlusLib/src/DataCollection/MicrosoftMediaFoundation/DeviceMicrosoftMediaFoundation.dox index d94a54253..300d9d336 100644 --- a/PlusLib/src/DataCollection/MicrosoftMediaFoundation/DeviceMicrosoftMediaFoundation.dox +++ b/PlusLib/src/DataCollection/MicrosoftMediaFoundation/DeviceMicrosoftMediaFoundation.dox @@ -1,8 +1,8 @@ /*! -\page DeviceMicrosoftMediaFoundation +\page DeviceMicrosoftMediaFoundation Microsoft Media Foundation compatible imaging device \section MicrosoftMediaFoundationSupportedHwDevices Supported hardware devices - +Any compatible framegrabbers and webcams through Microsoft Media Foundation interface. - Link to manufacturer's website: \section MicrosoftMediaFoundationSupportedPlatforms Supported platforms @@ -17,7 +17,7 @@ \section MicrosoftMediaFoundationConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "MicrosoftMediaFoundation" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "MmfVideo" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{125} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} diff --git a/PlusLib/src/DataCollection/NDICertusTracking/DeviceNDICertus.dox b/PlusLib/src/DataCollection/NDICertusTracking/DeviceNDICertus.dox index bbe539303..dba6f614a 100644 --- a/PlusLib/src/DataCollection/NDICertusTracking/DeviceNDICertus.dox +++ b/PlusLib/src/DataCollection/NDICertusTracking/DeviceNDICertus.dox @@ -1,23 +1,114 @@ /*! -\page DeviceNDICertus +\page DeviceNDICertus NDI Optotrak Certus optical pose tracker \section NDICertusSupportedHwDevices Supported hardware devices -- Link to manufacturer's website: +- Link to manufacturer's website: http://www.ndigital.com/msci/products/optotrak-certus/ \section NDICertusSupportedPlatforms Supported platforms - \ref PlatformWin32 -- \ref PlatformWin64 - \ref PlatformWin32Embedded - \ref PlatformMacOs - \ref PlatformLinux \section NDICertusInstallation Installation +\subsection NDICertusInstallCommon Install common software + +Before setting up anything about the device or the connection, some software has to be installed. +- Device drivers (\\image\shared\data\lab.hardware\NDITrackers\NDICertus\OptotrakDeviceDrivers_v3.5.2\OptotrakDeviceDrivers_v3.5.2\setup.exe) +- NDI First Principles software (\\image\shared\data\lab.hardware\NDITrackers\NDICertus\FirstPrinciples_v1.2.2\setup.exe) + +\subsection NDICertusComumnicationPCI Communicating Certus tracker by PCI card +PCI card installation. To install an NDI PCI drivers card you will need: +- This guide: [[Media:Optotrak_PCI_Interface_Card_Installation_Guide(IL-1070037).pdf |Optotrak PCI Interface Card Installation Guide, Rev. 3.0]] +- an NDI PCI interface card +- the NDI PCI drivers CD (NDIDeviceDrivers_v3.00.66) * + - Goodwin 757, NDI tools cabinet + - Copy at the image server (\\image\shared\data\lab.hardware\NDITrackers\NDIDeviceDrivers_v3.00.66) + +Ultrasound machines equipped with NDI PCI card: +- [http://media.cs.queensu.ca/media/wiki/index.php/Using_and_programming_the_Ultrasonix_machine#SonixRP-1 SonixRP-1] +- [http://media.cs.queensu.ca/media/wiki/index.php/Using_and_programming_the_Ultrasonix_machine#SonixRP-2 SonixRP-2] + +\subsection NDICertusComumnicationEthernet Communicating Certus tracker by via ethernet + +\subsubsection NDICertusSetUpPC How to set up your PC + +Install the following packages from the image server: +- OptotrakDeviceDrivers (\\image\shared_data\data\lab.hardware\NDITrackers\NDICertus\0_OptotrakDeviceDrivers_v3.5.2): + - Install '''Optotrak Link Drivers (Required)''' - you may need to reboot your computer. +[[Image:OptotrakDeviceDriversInstall.jpg|center]] +- OptoUpdate (\\image\shared_data\data\lab.hardware\NDITrackers\NDICertus\1_OptoUpdate_3.5.2): + - Click on the '''Update the system to v3.01''' button and select the '''Do Not Search for Hardware Components (Update Software Only)''' choice. +[[Image:OptotrakOptoUpdateInstall.jpg|center]] +- FirstPrinciples (\\image\shared_data\data\lab.hardware\NDITrackers\NDICertus\2_FirstPrinciples_v1.2.2): + - Install First Principles with the default values. +- 6DA_Optotrak (\\image\shared_data\data\lab.hardware\NDITrackers\NDICertus\3_6DA_Optotrak_1.3.3): + - Install 6DA_Optotrak with the default values. +- NDI DataView (\\image\shared_data\data\lab.hardware\NDITrackers\NDICertus\4_NDI_DataView_Version_1.00.03): + - Install NDI DataView with the default values. +- Copy the '''standard.cam''' and '''system.nif''' files to "c:\ndigital\realtime" folder (\\image\shared_data\data\lab.hardware\NDITrackers\NDICertus\5_Copy_To_ndigital_realtime) + +Change NDI settings file (by default optotrak.ini file is located in the "C:\ndigital\settings" folder) + +- Set ''Driver'' to ''etherlink.dll'' + - Copy ''etherlink.dll'' to the "c:\ndigital\programs" folder from "c:\ndigital\drivers" +- Set ''ResetTimeout''' to 500 and ''PropagationTimeout''' to 5000 (recommended in the manual but maybe not vital) +- Set ''Server Address'' to the NDI SCU IP (130.15.7.98) +- ''Control Port'' should be 9999, ''Data Port'' should be 10000 +- ''Data Timeout'' should be 10000 and ''Reset Delay'' should be between 5000 and 10000 (also recommended in the manual) + +If you made these changes, the NDI will work via ethernet. If you want to use the PCI card again, you have to undo these changes (the most important thing is to set ''Driver'' to ''pcilink.dll'' + + +\subsubsection NDICertusSetUpSCU How to set up the System Control Unit (SCU) +Change ethernet settings in NDI SCU ''(Note: this has to be done only when SCU, gateway or DNS IP address is changed)'' +- Connect Serial cable to the SCU and a Serial-to-USB adaptor cable, then the USB into a computer +- Connect to SCU using MTTTY (COM port can be read from Device Manager) +- Commands (Read: [Read command name] , Write: [Write command name][Value]) + - ENDHRD Reads the DHCP status + - ENDHWR Sets the DHCP status + - ENGWRD Reads the gateway address + - ENGWWR Sets the gateway address + - ENIPRD Reads the IP address + - ENIPWR Sets the IP address + - ENNMRD Reads the Ethernet host name + - ENNMWR Sets the Ethernet host name + - ENSMRD Reads the subnet mask + - ENSMWR Sets the subnet mask +- Current settings + - IP: 130.15.7.98 + - Gateway: 130.15.7.1 + - (DNS: 130.15.1.101) + - (DNS alternate: 130.15.1.11) + - Subnet mask: 255.255.255.0 + - Name: CERTUS061 + +\subsection NDICertusUsage How to use the NDI Certus optical tracker + +User guide: [[Media:Optotrak_Certus_User_Guide.pdf | Optotrak Certus User Guide rev. 2.0]] + + +\subsection NDICertusCoordinateSystems Coordinate systems + +Tracker \c (Left-handed) +- X+: up (against gravity) +- Y+: to the right (if we face the camera) +- Z+: away from the camera + +Reference DRB \c (Right-handed). The orientation of the DRB is the following: the side with the writing on it is on the far side from the camera and the screw points to the ground. + - X+: to the left (if we face the camera) + - Y+: up (against gravity) + - Z+: towards the camera + +No "beeps" when attempting to connect to a Certus tracker => Power off the OptoTrak Certus camera and communication unit for a few seconds and try to connect again +If no Certus device is attached to the system then the application crashes (due to the TransputerDetermineSystemCfg call in NDI's toolkit, which determines the system configuration causes the application to crash) + \section NDICertusConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "NDICertus" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "CertusTracker" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{50} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} - \xmlAtt \ref ToolReferenceFrame \OptionalAtt{Tracker} diff --git a/PlusLib/src/DataCollection/OpenIGTLinkTracking/DeviceOpenIGTLink.dox b/PlusLib/src/DataCollection/OpenIGTLinkTracking/DeviceOpenIGTLink.dox index 42031dcd9..49245e615 100644 --- a/PlusLib/src/DataCollection/OpenIGTLinkTracking/DeviceOpenIGTLink.dox +++ b/PlusLib/src/DataCollection/OpenIGTLinkTracking/DeviceOpenIGTLink.dox @@ -1,9 +1,17 @@ /*! -\page DeviceOpenIGTLink +\page DeviceOpenIGTLink Any OpenIGTLink compatible tracker \section OpenIGTLinkSupportedHwDevices Supported hardware devices +Any compatible tracker device through OpenIGTLink interface. +Any tracker device that are supported by the IGSTK toolkit can be used in Plus by using this OpenIGTLink interface -- Link to manufacturer's website: +- There are commercial systems that provide tracking coordinates and image data through OpenIGTLink, e.g., BrainLab + -BrainLab OpenIGTLink interface may be purchased as a license option with VectorVision Cranial 2.1. + - Contact BrainLab for information about licensing and for supported OpenIGTLink options. + - For tracking data, the BrainLab OpenIGTLink interface uses the TDATA message type, which is supported by PLUS 2.0 as of r2337 + - In the configuration section for OpenIGTLinkTracker Device, set MessageType="TDATA" and ReconnectOnReceiveTimeout="false" (to avoid reconnects, as BrainLab asks for manual confirmation on each connect request) + - See ConfigFiles/BWH directory for example configurations using BrainLab tracking. + - Receiving live data from 3D Slicer: set \c UseReceivedTimestamps="false" and \c UseLastTransformsOnReceiveTimeout="true" (as Slicer only sends transforms when they change) \section OpenIGTLinkSupportedPlatforms Supported platforms - \ref PlatformWin32 @@ -17,7 +25,7 @@ \section OpenIGTLinkConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "OpenIGTLink" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "OpenIGTLinkTracker" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{30} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} - \xmlAtt \ref ToolReferenceFrame \OptionalAtt{Tracker} diff --git a/PlusLib/src/DataCollection/OpenIGTLinkVideo/DeviceOpenIGTLinkVideo.dox b/PlusLib/src/DataCollection/OpenIGTLinkVideo/DeviceOpenIGTLinkVideo.dox index 5abeeb883..79c808e05 100644 --- a/PlusLib/src/DataCollection/OpenIGTLinkVideo/DeviceOpenIGTLinkVideo.dox +++ b/PlusLib/src/DataCollection/OpenIGTLinkVideo/DeviceOpenIGTLinkVideo.dox @@ -1,9 +1,10 @@ /*! -\page DeviceOpenIGTLinkVideo +\page DeviceOpenIGTLinkVideo Any OpenIGTLink compatible imaging device \section OpenIGTLinkVideoSupportedHwDevices Supported hardware devices +Any compatible video device through OpenIGTLink interface. +There are commercial systems that provide tracking video and image data through OpenIGTLink, such as BrainLab, Siemens MRI scanners -- Link to manufacturer's website: \section OpenIGTLinkVideoSupportedPlatforms Supported platforms - \ref PlatformWin32 diff --git a/PlusLib/src/DataCollection/PhidgetSpatialTracking/DevicePhidgetSpatial.dox b/PlusLib/src/DataCollection/PhidgetSpatialTracking/DevicePhidgetSpatial.dox index d64f67fdb..e14d1c5f2 100644 --- a/PlusLib/src/DataCollection/PhidgetSpatialTracking/DevicePhidgetSpatial.dox +++ b/PlusLib/src/DataCollection/PhidgetSpatialTracking/DevicePhidgetSpatial.dox @@ -1,16 +1,18 @@ /*! -\page DevicePhidgetSpatial +\page DevicePhidgetSpatial Phidgets Spatial 3/3/3 magnetic, angular rate, and gravity (MARG) sensor \section PhidgetSpatialSupportedHwDevices Supported hardware devices -- Link to manufacturer's website: +Contains accelerometer, gyroscope, and magnetometer sensors, each with 3 DOF +Small (few centimeters by few centimeters), low-cost (about $150) device +Gyroscope bias correction is performed at connection, therefore after the connection is initialized in Plus the device shall be kept stationary for 2 seconds. + +- Link to manufacturer's website: http://www.phidgets.com/products.php?product_id=1044_0 \section PhidgetSpatialSupportedPlatforms Supported platforms - \ref PlatformWin32 - \ref PlatformWin64 - \ref PlatformWin32Embedded -- \ref PlatformMacOs -- \ref PlatformLinux \section PhidgetSpatialInstallation Installation diff --git a/PlusLib/src/DataCollection/PolarisTracking/DevicePolaris.dox b/PlusLib/src/DataCollection/PolarisTracking/DevicePolaris.dox index 6807774fc..dbfc7c484 100644 --- a/PlusLib/src/DataCollection/PolarisTracking/DevicePolaris.dox +++ b/PlusLib/src/DataCollection/PolarisTracking/DevicePolaris.dox @@ -1,35 +1,42 @@ /*! -\page DevicePolaris +\page DevicePolaris NDI pose trackers \section PolarisSupportedHwDevices Supported hardware devices + Polaris optical and Aurora electromagnetic pose trackers -- Link to manufacturer's website: \section PolarisSupportedPlatforms Supported platforms - \ref PlatformWin32 -- \ref PlatformWin64 - \ref PlatformWin32Embedded - \ref PlatformMacOs - \ref PlatformLinux \section PolarisInstallation Installation - - +Uses the NDI Combined API C Interface Library (ndicapi). +Drivers should be installed to allow the computer to connect to the SCU. Detailed instructions can be found in the Hybrid Polaris Spectra User Guide, which comes with the system. +If you have just turned on the tracker and attempt to use it right away, you may get the error message "command is invalid while in current mode"; wait for the leftmost LED on the position sensor to stop flashing and try again. +Active (wired) tools does not seem to work with Polaris Spectra. The issue is tracked in #510. \section PolarisConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "PolarisTracker" \RequiredAtt OR "Type" = \c "AuroraTracker" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "PolarisTracker" \RequiredAtt OR \ref DeviceType "Type" = \c "AuroraTracker" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{50} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} - \xmlAtt \ref ToolReferenceFrame \OptionalAtt{Tracker} +- \b SerialPort parameter must correlate to the com port number used by the NDI Polaris Spectra SCU Port. This port number was determined during driver installation, to check its value go to control panel->Device Manager->Ports(COM&LPT) and you should see an icon labelled NDI Polaris Spectra SCU Port(COMx), with x representing the COM port number you need to specify in the config file. +- \b BaudRate specifies the speed of the COM port, the recommended value is 115200. + - NOTE: Some computers are unable to connect to the NDI Polaris if the COM port in device manager is > 4. If you see this, reassign the COM port to <= 4. + + - \xmlElem \ref DataSources: - \xmlElem \ref DataSource: there must be one child element - - \xmlAtt \ref RomFile \RequiredAtt + - \xmlAtt \ref RomFile For each passive (wireless) tool the following parameters shall be specified: PortName: any chosen number between 4 and 15 (must be unique for each tool). RomFile: name of the tool definition file (*.rom files), the location is relative to the configuration file location. Standard tool rom files are located on the NDI Polaris Spectra Tool Kit cd in the Tool Definition Files folder. \RequiredAtt - \xmlAtt \ref BufferSize \OptionalAtt{150} - \xmlAtt \ref AveragedItemsForFiltering \OptionalAtt{20} \section PolarisExampleConfigFile Example configuration file \include "data/ConfigFiles/PlusDeviceSet_Server_Polaris.xml" +\include "PlusConfiguration_NoVideo_NDIPolaris.xml" */ \ No newline at end of file diff --git a/PlusLib/src/DataCollection/SavedDataSource/DeviceSavedDataSource.dox b/PlusLib/src/DataCollection/SavedDataSource/DeviceSavedDataSource.dox index 99731b287..05b15465c 100644 --- a/PlusLib/src/DataCollection/SavedDataSource/DeviceSavedDataSource.dox +++ b/PlusLib/src/DataCollection/SavedDataSource/DeviceSavedDataSource.dox @@ -1,9 +1,9 @@ /*! -\page DeviceSavedDataSource +\page DeviceSavedDataSource Replay recorded data from file \section SavedDataSourceSupportedHwDevices Supported hardware devices -- Link to manufacturer's website: +For hardware-free testing and simulation purposes, any previous recording (saved into a sequence metafile) can be replayed as a live acquisition \section SavedDataSourceSupportedPlatforms Supported platforms - \ref PlatformWin32 @@ -17,10 +17,12 @@ \section SavedDataSourceConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "SavedDataSource" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "SavedDataSet" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{10} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} - \xmlAtt \ref ToolReferenceFrame \OptionalAtt{Tracker} +- \b UseData \cTRANSFORM or \cIMAGE_AND_TRANSFORM + - \xmlAtt \ref ImageType Color image acquisition is supported by setting the imaging device's common attribute \c ImageType="RGB_COLOR". \OptionalAtt{BRIGHTNESS} diff --git a/PlusLib/src/DataCollection/SonixVideo/DeviceSonixVideo.dox b/PlusLib/src/DataCollection/SonixVideo/DeviceSonixVideo.dox index 4ab1cdf70..ef85c4eae 100644 --- a/PlusLib/src/DataCollection/SonixVideo/DeviceSonixVideo.dox +++ b/PlusLib/src/DataCollection/SonixVideo/DeviceSonixVideo.dox @@ -1,26 +1,38 @@ /*! -\page DeviceSonixVideo +\page DeviceSonixVideo Ultrasonix ultrasound scanner \section SonixVideoSupportedHwDevices Supported hardware devices -- Link to manufacturer's website: +Ultrasonix SonixRP, SonixMDP, SonixTouch, SonixTablet etc. +- Supported interfaces: Ulterius and Porta (Porta is not used widely and may not be stable, see #751). As all models use the same research interface, there is no difference in using Plus with any of the Ultrasonix scanner models (e.g., a sample config file for SonixRP works well for a SonixMDP scanner) + +- Link to manufacturer's website: http://www.analogicultrasound.com/ultrasonix + +The Ultrasonix L14-5 linear probe does not work well with the NDI Aurora electromagnetic tracker. If the L14 probe is stationary, we can get consistent readings, but if the probe is moving, the tracking is not stable at all. We know there is a big piece of aluminium inside L14-5. Thus I would advise not to use Aurora with Ultrasonix probe at this time. (Reported by Elvis Chen, Feb 29, 2012) Note that Ascension electromagnetic trackers work just fine even if they are very close to the transducer. \section SonixVideoSupportedPlatforms Supported platforms - \ref PlatformWin32 -- \ref PlatformWin64 - \ref PlatformWin32Embedded - \ref PlatformMacOs - \ref PlatformLinux \section SonixVideoInstallation Installation +If tracking does not work then try to copy the Ascension tracker DLL file (ATC3DG.dll) from the Ultrasonix exam software directory to the Plus directory (as the DLL version that is shipped with Plus may not match the installed tracker hardware/software version) + \section SonixVideoConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "SonixVideo" \RequiredAtt OR "Type" = \c "SonixVideoPorta" \RequiredAtt +When using Ulterius interface the B-mode image processing (scan conversion, de-speckle filtering, etc.) is performed in the CPU. If higher frame rates are needed and speckle is tolerable then it is advisable to turn off de-speckle filtering. + +If there is horizontal striping/repetition of image contents (typically occurs in water tank), then set the number of focal points to 1. It usually removes the artifact. (Reported by Andras Lasso, Nov 15, 2012; Exam software version 5.7) + +- \xmlAtt \ref DeviceType "Type" = \c "SonixVideo" \RequiredAtt OR "Type" = \c "SonixPortaVideo" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{30} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} +- \b CompressionStatus When imaging with the EC59 probe, if compression is disabled (CompressionStatus ="0"), then a lot of BMode frames are lost. The reason for this is the fact that scan-conversion is performed on the CPU. Set to 1 to prevent frame loss. + - \xmlElem \ref DataSources: - \xmlElem \ref DataSource: there must be one child element - \xmlAtt \ref PortUsImageOrientation \RequiredAtt diff --git a/PlusLib/src/DataCollection/UsSimulatorVideo/DeviceUsSimulatorVideo.dox b/PlusLib/src/DataCollection/UsSimulatorVideo/DeviceUsSimulatorVideo.dox index 22eecf281..c32004992 100644 --- a/PlusLib/src/DataCollection/UsSimulatorVideo/DeviceUsSimulatorVideo.dox +++ b/PlusLib/src/DataCollection/UsSimulatorVideo/DeviceUsSimulatorVideo.dox @@ -1,23 +1,44 @@ /*! -\page DeviceUsSimulatorVideo +\page DeviceUsSimulator Ultrasound simulation -\section UsSimulatorVideoSupportedHwDevices Supported hardware devices +\section UsSimulatorOverview Overvivew -- Link to manufacturer's website: +Any number of moving, intersecting objects can be simulated +Each object is defined by a surface mesh and its acoustic material properties +Position and orientation of objects can be obtained in real-time from a tracking device, from pre-recorded files, or tracker simulator +Inidividual scanlines are computed using a simple ultrasound physics based model, which includes attenuation, absorption, surface reflection (depending on incidence angle), speckle (using Perlin noise). Refraction, speed of sound, and beamwidth are not modeled. +Both linear and curvilinear transducer geometry is supported. +With minor modification in the device set configuration file image acquisition can be switched to use a real ultrasound device. -\section UsSimulatorVideoSupportedPlatforms Supported platforms +\section UsSimulatorSupportedPlatforms Supported platforms - \ref PlatformWin32 - \ref PlatformWin64 - \ref PlatformWin32Embedded - \ref PlatformMacOs - \ref PlatformLinux -\section UsSimulatorVideoInstallation Installation +\section UsSimulatorExample Example +- Download the following files from https://subversion.assembla.com/svn/plus/trunk/PlusLib/data/ConfigFiles/ + - PlusDeviceSet_Server_SimulatedUltrasound_3DSlicer.xml + - GelBlockModel_Reference.stl + - NeedleModel_NeedleTip.stl + - VesselModel_Reference.stl + - Test_PlusConfiguration_SimulatedUS.mrb +- Download and install the latest nightly build of 3D Slicer and the SlicerIGT extension +- Load the Test_PlusConfiguration_SimulatedUS.mrb file into 3D Slicer +- Open a command prompt in the directory where you have the downloaded files +Run: \PlusServer.exe --config-file=Test_PlusConfiguration_SimulatedUS.xml +- In Slicer go to the Transforms module and modify the ProbeToTracker and NeedleToTracker transforms -\section UsSimulatorVideoConfigSettings Device configuration settings + Watch on Youtube. -- \xmlAtt \ref DeviceType "Type" = \c "UsSimulatorVideo" \RequiredAtt +Related publications +http://perk.cs.queensu.ca/contents/opensource-surface-meshbased-ultrasoundguided-spinal-intervention-simulator + +\section UsSimulatorConfigSettings Device configuration settings + +- \xmlAtt \ref DeviceType "Type" = \c "UsSimulator" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{30} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0} @@ -28,8 +49,9 @@ - \xmlAtt \ref BufferSize \OptionalAtt{150} - \xmlAtt \ref AveragedItemsForFiltering \OptionalAtt{20} -\section UsSimulatorVideoExampleConfigFile Example configuration file +\section UsSimulatorExampleConfigFile Example configuration file + +\include "data/ConfigFiles/PlusDeviceSet_Server_SimulatedUltrasound_3DSlicer.xml" -\include "data/ConfigFiles/PlusDeviceSet_Server_UsSimulatorVideo.xml" */ \ No newline at end of file diff --git a/PlusLib/src/DataCollection/VideoForWindows/DeviceVideoForWindows.dox b/PlusLib/src/DataCollection/VideoForWindows/DeviceVideoForWindows.dox index c2dc71a8a..01ab7c3fc 100644 --- a/PlusLib/src/DataCollection/VideoForWindows/DeviceVideoForWindows.dox +++ b/PlusLib/src/DataCollection/VideoForWindows/DeviceVideoForWindows.dox @@ -1,9 +1,13 @@ /*! -\page DeviceVideoForWindows +\page DeviceVideoForWindows Video for Windows compatible imaging device \section VideoForWindowsSupportedHwDevices Supported hardware devices -- Link to manufacturer's website: +This device is deprecated, use MmfVideo device instead. + +Compatible framegrabbers and webcams through Video for Windows interface. + +Limitations: currently only certain color modes are supported, minor additional conversion routines may be needed for some devices. \section VideoForWindowsSupportedPlatforms Supported platforms - \ref PlatformWin32 @@ -17,7 +21,7 @@ \section VideoForWindowsConfigSettings Device configuration settings -- \xmlAtt \ref DeviceType "Type" = \c "VideoForWindows" \RequiredAtt +- \xmlAtt \ref DeviceType "Type" = \c "VFWVideo" \RequiredAtt - \xmlAtt \ref DeviceAcquisitionRate "AcquisitionRate" \OptionalAtt{30} - \xmlAtt \ref LocalTimeOffsetSec \OptionalAtt{0}