Is it required that the two models of the input "buildbematrix" module are closed? #2300
Replies: 8 comments 1 reply
-
|
Beta Was this translation helpful? Give feedback.
-
This BEM implementation creates a transfer function between close surfaces. All the points on both. If you want a transfer matrix to the measurement nodes, or the sensor positions, just use buildmappingmatrix to create a mapping from the 771 torso to the measurement points. Make sure that both fields have a linear basis before making the mapping matrix using convertfieldbasis. once you have the mapping matrix, just premultiply it with the BEM matrix and you will a matrix that is between the cage and the measurement points. Also, the shape is a cylinder because that was the shape of the cage used in the experiment. |
Beta Was this translation helpful? Give feedback.
-
1.About question 4 last time, I mean how to get the measurement node?(as you mentioned) |
Beta Was this translation helpful? Give feedback.
-
@jessdtate |
Beta Was this translation helpful? Give feedback.
-
The measurement nodes are just another geometry that was made to reflect the recording locations. In these data, the electrode locations were recorded with a digitizer and the triangulation was made manually. The triangulation helps with mapping and visualization. It sounds like you ware describing the process for making a transfer matrix from the heart to recording locations accurately. One more point about the full 771 torso surface: it more accurately represents the experimental setup than a closed geometry with only the recording electrodes. That's another reason we do it this way. There are many ways to obtain sensor positions in a given setup, and it mostly depends on the setting and what's available. There are some infrared cameras that can take 3D images to make torso meshes with electrode positions. There is a company called Peacs that makes software for this. Another way would be to make a geometry for the sensor positions based on the manufacture specifications and register it to the correct position. SCIRun has some tools to register the sensor once you've created it in Matlab or Python. Digitizing is another way. Or you could try to estimate the positions. I'm sure there are other ways too. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply! |
Beta Was this translation helpful? Give feedback.
-
you'll have to make the geometry for the sensor somehow (see previous comment for some ideas). You can use map3d to add points and make triangles to the 771 tank geometry, but it isn't necessary for the sensors to be a part of the tank geom if you make the mapping matrix. If the sensor positions are a part of the torso geometry, and you know the index for them, you can extract the rows of the BE matrix that correspond to the node indices and that would be your transfer matrix. This would make it so you don't need to make a geometry for the sensor positions. |
Beta Was this translation helpful? Give feedback.
-
@jessdtate @jab0707 |
Beta Was this translation helpful? Give feedback.
-
I have a few doubts when learning the example program “torso-tank-bem.srn5”.
1.Is the imported cage.fld data epicardial geometry? Why is the shape a cylinder?
2.The dimension of the transfer matrix is 771 * 602, 771 represents the number of torso surface nodes and 602 represents the number of epicardial nodes(I think). When calculating the transfer matrix, Why is epicardium mapped to the whole torso instead of epicardium mapped to the sensor position on the surface of the torso?
3.Is it required that the two models of the input "buildbematrix" module are closed?
4.How to get "tank. FLD"_ measured_ Only. fld " from "tank.fld"? Is it possible to specify or program it?
Beta Was this translation helpful? Give feedback.
All reactions