.. -*- coding: utf-8 -*-

Project libaster
================
:creation date: 2011/03/03

Turn EDF Code_Aster into a python library for mechanical simulation using finite
elements

Version hackathon-1
-------------------

Clone the code_aster for libaster sources:: $ mkdir code_aster $ hg clone -r
code_aster_for_libaster http://hg.python-science.org/libaster/src code_aster/src

Then build with::

$ cd code_aster/src $ ./waf configure build -p

If you have troubles with 3rd party libraries::

$ ./waf configure build --disable-med --disable-hdf5 --disable-mumps
--disable-scotch --disable-petsc -p

external links: ===============

description: http://www.code-aster.org/wiki/doku.php?id=en:p03_dev:hackathon_01
forum topic: http://www.code-aster.org/forum2/viewtopic.php?id=18046 Code_Aster
development: http://www.code-aster.org/wiki/doku.php?id=en:p03_dev:start
:prevision date: 2012/10/18
:expected date: n/a

Ticket #32949 add a static check of aster script files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: open

The command file is executed with a patched environment to perform the script
check.

The good way is to perform a static check of the command file.

One may use `pylint-brain`_, yams_, traits_ ... ?

.. _`pylint-brain`: http://www.logilab.org/blogentry/100364 .. _traits:
http://code.enthought.com/projects/traits/ .. _yams:
http://www.logilab.org/project/yams

Ticket #2388 change messages texts
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

Messages in Code aster shall be reStructured Text. Generating a pdf/html report
will be easier.

Ticket #2387 change the log manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

Code_Aster use a custom log system. A better solution is to use ``logging``. By
this way it will possible to enable many more feauters (output into a file,
mail, colors, ...) which may be customized be the user.

Comments ::

  On 2012/10/17 16:36 - Unknown author wrote :
  It shall be interesting to build a new logging handler with ReST and JSon
  support with a common API.
  
  Links
  ------
  
  Logging Cookbook:
  http://docs.python.org/howto/logging-cookbook.html#logging-cookbook
  
  Logbook:
  logging sytem for Python that replaces the standard library’s logging module
  http://packages.python.org/Logbook/

Ticket #32946 make .comm file a real python file
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: in-progress

The .comm files are not real python files. The script execution is tunes by
aster. At a first time, Aster executes the comm file as a check script of
himself (by patching the command definitions). Then aster executes the script
again with the "real" commands code.

There are many problems with this approach as the script is executed twice with
2 different environments. For exemple, some huge data must be included with-in
the comm file instead of being loaded from external resources.

Many problems will be solved by this way:

- memory limitation induced by too big comm files - simplier/flexible/powerfull
parametric executions (RECAL is a problem as it requires external resources from
astk) - writing script file will be easier with autocompletion, online docs, etc
within ide like spider, eclipse, ... - make aster a library

Ticket #2350 refactor the supervisor
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

The superviser makes the link between the different parts of Code_Aster,
allowing C, Fortran, Python to communicate. It has been implemented because of
fortran77 limitations (variable name length). This limitation do not permit to
use the aster command names into the fortran code as subroutine labels. The
superviser (in C) calls fortran symbols depending of the aster commands using a
table of correspondances.

We can instead create an bindings for each fortran subroutines. Writing a new
fortran -> C -> python converter can help. One more advantage, the commands file
checking will be implicite (done by python).

Ticket #2382 Remove compilation warning
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: task
:state: open

The compilation shall be performed with ``-Wall -pedantic`` in order to be warn
by the compiler analysis. To do so, the actual warning must be solved.

Ticket #33569 Reorder sources by features
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:state: open

The code_aster code source arrangement is mostly language oriented. We shall
want a feature-oriented one.

Once done, we will be abble to split the project into different
projects/libraries.

Ticket #2398 subprocess to run shell commands in bibpyt
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

*Utilitai/System.py* embeds an ``ExecCommand`` function that use old style shell
command execution. Using **subprocess** shall be a better solution.

Ticket #2383 Use another memory manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:state: open

Jeveux is the Code_aster memory manager, use another simplest memory manager.

Version 10.3.0-0.1
------------------
:publication date: 2011/03/07
:expected date: n/a

Ticket #2338 publish a static page on libaster.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: task
:state: resolved

The libaster.org web domain shall display a static html page with a short
description and links (forge, documentation, ...)

Note: André may prefer a text browser compatible page.