Warning: Can't synchronize with repository "(default)" (/disks/svn_mcs/repos/neams-ibm does not appear to be a Subversion repository.). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of sharp


Ignore:
Timestamp:
01/31/09 13:14:21 (13 years ago)
Author:
bernhold
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • sharp

    v1 v2  
    99 * http://www.mcs.anl.gov/~tautges/downloads/sharp_moab_shortcourse.pdf 
    1010 * http://trac.mcs.anl.gov/projects/ITAPS/wiki/MOAB 
     11 * CGM (geometry), http://trac.mcs.anl.gov/projects/ITAPS/wiki/CGM 
     12 * a SHARP paper, http://scholar.google.com/scholar?hl=en&client=firefox-a&rls=org.mozilla:en-US:official&hs=boP&q=Simulation-based%20High-efficiency%20Reactor%20Prototyping&um=1&ie=UTF-8&sa=N&tab=ws 
     13 * a MOAB paper, http://www.google.com/search?q=Timothy+J.+Tautges%2C+MOAB-SD%3A+Integrated+Structured+and+Unstructured+Mesh+Representation%2C+Engineering+With+Computers%2C+20%3A286-293+(2004)&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a 
    1114 
     15 
     16An explanation of the relationship between SHARP and various other projects/packages: 
     17 
     18John H Magerlein wrote: 
     19>  
     20> Tim, 
     21> I'm afraid that I'm really confused about a number of things after  
     22> reading the information you send yesterday and various links on the web.  
     23> Below is a series of questions which I'd like to discuss with you. I'd  
     24> really appreciate it if we can talk by phone on Thursday or you can  
     25> reply by email. Thanks. 
     26>  
     27>     * I don't understand the relationship among ITAPS, CGM, MOAB, CUBIT, 
     28>       and SHARP. Can you explain further? 
     29 
     30Sure. 
     31 
     32ITAPS is an effort to define common interfaces to geometry, mesh, and a  
     33few other types of data, and to develop mesh-related tools based on  
     34those interfaces. 
     35 
     36CGM and MOAB are my implementations of the iGeom and iMesh interfaces,  
     37respectively.  There are a few other implementations of iMesh, but for  
     38the most part none of iGeom. 
     39 
     40CUBIT is a mesh generation toolkit developed at Sandia National Labs.  
     41CUBIT uses CGM as its geometry capability (or, to be more precise, CGM  
     42was taken out of cubit then re-integrated in component form).  CUBIT is  
     43not open source, but is available to those working under government  
     44contract (see www.cubit.sandia.gov for more details).  I am developing a  
     45set of smaller, more component-based meshing tools, to be used in  
     46conjunction with or separately from cubit.  This effort is in the very  
     47early stages. 
     48 
     49SHARP is a project at ANL to do coupled reactor simulation.  The  
     50approach we're taking is to access geometry and mesh data through common  
     51interfaces, i.e. using the ITAPS interfaces.  Infrastructure tools like  
     52mapping solution results between meshes are also being implemented based  
     53on these interfaces (though in a few cases we have to go all the way  
     54down to MOAB directly).  The so-called "SHARP framework" includes CGM,  
     55MOAB, and these infrastructure tools.  I say so-called because it's  
     56really more of a collection rather than a monolith. 
     57 
     58>     * If I understand what you said and what I read on the ITAPS web 
     59>       site, ITAPS is merely an interface specification. Am I correct 
     60>       that there is no code implementing ITAPS other than CGM and MOAB? 
     61>       However in your notes, you say things such as "Use ITAPS from 
     62>       Fortran & where memory isn't important, otherwise MOAB". I thus 
     63>       infer that there is some other implementation of ITAPS. Can you 
     64>       clarify? 
     65 
     66First, there are other implementations of iMesh (the ITAPS mesh  
     67interface), but none of iGeom (specifically, there is one other one, but  
     68it's based entirely on a mesh representation, at least as released in  
     69the public domain). 
     70 
     71When I talk about using ITAPS vs. MOAB, I'm referring to the interface  
     72functions. 
     73 
     74>     * You say that MOAB only interfaces with C++. Is it not correct than 
     75>       many of the codes of interest are in Fortran or C? If so, how will 
     76>       we be able to use those codes with MOAB? 
     77 
     78Through iMesh, the ITAPS mesh interface.  Most of the functionality  
     79available in MOAB can be accessed through iMesh, and for what can't be,  
     80we'll have to construct specific wrapper functions.  In my experience  
     81with SHARP, much of the driver code is in C++, which then calls into C-  
     82or Fortran-based physics modules, so this usually isn't an issue. 
     83 
     84>     * I can find almost nothing about SHARP. Your tutorial "SHARP 
     85>       Framework Tutorial" seems to discuss ITAPS and MOAB at some 
     86>       length, but it says little about SHARP. Is there some 
     87>       documentation or description? 
     88 
     89No documentation at the high level yet (we're working on the code first  
     90:) ).  There are two physics codes, UNIC (neutronics) and Nek (TH),  
     91which are being developed as both standalone codes and modules which can 
     92be called from a coupled code.  It's the coupled code which we refer to  
     93as sharp.  This is in very early stages of development compared to Nek  
     94and UNIC.  Nek is available as open source, UNIC is not (since it  
     95probably has export control restrictions). 
     96 
     97>     * If I want to download some code and try it out, how should I 
     98>       begin? Is there any type of user interface and example data which 
     99>       I could use to get some idea that it is working? 
     100>  
     101 
     102You could download CGM and MOAB and build each of them.  They don't have  
     103UI's, since they're mostly libraries.  There are test applications for  
     104both included with the distributions.  You should probably start with  
     105MOAB, since CGM will require a 3rd party package (OpenCascade) which  
     106isn't small.  MOAB includes some test meshes which you could use to test  
     107small programs you wrote.  MOAB's mbconvert utility can be used to  
     108convert these meshes to the vtk format, which can be read by Visit,  
     109Paraview, and other viz tools.