Continued issue with fNIRSFilterPipeline about preprocessingfnirs HOT 2 CLOSED

On Tue, Apr 28, 2020 at 3:55 PM mcooperwhite ***@***.***> wrote: Thanks for fixing the issue with BaselineVolatilityCorrection! I continue to get an error that prevents preprocessing from hmrIntensity2Conc when it is called up in fNIRSFilterPipeline. I found that removing d(:,SD.MeasListAct==0)=NaN; and adding dconverted(:,SD.MeasListAct==0)=NaN; after hmrIntensity2Conc gets applied fixed the problem, and then I was able to run. I'm not sure why this error has occurred for me but not others. My reasoning behind why it might not work is that hmrInensity2Conc cannot accept NaN values. So by introducing NaN values into d too early on (and then d becomes dfiltered), they may be interfering with the ability of hmrInensity2Conc to run. Just want to double check that it's reasonable to move it, without interfering with any preprocessing steps, as I'm not entirely certain about how it works, and don't know if certain calculations look across channels (in which case values that will not be used should not be included). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEG7IDFDTCOHK6JTFLIV5W3RO5NDNANCNFSM4MTHRR3A> .