I forgot to add that you should be able to work around this by using
GetFieldData and then SetFieldData to make the mesh pointer of one field
match the pointer of the other field. IE Grab the int data and stick it
onto the vector field and then use that as sigma to suppress this
warning.
Michael
On Tue, 2008-07-29 at 13:24 -0600, Michael Callahan wrote:
This is caused by overly strict sameness criteria. The module check to
see that the mesh pointers are the same rather than checking to see if
the meshes are equivalent. It would probably be better to have an
equivalence test that makes sure the types and number of simplexes are
the same for the two meshes and then use that instead for all of these
error checks.
Michael
On Tue, 2008-07-29 at 11:43 -0600, Jeroen Stinstra wrote:
Hi Ashu,
Thanks for the bug report. I will have a look to see what is wrong
with that module.
Jeroen Stinstra
On Jul 29, 2008, at 11:39 AM, Ashu Chaturvedi wrote:
Hi,
I was wondering if you guys fixed the IntegrateCurrent module that's
in the latest svn version of SCIRun? The reason I ask is because
I'm getting the following error when I try to use it:
"ERROR: EField and Sigma Field need to have the same mesh."
It doesn't seem to make sense to me, since both the EField and Sigma
meshes appear to the same. You can see the screenshots below:
<EField.png>
<Sigmas.png>
The only difference is that the EField is a vector, while the Sigmas
are an int. Perhaps I'm not using IntegrateCurrent correctly?
Thanks in advance for your help!
--Ashu Chaturvedi
ashu@case.edu
Archive powered by MHonArc 2.6.16.