open TELEMAC-MASCARET The mathematically superior suite of solvers

"If you have ideas on how to improve the documentation and topics to cover on the wiki, don't hesitate making suggestions on the forum."

Was posted in the latest news about the new wiki.
So I would suggest to collect at one place within the wiki or in the forum the experiences in not so well documented areas.
That would show which areas are seen as not good documented and to have some prewritten informations that would have been useful concerning those topics.

I guess in the forum the written informations won't be as expanded as in a wiki styled environment and someone would have to move them over, but most people are already familiar with the forum.

As a first not well documented area I would point out the Sedi3d area.
And as a second I would suggest to collect a handful running examples of steering files and parameter combinations (best with some explanations but even without quite useful) for example for turbulence models with diffusion schemes (to bee seen as a how to run a simulation that is not a validation test case).
And since there are always three good things I would suggest to have some place with informations about common errors beeing explained in a few words.
(Although I don't know how to measure common)

csee

Hi !

Good initiative csee, I would add some other suggestions that are on my mind.

1/ Adding information about the turbulence models available, and their typical range of application.

2/ Adding information about numerical settings available (coefficients, solvers...), and their typical range of application.

3/ Editing a document listing up all the benchmark test cases with basic information to ease the identification of useful tests.

4/ Detailing how to couple Mascaret and T2D when this will actually be possible.

That's all for now!
Thanks for improving the website and the documentation!

Regards,
PL

and since I just had that problem again and remembered that I was stuck there before, I would like to have a place for basic stuff like, a line in the steering file may have a maximum length of ~70 (or s.th. like that) characters.

Same for the names of the files and maximum (or maybe sometimes minimum) numbers of I don't know boundaries islands or such, so that one can check these (since I assume that it's not a big deal to gather this data together).

At least for me such a look up table or text would be nice.

regards
csee