Good Morning Andrea:
This process at UCSC has been using 'lastz' since about 2008.
The legacy name 'blastz' is sometimes used in procedure names and
scripts but that is just symbolic, it is not the program we are using.
The reason we are using lav output and the conversions to psl is
due to the types of inputs we give to lastz and the resulting
output types from lastz given those .2bit input formats. Our input
and output formats have been selected to optimize the compute times
for the procedure.
We can not say if a different procedure would produce the same results.
--Hiram
On 5/13/20 7:55 AM, TALENTI Andrea wrote:
> Good morning,
> I’m writing you about the genome liftover pipeline used for different species.
> Looking at the doBlastzChainNet.pl, it looks like you proceed in the following way:
>
> 1. Align with blastz with proper parameters and save as lav
> 2. Convert to psl with lavToAxt -dropSelf | axtToPsl
> 3. Chain everything with chainAxt | chainAntiRepeat
> 4. Merge and sort with chainMergeSort
> 5. Make a net file with chainPreNet | chainNet | netSyntenic
> 6. Make the liftover chain file with netChainSubset | chainStitchId
>
> Is this correct?
>
> Also, since I’m trying to use lastz instead of blastz, I’d like to know if it is possible to obtain similar results with the following workflow:
>
> 1. Align pairs of sequences (source to target) using lastz and save as axt
> 2. Concatenate the axt files for every pairwise alignments of source/target sequences
> 3. Use the new concatenated axt as input for chainAxt
> 4. Proceed as above