Gowerlabs / lumomat

MATLAB tools and SNIRF export for LUMO
https://www.gowerlabs.co.uk/lumo
MIT License
10 stars 2 forks source link

Channel design issue with Homer 3 #53

Closed labteng closed 10 months ago

labteng commented 10 months ago

Hi, I noticed that the .snirf data generated by Lumo cannot be properly read by Homer 3 in terms of the channel layout and channel index.

For instance, when two tiles are placed in separate L and R temporal locations, Homer 3 will present inter-channels connecting the two tiles. This means that a source will be linked to every detector on both tiles, resulting in numerous artificial channels. These channels do not actually exist during the recording in Lumo software. For example, source 4 connected to detector 2, S1 to D6, and so on.

image

With more tiles added, you can see more and more fake channels are added in the Homer3, causing trouble to find the index of real channels. AtlasViewerGUI will also present channels in this way, so I guess that might also relate to my previous issues about image reconstruction.

channel

When only using a single tile, this problem won't occur. image

I checked the functions used in lumomat on channels, it looks like the channel information is loaded right from the layout file. As long as the layout file is correct, I am not sure why the .snirf is not corresponded to .lufr.

Could you help me check this issue? As it really affects us doing by channel analysis and image reconstruction.

Step:

  1. download the testing package: https://gocuhk-my.sharepoint.com/:f:/g/personal/siqigao_cuhk_edu_hk/EiQ5z3eZMU9JrgPzkRW_3VsBXG98dYIlhSwWtNIZnwB58A?e=px5Eb4
  2. set folder 1T, 2T and 12T respectively as the working directory in the matlab cmd and call out the Homer3 immediately to load every snirf file. After Homer3 loads the file, you can see the channels on the right side.

system info: win 11 software version: Matlab 2023b Homer3 1.80.2 AtlasViewerGUI 2.44.0 Lumomat 18.0

samuelpowell commented 10 months ago

For instance, when two tiles are placed in separate L and R temporal locations, Homer 3 will present inter-channels connecting the two tiles. This means that a source will be linked to every detector on both tiles,

This is the correct behaviour.

LUMO can record both intra- and inter-tile channels across a cap. As such, we see no error in the data files nor the converted SNIRF files.

labteng commented 10 months ago

For instance, when two tiles are placed in separate L and R temporal locations, Homer 3 will present inter-channels connecting the two tiles. This means that a source will be linked to every detector on both tiles,

This is the correct behaviour.

LUMO can record both intra- and inter-tile channels across a cap. As such, we see no error in the data files nor the converted SNIRF files.

I just got replied from Gowerlab support team. They confirmed that source can be seen by all the detectors but only closely enough will form useful channels. image In addition, when selecting two tiles on LumoX GUI, it would not indicate any inter channels between those two tiles.

image

I am wondering why there is divergence between Homer and LumoX? So which one we should refer to? Thank you.

I will also forward this issue to the research support.

@samuelpowell

samuelpowell commented 10 months ago

I am closing this issue as it does not appear to relate to lumomat.

labteng commented 10 months ago

Is it possible for lumomat to include the intra tiles channels only in .snirf? @samuelpowell

samuelpowell commented 10 months ago

No this is not supported as inter-tile channels are required in most conceivable applications.