setup for fluent

[hpohekar]

No description provided.

[dnwillia-work]

It's not entirely clear to me what this is for.

[hpohekar]

It's not entirely clear to me what this is for.

We want to use meshing, workflow, solver, PartManagement,, PMFileManagement and preferences as global PyConsole objects while executing python journal. To get this to work seamlessly in PyFluent, we have implemented setup_for_fluent.

[dnwillia-work]

It's not entirely clear to me what this is for.

We want to use meshing, workflow, solver, PartManagement,, PMFileManagement and preferences as global PyConsole objects while executing python journal. To get this to work seamlessly in PyFluent, we have implemented setup_for_fluent.

So, that you don't need to type session.solver.<service>.x.y.z and you can instead type <service>.x.y.z?

If so, I'm confused. The thing is that these objects are specific to a session right.

[hpohekar]

It's not entirely clear to me what this is for.

We want to use meshing, workflow, solver, PartManagement,, PMFileManagement and preferences as global PyConsole objects while executing python journal. To get this to work seamlessly in PyFluent, we have implemented setup_for_fluent.

So, that you don't need to type session.solver.<service>.x.y.z and you can instead type <service>.x.y.z?

If so, I'm confused. The thing is that these objects are specific to a session right.

You're right, just one change, we don't need to type session.solver.<service>.x.y.z, we can type solver.<service>.x.y.z, meshing.<service>.x.y.z, workflow.<service>.x.y.z, preferences.<service>.x.y.z etc in python journal.

[seanpearsonuk]

@hpohekar based on recent discussions, we need to add tui to the globally exposed meshing object. We can discuss this.

cc: @mkundu1

[dnwillia-work]

It's not entirely clear to me what this is for.

We want to use meshing, workflow, solver, PartManagement,, PMFileManagement and preferences as global PyConsole objects while executing python journal. To get this to work seamlessly in PyFluent, we have implemented setup_for_fluent.

So, that you don't need to type session.solver.<service>.x.y.z and you can instead type <service>.x.y.z?
If so, I'm confused. The thing is that these objects are specific to a session right.

You're right, just one change, we don't need to type session.solver.<service>.x.y.z, we can type solver.<service>.x.y.z, meshing.<service>.x.y.z, workflow.<service>.x.y.z, preferences.<service>.x.y.z etc in python journal.

Which means this is useful in the scenario where you want to interact with a single Fluent session right?

[hpohekar]

It's not entirely clear to me what this is for.

We want to use meshing, workflow, solver, PartManagement,, PMFileManagement and preferences as global PyConsole objects while executing python journal. To get this to work seamlessly in PyFluent, we have implemented setup_for_fluent.

So, that you don't need to type session.solver.<service>.x.y.z and you can instead type <service>.x.y.z?
If so, I'm confused. The thing is that these objects are specific to a session right.

You're right, just one change, we don't need to type session.solver.<service>.x.y.z, we can type solver.<service>.x.y.z, meshing.<service>.x.y.z, workflow.<service>.x.y.z, preferences.<service>.x.y.z etc in python journal.

Which means this is useful in the scenario where you want to interact with a single Fluent session right?

Yes, right, it will be depend on whether the session is mode=meshing or mode=solver.

[hpohekar]

@hpohekar based on recent discussions, we need to add tui to the globally exposed meshing object. We can discuss this.

cc: @mkundu1

Yes, sure.