Conversation
|
Nice! Couple of thoughts:
|
|
|
|
|
Whoops, didn't mean to close this. |
Are you thinking this will be used to search by single assessors or for entire projects or both? |
|
Whichever. Getting the full tree for a single assessor is the main point though. |
|
|
Random suggestion, but you could forget spacing/tabs entirely maybe if you use a python structure to store the data, e.g. dict within dict within dict, generated recursively (?) Then I bet there's a module out there that can immediately reformat that to yaml/json/whatever |
|
Is there a good way to add lists into dictionaries? It would need to be something like |
|
Or a better way to have a running dictionary where you could append inputs to it? |
|
This works, but is ugly output. What I don't have is assessor inputs that are inputs for assessors, aka it only goes this far: |
|
Just used this the other day, https://bug.xnat.vanderbilt.edu/bugzilla/show_bug.cgi?id=3423#c5 :) |
|
This is what I'm currently getting. |
|
Nice. Hoping for something like this, i.e. a complete breakdown for each assessor: And maybe separately, a list of all unique scans that contribute at any level? As it's extensive output, it would be nice to be able to select just a single assessor or proctype to do this with. The |
|
New Update - Looks like this now You can also give it a proctype; for example fmrprep_v24 What's the best way to remove the subject? Is there a dax method I can use just for sessions? |
|
Here's the full output from what I've been testing on I think it's hard to read, but I'll let you decide |
|
@bud42 - We're ready to merge this in the next dax update. Take a look! https://bug.xnat.vanderbilt.edu/bugzilla/show_bug.cgi?id=3404 |
Example here: