febcba57979e8638ada173f0d26eba18cd51b3a8 hiram Tue Jul 30 13:29:27 2024 -0700 can be used for a UCSC database assembly with special arguments refs #34149 diff --git src/hg/utils/automation/asmHubChainNetComposite.pl src/hg/utils/automation/asmHubChainNetComposite.pl index 8342028..ec69330 100755 --- src/hg/utils/automation/asmHubChainNetComposite.pl +++ src/hg/utils/automation/asmHubChainNetComposite.pl @@ -1,339 +1,349 @@ #!/usr/bin/env perl use strict; use warnings; use FindBin qw($Bin); use lib "$Bin"; use AsmHub; use HgAutomate; use File::Basename; my $argc = scalar(@ARGV); if ($argc != 3) { printf STDERR "usage: asmHubChainNet.pl asmId ncbiAsmId asmId.names.tab > asmId.chainNet.html\n"; printf STDERR "where asmId is the assembly identifier,\n"; printf STDERR "and asmId.names.tab is naming file for this assembly,\n"; + printf STDERR "for UCSC database assemblies, use the third argument asmId.names.tab\n"; + printf STDERR " as the Scientific_name for the organism.\n"; exit 255; } # specific to UCSC environment my $dbHost = "hgwdev"; my $asmId = shift; my $ncbiAsmId = shift; my $namesFile = shift; my $queryId = ""; my $targetBuildDir = ""; if ($asmId =~ m/^GC/) { my $gcX = substr($asmId,0,3); my $d0 = substr($asmId,4,3); my $d1 = substr($asmId,7,3); my $d2 = substr($asmId,10,3); my $hubBuildDir = "refseqBuild"; $hubBuildDir = "genbankBuild" if ($gcX eq "GCA"); $targetBuildDir = "/hive/data/genomes/asmHubs/$hubBuildDir/$gcX/$d0/$d1/$d2/$asmId"; } else { $targetBuildDir = "/hive/data/genomes/$asmId"; } my %queryDates; # key is asmId, value is assembly date my %queryCommonName; # key is asmId, value is assembly common name my %querySubmitter; # key is asmId, value is assembly submitter my %fbStats; # key is asmId, value is featureBits measure for chains my %synStats; # key is asmId, value is featureBits measure for syntenic my %rbStats; # key is asmId, value is featureBits measure for recip best my %loStats; # key is asmId, value is featureBits measure for lift over open (TD, "ls -d ${targetBuildDir}/trackData/lastz.*|") or die "can not ls -d ${targetBuildDir}/trackData/lastz.*"; while (my $accession = <TD>) { chomp $accession; $accession =~ s#.*/trackData/lastz.##; # the hubDateName will translate the accessionId into an asmId # side effect it also returns the date my ($qDate, $qAsmName) = &HgAutomate::hubDateName($accession); my $qAsmId = "${accession}"; if ($accession =~ m/^GC/) { $qAsmId = "${accession}${qAsmName}"; } my $Accession = ucfirst($accession); $queryDates{$qAsmId} = $qDate; my ($qCommonName, undef, $qSubmitter) = &HgAutomate::getAssemblyInfo($dbHost, $qAsmId); $queryCommonName{$qAsmId} = $qCommonName; $querySubmitter{$qAsmId} = $qSubmitter; my $fbTxt = `ls ${targetBuildDir}/trackData/lastz.${accession}/fb.*chain${Accession}Link.txt 2> /dev/null`; chomp $fbTxt; if ( -s "${fbTxt}" ) { my $fBits = `cut -d' ' -f5 $fbTxt | tr -d '()%'`; chomp $fBits; $fbStats{$qAsmId} = $fBits; } else { $fbStats{$qAsmId} = "n/a"; } $fbTxt = `ls ${targetBuildDir}/trackData/lastz.${accession}/fb.*chainSyn${Accession}Link.txt 2> /dev/null`; chomp $fbTxt; if ( -s "${fbTxt}" ) { my $fBits = `cut -d' ' -f5 $fbTxt | tr -d '()%'`; chomp $fBits; $synStats{$qAsmId} = $fBits; } else { $synStats{$qAsmId} = "n/a"; } $fbTxt = `ls ${targetBuildDir}/trackData/lastz.${accession}/fb.*chainRBest.${Accession}.txt 2> /dev/null`; chomp $fbTxt; if ( -s "${fbTxt}" ) { my $fBits = `cut -d' ' -f5 $fbTxt | tr -d '()%'`; chomp $fBits; $rbStats{$qAsmId} = $fBits; } else { $rbStats{$qAsmId} = "n/a"; } $fbTxt = `ls ${targetBuildDir}/trackData/lastz.${accession}/fb.*chainLiftOver${Accession}Link.txt 2> /dev/null`; chomp $fbTxt; if ( -s "${fbTxt}" ) { my $fBits = `cut -d' ' -f5 $fbTxt | tr -d '()%'`; chomp $fBits; $loStats{$qAsmId} = $fBits; } else { $loStats{$qAsmId} = "n/a"; } } close (TD); -my $ncbiAssemblyId = `grep -v "^#" $namesFile | cut -f10`; +my $ncbiAssemblyId = $ncbiAsmId; + +if ( -s "${namesFile}" ) { + $ncbiAssemblyId = `grep -v "^#" $namesFile | cut -f10`; chomp $ncbiAssemblyId; +} +my $sciName = ${namesFile}; + +if ( -s "${namesFile}" ) { my $sciName = `grep -v "^#" $namesFile | cut -f5`; chomp $sciName; +} my ($tGenome, $tDate, $tSource) = &HgAutomate::getAssemblyInfo($dbHost, $asmId); print <<_EOF_ <h2>Description</h2> <p> This track shows regions of this <em>target</em> genome ($tGenome - $tDate - $tSource) that has alignment to other <em>query</em> genomes ("chain" subtracks) or in synteny ("net" subtracks). The alignable parts are shown with thick blocks that look like exons. Non-alignable parts between these are shown like introns. </p> <p> Other <em>query</em> genome assemblies aligning to this <em>target</em> genome assembly: <ul> _EOF_ ; my @orderedByFBits; foreach my $qDb ( sort {$fbStats{$b} <=> $fbStats{$a}} keys %fbStats) { push @orderedByFBits, $qDb; } foreach my $oAsmId (@orderedByFBits) { my $fbPercent = ""; $fbPercent = "% $fbStats{$oAsmId} " if (defined($fbStats{$oAsmId})); if ($oAsmId =~ m/^GC/) { printf "<li>%s<a href='https://genome.ucsc.edu/h/%s' target=_blank>%s</a> %s %s %s</li>\n", $fbPercent, $oAsmId, $oAsmId, $queryCommonName{$oAsmId}, $queryDates{$oAsmId}, $querySubmitter{$oAsmId}; } else { printf "<li>%s<a href='https://genome.ucsc.edu/cgi-bin/hgTracks?db=%s' target=_blank>%s</a> %s %s %s</li>\n", $fbPercent, $oAsmId, $oAsmId, $queryCommonName{$oAsmId}, $queryDates{$oAsmId}, $querySubmitter{$oAsmId}; } } printf "</ul> </p>\n"; printf "<h3>Alignments identity</h3>\n"; printf "<table border='1'>\n"; printf "<caption>showing percent identity, how much of the target is matched by the query</caption>\n"; printf "<thead style='position:sticky; top:0; background-color: white;'><tr>\n"; printf "<th>chains</th><th>syntenic</th><th>reciprocal<br>best</th><th>lift<br>over</th><th>common<br>name</th><th>assembly</th>\n"; printf "</tr></thead><tbody>\n"; foreach my $oAsmId (@orderedByFBits) { printf "<tr>"; if (defined($fbStats{$oAsmId})) { printf "<td style='text-align:right;'>%s</td>", $fbStats{$oAsmId}; } else { printf "<td style='text-align:right;'> </td>"; } if (defined($synStats{$oAsmId})) { printf "<td style='text-align:right;'>%s</td>", $synStats{$oAsmId}; } else { printf "<td style='text-align:right;'> </td>"; } if (defined($rbStats{$oAsmId})) { printf "<td style='text-align:right;'>%s</td>", $rbStats{$oAsmId}; } else { printf "<td style='text-align:right;'> </td>"; } if (defined($loStats{$oAsmId})) { printf "<td style='text-align:right;'>%s</td>", $loStats{$oAsmId}; } else { printf "<td style='text-align:right;'> </td>"; } printf "<td>%s</td><td>%s</td></tr>\n", $queryCommonName{$oAsmId}, $oAsmId; } printf "</tbody></table>\n"; print <<_EOF_ <h3>Chain Track</h3> <p> The chain tracks shows alignments of the other genome assemblies to the $tGenome/$sciName/$ncbiAssemblyId/$tDate genome using a gap scoring system that allows longer gaps than traditional affine gap scoring systems. It can also tolerate gaps in both <em>query</em> and <em>target</em> genomes simultaneously. These "double-sided" gaps can be caused by local inversions and overlapping deletions in both species. </p> <p> The chain track displays boxes joined together by either single or double lines. The boxes represent aligning regions. Single lines indicate gaps that are largely due to a deletion in the <em>query</em> assembly or an insertion in the <em>target</em> assembly. Double lines represent more complex gaps that involve substantial sequence in both species. This may result from inversions, overlapping deletions, an abundance of local mutation, or an unsequenced gap in one species. In cases where multiple chains align over a particular region of the <em>target</em> genome, the chains with single-lined gaps are often due to processed pseudogenes, while chains with double-lined gaps are more often due to paralogs and unprocessed pseudogenes.</p> <p> In the "pack" and "full" display modes, the individual feature names indicate the chromosome, strand, and location (in thousands) of the match for each matching alignment.</p> <p> There could be four different types of chain tracks: <ul> <li><b>Chains</b> - The first level of chain track showing all potential chains. The other chain tracks are derived from this chain data.</li> <li><b>Syntenic</b> - Filtered first level chain showing the corresponding regions between the two genomes in the alignment that have the same order of blocks and direction in the alignment.</li> <li><b>Reciprocal best</b> - Filtered first level chain showing the corresponding regions where the best target to query alignment, and the best query to target alignment identify the same regions.</li> <li><b>Lift over</b> - filtered first level chain selecting out the best/longest syntenic regions used to translate coordinates from the target genome to the query genome.</li> </ul> </p> <h3>Alignment Track</h3> <p> The alignment track shows the <b>net</b> derived from the chain data in the format of a pair-wise side by side alignment. The net file is converted to the <a href='https://genome.ucsc.edu/FAQ/FAQformat.html#format5' target=_blank>MAF format</a> for this display. </p> <h2>Display Conventions and Configuration</h2> <h3>Chain Track</h3> <p>By default, the chains to chromosome-based assemblies are colored based on which chromosome they map to in the aligning organism. To turn off the coloring, check the "off" button next to: Color track based on chromosome.</p> <p> To display only the chains of one chromosome in the aligning organism, enter the name of that chromosome (e.g. chr4) in box next to: Filter by chromosome.</p> <h2>Alignment Track</h3> <p> At base level in full display mode, this track will show the sequence of <em>query</em> as it aligned to <em>target</em>. When the view is too large to show such detail, blocks of alignments will show corresponding alignments to other chromosomes with colors indicating other chromosomes. </p> <h2>Methods</h2> <h3>Chain track</h3> <p> The <em>query</em> genome was aligned to <em>target</em> genome with <em>lastz</em>. The resulting alignments were converted into axt format using the <em>lavToAxt</em> program. The axt alignments were fed into <em>axtChain</em>, which organizes all alignments between a single <em>query</em> chromosome and a single <em>target</em> chromosome into a group and creates a kd-tree out of the gapless subsections (blocks) of the alignments. A dynamic program was then run over the kd-trees to find the maximally scoring chains of these blocks. </p> <h3>Alignment track</h3> <p> Chains were derived from lastz alignments, using the methods described on the chain tracks description pages, and sorted with the highest-scoring chains in the genome ranked first. The program <em>chainNet</em> was then used to place the chains one at a time, trimming them as necessary to fit into sections not already covered by a higher-scoring chain. During this process, a natural hierarchy emerged in which a chain that filled a gap in a higher-scoring chain was placed underneath that chain. The program <em>netSyntenic</em> was used to fill in information about the relationship between higher- and lower-level chains, such as whether a lower-level chain was syntenic or inverted relative to the higher-level chain. The program <em>netClass</em> was then used to fill in how much of the gaps and chains contained <em>N</em>s (sequencing gaps) in one or both species and how much was filled with transposons inserted before and after the two organisms diverged. </p> <p> The resulting net file was converted to axt format via <em>netToAxt</em>, then converted to maf format via <em>axtToMaf</em>, then converted to the bigMaf format with <em>mafToBigMaf</em> and <em>bedToBigBed</em> </p> <h2>Credits</h2> <p> <em>lastz</em> was developed by Robert Harris, Pennsylvania State University. </p> <p> The <em>axtChain</em> program was developed at the University of California at Santa Cruz by Jim Kent with advice from Webb Miller and David Haussler.</p> <p> The browser display and database storage of the chains and nets were created by Robert Baertsch and Jim Kent.</p> <p> The <em>chainNet</em>, <em>netSyntenic</em>, and <em>netClass</em> programs were developed at the University of California Santa Cruz by Jim Kent.</p> <h2>References</h2> <p> Harris, R.S. <a href="http://www.bx.psu.edu/~rsharris/lastz/" target=_blank>(2007) Improved pairwise alignment of genomic DNA</a> Ph.D. Thesis, The Pennsylvania State University </p> <p> Chiaromonte F, Yap VB, Miller W. <A HREF="http://psb.stanford.edu/psb-online/proceedings/psb02/chiaromonte.pdf" TARGET=_blank>Scoring pairwise genomic sequence alignments</A>. <em>Pac Symp Biocomput</em>. 2002:115-26. PMID: <a href="https://www.ncbi.nlm.nih.gov/pubmed/11928468" target="_blank">11928468</a> </p> <p> Kent WJ, Baertsch R, Hinrichs A, Miller W, Haussler D. <A HREF="https://www.pnas.org/content/100/20/11484" TARGET=_blank>Evolution's cauldron: duplication, deletion, and rearrangement in the mouse and human genomes</A>. <em>Proc Natl Acad Sci U S A</em>. 2003 Sep 30;100(20):11484-9. PMID: <a href="https://www.ncbi.nlm.nih.gov/pubmed/14500911" target="_blank">14500911</a>; PMC: <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC208784/" target="_blank">PMC208784</a> </p> <p> Schwartz S, Kent WJ, Smit A, Zhang Z, Baertsch R, Hardison RC, Haussler D, Miller W. <A HREF="https://genome.cshlp.org/content/13/1/103.abstract" TARGET=_blank>Human-mouse alignments with BLASTZ</A>. <em>Genome Res</em>. 2003 Jan;13(1):103-7. PMID: <a href="https://www.ncbi.nlm.nih.gov/pubmed/12529312" target="_blank">12529312</a>; PMC: <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC430961/" target="_blank">PMC430961</a> </p> _EOF_ ;