Msconvert Wine

From SPCTools

(Difference between revisions)
Jump to: navigation, search
Revision as of 17:22, 4 December 2012
JoeS (Talk | contribs)
(→Instructions for CentOS)
← Previous diff		 Revision as of 18:43, 11 December 2012
JoeS (Talk | contribs)
(→Instructions for Ubuntu (Updated 11/26/2012))
Next diff →
Line 25: Line 25:
# Ensure wine has the correct architecture and set the location of the Windows emulation # Ensure wine has the correct architecture and set the location of the Windows emulation
#:export WINEARCH=win32 #:export WINEARCH=win32
-#:export WINEPREFIX=~/.wine {{pad|5em}}''Default. Choose wherever''+#:export WINEPREFIX=~/.wine {{pad|5em}}''Default. Choose your location''
# Use ''winetricks'' to configure the Windows emulation # Use ''winetricks'' to configure the Windows emulation
#:winetricks win7 vcrun2005 vcrun2008 vcrun2010 #:winetricks win7 vcrun2005 vcrun2008 vcrun2010

Revision as of 18:43, 11 December 2012

Proteowizard's msconvert utility is a must have tool for converting mass spectrometry data from almost any proprietary data format into open standards formats (primary mzML and mzXML). While this tool runs on both Windows and Linux, the ability to convert many common instrument formats under Linux is limited due to the need to have vendor specific libraries (dlls) installed. Fortunately it is possible to run the Windows version of msconvert under Linux using Wine, a open source compatibility layer for Windows -- though your mileage may vary.

The following are instructions on how to install and setup Wine under a variety of Linux platforms. These instructions where largely derived from several spctools-discuss emails and a large thanks goes out to the users who posted them (see references below).

Contents

Requirements

  • You will need to use wine in 32bit emulation mode (basically a 32bit wine even if you are on a 64bit architecture). This is because the .Net and Visual Studio libraries are required and these libraries are installed using a 32 bit installer, even for the 64 bit versions of these libraries. Please also be aware that not all proprietary vendor libraries that are distributed with ProtoWizard are 64 bit hence the 64 bit version of msconvert cannot be used to convert most proprietary files.

Instructions for Ubuntu (Updated 11/26/2012)

The following instructions where developed using Wine 1.5.18 and ProteoWizard 2.1.4131 on the 4.5.2 TPP Amazon Machine Image which is based on the official Ubuntu 12.04 'precise' AMI.

middle
Please read the notes regarding potential issues following these instructions before executing.
  1. Connect to the system you want to install on. If using ssh use the -X option to ensure display forwarding is set since parts of the setup will prompt you with GUI dialogs asking you to accept licenses.
    ssh -X ubuntu@<hostname>
  2. Install the latest 32-bit version of wine
    sudo add-apt-repository ppa:ubuntu-wine/ppa
    sudo apt-get -y update
    sudo apt-get -y install wine1.5-i386
    sudo apt-get -y install winetricks
  3. Ensure wine has the correct architecture and set the location of the Windows emulation
    export WINEARCH=win32
    export WINEPREFIX=~/.wine  Default. Choose your location
  4. Use winetricks to configure the Windows emulation
    winetricks win7 vcrun2005 vcrun2008 vcrun2010
  5. Progressively install the .Net frameworks. While winetricks is suppose to install any older frameworks I found it works better if I did it manually starting from the oldest. Also see note below about sites blocking downloads.
    winetricks dotnet20
    winetricks dotnet20sp1
    winetricks dotnet20sp2
    winetricks dotnet30
  6. Correct known issue with dotnet20 (see [1])
    mkdir -p $WINEPREFIX/dosdevices/c:/windows/assembly/NativeImages_v2.0.50727_32
    touch $WINEPREFIX/dosdevices/c:/windows/assembly/NativeImages_v2.0.50727_32/indexb.dat
  7. Continue installing the rest of the .Net frameworks
    winetricks dotnet30sp1
    winetricks dotnet35 May fail. Rerunning it a 2nd time worked.
    winetricks dotnet35sp1 May fail. Rerunning it a 2nd time worked.
    winetricks dotnet40
  8. Download and install Proteowizard.
    Go to http://proteowizard.sourceforge.net/ using a web browser. Click on the downloads link and select the Windows with vendor support option with the tar.bz2 extension. Extract the package and move it to wherever you want to install it.
    mkdir pwiz; tar xvf pwiz*.tar.bz2 -C pwiz
  9. Register dll (shouldn't be needed but...)
    wine regsvr32 pwiz/MSFileReader.XRawfile2.dll
    wine regsvr32 pwiz/CompassXtractMS.dll
  10. Run msconvert
    wine pwiz/msconvert.exe

Issues/Problems

  • If you are trying to install on an Amazon EC2 instance winetricks may fail when trying to download and install packages. From what I can tell some download sites are blocking access from the Amazon Cloud. Just manually download the file from a different system (tip, use the wget command suggested by winetricks or a browser) and copy them to the location specified by winetricks.
  • If during the installation of .Net 3.0 it seems to hang, look in your "system tray" for the installer icon. This will be the final finish dialog that will need to be clicked through to end the installation.
  • Currently doesn't work for AB Sciex wiff files as it uses the .Net 4.0 framework which is not fully implemented yet in wine.
  • Lastly should be aware that various vendor libraries use versions of .Net that are still experimental at this time. ProteoWizard elements that make use of this may not work correctly.

Instructions for CentOS

The following instructions where tested using ProteoWizard on a CentOS 6.3 Amazon Machine Image (ami-f0ab24c0). CentOS presents a bigger challenge as you'll need the latest version of Wine and at the time these instructions where written none of the CentOS repositories contained pre-built rpms for it.

  1. Log into the system
  2. Upgrade your system if it hasn't already been
    sudo yum -y upgrade
  3. Install necessary packages for building and running wine
    yum -y installgroup "Development Tools"
    yum -y installgroup "X Window System"
    yum -y install libgcc.i686 glibc.i686 glibc-devel.i686 libX11.i686 libX11-devel.i686 freetype.i686 freetype-devel.i686 freetype-demos.x86_64 freetype-devel.x86_64 libxml2.i686 libxml2-devel.i686 libxslt.i686 libxslt-devel.i686 libXcursor.i686 libXcursor-devel.i686 libpng.i686 libpng-devel.i686 libjpeg.i686 libjpeg-devel.i686 libtiff.i686 libtiff-devel.i686 openssl.i686 openssl-devel.i686 libXrender.i686 libXrender-devel.i686 cabextract
  4. Get winetricks
    wget http://winetricks.org/winetricks
    chmod +x winetricks
  5. Run Steps 3 and on from the Ubtuntu section

What Works?

The following table shows the results of testing Wine/msconvert with the various different instrument formats available to us. For each format the instrument output was converted using the same version of msconvert installed on Windows 7 and Wine. The program readmzXML was then used to dump a summary of the resulting mzML file and the values compared between systems.

If you have any questions about the testing or have additional results to add please forward them to the spc-tools discussion mailing list.

Wine/msconvert Instrument Formats Tested
Vendor Model Acquisition Software Output Type Result Notes
Applied Biosystems (ABSciex) QQQ Analyst .wiff file Fails Requires .Net 3.5 which doesn't function under wine.
Agilent QQQ MassHunter 2.1 .d directory Success
Agilent QTOF MassHunter 2.1 .d directory Success
Bruker Apex, MicrOTOF ?1 .baf file Success
Waters  ? MassLynx 4.1 .raw directory Success

How can I install windows applications to be shared by multiple users under wine?

Wine does not currently allow sharing its Windows root (or "prefix") between users, due to the risk of registry corruption from running multiple wineservers simultaneously ([bug #11112]). This means you typically would need to go through and install each set of Windows applications for each user. If you have a lot of users this could become burdensome, however you can create a single prefix and then copy it for each user. (The default wine prefix is ~/.wine). This saves having to run the same installation instructions for each user.

Another option is to write a wrapper script around the whole process. This wrapper script could copy a standardized wine prefix with all of the applications installed into a new temporary prefix owned by the user, set the environment variable WINEPREFIX to point to the temp prefix, run the wine command(s), stop the user's wine server, and then remove the temporary prefix.

One last item, be careful about using NFS with wine. If your home directory is mounted using NFS and shared across systems you could experience some problems running wine on multiple systems in parallel. More information about wine's "windows" partition and NFS:

http://www.winehq.org/pipermail/wine-users/2010-July/076137.html

References

http://groups.google.com/group/spctools-discuss/browse_thread/thread/604745729ac0e541
http://groups.google.com/group/spctools-discuss/browse_thread/thread/bb2a608ad31f77dd/868fab027488bd09?hl=en&lnk=gst&q=wine#868fab027488bd09
http://groups.google.com/group/spctools-discuss/browse_thread/thread/2d98145b42479cb0/f8d80a25d1f8583c?hl=en&lnk=gst&q=wine#f8d80a25d1f8583c
Retrieved from "http://tools.proteomecenter.org/wiki/index.php?title=Msconvert_Wine"
Personal tools