Hi Adebimpe,
If you computed your own D-scores from the raw data, that's good.
I do recommend to correlate it with the D score recorded by the IAT script itself, just as a sanity check. I typically get a correlation above 0.9 between the score I compute from the raw data and the score recorded by Minno.js. If you don't get a correlation around ~0.9, there might be some mistake in your computation. A highly negative correlation around -0.9 is also fine, and you just need to find out whether the
Regarding the interpretation of the D score, it depends on which pairing condition you defined as Blocks 3 and 4, and which pairing condition you defined as Blocks 6 and 7, before computing the D score. If you defined Thin/Good, Fat/Bad as Blocks 3 and 4, then positive scores will reflect a pro-Thin preference.
When I am not sure, I always search for some kind of sanity check. For example, I would look only at one specific session and compute the mean latency in one pairing condition (e.g., Thin/Good, Fat/Bad) and the mean latency in the other pairing condition (e.g., Thin/Bad, Fat/Good). From the difference between these mean latencies, I know whether I expect the D score of that session to be positive or negative. For example, let's say I find a mean response latency of 777 for a specific session in the block with the Thin/Good pairing and a mean latency of 877 for that session in the blocks with the Thin/Bad pairing. I would expect that session to have a positive D score. If that is not the case, I continue to test the other sessions, until I understand what went wrong.
I hope that helps,
Yoav