Thermo Fisher Scientific Using SOLiDBioScope.com™ Quick start guide

Using SOLiDBioScope.com™

QUICK START GUIDE | OCTOBER 2010

SUBJECT: SOLiDBioScope.com

In this guide This Quick Start Guide covers:

■Access SOLiDBioScope.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

■Log in to SOLiDBioScope.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

■Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

■Use Linux commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

■Run a command-line analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

■Monitor your run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

■Obtain support and more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Purpose of this

guide

This Quick Start Guide provides instructions for logging into SOLiDBioScope.com™

and using BioScope™ Software to run secondary data analysis (aligning to a reference

genome and base calling) and tertiary data analysis (resequencing: find single

nucleotide polymorphisms [SNPs], copy number variations, inversions, small indels,

large indels; and whole transcriptome analysis: count known exons, create UCSC WIG

files, and find splicing fusion). For more information on BioScope Software, refer to the

Applied Biosystems BioScope™ User Guide (PN 4461308). For a quick reference of the

BioScope Software user interface, refer to the Applied Biosystems SOLiD™ 4 System

Software Integrated Workflow Quick Reference Guide (PN 4448432).

Overview SOLiDBioScope.com is an online suite of software tools for Next Generation

Sequencing (NGS) analysis. It provides you with the scalable resources of cloud

computing to perform intensive NGS data processing. Powered by Penguin On

Demand (POD), SOLiDBioScope.com offers you the ability to “rent a super computer”

and use BioScope Software and other analytical software to run NGS data analyses on

your SOLiD system.

SOLiDBioScope.com provides scientists, researchers, bioinformaticians, and other

specialized users with on-demand access to BioScope Software. The

SOLiDBioScope.com computing infrastructure consists of dynamically-scalable,

highly-optimized Linux clusters for parallel computing. Also available on

SOLiDBioScope.com are specialized hardware and software configurations for high-

performance computing (HPC).

Your analyses run directly on the physical cores of computer nodes, not on virtual

computers, so you that you have access to the server’s full resources for maximum

performance and to input-output for massive HPC workloads. The result for HPC

applications is a significant improvement in performance over traditional cloud

computing.

2SOLiDBioScope.com™ Quick Start Guide

Access SOLiDBioScope.com

SOLiDBioScope.com and the SOLiD™ system workflow

A workflow comprises a series of data analysis steps. Each analysis step is dependent

on the steps that precede it. For information about workflows, refer to the Applied

Biosystems SOLiD 4 System Software Integrated Workflow Quick Reference Guide (4448432).

For detailed data analysis procedures in the SOLiD workflow, refer to the Applied

Biosystems BioScope User Guide (PN 4461308).

Data analysis

The procedure for performing secondary and tertiary data analyses on

SOLiDBioScope.com is similar to the procedures for those analyses using BioScope

Software. For instructions, refer to the Applied Biosystems BioScope User Guide

(PN 4461308).

Custom software

You can use your own NGS analysis tool on SOLiDBioScope.com. If you prefer to use

BFAST as your mapper, you can upload and install BFAST on SOLiDBioScope.com,

then analyze your data using that tool. You can set up your own pipeline in

SOLiDBioScope.com and use that pipeline, rather than BioScope Software, for your

NGS data analysis.

To run other software packages on SOLiDBioScope.com, contact Penguin Computing

for instructions on how to set up your own analytical tools on POD. Email

[email protected].

Access SOLiDBioScope.com

You must obtain an account before you can use the SOLiDBioScope.com service. After

you get an account, there are two ways to access SOLiDBioScope.com: via a Linux®

shell window or a web-based, Internet browser.

Obtain an account To sign up for a SOLiDBioScope.com account, go to: www.solidbioscope.com and

follow the instructions for obtaining an account. After your account has been created,

you can remotely log in to SOLiDBioScope.com and use BioScope Software.

The initial communications notifying you of your SOLiDBioScope.com access include:

• The uniform resource locator (URL) to launch your SOLiDBioScope.com graphic

user interface (GUI).

• The IP address of your SOLiDBioScope.com login server.

• The username and password assigned to you.

• Your home directory ($HOME). This is the directory you are “in” whenever you

/home/username.

• The location of the storage space assigned to you. This location is for the files

required for and generated by your BioScope Software runs. Your storage space is

typically /filesystem/username.

• The location of your scratch space. Scratch space is used for temporary files,

intermediate files, and other files that do not require long-term persistence. An

example of a scratch space location is /scratch/username.

SOLiDBioScope.com™ Quick Start Guide

SOLiDBioScope.com

Access via a Linux®

window

You must log in to a SOLiDBioScope.com Linux shell window to customize the

initialization (.ini) and properties files containing settings for your BioScope Software

command-line analysis runs. Before you can access SOLiDBioScope.com, you need:

• Your username (this is your login account for SOLiDBioScope.com).

• The password for your username.

• The IP address of the SOLiDBioScope.com server.

This information is included in the initial emails sent to you when you signed up for

your SOLiDBioScope.com account.

You also need a method of logging onto the Linux server running

SOLiDBioScope.com. To log in, you need a Secure Shell (SSH) client, either native in

Linux or Macintosh®, or a Windows® SSH client such as PuTTY.

Access via Internet

browser

To run SOLiDBioScope.com on the Internet, open an Internet browser, then enter the

URL assigned to you. No password is required.

This section describes how to log in to SOLiDBioScope.com with the PuTTY utility on

Windows. The steps for other client utilities are quite similar. After you have logged in,

you can install and use your own, custom software.

Field Entry or Selection

Host Name (or IP address) IP address for your SOLiDBioScope.com server

Port Accept the default (for example, port 22)

Connection type SSH

Load, save or delete a stored

session

Session name, then click Save.

Your saved session stores your settings, so that you do

not have to repeat entering this information the next

time you use PuTTY to connect to SOLiDBioScope.com.

Close window on exit Only on clean exit

4SOLiDBioScope.com™ Quick Start Guide

Here is an example of the PuTTY utility configured to connect to SOLiDBioScope.com:

After you click Open in the PuTTY Configuration window, the PuTTY utility connects

to SOLiDBioScope.com and opens a Linux shell window. In the window, enter your

username and password to log in to SOLiDBioScope.com. When you are logged in,

your current directory is your home directory, which, by default, is /home/username.

Note: If your username or password is not accepted, please contact

[email protected] to reset or get a new username or password.

Internet

To log in to SOLiDBioScope.com via the Internet, open your Internet browser and enter

the URL assigned to you. The format for the URL is

http://IPaddress:port/bioscope/

where IPaddress is the IP address of the server running the BioScope Software and port

is the port used by BioScope Software. The default port is 8080.

Note: Do not type SOLiDBioScope.com to run BioScope Software via the Internet.

For information on running BioScope Software, refer to the Applied Biosystems SOLiD™

4 System Software Integrated Workflow Quick Reference Guide (PN 4448432) and Applied

Biosystems BioScope User Guide (PN 4461308).

Access custom

software

If you have already installed your own custom software on SOLiDBioScope.com, you

can access and execute your programs after the client has connected.

SOLiDBioScope.com™ Quick Start Guide

SOLiDBioScope.com

Before you begin

Before you use SOLiDBioScope.com, complete these prerequisites:

• Understand the control file functionality, described in “Files” on this page.

• Customize your controls files, described in “Set up command-line runs” on

page 6.

• Learn how to transfer your data to your SOLiDBioScope.com server, described in

“Transfer and store data” on page 10.

Files This section introduces you to the files needed to define BioScope Software analysis

settings.

The following control files are used with your BioScope Software analyses on the

command-line:

• Pipeline properties files define settings used in all runs for a particular pipeline.

These files are located in $BIOSCOPEROOT.

•Your

global.ini file defines settings for all your analysis runs. This file is located

in your analysis directories or your examples directories.

• Pipeline .ini files define settings for a single analysis run. In case of conflicting

settings, the pipeline .ini file setting takes precedence over settings in your

global.ini file and in the $BIOSCOPEROOT properties file. Your pipeline .ini

files are located in your analysis directories or your examples directories.

•.plan files define a sequence of analyses to be executed. A .plan file lists one or

more .ini files, each of which represents an analysis run to be executed. These

files are located in your analysis directories or your examples directories.

demo.ini file

The following example shows the contents of the file demo.ini in the directory

/filesystem/username/results/bioscope1.2/examples/demos/mapping:

######################

## global settings for the pipeline run

import ../globals/global.ini

reference = $(reference.dir)/DH10B_WithDup_FinalEdit_validated.fasta

read.length = 50

######################

## mapping pipeline

## mapping.run = 1

mapping.tagfiles.dir = $(base.dir)/reads1 mapping.output.dir =

$(output.dir)/s_mapping

6SOLiDBioScope.com™ Quick Start Guide

Before you begin

######################

## temp files and folder keep

#pipeline.cleanup.middle.files = 0

#job.cleanup.temp.files = 0

The demo.ini file performs the following actions:

• Global settings are imported from the file ../globals/global.ini.

• The reference file is specified (DH10B_WithDup_FinalEdit_validated.fasta).

• The read length is set to 50 base pairs.

• The location of the reads files is specified (with mapping.tagfiles.dir).

• The output directory (output.dir) is specified.

• The mapping analysis is run with the above settings.

Set up command-

line runs

The following sections provide information for setting up command-line runs.

■Locate your BioScope Software installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

■Locate your storage space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

■Customize your pipeline’s properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

■Provide the correct location of BioScope Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

■Customize .plan files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

■Access readme files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

■Run a demonstration experiment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Locate your BioScope Software installation

Use the echo command to determine the location of your BioScope Software:

echo $BIOSCOPEROOT

For more information, refer to the section “Set the BioScope environment” in the

Applied Biosystems BioScope User Guide (PN 4461308). If your $BIOSCOPEROOT

environment value is not defined, contact your Applied Biosystems Field Applications

Specialist.

Locate your storage space

You are assigned a storage space for your data, results files, and work area. Your

storage space is typically not in $BIOSCOPEROOT. An example is:

/filesystem/username

where filesystem is an example file-system mount point and username is your assigned

username.

Your assigned storage space is included in the initial communications notifying you

about your SOLiDBioScope.com account.

SOLiDBioScope.com™ Quick Start Guide

SOLiDBioScope.com

Before you begin

Customize your pipeline’s properties file

Check the BioScope Software properties files located in the directory:

$BIOSCOPEROOT/etc/plugins/properties

You might need to modify a properties file, which contains settings for your type of

analysis run. For example, the file mapping.properties contains the settings for

genomic mapping runs. Example contents for the mapping.properties file are shown

below.

mapping.number.of.nodes = 10

mapping.np.per.node = 8

mapping.min.reads = 10000000

mapping.memory.size = 30

mapping.scheme.unmapped.25 = 25.2.0 mapping.scheme.repetitive.25 =

mapping.scheme.unmapped.35 = 30.3.0 mapping.scheme.repetitive.35 =

mapping.scheme.unmapped.50 = 25.2.0,25.2.15

mapping.scheme.repetitive.50 =

In most cases, you need to modify only the mapping.number.of.nodes entry. For a

normal run of less than 500M reads, 4 nodes is sufficient.

Note: A node is a separate computer. Each node contains 8 cores, as defined in the

parameter mapping.np.per.node = 8.

Note: Modifying a setting in a properties file affects all future runs. Modifying the

setting in the mapping.ini file affects only the current run. Settings in the

mapping.ini file take precedence over settings in the mapping.properties file.

Provide the correct location of BioScope Software

Review the .ini file for your pipeline analysis to ensure that all path names reflect the

correct location of your BioScope Software, as given by $BIOSCOPEROOT. (See “Locate

your BioScope Software installation” on page 6 for information on determining the

environment value of $BIOSCOPEROOT.)

For example, this entry appears in diBayes.ini, the .ini file for SNPs analysis runs:

tm.file=/share/apps/bioscope/etc/analysis/6mers.Tm

You must modify this entry to provide the correct location of your BioScope Software.

To modify this entry with the absolute path given by $BIOSCOPEROOT:

1. Identify the pathname:

echo $BIOSCOPEROOT

which, for example, returns the location:

/usr/bioscope

This value is only an example. Your location will be different.

2. Use your environment value of $BIOSCOPEROOT to replace the string

/share/apps/bioscope. In the example tm.file entry in the diBayes.ini file,

you would replace /share/apps/bioscope with the pathname in step 1

(/usr/bioscope):

tm.file=/usr/bioscope/etc/analysis/6mers.Tm

8SOLiDBioScope.com™ Quick Start Guide

Before you begin

3. Check your global.ini file and change any default paths to custom paths.

For example, the value in the folder base.dir is ./:

base.dir=./

If you change the value to

base.dir=/data/results/MyData

you must change the variable ${base.dir} in the parameter

reads.results.dir.1 from

reads.result.dir.1=${base.dir}/../F3/reads1

reads.result.dir.1=/data/results/MyData/../F3/reads1

If an application needs an input file such as a color-space fasta reads file

(.csfasta) or a quality value reads file (.qual), make sure that the input file is in

the reads1 folder before you start a run. In the example, you would check the

folder /data/results/MyData/../F3/reads1. If the input file was not in that

folder, you would need to change the value of reads.result.dir.1 to the

location of the folder containing the input file needed by the application.

Another example of a default path is the path to the references folder:

reference.dir = /data/results/bioscope1.3/examples/demos/

references/

In this case, you would replace the string/data/results/bioscope1.3/ with

/data/results/MyData/:

reference.dir = /data/results/MyData/examples/demos/references/

Again, you would need to make sure that the input files needed for an application

are in the references folder before you started a run.

Customize .plan files

The .plan file is a job control mechanism used to launch a single BioScope Software

job or a sequence of several jobs. A .plan file contains a list of one or more .ini files.

For each .ini file listed, a run.sh job is launched for that pipeline.

Your .plan files are located in the pipeline directories.

This is the entire contents of the file demo.plan, in the mapping directory:

mapping.ini

When you invoke run.sh in the mapping directory, this entry in the demo.plan file

initiates a mapping analysis run, per the settings in the file mapping.ini.

This is the contents of the file demo.plan in the pairing directory:

=./F3/demoF3.ini

=./R3/demoR3.ini

./MP/demo.ini

Each pipeline with a .ini file appearing in the .plan file is executed in the order

listed. An = sign indicates that the .ini files can be simultaneously executed. In the

above example, the ./F3/demoF3.ini and ./R3/demoR3.ini tasks are run at the same

time. When both of those tasks are completed, then the ./MP/demo.ini job is run.

When you invoke run.sh in the pairing directory, those three .ini files in the

demo.plan file cause three pairing analysis runs to be initiated.

SOLiDBioScope.com™ Quick Start Guide

SOLiDBioScope.com

Before you begin

Access readme files

readme files contain information, requirements, and tips on running the analyses. You

can find readme files in the examples, applications, demos, and pipelines

directories.

Run a demonstration experiment

We strongly recommend running a job with small example data provided in the

BioScope Software installation. Run small example data to ensure correct

configuration and permissions before running a lengthy job with large data.

Example data are typically installed at the following locations:

/filesystem/username/results/bioscope1.2/examples/demos

and

/filesystem/username/results/bioscope1.2/examples/applications

where /filesystem is the storage file system assigned to you.

The examples/demos directory contains single pipeline runs, such as mapping and

pairing. The examples/applications directory contains more complicated scenarios

involving combinations of pipelines.

To run the small example job, follow these steps:

1. Change the directory to the demos directory:

cd /filesystem/username/results/bioscope1.2/examples/demos

2. Type this command:

./run.sh mapping

This command initiates a mapping analysis on the demonstration data. The

run.sh script takes one argument, the pipeline name.

3. Wait for the “finished successfully” or “completed successfully” notice on your

screen or in the main log file, for example:

17 Apr 2010 02:37:31,208 INFO [main] JMSEventSender:78 - Event

'[COMPLETE] PluginRunner Mapping-1 completed successfully' sent

on selector '8737b7ba-ab2b-42c0-b862-920d6f315bb1'

17 Apr 2010 02:37:31,209 INFO [main] PluginRunner:441 - >>>> END

of PluginRunner >>>> date=2010-04-17 02:37:31.209 GMT-07:00

17 Apr 2010 02:37:31,209 INFO [main] PluginRunner:442 - >>>> END

of PluginRunner >>>> date DURATION=53 secs

17 Apr 2010 02:37:31,209 INFO [main] EventTransportFactory:129 -

Closing JMS connection and session

10 SOLiDBioScope.com™ Quick Start Guide

Use Linux commands

Transfer and store

data

You can transfer large data files (up to 25 GB) directly to or from SOLiDBioScope.com

over the Internet (your actual transfer speeds depend on your local Internet connection

speeds).

SOLiDBioScope.com includes a “disk caddy” service that offers overnight transferal of

2 terabytes (TB) files. For data sets greater than 25 GB, we recommend exchanging 2 TB

disk drives through standard shipping services. You purchased these disks as part of

the SOLiDBioScope.com service. Your disks are immediately returned to you after the

data has been transferred to SOLiDBioScope.com storage. For larger data transfer

requirements, we supply a 4 unit (4U) storage server that provides up to 48 TB of data

transfer per shipment. If you have large data files and require greater security, we can

provide encrypted disk drives.

You can transfer raw, SOLiD data (.spch files) or color-space fasta (.csfasta) and quality

value (.qual) reads files. The size of SOLiD data files usually is in terabytes whereas

reads files are usually hundreds of gigabytes in size. Although SOLiDBioScope.com

can accommodate terabytes of data, only reads data for BioScope Software is needed to

perform secondary (mapping/pairing) and tertiary analyses (biological interpretation).

After data analysis has been completed, you can download your analyzed data using

the same method that you used to upload your data.

Use Linux commands

This section describes examples of Linux commands and features typically used with

your command-line analysis runs on SOLiDBioScope.com.

About the Linux

command prompt

When you log in to a SOLiDBioScope.com Linux shell window, the system displays a

command prompt made of your username, cluster name, and current directory.

An example command prompt is:

[hitaha@pod0 mapping]$

The fields in this example command prompt are:

•hitaha: your username

•pod0: your SOLiDBioScope.com hostname

•mapping: the name of the current directory (this portion of the command prompt

changes as you change directories)

Note: If you are in your home directory, the directory name in the command

prompt is shown as ~, for example:

[hitaha@pod0 ~]$

About the Linux

screen command

The screen command is a virtual window manager that gives you access to multiple

separate terminal sessions (screens) from a single login window. It also detaches your

Linux processes from the shell (screen) in which they were executed (normally a Linux

process is killed when the screen where it originated is closed.)

The screen command provides the following features, which are useful for managing

lengthy analysis runs:

• It opens a new shell window or screen.

• Linux processes that you run on the new screen continue running even when the

screen is closed.

SOLiDBioScope.com™ Quick Start Guide

SOLiDBioScope.com

Run a command-line analysis

• A closed screen can be reopened with the screen resume command: screen -r

• A resumed screen shows its normal screen output, as though it had never been

closed.

• Processes such as your analysis runs continue in a resumed screen, as though the

screen had never been closed.

• You can keep multiple screens. If you have multiple screens closed, the resume

screen command (screen -r) lists the available screens and enables you to select

the screen you want to resume.

About the Linux

nohup command

Normally Linux processes, including a running BioScope Software run.sh script, are

interrupted if the parent Linux shell window closes. Reasons that a shell window

might unexpectedly close while your job is running include:

• Losing your connection to the Linux server.

• Having your session time out while waiting for processing to finish.

• Manually closing the window by mistake.

The nohup (“no hang up”) command prevents your job from being affected by its

window closing. This feature makes nohup useful for lengthy jobs such as BioScope

Software analyses.

The following command runs the script run.sh in the background with nohup:

nohup ./run.sh mapping &

The “&” notation causes the command to run in the background. Commands that run

in the background continue processing even if their parent window is terminated.

About monitoring

commands

See “Monitor your run” on page 12 for examples of using the monitoring commands

qstat and ps.

Run a command-line analysis

This section includes explanations of the shell scripts in the applications and

pipeline directories, which are used to run a command-line analysis.

run.sh script The run.sh script is the starting point for your BioScope Software analysis runs on the

command-line. As an example, consider the sample applications directory in the

directory /filesystem/username/results/bioscope1.2/examples/applications. To

invoke run.sh in this directory, you must supply a pipeline name as an argument. The

general syntax is:

./run.sh pipeline

Here is an example command for the mapping pipeline:

./run.sh mapping

The run script executes the following sequence of actions:

• Checks for a directory named pipeline.run (for example, mapping.run).

• Deletes the directory pipeline.run if it exists.

12 SOLiDBioScope.com™ Quick Start Guide

Monitor your run

• Creates (or recreates) the directory pipeline.run by copying the entire directory

pipeline to pipeline.run.

• Changes directory to pipeline.run.

• Invokes a second run.sh script in the directory pipeline.run.

Note: Because the run.sh script always deletes an existing pipeline.run directory, we

strongly recommend that you rename your pipeline.run directory after every

successful run. Otherwise, you might accidentally delete your run data on the next

invocation of run.sh.

pipeline run.sh

scripts

In an examples/applications/pipeline directory, the secondary run.sh script

executes this command:

bioscope.sh -l log/example.log example.plan

This script:

• Invokes the script bioscope.sh (a BioScope Software script).

•Sets

example.log as the log file for this run.

• Uses the list of .ini files contained in the file example.plan as the list of BioScope

Software analyses to be run.

Note: Although the scripts share the same name, run.sh scripts in the pipeline

directories are different from the run.sh script in the applications directory.

Monitor your run

Use the qstat utility and ps command to monitor your data analysis run.

Use the qstat utility The utility qstat -n displays the currently running background jobs, with their

memory usage and run times. The output for BioScope Software runs contains the

string “bioscope”. The output for your command-line runs contains your username.

Use the ps

command

The ps command displays information about running processes. This section describes

two versions of the ps command: ps -fu and ps -ef.

ps –fu. This command displays all your running processes. Example output of this

command is shown below:

kavmon 19244 1 0 16:11 pts/4 00:02:19 /bin/bash /panasas/

kavmon/results/bioscope1.2/examples/demos/run.sh mapping

kavmon 19330 176711 0 16:12 pts/3 00:00:01 ps -fu

•kavmon names the owner of the process; the owner is the user who executed the

script.

•19244 and 19330 show the process identifications (pids); Linux assigns each

process a unique pid.

•/bin/bash names the Linux module that executes the script.

•/panasas/kavmon/results/bioscope1.2/examples/demos/run.sh mapping

shows the executing process (your run.sh script) and its arguments. It displays

the full path to the executing process. Long strings might be truncated.

SOLiDBioScope.com™ Quick Start Guide

SOLiDBioScope.com

Obtain support and more information

ps –ef. This command checks on running the process named “run.sh”:

Example command:

[kavmon@pod0 mapping]$ ps -ef | grep run.sh

ps -ef displays all running processes. The command grep run.sh restricts the output

to only entries containing the string “run.sh”. The output is in the same format as the

ps -fu output.

Obtain support and more information

For the latest BioScope Software services and support information, go to:

www.solidbioscope.com

For issues relating to BioScope Software, please contact your local field applications

specialist. You can also obtain support by sending email to:

[email protected]

At the SOLiDBioScope.com website, you can:

• Access worldwide telephone and fax numbers to contact Applied Biosystems

Technical Support and Sales facilities.

• Search through frequently-asked questions (FAQs).

• Submit a question directly to Technical Support.

• Order Applied Biosystems user documents, SDSs, certificates of analysis, and

Thermo Fisher Scientific Using SOLiDBioScope.com™ Quick start guide

Related papers

Other documents