Improve data selection in POST-TREATMENT

[ThibautVanHoof]

The current data selection procedure is not easy to use in case of large amount of data on the disk. A filtering approach is more user friendly in such case(see the LBMHYPE prototype).

Moreover, the selection table are showed in the main window and the plot itself is below and often off screen. It is more convenient to reserve the main window to the plot and put the filtering tools in the left part of the window.

[ThibautVanHoof]

Here are some more precise requests to improve the current interface:

• The scheme names do not corresponds to the scheme name in the SCHEME tab (D1Q333 instead of D1Q333_0 or D1Q333_1)
• Same for the test case name (always 'ToroCase' while both the 'Toro1' and 'Toro2' case have been performed in the example file)
• the 'directory' column shows absolute path hardly readible. Please use path relative wrt. ./Outputs in order to reduce the length of the line; or propose another column 'RelativePath' with such a shorter relative path
• what is the purpose of the 'id' column? How can the user use the provided hexadécimal code?

[gouarin]

This will be done in the future version since we have to be able to import each test case and each lb scheme in order to have their name. But, to achieve this, pylbm-catalog should be released.

I prefer to keep the absolute path but we can add the relative path as another entry.

The id can be hidden.

[gouarin]

oh wait, I have added the v_model entry which makes what we want for the name of the test case and the lb scheme.

I will make the changes accordingly.

[gouarin]

The id was removed and the names are now correct.
see bad1d62

[ThibautVanHoof]

• the field names associated with the responses 'plot FIELDNAME' in the h5 file are always 'sol' while it must be FIELDNAME (see the snapshot where 'plot momentum' and 'plot mass' are requested and plotted using the POST TREATMENT tool).
• Could you please add the relative path as entry since the absolute path are VERY inconvenient for the analyze of large database.