From 766f7db108e2b8402b892051ccd8f98639d4558d Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Fri, 22 Apr 2022 14:53:57 -0400 Subject: [PATCH 1/4] ENH elaborate description of rec entity to mention proc, and adjust _proc to not make analogous to _rec I think it is actually misleading to equate _proc to _rec of MRI. _rec should be specific about data reconstruction (specific to MR) and _proc to incorporate any possible processing performed on the hardware. I do not think it is productive to make _rec ambigously absorb any possible preprocessing, whenever there is a true process of "reconstruction" involved. Eventually, we might even have _rec used again for ultrasound or some other modality needing "reconstruction" from data "acquisition" domain into data "output" domain. Could even be for EEG inverse problem solving if some hardware would do any of that LORETA dance etc. But again, postprocessing (smoothing etc) would be a separate step --- src/modality-specific-files/magnetoencephalography.md | 5 ++--- src/schema/objects/entities.yaml | 4 +++- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/src/modality-specific-files/magnetoencephalography.md b/src/modality-specific-files/magnetoencephalography.md index 9548f84ee3..7b1990d198 100644 --- a/src/modality-specific-files/magnetoencephalography.md +++ b/src/modality-specific-files/magnetoencephalography.md @@ -74,9 +74,8 @@ For example: `sub-01_task-nback_markers.sqd` Please refer to the [MEG File Formats Appendix](../appendices/meg-file-formats.md) for general information on how to deal with such manufacturer specifics and to see more examples. -The [`proc-