Skip to content

docs: Update meshing doc after switching to solver #3962

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

mkundu1
Copy link
Contributor

@mkundu1 mkundu1 commented Apr 25, 2025

Before switch:

>>> help(meshing)
Help on Meshing in module ansys.fluent.core.session_meshing object:

class Meshing(ansys.fluent.core.session_pure_meshing.PureMeshing)
 |  Meshing(fluent_connection: ansys.fluent.core.fluent_connection.FluentConnection, scheme_eval: ansys.fluent.core.services.scheme_eval.SchemeEval, file_transfer_service: typing.Any | None = None, start_transcript: bool = True, launcher_args: Optional[Dict[str, Any]] = None)
 |
 |  Encapsulates a Fluent meshing session.
 |
 |  A ``tui`` object
 |  for meshing TUI commanding, and ``meshing`` and ``workflow``
 |  objects for access to task-based meshing workflows are all
 |  exposed here. A ``switch_to_solver`` method is available
 |  in this mode.

<more lines>

After switch:

>>> help(meshing)
Help on Meshing:

<ansys.fluent.core.session_meshing.Meshing object>
    Meshing session is not usable anymore after switching to solver mode.

@mkundu1
Copy link
Contributor Author

mkundu1 commented Apr 25, 2025

@prmukherj This is what I figured from #3949 discussion. Let me know if we are looking for any different behaviour.

@github-actions github-actions bot added the documentation Documentation related (improving, adding, etc) label Apr 25, 2025
@mkundu1 mkundu1 linked an issue Apr 25, 2025 that may be closed by this pull request
@prmukherj
Copy link
Collaborator

@prmukherj This is what I figured from #3949 discussion. Let me know if we are looking for any different behaviour.

yes, @mkundu1, this was exactly our requirement. However, I had tried this as well. Don't know why it didn't work. Will test it again.

@prmukherj
Copy link
Collaborator

@prmukherj This is what I figured from #3949 discussion. Let me know if we are looking for any different behaviour.

yes, @mkundu1, this was exactly our requirement. However, I had tried this as well. Don't know why it didn't work. Will test it again.

Great, tested. Working now, no idea what was going wrong. Thank you @mkundu1.

@mkundu1 mkundu1 force-pushed the doc/switch-to-solver branch from 9ccfd66 to d7fadf1 Compare April 28, 2025 11:40
@prmukherj prmukherj enabled auto-merge (squash) April 28, 2025 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation related (improving, adding, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

help(meshing) needs modification after 'switch_to_solver'
5 participants