kurokida/jsquest

A Bayesian adaptive psychometric method for measuring thresholds in online experiments.

jsquest's Issues

jsQUEST with Gorilla

Hi, @tpronk ,
I'm sorry I keep asking you for advice.

Have you ever used Gorilla?
I'm trying to get jsQUEST to work with Gorilla, and I'm having a little trouble.

To summarize, I probably need to store the jsQUEST object and retrieve it, but it fails.

Rather than explaining it in detail here, it would be better to show you a sample I created.

Gorilla has a collaborating feature, so if you have an account (or create one) I'll share the program with you.

If you have time and are interested in this, please let me know your Gorilla account.

As I mentioned earlier, I am writing a paper on jsQUEST. In it, I plan to describe how to use jsQUEST with PsychoJS, jsPsych, Gorilla, and lab.js. Thats why, I am checking how jsQUEST works with Gorilla.
As for lab.js, I haven't started yet.
I'm in no hurry, and you don't have to rush at all either.

Modularize jsQUEST & numeric.js

Hey @kurokida,

Continuing one of the topics that came up in our chat on the PsychoPy forum: how to turn jsQUEST into a module (and have it play nice with numeric.js)?

An advantage of numeric.js not being developed anymore is that we can edit its structure without worrying what happens upstream. I'm quite sure I can help you out converting it into a module, but before we go do that, a question...

What kind of module would you like? If I may make a recommendation: ES6 is the most modern standard. A build chain could look a bit like this:

• At PsychoJS we use babel to compile ES6 into JavaScript that is suitable for older browsers.
• Probably babel can also export ES6 to a global variable, similar to what you've got now, but for sure this can be done with browsersify, as I did in this experiment.

Note that I'm not really an expert in build chains, but we've got an expert in our team; I'll pull him in once we've got an outline of our plan.

Best, Thomas

Working with lab.js

Hi @tpronk , I'm sorry for bothering you.

You mentioned that you've used lab.js before, so let me ask you some questions.

This is a jsQUEST sample program for lab.js.
jsQuest_lab_js_json.txt
Change the extension to json and try to load it in lab.js.

You'll see intensity columns jsQUEST calculated in the output (CSV) file. In other words, jsQUEST is working fine.

I also want to present the intensity values on the Screen1 or Screen2 using a text ${this.parameters.intensity}, but I couldn't.

Do you have any suggestions?

Maybe we should add a sourcemap?

The bundle that's compiled with rollup makes sure the library can be used in all kinds of different module systems. However, it does mean that if an error occurs, it's difficult to trace the error back to the original source code. A sourcemap could help out with this. See https://www.npmjs.com/package/rollup-plugin-sourcemaps

Would math.js be an alternative to numeric?

I was looking around at WebGazer and noticed they've been moving away from numeric. One of the alternatives considered is math.js. Would that work for us?

For context see: brownhci/WebGazer#225

An intensity that was in range was reported as out of range

Denis Pelli has been running tests of the PsychoJS integration of jsQUEST and got an unexpected error message:

QuestUpdate: intensity -2.1941879156398305 out of range
-2.1989700043360187 to 2.8010299956639813. Pdf will be inexact.
Suggest that you increase “range” in call to QuestCreate.

Is the numeric.js updated?

Hi @tpronk , thank you in advance.

I've added the version information to src/jsQUEST.js, and compiled it.
This is the commit
b2735af

At this point, I noticed that the numeric.js was also updated.
Does this mean a change of the numeric in your repository?
Do I need to be concerned?