Why does /acquisition/receiver/transferFunctions exist?

[Neumann-A]

personally i think it should be coverd by measurement/data instead having its own dataset.
The measurement of the transfer function is a calibration measurement or not? It also can be spatial dependend.

maybe we should allow dropping singleton dimensions in measurement/data?

ping @AvGladiss (currently on one week vacation)

[tknopp]

no it cannot be spatially dependent. It describes the transfer function between the receive coil and the receiver. There is no space involved.

maybe we should allow dropping singleton dimensions in measurement/data?

this has nothing to do with your question.

The transfer function has to be stored in the file in order to correct it. Its small enough that we should not care if it is redundant.

[Neumann-A]

no it cannot be spatially dependent. It describes the transfer function between the receive coil and the receiver. There is no space involved.

I was thinking of including the sensitivity matrix of the coil within it as part of the transfer function.
That is where space gets involved.

[tknopp]

coil sensitivity maps are an orthogonal thing. Please get in contact with @hofmannmartin for a discussion how storing these. This is not v2 stuff though

[hofmannmartin]

@NeumannIMT we should discuss this in a separate issue.