Site upgrade to Mambo 4.5.2

Mambo group released 4.5.2 today and my site has been upgraded as well. Two great features that I have noticed are:

  1. "Latest News" and "Popular" modules shows the correct items. The
    items that requires higher privileges (ie. special) will not appear on
    the pages for guest users. This is a great bug fix.
  2. New "GeShi syntax highlighting" mambot works great for C and Perl code in my article.

Continue reading

Add X440 (linux) to LSF cluster

Some of the application Alan needs are not available for OSX and they
need to run it on a linux machine (X440). As a result, this machine is
expected to be available for the cluster and so for the /nfs2 file
system. Last year, I had a LSF copy installed on X440 and run it as a
standalone cluster system. Now the major work is to re-configure the
two cluster and merge them together.

Continue reading

Mambo wins two more great awards

According to Mambo offical site,
the winners of the Product Excellence Awards at LinuxWorld Conference
& Expo(R) in Boston have been announced!

Best Open Source Solution
was awarded to Mambo: Mambo 4.5.1a. Not only that, the "Best of Show"
award, which recognizes the best total industry solution, was also
award to Mambo as well.

Continue reading

Issues on re-running a failed pipeline

A pipeline is a seriez of applications running one after the other. Any
two connected applications are related either by files or database.
Currently we support only file-based connection. The pipeline jobs may
fail if any step inside the pipeline fails, or the files that should
connect two applications are not generated correctly, due to pipeline
misconfiguration.

For example, in the phylip tree protocol, where six steps (Clustalw
-> SeqBoot -> ProtDist -> Neighbor -> Consense ->
DrawTree) are generally involved, the failure of "seqboot" will stop
the entire pipeline. Or, "consense" should generate a phylip-tree
format file for drawtree, but in fact the expected file is not found
because pipeline designer chose the wrong configuration for "consense".
In this case, there is no failed job inside pipeline, but the pipeline
itself hangs and there will be no further jobs to be initialized.

Continue reading