<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[FindingFive Discussion Forum - New Study Grammar Features]]></title>
		<link>http://discuss.findingfive.com/</link>
		<description><![CDATA[FindingFive Discussion Forum - http://discuss.findingfive.com]]></description>
		<pubDate>Wed, 15 Apr 2026 02:21:43 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[2023 Fall Study Grammar Update]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=257</link>
			<pubDate>Sat, 12 Aug 2023 14:28:08 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=257</guid>
			<description><![CDATA[<span style="font-family: Verdana, sans-serif;" class="mycode_font">Dear Researchers,</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">The 2023 Fall Study Grammar Update is almost here! This update contains quite a few new features and improvements that we are really excited about!</span><br />
<br />
<br />
<span style="color: #e86e04;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Please note:</span></span></span><br />
<ol type="1" class="mycode_list"><li><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-family: Verdana, sans-serif;" class="mycode_font">Do you use the </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Keypress Response</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> type? If so, </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">please pay special attention to item #1</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">, as it may affect any scripts you have for processing reaction time data.</span></span><br />
</li>
<li><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-family: Verdana, sans-serif;" class="mycode_font">As always, you MUST </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">preview your study in full</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> to update to the </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">latest grammar version</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> in order to use these features.</span></span><br />
</li>
</ol>
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">FindingFive servers (US and EU, in their respective local times) will be updated on the early morning of </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">August 14, 2023</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> to include the following changes:</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">1. Reaction time data for Keypress Responses now calculated from </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">previous keypress</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">!</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">Previously, reaction time data for all keypresses recorded in a Keypress Response were calculated from the onset of the response (when the response is rendered on the trial). Based on feedback, we have decided to instead </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">calculate the reaction time of each successive keypress relative to the preceding keypress</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">, with the first keypress reaction time calculated from response onset.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">In other words, if a participant were to strike a key every 500ms, the </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">old </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">reaction time data would look like this: 500, 1000, 1500, etc. It will </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">now </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">look like this: 500, 500, 500, etc.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">2. Choice Responses now support </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">dropdown</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b"> selection!</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">It is now possible to organize the options of a choice response in a dropdown menu by setting the </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/responses/choice#mode" target="_blank" rel="noopener" class="mycode_url">“mode”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property to </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">“dropdown”</span><span style="font-family: Verdana, sans-serif;" class="mycode_font">. Dropdown mode supports feedback and resetting of the choice response, but does not presently support the </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/responses/choice#multi_select" target="_blank" rel="noopener" class="mycode_url">“multi_select”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> parameter (this will be made available in a future release).</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">A big thank you to Dr. Ming Xiang of University of Chicago for requesting this feature!</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">3. Tokenized Text Stimuli now support </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">bidirectional</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b"> self-paced reading!</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">It is now possible for participants to move </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">both forward and backward</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> through tokenized text stimuli. Simply set the new </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text" target="_blank" rel="noopener" class="mycode_url">“bidirectional”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property to </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">true</span><span style="font-family: Verdana, sans-serif;" class="mycode_font">. This feature is particularly useful for backward-masked and singleton self-paced reading setups.</span><br />
<br />
<span style="color: #e86e04;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Please note: </span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">This feature is only possible if </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#self_paced" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font">“self_paced”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> is set to </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">true</span><span style="font-family: Verdana, sans-serif;" class="mycode_font">. In addition, please see the new </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#key_reverse" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font">“key_reverse”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property which supplements the </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#key_advance" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font">“key_advance”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property to support custom key bindings.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">A big thank you to Dr. Jeffery Green of BYU Dept. of Linguistics for requesting this feature!</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">4. Changes to Tokenized Text Stimulus instructions</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">With the addition of bidirectional tokenized text stimuli, we are deprecating the old </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#key_advance_instruction" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font">“key_advance_instruction”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property in favor of a new </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#hint" target="_blank" rel="noopener" class="mycode_url">“hint”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property. This aligns key advance instructions across tokenized text and audio stimuli.</span><br />
<br />
<br />
<span style="color: #e86e04;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Please note: </span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">Studies employing the old property should continue to work for now, but we do not actively support deprecated features.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">5. A bug fix affecting the recording of Response Mode in the results CSV</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">A bug affecting how </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">“response_mode”</span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> was recorded in the </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">results.csv</span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> file of a completed session or study preview from grammar version 3.5.0 has been fixed. The response mode is now correctly recorded.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Questions?</span></span><br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">If you have any questions regarding this grammar update, please leave your comments below. Thanks!</span>]]></description>
			<content:encoded><![CDATA[<span style="font-family: Verdana, sans-serif;" class="mycode_font">Dear Researchers,</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">The 2023 Fall Study Grammar Update is almost here! This update contains quite a few new features and improvements that we are really excited about!</span><br />
<br />
<br />
<span style="color: #e86e04;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Please note:</span></span></span><br />
<ol type="1" class="mycode_list"><li><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-family: Verdana, sans-serif;" class="mycode_font">Do you use the </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Keypress Response</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> type? If so, </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">please pay special attention to item #1</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">, as it may affect any scripts you have for processing reaction time data.</span></span><br />
</li>
<li><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-family: Verdana, sans-serif;" class="mycode_font">As always, you MUST </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">preview your study in full</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> to update to the </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">latest grammar version</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> in order to use these features.</span></span><br />
</li>
</ol>
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">FindingFive servers (US and EU, in their respective local times) will be updated on the early morning of </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">August 14, 2023</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> to include the following changes:</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">1. Reaction time data for Keypress Responses now calculated from </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">previous keypress</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">!</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">Previously, reaction time data for all keypresses recorded in a Keypress Response were calculated from the onset of the response (when the response is rendered on the trial). Based on feedback, we have decided to instead </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">calculate the reaction time of each successive keypress relative to the preceding keypress</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">, with the first keypress reaction time calculated from response onset.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">In other words, if a participant were to strike a key every 500ms, the </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">old </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">reaction time data would look like this: 500, 1000, 1500, etc. It will </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">now </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">look like this: 500, 500, 500, etc.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">2. Choice Responses now support </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">dropdown</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b"> selection!</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">It is now possible to organize the options of a choice response in a dropdown menu by setting the </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/responses/choice#mode" target="_blank" rel="noopener" class="mycode_url">“mode”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property to </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">“dropdown”</span><span style="font-family: Verdana, sans-serif;" class="mycode_font">. Dropdown mode supports feedback and resetting of the choice response, but does not presently support the </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/responses/choice#multi_select" target="_blank" rel="noopener" class="mycode_url">“multi_select”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> parameter (this will be made available in a future release).</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">A big thank you to Dr. Ming Xiang of University of Chicago for requesting this feature!</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">3. Tokenized Text Stimuli now support </span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">bidirectional</span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b"> self-paced reading!</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">It is now possible for participants to move </span><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">both forward and backward</span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> through tokenized text stimuli. Simply set the new </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text" target="_blank" rel="noopener" class="mycode_url">“bidirectional”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property to </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">true</span><span style="font-family: Verdana, sans-serif;" class="mycode_font">. This feature is particularly useful for backward-masked and singleton self-paced reading setups.</span><br />
<br />
<span style="color: #e86e04;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Please note: </span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">This feature is only possible if </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#self_paced" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font">“self_paced”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> is set to </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">true</span><span style="font-family: Verdana, sans-serif;" class="mycode_font">. In addition, please see the new </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#key_reverse" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font">“key_reverse”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property which supplements the </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#key_advance" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font">“key_advance”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property to support custom key bindings.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">A big thank you to Dr. Jeffery Green of BYU Dept. of Linguistics for requesting this feature!</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">4. Changes to Tokenized Text Stimulus instructions</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">With the addition of bidirectional tokenized text stimuli, we are deprecating the old </span><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#key_advance_instruction" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-family: 'Courier New', monospace;" class="mycode_font">“key_advance_instruction”</span></span></a><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property in favor of a new </span><span style="color: #1155cc;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/stimuli/tokenized_text#hint" target="_blank" rel="noopener" class="mycode_url">“hint”</a></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> property. This aligns key advance instructions across tokenized text and audio stimuli.</span><br />
<br />
<br />
<span style="color: #e86e04;" class="mycode_color"><span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Please note: </span></span></span><span style="font-family: Verdana, sans-serif;" class="mycode_font">Studies employing the old property should continue to work for now, but we do not actively support deprecated features.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">5. A bug fix affecting the recording of Response Mode in the results CSV</span></span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">A bug affecting how </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">“response_mode”</span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> was recorded in the </span><span style="font-family: 'Courier New', monospace;" class="mycode_font">results.csv</span><span style="font-family: Verdana, sans-serif;" class="mycode_font"> file of a completed session or study preview from grammar version 3.5.0 has been fixed. The response mode is now correctly recorded.</span><br />
<br />
<br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Questions?</span></span><br />
<span style="font-family: Verdana, sans-serif;" class="mycode_font">If you have any questions regarding this grammar update, please leave your comments below. Thanks!</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[2022 Fall Study Grammar Update!]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=241</link>
			<pubDate>Wed, 09 Nov 2022 14:02:37 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=241</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
The 2022 Fall Study Grammar Update is almost here! This update contains quite a few new features and improvements that we are really excited about! FindingFive servers (US and EU, in their respective local times) will be updated on the early morning of <span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u">Friday, November 11, 2022</span></span> to include the following changes:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1. Major Upgrade - Stimulus files are now bundled with launched sessions!</span><br />
<br />
We have implemented a groundbreaking solution that addresses multiple pain points in running experiments with stimulus files. Starting with this grammar update, stimulus files are now bundled with launched sessions, instead of being dynamically sourced from "Resource Files" storage. This has a number of advantages:<ul class="mycode_list"><li>You can edit, replace, or even remove stimulus files in your account (under "Resource Files") after a session is launched. Such actions won't affect the active session because copies of the stimulus files have already been bundled together with the launched session.<br />
</li>
<li>The rendered experiment in a launched session will generally load faster as bundled stimulus files are saved into our distributed cloud infrastructure, as compared to a centralized database. <br />
</li>
<li>We will soon be able to introduce a "time capsule" function, where you can duplicate the exact settings of a previous session, even using stimulus files that have been bundled with that session.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b"><span style="color: #e86e04;" class="mycode_color">Please note:</span></span> you MUST launch your session <span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u">with the latest grammar version</span></span> to use this feature. If your session is launched with grammar version 3.3.0 or lower, stimulus files will NOT be bundled with sessions.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">2. Feature Enhancements and Bug Fixes to the Rating Response</span><br />
<br />
The rating response has gained the following new features:<ul class="mycode_list"><li>A new <a href="https://docs.findingfive.com/en/grammar/responses/rating#target" target="_blank" rel="noopener" class="mycode_url">"<span style="font-family: Courier New;" class="mycode_font">target"</span></a> property which allows accuracy determination on individual rating responses (when applicable) and/or in evaluating accuracy for conditionally branched procedures.<br />
</li>
<li>A new <span style="font-family: Courier New;" class="mycode_font">"<a href="https://docs.findingfive.com/en/grammar/responses/rating#target_sum" target="_blank" rel="noopener" class="mycode_url">target_sum</a>"</span> property which requires the sum of ratings in a multi-row rating response to add up to a certain number (our thanks to Souad Kheder of University of Florida for suggestion this feature)<br />
</li>
</ul>
The rating response also has a bugfix:<ul class="mycode_list"><li>When used with multiple rows, the rating response no longer momentarily flashes all rows in the beginning under the Safari browser. This issue did not affect Firefox or Chrome users.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">3. Forcing the Display Language of an Experiment</span><br />
<br />
It is now possible to force the Display Language of a FindingFive experiment - i.e., the language used in system-provided components, such as the greeting page, continue button, pop-up messages, and etc. This is done via setting the new "<span style="font-family: Courier New;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/procedures-blocking#language" target="_blank" rel="noopener" class="mycode_url">language</a></span>" property in the procedure of an experiment.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">4. Update to the Choice Response</span><br />
<br />
The choice response can now be configured to also report the location of choice response options via the new "<a href="https://docs.findingfive.com/en/grammar/responses/choice#record_location" target="_blank" rel="noopener" class="mycode_url"><span style="font-family: Courier New;" class="mycode_font">record_location</span></a>" property. This can be especially useful in cases where the locations of response options are randomly sampled. (Our thanks to Bissera Ivanova of UNIVERSITE D-AIX-MARSEILLE for suggesting this feature!)<br />
<br />
<span style="font-weight: bold;" class="mycode_b">5. Minor Updates to the Overall Theme of an Experiment</span><br />
<br />
We are in the process of gradually updating the overall style of a FindingFive experiment. In this update, you'll see:<ul class="mycode_list"><li>The cover page of an experiment has been updated to better confirm with the design language of the rest of FindingFive.<br />
</li>
<li>The base font of an experiment has been updated to use the same font as the rest of FindingFive.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">6. Prompts for Directing Participants to Subsequent Studies in a Prerequisite Chain</span><br />
<br />
FindingFive now displays a list of "Recommended Follow-up Studies" at the end of an experiment, if the experiment is a prerequisite (as configured in the Session Wizard) of another experiment. (Our thanks to Ariel Chan of UCLA for suggesting this feature!)<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Questions?</span><br />
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
The 2022 Fall Study Grammar Update is almost here! This update contains quite a few new features and improvements that we are really excited about! FindingFive servers (US and EU, in their respective local times) will be updated on the early morning of <span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u">Friday, November 11, 2022</span></span> to include the following changes:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1. Major Upgrade - Stimulus files are now bundled with launched sessions!</span><br />
<br />
We have implemented a groundbreaking solution that addresses multiple pain points in running experiments with stimulus files. Starting with this grammar update, stimulus files are now bundled with launched sessions, instead of being dynamically sourced from "Resource Files" storage. This has a number of advantages:<ul class="mycode_list"><li>You can edit, replace, or even remove stimulus files in your account (under "Resource Files") after a session is launched. Such actions won't affect the active session because copies of the stimulus files have already been bundled together with the launched session.<br />
</li>
<li>The rendered experiment in a launched session will generally load faster as bundled stimulus files are saved into our distributed cloud infrastructure, as compared to a centralized database. <br />
</li>
<li>We will soon be able to introduce a "time capsule" function, where you can duplicate the exact settings of a previous session, even using stimulus files that have been bundled with that session.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b"><span style="color: #e86e04;" class="mycode_color">Please note:</span></span> you MUST launch your session <span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u">with the latest grammar version</span></span> to use this feature. If your session is launched with grammar version 3.3.0 or lower, stimulus files will NOT be bundled with sessions.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">2. Feature Enhancements and Bug Fixes to the Rating Response</span><br />
<br />
The rating response has gained the following new features:<ul class="mycode_list"><li>A new <a href="https://docs.findingfive.com/en/grammar/responses/rating#target" target="_blank" rel="noopener" class="mycode_url">"<span style="font-family: Courier New;" class="mycode_font">target"</span></a> property which allows accuracy determination on individual rating responses (when applicable) and/or in evaluating accuracy for conditionally branched procedures.<br />
</li>
<li>A new <span style="font-family: Courier New;" class="mycode_font">"<a href="https://docs.findingfive.com/en/grammar/responses/rating#target_sum" target="_blank" rel="noopener" class="mycode_url">target_sum</a>"</span> property which requires the sum of ratings in a multi-row rating response to add up to a certain number (our thanks to Souad Kheder of University of Florida for suggestion this feature)<br />
</li>
</ul>
The rating response also has a bugfix:<ul class="mycode_list"><li>When used with multiple rows, the rating response no longer momentarily flashes all rows in the beginning under the Safari browser. This issue did not affect Firefox or Chrome users.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">3. Forcing the Display Language of an Experiment</span><br />
<br />
It is now possible to force the Display Language of a FindingFive experiment - i.e., the language used in system-provided components, such as the greeting page, continue button, pop-up messages, and etc. This is done via setting the new "<span style="font-family: Courier New;" class="mycode_font"><a href="https://docs.findingfive.com/en/grammar/procedures-blocking#language" target="_blank" rel="noopener" class="mycode_url">language</a></span>" property in the procedure of an experiment.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">4. Update to the Choice Response</span><br />
<br />
The choice response can now be configured to also report the location of choice response options via the new "<a href="https://docs.findingfive.com/en/grammar/responses/choice#record_location" target="_blank" rel="noopener" class="mycode_url"><span style="font-family: Courier New;" class="mycode_font">record_location</span></a>" property. This can be especially useful in cases where the locations of response options are randomly sampled. (Our thanks to Bissera Ivanova of UNIVERSITE D-AIX-MARSEILLE for suggesting this feature!)<br />
<br />
<span style="font-weight: bold;" class="mycode_b">5. Minor Updates to the Overall Theme of an Experiment</span><br />
<br />
We are in the process of gradually updating the overall style of a FindingFive experiment. In this update, you'll see:<ul class="mycode_list"><li>The cover page of an experiment has been updated to better confirm with the design language of the rest of FindingFive.<br />
</li>
<li>The base font of an experiment has been updated to use the same font as the rest of FindingFive.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">6. Prompts for Directing Participants to Subsequent Studies in a Prerequisite Chain</span><br />
<br />
FindingFive now displays a list of "Recommended Follow-up Studies" at the end of an experiment, if the experiment is a prerequisite (as configured in the Session Wizard) of another experiment. (Our thanks to Ariel Chan of UCLA for suggesting this feature!)<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Questions?</span><br />
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[2022 Summer Study Grammar Update!]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=234</link>
			<pubDate>Fri, 12 Aug 2022 15:03:58 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=234</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the 2022 Summer Study Grammar Update! FindingFive servers (US and EU) will be updated on the early morning of Monday August 15, 2022 to include the following changes:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">A Completely Redesigned Multi-row Rating Response</span><br />
<br />
The newly designed <a href="https://docs.findingfive.com/en/grammar/responses/rating" target="_blank" rel="noopener" class="mycode_url">rating response</a> now supports presenting multiple questions (i.e., rows of ratings) in a single response. This can be quite handy if you are interested in asking participants to rate on multiple properties of a stimulus (e.g., the shape, size, and color of an object). Previously, you'd need to create three rating responses and stack them awkwardly on the same trial - well, that kind of hassle is no longer necessary!<br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="http://discuss.findingfive.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=40" target="_blank" title="">Screen Shot 2022-08-12 at 11.19.15 AM.png</a> (Size: 49.72 KB / Downloads: 14)
<!-- end: postbit_attachments_attachment --><br />
<br />
Additionally, you'll find the redesigned rating response to be aesthetically more pleasing and congruent with the overall theme of FindingFive.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Audio Recording Tricks</span><br />
The <a href="https://docs.findingfive.com/en/grammar/responses/audio" target="_blank" rel="noopener" class="mycode_url">audio response</a> and the <a href="https://docs.findingfive.com/en/grammar/responses/background-audio" target="_blank" rel="noopener" class="mycode_url">background audio response</a> can now do the following <a href="https://docs.findingfive.com/en/grammar/responses/audio#stop_on_silence" target="_blank" rel="noopener" class="mycode_url">two nifty tricks</a>:<ul class="mycode_list"><li>Automatically trimming the leading silence of a recording<br />
</li>
<li>Automatically stopping a recording when participants stop speaking (heuristically determined)<br />
</li>
</ul>
Using these two features will implicitly turn on the onset detection feature, and you can adjust the <a href="https://docs.findingfive.com/en/grammar/responses/audio#onset_sensitivity" target="_blank" rel="noopener" class="mycode_url">onset sensitivity</a> value to experiment with these two new features beyond the default settings.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Questions?</span><br />
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the 2022 Summer Study Grammar Update! FindingFive servers (US and EU) will be updated on the early morning of Monday August 15, 2022 to include the following changes:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">A Completely Redesigned Multi-row Rating Response</span><br />
<br />
The newly designed <a href="https://docs.findingfive.com/en/grammar/responses/rating" target="_blank" rel="noopener" class="mycode_url">rating response</a> now supports presenting multiple questions (i.e., rows of ratings) in a single response. This can be quite handy if you are interested in asking participants to rate on multiple properties of a stimulus (e.g., the shape, size, and color of an object). Previously, you'd need to create three rating responses and stack them awkwardly on the same trial - well, that kind of hassle is no longer necessary!<br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="http://discuss.findingfive.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=40" target="_blank" title="">Screen Shot 2022-08-12 at 11.19.15 AM.png</a> (Size: 49.72 KB / Downloads: 14)
<!-- end: postbit_attachments_attachment --><br />
<br />
Additionally, you'll find the redesigned rating response to be aesthetically more pleasing and congruent with the overall theme of FindingFive.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Audio Recording Tricks</span><br />
The <a href="https://docs.findingfive.com/en/grammar/responses/audio" target="_blank" rel="noopener" class="mycode_url">audio response</a> and the <a href="https://docs.findingfive.com/en/grammar/responses/background-audio" target="_blank" rel="noopener" class="mycode_url">background audio response</a> can now do the following <a href="https://docs.findingfive.com/en/grammar/responses/audio#stop_on_silence" target="_blank" rel="noopener" class="mycode_url">two nifty tricks</a>:<ul class="mycode_list"><li>Automatically trimming the leading silence of a recording<br />
</li>
<li>Automatically stopping a recording when participants stop speaking (heuristically determined)<br />
</li>
</ul>
Using these two features will implicitly turn on the onset detection feature, and you can adjust the <a href="https://docs.findingfive.com/en/grammar/responses/audio#onset_sensitivity" target="_blank" rel="noopener" class="mycode_url">onset sensitivity</a> value to experiment with these two new features beyond the default settings.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Questions?</span><br />
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[February Study Grammar Update - 2/14/2022]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=194</link>
			<pubDate>Fri, 11 Feb 2022 22:48:53 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=194</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the February Study Grammar Update! FindingFive servers (US and EU) will be updated on the early morning of Monday 2/14/2022 to include the following changes:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features:</span><ul class="mycode_list"><li>Carryover response - it is now possible to <span style="font-weight: bold;" class="mycode_b">use participant responses collected on previous trials as stimuli </span>in later blocks of an experiment. This feature can be especially useful for paradigms where the participant is asked to review or judge their own responses in perception or decision-making tasks.<br />
<br />
Please refer to <a href="https://news.findingfive.com/2022/02/11/tutorial-using-carryover-responses-as-stimuli/" target="_blank" rel="noopener" class="mycode_url">our new tutorial</a> for how to use this feature.<br />
<br />
</li>
<li>Extended speech recognition support - studies that use the speech recognition feature in audio responses are now open to more browsers, including Firefox and Safari on desktop or laptop computers. Previously Chrome was the only browser that participants can use for these studies.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Bug Fixes:</span><ul class="mycode_list"><li>Fixed an issue where trials with stimuli using the barrier feature and an audio response would experience unexpected jumpiness during the trial.<br />
</li>
<li>Fixed an issue where participants couldn't start a study using Firefox on an iPhone or iPad.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Improvements:</span><ul class="mycode_list"><li>Better styling for requirement messages that participants see at the beginning of an experiment.<br />
</li>
</ul>
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the February Study Grammar Update! FindingFive servers (US and EU) will be updated on the early morning of Monday 2/14/2022 to include the following changes:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features:</span><ul class="mycode_list"><li>Carryover response - it is now possible to <span style="font-weight: bold;" class="mycode_b">use participant responses collected on previous trials as stimuli </span>in later blocks of an experiment. This feature can be especially useful for paradigms where the participant is asked to review or judge their own responses in perception or decision-making tasks.<br />
<br />
Please refer to <a href="https://news.findingfive.com/2022/02/11/tutorial-using-carryover-responses-as-stimuli/" target="_blank" rel="noopener" class="mycode_url">our new tutorial</a> for how to use this feature.<br />
<br />
</li>
<li>Extended speech recognition support - studies that use the speech recognition feature in audio responses are now open to more browsers, including Firefox and Safari on desktop or laptop computers. Previously Chrome was the only browser that participants can use for these studies.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Bug Fixes:</span><ul class="mycode_list"><li>Fixed an issue where trials with stimuli using the barrier feature and an audio response would experience unexpected jumpiness during the trial.<br />
</li>
<li>Fixed an issue where participants couldn't start a study using Firefox on an iPhone or iPad.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Improvements:</span><ul class="mycode_list"><li>Better styling for requirement messages that participants see at the beginning of an experiment.<br />
</li>
</ul>
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[January Study Grammar Update - 1/18/2022]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=188</link>
			<pubDate>Mon, 17 Jan 2022 01:43:23 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=188</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the January Grammar Update! Due to the MLK holiday on Monday 1/17/2022, this update will be made first available on our testing server (<a href="https://testing.findingfive.com" target="_blank" rel="noopener" class="mycode_url">https://testing.findingfive.com</a> - US server accounts only) on Monday 1/17/2022, and then on the production servers (<a href="https://www.findingfive.com" target="_blank" rel="noopener" class="mycode_url">https://www.findingfive.com</a> or <a href="https://eu.findingfive.com" target="_blank" rel="noopener" class="mycode_url">https://eu.findingfive.com</a>) on Tuesday, 1/18/2022.<br />
<br />
This January update mostly consists of bug fixes and a minor feature tweak:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Bug Fixes:</span><br />
<ul class="mycode_list"><li>Fixed an issue where a text response with a "max_char" setting would require an extra click in the text box before participants could enter their response.<br />
</li>
<li>Fixed an issue where the duration timer of a choice response continued counting while the choice response displays visual feedback (if feedback is set). The duration timer now stops as soon as a choice is made by participants, before the feedback is shown.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Improvements:</span><ul class="mycode_list"><li>Introduce a new "duration_timer_onset" property for customizing when the duration timer appears in responses that have "duration_timer" set to true. By default, the onset is "start" meaning that the duration timer appears as soon as the response is visible. It can be optionally set to "end" so that the timer only appears as a participant response is recorded. The "end" mode may be better suited for typical speeded task setups. <br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">New Features:<br />
</span><ul class="mycode_list"><li>No major new features are included in this update.<br />
</li>
</ul>
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the January Grammar Update! Due to the MLK holiday on Monday 1/17/2022, this update will be made first available on our testing server (<a href="https://testing.findingfive.com" target="_blank" rel="noopener" class="mycode_url">https://testing.findingfive.com</a> - US server accounts only) on Monday 1/17/2022, and then on the production servers (<a href="https://www.findingfive.com" target="_blank" rel="noopener" class="mycode_url">https://www.findingfive.com</a> or <a href="https://eu.findingfive.com" target="_blank" rel="noopener" class="mycode_url">https://eu.findingfive.com</a>) on Tuesday, 1/18/2022.<br />
<br />
This January update mostly consists of bug fixes and a minor feature tweak:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Bug Fixes:</span><br />
<ul class="mycode_list"><li>Fixed an issue where a text response with a "max_char" setting would require an extra click in the text box before participants could enter their response.<br />
</li>
<li>Fixed an issue where the duration timer of a choice response continued counting while the choice response displays visual feedback (if feedback is set). The duration timer now stops as soon as a choice is made by participants, before the feedback is shown.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Improvements:</span><ul class="mycode_list"><li>Introduce a new "duration_timer_onset" property for customizing when the duration timer appears in responses that have "duration_timer" set to true. By default, the onset is "start" meaning that the duration timer appears as soon as the response is visible. It can be optionally set to "end" so that the timer only appears as a participant response is recorded. The "end" mode may be better suited for typical speeded task setups. <br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">New Features:<br />
</span><ul class="mycode_list"><li>No major new features are included in this update.<br />
</li>
</ul>
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[December Grammar Update - 12/27/2021]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=181</link>
			<pubDate>Tue, 21 Dec 2021 16:50:23 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=181</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the December Study Grammar update, to be effective on December 27, 2021! For December, we are bringing a host of new features and optimizations:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><br />
<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Beta Support for Safari on MacOS, and all browsers on iOS and PadOS</span>: The FindingFive website is now fully accessible to both participants and researchers using the Safari browser on MacOS as well as all mobile browsers on iOS and PadOS. The support for Apple devices and software is currently in beta, meaning that some bugs may exist. <br />
<span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u"><br />
For participants to be able to use Safari to participate in your study, you must launch a new session.</span></span> Existing active sessions are still closed to Safari users, and will only work with Firefox or Chrome on a desktop or laptop.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Dark Mode:</span> It is now possible to display trial content using the dark mode (black background and white text) by setting the <a href="https://help.findingfive.com/api/trial-templates.html#basic" target="_blank" rel="noopener" class="mycode_url">color scheme</a> of a trial to "dark". <br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Duration timer: </span>It is now possible to display a duration timer for visible responses, indicating how long participants have spent on that response. Please check out the <a href="https://help.findingfive.com/api/responses.html" target="_blank" rel="noopener" class="mycode_url">documentation on responses</a> for details.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Bug fixes:</span><br />
<ul class="mycode_list"><li>Fixed an issue where the visual feedback for clickable images or videos isn't properly displayed<br />
</li>
<li>Fixed an issue where studies with identical duration settings for the trial and a response within the trial were permitted to run. This setup will result in a so-called racing condition, and is now banned. <br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes:</span><br />
<ul class="mycode_list"><li>Internal updates to the text, mouse_reset, mouse_position, and the keypress responses to improve the responsiveness of these responses and the precision of reaction time calculation.<br />
</li>
</ul>
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of the December Study Grammar update, to be effective on December 27, 2021! For December, we are bringing a host of new features and optimizations:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><br />
<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Beta Support for Safari on MacOS, and all browsers on iOS and PadOS</span>: The FindingFive website is now fully accessible to both participants and researchers using the Safari browser on MacOS as well as all mobile browsers on iOS and PadOS. The support for Apple devices and software is currently in beta, meaning that some bugs may exist. <br />
<span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u"><br />
For participants to be able to use Safari to participate in your study, you must launch a new session.</span></span> Existing active sessions are still closed to Safari users, and will only work with Firefox or Chrome on a desktop or laptop.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Dark Mode:</span> It is now possible to display trial content using the dark mode (black background and white text) by setting the <a href="https://help.findingfive.com/api/trial-templates.html#basic" target="_blank" rel="noopener" class="mycode_url">color scheme</a> of a trial to "dark". <br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Duration timer: </span>It is now possible to display a duration timer for visible responses, indicating how long participants have spent on that response. Please check out the <a href="https://help.findingfive.com/api/responses.html" target="_blank" rel="noopener" class="mycode_url">documentation on responses</a> for details.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Bug fixes:</span><br />
<ul class="mycode_list"><li>Fixed an issue where the visual feedback for clickable images or videos isn't properly displayed<br />
</li>
<li>Fixed an issue where studies with identical duration settings for the trial and a response within the trial were permitted to run. This setup will result in a so-called racing condition, and is now banned. <br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes:</span><br />
<ul class="mycode_list"><li>Internal updates to the text, mouse_reset, mouse_position, and the keypress responses to improve the responsiveness of these responses and the precision of reaction time calculation.<br />
</li>
</ul>
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[November Study Grammar Update - 11/8/2021]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=169</link>
			<pubDate>Sun, 07 Nov 2021 16:17:31 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=169</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to release FindingFive' November Study Grammar update! Going forward, we will adopt a semi-regular monthly updating schedule for our study grammar, barring any emergency bug fixes. For November, we are bringing these following new features and changes, to be effective on Monday, November 8, 2021:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><br />
<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Checking for the presence of external mouses:</span> For studies that use the "mouse position" response to achieve mouse tracking, FindingFive will now automatically detect if participants are using a touch-only device (which can't really be used for mouse tracking). Participants will be asked to attach an external pointing device (a trackpad or a mouse) to their computer before being allowed to continue. <br />
<br />
A (very amateurish) YouTube video demonstrating an early prototype of this feature can be viewed here: <a href="https://www.youtube.com/watch?v=drbsu1K3CfQ" target="_blank" rel="noopener" class="mycode_url">https://www.youtube.com/watch?v=drbsu1K3CfQ</a><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u"><span style="color: #e86e04;" class="mycode_color">Backward incompatibility warning:</span></span></span> If you currently have an active session using the mouse position response, you must stop them as they will cease to work properly. Please preview your study under the new grammar and launch it again. <br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Built-in mic check:</span> For studies using the audio response or the background audio response, a built-in "mic check" process will now be automatically added to the beginning of a study. Participants must first test their mic to make sure there is detectable audio input before being allowed to continue. This will effectively prevent participants with an unknowingly broken microphone from taking the study.<br />
<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Bug fixes:</span><ul class="mycode_list"><li>Fixed an issue where multiple audio players may appear if participants re-record themselves with the audio response.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes:</span><ul class="mycode_list"><li>There are no other changes.<br />
</li>
</ul>
<br />
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to release FindingFive' November Study Grammar update! Going forward, we will adopt a semi-regular monthly updating schedule for our study grammar, barring any emergency bug fixes. For November, we are bringing these following new features and changes, to be effective on Monday, November 8, 2021:<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><br />
<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Checking for the presence of external mouses:</span> For studies that use the "mouse position" response to achieve mouse tracking, FindingFive will now automatically detect if participants are using a touch-only device (which can't really be used for mouse tracking). Participants will be asked to attach an external pointing device (a trackpad or a mouse) to their computer before being allowed to continue. <br />
<br />
A (very amateurish) YouTube video demonstrating an early prototype of this feature can be viewed here: <a href="https://www.youtube.com/watch?v=drbsu1K3CfQ" target="_blank" rel="noopener" class="mycode_url">https://www.youtube.com/watch?v=drbsu1K3CfQ</a><br />
<br />
<span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u"><span style="color: #e86e04;" class="mycode_color">Backward incompatibility warning:</span></span></span> If you currently have an active session using the mouse position response, you must stop them as they will cease to work properly. Please preview your study under the new grammar and launch it again. <br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Built-in mic check:</span> For studies using the audio response or the background audio response, a built-in "mic check" process will now be automatically added to the beginning of a study. Participants must first test their mic to make sure there is detectable audio input before being allowed to continue. This will effectively prevent participants with an unknowingly broken microphone from taking the study.<br />
<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Bug fixes:</span><ul class="mycode_list"><li>Fixed an issue where multiple audio players may appear if participants re-record themselves with the audio response.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes:</span><ul class="mycode_list"><li>There are no other changes.<br />
</li>
</ul>
<br />
If you have any questions regarding this grammar update, please leave your comments below. Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Study Grammar update 10/18: Introducing the Photo Response!]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=162</link>
			<pubDate>Mon, 18 Oct 2021 01:14:00 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=162</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of a brand new response - the Photo Response! The photo response allows participants to take a picture with either a webcam (if they are using a laptop or desktop) or the built-in front-facing camera in their mobile devices. <br />
<br />
<span style="font-weight: bold;" class="mycode_b">Start using the photo response</span><br />
Using the photo response is as easy as adding a new response of the type "photo" to your study:<br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="http://discuss.findingfive.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=28" target="_blank" title="">Screen Shot 2021-10-17 at 8.37.28 PM.png</a> (Size: 50.93 KB / Downloads: 15)
<!-- end: postbit_attachments_attachment --><br />
<br />
That's it! Participants will be prompted to take a picture (of themselves or anything else) and the resulting images will be available as JPG files in the downloadable ZIP after your session is complete.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Optional tweaks</span><br />
If you wish to make tweaks such as changing the size of the output picture size, or horizontally flipping the image, please take a look at <a href="https://help.findingfive.com/api/responses.html#photo" target="_blank" rel="noopener" class="mycode_url">the documentation on the photo response</a>.<br />
<br />
For any questions or comments, please leave them here as a reply! Thanks!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of a brand new response - the Photo Response! The photo response allows participants to take a picture with either a webcam (if they are using a laptop or desktop) or the built-in front-facing camera in their mobile devices. <br />
<br />
<span style="font-weight: bold;" class="mycode_b">Start using the photo response</span><br />
Using the photo response is as easy as adding a new response of the type "photo" to your study:<br />
<br />
<!-- start: postbit_attachments_attachment -->
<br /><!-- start: attachment_icon -->
<img src="http://discuss.findingfive.com/images/attachtypes/image.png" title="PNG Image" border="0" alt=".png" />
<!-- end: attachment_icon -->&nbsp;&nbsp;<a href="attachment.php?aid=28" target="_blank" title="">Screen Shot 2021-10-17 at 8.37.28 PM.png</a> (Size: 50.93 KB / Downloads: 15)
<!-- end: postbit_attachments_attachment --><br />
<br />
That's it! Participants will be prompted to take a picture (of themselves or anything else) and the resulting images will be available as JPG files in the downloadable ZIP after your session is complete.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Optional tweaks</span><br />
If you wish to make tweaks such as changing the size of the output picture size, or horizontally flipping the image, please take a look at <a href="https://help.findingfive.com/api/responses.html#photo" target="_blank" rel="noopener" class="mycode_url">the documentation on the photo response</a>.<br />
<br />
For any questions or comments, please leave them here as a reply! Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Major Study Grammar Update 9/13]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=146</link>
			<pubDate>Fri, 10 Sep 2021 14:14:49 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=146</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
The FindingFive Study Grammar is updated on <span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u">Monday, September 13, 2021</span></span> to include the following new features, bugfixes, and other changes. <br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">FindingFive studies will now run on Android mobile browsers! </span>Yep - that's right: you can now design your study just once and it'll run on desktops, laptops, Android phones, and Android tablets! iPhone and iPad support will be introduced in early 2022 as well.<br />
<br />
Not only the studies themselves can run on small screens now, most participant-facing pages (including signin, study list, single study details page) are also optimized for mobile devices. As a result, if a participant gets a link to your study, they can complete the entire participation process on a mobile device.<br />
<br />
Researchers will still need to design studies on a desktop or laptop, but you'll be able to preview the study on mobile devices now as well.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Improved pseudorandom stimulus pattern:</span> It is now possible to assign multiple values to a custom stimulus attribute and perform <br />
pseudorandomization on the trial template(s) containing stimuli with this custom attribute.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Hide the "Press X" hint in a choice response:</span> It is now possible to hide such a hint, which is normally displayed below the buttons, by adding <span style="font-family: Courier New;" class="mycode_font">"hint": false </span>to a choice response.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Always show the "Response Received" confirmation at the end of a trial:</span> It is now possible to always show this message, which by default only shows up when FindingFive is syncing participant data to the server. To manually turn this on, add <span style="font-family: Courier New;" class="mycode_font">"response_receipt": true</span> to the corresponding trial templates. <br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Bug fixes</span><ul class="mycode_list"><li>In some cases, the keypress response did not accept key presses that are defined in a whitelist. This has now been fixed.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes</span><ul class="mycode_list"><li>No other notable changes in this update<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
The FindingFive Study Grammar is updated on <span style="font-weight: bold;" class="mycode_b"><span style="text-decoration: underline;" class="mycode_u">Monday, September 13, 2021</span></span> to include the following new features, bugfixes, and other changes. <br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">FindingFive studies will now run on Android mobile browsers! </span>Yep - that's right: you can now design your study just once and it'll run on desktops, laptops, Android phones, and Android tablets! iPhone and iPad support will be introduced in early 2022 as well.<br />
<br />
Not only the studies themselves can run on small screens now, most participant-facing pages (including signin, study list, single study details page) are also optimized for mobile devices. As a result, if a participant gets a link to your study, they can complete the entire participation process on a mobile device.<br />
<br />
Researchers will still need to design studies on a desktop or laptop, but you'll be able to preview the study on mobile devices now as well.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Improved pseudorandom stimulus pattern:</span> It is now possible to assign multiple values to a custom stimulus attribute and perform <br />
pseudorandomization on the trial template(s) containing stimuli with this custom attribute.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Hide the "Press X" hint in a choice response:</span> It is now possible to hide such a hint, which is normally displayed below the buttons, by adding <span style="font-family: Courier New;" class="mycode_font">"hint": false </span>to a choice response.<br />
<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Always show the "Response Received" confirmation at the end of a trial:</span> It is now possible to always show this message, which by default only shows up when FindingFive is syncing participant data to the server. To manually turn this on, add <span style="font-family: Courier New;" class="mycode_font">"response_receipt": true</span> to the corresponding trial templates. <br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Bug fixes</span><ul class="mycode_list"><li>In some cases, the keypress response did not accept key presses that are defined in a whitelist. This has now been fixed.<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes</span><ul class="mycode_list"><li>No other notable changes in this update<br />
</li>
</ul>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Minor Study Grammar Update 08/18/2021]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=137</link>
			<pubDate>Thu, 19 Aug 2021 13:32:37 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=137</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
The FindingFive Study Grammar has been updated to include the following new features, bugfixes, and other minor changes.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><ul class="mycode_list"><li>It is now possible to assign the key corresponding to the "continue" button to a key other than the space bar, or just disable it altogether. <a href="https://help.findingfive.com/api/trial-templates.html#basic" target="_blank" rel="noopener" class="mycode_url">https://help.findingfive.com/api/trial-t...html#basic</a><br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Bug fixes</span><ul class="mycode_list"><li>No bug fixes in this update<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes</span><ul class="mycode_list"><li>If a study features audio recording or other actions that require microphone access, the way that participants are asked to share their microphone access is now more intuitive to participants. <br />
</li>
<li>If a participant uses a keyboard with media control keys like "Play" and "Stop", pressing those keys will no longer have an effect on audio and video stimuli.<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
The FindingFive Study Grammar has been updated to include the following new features, bugfixes, and other minor changes.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">New Features</span><ul class="mycode_list"><li>It is now possible to assign the key corresponding to the "continue" button to a key other than the space bar, or just disable it altogether. <a href="https://help.findingfive.com/api/trial-templates.html#basic" target="_blank" rel="noopener" class="mycode_url">https://help.findingfive.com/api/trial-t...html#basic</a><br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Bug fixes</span><ul class="mycode_list"><li>No bug fixes in this update<br />
</li>
</ul>
<span style="font-weight: bold;" class="mycode_b">Other changes</span><ul class="mycode_list"><li>If a study features audio recording or other actions that require microphone access, the way that participants are asked to share their microphone access is now more intuitive to participants. <br />
</li>
<li>If a participant uses a keyboard with media control keys like "Play" and "Stop", pressing those keys will no longer have an effect on audio and video stimuli.<br />
</li>
</ul>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Support for setting "barrier" on text and image stimuli]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=127</link>
			<pubDate>Thu, 22 Jul 2021 15:11:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=127</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are happy to announce a minor feature addition to FindingFive's study grammar: it is now possible to set "barrier" on text and image stimuli! <br />
<br />
<span style="font-weight: bold;" class="mycode_b">What's Barrier?</span><br />
If you haven't heard of barrier and its function in building adapative experiments yet, please check out this tutorial: <a href="https://news.findingfive.com/2019/04/23/tutorial-adjusting-the-timing-of-stimuli-with-barriers/" target="_blank" rel="noopener" class="mycode_url">https://news.findingfive.com/2019/04/23/...-barriers/</a><br />
<br />
<span style="font-weight: bold;" class="mycode_b">A hypothetical setup: display two text stimuli in order</span><br />
Imagine that you are displaying two text stimuli on the same trial, where the first text stimulus should stay on the screen for 3 seconds, and then the second stimulus will show up. <br />
<br />
This can already be done without this new barrier support for text stimuli, but it comes with some hassle and inflexibility. Essentially, you'll need to set a duration of 3 seconds to the first stimulus, which controls how long the first stimulus is visible, AND <span style="font-style: italic;" class="mycode_i">a delay</span> of 3 seconds for the second stimulus, which tells the second stimulus not to show up when the first stimulus is visible. This is a little clumsy - we had to modify two stimuli to achieve this functionality. Moreover, if the duration of the first stimulus is variable across trials, this will get out of control: we would need to create many duplicate versions of the second stimulus, each with a different delay setting to accommodate the duration of the first stimulus!<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Barrier solves this problem</span><br />
Now with the newly introduced barrier support for text and image stimuli, this can be easily done. All you need to do is to add to the first stimulus a barrier setting in addition to the duration one, like this:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"barrier": true,<br />
"duration": 3</code></div></div><br />
This tells FindingFive to display the first stimulus for 3 seconds, and bars all subsequent stimuli or responses from showing up until the duration is over. In other words, the barrier function allows you to avoid changing the definition of all following elements, stimulus or response, on the same trial. Overall, such a setup offers a cleaner flow and more predictable trial behavior.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Documentation page is updated</span><br />
You can find the new entry on "barrier" for <a href="https://help.findingfive.com/api/stimuli.html#text" target="_blank" rel="noopener" class="mycode_url">the text stimulus</a> and similarly for <a href="https://help.findingfive.com/api/stimuli.html#image" target="_blank" rel="noopener" class="mycode_url">the image stimulus</a>.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Questions?<br />
</span>Leave your comments below if you have questions about this new feature!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are happy to announce a minor feature addition to FindingFive's study grammar: it is now possible to set "barrier" on text and image stimuli! <br />
<br />
<span style="font-weight: bold;" class="mycode_b">What's Barrier?</span><br />
If you haven't heard of barrier and its function in building adapative experiments yet, please check out this tutorial: <a href="https://news.findingfive.com/2019/04/23/tutorial-adjusting-the-timing-of-stimuli-with-barriers/" target="_blank" rel="noopener" class="mycode_url">https://news.findingfive.com/2019/04/23/...-barriers/</a><br />
<br />
<span style="font-weight: bold;" class="mycode_b">A hypothetical setup: display two text stimuli in order</span><br />
Imagine that you are displaying two text stimuli on the same trial, where the first text stimulus should stay on the screen for 3 seconds, and then the second stimulus will show up. <br />
<br />
This can already be done without this new barrier support for text stimuli, but it comes with some hassle and inflexibility. Essentially, you'll need to set a duration of 3 seconds to the first stimulus, which controls how long the first stimulus is visible, AND <span style="font-style: italic;" class="mycode_i">a delay</span> of 3 seconds for the second stimulus, which tells the second stimulus not to show up when the first stimulus is visible. This is a little clumsy - we had to modify two stimuli to achieve this functionality. Moreover, if the duration of the first stimulus is variable across trials, this will get out of control: we would need to create many duplicate versions of the second stimulus, each with a different delay setting to accommodate the duration of the first stimulus!<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Barrier solves this problem</span><br />
Now with the newly introduced barrier support for text and image stimuli, this can be easily done. All you need to do is to add to the first stimulus a barrier setting in addition to the duration one, like this:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"barrier": true,<br />
"duration": 3</code></div></div><br />
This tells FindingFive to display the first stimulus for 3 seconds, and bars all subsequent stimuli or responses from showing up until the duration is over. In other words, the barrier function allows you to avoid changing the definition of all following elements, stimulus or response, on the same trial. Overall, such a setup offers a cleaner flow and more predictable trial behavior.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Documentation page is updated</span><br />
You can find the new entry on "barrier" for <a href="https://help.findingfive.com/api/stimuli.html#text" target="_blank" rel="noopener" class="mycode_url">the text stimulus</a> and similarly for <a href="https://help.findingfive.com/api/stimuli.html#image" target="_blank" rel="noopener" class="mycode_url">the image stimulus</a>.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Questions?<br />
</span>Leave your comments below if you have questions about this new feature!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Experimental support for speech recognition now available]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=109</link>
			<pubDate>Fri, 21 May 2021 14:57:30 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=109</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are *very* excited to tell you about a new cool grammar feature: SPEECH RECOGNITION in audio responses. With speech recognition, FindingFive will automatically transcribe participants' audio recordings for you! For the time being, it <span style="text-decoration: underline;" class="mycode_u">only works with English</span>, but we are exploring the possibility of enabling other languages as well.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Highly experimental (Must Read)</span><br />
Speech recognition on FindingFive is implemented by using a closed-source and yet openly accessible speech-to-text technology provided by Google for everyone to use. Because this technology is provided to everyone for free, Google offers <span style="text-decoration: underline;" class="mycode_u">no guarantee</span> whatsoever on its accuracy or reliability. As a result, FindingFive cannot offer any guarantee either. <br />
<br />
In addition, this feature is "rate limited", meaning that Google may suddenly deny further requests to use this feature once the number of requests from a single user reaches a certain, undisclosed threshold on a daily basis. That means:<ul class="mycode_list"><li>While you are creating and tweaking your study, the speech recognition feature may suddenly stop working because you have reached the limit. When that happens, take a break and it'll resolve itself the next day.<br />
</li>
<li>While a participant is participating your study, the speech recognition feature may stop working in the middle of the study, because the participant has hit their daily limit. The next participant, assuming they are not using the same computer as the first one, will not be affected. This limit is applied per Chrome browser installation. As a result, as long as you are not transcribing tons of audio recording in a single study, this limit is less of an issue in production studies because of the distributed nature of online testing (each participant is only restricted by their own limit)!<br />
</li>
</ul>
In summary, our advice is that please design your study in a way so that automatically transcribed speech text is the icing on the cake, rather than the cake itself! <img src="http://discuss.findingfive.com/images/smilies/biggrin.png" alt="Big Grin" title="Big Grin" class="smilie smilie_4" /> You will always get the audio recording, even when speech recognition stops working.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Google Chrome Only</span><br />
Also because the underlying speech-to-text technology is offered by Google, only participants with a Chrome browser can use it. FindingFive has implemented a robust check mechanism to prevent participants with Firefox from ever starting a study that uses speech recognition. Such participants would be asked to switch browsers before being allowed to start the study.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">How to use</span><br />
We have updated our Study Grammar documentation with the details, but it's very straightforward. Just add the following bit to either the <a href="https://help.findingfive.com/api/responses.html#audio" target="_blank" rel="noopener" class="mycode_url">audio response</a> or the <a href="https://help.findingfive.com/api/responses.html#background_audio" target="_blank" rel="noopener" class="mycode_url">background audio response</a>:<br />
<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"speech_to_text": true</code></div></div><br />
That's it! In the downloadable CSV containing participant data, you'll get both the original audio recording (saved separately as an audio file) and a transcribed text in the CSV.<br />
<br />
Please feel free to leave your questions in this thread! We look forward to hearing your suggestions and feedback.]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are *very* excited to tell you about a new cool grammar feature: SPEECH RECOGNITION in audio responses. With speech recognition, FindingFive will automatically transcribe participants' audio recordings for you! For the time being, it <span style="text-decoration: underline;" class="mycode_u">only works with English</span>, but we are exploring the possibility of enabling other languages as well.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Highly experimental (Must Read)</span><br />
Speech recognition on FindingFive is implemented by using a closed-source and yet openly accessible speech-to-text technology provided by Google for everyone to use. Because this technology is provided to everyone for free, Google offers <span style="text-decoration: underline;" class="mycode_u">no guarantee</span> whatsoever on its accuracy or reliability. As a result, FindingFive cannot offer any guarantee either. <br />
<br />
In addition, this feature is "rate limited", meaning that Google may suddenly deny further requests to use this feature once the number of requests from a single user reaches a certain, undisclosed threshold on a daily basis. That means:<ul class="mycode_list"><li>While you are creating and tweaking your study, the speech recognition feature may suddenly stop working because you have reached the limit. When that happens, take a break and it'll resolve itself the next day.<br />
</li>
<li>While a participant is participating your study, the speech recognition feature may stop working in the middle of the study, because the participant has hit their daily limit. The next participant, assuming they are not using the same computer as the first one, will not be affected. This limit is applied per Chrome browser installation. As a result, as long as you are not transcribing tons of audio recording in a single study, this limit is less of an issue in production studies because of the distributed nature of online testing (each participant is only restricted by their own limit)!<br />
</li>
</ul>
In summary, our advice is that please design your study in a way so that automatically transcribed speech text is the icing on the cake, rather than the cake itself! <img src="http://discuss.findingfive.com/images/smilies/biggrin.png" alt="Big Grin" title="Big Grin" class="smilie smilie_4" /> You will always get the audio recording, even when speech recognition stops working.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Google Chrome Only</span><br />
Also because the underlying speech-to-text technology is offered by Google, only participants with a Chrome browser can use it. FindingFive has implemented a robust check mechanism to prevent participants with Firefox from ever starting a study that uses speech recognition. Such participants would be asked to switch browsers before being allowed to start the study.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">How to use</span><br />
We have updated our Study Grammar documentation with the details, but it's very straightforward. Just add the following bit to either the <a href="https://help.findingfive.com/api/responses.html#audio" target="_blank" rel="noopener" class="mycode_url">audio response</a> or the <a href="https://help.findingfive.com/api/responses.html#background_audio" target="_blank" rel="noopener" class="mycode_url">background audio response</a>:<br />
<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"speech_to_text": true</code></div></div><br />
That's it! In the downloadable CSV containing participant data, you'll get both the original audio recording (saved separately as an audio file) and a transcribed text in the CSV.<br />
<br />
Please feel free to leave your questions in this thread! We look forward to hearing your suggestions and feedback.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[A new way to specify duration of background audio]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=100</link>
			<pubDate>Thu, 29 Apr 2021 15:59:25 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=48">Grace</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=100</guid>
			<description><![CDATA[<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Researchers,</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We are excited to announce a new way to specify the duration of a background audio response, making it possible to dynamically adapt the duration of an audio recording to the duration of multimedia stimulus content presented on the same trial as the audio response. </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b"> </span></span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">The new feature allows researchers to</span></span></span> <a href="https://help.findingfive.com/api/responses.html?highlight=stimulus_group" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">specify the duration of a background audio response </span></span></span></span></span><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-style: italic;" class="mycode_i"><span style="font-weight: bold;" class="mycode_b">relative</span></span></span></span></span></span><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b"> to the duration of a separate stimulus on the same trial</span></span></span></span></span></a><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"> (e.g., an audio or video stimulus). This can be particularly useful when your audio stimulus files vary in duration, and you would like to record participants adaptively - longer for longer stimuli and shorter for shorter stimuli.</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">This new property will work in conjunction with a new feature -- </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">stimulus group</span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"> -- which allows researchers to  define the group of audio stimuli to which the audio recording duration will be adjusted.  For example, when the duration of a background audio response is set as follows:</span></span></span><br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"duration": "%sgroup:audio+2.0"</code></div></div><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">The duration of the audio recording will be the duration of the stimulus of the group “audio” (or any group name that you may want to use), </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">on the same trial as the current response</span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">, plus 2 seconds. If there are no stimuli of the group “audio” on the same trial, this duration setting will be ignored and the audio response will record indefinitely and result in a stuck trial. The minus sign “-” is also supported, if the desired goal is to record a shorter duration than the referenced stimulus.</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">For the above setup to work, the stimuli being referenced must have a group defined. In this case, each stimulus needs to be added to the “audio” group like this (if you used a different group name above, make sure to change “audio” to your group name):</span></span></span><br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"group": "audio"</code></div></div><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">*Importantly, “audio” in this example can be subbed for any phrase as long as it is consistent throughout the code.*</span></span></span></span><br />
<br />
<br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We hope you find this update useful! </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-family: Verdana;" class="mycode_font">Questions? Reply to</span></span><span style="color: #333333;" class="mycode_color"><span style="font-family: Verdana;" class="mycode_font"> this thread and let us know!</span></span>]]></description>
			<content:encoded><![CDATA[<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Researchers,</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We are excited to announce a new way to specify the duration of a background audio response, making it possible to dynamically adapt the duration of an audio recording to the duration of multimedia stimulus content presented on the same trial as the audio response. </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b"> </span></span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">The new feature allows researchers to</span></span></span> <a href="https://help.findingfive.com/api/responses.html?highlight=stimulus_group" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b">specify the duration of a background audio response </span></span></span></span></span><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-style: italic;" class="mycode_i"><span style="font-weight: bold;" class="mycode_b">relative</span></span></span></span></span></span><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u"><span style="font-weight: bold;" class="mycode_b"> to the duration of a separate stimulus on the same trial</span></span></span></span></span></a><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"> (e.g., an audio or video stimulus). This can be particularly useful when your audio stimulus files vary in duration, and you would like to record participants adaptively - longer for longer stimuli and shorter for shorter stimuli.</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">This new property will work in conjunction with a new feature -- </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">stimulus group</span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"> -- which allows researchers to  define the group of audio stimuli to which the audio recording duration will be adjusted.  For example, when the duration of a background audio response is set as follows:</span></span></span><br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"duration": "%sgroup:audio+2.0"</code></div></div><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">The duration of the audio recording will be the duration of the stimulus of the group “audio” (or any group name that you may want to use), </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">on the same trial as the current response</span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">, plus 2 seconds. If there are no stimuli of the group “audio” on the same trial, this duration setting will be ignored and the audio response will record indefinitely and result in a stuck trial. The minus sign “-” is also supported, if the desired goal is to record a shorter duration than the referenced stimulus.</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">For the above setup to work, the stimuli being referenced must have a group defined. In this case, each stimulus needs to be added to the “audio” group like this (if you used a different group name above, make sure to change “audio” to your group name):</span></span></span><br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>"group": "audio"</code></div></div><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">*Importantly, “audio” in this example can be subbed for any phrase as long as it is consistent throughout the code.*</span></span></span></span><br />
<br />
<br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We hope you find this update useful! </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-family: Verdana;" class="mycode_font">Questions? Reply to</span></span><span style="color: #333333;" class="mycode_color"><span style="font-family: Verdana;" class="mycode_font"> this thread and let us know!</span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New Follow-Up Responses Feature]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=91</link>
			<pubDate>Wed, 07 Apr 2021 14:52:33 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=8">Lila - FF Operations</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=91</guid>
			<description><![CDATA[<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Dear Researchers,</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We are happy to announce the development of a <span style="font-style: italic;" class="mycode_i">new</span> property within our existing trial templates: </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">follow-up responses!</span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"> Please find full documentation of this property here: </span></span></span><a href="https://help.findingfive.com/api/trial-templates.html?highlight=follow_up" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u">https://help.findingfive.com/api/trial-templates.html?highlight=follow_up</span></span></span></span></a><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">. </span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">What it does</span></span></span></span><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">This new property allows you to specify follow-up responses, based on participants’ initial responses to a stimulus. For example, if participants select the choice “other” in an initial response, you can use this trial template to trigger a follow-up text-box, allowing participants to explain their selection in more detail. </span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Recommended usage</span></span></span></span><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">This property is recommended for situations where </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">only </span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">follow-up responses are required. You may instead wish to branch participants into conditions with different stimuli, responses, and tasks, based on their responses in an initial trial. In these scenarios, please use our conditional branching feature instead! Details on conditional branching can be found here: </span></span></span><a href="https://news.findingfive.com/2021/01/08/tutorial-conditional-branching/" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u">https://news.findingfive.com/2021/01/08/tutorial-conditional-branching/</span></span></span></span></a><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">  </span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Pain points addressed</span></span></span></span><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Development of this new property means you no longer have to use conditional branching for simple follow-up responses!</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We hope you find this new property helpful! </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Questions? Reply in this thread, and we will answer!</span></span></span>]]></description>
			<content:encoded><![CDATA[<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Dear Researchers,</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We are happy to announce the development of a <span style="font-style: italic;" class="mycode_i">new</span> property within our existing trial templates: </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">follow-up responses!</span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"> Please find full documentation of this property here: </span></span></span><a href="https://help.findingfive.com/api/trial-templates.html?highlight=follow_up" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u">https://help.findingfive.com/api/trial-templates.html?highlight=follow_up</span></span></span></span></a><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">. </span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">What it does</span></span></span></span><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">This new property allows you to specify follow-up responses, based on participants’ initial responses to a stimulus. For example, if participants select the choice “other” in an initial response, you can use this trial template to trigger a follow-up text-box, allowing participants to explain their selection in more detail. </span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Recommended usage</span></span></span></span><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">This property is recommended for situations where </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-style: italic;" class="mycode_i">only </span></span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">follow-up responses are required. You may instead wish to branch participants into conditions with different stimuli, responses, and tasks, based on their responses in an initial trial. In these scenarios, please use our conditional branching feature instead! Details on conditional branching can be found here: </span></span></span><a href="https://news.findingfive.com/2021/01/08/tutorial-conditional-branching/" target="_blank" rel="noopener" class="mycode_url"><span style="color: #1155cc;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="text-decoration: underline;" class="mycode_u">https://news.findingfive.com/2021/01/08/tutorial-conditional-branching/</span></span></span></span></a><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">  </span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font"><span style="font-weight: bold;" class="mycode_b">Pain points addressed</span></span></span></span><br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Development of this new property means you no longer have to use conditional branching for simple follow-up responses!</span></span></span><br />
 <br />
<span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">We hope you find this new property helpful! </span></span></span><span style="color: #333333;" class="mycode_color"><span style="font-size: small;" class="mycode_size"><span style="font-family: Verdana;" class="mycode_font">Questions? Reply in this thread, and we will answer!</span></span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[New Stimulus: Tokenized Images!]]></title>
			<link>http://discuss.findingfive.com/showthread.php?tid=77</link>
			<pubDate>Fri, 19 Mar 2021 00:42:44 +0000</pubDate>
			<dc:creator><![CDATA[<a href="http://discuss.findingfive.com/member.php?action=profile&uid=1">Ting</a>]]></dc:creator>
			<guid isPermaLink="false">http://discuss.findingfive.com/showthread.php?tid=77</guid>
			<description><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of a new stimulus type, <span style="font-weight: bold;" class="mycode_b">tokenized images</span>! The documentation on this new stimulus can be found here: <a href="https://help.findingfive.com/api/stimuli.html#tokenized_image" target="_blank" rel="noopener" class="mycode_url">https://help.findingfive.com/api/stimuli...ized_image</a><br />
<br />
<span style="font-weight: bold;" class="mycode_b">What it does</span><br />
As the name suggests, a tokenized image stimulus can be used to display a list of images in sequence. If you have used our tokenized text or tokenized audio stimuli, the tokenized image stimulus is our effort to bring similar functionality to images.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Recommended usage</span><br />
The tokenized image stimulus is best at simulating GIF-like animation, and yet with precise timing control for how long each frame / image token should be displayed. This has many uses in psychological studies. For example, in visual priming studies, it is common to present the priming image for only a split of a second, and then collect a response on the actual target image. This new stimulus will make the creation of such stimuli easy and flexible.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Pain points addressed</span><br />
Before the introduction of this new stimulus, in order to present several images in sequence, researchers needed to use <a href="https://news.findingfive.com/2019/07/17/tutorial-yoked-trials/" target="_blank" rel="noopener" class="mycode_url">a trial-yoking technique</a> that has the side effect of a "flashing screen". Using that technique also limits the options in randomizing trials at the block level. The new tokenized image stimulus can now be used instead.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Future work</span><br />
The tokenized image stimulus does not support a self-paced option, unlike the tokenized text and tokenized audio stimuli. We are planning to add this support eventually. If you have a particular use for a self-paced tokenized image stimulus, please leave a reply below to let us know!]]></description>
			<content:encoded><![CDATA[Dear Researchers,<br />
<br />
We are excited to announce the availability of a new stimulus type, <span style="font-weight: bold;" class="mycode_b">tokenized images</span>! The documentation on this new stimulus can be found here: <a href="https://help.findingfive.com/api/stimuli.html#tokenized_image" target="_blank" rel="noopener" class="mycode_url">https://help.findingfive.com/api/stimuli...ized_image</a><br />
<br />
<span style="font-weight: bold;" class="mycode_b">What it does</span><br />
As the name suggests, a tokenized image stimulus can be used to display a list of images in sequence. If you have used our tokenized text or tokenized audio stimuli, the tokenized image stimulus is our effort to bring similar functionality to images.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Recommended usage</span><br />
The tokenized image stimulus is best at simulating GIF-like animation, and yet with precise timing control for how long each frame / image token should be displayed. This has many uses in psychological studies. For example, in visual priming studies, it is common to present the priming image for only a split of a second, and then collect a response on the actual target image. This new stimulus will make the creation of such stimuli easy and flexible.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Pain points addressed</span><br />
Before the introduction of this new stimulus, in order to present several images in sequence, researchers needed to use <a href="https://news.findingfive.com/2019/07/17/tutorial-yoked-trials/" target="_blank" rel="noopener" class="mycode_url">a trial-yoking technique</a> that has the side effect of a "flashing screen". Using that technique also limits the options in randomizing trials at the block level. The new tokenized image stimulus can now be used instead.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Future work</span><br />
The tokenized image stimulus does not support a self-paced option, unlike the tokenized text and tokenized audio stimuli. We are planning to add this support eventually. If you have a particular use for a self-paced tokenized image stimulus, please leave a reply below to let us know!]]></content:encoded>
		</item>
	</channel>
</rss>