Problem with mhrR_GLM

[Jordan Borrell]

Hello,

I'm running into an error with the hmrR_GLM function.  The is as follows: "Function hmrR_GLM generated error at line 232: Too many input arguments."  Do you have any recommendations for solving this issue?

Thanks,

Jordan

[Stephen Tucker]

Hi Jordan,

Please provide the processing stream and options you are using (a screenshot of Options Edit GUI) and note the version of Homer you are using. 

Thanks!

Stephen

--
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/da817565-38d9-4f47-a58c-022792395e6en%40googlegroups.com.

[Jordan Borrell]

Hey Stephen,

Here's the screenshot of the processing stream and the message the is issue due to the error.  The verison is v1.28.2.  Please let me know if you need any further information.

Thanks,

Jordan

[Stephen Tucker]

Hi Jordan,

If you clear all .mat files such as groupResults.mat (File --> Reset Processing Results) and then recreate your processing stream, the problem should be resolved.

Sorry for the inconvenience! We are working on a feature that will prevent this issue in the future.

Best,

Stephen

[Stephen Tucker]

Important additional note: before creating the new processing stream, use the Edit Processing Stream GUI to reset the user function registry:

[Jordan Borrell]

Hey Stephen,

Sadly, that did not work.  However, I decided to create a new clone in a new folder to the Homer code in github.  This worked.  I think my old clone wasn't pulling updated files or wasn't connecting properly.  For example, after I made a new clone in a new folder, the "flagMotionCorrection" option under hmrR_GLM function was no longer there.  This told me that the function wasn't being updated.  Several lab mates have been having this issue, so I'll have them do the same and see if it works for them as well.  Do you have any insight into why it may not have been updating?  I would Pull the master code from github, so maybe I was doing that wrong?  Is there a better way to get the updates?

Thanks,

Jordan

[Stephen Tucker]

Thanks for your correspondence about this-- you are right: the issue arose because a recent update changed the format of UserFunctions hmrR_OD2Conc and hmrR_GLM, leading to mismatches between data created by running Homer3 and the scripts actually available.

There are currently no safeguards against this inconsistency in Homer, which is the issue we are working to resolve. You should be able to manually fix it by deleting all .mat files generated by Homer... this should have the same effect as a complete reinstallation.

Sorry this has been an issue for you and your labmates!

Stephen