# Error running make\_forward\_solution: Head\<--\>sensor transform not found

**URL:** <https://mne.discourse.group/t/error-running-make-forward-solution-head-sensor-transform-not-found/922>\
**Category:** Mailing List Archive (read-only)\
**Tags:** list-archive\
**Created:** [November 18, 2015, 9:02pm UTC](https://mne.discourse.group/t/error-running-make-forward-solution-head-sensor-transform-not-found/922 "2015-11-18T21:02:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/mne/original/1X/85cc6bd2b69cb698a166dc6d880fb550510d0144.jpeg) [@system](https://mne.discourse.group/u/system)\
**Post date:** [November 18, 2015, 9:02pm UTC](https://mne.discourse.group/t/error-running-make-forward-solution-head-sensor-transform-not-found/922/1 "2015-11-18T21:02:36Z")

</div>

Update:

(1) Re Hari's suggestion

I tried converting the fif file to a hpts file using the C implementation:  
(from the shell)  
mne\_convert\_dig\_data --fif $SUBJECT.fif --hptsout $SUBJECT.hpts --headcoord

(from python)  
digfile\_hpts = op.join(subjects\_dir, subject, subject + '.hpts')  
montage = mne.channels.read\_montage(digfile\_hpts)  
raw = mne.io.read\_raw\_brainvision(subjects\_dir + subject + '/' + subject +  
'.vhdr',  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;montage=montage, verbose=None,  
preload=False)

This raises a new error:  
None of the sensors defined in the montage were found in the info  
structure. Check the channel names.

The channel names in the montage are of the form '0001' ... '0291', with  
duplicated '0001' ... '0064' at the end. The channel names in the raw data  
are of the form '01' ... '64'.

I noticed that the first column in the .hpts file has 'eeg' for the last 64  
rows (vs 'cardinal', 'hpi', and 'extra' for the previous ones). This first  
column isn't being used by read\_montage, but I think it is what  
distinguishes the eeg channel locations from the other digitizer info.

I could manually change the channel names in the .hpts file to '01' ...  
'64' for those rows, to match the channel names in the Brainvision file.  
Not a pretty solution, but it might work.

(2) Re Eric's comment

I'd be happy to cut down the script/files. Where should I upload files? I'm  
at Martinos, want to be sure to follow HIPAA etc.

In the meantime, I've created an issue on github linking back to this  
thread.

Thanks,  
Emily