CodeProfiling - Revision history

DavidA at 08:38, 2 July 2019

2019-07-02T08:38:13Z

← Older revision		Revision as of 08:38, 2 July 2019
Line 1:		Line 1:
	~~<sidebar>Sidebar: Flowcode Help Overview:Simulation</sidebar>~~


	__TOC__		__TOC__

2018-08-01T10:52:31Z

← Older revision		Revision as of 10:52, 1 August 2018
Line 1:		Line 1:
	<sidebar>Sidebar: Flowcode Help Overview:~~ToolsViews~~</sidebar>		<sidebar>Sidebar: Flowcode Help Overview:Simulation</sidebar>

2016-07-07T11:00:06Z

← Older revision		Revision as of 11:00, 7 July 2016
Line 12:		Line 12:
	Code profiling is activated from the top toolbar with the following icon [[File:CodeProfilingIcon.png]] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.		Code profiling is activated from the top toolbar with the following icon [[File:CodeProfilingIcon.png]] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.


			===Using Code Profiling===
	Here we can see that the 'yes' branch of the switch statement has not been executed, and so the 'output 1 to B0' icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.		Here we can see that the 'yes' branch of the switch statement has not been executed, and so the 'output 1 to B0' icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.
	[[File:CodeProfilingEx1a.png]]		[[File:CodeProfilingEx1a.png]]

2016-07-07T10:59:39Z

← Older revision		Revision as of 10:59, 7 July 2016
Line 11:		Line 11:
	===Activating Code Profiling===		===Activating Code Profiling===
	Code profiling is activated from the top toolbar with the following icon [[File:CodeProfilingIcon.png]] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.		Code profiling is activated from the top toolbar with the following icon [[File:CodeProfilingIcon.png]] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.



	Here we can see that the 'yes' branch of the switch statement has not been executed, and so the 'output 1 to B0' icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.		Here we can see that the 'yes' branch of the switch statement has not been executed, and so the 'output 1 to B0' icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.

2016-07-07T10:59:18Z

← Older revision		Revision as of 10:59, 7 July 2016
Line 6:		Line 6:

	===Code Profiling Introduction===		===Code Profiling Introduction===
	Code profiling is a tool for identifying bugs within code and also alerting programmers of redundant code. ~~When users simulate their program,~~ Flowcode will highlight ~~the~~ icons ~~that~~ are 'hit', the frequency at which they are hit, and also ~~notiy~~ which icons have never been hit.		Code profiling is a tool for identifying bugs within code and also alerting programmers of redundant code during simulation. Flowcode will highlight any icons which are 'hit', the frequency at which they are hit, and also notify which icons have never been hit.


Line 14:		Line 14:


	Here we can see that the 'yes' branch of the switch statement has not been executed, and so the output B0 icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.		Here we can see that the 'yes' branch of the switch statement has not been executed, and so the 'output 1 to B0' icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.
	[[File:CodeProfilingEx1a.png]]		[[File:CodeProfilingEx1a.png]]

2016-07-07T10:56:00Z

← Older revision		Revision as of 10:56, 7 July 2016
Line 10:		Line 10:

	===Activating Code Profiling===		===Activating Code Profiling===
	Code profiling is activated from the top toolbar with the following icon [File:CodeProfilingIcon.png] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.		Code profiling is activated from the top toolbar with the following icon [[File:CodeProfilingIcon.png]] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.

2016-07-07T10:55:52Z

← Older revision		Revision as of 10:55, 7 July 2016
Line 10:		Line 10:

	===Activating Code Profiling===		===Activating Code Profiling===
	Code profiling is activated from the top toolbar with the following icon File:CodeProfilingIcon.png Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.		Code profiling is activated from the top toolbar with the following icon [File:CodeProfilingIcon.png] Once activated, run the simulation as normal and you will see the glow appear around icons that have been hit. A cross will appear over any icons that have not been executed.

2016-07-07T10:55:10Z

← Older revision		Revision as of 10:55, 7 July 2016
Line 19:		Line 19:


	Here we can see that the switch has been pressed now. We know this as the cross has disappeared, and the icon has turned blue. The blue is a visual representation of how frequently this icon has been executed. Red icons are hit every time, and the more blue they turn, the less ~~frequenct~~ they are executed.		Here we can see that the switch has been pressed now. We know this as the cross has disappeared, and the icon has turned blue. The blue is a visual representation of how frequently this icon has been executed. Red icons are hit every time, and the more blue they turn, the less frequently they are executed.

	[[File:CodeProfilingEx1b.png]]		[[File:CodeProfilingEx1b.png]]

2016-07-07T10:54:43Z

← Older revision		Revision as of 10:54, 7 July 2016
Line 20:		Line 20:

	Here we can see that the switch has been pressed now. We know this as the cross has disappeared, and the icon has turned blue. The blue is a visual representation of how frequently this icon has been executed. Red icons are hit every time, and the more blue they turn, the less frequenct they are executed.		Here we can see that the switch has been pressed now. We know this as the cross has disappeared, and the icon has turned blue. The blue is a visual representation of how frequently this icon has been executed. Red icons are hit every time, and the more blue they turn, the less frequenct they are executed.

	[[File:CodeProfilingEx1b.png]]		[[File:CodeProfilingEx1b.png]]

2016-07-07T10:54:19Z

@@ Line 13: / Line 13: @@
-[[File:CodeProfilingEx1a.png|right]]
 Here we can see that the 'yes' branch of the switch statement has not been executed, and so the output B0 icon, has also not been executed. This could be due to a bug in the code, or as in this example, the switch simply hasn't been pressed yet.
+[[File:CodeProfilingEx1a.png]]
 Here we can see that the switch has been pressed now. We know this as the cross has disappeared, and the icon has turned blue. The blue is a visual representation of how frequently this icon has been executed. Red icons are hit every time, and the more blue they turn, the less frequenct they are executed.