RTE6 - Ablation Tests - Revision history

Pdturney: Reverted edits by Creek (talk) to last revision by Amarchetti

2012-06-25T11:18:30Z

Reverted edits by Creek (talk) to last revision by Amarchetti

← Older revision		Revision as of 11:18, 25 June 2012
Line 1:		Line 1:
	The following table lists the results of the ablation tests submitted by participants to RTE6 .<br>		The following table lists the results of the ablation tests submitted by participants to RTE6 .<br>
	The exploratory effort started in RTE5 as a mandatory track, was not only reiterated in RTE6, but also extended to tools.		The exploratory effort started in RTE5 as a mandatory track, was not only reiterated in RTE6, but also extended to tools.
	The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the ~~[http://www.thai-sbobet.com sbo]~~normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>		The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>
	The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br>		The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br>
	If the ablated resource is highlighted in yellow, it is a tool, otherwise is a knowledge resource.<br>		If the ablated resource is highlighted in yellow, it is a tool, otherwise is a knowledge resource.<br>

Creek at 09:22, 25 June 2012

2012-06-25T09:22:04Z

← Older revision		Revision as of 09:22, 25 June 2012
Line 1:		Line 1:
	The following table lists the results of the ablation tests submitted by participants to RTE6 .<br>		The following table lists the results of the ablation tests submitted by participants to RTE6 .<br>
	The exploratory effort started in RTE5 as a mandatory track, was not only reiterated in RTE6, but also extended to tools.		The exploratory effort started in RTE5 as a mandatory track, was not only reiterated in RTE6, but also extended to tools.
	The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>		The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the [http://www.thai-sbobet.com sbo]normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>
	The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br>		The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br>
	If the ablated resource is highlighted in yellow, it is a tool, otherwise is a knowledge resource.<br>		If the ablated resource is highlighted in yellow, it is a tool, otherwise is a knowledge resource.<br>

Amarchetti at 16:22, 3 February 2011

2011-02-03T16:22:03Z

← Older revision		Revision as of 16:22, 3 February 2011
Line 223:		Line 223:

	\|- bgcolor="#FFFFF" "align="left"		\|- bgcolor="#FFFFF" "align="left"
	\| ~~Shalmanesar~~ Parser		\| Shalmaneser Parser
	\| Sangyan1_abl-1		\| Sangyan1_abl-1
	\| style="text-align: center;"\| -1.76		\| style="text-align: center;"\| -1.76
	\| style="text-align: center;"\| This ablation run was executed with the ~~Shalmanesar~~ parser ablated from our system. Our system uses the ~~Shalmanesar~~ Parser for Framenet frame assignment.		\| style="text-align: center;"\| This ablation run was executed with the Shalmaneser parser ablated from our system. Our system uses the Shalmaneser Parser for Framenet frame assignment.
	Our system required minor tweaking of the source code in order ablate ~~Shalmanesar~~ Parser.		Our system required minor tweaking of the source code in order ablate Shalmaneser Parser.

	\|- bgcolor="#ECECEC" "align="left"		\|- bgcolor="#ECECEC" "align="left"

Amarchetti at 16:17, 3 February 2011

2011-02-03T16:17:45Z

← Older revision		Revision as of 16:17, 3 February 2011
Line 1:		Line 1:
	The following table lists the results of the ablation tests ~~(a mandatory track since the RTE5 campaign),~~ submitted by participants to RTE6 .<br>		The following table lists the results of the ablation tests submitted by participants to RTE6 .<br>
			The exploratory effort started in RTE5 as a mandatory track, was not only reiterated in RTE6, but also extended to tools.
	The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>		The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>
	The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br><br>		The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br>
			If the ablated resource is highlighted in yellow, it is a tool, otherwise is a knowledge resource.<br>


	Participants are kindly invited to check if all the inserted information is correct and complete.		Participants are kindly invited to check if all the inserted information is correct and complete.

Amarchetti at 15:41, 3 February 2011

2011-02-03T15:41:27Z

← Older revision		Revision as of 15:41, 3 February 2011
Line 1:		Line 1:
	The following table lists the results of the ablation tests (a mandatory track since the RTE5 campaign), submitted by participants to RTE6 .<br>		The following table lists the results of the ablation tests (a mandatory track since the RTE5 campaign), submitted by participants to RTE6 .<br>
	The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column ~~present~~ the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system~~. The third refers to the score obtained in the 2-way task, the fourth to that obtained in the 3-way task. For all the runs submitted as 3-way, also the 2-way derived accuracy has been calculated~~.<br>		The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column presents the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system.<br>
	The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br><br>		The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br><br>

Amarchetti at 15:40, 3 February 2011

2011-02-03T15:40:31Z

← Older revision		Revision as of 15:40, 3 February 2011
Line 1:		Line 1:
	The following table lists the results of the ablation tests (a mandatory track since the RTE5 campaign), submitted by participants to RTE6 .<br><br>		The following table lists the results of the ablation tests (a mandatory track since the RTE5 campaign), submitted by participants to RTE6 .<br>
			The first column contains the specific resources which have been ablated.<br>The second column lists the Team Run in the form ''[name_of_the_Team][number_of_the_submitted_run].[submission_task]'' (e.g. BIU1.2way, Boeing3.3way).<br>The third column present the normalized difference between the accuracy of the complete system run and the accuracy of the ablation run (i.e. the output of the complete system without the ablated resource), showing the impact of the resource on the performance of the system. The third refers to the score obtained in the 2-way task, the fourth to that obtained in the 3-way task. For all the runs submitted as 3-way, also the 2-way derived accuracy has been calculated.<br>
			The fourth column contains a brief description of the specific usage of the resource. It is based on the information provided both in the "readme" files submitted together with the ablation tests and in the system reports published in the RTE6 proceedings.<br><br>

Amarchetti at 13:31, 3 February 2011

2011-02-03T13:31:20Z

@@ Line 316: / Line 316: @@
 | style="text-align: center;"| -0.98
 | style="text-align: center;"| Run 3 without DIRT.
 |}
 <br>

Amarchetti at 13:25, 3 February 2011

2011-02-03T13:25:18Z

@@ Line 281: / Line 281: @@
 | style="text-align: center;"| The resource that has been ablated is VerbOcean.
 |}
 <br>

Amarchetti at 13:18, 3 February 2011

2011-02-03T13:18:39Z

@@ Line 262: / Line 262: @@
 | style="text-align: center;"| 18.28
 | style="text-align: center;"| Only NEs on WN 3.0
 |}

Amarchetti at 13:10, 3 February 2011

2011-02-03T13:10:27Z

@@ Line 225: / Line 225: @@
 | style="text-align: center;"| This ablation run was executed with the Shalmanesar parser ablated from our system. Our system uses the Shalmanesar Parser for Framenet frame assignment.
 Our system required minor tweaking of the source code in order ablate Shalmanesar Parser.
 |}