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

Add server license option to switch between read only and read/write #874

Open
dkowollik opened this issue Sep 9, 2024 · 1 comment
Open
Labels
aps Anything related to Ansys Prime Server enhancement New features or code improvements

Comments

@dkowollik
Copy link

📝 Description of the feature

It would be great to have a similar license behaviour comparable to the Workbench, where the Services like Mechanical and SpaceClaim can change from read/write mode to read only and back. This is extremely useful to get rid of the launch and exit overhead that is included in each service. Parameter variations with a workflow of four to five pyansys packages need too many preppost licenses in parallel.

💡 Steps for implementing the feature

No response

🔗 Useful links and references

No response

@dkowollik dkowollik added the enhancement New features or code improvements label Sep 9, 2024
@dkowollik
Copy link
Author

A read only option might not be necessary, if you organize the check_in and check_out of licenses differently. A method license_check_in() and license_check_out() added to the prime client object would be sufficient. Python packages like PyACP use check in and check out only during an update call. I can understand, if you think that this is too much overhead. For me it would be sufficient to be able to call license_check_in() at the end of an update loop, before I continue the update with a different pyansys service.

@waltersma waltersma added the aps Anything related to Ansys Prime Server label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aps Anything related to Ansys Prime Server enhancement New features or code improvements
Projects
None yet
Development

No branches or pull requests

2 participants