Feat/enable command args for datamodel se

[prmukherj]

No description provided.

[seanpearsonuk]

@prmukherj I have restarted the CI. tuigen was failing which shouldn't be triggered by these changes.

[seanpearsonuk]

@mkundu1 @prmukherj

There seem to be two classes of errors in the 23R1 failing tests:

• mysteriously missing TUI menus. Some menus are missing in these tests, but I see them locally in PyFluent and in the Fluent TUI. Those affect meshing and solver

• settings API updates between 22R2 and 23R1 that are not reflected in these tests:
  (a) difference between {'constant': 0, 'option': 'constant or expression'} and later {'option': 'value', 'value': 0}
  (b) difference between materials.copy_database_material_by_name(...) and later materials.database.copy_by_name(...)
  for each of these I propose a test util wrapper function:
  (a) compare_constants and (b) copy_material

Are we able to check the backend version from within the test?

[seanpearsonuk]

@mkundu1 @prmukherj

There seem to be two classes of errors in the 23R1 failing tests:

• mysteriously missing TUI menus. Some menus are missing in these tests, but I see them locally in PyFluent and in the Fluent TUI. Those affect meshing and solver
• settings API updates between 22R2 and 23R1 that are not reflected in these tests:
  (a) difference between {'constant': 0, 'option': 'constant or expression'} and later {'option': 'value', 'value': 0}
  (b) difference between materials.copy_database_material_by_name(...) and later materials.database.copy_by_name(...)
  for each of these I propose a test util wrapper function:
  (a) compare_constants and (b) copy_material

Are we able to check the backend version from within the test?

I have merged some test changes so that all settings API issues are resolved. We are now down to just those TUI API issues. TUI API Issues are not reproducible locally here!
@mkundu1 @prmukherj