You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
📝 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
The text was updated successfully, but these errors were encountered: