You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so when i want to read the stimulus : shared0953_nsd69215.png if I follow the logic explained in the nds_dataset.doc, 0953 is the index in shared1000 space, and 69215 is the index in 73KIDs space.
However, if I want to read and show that same image from the brick, using nsda.read_images() i need to query for 69214.
were you aware of this? I'm wondering then if the same thing happens with the captions? i.e. if I want to return the caption for shared0953_nsd69215.png, should I query for 69214?
ian
The text was updated successfully, but these errors were encountered:
One more thing to bear in mind. nsda.read_behaviour returns the 1-based indexing 73K indices! so it all gets very messy, at least with my use of the shared1000 images for analysis when wanting to bring together the captions, the betas, etc..
Hi Tomas,
I just realised that there is a mismatch between the filenames in
os.path.join(nsd_dir, 'Stimuli', 'shared1000', '*.png')
and the image brick.
so when i want to read the stimulus : shared0953_nsd69215.png if I follow the logic explained in the nds_dataset.doc, 0953 is the index in shared1000 space, and 69215 is the index in 73KIDs space.
However, if I want to read and show that same image from the brick, using nsda.read_images() i need to query for 69214.
were you aware of this? I'm wondering then if the same thing happens with the captions? i.e. if I want to return the caption for shared0953_nsd69215.png, should I query for 69214?
ian
The text was updated successfully, but these errors were encountered: