Too many trigger markers prevents loading data into Homer3

[Asger L. Christiansen]

Hi everyone,

We're attempting to load our data into Homer3 (collected using a NIRSport2 device, 32x32 setup). After choosing a data folder (Using Choose Group), we get an error called 'index exceeds matrix dimensions', followed by a host of other errors.

We were able to determine that this occurs because our data files have more than 99 event markers, which Homer3 is not able to handle. Is there a way to modify the source code so more than 100 markers are accepted?

Thanks,

Asger L. Christiansen

[Boas, David]

Asger,

How did you come to this conclusion that Homer3 can’t handle more than 99 event marks?

We are checking the code… but this seems highly unlikely.

There is probably some other issue causing this error.

David

--
You received this message because you are subscribed to the Google Groups "Homer-fNIRS and AtlasViewer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to homer-fnirs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/homer-fnirs/16d5f297-ae00-4b63-aa53-542b5560051ao%40googlegroups.com.

[Asger L. Christiansen]

David,

Thank you very much for your reply. I should correct my earlier statement (apologies for the confusion): We are not 100% certain this is the issue. We initially contacted the support team at NIRx about the issue, and they identified what I wrote earlier as a likely issue, and redirected us here. It is certainly possible that we've misidentified the problem.

I gave the error messages another look, and the issue appears to occur right after colors are loaded from a file called SDGcolors.csv. I've included screenshots of the matlab output that we get when the issue occurs.

We've been unable to find examples of others having this issue. Any help is greatly appreciated.

-Asger

mandag den 9. november 2020 kl. 15.26.33 UTC+1 skrev Boas, David:

Asger,

How did you come to this conclusion that Homer3 can’t handle more than 99 event marks?

We are checking the code… but this seems highly unlikely.

There is probably some other issue causing this error.

David

 

 

From: <homer...@googlegroups.com> on behalf of "Asger L. Christiansen" <A.Lak...@gmail.com>
Reply-To: "homer...@googlegroups.com" <homer...@googlegroups.com>
Date: Monday, November 9, 2020 at 7:03 AM
To: Homer-fNIRS and AtlasViewer Community <homer...@googlegroups.com>
Subject: Too many trigger markers prevents loading data into Homer3

 

Hi everyone,

We're attempting to load our data into Homer3 (collected using a NIRSport2 device, 32x32 setup). After choosing a data folder (Using Choose Group), we get an error called 'index exceeds matrix dimensions', followed by a host of other errors.

We were able to determine that this occurs because our data files have more than 99 event markers, which Homer3 is not able to handle. Is there a way to modify the source code so more than 100 markers are accepted?

Thanks,

Asger L. Christiansen

--
You received this message because you are subscribed to the Google Groups "Homer-fNIRS and AtlasViewer Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to homer...@googlegroups.com.

[Boas, David]

This is a different issue than what you suggested.

Stephen or Jay should be able to figure this out from the error message you provided.

More soon.

To unsubscribe from this group and stop receiving emails from it, send an email to homer-fnirs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/homer-fnirs/470aef38-b19f-4388-8e3a-ae17929d75a2o%40googlegroups.com.

[Asger L. Christiansen]

David,

Thanks for working on this issue! I plan to use Homer3 to process and analyze our pilot data for my thesis, which is due in January. Could you please give me an estimate of how long it might take for the problem to be solved? Is there any more information I should provide?

-Asger

mandag den 9. november 2020 kl. 20.46.00 UTC+1 skrev Boas, David:

This is a different issue than what you suggested.

Stephen or Jay should be able to figure this out from the error message you provided.

More soon.

 

 

From: <homer...@googlegroups.com> on behalf of "Asger L. Christiansen" <A.Lak...@gmail.com>

To view this discussion on the web visit https://groups.google.com/d/msgid/homer-fnirs/470aef38-b19f-4388-8e3a-ae17929d75a2o%40googlegroups.com.