-
-
August 14, 2023 at 7:29 pm
bla92
SubscriberHello,
I am attempting to set up a ansyslmd.opt file to separate research and teaching licenses. From the license file our teaching and research licenses look identical with the exception of the "customer:xxxxxx tp:at" and "customer:xxxxxx tp:a". Which of these is the research feature and which is teaching?I want to restrict only research computers to the research licenses with full features set of the licenses (possibly reserve license). The other computers I would like to get teaching first and then when they run out any research that are available. Most of the computers will have both Electronics and Mechanical and CFD versions installed.
What would be the best way for the option file to do this?
-
August 18, 2023 at 6:16 pm
VG
SubscriberPlease look at this forum thread to check teaching and research licenses:
https://forum.ansys.com/forums/topic/how-to-check-out-a-teaching-license-vs-research-license/
To learn about options file, please folow this link:
https://optics.ansys.com/hc/en-us/articles/4403333893267-Controlling-access-to-the-license-using-the-options-file
-
August 23, 2023 at 4:05 pm
bla92
SubscriberYes I have seen this link and have taken alot from it but it doesn't help me to identify what is a research license and what is an academic license. It seems the TP:AT and TP:A are the only distinguishing differences in the license lines. Which one is which?
-
August 23, 2023 at 4:47 pm
VG
Subscribertp:at is teaching and tp:a is research
-
August 23, 2023 at 9:03 pm
bla92
SubscriberThe only issue is that this is embedded in the VENDOR_STRING which requires you to list out every feature in our license (226 features in Teaching and 226 in Research). I'm trying to figure out an easier way to separate computers getting the research licenses and those getting the teaching licenses without having a Options file that contains 452 lines of INCLUDE VENDOR_STRING. I can't use INCLUDEALL because it might give research to teaching and visa versa. Any ideas besides the listing each feature in the license file of teaching and research?
-
August 24, 2023 at 12:53 pm
George Karnos
Ansys EmployeeHello bla92,
Unfortunately, there is no way around including all lines in the options file without separating the Teaching Licenses from the Research licenses to 2 different License servers and allowing the users to specify which Server to check out licenses from
Best Regards,
George Karnos
ANSYS Inc. -
August 24, 2023 at 1:15 pm
bla92
SubscriberI was afraid you were going to say that. Thank you for the reply.
-
August 24, 2023 at 1:35 pm
bla92
SubscriberIn adding mutiple computers to the Host_Group, is there a continuation line separator like in the license file "\"?
Is there a limit to how many computers can be in a Host_Group?
Can you have groups within groups for ease of management?
-
August 24, 2023 at 1:43 pm
VG
SubscriberLines in the options file are limited to 4000 characters. The \ character is the line-continuation character.
I don't know of any limit to the number of computers can be added to HOST_GROUP.
Yes, you can have group within groups. You need to specify each group in that case.
-
August 24, 2023 at 4:29 pm
bla92
SubscriberHow would I go about having groups in groups, like this?
HOST_GROUP Group1 cmp1 cmp2 cmp3 cmp4
HOST_GROUP RSCH Group1 Group2 Group3 etc
-
August 24, 2023 at 4:36 pm
VG
SubscriberNo, you can't do it that way. You need to specify individual computer names in the HOST_GROUP. I thought you meant this by having groups in group:
HOST_GROUP Group1 cmp1 cmp2 cmp3 cmp4
HOST_GROUP Group2 cmp2 cmp3
-
August 24, 2023 at 5:52 pm
bla92
SubscriberThe idea was to make it more manageble with less INCLUDE lines since I will need a INCLUDE line for each group.
That is not really having groups withing groups as computers can be only in one HOST_GROUP. Looks like it will be one massive teaching group.
-
- You must be logged in to reply to this topic.

Boost Ansys Fluent Simulations with AWS
Computational Fluid Dynamics (CFD) helps engineers design products in which the flow of fluid components is a significant challenge. These different use cases often require large complex models to solve on a traditional workstation. Click here to join this event to learn how to leverage Ansys Fluids on the cloud, thanks to Ansys Gateway powered by AWS.

Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.

Ansys Blog
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- License Error
- Error with workbench SceneGraphChart
- Sizing on Ansys Workbench 19.2
- Workbench not opening
- Error: Exception of type ‘Ansys.Fluent.Cortex.Cortex not availableException’ was thrown
- Workbench error
- how to open DesignModeler
- FlexNet Licensing – Not running
- Problem with FlexNet Licensing
- An error occurred when the post processor attempted to load a specific result.
-
7592
-
4440
-
2953
-
1427
-
1322
© 2023 Copyright ANSYS, Inc. All rights reserved.