| <!DOCTYPEHTMLPUBLIC"-<html><HEAD><LINKHREF="doxygen.css"REL="stylesheet"TYPE="text/css"></HEAD><BODYBGCOLOR="#d4ebf9"><IMGSRC="../Images/tBird2D.gif"WIDTH=100ALIGN="LEFT"/><br><br><br><br><br><h1> Recent additions</h1><tableborder="4"width="100%"><tr><td><b> Feature</b></td><td><b> Motivation</b></td><td><b> Status</b></td></tr><tr><td> Expressions defined on regions</td><td> Multi material problems</td><td> Has passed simple tests</td></tr><tr><td> High level nonlinear solver objects</td><td> Nonlinear problems</td><td> Has passed fairly serious tests Needs better user interface for parameter input Newton and Picard solvers have been implemented so far</td></tr><tr><td> Parameter expression objects</td><td> Design parameters in optimization continuation parameters in nonlinear solves</td><td> Has passed simple tests Single and listed parameters have been implemented For problems with a moderate I d like to have a vector of parameters to avoid working with a large symbolic list at the expression level This needs to be designed</td></tr></table><h1> Cool features to add</h1><tableborder="4"width="100%"><tr><td><b> Feature</b></td><td><b> Motivation</b></td><td><b> Dependencies</b></td><td><b> Work level</b></td><td><b> Status</b></td></tr><tr><td> Non affine quad and brick cells</td><td> Support for exodus files based on fastq and cubit meshes</td><td> None</td><td> Moderate</td><td> Started The major bottleneck is the need for to modify the WorkSet code to handle non affine cells</td></tr><tr><td> autoconf</td><td> Conform to standard configuration procedure</td><td> None</td><td> Low</td><td> Not begun</td></tr><tr><td> symmetric quad rules for tets</td><td> performance</td><td> None</td><td> Very low</td><td> waiting to be done</td></tr><tr><td> symmetric essential BCs</td><td> Allows use of CG Simplifies formulation of eigenvalue problems</td><td> None</td><td> Moderate</td><td> In design phase</td></tr><tr><td> Eigenvalue problems</td><td> Model vibrational problems</td><td> Symmetric BCs</td><td> Moderate</td><td> Not begun</td></tr><tr><td> Interface to rSQP</td><td> Optimization</td><td> None</td><td> Low</td><td> Started Roscoe and I need to be careful about coordination of our smart pointers and memory but it s otherwise straightforward as long as we both use Petra</td></tr><tr><td> Interface to O3D</td><td> Optimization</td><td> None</td><td> Moderate</td><td> In design phase HCL needs some row access operators</td></tr><tr><td> Interface to Opt</td><td> Optimization</td><td> None</td><td> Moderate</td><td> Need compatibility with Omar and George</td><td> None</td><td> Unknown</td><td> Not begun</td></tr><tr><td> Interface to SUNDIALS</td><td> Access to time access to checkpointing code for adjoint problems</td><td> None</td><td> Unknown</td><td> Not begun</td></tr><tr><td> Exodus mesh reader</td><td> Sandia real world problems</td><td> Needs non affine quads and bricks</td><td> but moderate dependencies</td><td> Waiting for dependencies</td></tr><tr><td> Expression objects for functionals</td><td> Symbolic objective functions in optimization</td><td> None</td><td> Moderate</td><td> In design phase</td></tr><tr><td> Solving for unmeshed unknowns</td><td> Solving for unmeshed design parameters in optimization every unknown and test function is assumed to be represented on a finite element mesh There are ParameterExpr objects for design parameters
|
|
