-
Notifications
You must be signed in to change notification settings - Fork 3
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
To do list #1
Comments
Other points:
|
So we do not forget. Are still needed to finalize the BEP:
|
ENH: Remove Atlas metadata, update imaging derivatives text around seg-
I've had a look into the openneuro dataset proposed above, and it seems to have been acquired with an Arrington Research Viewpoint Eyetracker. Documentation - https://www.biopac.com/wp-content/uploads/viewpoint_eyetracker_manual.pdf It writes out text files, so relatively easy to parse. I may take a stab at this next week and we could present it as an example. Once the BEP is accepted, I'll ask Gustav to update the openneuro dataset (or give me/us permission to move the eye tracking data into raw). |
I can also create a bids-example from my data (the repo I shared privately with you). Since I will not publish any data (i.e., the tsv.gz files will be empty files, as other examples), I can share the metadata without issues. |
Pretty sure I already took care of it. Will. Just need to update the code to the latest change of the BEP. |
I have updated the HackMD to remind myself of adding columns/metadata recommendations for this eye tracker (once we pass the page of new vs old specs). |
In case someone else asks for it. Like future me for example. https://github.com/Remi-Gau/ds000201-eyetrack-conversion |
BTW, how did you get around the fact that this eyetracker does not give you monotonic sampling (i.e., there is a sampling frequency but it is not "normalized")? |
Don't remember. Not sure that I actually checked for that. Feel free to open an issue on that repo so we don't forget. |
I also prepared some example datasets, just didn’t share them yet. Will do next week! Am 01.03.2024 um 16:03 schrieb Remi Gau ***@***.***>:
Don't remember. Not sure that I actually checked for that. Feel free to open an issue on that repo so we don't forget.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
BEP-020 reference file
This is a list of things we identified with @Remi-Gau for the BEP-020 of BIDS.
Previous meeting planned Tuesday December 13th
Next meeting planned Tuesday January 10th
The text was updated successfully, but these errors were encountered: