hi Cristiano
what are the dimensions of your input arrays?
Qianqian
> I use the following instructions:
>
> plane = [0 0 0;0 22 70;0 44 70]; % axial slice, z-axis oriented along
> the inferior-superior brain axis
> [aa,bb,cc] = qmeshcut(mesh.cell,mesh.node,value,plane);
> hold on,
> patch('Vertices',aa,'Faces',cc,'FaceVertexCData',bb,'FaceColor','flat');
>
> Note that the same mesh can be correctly visualized using SCIrun.
>
> Regards,
> Cristiano
>
>
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
hi Cristiano
qmeshcut only accepts nodal-based values,
i.e. the values are attached to nodes, not
elements. I just committed a change and
extended qmeshcut for element-oriented
value list. The update can be found at:
http://iso2mesh.svn.sf.net/viewvc/iso2mesh?view=revision&revision=357
When plotting, you should use
patch('Vertices',cutpos,'Faces',facedata,'CData',cutvalue,'FaceColor','flat');
please let me know if this new feature works
for you.
Qianqian
> plane = [3X3]
>
> Please let me know if you need further details.
> Thank you,
> Cristiano
Cristiano
----- "Qianqian Fang" <fa...@nmr.mgh.harvard.edu> schreef:
> --
> You received this message because you are subscribed to the Google
> Groups "iso2mesh-users" group.
> To post to this group, send email to iso2mes...@googlegroups.com.
> To unsubscribe from this group, send email to
> iso2mesh-user...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/iso2mesh-users?hl=en.
that doesn't look right. There are lots of hollow
elements, which I assume they are NaNs. You need
to find out where they come from.
You can also disable the lines by appending
'linestyle','none' in the patch command.
Do a "help qmeshcut", and double check each
of your input. It is supposed to be easy to use.
Qianqian
The information in this e-mail is intended only for the person to whom it is
Matlab command:
patch('Vertices',cutpos,'Faces',facedata)
Maybe the edges are projected in a different way with the new implementation, and this results in a weird representation of the triangles (I see a lot of 'black holes').
Actually none of the output variables contains NaNs, therefore it is difficult for me to understand what is going on, and I agree that it does not look correct.
Cristiano
hi Cristiano
I tried your script, qmeshcut works as expected.
3 minor suggestions:
1. newer qmeshcut function accepts logical expressions
for the "plane" input. In your case, you can do
[aa,bb,cc] = qmeshcut(mesh.cell,mesh.node,value,'x=0');
2. see the output x-axis is in the range of +-10^-16. These
are virtual 0 and are results of numerical errors of double
precision numbers. When you plot them, you will see rough
surfaces due to the magnified x-axis range. You can either
use set(gca,'xlim',[-1 1]) to flatten the roughness, or use
aa(find(aa<eps))=0, or aa(:,1)=0 to zerorize these tiny
elements.
3. when plotting, I used
patch('Vertices',aa,'Faces',cc,'CData',bb,'FaceColor','flat','linestyle','none');
view([1 0 0]);
notice the last property, this removes the distracting edges.
let me know if you can replicate.
Qianqian
> ...
>
> Please, let me know if you have all the necessary information.
> Cristiano
>
>
>
> ----- "Qianqian Fang"<fan...@gmail.com> schreef:
>
>> Van: "Qianqian Fang"<fan...@gmail.com>
>> Aan: "C. Micheli"<c.mi...@fcdonders.ru.nl>
>> Verzonden: Dinsdag 28 februari 2012 18:51:46
>> Onderwerp: Re: [iso2mesh-users] qmeshcut
>>
>> On 02/28/2012 12:47 PM, Micheli, C. wrote:
>>> Dear Qianqian Fang,
>>> thank you for the swift reply,
>>> I attach a version of the qmeshcut output, where the faces have no
>> color, in order to view the edges' pattern on the plane.
>>> Matlab command:
>>> patch('Vertices',cutpos,'Faces',facedata)
>>>
>>> Maybe the edges are projected in a different way with the new
>> implementation, and this results in a weird representation of the
>> triangles (I see a lot of 'black holes').
>>> Actually none of the output variables contains NaNs, therefore it is
>> difficult for me to understand what is going on, and I agree that it
>> does not look correct.
>>
>> it will be helpful if you can send me your data and
>> sample script, otherwise, it difficult to debug the problem
>> just by looking at an image.
All the best,