- Warning: Array to string conversion in Drupal\Core\Template\AttributeArray->__toString() (line 77 of core/lib/Drupal/Core/Template/AttributeArray.php).
Drupal\Core\Template\AttributeArray->__toString() (Line: 53)
Drupal\Core\Template\AttributeValueBase->render() (Line: 324)
Drupal\Core\Template\Attribute->__toString() (Line: 40)
__TwigTemplate_1c7d6fa4f60971d5f6825029b91a632c4a9856410e8f9dda904f1f54a370dd4e->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('modules/contrib/entity_embed/templates/entity-embed-container.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('entity_embed_container', Array) (Line: 489)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 212)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->Drupal\entity_embed\Plugin\Filter\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 213)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->process('<strong>The Palisade Insectary applies many scientific protocols and methods to study biocontrol agents. Investigations are made into the safety, impact, effectiveness, establishment, and spread of agents and pest hosts. </strong>
<strong>Here are some of the research methods utilized.</strong>
<dl class="ckeditor-accordion"><dt>Laboratory Research and Rearing</dt>
<dd>
Before most agents are released into the wider ecosystem, extensive laboratory research is conducted to ensure the safety, effectiveness and impact of the agents on the target pest species. The Palisade Insectary conducts research into the lifecycles and interactions of agents and their hosts.
Laboratory rearing of certain agents is critical to build populations, or to maintain populations that may not overwinter in Colorado's climate.
</dd>
<dt>Surveys and Releases</dt>
<dd>
Consistent surveying of vegetation and biocontrol agents across Colorado allows the Palisade Insectary to identify emerging pest problems, find and utilize field nursery sites to redistribute agents, and establish agents in areas where they are most needed.
</dd>
<dt>Field Monitoring</dt>
<dd>
Multiple monitoring methods are used by the Insectary to look at the effects of different biocontrols. The most common methods are:
<ul><li>SIMP (Standardized Impact Monitoring Protocol)
<ul><li>Developed by researchers in Idaho and adopted nationally, the SIMP protocol is used to document target weed density, vegetation cover, and biological control agent abundance along a 20-meter transect. Data can be documented on a SIMP form (<a href="https://invasivespecies.idaho.gov/bio-control-monitoring">Idaho Invasive Species</a>) or using the <a href="https://www.ibiocontrol.org/simp.cfm">iBiocontrol App</a> on a mobile device. </li>
</ul></li>
<li>Macro Plot Monitoring
<ul><li>This monitoring consists of a 16-meter square plot along with six 50-meter transects going out from the agent release point to document changes in the abundance of the targeted plant species, changes in the abundance of the insect biocontrol agent, expansion of impact area away from the point of introduction, and changes in the overall vegetation community. </li>
</ul></li>
</ul></dd>
<dt>Field Experiments</dt>
<dd>
Conducting field experiments allows the Palisade Insectary to look at biological control in the context of Colorado's environment. Experiments in field conditions can answer questions that more broadly address biocontrol effects on plant species composition and integration with other control methods.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Data Analysis and Mapping</dt>
<dd>
Survey, monitoring, release, and experimental data are utilized by the Palisade Insectary to make better land management decisions for the control of invasive pest species. Data collected is verified, analyzed and then shared to improve biocontrol usage and effectiveness.
Mapping of Colorado's weed and insect pests can help manage the spread of pests and create more effective control strategies.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Research Collaboration</dt>
<dd>
The Palisade Insectary participates in regional and national biocontrol programs, and has established partnerships with many individuals and organizations to facilitate biocontrol projects in Colorado. We have a long history of collaboration on projects with the USDA, CSU, CMU, USU, US Forest Service, BLM, EPA, SERDP, international organizations and many other biocontrol researchers in the US.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Outreach</dt>
<dd>
One of our main goals is to inform resource managers, landowners, and the general public of the availability of agents and help them understand the opportunities to utilize biological control to improve their pest control efforts and achieve management objectives. We do this through our website, press releases, social media posts, presentations, and group tours of the Insectary.
</dd>
</dl><dl class="ckeditor-accordion"><dt>International Code of Best Practices for Classical Biological Control of Weeds</dt>
<dd>
The Code was approved in 1999 by the delegates to the 10th International Symposium on Biological Control of Weeds and provides a standard guideline for biological control:
<ol><li>Ensure target weed’s potential impact justifies release of non-endemic agents</li>
<li>Obtain multi-agency approval for target </li>
<li>Select agents with the potential to control the target weed</li>
<li>Release safe and approved agents</li>
<li>Ensure only the intended agent is released</li>
<li>Use appropriate protocols for release and documentation</li>
<li>Monitor impact on the target plant species</li>
<li>Stop releases of ineffective agents, or when control is achieved</li>
<li>Monitor impacts on potential non target species</li>
<li>Encourage assessment of changes in plant and animal communities</li>
<li>Monitor interactions among agents</li>
<li>Communicate the results to the public
</li>
</ol></dd>
</dl>Project Spotlight
<dl class="ckeditor-accordion"><dt>SERDP Funded Phenology Modeling of Tamarix and Biological Controls</dt>
<dd>
In cooperation with the Department of Defense Strategic Environmental Research and Development Program (SRDP), researchers at the CDA Palisade Insectary and Oregon State University have developed a phenology model of the Northern Tamarisk Beetle, <em>Diorhabda carinulata</em>. This model predicts when different life stages of the beetle occur in the field based on temperature and day length. This is particularly important to predict when these beneficial biological control agents may be collected and redistributed. The model is applicable to all of North America and may also be applied to other <em>Diorhabda</em> species with success. This lifecycle model can be located at <a href="http://uspest.org/">uspest.org</a>, which also has models for many other insects both pest species and beneficials.
</dd>
</dl>
', 'en') (Line: 118)
Drupal\filter\Element\ProcessedText::preRenderText(Array)
call_user_func_array(Array, Array) (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 374)
Drupal\Core\Render\Renderer->doRender(Array, 1) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, 1) (Line: 160)
Drupal\Core\Render\Renderer->Drupal\Core\Render\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 161)
Drupal\Core\Render\Renderer->renderPlain(Array) (Line: 62)
Drupal\text\TextProcessed->getValue() (Line: 140)
Drupal\Core\Field\FieldItemBase->__get('processed') (Line: 139)
node_tokens('node', Array, Array, Array, Object)
call_user_func_array(Object, Array) (Line: 426)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}(Object, 'node') (Line: 405)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('tokens', Object) (Line: 433)
Drupal\Core\Extension\ModuleHandler->invokeAll('tokens', Array) (Line: 357)
Drupal\Core\Utility\Token->generate('node', Array, Array, Array, Object) (Line: 239)
Drupal\Core\Utility\Token->doReplace(1, '[node:summary]', Array, Array, Object) (Line: 189)
Drupal\Core\Utility\Token->replace('[node:summary]', Array, Array, NULL) (Line: 66)
Drupal\metatag\MetatagToken->replace('[node:summary]', Array, Array) (Line: 586)
Drupal\metatag\MetatagManager->generateRawElements(Array, Object) (Line: 493)
Drupal\metatag\MetatagManager->generateElements(Array, Object) (Line: 529)
metatag_get_tags_from_route() (Line: 298)
_metatag_remove_duplicate_entity_tags(Array) (Line: 244)
metatag_entity_view_alter(Array, Object, Object) (Line: 562)
Drupal\Core\Extension\ModuleHandler->alter('node_view', Array, Object, Object) (Line: 305)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 239)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func_array(Array, Array) (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 374)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 242)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 243)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 132)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 174)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
- Warning: Array to string conversion in Drupal\Core\Template\AttributeArray->__toString() (line 78 of core/lib/Drupal/Core/Template/AttributeArray.php).
Drupal\Core\Template\AttributeArray->__toString() (Line: 53)
Drupal\Core\Template\AttributeValueBase->render() (Line: 324)
Drupal\Core\Template\Attribute->__toString() (Line: 40)
__TwigTemplate_1c7d6fa4f60971d5f6825029b91a632c4a9856410e8f9dda904f1f54a370dd4e->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('modules/contrib/entity_embed/templates/entity-embed-container.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('entity_embed_container', Array) (Line: 489)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 212)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->Drupal\entity_embed\Plugin\Filter\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 213)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->process('<strong>The Palisade Insectary applies many scientific protocols and methods to study biocontrol agents. Investigations are made into the safety, impact, effectiveness, establishment, and spread of agents and pest hosts. </strong>
<strong>Here are some of the research methods utilized.</strong>
<dl class="ckeditor-accordion"><dt>Laboratory Research and Rearing</dt>
<dd>
Before most agents are released into the wider ecosystem, extensive laboratory research is conducted to ensure the safety, effectiveness and impact of the agents on the target pest species. The Palisade Insectary conducts research into the lifecycles and interactions of agents and their hosts.
Laboratory rearing of certain agents is critical to build populations, or to maintain populations that may not overwinter in Colorado's climate.
</dd>
<dt>Surveys and Releases</dt>
<dd>
Consistent surveying of vegetation and biocontrol agents across Colorado allows the Palisade Insectary to identify emerging pest problems, find and utilize field nursery sites to redistribute agents, and establish agents in areas where they are most needed.
</dd>
<dt>Field Monitoring</dt>
<dd>
Multiple monitoring methods are used by the Insectary to look at the effects of different biocontrols. The most common methods are:
<ul><li>SIMP (Standardized Impact Monitoring Protocol)
<ul><li>Developed by researchers in Idaho and adopted nationally, the SIMP protocol is used to document target weed density, vegetation cover, and biological control agent abundance along a 20-meter transect. Data can be documented on a SIMP form (<a href="https://invasivespecies.idaho.gov/bio-control-monitoring">Idaho Invasive Species</a>) or using the <a href="https://www.ibiocontrol.org/simp.cfm">iBiocontrol App</a> on a mobile device. </li>
</ul></li>
<li>Macro Plot Monitoring
<ul><li>This monitoring consists of a 16-meter square plot along with six 50-meter transects going out from the agent release point to document changes in the abundance of the targeted plant species, changes in the abundance of the insect biocontrol agent, expansion of impact area away from the point of introduction, and changes in the overall vegetation community. </li>
</ul></li>
</ul></dd>
<dt>Field Experiments</dt>
<dd>
Conducting field experiments allows the Palisade Insectary to look at biological control in the context of Colorado's environment. Experiments in field conditions can answer questions that more broadly address biocontrol effects on plant species composition and integration with other control methods.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Data Analysis and Mapping</dt>
<dd>
Survey, monitoring, release, and experimental data are utilized by the Palisade Insectary to make better land management decisions for the control of invasive pest species. Data collected is verified, analyzed and then shared to improve biocontrol usage and effectiveness.
Mapping of Colorado's weed and insect pests can help manage the spread of pests and create more effective control strategies.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Research Collaboration</dt>
<dd>
The Palisade Insectary participates in regional and national biocontrol programs, and has established partnerships with many individuals and organizations to facilitate biocontrol projects in Colorado. We have a long history of collaboration on projects with the USDA, CSU, CMU, USU, US Forest Service, BLM, EPA, SERDP, international organizations and many other biocontrol researchers in the US.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Outreach</dt>
<dd>
One of our main goals is to inform resource managers, landowners, and the general public of the availability of agents and help them understand the opportunities to utilize biological control to improve their pest control efforts and achieve management objectives. We do this through our website, press releases, social media posts, presentations, and group tours of the Insectary.
</dd>
</dl><dl class="ckeditor-accordion"><dt>International Code of Best Practices for Classical Biological Control of Weeds</dt>
<dd>
The Code was approved in 1999 by the delegates to the 10th International Symposium on Biological Control of Weeds and provides a standard guideline for biological control:
<ol><li>Ensure target weed’s potential impact justifies release of non-endemic agents</li>
<li>Obtain multi-agency approval for target </li>
<li>Select agents with the potential to control the target weed</li>
<li>Release safe and approved agents</li>
<li>Ensure only the intended agent is released</li>
<li>Use appropriate protocols for release and documentation</li>
<li>Monitor impact on the target plant species</li>
<li>Stop releases of ineffective agents, or when control is achieved</li>
<li>Monitor impacts on potential non target species</li>
<li>Encourage assessment of changes in plant and animal communities</li>
<li>Monitor interactions among agents</li>
<li>Communicate the results to the public
</li>
</ol></dd>
</dl>Project Spotlight
<dl class="ckeditor-accordion"><dt>SERDP Funded Phenology Modeling of Tamarix and Biological Controls</dt>
<dd>
In cooperation with the Department of Defense Strategic Environmental Research and Development Program (SRDP), researchers at the CDA Palisade Insectary and Oregon State University have developed a phenology model of the Northern Tamarisk Beetle, <em>Diorhabda carinulata</em>. This model predicts when different life stages of the beetle occur in the field based on temperature and day length. This is particularly important to predict when these beneficial biological control agents may be collected and redistributed. The model is applicable to all of North America and may also be applied to other <em>Diorhabda</em> species with success. This lifecycle model can be located at <a href="http://uspest.org/">uspest.org</a>, which also has models for many other insects both pest species and beneficials.
</dd>
</dl>
', 'en') (Line: 118)
Drupal\filter\Element\ProcessedText::preRenderText(Array)
call_user_func_array(Array, Array) (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 374)
Drupal\Core\Render\Renderer->doRender(Array, 1) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, 1) (Line: 160)
Drupal\Core\Render\Renderer->Drupal\Core\Render\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 161)
Drupal\Core\Render\Renderer->renderPlain(Array) (Line: 62)
Drupal\text\TextProcessed->getValue() (Line: 140)
Drupal\Core\Field\FieldItemBase->__get('processed') (Line: 139)
node_tokens('node', Array, Array, Array, Object)
call_user_func_array(Object, Array) (Line: 426)
Drupal\Core\Extension\ModuleHandler->Drupal\Core\Extension\{closure}(Object, 'node') (Line: 405)
Drupal\Core\Extension\ModuleHandler->invokeAllWith('tokens', Object) (Line: 433)
Drupal\Core\Extension\ModuleHandler->invokeAll('tokens', Array) (Line: 357)
Drupal\Core\Utility\Token->generate('node', Array, Array, Array, Object) (Line: 239)
Drupal\Core\Utility\Token->doReplace(1, '[node:summary]', Array, Array, Object) (Line: 189)
Drupal\Core\Utility\Token->replace('[node:summary]', Array, Array, NULL) (Line: 66)
Drupal\metatag\MetatagToken->replace('[node:summary]', Array, Array) (Line: 586)
Drupal\metatag\MetatagManager->generateRawElements(Array, Object) (Line: 493)
Drupal\metatag\MetatagManager->generateElements(Array, Object) (Line: 529)
metatag_get_tags_from_route() (Line: 298)
_metatag_remove_duplicate_entity_tags(Array) (Line: 244)
metatag_entity_view_alter(Array, Object, Object) (Line: 562)
Drupal\Core\Extension\ModuleHandler->alter('node_view', Array, Object, Object) (Line: 305)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 239)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func_array(Array, Array) (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 374)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 242)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 243)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 132)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 174)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
- Warning: Array to string conversion in Drupal\Core\Template\AttributeArray->__toString() (line 77 of core/lib/Drupal/Core/Template/AttributeArray.php).
Drupal\Core\Template\AttributeArray->__toString() (Line: 53)
Drupal\Core\Template\AttributeValueBase->render() (Line: 324)
Drupal\Core\Template\Attribute->__toString() (Line: 40)
__TwigTemplate_1c7d6fa4f60971d5f6825029b91a632c4a9856410e8f9dda904f1f54a370dd4e->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('modules/contrib/entity_embed/templates/entity-embed-container.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('entity_embed_container', Array) (Line: 489)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 212)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->Drupal\entity_embed\Plugin\Filter\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 213)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->process('<strong>The Palisade Insectary applies many scientific protocols and methods to study biocontrol agents. Investigations are made into the safety, impact, effectiveness, establishment, and spread of agents and pest hosts. </strong>
<strong>Here are some of the research methods utilized.</strong>
<dl class="ckeditor-accordion"><dt>Laboratory Research and Rearing</dt>
<dd>
Before most agents are released into the wider ecosystem, extensive laboratory research is conducted to ensure the safety, effectiveness and impact of the agents on the target pest species. The Palisade Insectary conducts research into the lifecycles and interactions of agents and their hosts.
Laboratory rearing of certain agents is critical to build populations, or to maintain populations that may not overwinter in Colorado's climate.
</dd>
<dt>Surveys and Releases</dt>
<dd>
Consistent surveying of vegetation and biocontrol agents across Colorado allows the Palisade Insectary to identify emerging pest problems, find and utilize field nursery sites to redistribute agents, and establish agents in areas where they are most needed.
</dd>
<dt>Field Monitoring</dt>
<dd>
Multiple monitoring methods are used by the Insectary to look at the effects of different biocontrols. The most common methods are:
<ul><li>SIMP (Standardized Impact Monitoring Protocol)
<ul><li>Developed by researchers in Idaho and adopted nationally, the SIMP protocol is used to document target weed density, vegetation cover, and biological control agent abundance along a 20-meter transect. Data can be documented on a SIMP form (<a href="https://invasivespecies.idaho.gov/bio-control-monitoring">Idaho Invasive Species</a>) or using the <a href="https://www.ibiocontrol.org/simp.cfm">iBiocontrol App</a> on a mobile device. </li>
</ul></li>
<li>Macro Plot Monitoring
<ul><li>This monitoring consists of a 16-meter square plot along with six 50-meter transects going out from the agent release point to document changes in the abundance of the targeted plant species, changes in the abundance of the insect biocontrol agent, expansion of impact area away from the point of introduction, and changes in the overall vegetation community. </li>
</ul></li>
</ul></dd>
<dt>Field Experiments</dt>
<dd>
Conducting field experiments allows the Palisade Insectary to look at biological control in the context of Colorado's environment. Experiments in field conditions can answer questions that more broadly address biocontrol effects on plant species composition and integration with other control methods.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Data Analysis and Mapping</dt>
<dd>
Survey, monitoring, release, and experimental data are utilized by the Palisade Insectary to make better land management decisions for the control of invasive pest species. Data collected is verified, analyzed and then shared to improve biocontrol usage and effectiveness.
Mapping of Colorado's weed and insect pests can help manage the spread of pests and create more effective control strategies.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Research Collaboration</dt>
<dd>
The Palisade Insectary participates in regional and national biocontrol programs, and has established partnerships with many individuals and organizations to facilitate biocontrol projects in Colorado. We have a long history of collaboration on projects with the USDA, CSU, CMU, USU, US Forest Service, BLM, EPA, SERDP, international organizations and many other biocontrol researchers in the US.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Outreach</dt>
<dd>
One of our main goals is to inform resource managers, landowners, and the general public of the availability of agents and help them understand the opportunities to utilize biological control to improve their pest control efforts and achieve management objectives. We do this through our website, press releases, social media posts, presentations, and group tours of the Insectary.
</dd>
</dl><dl class="ckeditor-accordion"><dt>International Code of Best Practices for Classical Biological Control of Weeds</dt>
<dd>
The Code was approved in 1999 by the delegates to the 10th International Symposium on Biological Control of Weeds and provides a standard guideline for biological control:
<ol><li>Ensure target weed’s potential impact justifies release of non-endemic agents</li>
<li>Obtain multi-agency approval for target </li>
<li>Select agents with the potential to control the target weed</li>
<li>Release safe and approved agents</li>
<li>Ensure only the intended agent is released</li>
<li>Use appropriate protocols for release and documentation</li>
<li>Monitor impact on the target plant species</li>
<li>Stop releases of ineffective agents, or when control is achieved</li>
<li>Monitor impacts on potential non target species</li>
<li>Encourage assessment of changes in plant and animal communities</li>
<li>Monitor interactions among agents</li>
<li>Communicate the results to the public
</li>
</ol></dd>
</dl>Project Spotlight
<dl class="ckeditor-accordion"><dt>SERDP Funded Phenology Modeling of Tamarix and Biological Controls</dt>
<dd>
In cooperation with the Department of Defense Strategic Environmental Research and Development Program (SRDP), researchers at the CDA Palisade Insectary and Oregon State University have developed a phenology model of the Northern Tamarisk Beetle, <em>Diorhabda carinulata</em>. This model predicts when different life stages of the beetle occur in the field based on temperature and day length. This is particularly important to predict when these beneficial biological control agents may be collected and redistributed. The model is applicable to all of North America and may also be applied to other <em>Diorhabda</em> species with success. This lifecycle model can be located at <a href="http://uspest.org/">uspest.org</a>, which also has models for many other insects both pest species and beneficials.
</dd>
</dl>
', 'en') (Line: 118)
Drupal\filter\Element\ProcessedText::preRenderText(Array)
call_user_func_array(Array, Array) (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 374)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 479)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 87)
__TwigTemplate_75efb36593d5efb676caca37b7fa6f2877330aa4afb8eba160d42b9b0eb91e9c->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('themes/contrib/bootstrap/templates/field/field.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('field', Array) (Line: 433)
Drupal\Core\Render\Renderer->doRender(Array) (Line: 446)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 479)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 111)
__TwigTemplate_36b63c29c212f80258d420ba0945692c14ed672f6ff5989e4f40d21a8886d816->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('themes/custom/ci_xy/templates/system/node.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('node', Array) (Line: 433)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 242)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 243)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 132)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 174)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
- Warning: Array to string conversion in Drupal\Core\Template\AttributeArray->__toString() (line 78 of core/lib/Drupal/Core/Template/AttributeArray.php).
Drupal\Core\Template\AttributeArray->__toString() (Line: 53)
Drupal\Core\Template\AttributeValueBase->render() (Line: 324)
Drupal\Core\Template\Attribute->__toString() (Line: 40)
__TwigTemplate_1c7d6fa4f60971d5f6825029b91a632c4a9856410e8f9dda904f1f54a370dd4e->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('modules/contrib/entity_embed/templates/entity-embed-container.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('entity_embed_container', Array) (Line: 489)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 212)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->Drupal\entity_embed\Plugin\Filter\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 213)
Drupal\entity_embed\Plugin\Filter\EntityEmbedFilter->process('<strong>The Palisade Insectary applies many scientific protocols and methods to study biocontrol agents. Investigations are made into the safety, impact, effectiveness, establishment, and spread of agents and pest hosts. </strong>
<strong>Here are some of the research methods utilized.</strong>
<dl class="ckeditor-accordion"><dt>Laboratory Research and Rearing</dt>
<dd>
Before most agents are released into the wider ecosystem, extensive laboratory research is conducted to ensure the safety, effectiveness and impact of the agents on the target pest species. The Palisade Insectary conducts research into the lifecycles and interactions of agents and their hosts.
Laboratory rearing of certain agents is critical to build populations, or to maintain populations that may not overwinter in Colorado's climate.
</dd>
<dt>Surveys and Releases</dt>
<dd>
Consistent surveying of vegetation and biocontrol agents across Colorado allows the Palisade Insectary to identify emerging pest problems, find and utilize field nursery sites to redistribute agents, and establish agents in areas where they are most needed.
</dd>
<dt>Field Monitoring</dt>
<dd>
Multiple monitoring methods are used by the Insectary to look at the effects of different biocontrols. The most common methods are:
<ul><li>SIMP (Standardized Impact Monitoring Protocol)
<ul><li>Developed by researchers in Idaho and adopted nationally, the SIMP protocol is used to document target weed density, vegetation cover, and biological control agent abundance along a 20-meter transect. Data can be documented on a SIMP form (<a href="https://invasivespecies.idaho.gov/bio-control-monitoring">Idaho Invasive Species</a>) or using the <a href="https://www.ibiocontrol.org/simp.cfm">iBiocontrol App</a> on a mobile device. </li>
</ul></li>
<li>Macro Plot Monitoring
<ul><li>This monitoring consists of a 16-meter square plot along with six 50-meter transects going out from the agent release point to document changes in the abundance of the targeted plant species, changes in the abundance of the insect biocontrol agent, expansion of impact area away from the point of introduction, and changes in the overall vegetation community. </li>
</ul></li>
</ul></dd>
<dt>Field Experiments</dt>
<dd>
Conducting field experiments allows the Palisade Insectary to look at biological control in the context of Colorado's environment. Experiments in field conditions can answer questions that more broadly address biocontrol effects on plant species composition and integration with other control methods.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Data Analysis and Mapping</dt>
<dd>
Survey, monitoring, release, and experimental data are utilized by the Palisade Insectary to make better land management decisions for the control of invasive pest species. Data collected is verified, analyzed and then shared to improve biocontrol usage and effectiveness.
Mapping of Colorado's weed and insect pests can help manage the spread of pests and create more effective control strategies.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Research Collaboration</dt>
<dd>
The Palisade Insectary participates in regional and national biocontrol programs, and has established partnerships with many individuals and organizations to facilitate biocontrol projects in Colorado. We have a long history of collaboration on projects with the USDA, CSU, CMU, USU, US Forest Service, BLM, EPA, SERDP, international organizations and many other biocontrol researchers in the US.
</dd>
</dl><dl class="ckeditor-accordion"><dt>Outreach</dt>
<dd>
One of our main goals is to inform resource managers, landowners, and the general public of the availability of agents and help them understand the opportunities to utilize biological control to improve their pest control efforts and achieve management objectives. We do this through our website, press releases, social media posts, presentations, and group tours of the Insectary.
</dd>
</dl><dl class="ckeditor-accordion"><dt>International Code of Best Practices for Classical Biological Control of Weeds</dt>
<dd>
The Code was approved in 1999 by the delegates to the 10th International Symposium on Biological Control of Weeds and provides a standard guideline for biological control:
<ol><li>Ensure target weed’s potential impact justifies release of non-endemic agents</li>
<li>Obtain multi-agency approval for target </li>
<li>Select agents with the potential to control the target weed</li>
<li>Release safe and approved agents</li>
<li>Ensure only the intended agent is released</li>
<li>Use appropriate protocols for release and documentation</li>
<li>Monitor impact on the target plant species</li>
<li>Stop releases of ineffective agents, or when control is achieved</li>
<li>Monitor impacts on potential non target species</li>
<li>Encourage assessment of changes in plant and animal communities</li>
<li>Monitor interactions among agents</li>
<li>Communicate the results to the public
</li>
</ol></dd>
</dl>Project Spotlight
<dl class="ckeditor-accordion"><dt>SERDP Funded Phenology Modeling of Tamarix and Biological Controls</dt>
<dd>
In cooperation with the Department of Defense Strategic Environmental Research and Development Program (SRDP), researchers at the CDA Palisade Insectary and Oregon State University have developed a phenology model of the Northern Tamarisk Beetle, <em>Diorhabda carinulata</em>. This model predicts when different life stages of the beetle occur in the field based on temperature and day length. This is particularly important to predict when these beneficial biological control agents may be collected and redistributed. The model is applicable to all of North America and may also be applied to other <em>Diorhabda</em> species with success. This lifecycle model can be located at <a href="http://uspest.org/">uspest.org</a>, which also has models for many other insects both pest species and beneficials.
</dd>
</dl>
', 'en') (Line: 118)
Drupal\filter\Element\ProcessedText::preRenderText(Array)
call_user_func_array(Array, Array) (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback(Array, Array, 'Render #pre_render callbacks must be methods of a class that implements \Drupal\Core\Security\TrustedCallbackInterface or be an anonymous function. The callback was %s. See https://www.drupal.org/node/2966725', 'exception', 'Drupal\Core\Render\Element\RenderCallbackInterface') (Line: 788)
Drupal\Core\Render\Renderer->doCallback('#pre_render', Array, Array) (Line: 374)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 479)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 87)
__TwigTemplate_75efb36593d5efb676caca37b7fa6f2877330aa4afb8eba160d42b9b0eb91e9c->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('themes/contrib/bootstrap/templates/field/field.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('field', Array) (Line: 433)
Drupal\Core\Render\Renderer->doRender(Array) (Line: 446)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array) (Line: 479)
Drupal\Core\Template\TwigExtension->escapeFilter(Object, Array, 'html', NULL, 1) (Line: 111)
__TwigTemplate_36b63c29c212f80258d420ba0945692c14ed672f6ff5989e4f40d21a8886d816->doDisplay(Array, Array) (Line: 405)
Twig\Template->displayWithErrorHandling(Array, Array) (Line: 378)
Twig\Template->display(Array) (Line: 390)
Twig\Template->render(Array) (Line: 55)
twig_render_template('themes/custom/ci_xy/templates/system/node.html.twig', Array) (Line: 384)
Drupal\Core\Theme\ThemeManager->render('node', Array) (Line: 433)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 204)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 242)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 243)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 132)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object)
call_user_func(Array, Object, 'kernel.view', Object) (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object, 'kernel.view') (Line: 174)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 191)
Drupal\page_cache\StackMiddleware\PageCache->fetch(Object, 1, 1) (Line: 128)
Drupal\page_cache\StackMiddleware\PageCache->lookup(Object, 1, 1) (Line: 82)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 718)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
