Closed kaitj closed 5 years ago
Flurry of activity today!
@tkkuehn: Yes, that's basically the essence of what we care about in the file (Markups fiducial file version ~= 4.6), but it may be worth also ensuring each of the 32 rows has 14 columns.
Also, I've noticed some raters sometimes submit files with the AFIDs out of order. This can be fixed post-hoc but probably better to establish good habits in trainees up front: i.e. ensuring that each AFID has been placed in ascending order (1,2,...,32). It would not be difficult to add a section to our tutorial that explains how to shift single markup points up or down.
Perfect, thanks for the quick response. Just to reiterate for reference, I'll implement this checking the following requirements, and make sure that information about what's wrong is returned if the .fcsv
is invalid:
.fcsv
, and I think it's safe (or at least the best we can do) to assume the format won't change in a minor version change)desc
column (second last) contains the associated string in the protocol, after the number but before any equals sign, and with capitalized letters only in initialized landmark names.x
, y
, and z
(second, third, and fourth) columns.Looks great! Nice to haves:
1,2,...,32
label:desc
corresponds to the ground truth label:desc
.
Just so I'm sure, for an AFIDs
.fcsv
file to be valid, it needs to meet the following requirements:desc
column (second last) contains the associated string in the protocol, after the number but before any equals sign, and with capitalized letters only in initialized landmark names.x
,y
, andz
(second, third, and fourth) columns.@jclauneuro Can you confirm that these are each accurate and that I'm not missing anything?