Tweet
Seems like a pity why you pulled hadoop out of Goby. Any compelling reason?
Also for the Aligner portion so far it only supports BWA ?
Also for the Aligner portion so far it only supports BWA ?
-
Aligners support in Goby
In addition to BWA, Goby also supports the Last aligner. Last can be downloaded from http://last.cbrc.jp/archive/last-96.zip (see http://last.cbrc.jp/ for information).
Last is slower than bwa for short reads, but is very useful to align longer reads (i.e., in the several hundred bases and more). Last is also useful if you need very sensitive searches (e.g., align reads that match only in a third of their length, but are still mapping in a single location in the genome).
In version 1.4, we added the ability to run a released version of last (we tested version 96). You should be able to switch the aligner by replacing bwa below, with last:
java -jar goby.jar --mode align --aligner bwa --search
This requires that you modify the configuration file config/goby.properties and specify where you have installed last on your system. Uncomment and change this line:
#executables.path.last = /usr/local/last-96/src
Please note that the developers of last have recently changed some of the file formats they generate. Goby has not yet been adapted to these changes, so for instance Last version 99 is known not to work with Goby 1.4.Comment
-
Is the Goby use the default setting of the bwa for the alignment? Thanks again.Comment
-
Hi Alex,
For the most part the default options for bwa are used except for the seed length which gets set to 35 (-l 35) and the color space option to "bwa" (-c) will be set appropriately depending on whether or not the --color-space flag is present in the AlignMode option. Options can be passed directly to bwa by specifying the "--options" flag on the goby command line. This takes a comma separated list of options that will get passed onto the native aligner. So for example if you wanted to pass "-l 30 -d 8 -k 2" to bwa you would add "--options l=30,d=8,k=2". The same can be done for the last aligner.
If you to add these to the sample listed at http://icbtools.med.cornell.edu/goby/ as follows:
$ java -Xmx3g -jar goby.jar --mode align --aligner bwa --search --database-name chr1-index --reference data/reference/mm9/chr1.compact-reads --database-directory data/reference-index/mm9 --reads data/reads/goby-mouse-reads-sample.compact-reads --basename goby-sample --options l=30,d=8,k=2
To verify actual bwa execution you should see all the options passed to bwa in the goby console log as something like:
INFO BWAAligner - About to execute nice /home/marko/bwa-0.5.5/bwa aln -l 30 -d 8 -k 2 chr1-index goby-mouse-reads-sample.fasta
Please let me know if you have any other questions.
-- MarkoComment
-
Actually, the "issue" has more to do with differences naming conventions for chromosomes in the reference datasets used. The mouse reference file included with Goby was created from the UCSC MM9 dataset ("chr1", "chr2", "chr3", etc.) and the biomart annotation file uses the NCBI/ENSEMBL dataset ("1", "2", "3", etc.). The alignment to annotations mode doesn't output any results due to the naming differences. As Fabien mentioned, prepending chromosome names with "chr" should fix most of the entries, however this is not appropriate for all the name mappings.
For example, 1 --> chr1, 2 --> chr2, X --> chrX, but MT --> chrM and as far as I can tell NT_166323 doesn't map anywhere. A more appropriate way to create the annotation file from the NCBI file would be:
In the next release of Goby we will make this more clear in the documentation and add appropriate warning messages if no data is output from that mode.Code:sed -e 's/^\([0-9]\+\t\|X\t\|Y\t\)/chr\1/' -e 's/^MT\t/chrM\t/' data/biomart-mouse-exons-ensembl55-genes-NCBIM37.txt >data/biomart-mouse-exons-ensembl55-genes-NCBIM37-chr-fix.txt
Originally posted by Fabien Campagne View PostComment
-
Hi,
First I wanted to say thanks - this looks like a great tool! I'm trying to use Goby to filter out redundant reads in a very large data set. I just downloaded the package (tried 1.4 and 1.4.1), but am getting this error message for any method I try to run - Is there something I'm missing or also need to install? Machine is LINUX based and Java works for everything else I'm doing...
Thanks!
Command Line: java -jar goby.jar --help
Exception in thread "main" java.lang.ClassFormatError: edu.cornell.med.icb.goby.modes.GobyDriver (unrecognized class file version)
at java.lang.VMClassLoader.defineClass(libgcj.so.7rh)
at java.lang.ClassLoader.defineClass(libgcj.so.7rh)
at java.security.SecureClassLoader.defineClass(libgcj.so.7rh)
at java.net.URLClassLoader.findClass(libgcj.so.7rh)
at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
at gnu.java.lang.MainThread.run(libgcj.so.7rh)Comment
-
Gcj?
What version of Java are you running? RunOriginally posted by Ashok View Post
java -version
and report back.
If you are using gcj (GNU Compiler for Java) I would recommend trying Sun's java. GCJ isn't a complete Java implementation and doesn't fully implement JDK 1.4 and only parts of JDK 1.5. We target JDK 1.5 and develop with Sun's JDK 1.6.Comment
-
You are correct - I will update my machine accordingly. Thanks for the quick reply!
java -version
java version "1.4.2"
gij (GNU libgcj) version 4.1.1 20070105 (Red Hat 4.1.1-52)Comment
-
Just to clarify what Kevin stated - Goby does in fact require version 1.6+ of the Sun JDK/JRE
Originally posted by Ashok View PostComment
-
Goby 1.5
We've recently released Goby 1.5. New features include parsing and storage of sequence variations in the Goby file formats, non ambiguous storage of quality scores in reads format, support for the Bullard et al 2010 normalization method (and plugin infrastructure to add new normalization methods). The detailed change log is reproduced below.
Please note that the project is now hosted at http://goby.campagnelab.org. This new web site provides documentation for some of these new features.
* Added a mode to calculate counts and perform differential expression analysis for transcript
runs (alignment-to-transcript-counts). Transcript runs are performed against a cDNA library. They
finds matches through through exon-exon junctions represented in the input cDNA library. They are
a faster alternative to mapping the genome and exon-exon boundaries separately. Disadvantage is that
these searches will only map to transcripts represented in the input library.
* Changes to fasta-to-compact mode:
- Add parallel processing in fasta-to-compact mode. Use the --parallel flag to activate.
Will now only regenerate compact-reads that do not exist, or are older than the input file.
* Changes to CompactAlignmentToAnnotationCountsMode
- added new option --write-annotation-counts boolean, defaults to true. If set to
false the annotation counts intermediate files will not be written.
- Lines where "average count group *" values are ALL NaN or <= 0 will not be written
This makes it so lines that don't add anything to the output are just omitted.
- added new option --omit-non-informative-columns, defaults to false. If set to
true, columns in which all of the data is non-informative (values are ALL NaN or <= 0)
will be omitted.
- support for alternative global normalization methods. We currently provide an implementation of the
upper quartile normalization method by Bullard et al (BUQ) and the normalization method
provided in Goby 1.4 (CAC, normalize by the number of alignment record in a sample)
See the --normalization-methods argument. New normalization methods can be used with Goby by
creating an implementation of the edu.cornell.med.icb.goby.stats.NormalizationMethod interface,
and adding a jar on the classpath that defines a ServiceProvider (see build.xml goby-jar target
for an example of how this is done). When several normalization methods are given as an argument
to --normalization-methods Goby will produce derived statistics for each normalization method and
append them as new columns in the summary stats output. This makes it easy to compare alternative
normalization methods on the same dataset.
* Added support for sequence variations:
- changed the compact alignment format to support recording sequence variations.
- the new mode display-sequence-variations provides text output of sequence variations in several formats.
- the new mode sequence-variation-stats will print statistics about sequence variations found in a set of alignments.
* Added support for quality scores in reads format:
- Changed fasta-to-compact and compact-to-fasta to read and write with the Sanger or Illumina quality encoding.
- Modified aligners to indicate which format they require (bwa needs fastq format, lastag fasta format, lastal fastq format). This will need extensive testing as some of these changes can affect gobyweb.
We use the FASTQ-SANGER encoding to communicate with lastal.
We don't yet support the Solexa quality score encoding (it is a bit obsolete anyway).
Please note that the output format in compact-to-fasta now defaults to Fasta format.
This format has no quality scores, and consequently, we now never write quality scores
when Fasta is requested. The aligners that need quality scores must request FastaQ format
explicitely.
See also:
http://last.cbrc.jp/last/doc/last-manual.txt (look for FASTQ-SANGER)
* Other changes to the Compact formats:
- Store target/reference sequence lengths in the alignment header. This information is helpful when calculating
statistics such as RPKMs (transcript-level searches).
- Store constant query lengths as one integer. Goby 1.4.1- stored one length for each read. This can become very
memory consuming when the number of reads is very large. This change saves memory and storage.Comment
-
Goby 1.6 (python API)
We've just released Goby 1.6. Of note is a python API to parse the Goby file formats (reads and alignments, with examples of use). See the complete change log at http://campagnelab.org/software/goby/change-log/Comment
-
Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.
The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
...06-02-2026, 10:05 AM -
With the launch of new single-cell sequencing platforms in 2026, the field stands at an exciting inflection point. This article surveys the most impactful advances in the field and discusses how they’re reshaping research in cancer, immunology, and beyond.
Introduction
Single-cell sequencing technologies have undergone remarkable advances over the past decade, transitioning from low-throughput experimental approaches to highly scalable platforms capable of...05-22-2026, 06:42 AM
Comment