WP6-26 - Revision history

Grolleaue: /* Introduction */

2023-03-10T08:49:43Z

Introduction

← Older revision		Revision as of 08:49, 10 March 2023
Line 18:		Line 18:
	\|-		\|-
	\| TRL \|\| 5		\| TRL \|\| 5
			\|-
			\| Contact \|\| evillar at teisa.unican.es
	\|}		\|}

Raulgv: /* Detailed Description */

2023-02-17T10:05:52Z

Detailed Description

← Older revision		Revision as of 10:05, 17 February 2023
Line 30:		Line 30:
	SoSIM covers the following states in the mechatronic V-Cycle of Figure 2:		SoSIM covers the following states in the mechatronic V-Cycle of Figure 2:

	[[File:wp6-26-D-01.png\|frame\|~~center~~\|Figure 2 - S3D-SoSIM V cycle coverage]]		[[File:wp6-26-D-01.png\|frame\|raight\|Figure 2 - S3D-SoSIM V cycle coverage]]

	2. System Design		2. System Design

Raulgv: /* Detailed Description */

2023-02-17T10:04:32Z

Detailed Description

← Older revision		Revision as of 10:04, 17 February 2023
Line 29:		Line 29:

	SoSIM covers the following states in the mechatronic V-Cycle of Figure 2:		SoSIM covers the following states in the mechatronic V-Cycle of Figure 2:

			[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]

	2. System Design		2. System Design
Line 55:		Line 57:

	15. System Acceptance Verification		15. System Acceptance Verification

	~~[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]~~

	The improvement provided by SoSIM comes from the fact that the use of virtual models of the system simplifies simulation-based DSE, which greatly reduces the time required to select the most appropriate solution [2]. However, as the information about the system and its components evolve along the design process, so should their models and, in general, the infrastructure required for their simulation. As a result, different simulation levels must be considered during the different steps of the design and verification process. Table 1 shows the four simulation levels considered for the functional components:		The improvement provided by SoSIM comes from the fact that the use of virtual models of the system simplifies simulation-based DSE, which greatly reduces the time required to select the most appropriate solution [2]. However, as the information about the system and its components evolve along the design process, so should their models and, in general, the infrastructure required for their simulation. As a result, different simulation levels must be considered during the different steps of the design and verification process. Table 1 shows the four simulation levels considered for the functional components:

Raulgv: /* Detailed Description */

2023-02-17T09:19:31Z

Detailed Description

← Older revision		Revision as of 09:19, 17 February 2023
Line 30:		Line 30:
	SoSIM covers the following states in the mechatronic V-Cycle of Figure 2:		SoSIM covers the following states in the mechatronic V-Cycle of Figure 2:

	# System Design		2. System Design
	# Mechanical Analysis and Design
	# IT Analysis and Design		3. Mechanical Analysis and Design
	# SW Analysis and Design
	# HW Analysis and Design		4. IT Analysis and Design
	# SW Detailed Design
	# SW Component Verification		5. SW Analysis and Design
	# SW Integration and Verification
	# HW Integration and Verification		6. HW Analysis and Design
	~~# IT~~ Integration and Verification
	~~# Mechanic~~ Integration and Verification		7. SW Detailed Design
	# System Integration and Verification
	# System Acceptance Verification		9. SW Component Verification

			10. SW Integration and Verification

			11. HW Integration and Verification

			12. Mechanic Integration and Verification

			13. IT Integration and Verification

			14. System Integration and Verification

			15. System Acceptance Verification

	[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]		[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]

Raulgv: /* Detailed Description */

2023-02-17T08:48:33Z

Detailed Description

← Older revision		Revision as of 08:48, 17 February 2023
Line 43:		Line 43:
	# System Integration and Verification		# System Integration and Verification
	# System Acceptance Verification		# System Acceptance Verification

			[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]

	The improvement provided by SoSIM comes from the fact that the use of virtual models of the system simplifies simulation-based DSE, which greatly reduces the time required to select the most appropriate solution [2]. However, as the information about the system and its components evolve along the design process, so should their models and, in general, the infrastructure required for their simulation. As a result, different simulation levels must be considered during the different steps of the design and verification process. Table 1 shows the four simulation levels considered for the functional components:		The improvement provided by SoSIM comes from the fact that the use of virtual models of the system simplifies simulation-based DSE, which greatly reduces the time required to select the most appropriate solution [2]. However, as the information about the system and its components evolve along the design process, so should their models and, in general, the infrastructure required for their simulation. As a result, different simulation levels must be considered during the different steps of the design and verification process. Table 1 shows the four simulation levels considered for the functional components:
Line 78:		Line 80:

	Regarding the simulation of the drones, four different models are considered. Let’s consider the command “move to X/Y/Z”. A minimal implementation will estimate the path and the movement time considering constant horizontal and vertical speed values, the power consumption, and will perform the movement in a single step (FN). In many cases, a more detailed model for the drone(s) is required. An autopilot and a physical simulator are needed.		Regarding the simulation of the drones, four different models are considered. Let’s consider the command “move to X/Y/Z”. A minimal implementation will estimate the path and the movement time considering constant horizontal and vertical speed values, the power consumption, and will perform the movement in a single step (FN). In many cases, a more detailed model for the drone(s) is required. An autopilot and a physical simulator are needed.
	~~[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]~~

	In this case, the full code (FC/FD) will generate all the signals to the motors required by the physical simulator to reach the final destination, including the estimation of all the intermediate positions, the actual time to reach them, the corresponding power consumption, angles and orientations.		In this case, the full code (FC/FD) will generate all the signals to the motors required by the physical simulator to reach the final destination, including the estimation of all the intermediate positions, the actual time to reach them, the corresponding power consumption, angles and orientations.

Raulgv: /* Detailed Description */

2023-01-12T10:57:41Z

Detailed Description

← Older revision		Revision as of 10:57, 12 January 2023
Line 78:		Line 78:

	Regarding the simulation of the drones, four different models are considered. Let’s consider the command “move to X/Y/Z”. A minimal implementation will estimate the path and the movement time considering constant horizontal and vertical speed values, the power consumption, and will perform the movement in a single step (FN). In many cases, a more detailed model for the drone(s) is required. An autopilot and a physical simulator are needed.		Regarding the simulation of the drones, four different models are considered. Let’s consider the command “move to X/Y/Z”. A minimal implementation will estimate the path and the movement time considering constant horizontal and vertical speed values, the power consumption, and will perform the movement in a single step (FN). In many cases, a more detailed model for the drone(s) is required. An autopilot and a physical simulator are needed.
	[[File:wp6-~~25_DD_01~~.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]		[[File:wp6-26-D-01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]

	In this case, the full code (FC/FD) will generate all the signals to the motors required by the physical simulator to reach the final destination, including the estimation of all the intermediate positions, the actual time to reach them, the corresponding power consumption, angles and orientations.		In this case, the full code (FC/FD) will generate all the signals to the motors required by the physical simulator to reach the final destination, including the estimation of all the intermediate positions, the actual time to reach them, the corresponding power consumption, angles and orientations.

Raulgv: /* Detailed Description */

2023-01-12T08:27:21Z

Detailed Description

← Older revision		Revision as of 08:27, 12 January 2023
Line 78:		Line 78:

	Regarding the simulation of the drones, four different models are considered. Let’s consider the command “move to X/Y/Z”. A minimal implementation will estimate the path and the movement time considering constant horizontal and vertical speed values, the power consumption, and will perform the movement in a single step (FN). In many cases, a more detailed model for the drone(s) is required. An autopilot and a physical simulator are needed.		Regarding the simulation of the drones, four different models are considered. Let’s consider the command “move to X/Y/Z”. A minimal implementation will estimate the path and the movement time considering constant horizontal and vertical speed values, the power consumption, and will perform the movement in a single step (FN). In many cases, a more detailed model for the drone(s) is required. An autopilot and a physical simulator are needed.
	[[File:wp6-~~26-D-01~~.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]		[[File:wp6-25_DD_01.png\|frame\|center\|Figure 2 - S3D-SoSIM V cycle coverage]]

	In this case, the full code (FC/FD) will generate all the signals to the motors required by the physical simulator to reach the final destination, including the estimation of all the intermediate positions, the actual time to reach them, the corresponding power consumption, angles and orientations.		In this case, the full code (FC/FD) will generate all the signals to the motors required by the physical simulator to reach the final destination, including the estimation of all the intermediate positions, the actual time to reach them, the corresponding power consumption, angles and orientations.

Raulgv: /* Introduction */

2023-01-11T15:45:44Z

Introduction

← Older revision		Revision as of 15:45, 11 January 2023
Line 7:		Line 7:
	\| Levels \|\| Tool, Platform		\| Levels \|\| Tool, Platform
	\|-		\|-
	\| Require \|\| Linux Ubuntu 18.04 ~~LTE~~		\| Require \|\| Linux Ubuntu 18.04
	\|-		\|-
	\| Provide \|\| Timing/Energy Simulation		\| Provide \|\| Timing/Energy Simulation

Raulgv: /* Introduction */

2023-01-11T14:15:48Z

Introduction

← Older revision		Revision as of 14:15, 11 January 2023
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	{\|class="wikitable"		{\|class="wikitable"
	\| ID\|\| WP6-		\| ID\|\| WP6-26
	\|-		\|-
	\| Contributor \|\| UNICAN		\| Contributor \|\| UNICAN

Raulgv: /* Introduction */

2023-01-11T14:14:12Z

Introduction

← Older revision		Revision as of 14:14, 11 January 2023
Line 11:		Line 11:
	\| Provide \|\| Timing/Energy Simulation		\| Provide \|\| Timing/Energy Simulation
	\|-		\|-
	\| Input \|\| ~~Platform Independent Model, Platform Description Model, Functional~~ code		\| Input \|\| XML system description & functional code
	\|-		\|-
	\| Output \|\| Functional & performance simulation results		\| Output \|\| Functional & performance simulation results