View Single Post
Old 05-14-2014, 02:10 AM   #4
Hyunmin
Member
 
Location: Seoul, Korea

Join Date: Feb 2012
Posts: 13
Default

Quote:
Originally Posted by Bob-Harris View Post
The short answer is you need to use lastz_32 instead of lastz.

The long answer… the default lastz build can only handle a target up to 2Gbp combined length. This was a conscious design choice (circa 2004), as there is some efficiency gain from limiting the variables that track sequence positions to 31 bits. The lastz_32 build relaxes that constraint so that it can handle a target up to 4Gbp combined length.

The efficiency gain was more important on machines 10 years ago than it is now, but for backward compatibility I am keeping that as the default behavior. I'll (probably) change this error report on future releases so that it tells the user to consider using lastz_32.

The issue is discussed in the readme file here:
http://www.bx.psu.edu/~rsharris/last...v_whole_genome

Bob H
(lastz author)
sorry, my late thread..

I solve the problem with upper.
Thanks!
Hyunmin is offline   Reply With Quote