RS3Scripting 4.42.0__tar.gz → 4.44.0__tar.gz

rs3scripting-4.44.0/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.4
+Name: RS3Scripting
+Version: 4.44.0
+Summary: Client library for interacting with RS3 through python
+Author: Rocscience
+License-Expression: MIT
+Project-URL: Homepage, https://www.rocscience.com/software/rs3
+Project-URL: Documentation, https://www.rocscience.com/help/rs3/overview
+Keywords: Rocscience,RS3,Scripting,RocScript,Geotechnical,Finite Element Analysis,FEM,3D
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: License.txt
+Requires-Dist: grpcio
+Requires-Dist: protobuf<6.0
+Dynamic: license-file
+
+## Introduction 
+This project is a library that can be used to interact with RS3 through python.  
+
+### Goal
+Each function exposed corresponds to an equivalent operation you could have done through the UI.  
+Using this idea, the user should be able to edit models and get results without having to go through the UI at all.
+Although only a limited set of functionality is exposed for now, some basic workflows should still be possible. For a list of the functionality we have so far, see [Exposed Functionality](#exposed-functionality).
+
+### Python UI equivalents
+Events and workflows done in the UI will have equivalents in the python library.  
+Wherever a dialog is shown in the UI, there will be an equivalent class with methods that mimick the dialog's behavior.  
+Wherever a warning or error dialog is displayed, an exception will be thrown, or a warning will be displayed in python instead.  
+Wherever you can select and manipulate an entity, identifiers can be used in the library to get references to those entities in python and objects will be constructed to help you interface with them.  
+
+### How it works
+Each function in the library is a wrapper to make an api call to the Application.  
+Objects retrieved through function calls will often not contain any data themselves, but will instead be proxies, allowing you to get information from the objects in the application.  
+For this reason, debugging will sometimes be tricky, as not all data will always be available for you to inspect unless you get it and assign it to a variable yourself.  
+
+### Warnings
+References can be *invalidated* whenever the corresponding object in the application is destroyed or reloaded. You will need to watch out for expired referenecs and renew them when needed as it can cause crashes or incorrect results if not managed properly. Functions that invalidate objects will always be marked with a warning and will indicate which objects should be re-loaded. 
+
+## Exposed Functionality
+
+## Getting Started
+
+**Getting started guide**  
+
+**First Tutorial**  
+
+
+# For Contributors:
+
+## Build
+First, make sure you have python installed on your computer. Then follow the steps to build:  
+1. Run the command below to install the python build module.    
+```python -m pip install --upgrade build```  
+2. Run the script to build and reinstall:
+```./buildAndReinstall.bat```  
+
+The next time you update the library, it can be re-built and re-installed using:
+```./buildAndReinstall.bat```
+
+## Unit Testing
+
+To ensure the project's functionality and maintain code quality, a test suite using the `unittest` framework has been implemented. The documentation for `unittest` can be found at the following link: https://docs.python.org/3/library/unittest.html  
+
+### Creating Unit Tests
+**Directory Structure:**   
+- Place new .py files for unit testing in the tests directory.
+- Save any RS3 files required for testing in the tests/resources directory.
+
+**Handling Test Resources:**  
+Instead of directly modifying the base files in tests/resources, create copies of these files in each test file's setup and delete them in the teardown phase. This ensures that the original resources remain intact and unmodified after running the tests.
+
+### Running Unit Test Cases
+Before running the tests, make sure you have:
+1. Built the RS3 library as explained in the [Build](#build) section.
+2. Started the RS3 Modeler.
+3. Started the RS3 Interpreter.
+4. Started the Server on both the RS3 Modeler and RS3 Interpreter. 
+
+To run a test, vscode has a 'Testing' section, where you can run inidividual tests:  
+![alt text](image.png)  
+
+To run all the tests, navigate to the root directory of the project and execute the following command:  
+```python -m unittest discover -s tests```  
+
+To run an individual test file from the command line, navigate to the root directory of the project and execute the following command with the correct filename:  
+```python -m unittest discover -s tests -p "<sampleTestFile>.py"```
+
+To run a sub-folder of tests, navigate to the 'tests' folder, and run:  
+```python -m unittest discover -v -s Path/To/Folder```  
+
+
+**_NOTE:_** To display additional information on the results of the unit tests, pass the `-v` option into the testing command:  
+```python -m unittest discover -v -s tests```
+
+## Documentation
+The following steps can be taken to regenerate the RS3 Scripting Documentation:
+1. Create python a virtual environment. Navigate to the root directory of your workspace and run the commands below:  
+```python -m venv venv```
+```venv/Scripts/activate```
+2. Rebuild the RS3 library in your virtual environment by following the [Build](#build) section.
+3. Install the documentation requirement packages.
+```pip install -r docs/requirements.txt```
+4. To rerun all examples with the command below:
+```python docs/example_code/runAll.py```
+5. To generate the documentation run the following: 
+```python generateAndBuildDocumentation.py```
+6. The Documentation in html format will be located here: ```RS3 Python Client Library/docs/_build/index.html```
+
+### Adding To Documentation
+The following steps can be taken to add a new proxy object to the autogenerated documentation:
+1. Ensure automatic generation of the proxy object python files has been completed for the new proxy object. 
+2. To include an example code snippet, ensure a docstring is being generated at the top of the base proxy object ```.py``` file, which will link to the example.  
+   See Below:    
+   ```
+	"""
+	:ref:`Bolt Example`
+	"""
+   ```
+3. Add your example code snippet to ```docs\example_code```
+4. Open examples.rst and following the format of the existing example links, add a link to your code example. Ensure that your link label matches the link label being generated in Step 2.  
+   See Below:  
+	```
+	.. _Bolt Example:
+	```
+5. Follow the steps in [Documentation](#documentation) to regenerate the new documentaiton.
+
+## Contribution Guidelines
+Contributions are welcomed to improve RS3's Scripting Features. To make a contribution, follow the guidelines below:
+1. **Make Changes:** Start by making the necessary changes to the relevant `.py` file(s) to address the task or implement new features.
+2. **Install Dependencies:** Install the required dependencies specified in the `requirements.txt` file, as explained in the [Build](#build) section. It is recommended that these dependencies be installed within a virtual environment.
+3. **Python Interpreter:** Select the same Python interpreter used to install the package. You can specify the interpreter in your virtual environment or project settings.
+4. **Testing:** Thoroughly test your changes to ensure they meet the project's requirements and do not introduce regressions. Consult the [Unit Testing](#unit-testing) section for more information. Include additional test cases to cover modifications to the project.
+5. **Pull Request:** After thorough testing and review, submit a pull request which describes the purpose of your changes. After review and approval, merge your changes into the main branch.

rs3scripting-4.44.0/README.md

@@ -0,0 +1,117 @@
+## Introduction 
+This project is a library that can be used to interact with RS3 through python.  
+
+### Goal
+Each function exposed corresponds to an equivalent operation you could have done through the UI.  
+Using this idea, the user should be able to edit models and get results without having to go through the UI at all.
+Although only a limited set of functionality is exposed for now, some basic workflows should still be possible. For a list of the functionality we have so far, see [Exposed Functionality](#exposed-functionality).
+
+### Python UI equivalents
+Events and workflows done in the UI will have equivalents in the python library.  
+Wherever a dialog is shown in the UI, there will be an equivalent class with methods that mimick the dialog's behavior.  
+Wherever a warning or error dialog is displayed, an exception will be thrown, or a warning will be displayed in python instead.  
+Wherever you can select and manipulate an entity, identifiers can be used in the library to get references to those entities in python and objects will be constructed to help you interface with them.  
+
+### How it works
+Each function in the library is a wrapper to make an api call to the Application.  
+Objects retrieved through function calls will often not contain any data themselves, but will instead be proxies, allowing you to get information from the objects in the application.  
+For this reason, debugging will sometimes be tricky, as not all data will always be available for you to inspect unless you get it and assign it to a variable yourself.  
+
+### Warnings
+References can be *invalidated* whenever the corresponding object in the application is destroyed or reloaded. You will need to watch out for expired referenecs and renew them when needed as it can cause crashes or incorrect results if not managed properly. Functions that invalidate objects will always be marked with a warning and will indicate which objects should be re-loaded. 
+
+## Exposed Functionality
+
+## Getting Started
+
+**Getting started guide**  
+
+**First Tutorial**  
+
+
+# For Contributors:
+
+## Build
+First, make sure you have python installed on your computer. Then follow the steps to build:  
+1. Run the command below to install the python build module.    
+```python -m pip install --upgrade build```  
+2. Run the script to build and reinstall:
+```./buildAndReinstall.bat```  
+
+The next time you update the library, it can be re-built and re-installed using:
+```./buildAndReinstall.bat```
+
+## Unit Testing
+
+To ensure the project's functionality and maintain code quality, a test suite using the `unittest` framework has been implemented. The documentation for `unittest` can be found at the following link: https://docs.python.org/3/library/unittest.html  
+
+### Creating Unit Tests
+**Directory Structure:**   
+- Place new .py files for unit testing in the tests directory.
+- Save any RS3 files required for testing in the tests/resources directory.
+
+**Handling Test Resources:**  
+Instead of directly modifying the base files in tests/resources, create copies of these files in each test file's setup and delete them in the teardown phase. This ensures that the original resources remain intact and unmodified after running the tests.
+
+### Running Unit Test Cases
+Before running the tests, make sure you have:
+1. Built the RS3 library as explained in the [Build](#build) section.
+2. Started the RS3 Modeler.
+3. Started the RS3 Interpreter.
+4. Started the Server on both the RS3 Modeler and RS3 Interpreter. 
+
+To run a test, vscode has a 'Testing' section, where you can run inidividual tests:  
+![alt text](image.png)  
+
+To run all the tests, navigate to the root directory of the project and execute the following command:  
+```python -m unittest discover -s tests```  
+
+To run an individual test file from the command line, navigate to the root directory of the project and execute the following command with the correct filename:  
+```python -m unittest discover -s tests -p "<sampleTestFile>.py"```
+
+To run a sub-folder of tests, navigate to the 'tests' folder, and run:  
+```python -m unittest discover -v -s Path/To/Folder```  
+
+
+**_NOTE:_** To display additional information on the results of the unit tests, pass the `-v` option into the testing command:  
+```python -m unittest discover -v -s tests```
+
+## Documentation
+The following steps can be taken to regenerate the RS3 Scripting Documentation:
+1. Create python a virtual environment. Navigate to the root directory of your workspace and run the commands below:  
+```python -m venv venv```
+```venv/Scripts/activate```
+2. Rebuild the RS3 library in your virtual environment by following the [Build](#build) section.
+3. Install the documentation requirement packages.
+```pip install -r docs/requirements.txt```
+4. To rerun all examples with the command below:
+```python docs/example_code/runAll.py```
+5. To generate the documentation run the following: 
+```python generateAndBuildDocumentation.py```
+6. The Documentation in html format will be located here: ```RS3 Python Client Library/docs/_build/index.html```
+
+### Adding To Documentation
+The following steps can be taken to add a new proxy object to the autogenerated documentation:
+1. Ensure automatic generation of the proxy object python files has been completed for the new proxy object. 
+2. To include an example code snippet, ensure a docstring is being generated at the top of the base proxy object ```.py``` file, which will link to the example.  
+   See Below:    
+   ```
+	"""
+	:ref:`Bolt Example`
+	"""
+   ```
+3. Add your example code snippet to ```docs\example_code```
+4. Open examples.rst and following the format of the existing example links, add a link to your code example. Ensure that your link label matches the link label being generated in Step 2.  
+   See Below:  
+	```
+	.. _Bolt Example:
+	```
+5. Follow the steps in [Documentation](#documentation) to regenerate the new documentaiton.
+
+## Contribution Guidelines
+Contributions are welcomed to improve RS3's Scripting Features. To make a contribution, follow the guidelines below:
+1. **Make Changes:** Start by making the necessary changes to the relevant `.py` file(s) to address the task or implement new features.
+2. **Install Dependencies:** Install the required dependencies specified in the `requirements.txt` file, as explained in the [Build](#build) section. It is recommended that these dependencies be installed within a virtual environment.
+3. **Python Interpreter:** Select the same Python interpreter used to install the package. You can specify the interpreter in your virtual environment or project settings.
+4. **Testing:** Thoroughly test your changes to ensure they meet the project's requirements and do not introduce regressions. Consult the [Unit Testing](#unit-testing) section for more information. Include additional test cases to cover modifications to the project.
+5. **Pull Request:** After thorough testing and review, submit a pull request which describes the purpose of your changes. After review and approval, merge your changes into the main branch.

{rs3scripting-4.42.0 → rs3scripting-4.44.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "RS3Scripting"
-version = "4.042.0"
+version = "4.044.0"
 dependencies = [
   "grpcio",
   "protobuf<6.0"

rs3scripting-4.44.0/src/RS3Scripting.egg-info/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.4
+Name: RS3Scripting
+Version: 4.44.0
+Summary: Client library for interacting with RS3 through python
+Author: Rocscience
+License-Expression: MIT
+Project-URL: Homepage, https://www.rocscience.com/software/rs3
+Project-URL: Documentation, https://www.rocscience.com/help/rs3/overview
+Keywords: Rocscience,RS3,Scripting,RocScript,Geotechnical,Finite Element Analysis,FEM,3D
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.7
+Description-Content-Type: text/markdown
+License-File: License.txt
+Requires-Dist: grpcio
+Requires-Dist: protobuf<6.0
+Dynamic: license-file
+
+## Introduction 
+This project is a library that can be used to interact with RS3 through python.  
+
+### Goal
+Each function exposed corresponds to an equivalent operation you could have done through the UI.  
+Using this idea, the user should be able to edit models and get results without having to go through the UI at all.
+Although only a limited set of functionality is exposed for now, some basic workflows should still be possible. For a list of the functionality we have so far, see [Exposed Functionality](#exposed-functionality).
+
+### Python UI equivalents
+Events and workflows done in the UI will have equivalents in the python library.  
+Wherever a dialog is shown in the UI, there will be an equivalent class with methods that mimick the dialog's behavior.  
+Wherever a warning or error dialog is displayed, an exception will be thrown, or a warning will be displayed in python instead.  
+Wherever you can select and manipulate an entity, identifiers can be used in the library to get references to those entities in python and objects will be constructed to help you interface with them.  
+
+### How it works
+Each function in the library is a wrapper to make an api call to the Application.  
+Objects retrieved through function calls will often not contain any data themselves, but will instead be proxies, allowing you to get information from the objects in the application.  
+For this reason, debugging will sometimes be tricky, as not all data will always be available for you to inspect unless you get it and assign it to a variable yourself.  
+
+### Warnings
+References can be *invalidated* whenever the corresponding object in the application is destroyed or reloaded. You will need to watch out for expired referenecs and renew them when needed as it can cause crashes or incorrect results if not managed properly. Functions that invalidate objects will always be marked with a warning and will indicate which objects should be re-loaded. 
+
+## Exposed Functionality
+
+## Getting Started
+
+**Getting started guide**  
+
+**First Tutorial**  
+
+
+# For Contributors:
+
+## Build
+First, make sure you have python installed on your computer. Then follow the steps to build:  
+1. Run the command below to install the python build module.    
+```python -m pip install --upgrade build```  
+2. Run the script to build and reinstall:
+```./buildAndReinstall.bat```  
+
+The next time you update the library, it can be re-built and re-installed using:
+```./buildAndReinstall.bat```
+
+## Unit Testing
+
+To ensure the project's functionality and maintain code quality, a test suite using the `unittest` framework has been implemented. The documentation for `unittest` can be found at the following link: https://docs.python.org/3/library/unittest.html  
+
+### Creating Unit Tests
+**Directory Structure:**   
+- Place new .py files for unit testing in the tests directory.
+- Save any RS3 files required for testing in the tests/resources directory.
+
+**Handling Test Resources:**  
+Instead of directly modifying the base files in tests/resources, create copies of these files in each test file's setup and delete them in the teardown phase. This ensures that the original resources remain intact and unmodified after running the tests.
+
+### Running Unit Test Cases
+Before running the tests, make sure you have:
+1. Built the RS3 library as explained in the [Build](#build) section.
+2. Started the RS3 Modeler.
+3. Started the RS3 Interpreter.
+4. Started the Server on both the RS3 Modeler and RS3 Interpreter. 
+
+To run a test, vscode has a 'Testing' section, where you can run inidividual tests:  
+![alt text](image.png)  
+
+To run all the tests, navigate to the root directory of the project and execute the following command:  
+```python -m unittest discover -s tests```  
+
+To run an individual test file from the command line, navigate to the root directory of the project and execute the following command with the correct filename:  
+```python -m unittest discover -s tests -p "<sampleTestFile>.py"```
+
+To run a sub-folder of tests, navigate to the 'tests' folder, and run:  
+```python -m unittest discover -v -s Path/To/Folder```  
+
+
+**_NOTE:_** To display additional information on the results of the unit tests, pass the `-v` option into the testing command:  
+```python -m unittest discover -v -s tests```
+
+## Documentation
+The following steps can be taken to regenerate the RS3 Scripting Documentation:
+1. Create python a virtual environment. Navigate to the root directory of your workspace and run the commands below:  
+```python -m venv venv```
+```venv/Scripts/activate```
+2. Rebuild the RS3 library in your virtual environment by following the [Build](#build) section.
+3. Install the documentation requirement packages.
+```pip install -r docs/requirements.txt```
+4. To rerun all examples with the command below:
+```python docs/example_code/runAll.py```
+5. To generate the documentation run the following: 
+```python generateAndBuildDocumentation.py```
+6. The Documentation in html format will be located here: ```RS3 Python Client Library/docs/_build/index.html```
+
+### Adding To Documentation
+The following steps can be taken to add a new proxy object to the autogenerated documentation:
+1. Ensure automatic generation of the proxy object python files has been completed for the new proxy object. 
+2. To include an example code snippet, ensure a docstring is being generated at the top of the base proxy object ```.py``` file, which will link to the example.  
+   See Below:    
+   ```
+	"""
+	:ref:`Bolt Example`
+	"""
+   ```
+3. Add your example code snippet to ```docs\example_code```
+4. Open examples.rst and following the format of the existing example links, add a link to your code example. Ensure that your link label matches the link label being generated in Step 2.  
+   See Below:  
+	```
+	.. _Bolt Example:
+	```
+5. Follow the steps in [Documentation](#documentation) to regenerate the new documentaiton.
+
+## Contribution Guidelines
+Contributions are welcomed to improve RS3's Scripting Features. To make a contribution, follow the guidelines below:
+1. **Make Changes:** Start by making the necessary changes to the relevant `.py` file(s) to address the task or implement new features.
+2. **Install Dependencies:** Install the required dependencies specified in the `requirements.txt` file, as explained in the [Build](#build) section. It is recommended that these dependencies be installed within a virtual environment.
+3. **Python Interpreter:** Select the same Python interpreter used to install the package. You can specify the interpreter in your virtual environment or project settings.
+4. **Testing:** Thoroughly test your changes to ensure they meet the project's requirements and do not introduce regressions. Consult the [Unit Testing](#unit-testing) section for more information. Include additional test cases to cover modifications to the project.
+5. **Pull Request:** After thorough testing and review, submit a pull request which describes the purpose of your changes. After review and approval, merge your changes into the main branch.

{rs3scripting-4.42.0 → rs3scripting-4.44.0}/src/RS3Scripting.egg-info/SOURCES.txt

@@ -20,6 +20,18 @@ src/rs3/Selection.py
 src/rs3/__init__.py
 src/rs3/_client.py
 src/rs3/_proxyObject.py
+src/rs3/entities/BaseEntity.py
+src/rs3/entities/entity.py
+src/rs3/entities/beam/__init__.py
+src/rs3/entities/beam/beam.py
+src/rs3/entities/bolt/__init__.py
+src/rs3/entities/bolt/bolt.py
+src/rs3/entities/joint/__init__.py
+src/rs3/entities/joint/joint.py
+src/rs3/entities/liningComposition/__init__.py
+src/rs3/entities/liningComposition/liningComposition.py
+src/rs3/entities/pile/__init__.py
+src/rs3/entities/pile/pile.py
 src/rs3/generatedFiles/BFPCommonMessage_pb2.py
 src/rs3/generatedFiles/BFPCommonMessage_pb2.pyi
 src/rs3/generatedFiles/BFPCommonMessage_pb2_grpc.py
@@ -77,6 +89,9 @@ src/rs3/generatedFiles/FieldStressSourceService_pb2_grpc.py
 src/rs3/generatedFiles/GaussPointFailureMessage_pb2.py
 src/rs3/generatedFiles/GaussPointFailureMessage_pb2.pyi
 src/rs3/generatedFiles/GaussPointFailureMessage_pb2_grpc.py
+src/rs3/generatedFiles/GroupsService_pb2.py
+src/rs3/generatedFiles/GroupsService_pb2.pyi
+src/rs3/generatedFiles/GroupsService_pb2_grpc.py
 src/rs3/generatedFiles/HydraulicStageFactorService_pb2.py
 src/rs3/generatedFiles/HydraulicStageFactorService_pb2.pyi
 src/rs3/generatedFiles/HydraulicStageFactorService_pb2_grpc.py
@@ -149,6 +164,24 @@ src/rs3/generatedFiles/ModelFunctionService_pb2_grpc.py
 src/rs3/generatedFiles/ModelService_pb2.py
 src/rs3/generatedFiles/ModelService_pb2.pyi
 src/rs3/generatedFiles/ModelService_pb2_grpc.py
+src/rs3/generatedFiles/ModifyBeamEntityService_pb2.py
+src/rs3/generatedFiles/ModifyBeamEntityService_pb2.pyi
+src/rs3/generatedFiles/ModifyBeamEntityService_pb2_grpc.py
+src/rs3/generatedFiles/ModifyBoltEntityService_pb2.py
+src/rs3/generatedFiles/ModifyBoltEntityService_pb2.pyi
+src/rs3/generatedFiles/ModifyBoltEntityService_pb2_grpc.py
+src/rs3/generatedFiles/ModifyCompositeLinerEntity_pb2.py
+src/rs3/generatedFiles/ModifyCompositeLinerEntity_pb2.pyi
+src/rs3/generatedFiles/ModifyCompositeLinerEntity_pb2_grpc.py
+src/rs3/generatedFiles/ModifyJointEntityService_pb2.py
+src/rs3/generatedFiles/ModifyJointEntityService_pb2.pyi
+src/rs3/generatedFiles/ModifyJointEntityService_pb2_grpc.py
+src/rs3/generatedFiles/ModifyPileEntityService_pb2.py
+src/rs3/generatedFiles/ModifyPileEntityService_pb2.pyi
+src/rs3/generatedFiles/ModifyPileEntityService_pb2_grpc.py
+src/rs3/generatedFiles/ModifyPileEntity_pb2.py
+src/rs3/generatedFiles/ModifyPileEntity_pb2.pyi
+src/rs3/generatedFiles/ModifyPileEntity_pb2_grpc.py
 src/rs3/generatedFiles/PileDataService_pb2.py
 src/rs3/generatedFiles/PileDataService_pb2.pyi
 src/rs3/generatedFiles/PileDataService_pb2_grpc.py
@@ -197,6 +230,9 @@ src/rs3/generatedFiles/StiffnessStageFactorService_pb2_grpc.py
 src/rs3/generatedFiles/StrengthStageFactorService_pb2.py
 src/rs3/generatedFiles/StrengthStageFactorService_pb2.pyi
 src/rs3/generatedFiles/StrengthStageFactorService_pb2_grpc.py
+src/rs3/generatedFiles/SupportEntityService_pb2.py
+src/rs3/generatedFiles/SupportEntityService_pb2.pyi
+src/rs3/generatedFiles/SupportEntityService_pb2_grpc.py
 src/rs3/generatedFiles/WaterByLocationDataService_pb2.py
 src/rs3/generatedFiles/WaterByLocationDataService_pb2.pyi
 src/rs3/generatedFiles/WaterByLocationDataService_pb2_grpc.py
@@ -234,6 +270,7 @@ src/rs3/projectSettings/__init__.py
 src/rs3/properties/CustomHydraulicModel.py
 src/rs3/properties/DiscreteFunction.py
 src/rs3/properties/GeneralizedAnisotropicFunction.py
+src/rs3/properties/Group.py
 src/rs3/properties/IPropertyGroupAccessors.py
 src/rs3/properties/PropertyEnums.py
 src/rs3/properties/ShearNormalFunction.py

{rs3scripting-4.42.0 → rs3scripting-4.44.0}/src/rs3/CommonEnums.py

@@ -13,4 +13,11 @@ class AutoRestraintsType(Enum):
 class ExternalVolumeRoles(Enum):
     GEOLOGY = "Geology"
     CONSTRUCTION = "Construction"
-    EXCAVATION = "Excavation"
+    EXCAVATION = "Excavation"
+    
+class SupportTypes(Enum):
+    BEAM = 1
+    BOLT = 2
+    PILE = 3
+    JOINT = 4
+    COMPOSITE_LINER = 5

{rs3scripting-4.42.0 → rs3scripting-4.44.0}/src/rs3/ExternalVolume.py

@@ -17,7 +17,7 @@ class ExternalVolume(_ProxyObject):
         self._propertyAccessor = PropertyAccessor(client, projectID, self._externalVolumesService)
         
     def setName(self, name : str):    
-        request = CommonMessages_pb2.SetPropertyRequest(objectId=self._objectId, propertyName="Name", value=CommonMessages_pb2.PropertyValue(stringValue=name))
+        request = CommonMessages_pb2.SetEntityPropertyRequest(entityId=self._objectId, propertyIdOrName=name)
         self._client.callFunction(self._externalVolumesService.SetExternalVolumeName, request)
     def getName(self) -> str:
         return self._propertyAccessor.getStringValue("Name")
@@ -39,6 +39,17 @@ class ExternalVolume(_ProxyObject):
         response : ExternalVolumesService_pb2.GetAppliedMaterialPropertyResponse = self._client.callFunction(self._externalVolumesService.GetAppliedMaterialProperty, request)
         return response.materialName
     
+    def setGrouping(self, stageNum : int, groupName : str):
+        """
+        Assign group to the given stage by the group name. To ungroup the material, "Ungrouped" should be used as the groupName.
+        """
+        request = CommonMessages_pb2.SetGroupingRequest(objectId=self._objectId, stageNum=stageNum, groupName=groupName)
+        self._client.callFunction(self._externalVolumesService.SetGrouping, request)
+    def getGrouping(self, stageNum : int):
+        request = CommonMessages_pb2.GetGroupingRequest(objectId=self._objectId, stageNum=stageNum)
+        response : CommonMessages_pb2.GetGroupingResponse = self._client.callFunction(self._externalVolumesService.GetGrouping, request)
+        return response.groupName
+    
     def getVolume(self) -> str:
         return self._propertyAccessor.getDoubleProperty("Volume")
     

{rs3scripting-4.42.0 → rs3scripting-4.44.0}/src/rs3/Geometry.py

@@ -47,6 +47,13 @@ class Cube(Geometry):
         geometry_ = CommonGeometryMessages.Geometry(box=box_)
         return geometry_
     
+    def toCommonVolumeGeometryObject(self):
+        corner1_ = CommonGeometryMessages.Point(x=self.corner1.x, y=self.corner1.y, z=self.corner1.z)
+        corner2_ = CommonGeometryMessages.Point(x=self.corner2.x, y=self.corner2.y, z=self.corner2.z)
+        box_ = CommonGeometryMessages.Box(corner1=corner1_, corner2=corner2_, rotationAboutX=self.rotationAboutX, rotationAboutY=self.rotationAboutY, rotationAboutZ=self.rotationAboutZ)
+        geometry_ = CommonGeometryMessages.VolumeGeometry(box=box_)
+        return geometry_
+    
 @dataclass
 class Cylinder(Geometry):
     axisStartPoint: Point
@@ -60,6 +67,14 @@ class Cylinder(Geometry):
         cylinder_ = CommonGeometryMessages.Cylinder(axisStartPoint=axisStartPoint_, axisEndPoint=axisEndPoint_, radius=radius_)
         geometry_ = CommonGeometryMessages.Geometry(cylinder=cylinder_)
         return geometry_
+    
+    def toCommonVolumeGeometryObject(self):
+        axisStartPoint_ = CommonGeometryMessages.Point(x=self.axisStartPoint.x, y=self.axisStartPoint.y, z=self.axisStartPoint.z)
+        axisEndPoint_ = CommonGeometryMessages.Point(x=self.axisEndPoint.x, y=self.axisEndPoint.y, z=self.axisEndPoint.z)
+        radius_ = self.radius
+        cylinder_ = CommonGeometryMessages.Cylinder(axisStartPoint=axisStartPoint_, axisEndPoint=axisEndPoint_, radius=radius_)
+        geometry_ = CommonGeometryMessages.VolumeGeometry(cylinder=cylinder_)
+        return geometry_
 
 @dataclass
 class Sphere(Geometry):
@@ -71,4 +86,11 @@ class Sphere(Geometry):
         radius_ = self.radius
         sphere_ = CommonGeometryMessages.Sphere(center=center_, radius=radius_)
         geometry_ = CommonGeometryMessages.Geometry(sphere=sphere_)
+        return geometry_
+    
+    def toCommonVolumeGeometryObject(self):
+        center_ = CommonGeometryMessages.Point(x=self.center.x, y=self.center.y, z=self.center.z)
+        radius_ = self.radius
+        sphere_ = CommonGeometryMessages.Sphere(center=center_, radius=radius_)
+        geometry_ = CommonGeometryMessages.VolumeGeometry(sphere=sphere_)
         return geometry_

{rs3scripting-4.42.0 → rs3scripting-4.44.0}/src/rs3/Model.py

@@ -136,6 +136,14 @@ class ModelBase:
         result = result_.result
         return result
     
+    def getGroupByName(self, groupName: str) -> str:
+        _projectId_ = self._projectId
+        groupName_ = groupName
+        request = ModelService.getGroupByNameRequest(_projectId=_projectId_, groupName=groupName_)
+        result_ = self._client.callFunction(self._ModelService.getGroupByName, request)
+        result = result_.result
+        return result
+    
     def getDiscreteFunctionByName(self, discreteFunctionName: str) -> str:
         _projectId_ = self._projectId
         discreteFunctionName_ = discreteFunctionName
@@ -245,6 +253,13 @@ class ModelBase:
         result = [obj for obj in result_.result]
         return result
     
+    def getAllGroups(self) -> list[str]:
+        _projectId_ = self._projectId
+        request = ModelService.getAllGroupsRequest(_projectId=_projectId_)
+        result_ = self._client.callFunction(self._ModelService.getAllGroups, request)
+        result = [obj for obj in result_.result]
+        return result
+    
     def getAllBoltPropertiesInUse(self) -> list[str]:
         _projectId_ = self._projectId
         request = ModelService.getAllBoltPropertiesInUseRequest(_projectId=_projectId_)
@@ -458,6 +473,18 @@ class ModelBase:
         request = ModelService.deleteWaterGridPropertyRequest(_projectId=_projectId_, waterGridName=waterGridName_)
         self._client.callFunction(self._ModelService.deleteWaterGridProperty, request)
     
+    def createNewGroupProperty(self, groupName: str) -> None:
+        _projectId_ = self._projectId
+        groupName_ = groupName
+        request = ModelService.createNewGroupPropertyRequest(_projectId=_projectId_, groupName=groupName_)
+        self._client.callFunction(self._ModelService.createNewGroupProperty, request)
+    
+    def deleteGroupProperty(self, groupName: str) -> None:
+        _projectId_ = self._projectId
+        groupName_ = groupName
+        request = ModelService.deleteGroupPropertyRequest(_projectId=_projectId_, groupName=groupName_)
+        self._client.callFunction(self._ModelService.deleteGroupProperty, request)
+    
     def getDiscreteFunctions(self) -> list[str]:
         _projectId_ = self._projectId
         request = ModelService.getDiscreteFunctionsRequest(_projectId=_projectId_)
@@ -550,12 +577,14 @@ from rs3.properties.material.Material import MaterialProperty
 from rs3.properties.groundwater.WaterByLocation import WaterByLocationProperty
 from rs3.properties.groundwater.WaterGrid import WaterGridProperty
 from rs3.ExternalVolume import ExternalVolume
+from rs3.properties.Group import Group
 from rs3.properties.DiscreteFunction import DiscreteFunction
 from rs3.properties.ShearNormalFunction import ShearNormalFunction
 from rs3.properties.GeneralizedAnisotropicFunction import GeneralizedAnisotropicFunction
 from rs3.properties.CustomHydraulicModel import CustomHydraulicModel
 from rs3.Restraints import Restraints
 from rs3.Selection import Selection
+from rs3.entities.entity import Entity
 from rs3.Compute import Compute
 from rs3.results.Results import Results
 from rs3.ModelEnums import *
@@ -569,6 +598,7 @@ class Model(ModelBase):
         super().__init__(client, projectId)
         self.ProjectSettings = ProjectSettings(client, projectId)
         self.Selection = Selection(client, projectId)
+        self.Entity = Entity(client, projectId)
         self.Loadings = Loadings(client, projectId)
         self.Restraints = Restraints(client, projectId)
         self.Mesh = Mesh(client, projectId)
@@ -670,6 +700,10 @@ class Model(ModelBase):
         externalVolumeProp = super().getExternalVolumeByName(externalVolumeName)
         return ExternalVolume(self._client, externalVolumeProp)
     
+    def getGroupByName(self, groupName) -> Group:
+        groupProp = super().getGroupByName(groupName)
+        return Group(self._client, groupProp, self._projectId)
+    
     def getDiscreteFunctionByName(self, discreteFunctionName) -> DiscreteFunction:
         discreteFunctionProp = super().getDiscreteFunctionByName(discreteFunctionName)
         return DiscreteFunction(self._client, discreteFunctionProp)
@@ -726,6 +760,10 @@ class Model(ModelBase):
         externalVolumesProps = super().getAllExternalVolumes()
         return [ExternalVolume(self._client, obj) for obj in externalVolumesProps]
     
+    def getAllGroups(self) -> list[Group]:
+        groups = super().getAllGroups()
+        return [Group(self._client, obj, self._projectId) for obj in groups]
+    
     def getAllBoltPropertiesInUse(self) -> list[BoltProperty]:
         boltProps = super().getAllBoltPropertiesInUse()
         return [BoltProperty(self._client, obj) for obj in boltProps]