[Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED)
Su, Simon M CTR USARMY ARL (US)
simon.m.su.ctr at mail.mil
Tue Aug 5 09:11:44 EDT 2014
Classification: UNCLASSIFIED
Caveats: NONE
Hi Andy,
Thanks for your insight.... I will know more on the complexity when I dig
more into it.
Thanks
-simon
-----Original Message-----
From: Andy Bauer [mailto:andy.bauer at kitware.com]
Sent: Monday, August 04, 2014 9:14 PM
To: tim gallagher
Cc: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org
Subject: Re: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED)
Hi Simon,
It can be a fairly wide range to do that. I was able to do it for Chris Kees'
Proteus code in an hour. But he already had VTK data structures created for
his own internal in situ stuff and it was with Python so even compilation
issues were very easy (also, we sat down together to do it so all of the
knowledge was there). I generally try to allocate two weeks to do that
assuming that I'll do a decent amount of the work figuring out the simulation
code on my own as well as waiting some for answers to emails. If the code
isn't "cmakeified" then it also adds a bit of time to it as well. If you're
not that familiar with the simulation code I suggest focusing on the part of
the code that writes out the simulation information (grid and fields) to
files. That generally has all of the information you need to know in order to
create the VTK data structures to represent their data structures.
Regards,
Andy
On Mon, Aug 4, 2014 at 4:41 PM, Tim Gallagher <tim.gallagher at gatech.edu>
wrote:
Hi Simon,
I've gone through the process myself and it actually was not that painful,
but how long it takes will depend on how familiar you are with VTK already.
It's almost trivial if your code's data structures already use VTK. If they
don't, then it's a matter of translating your data into the VTK data
structures which isn't too bad in Python.
Our code is in Fortran and is a parallel, finite volume, structured,
multi-block code. So in some ways it's a bit easier to define the data
structures in VTK as they are structured and I don't need to worry about
connectivity. I wrote the wrappers and interface code in less than a week with
no prior knowledge of VTK but a very strong desire to make it work :) This was
a few years back when the documentation on Catalyst wasn't very mature so it
was probably harder than it would have been now.
I can't be any more specific or give you advice on how long it will take with
your code, but it was much easier than I expected it to be when I did it.
Tim
----- Original Message -----
From: "Simon M CTR USARMY ARL Su (US)" <simon.m.su.ctr at mail.mil>
To: paraview at paraview.org
Sent: Monday, August 4, 2014 4:29:52 PM
Subject: [Paraview] ParaView + Catalyst - effort estimation (UNCLASSIFIED)
Classification: UNCLASSIFIED
Caveats: NONE
Hello,
From a tutorial I attended on ParaView + Catalyst, I sort of get the idea of
all the parts involved. However, from effort point of view, on an average
case, how many man hours would be estimated to develop a Catalyst Bridge and
get it to work in ParaView for a homegrown discrete element method code
written in python with some functionality in wrapped fortran, but the data
needed for visualization is exposed to python? Just a ballpark guess
(min/max would be nice). I want to know how big of a project I am getting
myself into... :)
Thanks
-simon
Classification: UNCLASSIFIED
Caveats: NONE
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
Classification: UNCLASSIFIED
Caveats: NONE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 9990 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140805/83d0e383/attachment.bin>
More information about the ParaView
mailing list