Ehsan Bakhtiari When dealing with Named Selections in ANSYS Meshing scripts, encountering the error 'NoneType' object has no attribute 'Location' is common, especially when automating tasks. This error typically arises because the script attempts to access or assign a Location property to a Named Selection object that doesn’t exist or hasn't been properly initialized.

Imagine you are preparing a lunchbox for a child every morning. You create sections (like compartments) to separate fruits, sandwiches, and snacks. Now, let's say you labeled each compartment as 'Fruit', 'Sandwich', and 'Snack'. If you forget to create one of these sections, but still try to assign food to it, you’ll face an error—similar to how ANSYS reports that the 'Named Selection' doesn't have a Location attribute.

Key Problem:

In your script, the following line is causing the issue:

named_selection_1 = DataModel.GetObjectById(29)

Here, the script is looking for an object with ID 29, but if it doesn’t exist, the variable named_selection_1 becomes None. When the next line tries to assign a location to this undefined object:

named_selection_1.Location = selection

the error occurs because None doesn’t have a Location attribute.

Solution: Step-by-Step Fix

Think of this process like setting up compartments in a lunchbox. First, you check if the compartment exists. If it doesn’t, you create it, label it, and then place food inside. Similarly, in ANSYS, you first verify if the Named Selection exists, create it if needed, assign it a label, and finally associate it with the desired geometry.

This structured approach prevents errors and ensures the automation script works smoothly for any geometry updates in your project.

Qamar Ul Islam Thank you, Qamar for your response. It meant a lot to me.

Yes, the problem was generating the location spot in the meshing tree.

It is interesting that everything looks fine if I clear the meshing project data and reopen it. Even if I've changed the name of the Named_selection, it works fine when running the script. But, resetting the meshing in the workbench causes this error.

As you said, the key is the Model.AddNamedSelection() command. I've checked the code generated using the record button. I realized that there is always an "Add" line in the beginning for many other commands, like sizing and inflation. I don't know why Meshing does not write this line automatically for Named Selections, so we have to add it manually.

Anyway, thank you so much for your time and your detailed response.

Wish you all the best