merging two branches

Tools/VSS-GUI-Tool/.gitignore

+__pycache__/

Tools/VSS-GUI-Tool/.gitmodules

+[submodule "scripts/vss"]
+	path = scripts/vss
+	url = https://github.com/COVESA/vehicle_signal_specification.git

Tools/VSS-GUI-Tool/Python-License.txt

+A. HISTORY OF THE SOFTWARE
+==========================
+Python was created in the early 1990s by Guido van Rossum at Stichting
+Mathematisch Centrum (CWI, see https://www.cwi.nl) in the Netherlands
+as a successor of a language called ABC. Guido remains Python's
+principal author, although it includes many contributions from others.
+In 1995, Guido continued his work on Python at the Corporation for
+National Research Initiatives (CNRI, see https://www.cnri.reston.va.us)
+in Reston, Virginia where he released several versions of the
+software.
+In May 2000, Guido and the Python core development team moved to
+BeOpen.com to form the BeOpen PythonLabs team. In October of the same
+year, the PythonLabs team moved to Digital Creations, which became
+Zope Corporation. In 2001, the Python Software Foundation (PSF, see
+https://www.python.org/psf/) was formed, a non-profit organization
+created specifically to own Python-related Intellectual Property.
+Zope Corporation was a sponsoring member of the PSF.
+All Python releases are Open Source (see https://opensource.org for
+the Open Source Definition). Historically, most, but not all, Python
+releases have also been GPL-compatible; the table below summarizes
+the various releases.
+Release Derived Year Owner GPLfrom
+compatible? (1)
+0.9.0 thru 1.2 1991-1995 CWI yes
+1.3 thru 1.5.2 1.2 1995-1999 CNRI yes
+1.6 1.5.2 2000 CNRI no
+2.0 1.6 2000 BeOpen.com no
+1.6.1 1.6 2001 CNRI yes (2)
+2.1 2.0+1.6.1 2001 PSF no
+2.0.1 2.0+1.6.1 2001 PSF yes
+2.1.1 2.1+2.0.1 2001 PSF yes
+2.1.2 2.1.1 2002 PSF yes
+2.1.3 2.1.2 2002 PSF yes
+2.2 and above 2.1.1 2001-now PSF yes
+Footnotes:
+(1) GPL-compatible doesn't mean that we're distributing Python under
+the GPL. All Python licenses, unlike the GPL, let you distribute
+a modified version without making your changes open source. The
+GPL-compatible licenses make it possible to combine Python with
+other software that is released under the GPL; the others don't.
+(2) According to Richard Stallman, 1.6.1 is not GPL-compatible,
+because its license has a choice of law clause. According to
+CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1
+is "not incompatible" with the GPL.
+Thanks to the many outside volunteers who have worked under Guido's
+direction to make these releases possible.
+B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON
+===============================================================
+Python software and documentation are licensed under the
+Python Software Foundation License Version 2.
+Starting with Python 3.8.6, examples, recipes, and other code in
+the documentation are dual licensed under the PSF License Version 2
+and the Zero-Clause BSD license.
+Some software incorporated into Python is under different licenses.
+The licenses are listed with code falling under that license.
+PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
+--------------------------------------------
+1. This LICENSE AGREEMENT is between the Python Software Foundation
+("PSF"), and the Individual or Organization ("Licensee") accessing and
+otherwise using this software ("Python") in source or binary form and
+its associated documentation.
+2. Subject to the terms and conditions of this License Agreement, PSF hereby
+grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
+analyze, test, perform and/or display publicly, prepare derivative works,
+distribute, and otherwise use Python alone or in any derivative version,
+provided, however, that PSF's License Agreement and PSF's notice of copyright,
+i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
+2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023 Python
+Software Foundation; All Rights Reserved" are retained in Python alone or in any
+derivative version prepared by Licensee.
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python.
+4. PSF is making Python available to Licensee on an "AS IS"
+basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+7. Nothing in this License Agreement shall be deemed to create any
+relationship of agency, partnership, or joint venture between PSF and
+Licensee. This License Agreement does not grant permission to use PSF
+trademarks or trade name in a trademark sense to endorse or promote
+products or services of Licensee, or any third party.
+8. By copying, installing or otherwise using Python, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
+-------------------------------------------
+BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
+1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
+office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
+Individual or Organization ("Licensee") accessing and otherwise using
+this software in source or binary form and its associated
+documentation ("the Software").
+2. Subject to the terms and conditions of this BeOpen Python License
+Agreement, BeOpen hereby grants Licensee a non-exclusive,
+royalty-free, world-wide license to reproduce, analyze, test, perform
+and/or display publicly, prepare derivative works, distribute, and
+otherwise use the Software alone or in any derivative version,
+provided, however, that the BeOpen Python License is retained in the
+Software, alone or in any derivative version prepared by Licensee.
+3. BeOpen is making the Software available to Licensee on an "AS IS"
+basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
+SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
+AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
+DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+5. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+6. This License Agreement shall be governed by and interpreted in all
+respects by the law of the State of California, excluding conflict of
+law provisions. Nothing in this License Agreement shall be deemed to
+create any relationship of agency, partnership, or joint venture
+between BeOpen and Licensee. This License Agreement does not grant
+permission to use BeOpen trademarks or trade names in a trademark
+sense to endorse or promote products or services of Licensee, or any
+third party. As an exception, the "BeOpen Python" logos available at
+http://www.pythonlabs.com/logos.html may be used according to the
+permissions granted on that web page.
+7. By copying, installing or otherwise using the software, Licensee
+agrees to be bound by the terms and conditions of this License
+Agreement.
+CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
+---------------------------------------
+1. This LICENSE AGREEMENT is between the Corporation for National
+Research Initiatives, having an office at 1895 Preston White Drive,
+Reston, VA 20191 ("CNRI"), and the Individual or Organization
+("Licensee") accessing and otherwise using Python 1.6.1 software in
+source or binary form and its associated documentation.
+2. Subject to the terms and conditions of this License Agreement, CNRI
+hereby grants Licensee a nonexclusive, royalty-free, world-wide
+license to reproduce, analyze, test, perform and/or display publicly,
+prepare derivative works, distribute, and otherwise use Python 1.6.1
+alone or in any derivative version, provided, however, that CNRI's
+License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
+1995-2001 Corporation for National Research Initiatives; All Rights
+Reserved" are retained in Python 1.6.1 alone or in any derivative
+version prepared by Licensee. Alternately, in lieu of CNRI's License
+Agreement, Licensee may substitute the following text (omitting the
+quotes): "Python 1.6.1 is made available subject to the terms and
+conditions in CNRI's License Agreement. This Agreement together with
+Python 1.6.1 may be located on the internet using the following
+unique, persistent identifier (known as a handle): 1895.22/1013. This
+Agreement may also be obtained from a proxy server on the internet
+using the following URL: http://hdl.handle.net/1895.22/1013".
+3. In the event Licensee prepares a derivative work that is based on
+or incorporates Python 1.6.1 or any part thereof, and wants to make
+the derivative work available to others as provided herein, then
+Licensee hereby agrees to include in any such work a brief summary of
+the changes made to Python 1.6.1.
+4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
+basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
+IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
+DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
+FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
+INFRINGE ANY THIRD PARTY RIGHTS.
+5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
+1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
+A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
+OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
+6. This License Agreement will automatically terminate upon a material
+breach of its terms and conditions.
+7. This License Agreement shall be governed by the federal
+intellectual property law of the United States, including without
+limitation the federal copyright law, and, to the extent such
+U.S. federal law does not apply, by the law of the Commonwealth of
+Virginia, excluding Virginia's conflict of law provisions.
+Notwithstanding the foregoing, with regard to derivative works based
+on Python 1.6.1 that incorporate non-separable material that was
+previously distributed under the GNU General Public License (GPL), the
+law of the Commonwealth of Virginia shall govern this License
+Agreement only as to issues arising under or with respect to
+Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
+License Agreement shall be deemed to create any relationship of
+agency, partnership, or joint venture between CNRI and Licensee. This
+License Agreement does not grant permission to use CNRI trademarks or
+trade name in a trademark sense to endorse or promote products or
+services of Licensee, or any third party.
+8. By clicking on the "ACCEPT" button where indicated, or by copying,
+installing or otherwise using Python 1.6.1, Licensee agrees to be
+bound by the terms and conditions of this License Agreement.
+ACCEPT
+CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
+--------------------------------------------------
+Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
+The Netherlands. All rights reserved.
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
+provided that the above copyright notice appear in all copies and that
+both that copyright notice and this permission notice appear in
+supporting documentation, and that the name of Stichting Mathematisch
+Centrum or CWI not be used in advertising or publicity pertaining to
+distribution of the software without specific, written prior
+permission.
+STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
+THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
+FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
+OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION
+----------------------------------------------------------------------
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted.
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
+OTHER TORTIOUS ACTION, ARISING O
\ No newline at end of file

Tools/VSS-GUI-Tool/README.md

+# Introduction 
+This repository contains the GUI tool for the selection and addition of signals to the Vehicle Signal Specification (VSS). The tool is used to select signals (data or parameters) from hundreds of signals defined in VSS bassed on the requirements of an application. 
+
+# Getting started 
+## Dependencies 
+1. The VSS GUI tool runs in Ubuntu (tested in Ubuntu 22.04). 
+2. The GUI tool is based on Python (tested in v3.10) and the following libraries: 
+    - Tkinter 
+    - Anytree
+    - Pyyaml 
+    - Screeninfo
+3. The GUI tool is also dependent on the .vspec files defined in the <a href="https://github.com/COVESA/vehicle_signal_specification">Vehicle Signal Specification</a> repository and the corresponding <a href="https://github.com/COVESA/vss-tools">VSS-tools</a> repository. 
+
+## Structure of the repository 
+1. [container](./container) - Contains the dockerfile recipe for the container image that is used to run the necessary scripts. 
+2. [scripts](./scripts) - Contains the necessary Python scripts with respect to the GUI tool. 
+3. [documentation](./documentation) - Contains the document explaining the features of the GUI tool. 
+
+## Running the script 
+1. Update the submodules linked to the repository: `git submodule update --init --recursive`. 
+2. Since the GUI tool has been tested upto v4.X of the VSS tools, navigate to the vss-tools repository located in the [vss] (./scripts/vss) folder and checkout to the required version: `git checkout v4.1.1`. 
+3. Build the container image by running the `build.sh` script in the [container](./container/) folder. 
+4. Run the container: `docker run -ti -e DISPLAY=$(hostname).local:0 -it vss_gui:latest`. In case of WSL, ensure that x11 forwarding is enabled and working. 
+5. Run the Python `vss_gui.py`script in `/app/gui` folder.  
+
+
+
+

Tools/VSS-GUI-Tool/container/README.md

+Run the ´build.sh´ script to create the container image that will be used for running the GUI script. 
\ No newline at end of file

Tools/VSS-GUI-Tool/container/build.sh

+cd .. 
+docker build -t vss_gui:latest -f container/vss_gui.dockerfile . 
\ No newline at end of file

Tools/VSS-GUI-Tool/container/vss_gui.dockerfile

+
+# Use the official Ubuntu 22.04 image as the base image
+FROM ubuntu:22.04
+
+# Set environment variables to avoid prompts during package installation
+ENV DEBIAN_FRONTEND=noninteractive
+
+# Update the package list and install necessary packages
+
+RUN apt-get update && apt-get install -y bash
+RUN apt-get install -y python3.10 python3.10-venv python3.10-dev python3-pip python3-tk && apt-get clean
+
+
+# Create a virtual environment for Python 3.10
+RUN python3.10 -m venv /opt/venv
+
+# Activate the virtual environment and install Python libraries
+RUN /opt/venv/bin/pip install --upgrade pip
+RUN /opt/venv/bin/pip install anytree pyyaml screeninfo graphql-core
+
+
+# Set the virtual environment as the default Python environment
+ENV PATH="/opt/venv/bin:$PATH"
+
+# Verify the installation
+RUN python --version && pip list
+
+# Set the working directory
+WORKDIR /app
+
+# Copy the files 
+COPY /scripts/gui/ /app/gui
+COPY /scripts/vss/ /app/vss
+
+

Tools/VSS-GUI-Tool/documentation/10_introduction.md

+# Introduction
+To allow easier integration and re-usable data elements, it is necessary to establish a standard that allows easier and efficient exchange of data. 
+Here, we adopt the Vehicle Signal Specification (VSS) introduced by the Connected Vehicle Systems Alliance (COVESA). 
+It is an industry relevant data standard developed as part of the Connected Vehicle Interface Initiative (CVII), a collaboration between COVESA and World Wide Web Consortium (W3C). 
+It is currently a global OEM-led joint development. 
+Though, the main aim of the VSS is to provide standard interfaces between vehicle and cloud, here VSS is extended to provide a standard definition of the data elements that are exchanged between software components (SWCs). 
+
+# Process overview
+Process to be followed with respect to the input interfaces of an application. 
+![Process flow for required/input interfaces of an application.](figures/process_flow_input.png)
+
+Process to be followed with respect to the output interfaces of an application. 
+![Process flow for output interfaces of an application](figures/process_flow_output.png)
\ No newline at end of file

Tools/VSS-GUI-Tool/documentation/20_steps.md

+# Steps to use the GUI tool 
+Execute the Python `vss_gui.py` script.
+
+## Signal selection 
+1. Provide the path for .vspec files `scripts\vss\vspec` through the *Browse Folder* button. 
+![Select .vspec file](figures/browse_folder.png)
+2. Search for the required signal in *Search* button. 
+![Search for signal](figures/search_signal.png)
+3. List of all signals that match the search criteria are listed in the *Search Data* pane along with the respective attributes. 
+![Search pane result](figures/search_pane_result.png)
+4. Select the required signals and move them to *Selected Data* pane by clicking the *Move to Selected* button. 
+![Move to selected](figures/move_to_selected.png)
+5. Similarly select the other required signals for the application and generate the .csv file by clicking the *Generate CSV File* button. 
+![Generate CSV](figures/generate_csv.png)
+
+## Signal creation 
+1. To create a new signal, select the *VSPEC_Update* button. 
+![VSPEC update](figures/update_vspec.png)
+2. *VSPEC File Manager* window will be opened and select the spec folder path to be updated using the *Browse Folder* button. 
+![Browse folder](figures/browse_spec_folder.png)
+3. Add signal/branch by selecting the *Add Row* button. It is necessary to select branch, type, and the relevant attributes of the signal. Provide also the username to save the data into files. 
+![Data saved](figures/data_saved.png)
\ No newline at end of file

Tools/VSS-GUI-Tool/documentation/30_openpoints.md

+# Open points/Issues  
+While updating .vspec files in *VSPEC File Manager*:
+1. After updating new attribute/sensor/actuator signals to vspec files, if *VSS_GUI* window is used to search the new signal it couldn’t be found due to incompatible/supported information of the signal. Due to this tool can get closed abnormally when path is browsed without any error notification.
+2. While browsing the path in any of the applications if the tool gets terminated, it could be due to newly updated signal information in one of the vspec files.
+3. *VSS_GUI* window must be configured with dynamic re-sizing according to the dimensions of screen. 
+4. In *VSPEC File Manager* format verification of *Allowed* column must be with respect to provided datatype. It is yet to be implemented.
+5. *VSS_GUI* and *VSPEC File Manager* windows cannot be closed once opened without providing the spec folder path, as tool will search for the path to delete the internal file created. So, the windows can be closed only after providing some path.
+6. Alternative: Close the log window and then try closing the tool windows hassle free closure.
+7. The dropdown option for unit in the *VSPEC File Manager* is currently not fully functional, as it does not allow scrolling through the list.