<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Igupta</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Igupta"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Igupta"/>
	<updated>2026-09-08T05:18:03Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140869</id>
		<title>CSC/ECE 517 Fall 2021 - E2164. Heatgrid fixes and improvements</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140869"/>
		<updated>2021-11-04T02:36:18Z</updated>

		<summary type="html">&lt;p&gt;Igupta: /* Refactoring */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Project Background ==&lt;br /&gt;
Heatgrid is the page where instructor can visit and view the work done by participant using Reviews, Author Feedbacks and Meta Reviews. This one web page displays all the evaluations done by peers of the participant for his project. The page is displayed in the format of table with colors. The columns in the table can be sorted with the requirement of the project. Heatgrid shows scores assigned by reviewers on individual rubric items for participant. &lt;br /&gt;
&lt;br /&gt;
===What is wrong with it===&lt;br /&gt;
It is called from Instructor's &amp;quot;Assign Grades&amp;quot; function and student's view scores functions. But , there are issues that students are reviews themselves. Question is about Are reviews getting assigned correctly? Assignment of metric is also wrong at some places&lt;br /&gt;
&lt;br /&gt;
=Issue 1=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue #2019===&lt;br /&gt;
Questions whether the reviewers are correctly identified.  In one case, a student was shown as reviewing his/her team, which is impossible.  Also write tests so that if this bug occurs again, we will be informed.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current review system implementation, the instructor has the ability to select or deselect the &amp;quot;Allow Self Reviews?&amp;quot; checkbox from the &amp;quot;Review Strategy&amp;quot; tab of the Edit Assignment page. On deselecting this checkbox, a student will not be able to review his/her own work.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following images show how this functionality works currently:&lt;br /&gt;
&lt;br /&gt;
[[File:SelfReviewCheckbox.png|1200px|thumb|left]] &lt;br /&gt;
&lt;br /&gt;
[[File:AssignReviewer.png|1800px|thumb|center]]&lt;br /&gt;
The instructor will get the error &amp;quot;You cannot assign this student to review his/her own artifact.&amp;quot; when an attempt to add a student as a reviewer to his/her own assignment is made.&lt;br /&gt;
&lt;br /&gt;
=== Control Flow ===&lt;br /&gt;
[[File:Issue1CF.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Observations ==&lt;br /&gt;
Whenever an instructor assigns a reviewer for an assignment of a team, there is already a check present and it is not allowing instructor to assign the team member of the team for the review.&lt;br /&gt;
&lt;br /&gt;
[[File:CheckReviewer.png]]&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is disabled, then the reviewer should not be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is enabled, then the reviewer should be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on self-review and grades section. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/_review_strategy.html.erb:- Here, the checkbox of &amp;quot;Allow Self Review?&amp;quot; is written. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Grades helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; spec/controllers/review_mapping_controller.rb:- Adding test cases for checking whether the reviewer can self-review if the &amp;quot;Allow Self Review?&amp;quot; checkkbox is disabled and the vice-versa too. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Issue 2=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue#1869===&lt;br /&gt;
Notes that there is a “metric-1” column in the review report, but it doesn’t say what the metric is. Please figure out what the metric is, and change the column header accordingly.  However, the intent was that eventually an instructor would be allowed to select a metric to be shown on the heatgrid.  So, somewhere in the UI for creating/editing an assignment, there should be a way for the instructor to select a metric from a dropdown list.  You don’t have to add any more metrics to this list other than the one that is currently displayed, just create a mechanism for adding metrics in the future.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current implementation, the columns in the heatgrid table are static. The &amp;quot;metric-1&amp;quot; column in the table represents the count of comments for the respective question which have a word count greater than 10. On hovering over the column name, the correct information is displayed but the name itself does not make the information apparent at first glance.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following image captures how the heatgrid is currently being displayed:&lt;br /&gt;
&lt;br /&gt;
[[File:Summary Report.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
== Refactoring ==&lt;br /&gt;
&lt;br /&gt;
The header for the metric-1 column should be changed and it should display an appropriate name for the metric.&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/_view_heatgrid.html.erb:- View file for the Heat Grid. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/view_team.html.erb:- View file for the Team. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Focussing on the view_heatgrid function and  of the helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on the populate_view_model function of the controller file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/models/vm_question_response.rb:- Focussing on the number_of_comments_greater_than_10_words function of the model file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; Capybara Test cases for the heat grid view and team view should be added to check if the dropdown is visible as expected. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Spec test cases should be added for the grades controller should be added to verify the responses returned from the controller. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Unit test cases will be added to verify the logic of the number_of_comments_greater_than_10_words method of the vm_question_response model. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Important Links =&lt;br /&gt;
* GitHub repository link: https://github.com/ShlokSayani/expertiza&lt;br /&gt;
* Project Description Document: https://docs.google.com/document/d/1slx4HPIbgTH-psIKMSCF-HDF9brxf-FuYhzVT9ZiIrM/edit#heading=h.tqdrrd12xs4x&lt;br /&gt;
&lt;br /&gt;
= Team =&lt;br /&gt;
&lt;br /&gt;
* Shlok Sayani (sdsayani)&lt;br /&gt;
&lt;br /&gt;
* Hardik Udeshi (hvudeshi)&lt;br /&gt;
&lt;br /&gt;
* Isha Gupta (igupta)&lt;br /&gt;
&lt;br /&gt;
* Manish Shinde (msshinde)&lt;/div&gt;</summary>
		<author><name>Igupta</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140867</id>
		<title>CSC/ECE 517 Fall 2021 - E2164. Heatgrid fixes and improvements</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140867"/>
		<updated>2021-11-04T02:32:04Z</updated>

		<summary type="html">&lt;p&gt;Igupta: /* Observations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Project Background ==&lt;br /&gt;
Heatgrid is the page where instructor can visit and view the work done by participant using Reviews, Author Feedbacks and Meta Reviews. This one web page displays all the evaluations done by peers of the participant for his project. The page is displayed in the format of table with colors. The columns in the table can be sorted with the requirement of the project. Heatgrid shows scores assigned by reviewers on individual rubric items for participant. &lt;br /&gt;
&lt;br /&gt;
===What is wrong with it===&lt;br /&gt;
It is called from Instructor's &amp;quot;Assign Grades&amp;quot; function and student's view scores functions. But , there are issues that students are reviews themselves. Question is about Are reviews getting assigned correctly? Assignment of metric is also wrong at some places&lt;br /&gt;
&lt;br /&gt;
=Issue 1=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue #2019===&lt;br /&gt;
Questions whether the reviewers are correctly identified.  In one case, a student was shown as reviewing his/her team, which is impossible.  Also write tests so that if this bug occurs again, we will be informed.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current review system implementation, the instructor has the ability to select or deselect the &amp;quot;Allow Self Reviews?&amp;quot; checkbox from the &amp;quot;Review Strategy&amp;quot; tab of the Edit Assignment page. On deselecting this checkbox, a student will not be able to review his/her own work.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following images show how this functionality works currently:&lt;br /&gt;
&lt;br /&gt;
[[File:SelfReviewCheckbox.png|1200px|thumb|left]] &lt;br /&gt;
&lt;br /&gt;
[[File:AssignReviewer.png|1800px|thumb|center]]&lt;br /&gt;
The instructor will get the error &amp;quot;You cannot assign this student to review his/her own artifact.&amp;quot; when an attempt to add a student as a reviewer to his/her own assignment is made.&lt;br /&gt;
&lt;br /&gt;
=== Control Flow ===&lt;br /&gt;
[[File:Issue1CF.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Observations ==&lt;br /&gt;
Whenever an instructor assigns a reviewer for an assignment of a team, there is already a check present and it is not allowing instructor to assign the team member of the team for the review.&lt;br /&gt;
&lt;br /&gt;
[[File:CheckReviewer.png]]&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is disabled, then the reviewer should not be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is enabled, then the reviewer should be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on self-review and grades section. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/_review_strategy.html.erb:- Here, the checkbox of &amp;quot;Allow Self Review?&amp;quot; is written. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Grades helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; spec/controllers/review_mapping_controller.rb:- Adding test cases for checking whether the reviewer can self-review if the &amp;quot;Allow Self Review?&amp;quot; checkkbox is disabled and the vice-versa too. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Issue 2=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue#1869===&lt;br /&gt;
Notes that there is a “metric-1” column in the review report, but it doesn’t say what the metric is. Please figure out what the metric is, and change the column header accordingly.  However, the intent was that eventually an instructor would be allowed to select a metric to be shown on the heatgrid.  So, somewhere in the UI for creating/editing an assignment, there should be a way for the instructor to select a metric from a dropdown list.  You don’t have to add any more metrics to this list other than the one that is currently displayed, just create a mechanism for adding metrics in the future.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current implementation, the columns in the heatgrid table are static. The &amp;quot;metric-1&amp;quot; column in the table represents the count of comments for the respective question which have a word count greater than 10. On hovering over the column name, the correct information is displayed but the name itself does not make the information apparent at first glance.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following image captures how the heatgrid is currently being displayed:&lt;br /&gt;
&lt;br /&gt;
[[File:Summary Report.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
== Refactoring ==&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/_view_heatgrid.html.erb:- View file for the Heat Grid. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/view_team.html.erb:- View file for the Team. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Focussing on the view_heatgrid function and  of the helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on the populate_view_model function of the controller file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/models/vm_question_response.rb:- Focussing on the number_of_comments_greater_than_10_words function of the model file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; Capybara Test cases for the heat grid view and team view should be added to check if the dropdown is visible as expected. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Spec test cases should be added for the grades controller should be added to verify the responses returned from the controller. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Unit test cases will be added to verify the logic of the number_of_comments_greater_than_10_words method of the vm_question_response model. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Important Links =&lt;br /&gt;
* GitHub repository link: https://github.com/ShlokSayani/expertiza&lt;br /&gt;
* Project Description Document: https://docs.google.com/document/d/1slx4HPIbgTH-psIKMSCF-HDF9brxf-FuYhzVT9ZiIrM/edit#heading=h.tqdrrd12xs4x&lt;br /&gt;
&lt;br /&gt;
= Team =&lt;br /&gt;
&lt;br /&gt;
* Shlok Sayani (sdsayani)&lt;br /&gt;
&lt;br /&gt;
* Hardik Udeshi (hvudeshi)&lt;br /&gt;
&lt;br /&gt;
* Isha Gupta (igupta)&lt;br /&gt;
&lt;br /&gt;
* Manish Shinde (msshinde)&lt;/div&gt;</summary>
		<author><name>Igupta</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=File:CheckReviewer.png&amp;diff=140864</id>
		<title>File:CheckReviewer.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=File:CheckReviewer.png&amp;diff=140864"/>
		<updated>2021-11-04T02:31:19Z</updated>

		<summary type="html">&lt;p&gt;Igupta: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Igupta</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140863</id>
		<title>CSC/ECE 517 Fall 2021 - E2164. Heatgrid fixes and improvements</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140863"/>
		<updated>2021-11-04T02:31:06Z</updated>

		<summary type="html">&lt;p&gt;Igupta: /* Observations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Project Background ==&lt;br /&gt;
Heatgrid is the page where instructor can visit and view the work done by participant using Reviews, Author Feedbacks and Meta Reviews. This one web page displays all the evaluations done by peers of the participant for his project. The page is displayed in the format of table with colors. The columns in the table can be sorted with the requirement of the project. Heatgrid shows scores assigned by reviewers on individual rubric items for participant. &lt;br /&gt;
&lt;br /&gt;
===What is wrong with it===&lt;br /&gt;
It is called from Instructor's &amp;quot;Assign Grades&amp;quot; function and student's view scores functions. But , there are issues that students are reviews themselves. Question is about Are reviews getting assigned correctly? Assignment of metric is also wrong at some places&lt;br /&gt;
&lt;br /&gt;
=Issue 1=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue #2019===&lt;br /&gt;
Questions whether the reviewers are correctly identified.  In one case, a student was shown as reviewing his/her team, which is impossible.  Also write tests so that if this bug occurs again, we will be informed.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current review system implementation, the instructor has the ability to select or deselect the &amp;quot;Allow Self Reviews?&amp;quot; checkbox from the &amp;quot;Review Strategy&amp;quot; tab of the Edit Assignment page. On deselecting this checkbox, a student will not be able to review his/her own work.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following images show how this functionality works currently:&lt;br /&gt;
&lt;br /&gt;
[[File:SelfReviewCheckbox.png|1200px|thumb|left]] &lt;br /&gt;
&lt;br /&gt;
[[File:AssignReviewer.png|1800px|thumb|center]]&lt;br /&gt;
The instructor will get the error &amp;quot;You cannot assign this student to review his/her own artifact.&amp;quot; when an attempt to add a student as a reviewer to his/her own assignment is made.&lt;br /&gt;
&lt;br /&gt;
=== Control Flow ===&lt;br /&gt;
[[File:Issue1CF.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Observations ==&lt;br /&gt;
Whenever an instructor assigns a reviewer for an assignment of a team, there is already a check present and it is not allowing instructor to assign the team member of the team for the review.&lt;br /&gt;
&lt;br /&gt;
[[File:checkReviewer.png]]&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is disabled, then the reviewer should not be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is enabled, then the reviewer should be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on self-review and grades section. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/_review_strategy.html.erb:- Here, the checkbox of &amp;quot;Allow Self Review?&amp;quot; is written. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Grades helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; spec/controllers/review_mapping_controller.rb:- Adding test cases for checking whether the reviewer can self-review if the &amp;quot;Allow Self Review?&amp;quot; checkkbox is disabled and the vice-versa too. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Issue 2=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue#1869===&lt;br /&gt;
Notes that there is a “metric-1” column in the review report, but it doesn’t say what the metric is. Please figure out what the metric is, and change the column header accordingly.  However, the intent was that eventually an instructor would be allowed to select a metric to be shown on the heatgrid.  So, somewhere in the UI for creating/editing an assignment, there should be a way for the instructor to select a metric from a dropdown list.  You don’t have to add any more metrics to this list other than the one that is currently displayed, just create a mechanism for adding metrics in the future.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current implementation, the columns in the heatgrid table are static. The &amp;quot;metric-1&amp;quot; column in the table represents the count of comments for the respective question which have a word count greater than 10. On hovering over the column name, the correct information is displayed but the name itself does not make the information apparent at first glance.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following image captures how the heatgrid is currently being displayed:&lt;br /&gt;
&lt;br /&gt;
[[File:Summary Report.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
== Refactoring ==&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/_view_heatgrid.html.erb:- View file for the Heat Grid. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/view_team.html.erb:- View file for the Team. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Focussing on the view_heatgrid function and  of the helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on the populate_view_model function of the controller file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/models/vm_question_response.rb:- Focussing on the number_of_comments_greater_than_10_words function of the model file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; Capybara Test cases for the heat grid view and team view should be added to check if the dropdown is visible as expected. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Spec test cases should be added for the grades controller should be added to verify the responses returned from the controller. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Unit test cases will be added to verify the logic of the number_of_comments_greater_than_10_words method of the vm_question_response model. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Important Links =&lt;br /&gt;
* GitHub repository link: https://github.com/ShlokSayani/expertiza&lt;br /&gt;
* Project Description Document: https://docs.google.com/document/d/1slx4HPIbgTH-psIKMSCF-HDF9brxf-FuYhzVT9ZiIrM/edit#heading=h.tqdrrd12xs4x&lt;br /&gt;
&lt;br /&gt;
= Team =&lt;br /&gt;
&lt;br /&gt;
* Shlok Sayani (sdsayani)&lt;br /&gt;
&lt;br /&gt;
* Hardik Udeshi (hvudeshi)&lt;br /&gt;
&lt;br /&gt;
* Isha Gupta (igupta)&lt;br /&gt;
&lt;br /&gt;
* Manish Shinde (msshinde)&lt;/div&gt;</summary>
		<author><name>Igupta</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140860</id>
		<title>CSC/ECE 517 Fall 2021 - E2164. Heatgrid fixes and improvements</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2021_-_E2164._Heatgrid_fixes_and_improvements&amp;diff=140860"/>
		<updated>2021-11-04T02:25:29Z</updated>

		<summary type="html">&lt;p&gt;Igupta: /* Observations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Project Background ==&lt;br /&gt;
Heatgrid is the page where instructor can visit and view the work done by participant using Reviews, Author Feedbacks and Meta Reviews. This one web page displays all the evaluations done by peers of the participant for his project. The page is displayed in the format of table with colors. The columns in the table can be sorted with the requirement of the project. Heatgrid shows scores assigned by reviewers on individual rubric items for participant. &lt;br /&gt;
&lt;br /&gt;
===What is wrong with it===&lt;br /&gt;
It is called from Instructor's &amp;quot;Assign Grades&amp;quot; function and student's view scores functions. But , there are issues that students are reviews themselves. Question is about Are reviews getting assigned correctly? Assignment of metric is also wrong at some places&lt;br /&gt;
&lt;br /&gt;
=Issue 1=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue #2019===&lt;br /&gt;
Questions whether the reviewers are correctly identified.  In one case, a student was shown as reviewing his/her team, which is impossible.  Also write tests so that if this bug occurs again, we will be informed.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current review system implementation, the instructor has the ability to select or deselect the &amp;quot;Allow Self Reviews?&amp;quot; checkbox from the &amp;quot;Review Strategy&amp;quot; tab of the Edit Assignment page. On deselecting this checkbox, a student will not be able to review his/her own work.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following images show how this functionality works currently:&lt;br /&gt;
&lt;br /&gt;
[[File:SelfReviewCheckbox.png|1200px|thumb|left]] &lt;br /&gt;
&lt;br /&gt;
[[File:AssignReviewer.png|1800px|thumb|center]]&lt;br /&gt;
The instructor will get the error &amp;quot;You cannot assign this student to review his/her own artifact.&amp;quot; when an attempt to add a student as a reviewer to his/her own assignment is made.&lt;br /&gt;
&lt;br /&gt;
=== Control Flow ===&lt;br /&gt;
[[File:Issue1CF.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Observations ==&lt;br /&gt;
Whenever an instructor assigns a reviewer for an assignment of a team, there is already a check present and it is not allowing instructor to assign the team member of the team for the review.&lt;br /&gt;
&lt;br /&gt;
[[File:checkReviewer.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is disabled, then the reviewer should not be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; If the &amp;quot;Allow Self Review?&amp;quot; checkbox is enabled, then the reviewer should be able to review their own assignment. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on self-review and grades section. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/_review_strategy.html.erb:- Here, the checkbox of &amp;quot;Allow Self Review?&amp;quot; is written. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Grades helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; spec/controllers/review_mapping_controller.rb:- Adding test cases for checking whether the reviewer can self-review if the &amp;quot;Allow Self Review?&amp;quot; checkkbox is disabled and the vice-versa too. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Issue 2=&lt;br /&gt;
== Problem Definition ==&lt;br /&gt;
===Issue#1869===&lt;br /&gt;
Notes that there is a “metric-1” column in the review report, but it doesn’t say what the metric is. Please figure out what the metric is, and change the column header accordingly.  However, the intent was that eventually an instructor would be allowed to select a metric to be shown on the heatgrid.  So, somewhere in the UI for creating/editing an assignment, there should be a way for the instructor to select a metric from a dropdown list.  You don’t have to add any more metrics to this list other than the one that is currently displayed, just create a mechanism for adding metrics in the future.&lt;br /&gt;
&lt;br /&gt;
== Current Implementation ==&lt;br /&gt;
&lt;br /&gt;
=== Overview ===&lt;br /&gt;
In the current implementation, the columns in the heatgrid table are static. The &amp;quot;metric-1&amp;quot; column in the table represents the count of comments for the respective question which have a word count greater than 10. On hovering over the column name, the correct information is displayed but the name itself does not make the information apparent at first glance.&lt;br /&gt;
&lt;br /&gt;
=== UI Screenshots ===&lt;br /&gt;
The following image captures how the heatgrid is currently being displayed:&lt;br /&gt;
&lt;br /&gt;
[[File:Summary Report.png|1200px|thumb|center]]&lt;br /&gt;
&lt;br /&gt;
== Refactoring ==&lt;br /&gt;
&lt;br /&gt;
== Files to be Targeted ==&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/_view_heatgrid.html.erb:- View file for the Heat Grid. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/views/grades/view_team.html.erb:- View file for the Team. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/helpers/grades_helper.rb:- Focussing on the view_heatgrid function and  of the helper file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/controllers/grades_controller.rb:- Focussing on the populate_view_model function of the controller file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; app/models/vm_question_response.rb:- Focussing on the number_of_comments_greater_than_10_words function of the model file. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Test Plan ==&lt;br /&gt;
&amp;lt;li&amp;gt; Capybara Test cases for the heat grid view and team view should be added to check if the dropdown is visible as expected. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Spec test cases should be added for the grades controller should be added to verify the responses returned from the controller. &amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Unit test cases will be added to verify the logic of the number_of_comments_greater_than_10_words method of the vm_question_response model. &amp;lt;/li&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Important Links =&lt;br /&gt;
* GitHub repository link: https://github.com/ShlokSayani/expertiza&lt;br /&gt;
* Project Description Document: https://docs.google.com/document/d/1slx4HPIbgTH-psIKMSCF-HDF9brxf-FuYhzVT9ZiIrM/edit#heading=h.tqdrrd12xs4x&lt;br /&gt;
&lt;br /&gt;
= Team =&lt;br /&gt;
&lt;br /&gt;
* Shlok Sayani (sdsayani)&lt;br /&gt;
&lt;br /&gt;
* Hardik Udeshi (hvudeshi)&lt;br /&gt;
&lt;br /&gt;
* Isha Gupta (igupta)&lt;br /&gt;
&lt;br /&gt;
* Manish Shinde (msshinde)&lt;/div&gt;</summary>
		<author><name>Igupta</name></author>
	</entry>
</feed>