Skip to content
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

Loose ideas about shareable timelines template #3

Open
cherriechang opened this issue May 30, 2023 · 1 comment
Open

Loose ideas about shareable timelines template #3

cherriechang opened this issue May 30, 2023 · 1 comment

Comments

@cherriechang
Copy link

cherriechang commented May 30, 2023

  • Is having the changeable stuff be a list of arguments scaleable → maybe just like the plugins some functions need to be called and those will have their own standard versions too → have to find some way to make these all easily readible + comprehensive + transparent to users → just docs or embedded in the code too

  • (submodules) what the classification structure looks like: could you nest modules like have a general template for traditional memory vs visual perception experiments; or would the grouping be more at the level of required functionality → what kinds of "display" or interaction each experiment needs, like experiments that need users to focus on different parts of screen thru clicking on different zones vs answering questions (but thats kinda handled by the existing plugins); or just simply each experiment is a single unit and they're all at the same flat level ungrouped

  • this might just be me but i think another reason why it feels icky to do it very similarly to how importing e.g. a jsPsychHtmlKeyboardResponse is that there's 1) more stuff happening in a timeline (within it contains jsPsychHtmlKeyboardResponse instances, spans multiple pages etc.) and 2) the nature of it is more sequential → it contains info of a whole experiment procedure whereas something like jsPsychHtmlKeyboardResponse means one thing: display an html script that interacts with user keyboard; so as a user I would wanna understand the general flow of the timeline im importing conceptually when im tweaking its parameters, which i dont think is captured by the way the importing works now. i guess this can the burden of clear documentation but i also feel like the code should roughly stand on its own in this way..?

  • Make a tree of what the common parameters across experiments look like

@cherriechang
Copy link
Author

Stuff to parameterize in false memory (descending priority):
can do now

  1. number of studied lists (1-6)
  2. number of unstudied lists (1-(6-num_studied_lists))
  3. which studied lists → give one array; some default export to represent 'ALL'
  4. which unstudied lists → cannot choose duplicates → some kind of error message?
  5. studied list order of appearance → another array; some const to represent 'RANDOM'
  6. number of words in studied lists (1-15)
  7. number of words in unstudied lists (1-15)
  8. word order of appearance → ascending association, descending association, random
  9. number of test trials
  10. all studied lures included? → default 'YES', custom option give array of list indices with lure included
  11. all unstudied lures included? → default 'YES', custom option give array of list indices with lure included
  12. sample proportion of test trial → ..a fraction? (%studied vs %unstudied in remaining slots (num_test_trial - lures))
  13. free recall?
  14. break?
  15. word show period
  16. recall period
  17. break period
  18. title card show period
  19. end card show period
  20. key choice for word present vs not

bigger changes

  1. what task follows after each list is shown → free recall? math? none?
  2. order of their appearance → each list gets one? which list gets what?
  3. [general] what data gets saved, labels, etc.

need library of lists

  1. number of studied lists (1-99)
  2. number of unstudied lists (1-(99-num_studied_lists))
  3. number of words in studied lists (1-?)
  4. number of words in unstudied lists (1-?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant