Text archives Help
- From: Michael Callahan <callahan@sci.utah.edu>
- To: scirun-users@sci.utah.edu
- Subject: [SCIRUN-USERS] Re: Re: Re: Re: Re: Re: Re: IntegrateCurrent module errors in latest svn build
- Date: Tue, 29 Jul 2008 15:50:23 -0600
The sigma field should be an int field where each entry points into a
conductivity table of tensors. There is a
BioPSE/Modeling/SetConductivities module that you can use to set up the
int->tensor map.
Michael
On Tue, 2008-07-29 at 17:43 -0400, Ashu Chaturvedi wrote:
>
Michael,
>
>
Thanks for that fix. After I tried it again, I needed to make sure my
>
Sigmas were an int instead of a double, so I fed it through another
>
ConvertFieldDataType. Now the error I get within IntegrateCurrent is:
>
ERROR: No conductivity_table found in Sigmas.
>
>
Below is a screenshot of ReportFieldInfo on the Sigmas, and it appears
>
there is a lookup table in it (rows 0-831424).
>
>
>
>
So, I'm not sure if this is another bug or if I'm messing up my data
>
somewhere. Let me know if you would like for me to send, only to you,
>
a copy of my data and simplified network. Thanks,
>
>
--Ashu Chaturvedi
>
ashu@case.edu
>
>
>
>
>
On Jul 29, 2008, at 5:24 PM, Michael Callahan wrote:
>
>
> It looks like that module is incorrectly expecting a linear basis
>
> rather
>
> than a constant basis. I have just fixed it in the svn tree. You
>
> should be able to update that file and continue.
>
>
>
> Michael
>
>
>
> On Tue, 2008-07-29 at 16:20 -0400, Ashu Chaturvedi wrote:
>
>> Michael,
>
>>
>
>> Thanks for your explanation. I tried implementing what you
>
>> suggested. Take the int data and feed it through GetFieldData, then
>
>> feed its matrix output into the matrix input of SetFieldData (with
>
>> the
>
>> field input to this module being the vector field data). Now, this
>
>> field output from SetFieldData goes into the middle field input of
>
>> IntegrateCurrent (the sigmas). While it does suppress my previous
>
>> error, the new error I get within IntegrateCurrent is:
>
>> ERROR: EField isn't a TetVolField<Vector>
>
>>
>
>> Any further suggestions? Thanks,
>
>>
>
>> --Ashu Chaturvedi
>
>> ashu@case.edu
>
>>
>
>>
>
>> On Jul 29, 2008, at 3:43 PM, Michael Callahan wrote:
>
>>
>
>>> 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.