Skip to content
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

Should PyFluent clean up Fluent .trn files? #2001

Closed
seanpearsonuk opened this issue Sep 21, 2023 Discussed in #2000 · 2 comments · Fixed by #3488
Closed

Should PyFluent clean up Fluent .trn files? #2001

seanpearsonuk opened this issue Sep 21, 2023 Discussed in #2000 · 2 comments · Fixed by #3488
Assignees
Labels
enhancement New feature or request. Feature work invariably requires testing-team involvement question Further information is requested

Comments

@seanpearsonuk
Copy link
Collaborator

Discussed in #2000

Originally posted by raph-luc July 6, 2023
Minor issue/idea after talking with Adam. In addition to cleaning up the Fluent process itself, we could, maybe by default, also clean up the Fluent .trn files as they are often not wanted

@seanpearsonuk seanpearsonuk added the question Further information is requested label Sep 21, 2023
@seanpearsonuk seanpearsonuk added enhancement New feature or request. Feature work invariably requires testing-team involvement and removed enhancement New feature or request. Feature work invariably requires testing-team involvement labels Sep 21, 2023
@seanpearsonuk
Copy link
Collaborator Author

Heck, sorry, you now need to go to the discussion to find the full thread.

@seanpearsonuk
Copy link
Collaborator Author

seanpearsonuk commented Nov 14, 2024

@hpohekar This is the key comment

Comment by @mkundu1 in the discussion #2000:

@seanpearsonuk One thing is that the automatic transcript in Fluent is not relevant for PyFluent users, so that doesn't have to be exposed in PyFluent API. We can have a module-level global for it which will be less prominent.

Similar treatment was done for pyfluent.SHOW_MESH_AFTER_CASE_READ.

@seanpearsonuk seanpearsonuk added the enhancement New feature or request. Feature work invariably requires testing-team involvement label Nov 14, 2024
@seanpearsonuk seanpearsonuk moved this to 2024 Q4 Oct - Dec in PyFluent Public Roadmap Nov 14, 2024
@mkundu1 mkundu1 linked a pull request Nov 15, 2024 that will close this issue
@hpohekar hpohekar assigned mkundu1 and unassigned hpohekar Nov 15, 2024
@github-project-automation github-project-automation bot moved this from 2024 Q4 Oct - Dec to 2025 Q3 Jul - Sep in PyFluent Public Roadmap Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request. Feature work invariably requires testing-team involvement question Further information is requested
Projects
Status: 2025 Q3 Jul - Sep
Development

Successfully merging a pull request may close this issue.

3 participants