<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SnapGene on Michael’s Domain</title><link>https://jeltsch.org/en/tags/snapgene/</link><description>Recent content in SnapGene on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/snapgene/index.xml" rel="self" type="application/rss+xml"/><item><title>An impossible overlap-extension PCR</title><link>https://jeltsch.org/en/oep/</link><pubDate>Sat, 21 Jun 2025 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/oep/</guid><description>&lt;p&gt;A PhD student of mine asked me about plasmid maps for several DNA constructs that I had created some 20 years ago. Since 
 &lt;a href="https://snapgene.com" target="_blank" rel="noopener noreferrer nofollow"&gt;SnapGene&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 did not exist at the time, I had used the now obsolete GeneConstructionKit2. I performed many clonings at the time, but I did not continue generating maps for all of them. The GCK2 format does not allow for easy annotation. You needed a separate program for comprehensively annotating the plasmids, and this data was saved in a separate file, the so-called &amp;ldquo;illustration&amp;rdquo; file: what could possibly go wrong? Yesterday, I ended up digging out my old lab notebooks and retracing about 10 old clonings in SnapGene. However, I was unable to simulate one of the assemblies because SnapGene was too conservative in disallowing &amp;ldquo;bad&amp;rdquo; PCR primers to function. I had performed overlap-extension PCR to introduce a mutation into the mouse VEGF-D cDNA. The homologous mutation had been introduced into human VEGF-D before, and I therefore had the primers for the human sequences. Mouse and human VEGF-D are very similar. The primers designed to amplify the human PCR were not perfect when using mouse cDNA as a template, but none of the differences would result in amino acid changes. So I attempted the PCR with a primer that had a mismatch in the third nucleotide from the 3&amp;rsquo;-end. The PCR was successful, but even when I lowered the hybridisation parameters to the least stringent settings, SnapGene would not anneal this primer to my template. To simulate cloning in SnapGene and generate a map, I needed to introduce a mutation into my primer and then reverse the mutation after the overlap extension PCR. I guess I need to file a bug report (or would this be a feature request?). It seems appropriate that the program should be able to allow annealing of primers that do anneal in reality…&lt;/p&gt;</description></item><item><title>Opening old plasmid map files</title><link>https://jeltsch.org/en/gck/</link><pubDate>Sat, 01 Jan 2022 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/gck/</guid><description>&lt;p&gt;For a new cloning project, we needed to access the plasmid maps of an old construct of mine (pSecTagN2, which was a precursor of 
 &lt;a href="https://doi.org/10.1074/jbc.M511593200" target="_blank" rel="noopener noreferrer nofollow"&gt;pMosaic&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
, aka pSecTagI) which I had composed from many different sources in 1999. In 1999, I was working in 
 &lt;a href="https://www2.helsinki.fi/en/researchgroups/translational-cancer-biology" target="_blank" rel="noopener noreferrer nofollow"&gt;Kari Alitalo’s laboratory&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 as a Ph.D. student. We were at the &amp;ldquo;cutting edge&amp;rdquo; of technology because we used a software program called 
 &lt;a href="http://www.textco.com/gene-construction-kit.php" target="_blank" rel="noopener noreferrer nofollow"&gt;Gene Construction Kit&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 (GCK) to keep track of our clonings. Last Wednesday, I spent 4 hours of my working time opening one file created with GCK version 2.5 in 1999.&lt;/p&gt;</description></item><item><title>Assembly of an OCAA collection Entry vector (pENTR221)</title><link>https://jeltsch.org/en/assembly_of_an_ocaa_collection_entry_vector_pentr221/</link><pubDate>Fri, 30 Oct 2020 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/assembly_of_an_ocaa_collection_entry_vector_pentr221/</guid><description>&lt;p&gt;This article is for people, who do molecular cloning. More specifically for people who need to deal with Gateway vectors. Let&amp;rsquo;s assume you received a Gateway clone from somebody. You know the insert sequence and you know the backbone. One of the most common backbones is pENTR221. Let take as an example insert the human CTSL1 cDNA, more specifically the clone id 100010639 from the OCAA clone collection. You know the insert sequence from its Accession Number (BC012612).You want the full DNA sequence of this vector in order to be able to use smart cloning software like 
 &lt;a href="https://snapgene.com" target="_blank" rel="noopener noreferrer nofollow"&gt;SnapGene&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 to help you with your cloning design. But this software requires you to have the full sequence of the construct (or at least the full sequence of its important parts). So how do you figure out the full sequence of the pENTR221-CTSL1 clone?The insert sequence you can get from 
 &lt;a href="https://www.ncbi.nlm.nih.gov/" target="_blank" rel="noopener noreferrer nofollow"&gt;NCBI&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
: Just type in the Accession number that you got for your clone. Download the sequence in Fasta or Genbank format.Very interestingly, the otherwise smart SnapGene software does not know the pENTR221 vector. So you need to google the vector backbone &amp;ldquo;pENTR221 DNA sequence&amp;rdquo;. You get many hits and here are just four of them:1. 
 &lt;a href="http://dnasu.org/DNASU/GetVectorDetail.do?vectorid=2792" target="_blank" rel="noopener noreferrer nofollow"&gt;http://dnasu.org/DNASU/GetVectorDetail.do?vectorid=2792&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. 
 &lt;a href="https://plasmid.med.harvard.edu/PLASMID/GetVectorDetail.do?vectorid=279" target="_blank" rel="noopener noreferrer nofollow"&gt;https://plasmid.med.harvard.edu/PLASMID/GetVectorDetail.do?vectorid=279&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 3. 
 &lt;a href="https://www.genomics-online.com/vector-backbone/48/pentr221/4" target="_blank" rel="noopener noreferrer nofollow"&gt;https://www.genomics-online.com/vector-backbone/48/pentr221/4&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. 
 &lt;a href="http://yrgene.com/documents/vector/pentr221.pdfMatthias" target="_blank" rel="noopener noreferrer nofollow"&gt;http://yrgene.com/documents/vector/pentr221.pdfMatthias&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
, the author of the 4th source gives the sequence in a PDF file, which is not advisable. If you copy the DNA sequence from this file, it will be all scrambled up, because PDF does not read the groupings of 10 nucleotides line-by-line. Dear Matthias, do not use a PDF for distributing or documenting DNA sequences! If you MUST do so, please attach a plain text file of the nucleotide sequence to the PDF! Of course, you can extract the DNA sequence with a smart PDF tool like PDF Studio Pro in the correct order. For some strange reason, the sequence of the 3rd URL deviates from the other four being the only one that has the full attachment sites (attL1 and attL2). However, it does not matter which one of the sequences you use for the assembly, because the differences are all in the area that is removed during the assembly process (I don&amp;rsquo;t know how the pENTR221 vector was prepared for the library cloning of my specific example, but it looks to me that the original vector was opened with a single DraI digest (which creates blunt ends) and then first the linker were added and thereafter the insert.I suggest you use the sequence from the 3rd URL (because it is in Fasta format) and import it into SnapGene and let SnapGene detect common features. Now you still need the linker. How do you know which linker have been used? We get most of our Gateway clones from an in-house replica of the OCAA clone collection and you can download the full list of clones as an Excel spreadsheet from 
 &lt;a href="https://www.helsinki.fi/en/researchgroups/genome-biology-unit/clones-and-cloning" target="_blank" rel="noopener noreferrer nofollow"&gt;here&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. The data includes for each clones the linker that have been used (there are 8 different 5&amp;rsquo;-linker and 16 different 3&amp;rsquo;-linker). Unfortunately, it seems to be that this Excel sheet contains some errors, because some linker contain a stop codon, but are nevertheless marked &amp;ldquo;without stop&amp;rdquo; and vice-versa.For our example clone the following linker have been used:5&amp;rsquo;-linker:GTACAAAAAAGCAGGCTCCACCATG3&amp;rsquo;-linker:TAGGACCCAGCTTTCTTGTACAlmost all of the 5&amp;rsquo;-linker contain the Kozak sequence (CACC) as the last nucleotides before the insert starts and a few contain in addition to the Kozak the ATG itself (like the one above). At the other end of the linker you can easily identify the homologous sequence with the end of the attL1 of the pENTR221 backbone (GTACAAAAAAG).The 3&amp;rsquo;-linker are more heterogenous but they all contain the CTTTCTTG sequence from the attL2. When they are used to make clones with a stop codon, then they all start with that very stop codon (TAG, TGA or TAA).Now you just need to copy the open reading frame from your insert sequence in between the linker sequences. If your 3&amp;rsquo;-linker contains the initiation-ATG, you need to skip it. Also do not copy the stop codon, because in the &amp;ldquo;with stop codon clones&amp;rdquo; it is always included in the linker and in the &amp;ldquo;without stop codon clones&amp;rdquo; you don&amp;rsquo;t want to have it. For our example this sequence comprises nucleotides 202-1197 of Accession Number 
 &lt;a href="https://www.ncbi.nlm.nih.gov/nuccore/BC012612.1/" target="_blank" rel="noopener noreferrer nofollow"&gt;BC012612&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. That would be:&lt;code&gt;AATCCTACACTCATCCTTGCTGCCTTTTGCCTGGGAATTGCCTCAGCTACTCTAACATTTGATCACAGTTTAGAGGCACAGTGGACCAAGTGGAAGGCGATGCACAACAGATTATACGGCATGAATGAAGAAGGATGGAGGAGAGCAGTGTGGGAGAAGAACGTGAAGATGATTGAACTGCACAATCAGGAATACAGGGAAGGGAAACACAGCTTCACAATGGCCATGAACGCCTTTGGAGACATGACCAGTGAAGAATTCAGGCAGGTGATGAATGGCTTTCAAAACCGTAAGCCCAGGAAGGGGAAAGTGTTCCAGGAACCTCTGTTTTATGAGGCCCCCAGATCTGTGGATTGGAGAGAGAAAGGCTACGTGACTCCTGTGAAGAATCAGGGTCAGTGTGGTTCTTGTTGGGCTTTTAGTGCTACTGGTGCTCTTGAAGGACAGATGTTCCGGAAAACTGGGAGGCTTATCTCACTGAGTGAGCAGAATCTGGTAGACTGCTCTGGGCCTCAAGGCAATGAAGGCTGCAATGGTGGCCTAATGGATTATGCTTTCCAGTATGTTCAGGATAATGGAGGCCTGGACTCTGAGGAATCCTATCCATATGAGGCAACAGAAGAATCCTGTAAGTACAATCCCAAGTATTCTGTTGCTAATGACACCGGCTTTGTGGACATCCCTAAGCAGGAGAAGGCCCTGATGAAGGCAGTTGCAACTGTGGGGCCCATTTCTGTTGCTATTGATGCAGGTCATGAGTCCTTCCTGTTCTATAAAGAAGGCATTTATTTTGAGCCAGACTGTAGCAGTGAAGACATGGATCATGGTGTGCTGGTGGTTGGCTACGGATTTGAAAGCACAGAATCAGATAACAATAAATATTGGCTGGTGAAGAACAGCTGGGGTGAAGAATGGGGCATGGGTGGCTACGTAAAGATGGCCAAAGACCGGAGAAACCATTGTGGAATTGCCTCAGCAGCCAGCTACCCCACTGTG&lt;/code&gt;Now we add the linker (first and last row):&lt;code&gt;GTACAAAAAAGCAGGCTCCACCATGAATCCTACACTCATCCTTGCTGCCTTTTGCCTGGGAATTGCCTCAGCTACTCTAACATTTGATCACAGTTTAGAGGCACAGTGGACCAAGTGGAAGGCGATGCACAACAGATTATACGGCATGAATGAAGAAGGATGGAGGAGAGCAGTGTGGGAGAAGAACGTGAAGATGATTGAACTGCACAATCAGGAATACAGGGAAGGGAAACACAGCTTCACAATGGCCATGAACGCCTTTGGAGACATGACCAGTGAAGAATTCAGGCAGGTGATGAATGGCTTTCAAAACCGTAAGCCCAGGAAGGGGAAAGTGTTCCAGGAACCTCTGTTTTATGAGGCCCCCAGATCTGTGGATTGGAGAGAGAAAGGCTACGTGACTCCTGTGAAGAATCAGGGTCAGTGTGGTTCTTGTTGGGCTTTTAGTGCTACTGGTGCTCTTGAAGGACAGATGTTCCGGAAAACTGGGAGGCTTATCTCACTGAGTGAGCAGAATCTGGTAGACTGCTCTGGGCCTCAAGGCAATGAAGGCTGCAATGGTGGCCTAATGGATTATGCTTTCCAGTATGTTCAGGATAATGGAGGCCTGGACTCTGAGGAATCCTATCCATATGAGGCAACAGAAGAATCCTGTAAGTACAATCCCAAGTATTCTGTTGCTAATGACACCGGCTTTGTGGACATCCCTAAGCAGGAGAAGGCCCTGATGAAGGCAGTTGCAACTGTGGGGCCCATTTCTGTTGCTATTGATGCAGGTCATGAGTCCTTCCTGTTCTATAAAGAAGGCATTTATTTTGAGCCAGACTGTAGCAGTGAAGACATGGATCATGGTGTGCTGGTGGTTGGCTACGGATTTGAAAGCACAGAATCAGATAACAATAAATATTGGCTGGTGAAGAACAGCTGGGGTGAAGAATGGGGCATGGGTGGCTACGTAAAGATGGCCAAAGACCGGAGAAACCATTGTGGAATTGCCTCAGCAGCCAGCTACCCCACTGTGTAGGACCCAGCTTTCTTGTAC&lt;/code&gt;Now we have the first problem: There is a stop codon in the 3&amp;rsquo;-linker (immediately in the beginning of the last row) even though the clone is according to the information that we received &amp;ldquo;without stop codon&amp;rdquo;.We have sequenced the clone and determined that the only difference between the with and without stop codon clones is a mutation, that converts the TAG stop codon into a TTG (leucin) codon.So we change one A nucleotide in the sequence above into a T nucleotide:&lt;code&gt;GTACAAAAAAGCAGGCTCCACCATGAATCCTACACTCATCCTTGCTGCCTTTTGCCTGGGAATTGCCTCAGCTACTCTAACATTTGATCACAGTTTAGAGGCACAGTGGACCAAGTGGAAGGCGATGCACAACAGATTATACGGCATGAATGAAGAAGGATGGAGGAGAGCAGTGTGGGAGAAGAACGTGAAGATGATTGAACTGCACAATCAGGAATACAGGGAAGGGAAACACAGCTTCACAATGGCCATGAACGCCTTTGGAGACATGACCAGTGAAGAATTCAGGCAGGTGATGAATGGCTTTCAAAACCGTAAGCCCAGGAAGGGGAAAGTGTTCCAGGAACCTCTGTTTTATGAGGCCCCCAGATCTGTGGATTGGAGAGAGAAAGGCTACGTGACTCCTGTGAAGAATCAGGGTCAGTGTGGTTCTTGTTGGGCTTTTAGTGCTACTGGTGCTCTTGAAGGACAGATGTTCCGGAAAACTGGGAGGCTTATCTCACTGAGTGAGCAGAATCTGGTAGACTGCTCTGGGCCTCAAGGCAATGAAGGCTGCAATGGTGGCCTAATGGATTATGCTTTCCAGTATGTTCAGGATAATGGAGGCCTGGACTCTGAGGAATCCTATCCATATGAGGCAACAGAAGAATCCTGTAAGTACAATCCCAAGTATTCTGTTGCTAATGACACCGGCTTTGTGGACATCCCTAAGCAGGAGAAGGCCCTGATGAAGGCAGTTGCAACTGTGGGGCCCATTTCTGTTGCTATTGATGCAGGTCATGAGTCCTTCCTGTTCTATAAAGAAGGCATTTATTTTGAGCCAGACTGTAGCAGTGAAGACATGGATCATGGTGTGCTGGTGGTTGGCTACGGATTTGAAAGCACAGAATCAGATAACAATAAATATTGGCTGGTGAAGAACAGCTGGGGTGAAGAATGGGGCATGGGTGGCTACGTAAAGATGGCCAAAGACCGGAGAAACCATTGTGGAATTGCCTCAGCAGCCAGCTACCCCACTGTGTTGGACCCAGCTTTCTTGTAC&lt;/code&gt;The last operation is to insert this sequence into the empty pENTR221 sequence that we have opened in SnapGene. Practically you select the 32 nucleotides from 652 to 687 and replace them with the sequence above. Voila! Unfortunately, the fact that the linker are not always correctly indicated gives me a bad feeling. However, according to our own experience the library replicas of the Orfeome contain sufficient errors that it is anyway advisable to sequence the complete insert using T7 or M13 rev primers from the 3&amp;rsquo;-end and M13 fwd primer from the 5&amp;rsquo;-end. This way, you will figure out any linker mistakes that have been done in the annotation of the clones.&lt;/p&gt;</description></item><item><title>SnapGene and partial restriction digests revisited</title><link>https://jeltsch.org/en/snapgene_and_partial_restriction_digests_revisited/</link><pubDate>Thu, 23 Aug 2018 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/snapgene_and_partial_restriction_digests_revisited/</guid><description>&lt;p&gt;Snapgene is a software for the wet lab molecular biologist, who does lots of cloning work (construct design and annotation). Since I last wrote about the SnapGene software (
 &lt;a href="https://www.snapgene.com/" target="_blank" rel="noopener noreferrer nofollow"&gt;https://www.snapgene.com/&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 ), many good things have happened:&lt;/p&gt;</description></item><item><title>Remote desktop sessions to your Helsinki University work computer</title><link>https://jeltsch.org/en/remote_desktop_sessions_to_your_helsinki_university_work_computer/</link><pubDate>Mon, 15 Jan 2018 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/remote_desktop_sessions_to_your_helsinki_university_work_computer/</guid><description>&lt;p&gt;If you have a work laptop, you can take it home to do work. But what if you have a desktop computer and need to access it from home? The technology to make this possible exists for more than 20 years, but if you think that University IT has made this easy for you, you would be wrong. In fact, I don&amp;rsquo;t know anybody who knows how to do this (let alone how to make the process easy). Even with the setup explained below, some things do not work well (e.g. I never could figure out how to get the file sharing to work with a Mac-to-Mac connection and thus I still use 
 &lt;a href="http://rsug.itd.umich.edu/software/fugu/" target="_blank" rel="noopener noreferrer nofollow"&gt;Fugu&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 with a separate tunnelled sftp connection to transfer files). You have several options:&lt;/p&gt;</description></item><item><title>SnapGene - Simply the best DNA manipulation software</title><link>https://jeltsch.org/en/snapgene_simply_the_best_dna_manipulation_software/</link><pubDate>Fri, 01 Jan 2016 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/snapgene_simply_the_best_dna_manipulation_software/</guid><description>&lt;p&gt;Our lab has been using different software packages to plan, document and visualize DNA constructs. Among those that we liked a lot for a long time were Textco&amp;rsquo;s 
 &lt;a href="http://www.textco.com/gene-construction-kit.php" target="_blank" rel="noopener noreferrer nofollow"&gt;GeneConstructionKit&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 (GCK) and 
 &lt;a href="http://www.scied.com/pr_cmpro.htm" target="_blank" rel="noopener noreferrer nofollow"&gt;Clone Manager (Professional)&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. The latter runs unfortunately only under Windows. However, since several of our computers run 
 &lt;a href="http://www.ubuntu.com/desktop" target="_blank" rel="noopener noreferrer nofollow"&gt;Ubuntu Linux&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
, we did run GCK versions 2.5 and 3 using 
 &lt;a href="https://www.winehq.org/" target="_blank" rel="noopener noreferrer nofollow"&gt;WINE&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 (a compatibility layer that allows us to run native Windows programs under Linux). However, with the upgrade to version 4, GCK became unusably slow under WINE and we were looking for a replacement. We contacted the developers of GCK, but they apparently were either not willing or able to help us. I suppose that the codebase of GCK is probably more than 20 years old and for that reason nobody dares to touch it. Just around that time, 
 &lt;a href="http://www.snapgene.com" target="_blank" rel="noopener noreferrer nofollow"&gt;SnapGene&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 was released and it fulfilled almost all of our requirements:&lt;/p&gt;</description></item><item><title>Shortcoming of silent mutagenesis tools (EMBOSS, GCK): WatCut as a solution</title><link>https://jeltsch.org/en/shortcoming_of_silent_mutagenesis_tools_emboss_gck_watcut_as_a_solution/</link><pubDate>Sun, 22 Feb 2004 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/shortcoming_of_silent_mutagenesis_tools_emboss_gck_watcut_as_a_solution/</guid><description>&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; As of May 2026, the last functional instance of the WatCut web service (by the University of Pittsburgh) was discontinued. However, tools like Snapgene (
 &lt;a href="https://snapgene.com" target="_blank" rel="noopener noreferrer nofollow"&gt;https://snapgene.com&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 ) have the same functionality (i.e. can detect novel restriction sites by silent mutagenesis of two nucleotides).&lt;/p&gt;</description></item></channel></rss>