NaxToPy 1.5.6__tar.gz → 2.2.3__tar.gz

{NaxToPy-1.5.6 → naxtopy-2.2.3}/LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2023 Idaero Solutions
+Copyright (c) 2024 Idaero Solutions
 
 This freeware license agreement (“agreement”) is a legally binding contract
 between the individual who downloads the software (“you”) and the licensor,

{NaxToPy-1.5.6/src/NaxToPy.egg-info → naxtopy-2.2.3}/PKG-INFO

@@ -1,11 +1,11 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.2
 Name: NaxToPy
-Version: 1.5.6
+Version: 2.2.3
 Summary: Package for postprocessing FEM results in Python
 Home-page: https://www.idaerosolutions.com/Home/NaxToPy
 Download-URL: https://apps.microsoft.com/detail/XP9MMH0KDKGRJN?hl=en-US&gl=US
 Author-email: Idaero Solutions <manuel.sanchez@idaerosolutions.com>
-License: Copyright (c) 2023 Idaero Solutions
+License: Copyright (c) 2024 Idaero Solutions
         
         This freeware license agreement (“agreement”) is a legally binding contract
         between the individual who downloads the software (“you”) and the licensor,
@@ -118,9 +118,12 @@ Classifier: Topic :: Scientific/Engineering
 Requires-Python: >=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: pythonnet>=3.0.1
+Requires-Dist: pythonnet>=3.0.3
 Requires-Dist: numpy>=1.22.0
 Requires-Dist: setuptools>=67.8.0
+Requires-Dist: h5py>=3.12.1
+Dynamic: download-url
+Dynamic: home-page
 
 [![Idaero](https://img.shields.io/badge/powered%20by-Idaero%20Solutions-299797)](https://idaerosolutions.com)
 [![PyPi](https://img.shields.io/pypi/v/NaxToPy?color=ffd500)](https://pypi.org/project/NaxToPy/)
@@ -134,27 +137,35 @@ Requires-Dist: setuptools>=67.8.0
 # NaxToPy
 
 **NaxToPy** is the [**NaxTo**](https://apps.microsoft.com/detail/XP9MMH0KDKGRJN?hl=en-US&gl=US)
-library designed for Python, which allows reading and manipulating FEM
-analysis results files from the most common tools: Nastran (op2, xdb, h5), Abaqus (odb), Optistruct
-(h3d, op2) and Ansys (rst); and stores them in a user-friendly Python structure. Additionally, it
-can read input files from Nastran (bdf, fem) and change it contents.
+library designed for Python, allowing users to read and manipulate FEM analysis
+results files from the most common tools: Nastran (op2, xdb, h5), Abaqus (odb), Optistruct (h3d, op2),
+and Ansys (rst). It stores these results in a user-friendly Python structure. Additionally, it can
+read input files from Nastran (bdf/dat), Optistruct (fem) and Abaqus(inp) and modify their contents.
 
-It could be easily combined with other Python packages as Matplotlib or Pandas. This provides access
-to the full coding power of Python to interpret and process the results, without the need to install
-any additional software other than having NaxTo already installed (see the _Download_ and _Homepage_
-links on the left).
+It can easily be combined with other Python packages, such as Matplotlib or Pandas, providing access
+to Python's full coding power for interpreting and processing results without the need to install
+additional software beyond NaxTo (see the Download and Homepage links on the left).
 
 **NaxToPy** is a powerful tool for FEM analysis post-processing!
 
-**CAUTION:** This version is only compatible with **NaxTo 2024.0.5**.
+---------------
+
+⚠️**Warning:** To use NaxToPy, [**NaxTo**](https://apps.microsoft.com/detail/XP9MMH0KDKGRJN?hl=en-US&gl=US) must be installed.
+This version is compatible with **NaxTo 2024.3**. It is compatible with all the steps of this version (2024.3.0, 2024.3.1).
 Check in _Programs and Features_ the NaxTo version that is installed.
 
+📘**Note:** If a specific NaxTo version is installed, search the [**NaxToPy History**](https://pypi.org/project/NaxToPy/2.2.1/#history) to find which newer version is compatible with it.
+
+
 ## Installation
 
+If python is installed and `pip` is added to the PATH:
 
-If python is callable from the command line:
+`pip install NaxToPy`
+
+An alternative, if Python is callable from the command line:
 
-`py -m pip install NaxToPy`
+`python -m pip install NaxToPy`
 
 For **Visual Studio** users:
 - Open "Python Environments" window
@@ -178,7 +189,7 @@ same directory. When ever you want to use the NaxToPy package add the following
 
 If python is callable from the command line:
 
-`py -m pip install -U NaxToPy`
+`python -m pip install -U NaxToPy`
 
 For Visual Studio users:
 - Open "Python Environments" window
@@ -254,6 +265,74 @@ To see previous version see the pre-release versions in https://test.pypi.org/pr
 1. The method new_envelope_loadcase() now has the option to choose the envelope group. Which means the user can ask for
 the LoadCases that are critical or the Increment that is critical instead of the value.
 
+### v.2.0.0
+1. Changes made to align the library with updates in lower-level dependencies.
+2. New internal methods to look for the compatibility with low-level dependencies.
+3. The name of the .log is now NaxToPy_Year-Month-Day.log.
+
+### v.2.0.1
+1. The compatibility is extended to all NaxTo steps of the same version.
+2. The property N2PLoadCase.ActiveIncrement is subtitued by N2PLoadCase.ActiveN2PIncrement.
+It uses an object instaed of an int.
+3. Update of the examples of some docstrings.
+
+### v.2.1.0
+1. Reading a Natran Input File: SPC and SCP1 are now supported.
+2. Bug fix. The order in the components in new_report() does not affect now.
+3. Formula check in new_derived_loadcase(), new_enevelope_loadcase() and new_derived_component().
+4. New optional arguments if n2ptoexe() to add extra libaries, packages or files.
+
+### v.2.1.1
+1. Two new methods in N2PModelContent: load_user_coord_sys_from_csv() and set_user_coord_sys().
+Also, there is a new property for N2PElement and N2PNode: UserSystemArray. This update allow the
+user to define a different coordinate system for each element or node. To ask for the results
+in this system, the optional argument `coordsys` must be equal to `-20`.
+2. Bug fix: The checking for component and section in new_report() has been fixed. If a comma
+appeared in the component or section name, the method failed.
+
+### v.2.1.2
+1. Internal change for speeding up the read of NastranInputFiles. Now the Nastran Cards are loaded
+when they are asked and not all at once.
+2. Improvement in error handling and log writing.
+3. The function import_results_from_files() checks if the file exist. If not, it prints an error
+but the execution doesn't crash.
+
+### v.2.2.0
+1. Feat: New module for fastener analysis: N2PGetFasteners.
+2. Feat: New module for fastener analysis: N2PGetLoadFasteners. Calculates forces in joints and bypass forces.
+3. Bug fix: When a NaxToPy executable file is used on a machine where NaxTo is installed, the libraries are selected accordingly.
+4. Feat: Hidden imports are now allowed in n2ptoexe.
+5. Bug fix: Fixed the rotation of the FORCES tensor. Now the QX and QY components (transverse shears) are calculated correctly.
+6. Refactor: The dictionary and list for Cards have been replaced with a lazy dictionary and a lazy list, improving execution efficiency.
+7. Refactor: Reading the mesh from binary files is now executed in parallel by default, as this approach is more memory-safe.
+
+### v.2.2.1
+1. BugFix: The method set_increment() is fixed.
+2. BugFix: Several bugfix (not in the result accuracy) are fixed in modules N2PGetFastener and N2PGetLoadsFastener. Several optimizations are included.
+3. Feat: Now the method get_load_case() admits a list of int and a list of string and return a list of N2PLoadCase.
+4. Refactor: N2P classes use __slots__ for security and optimization.
+5. Refactor: Complete refactor of the module that loads the NaxTo libraries.
+6. BugFix: in parallel mesh load with a small mesh and lot of results.
+7. BugFix: in sequential mesh load in op2.
+
+### v.2.2.2
+1. BugFix: Solved an issue in the Nastran Cards Dictionary
+2. BugFix: Solved the Prop atribute of an N2PElement in Abaqus
+3. Feat: Now is possible to create `N2PCoord` by the user with the `new_coordinate_system()` method.
+4. Feat: Now is possible to add to `element_nodal()` a list of N2PElement to unshew only the nodes of these elements.
+5. Feat: Now is possible to ask for results in a list of elements or nodes using the optional argument `filter_list`.
+6. Feat: When the user provides a coordinate system and two vectors (v1, v2) to specify the output results, the information
+is redundant. The coordinate system will prevail.
+7. Feat: New properties supported: PBUSH, PFAST, PMASS, PELAS, PGAP, PWELD
+8. BugFix: The method get_elements_attached() is fixed so when there are MPC connectors with the same ID.
+
+### v.2.2.3
+1. Requirement: Now NaxToPy require the package [**h5py** ](https://pypi.org/project/h5py/).
+2. Feat: N2PGetLoadFastener now can use PAG method and display format.
+3. BugFix: Some bugs are solved in N2PGetFastener and N2PGetLoadFastener.
+4. Feat: N2PGetLoadFastener can export results in HDF5 format.
+5. BugFix: The filtering in the method get_result_by_LCs_Incr() in elements when results are in Corner Data is fixed.
+
 # Documentation
 
 **NaxToPy** is a package developed by Idaero Solutions© as a part of the **NaxTo** software.
@@ -262,6 +341,7 @@ NaxToPy only use three dependeces:
 - NumPy: https://numpy.org/
 - PythonNET: https://pythonnet.github.io/
 - Setuptools: https://setuptools.pypa.io/en/latest/index.html
+- HDF5: https://www.h5py.org/
 
 ## Supported Files
 
@@ -272,7 +352,9 @@ NaxToPy only use three dependeces:
 - **Ansys:** .rst, .rth(beta)
 
 ### Input files:
-- **Nastran** (bdf)
+- **Nastran** (.bdf)
+- **Optistruct** (.fem)
+- **Abaqus** (.inp)
 
 ## Initialize your model
 
@@ -333,7 +415,7 @@ loadcaseslist = model.LoadCases
 pressure_lc = model.get_load_case("pressure")
 
 # Change the active increment (by default is the last one):
-pressure_lc.ActiveIncrement = 10
+pressure_lc.ActiveN2PIncrement = pressure_lc.get_increment(10)
 
 # Look for all results
 all_results = pressure_lc.Results

{NaxToPy-1.5.6 → naxtopy-2.2.3}/README.md

@@ -10,27 +10,35 @@
 # NaxToPy
 
 **NaxToPy** is the [**NaxTo**](https://apps.microsoft.com/detail/XP9MMH0KDKGRJN?hl=en-US&gl=US)
-library designed for Python, which allows reading and manipulating FEM
-analysis results files from the most common tools: Nastran (op2, xdb, h5), Abaqus (odb), Optistruct
-(h3d, op2) and Ansys (rst); and stores them in a user-friendly Python structure. Additionally, it
-can read input files from Nastran (bdf, fem) and change it contents.
+library designed for Python, allowing users to read and manipulate FEM analysis
+results files from the most common tools: Nastran (op2, xdb, h5), Abaqus (odb), Optistruct (h3d, op2),
+and Ansys (rst). It stores these results in a user-friendly Python structure. Additionally, it can
+read input files from Nastran (bdf/dat), Optistruct (fem) and Abaqus(inp) and modify their contents.
 
-It could be easily combined with other Python packages as Matplotlib or Pandas. This provides access
-to the full coding power of Python to interpret and process the results, without the need to install
-any additional software other than having NaxTo already installed (see the _Download_ and _Homepage_
-links on the left).
+It can easily be combined with other Python packages, such as Matplotlib or Pandas, providing access
+to Python's full coding power for interpreting and processing results without the need to install
+additional software beyond NaxTo (see the Download and Homepage links on the left).
 
 **NaxToPy** is a powerful tool for FEM analysis post-processing!
 
-**CAUTION:** This version is only compatible with **NaxTo 2024.0.5**.
+---------------
+
+⚠️**Warning:** To use NaxToPy, [**NaxTo**](https://apps.microsoft.com/detail/XP9MMH0KDKGRJN?hl=en-US&gl=US) must be installed.
+This version is compatible with **NaxTo 2024.3**. It is compatible with all the steps of this version (2024.3.0, 2024.3.1).
 Check in _Programs and Features_ the NaxTo version that is installed.
 
+📘**Note:** If a specific NaxTo version is installed, search the [**NaxToPy History**](https://pypi.org/project/NaxToPy/2.2.1/#history) to find which newer version is compatible with it.
+
+
 ## Installation
 
+If python is installed and `pip` is added to the PATH:
 
-If python is callable from the command line:
+`pip install NaxToPy`
+
+An alternative, if Python is callable from the command line:
 
-`py -m pip install NaxToPy`
+`python -m pip install NaxToPy`
 
 For **Visual Studio** users:
 - Open "Python Environments" window
@@ -54,7 +62,7 @@ same directory. When ever you want to use the NaxToPy package add the following
 
 If python is callable from the command line:
 
-`py -m pip install -U NaxToPy`
+`python -m pip install -U NaxToPy`
 
 For Visual Studio users:
 - Open "Python Environments" window
@@ -130,6 +138,74 @@ To see previous version see the pre-release versions in https://test.pypi.org/pr
 1. The method new_envelope_loadcase() now has the option to choose the envelope group. Which means the user can ask for
 the LoadCases that are critical or the Increment that is critical instead of the value.
 
+### v.2.0.0
+1. Changes made to align the library with updates in lower-level dependencies.
+2. New internal methods to look for the compatibility with low-level dependencies.
+3. The name of the .log is now NaxToPy_Year-Month-Day.log.
+
+### v.2.0.1
+1. The compatibility is extended to all NaxTo steps of the same version.
+2. The property N2PLoadCase.ActiveIncrement is subtitued by N2PLoadCase.ActiveN2PIncrement.
+It uses an object instaed of an int.
+3. Update of the examples of some docstrings.
+
+### v.2.1.0
+1. Reading a Natran Input File: SPC and SCP1 are now supported.
+2. Bug fix. The order in the components in new_report() does not affect now.
+3. Formula check in new_derived_loadcase(), new_enevelope_loadcase() and new_derived_component().
+4. New optional arguments if n2ptoexe() to add extra libaries, packages or files.
+
+### v.2.1.1
+1. Two new methods in N2PModelContent: load_user_coord_sys_from_csv() and set_user_coord_sys().
+Also, there is a new property for N2PElement and N2PNode: UserSystemArray. This update allow the
+user to define a different coordinate system for each element or node. To ask for the results
+in this system, the optional argument `coordsys` must be equal to `-20`.
+2. Bug fix: The checking for component and section in new_report() has been fixed. If a comma
+appeared in the component or section name, the method failed.
+
+### v.2.1.2
+1. Internal change for speeding up the read of NastranInputFiles. Now the Nastran Cards are loaded
+when they are asked and not all at once.
+2. Improvement in error handling and log writing.
+3. The function import_results_from_files() checks if the file exist. If not, it prints an error
+but the execution doesn't crash.
+
+### v.2.2.0
+1. Feat: New module for fastener analysis: N2PGetFasteners.
+2. Feat: New module for fastener analysis: N2PGetLoadFasteners. Calculates forces in joints and bypass forces.
+3. Bug fix: When a NaxToPy executable file is used on a machine where NaxTo is installed, the libraries are selected accordingly.
+4. Feat: Hidden imports are now allowed in n2ptoexe.
+5. Bug fix: Fixed the rotation of the FORCES tensor. Now the QX and QY components (transverse shears) are calculated correctly.
+6. Refactor: The dictionary and list for Cards have been replaced with a lazy dictionary and a lazy list, improving execution efficiency.
+7. Refactor: Reading the mesh from binary files is now executed in parallel by default, as this approach is more memory-safe.
+
+### v.2.2.1
+1. BugFix: The method set_increment() is fixed.
+2. BugFix: Several bugfix (not in the result accuracy) are fixed in modules N2PGetFastener and N2PGetLoadsFastener. Several optimizations are included.
+3. Feat: Now the method get_load_case() admits a list of int and a list of string and return a list of N2PLoadCase.
+4. Refactor: N2P classes use __slots__ for security and optimization.
+5. Refactor: Complete refactor of the module that loads the NaxTo libraries.
+6. BugFix: in parallel mesh load with a small mesh and lot of results.
+7. BugFix: in sequential mesh load in op2.
+
+### v.2.2.2
+1. BugFix: Solved an issue in the Nastran Cards Dictionary
+2. BugFix: Solved the Prop atribute of an N2PElement in Abaqus
+3. Feat: Now is possible to create `N2PCoord` by the user with the `new_coordinate_system()` method.
+4. Feat: Now is possible to add to `element_nodal()` a list of N2PElement to unshew only the nodes of these elements.
+5. Feat: Now is possible to ask for results in a list of elements or nodes using the optional argument `filter_list`.
+6. Feat: When the user provides a coordinate system and two vectors (v1, v2) to specify the output results, the information
+is redundant. The coordinate system will prevail.
+7. Feat: New properties supported: PBUSH, PFAST, PMASS, PELAS, PGAP, PWELD
+8. BugFix: The method get_elements_attached() is fixed so when there are MPC connectors with the same ID.
+
+### v.2.2.3
+1. Requirement: Now NaxToPy require the package [**h5py** ](https://pypi.org/project/h5py/).
+2. Feat: N2PGetLoadFastener now can use PAG method and display format.
+3. BugFix: Some bugs are solved in N2PGetFastener and N2PGetLoadFastener.
+4. Feat: N2PGetLoadFastener can export results in HDF5 format.
+5. BugFix: The filtering in the method get_result_by_LCs_Incr() in elements when results are in Corner Data is fixed.
+
 # Documentation
 
 **NaxToPy** is a package developed by Idaero Solutions© as a part of the **NaxTo** software.
@@ -138,6 +214,7 @@ NaxToPy only use three dependeces:
 - NumPy: https://numpy.org/
 - PythonNET: https://pythonnet.github.io/
 - Setuptools: https://setuptools.pypa.io/en/latest/index.html
+- HDF5: https://www.h5py.org/
 
 ## Supported Files
 
@@ -148,7 +225,9 @@ NaxToPy only use three dependeces:
 - **Ansys:** .rst, .rth(beta)
 
 ### Input files:
-- **Nastran** (bdf)
+- **Nastran** (.bdf)
+- **Optistruct** (.fem)
+- **Abaqus** (.inp)
 
 ## Initialize your model
 
@@ -209,7 +288,7 @@ loadcaseslist = model.LoadCases
 pressure_lc = model.get_load_case("pressure")
 
 # Change the active increment (by default is the last one):
-pressure_lc.ActiveIncrement = 10
+pressure_lc.ActiveN2PIncrement = pressure_lc.get_increment(10)
 
 # Look for all results
 all_results = pressure_lc.Results

{NaxToPy-1.5.6 → naxtopy-2.2.3}/pyproject.toml

@@ -4,14 +4,14 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "NaxToPy"
-version = "1.5.6"
+version = "2.2.3"
 license = {file = "LICENSE"}
 authors = [ { name = "Idaero Solutions", email = "manuel.sanchez@idaerosolutions.com" }, ]
 requires-python = ">=3.9"
-dependencies = ["pythonnet>=3.0.1",
+dependencies = ["pythonnet>=3.0.3",
                 "numpy>=1.22.0",
                 "setuptools>=67.8.0",
-                ]
+                "h5py>=3.12.1"]
 description = "Package for postprocessing FEM results in Python"
 readme = "README.md"
 classifiers = ["Intended Audience :: Science/Research",

{NaxToPy-1.5.6 → naxtopy-2.2.3}/setup.py

@@ -7,7 +7,9 @@ setup(
     packages = find_packages(where="src"),
     package_dir = {"": "src"},
     include_package_data=True,
-    data_files=[("NaxToPy", ["src/NaxToPy/NaxToPy.ico", "src/NaxToPy/user_functions.txt"])],
+    package_data={
+        "NaxToPy": ["NaxToPy.ico", "user_functions.txt"]
+    },
     url="https://www.idaerosolutions.com/Home/NaxToPy",
     download_url="https://apps.microsoft.com/detail/XP9MMH0KDKGRJN?hl=en-US&gl=US"
 )

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQEntities/N2PEntity.py

@@ -0,0 +1,28 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeyword import N2PKeyword
+
+
+class N2PEntity:
+    """Class created to add information under a Keyword. There is not a similar concept in Abaqus. It is used to define
+    nodes, elements and shells."""
+
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        self.__info = info
+        self.__dictKeywordToN2P = dictKeywordToN2P
+        self.__dictEntityToN2P = dictEntityToN2P
+
+    @property
+    def KeywordParent(self) -> N2PKeyword:
+        """Keyword the entity belongs to. It always belongs to a keyword"""
+        return self.__dictKeywordToN2P[self.__info.KeywordParent]
+
+    @property
+    def KeywordIndex(self) -> int:
+        """Identification number of the Keyword ot belongs"""
+        return self.__info.KeywordIndex
+
+    @property
+    def Part(self) -> str:
+        """The part of an entity is always the part of the KeywordParent"""
+        return self.KeywordParent.Part

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQEntities/N2PEntityElement.py

@@ -0,0 +1,19 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQEntities.N2PEntity import N2PEntity
+from NaxToPy.Core.Classes.ABQEntities.N2PEntityNode import N2PEntityNode
+
+
+class N2PEntityElement(N2PEntity):
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info, dictKeywordToN2P, dictEntityToN2P)
+
+    @property
+    def ID(self) -> int:
+        """Element identification number"""
+        return self._N2PEntity__info.ID
+
+    @property
+    def NodeArray(self) -> list[N2PEntityNode, ]:
+        """Element identification number"""
+        return [self._N2PEntity__dictEntityToN2P[node] for node in self._N2PEntity__info.NodeArray]

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQEntities/N2PEntityNode.py

@@ -0,0 +1,46 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQEntities.N2PEntity import N2PEntity
+
+
+class N2PEntityNode(N2PEntity):
+
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info, dictKeywordToN2P, dictEntityToN2P)
+        
+    @property
+    def ID(self) -> int:
+        """Node identification number"""
+        return self._N2PEntity__info.ID
+
+    @property
+    def X1(self) -> float:
+        """First coordinate"""
+        return self._N2PEntity__info.ID
+
+    @property
+    def X2(self) -> float:
+        """Second coordinate"""
+        return self._N2PEntity__info.ID
+
+    @property
+    def X3(self) -> float:
+        """Third coordinate"""
+        return self._N2PEntity__info.ID
+
+    @property
+    def DirectionCosine1(self) -> float:
+        """First direction cosine of the normal at the node (Optional)"""
+        return self._N2PEntity__info.DirectionCosine1
+
+    @property
+    def DirectionCosine2(self) -> float:
+        """ Second direction cosine of the normal at the node (Optional)
+        For nodes entered a cylindrical or spherical system, this entry is an angle given in degrees."""
+        return self._N2PEntity__info.DirectionCosine2
+
+    @property
+    def DirectionCosine3(self) -> float:
+        """ Third direction cosine of the normal at the node (Optional)
+        For nodes entered a spherical system, this entry is an angle given in degrees."""
+        return self._N2PEntity__info.DirectionCosine3

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQEntities/N2PEntityShell.py

@@ -0,0 +1,34 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeyword import N2PKeyword
+from NaxToPy.Core.Classes.ABQEntities.N2PEntity import N2PEntity
+
+
+class N2PEntityShell(N2PEntity):
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info, dictKeywordToN2P, dictEntityToN2P)
+
+    @property
+    def Name(self) -> str:
+        """Name of the layer"""
+        return self._N2PEntity__info.Name
+
+    @property
+    def Thickness(self) -> float:
+        """Shell thickness"""
+        return self._N2PEntity__info.Thickness
+
+    @property
+    def IntegrationPoints(self) -> int:
+        """Number of integration points to be used through the shell section. Default: five for Simpson's rule and 3 for Gauss quadrature """
+        return self._N2PEntity__info.IntegrationPoints
+
+    @property
+    def Material(self) -> N2PKeyword:
+        """Node identification number"""
+        return self._N2PEntity__dictKeywordToN2P[self._N2PEntity__info.Material]
+
+    @property
+    def Orientation(self) -> N2PKeyword:
+        """Node identification number"""
+        return self._N2PEntity__dictKeywordToN2P.get(self._N2PEntity__info.Orientation)

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQEntities/__init__.py

@@ -0,0 +1,4 @@
+from NaxToPy.Core.Classes.ABQEntities.N2PEntity import N2PEntity
+from NaxToPy.Core.Classes.ABQEntities.N2PEntityNode import N2PEntityNode
+from NaxToPy.Core.Classes.ABQEntities.N2PEntityElement import N2PEntityElement
+from NaxToPy.Core.Classes.ABQEntities.N2PEntityShell import N2PEntityShell

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQKeywords/N2PKeyword.py

@@ -0,0 +1,43 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.N2PNastranInputData import N2PInputData
+
+
+class N2PKeyword(N2PInputData):
+
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info)
+        self.__info = info
+        self.__dictKeywordToN2P = dictKeywordToN2P
+        self.__dictEntityToN2P = dictEntityToN2P
+
+    @property
+    def SuperKeyword(self) -> N2PKeyword:
+        """Keyword that this one depends on"""
+        return self._N2PKeyword__dictKeywordToN2P.get(self._N2PKeyword__info.SuperKeyword)
+
+    @property
+    def SubKeywords(self) -> list[N2PKeyword, ]:
+        """Keywords that depend on this one"""
+        if self._N2PKeyword__info.SubKeywords:
+            return [self._N2PKeyword__dictKeywordToN2P.get(keyword) for keyword in self._N2PKeyword__info.SubKeywords]
+        else:
+            return []
+
+    @property
+    def Part(self) -> str:
+        """Part of the keyword"""
+        return self.__info.Part
+
+    @property
+    def KeywordType(self) -> str:
+        return self.__info.KeywordType.ToString()
+
+    @property
+    def KeywordCode(self) -> str:
+        """Keyword code: the first field read from a keyword"""
+        return self.__info.KeywordCode
+
+    @property
+    def Parameters(self) -> dict:
+        return dict(self.__info.Parameters)

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQKeywords/N2PKeywordBEAMSECTION.py

@@ -0,0 +1,30 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeywordELSET import N2PKeywordELSET 
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeyword import N2PKeyword
+from NaxToPy.Core.Classes.ABQEntities.N2PEntity import N2PEntity
+
+
+class N2PKeywordBEAMSECTION(N2PKeyword):
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info, dictKeywordToN2P, dictEntityToN2P)
+
+    @property
+    def Elset(self) -> N2PKeywordELSET:
+        """Set to which the property is applied"""
+        return self._N2PKeyword__dictKeywordToN2P[self._N2PKeyword_N2PKeyword__info.Elset]
+
+    @property
+    def Material(self) -> str:
+        """Material of the elements of the set"""
+        return self._N2PKeyword_N2PKeyword__info.Material
+
+    @property
+    def Name(self) -> str:
+        """Name given to the section"""
+        return self._N2PKeyword__info.Name
+
+    @property
+    def Section(self) -> N2PEntity:
+        """Description"""
+        return self._N2PKeyword__dictEntityToN2P[self._N2PKeyword__info.Section]

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQKeywords/N2PKeywordCOUPLING.py

@@ -0,0 +1,40 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeyword import N2PKeyword
+from NaxToPy.Core.Classes.ABQEntities.N2PEntityNode import N2PEntityNode
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeywordSURFACE import N2PKeywordSURFACE
+
+
+class N2PKeywordCOUPLING(N2PKeyword):
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info, dictKeywordToN2P, dictEntityToN2P)
+
+    @property
+    def RefNode(self) -> N2PEntityNode:
+        """Reference node of the coupling"""
+        return self._N2PKeyword__info.RefNode
+
+    @property
+    def Surface(self) -> N2PKeywordSURFACE:
+        """Surface defining the constrained nodes"""
+        return self._N2PKeyword__dictKeywordToN2P[self._N2PKeyword__info.Surface]
+
+    @property
+    def ConstrainedSpareNodes(self) -> list[N2PEntityNode, ]:
+        """Nodes defined in the coupling outside the surface"""
+        return list(self._N2PKeyword__info.ConstrainedSpareNodes)
+
+    @property
+    def ConstrainedNodes(self) -> list[N2PEntityNode, ]:
+        """All the nodes defined in the coupling"""
+        return list(self._N2PKeyword__info.ConstrainedNodes)
+
+    @property
+    def Name(self) -> str:
+        """Name of the Coupling"""
+        return self._N2PKeyword__info.Name
+
+    @property
+    def FreedomDegrees(self) -> list[str]:
+        """List with the degrees of freedom"""
+        return self._N2PKeyword__info.FreedomDegrees

naxtopy-2.2.3/src/NaxToPy/Core/Classes/ABQKeywords/N2PKeywordDENSITY.py

@@ -0,0 +1,23 @@
+from __future__ import annotations  # For compatibility with Python 3.9 or higher
+
+from NaxToPy.Core.Classes.ABQKeywords.N2PKeyword import N2PKeyword
+
+
+class N2PKeywordDENSITY(N2PKeyword):
+    def __init__(self, info, dictKeywordToN2P, dictEntityToN2P):
+        super().__init__(info, dictKeywordToN2P, dictEntityToN2P)
+
+    @property
+    def Density(self) -> float:
+        """Mass density [ML^-3]"""
+        return self._N2PKeyword__info.Density
+
+    @property
+    def Temperature(self) -> float:
+        """Temperature (optional)"""
+        return self._N2PKeyword__info.Temperature
+
+    @property
+    def FieldVariables(self) -> list[float]:
+        """Field variables (optional)"""
+        return list(self._N2PKeyword__info.FieldVariables)