[Imstk-developers] high-speed thread in iMSTK

[Sreekanth Arikatla]

Hi Zhaohui,
                  I believe what Andinet asked was not the physical size of
the scene in space! Can you give us an estimated size of the problem i.e.,
the degree of freedom that the final application would need?

We already have SCCD <http://gamma.cs.unc.edu/SELFCD/> interfaced with
iMSTK. If your continuous collision implementation is different and
provides some advantages, it would be great to have it part of iMSTK.



On Thu, Jun 8, 2017 at 6:37 PM, Andinet Enquobahrie <
andinet.enqu at kitware.com> wrote:

>
> Can you contribute your continuous collision detection algorithm to imstk ?
>
>
> Sent from my iPhone
>
> On Jun 8, 2017, at 6:09 PM, Zhaohui Xia <xiaz at rpi.edu> wrote:
>
> 1. 24inch
> 2. PBD
> 3. I write collision algorithm by myself since I need do continuous
> collision detection not only static collision detection.
>
>
> On Jun 8, 2017 5:38 PM, "Andinet Enquobahrie" <andinet.enqu at kitware.com>
> wrote:
>
> Can you tell you us a little bit more about the individual components you
> are using for your VESS simulator?
>
> 1) How large is your scene ?
>
> 2) What physics simulation formulation are you using? co-rotational FEM,
> PBM, FEM, etc...
>
> 3) What Collision Detection algorithm?
>
> On Thu, Jun 8, 2017 at 5:29 PM, Zhaohui Xia <unihui at gmail.com> wrote:
>
>> I am working on VESS simulator. Actually, sometimes some issue will be
>> fixed in the next update of iMSTK.
>>
>> The version I used is not the latest, so I will check it and report when
>> I use the latest version.
>>
>>
>>
>> Currently, I meet some problem related to high-speed thread of haptic
>> device and transformation matrix of geometry. But I am not sure whether my
>> understand is correct, so I want to discuss with group to make clear. As
>> Nick’s advice, I will try to create a subclass for haptic device thread to
>> check whether it can meet my requirement.
>>
>> Thanks,
>>
>> Zhaohui
>>
>> *From:* Andinet Enquobahrie [mailto:andinet.enqu at kitware.com]
>> *Sent:* 2017年6月8日 16:59
>> *To:* Zhaohui Xia <unihui at gmail.com>; Alexis Girault <
>> alexis.girault at kitware.com>; Sreekanth Arikatla <
>> sreekanth.arikatla at kitware.com>; Milef, Nicholas Boris <milefn at rpi.edu>
>> *Subject:* Re: high-speed thread in iMSTK
>>
>>
>>
>> Zhaohui,
>>
>>
>>
>> Great to hear you are well familiar with iMSTK now.
>>
>>
>>
>> I am sure Alexis, Sreekanth and NIck would love to hear your feedback on
>> the code.
>>
>>
>>
>> What application are you developing right now? and what are the issues
>> you have observed?
>>
>>
>>
>> Andinet
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Jun 8, 2017 at 3:40 PM, Zhaohui Xia <unihui at gmail.com> wrote:
>>
>> Hi Andinet,
>>
>>
>>
>> Can I take part in code session meeting for iMSTK? Now I think I am very
>> familiar with iMSTK, it is really robust and powerful. I like it very much.
>>
>> But there might be some small issues, I want to communicate with group to
>> reduce the gap.
>>
>>
>>
>> Thanks,
>>
>> Zhaohui
>>
>>
>>
>>
>>
>> --
>>
>> Andinet Enquobahrie, Ph.D., MBA
>> Director of Medical Computing
>> Kitware, Inc.
>>
>> http://www.kitware.com
>>
>> (919) 969-6990 x311 <%28919%29%20969-6990%20x311>
>>
>>
>>
>>
>>
>
>
>
> --
> Andinet Enquobahrie, Ph.D., MBA
> Director of Medical Computing
> Kitware, Inc.
>
> http://www.kitware.com
> (919) 969-6990 x311 <%28919%29%20969-6990%20x311>
>
>
>
>
>


-- 
Sreekanth Arikatla, Ph.D.,
Senior R&D Engineer,
Kitware, Inc. <http://www.kitware.com>, Carrboro, NC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170608/93fa67f2/attachment-0001.html>