As a sidenote, I’m using individual empty-room recordings to compute the Noise covariance for each subject and the head models were created from the individual subject’s anatomy using the options specified in the tutorial.
Any ideas would be greatly appreciated and thank you for your time!
Please describe what you mean with "empty power maps.
Do you mean: empty variables in the files, blank cortex surface when you open the files for display?
By "power maps" do you designate the minimum norm source maps, or the PSD values computed from these source maps?
Please post screen captures illustrating your request.
When I examine the source localized files in Matlab I can see that the Time and ImageGridAmp fields are empty (as if they were never converted to continuous files?)
Before reading the tutorial you are referring to, we recommend you start by following all the introduction tutorials (section "Get started") using the example dataset provided: https://neuroimage.usc.edu/brainstorm/Tutorials
Thank you for your quick response. Yes, I was referring to the blank cortical surface when I open the PSD files computed from the source maps. At first I thought that this may have been related to the colormap thresholds but when I tried to adjust the thresholds I saw that the min and max values were 0.
Hi Katie,
I reproduced the problem. Indeed I get this in the Matlab window when computing the PSD:
BST> Skipping window #1 because it contains a bad segment.
BST> Warning: Frequency band "delta" is empty.
BST> Warning: Frequency band "theta" is empty.
BST> Warning: Frequency band "alpha" is empty.
BST> Warning: Frequency band "beta" is empty.
BST> Warning: Frequency band "gamma1" is empty.
BST> Warning: Frequency band "gamma2" is empty.
BST> All values are null. Please check your input file.
BST> All values are null. Please check your input file.
Using the "physical" units for the PSD worked though:
So looks like the bug is with the "Normalized" units option in the PSD, which I introduced at the same time as the physical units. In this case, the frequencies are also normalized: going from 0 to 1. So the frequency bands would have to also be normalized accordingly and it's not currently the case...
So while this is a bug that we'll need to fix (possibly by removing that option altogether). I would recommend using Physical units for now.
P.S. I saw you used the 2016 version of compute sources, probably because it's older data that had already been processed, or comparing with previous results. If possible though, you may want to use the latest version.