{composition-setup}
ScanImage and Ephus support a wide-range of commercial and customized hardware used in neurophysiology laboratories.
{hide-from:groups=ephus-users|users=@anonymous}
h5. !Shared Pics^navigate_right_10.gif! [JFRC Shared Two-photon Microscope Designs|shareddesigns:Shared Two-photon Microscope Designs]
{hide-from}
h5. {toggle-cloak:id=HardwareVendors} Hardware Info (by vendor)
{cloak:id=HardwareVendors}
{comment}{children:page=Hardware Vendors|sort=title}{comment}
{pagetree:root=Hardware Vendors|searchBox=true}
{cloak}
For the wide-range of hardware supported by ScanImage & Ephus, custom software interfaces must often be developed, allowing their capabilities to be accessed via scripting in Matlab. SuchAll devicerecent interfacesand areplanned developedreleases asof partScanImage ofinclude a growing Matlab [package|http://www.mathworks.com/help/techdoc/matlab_oop/brfynt_-1.html] of devices [classes|http://www.mathworks.com/help/techdoc/matlab_oop/bri1rtu-1.html] called *DabsDABS*., (Seewhich listcontains below.) {comment}The current versiona growing number of thissuch packagedevice is included with all recent and planned releases of ScanImage.{comment}
Some users may find some of these device interfaces useful in and of themselves -- i.e. as a Matlabinterface [classes].
DABS classes provide a MATLAB object-oriented scripting interface for thesethe supported devices., Notewhich thatsome theusers interfacesmay arefind provideduseful as-isin and their distribution/maintenance is not presently a primary aimof themselves.
For instance, the package *dabs.ni.daqmx* is a near complete wrapping of the ScanImage/Ephus projects. (Any issues affecting ScanImage/Ephus operation, however, should be brought to the [developers' attention|mailto:iyerv@janelia.hhmi.org?subject=\[ScanImage/Ephus Feedback\]].)
In some cases,National Instruments [DAQmx] driver into MATLAB. This package effectively recapitulates and extends upon the MATLAB [Data Acquisition Toolbox]. DABS also includes _abstract superclasses_ are included in the Dabs package to facilitate the development of device interfaces to a common standard. For instance a [Linear Stage Controller superclass|DABS Subclassing LSC] has been developed. Users can create custom subclasses for their particular stage controllers, allowing ScanImage to operate with these devices.
Note that Ephus makes use of two earlier-style Matlab device interfaces: [NiMex|NIMEX] and [QCamMex].
{info}Note that DABS interfaces are provided as-is and their distribution/maintenance is not presently a primary aim of the ScanImage/Ephus projects. However, any issues affecting ScanImage/Ephus operation should of course be brought to the [developers' attention|mailto:iyerv@janelia.hhmi.org?subject=\[ScanImage/Ephus Feedback\]].{info}
{comment}
h5. {toggle-cloak:id=DabsList} List of Current Dabs Classes (& Packages)
{cloak:id=DabsList}
* dabs.andor.AndorCamera
* dabs.coherent.Chameleon
* dabs.coolled.PE
* dabs.newport.XPS
* dabs.ni.daqmx (_package_)
* dabs.pi.(E517/E712/E753/E816)
* dabs.piezojena.DDrive
* dabs.prior.PriorStage
* dabs.qimaging.QCam
* dabs.scientifica.LinearStageController
* dabs.sutter.(MPC200/MP285)
* dabs.thorlabs.LSM
{comment}
{cloak}
|