Ladutenko,
It all depends on what your goal is. If you want to compute the
deflection of a beam, or want to solve a Laplace equation with a
standard discretization on a mesh you have little control over with a
solver you can't change, then deal.II is not the right tool for you.
There are many good codes that can do that -- Comsol is one, but also
Ansys and Abaqus are excellent tools if you have an application that
fits what they can do.
The point of deal.II is a different one, though: we provide the tools if
you want to (i) build a FEM solver for problems for which there are not
yet any commercial and well developed codes, or (ii) you are a method
developer and want to play with different discretizations, different
solvers, etc. If these are your goals, then you will need to be able to
control the different parts of your application yourself, and in that
case a library like deal.II is a tool much better suited to the task
than is an application like Comsol.
> Last but not least - there should be less math and more physics in the
> description, which is intuitively can be understood with applied
> scientist of engineer. Yes, same kind of equation can describe many
> effects in very different topics... But it should be much more easier to
> understand what is going on if you put Maxwell equations into deal.II
> instead of writing many math around "u" and "v" for the same problem.
I think that depends on where you come from. In the end, handwaving is
not enough in documentation but one has to be precise to explain what
exactly a function does. This being mathematical software, "intuition"
does not suffice, but formulas are frequently necessary.
All of this said, there is no question that providing adequate
documentation for a tool like deal.II is about the biggest challenge we
have with software this large. This is why there are many layers of
documentation (videos, tutorial programs, documentation modules,
class-level documentation, function-level documentation) that provide
you with different views. We have spent many years writing this
documentation (my guess is that there are 5+ man years of work in the
documentation alone) but it is a process that is never finished and
where one can always (i) write more to explain better, (ii) provide
alternative points of entry to those looking at things from a different
direction. Any concrete suggestions on how to (and, in particular help
with) improve the documentation are always welcome, and we'd be happy to
work with you if you have ideas!
Best
Wolfgang
--
------------------------------------------------------------------------
Wolfgang Bangerth email:
bang...@math.tamu.edu
www:
http://www.math.tamu.edu/~bangerth/