Skip to content

Commit

Permalink
Update varVAMP to version 1.1.2 (#5933)
Browse files Browse the repository at this point in the history
* Update varvamp to latest version, pin key dependencies

* Fix citation
  • Loading branch information
wm75 authored Apr 5, 2024
1 parent 01e7e08 commit 1626c59
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
2 changes: 1 addition & 1 deletion tools/varvamp/macros.xml
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
<?xml version="1.0"?>
<macros>
<token name="@TOOL_VERSION@">1.1.1</token>
<token name="@TOOL_VERSION@">1.1.2</token>
<token name="@VERSION_SUFFIX@">0</token>
<xml name="main_parameters">
<conditional name="main_params">
Expand Down
4 changes: 3 additions & 1 deletion tools/varvamp/varvamp.xml
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@
</xrefs>
<requirements>
<requirement type="package" version="@TOOL_VERSION@">varvamp</requirement>
<requirement type="package" version="2.0.1">primer3-py</requirement>
<requirement type="package" version="0.7.17">seqfold</requirement>
</requirements>
<version_command>varvamp --version</version_command>
<command detect_errors="exit_code"><![CDATA[
Expand Down Expand Up @@ -458,6 +460,6 @@ Testing with a new alignment/analysis:
As a first check whether a new alignment of viral sequences can be used with specific settings of the tool, it may help to disable all configurable outputs, which will leave you with only the Analysis Log. This will be enough to see if there are any errors with the combination of alignment and settings, and whether you are on a roughly correct track (varVAMP reports some primers, for example). This way, you're not flooding your analysis history with lots of likely useless datasets, and once you've fixed potential issues you can add back more outputs and rerun the analysis.
]]></help>
<citations>
<citation type="doi">https://github.com/jonas-fuchs/varVAMP/</citation>
<citation type="doi">10.5281/zenodo.10908223</citation>
</citations>
</tool>

0 comments on commit 1626c59

Please sign in to comment.