search

gasparl / citapp_pc

CITapp: a response time-based Concealed Information Test lie detector web application. This method aims to reveal whether or not a certain information detail (e.g. a photo taken from the scene of a recent burglary) is known to the tested person.
https://gasparl.github.io/citapp_pc/CITapp.html
BSD 2-Clause "Simplified" License
1 stars 3 forks source link

2. Summary opening assumes previous knowledge #2

Closed vsoch closed 5 years ago

vsoch commented 5 years ago

You open with:

This application implements two versions of the response time-based Concealed Informa- tion Test (RT-CIT) deception detection method: a standard version that has been often used in the recent years (Seymour, Seifert, Shafto, & Mosmann, 2000), and a recently introduced enhanced version (Lukács, Kleinberg, & Verschuere, 2017)

referencing "the response time-based Concealed Information Test" as if I know what you are talking about. I have no idea. I would suggest to rewrite the summary for the user that doesn't know what you are talking about. For example, something along an outline like:

  1. It's important to study how people recognize items (because...)
  2. Thus they developed this task called the Concealed.... (references)
  3. The task is great, but there are still pressing problems that (it's not reproducible, hard to run, etc.)
  4. Thus, to solve these issues, we created this! :)

I would rewrite the summary in that context - you can still provide some of the more "academic paper" sounding details of the task, but remember that the paper here is intended for a general audience, and not a niche psychology community.

Review: https://github.com/openjournals/joss-reviews/issues/1179

gasparl commented 5 years ago

I revised the paper along the lines of your suggestion; mainly more detailed introduction and a screenshot of the GUI.

vsoch commented 5 years ago

Spot on!

Undetected deception may have extremely high costs in certain scenarios, such as counterterrorism, pre-employment screening for intelligence agencies, or high-stake criminal proceedings. However, meta-analyses have repeatedly shown that without special aid, based on their own best judgment only, people (including police officers, detectives, and professional judges) distinguish lies from truth on a level hardly better than mere chance (e.g., (Hartwig & Bond, 2011)).

This is exactly what I needed - you open the paper and immediately tell me the problem (lying has high costs, and people aren't great at detecting it) and then open into the next paragraph with a solution (what the manuscript is about). You've also greatly improved it by giving an example of how the interface would be used (I didn't get this before!)

Excellent work writing this for the correct audience! One quick question - are there limitations to browser support? You mention:

This application requires no technical knowledge; it can simply be opened and used in a Google Chrome browser

Is there any reason Firefox, some derivative of Edge / IE, or Safari couldn't be used?

gasparl commented 5 years ago

Thank you!

As you may have seen there are several warning messages on the start page whenever any browser other than Chrome is used. In my related online experiments I did not only put warnings but actually completely disabled the task for other browsers. Always using the same browser ensures that everything works and is displayed exactly the same way; so that it would be consistent both within and across experiments/studies/individual tests. Since this is not some website for general visits but an experimental tool, this doesn't seem much of a practical limitation. (That is: for someone conducting an experiment, downloading Chrome - if not already in use - is the least of the trouble.) I confess though that I decided on this mainly because of the time it took to each time test and make the code compatible with all browsers, which was especially and repeatedly problematic with IE. (Now I made a few quick tests; IE again doesn't work, Firefox and Opera seems fine.) Using one browser hugely simplifies this. But I also had some more nuanced issues, e.g., based on my tests, synchronizing code execution to screen repaint only seems to work well (for my timing purposes) on Chrome. In general, everything seems to work most easily and best on Chrome. And everyone uses Chrome anyway.

vsoch commented 5 years ago

I think it's okay that you are clear to specify the browser to use - it certainly is hard to maintain support for all of them. I was mainly curious and double checking that it wasn't an error to only specify Chrome.