[Webnucleo] ANNOUNCE: libnucnet 0.4 is now publicly available

[Announce list for the Webnucleo project.]

Release 0.4 of Webnucleo's libnucnet Module is now publicly available.
Libnucnet is a library of codes for storing and managing nuclear reaction
networks (that is, collections of nuclei and reactions among them). The
module is available at this location:

http://www.webnucleo.org/home/modules/libnucnet/0.4

  Below are the recent updates to the module:

        New:

        Two new examples demonstrate how to check that forward and reverse
reaction rates lie within specified bounds and how to run a single
zone network calculation with input thermodynamic and initial mass
fraction data from a text file.

        It is now possible for the user to specify the order in which
reactions and zones are iterated over with their iterators. The
user specifies these with user-defined compare functions that are
set and cleared with API routines. The default iteration order for
both reactions and zones is now based on their internal storage,
which the user does not define.  The default iteration
for
        reactions or zones can be considerably faster than one requiring
sorting and should be used whenever possible.

        The routines Libnucnet__Species__updatePartitionFunctionData() and
Libnucnet__Reaction__updateRateTable() now sort the input data by
temperature before storing them.

        The single zone evolution examples now use the new wn_matrix arrow
solver by default (though the user can still change to use the gsl
lu decomp routine).  This requires an upgrade to wn_matrix 0.8 or
later.  The arrow solver can run much faster than the gsl lu
decomp
        routine for large networks.

        Fix:

        The argument check for the single zone evolution example has been
fixed.

        A bug that caused the routine to compute the nuclear partition
function to crash when the species only has two partition function
points has been fixed.  The similar bug for computing reaction
rates from rate tables has also been fixed.

        Some usage statements in the example codes have been fixed or made
clearer.

        Some typos in the documentation have been fixed.