-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom psychometric functions #24
Comments
Dear Armin,
Unfortunately, my current schedule will prevent me from being able to look at this
for at least a few months.
I do note that someone else already contributed a qpStandardWeibull function
to mQUESTPlus. I don't immediately see a demo for that, but perhaps it will
be helpful to you.
If you do figure this out, please send updated code and demos and I will sooner
or later review and add to the contributed folder. If you can't figure it out by,
say, mid-March, post back and I will do my best to look at it.
Best,
David
From: Armin Drusko <[email protected]>
Reply-To: BrainardLab/mQUESTPlus <[email protected]>
Date: Friday, January 31, 2020 at 8:01 AM
To: BrainardLab/mQUESTPlus <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [BrainardLab/mQUESTPlus] Custom (#24)
customPFDemos.zip<https://github.com/BrainardLab/mQUESTPlus/files/4139424/customPFDemos.zip>
Hello,
I wanted to implement two custom psychometric functions and test their performance with the simple routine from qpQuestPlusCoreFunctionDemo.m.
Attached are the custom PFs "Gumbel_pal" and "Weibull_pal". In the respective qpQuestPlusCoreFunctionDemo_Gumbel and qpQuestPlusCoreFunctionDemo_Weibull scripts, I specified the PFs and adjusted the stimulus domains.
The idea behind it:
The original Weibull function in mQuestPlus is a log-Weibull (or Gumbel) adjusted for the dB scale (therefore dividing by 20).
I wanted to write a more general log-scale Weibull ("Gumbel_pal").
Also, on a linear scale, a conventional Weibull ("Weibull_pal") would be useful.
Testing these two PFs leads to bad performance though. The stimuli presented by Quest seem to be way off and the parameter estimates for threshold or slope are disastrous.
I am not sure whether I adapted the scripts at all places to work with the custom PFs. Plotting the functions seems to result in a valid output i.e.
stimFine = linspace(-60,-20,100)';
y = qpPFGumbel_pal(stimFine, [-28, 0.15, 0.01, 0.01]);
plot(stimFine, y(:,2), 'linewidth', 2);
Hope someone can resolve this issue with me. Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#24?email_source=notifications&email_token=AAI24ZIQIDXC4BFXMQ25U73RAQOJXA5CNFSM4KOGVN62YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IKEG5DA>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAI24ZIWKDEJJCPVZTG346LRAQOJXANCNFSM4KOGVN6Q>.
|
Dear David, thank you for your reply. I did miss the already contributed Weibull function. Still, even testing my Demo with this PF is not leading to a good performance. Maybe @aernesto could help me out here. I would appreciate your thoughts on this. The figures below show the PFs after questPlus threshold estimation with the Weibull and contributed StandardWeibull respectively. |
Dear David, Could you have a look at it? Best, |
customPFDemos.zip
Hello,
I wanted to implement two custom psychometric functions and test their performance with the simple routine from qpQuestPlusCoreFunctionDemo.m.
Attached are the custom PFs "Gumbel_pal" and "Weibull_pal". In the respective qpQuestPlusCoreFunctionDemo_Gumbel and qpQuestPlusCoreFunctionDemo_Weibull scripts, I specified the PFs and adjusted the stimulus domains.
The idea behind it:
The original Weibull function in mQuestPlus is a log-Weibull (or Gumbel) adjusted for the dB scale (therefore dividing by 20).
I wanted to write a more general log-scale Weibull ("Gumbel_pal").
Also, on a linear scale, a conventional Weibull ("Weibull_pal") would be useful.
Testing these two PFs leads to bad performance though. The stimuli presented by Quest seem to be way off and the parameter estimates for threshold or slope are disastrous.
I am not sure whether I adapted the scripts at all places to work with the custom PFs. Plotting the functions seems to result in a valid output i.e.
Hope someone can resolve this issue with me. Thank you!
The text was updated successfully, but these errors were encountered: