Expertiza_Wiki - User contributions [en]

File:Checkbox question.png

2018-04-29T02:06:44Z

Bkarumu:

CSC/ECE 517 Spring 2018- Project E1815: Improvements to review grader

2018-04-29T01:37:36Z

Bkarumu:

== '''Introduction''' ==

This project aims to enhance the review report and summary page, and display more information necessary for grading. The goal is to help the instructors by making the process of grading reviews easier and more accurate.

== '''Problem Statement''' ==

===Issue 1: Visualization of Metrics in Review Reports===

There are some issues with the current review report page with regards to the Metrics column.
:*Metrics are displayed as plain text.
:*No comparison on how this student compares with other students.
:*If more metrics are added, showing multiple lines of text for each metric can make the column cluttered and difficult to read.

Showing a bar chart for the metric rather than just text would improve the user experience. The bar chart can also depict the average for all students for this metric, so the grader can see how this student compares with other students. Also, if several metrics are shown in the column, the bar chart can be made resizable to accommodate multiple bars.

[[File: e1815_issue1.JPG|center]]

===Issue 2: Updating Review Summary view===

To view this page you click the summary in the row for any student.

This page summarizes the peer Reviews given to the Author. They are basically separated into three columns i.e reviewee, score and comments.

#The first issue in this view is that there is no header saying what course, assignment, or student this relates to.
#Secondly, The field that lists the team members is wider than the rest of the columns combined. The comments column needs more space it will contain more information
#Finally, For questions answered with check-boxes, comments are not necessary, but still a blank cell is displayed.

[[File:reviewee.PNG|center]]

===Issue 3: Adding color schemes to identify updates to reviews as per submissions===

Currently, in review report, each team reviewed is color coded as, red indicating that the review is not yet completed and blue indicating that the review grade is not assigned or updated. So if an instructor sees a name in red, the student should not be given credit for the review. If text is in blue, then the student has not been graded for the review, so the instructor should grade it now. But there is caveat here. If the reviewer has reviewed the work but the author did not resubmit, the reviewer has nothing new to review in the latest round and should not be downgraded for not re-reviewing the work. This issue needs to be addressed.
[[File:Colorscheme.PNG]]

This is what the current color scheme looks like. The text in blue indicates that the student has not been graded, while the text in red indicates the student should not be given credits.

== '''Files Changed''' ==
* app/assets/stylesheets/redbox.scss
* app/helpers/review_mapping_helper.rb
* app/views/review_mapping/_review_report.html.erb
* app/views/popup/view_review_scores_popup.html.erb
* config/application.rb

== '''Solutions Implemented''' ==

===Issue 1: Visualization of Metrics in Review Reports===

We replaced the text given in the Metrics column with a bar chart, as shown below. The bar chart depicts the overall average of all students for this metric, the average of this student for this metric (based on each round) and the metric values for each round for this student.

====Code Changes====

* File: app/helpers/review_mapping_helper.rb
The following methods were added to calculate average for this metric for all students and for calculating maximum value for this metric. The maximum is needed for constructing bar chart. The second method was added to construct the x-axis labels in the format "0|50|100|...|max" for the bar chart.
[[File: Methods-1.JPG|center]]

* File: app/helpers/review_mapping_helper.rb
The following method constructs the bar chart.
[[File: Methods-2.JPG|center]]

* File: app/views/review_mapping/_review_report.html.erb
The following code is added to get the average metric, maximum value of metric and x-axis value from controller.
[[File: Html-1.JPG|center]]

* File: app/views/review_mapping/_review_report.html.erb
The following code includes the bar chart in the review report page.
[[File: Html-2.JPG|center]]

====Screenshots====

[[File: Metrics-result.JPG|center]]

===Issue 2: Updating Review Summary view===

We have spanned the question text to all three columns instead of it being one, also the width of the first column containing the reviewee information is reduced appropriately.
Checkbox Questions are displayed more compactly by including Question to the left and automatically adjusting the width of the reviews to right. A green tick is added if the reviewer selected the checkbox and a red cross mark is added if the reviewer did not select the checkbox.

The file modified is app/views/popup/view_review_scores_popup.html.erb

In the code, we identified whether a question is Checkbox question or not and changed the row to include the question on the left and auto adjusting the response from the reviewer's on right.

[[File:Issue_2_code_snippet.png]]

The page looks as follows

[[File:Issue_2_final_display1.png]]

===Issue 3===
To address the caveat mentioned above, we could use a different color, perhaps green, to distinguish reviewers who have nothing new to review as the authors have not made any changes. This is what we are planning to implement.

[[File:Colorschemeedit.png]]

== '''Test Plan''' ==
===Issue 1: Visualization of Metrics in Review Reports===

1) Login as an instructor

2) Navigate to review grader by doing this (Manage > Assignments)

3) Click on the “View review report” icon (the one with the spyglass and two people)

4) Check if the visualizations are appearing in the review report.

===Issue 2: Updates and Review Summary View ===

1) Login as an instructor

2) Navigate to review grader by doing this (Manage > Assignments)

3) Click on the “View review report” icon (the one with the spyglass and two people)

4) In the review report click on the “summary” in the row for any student.

5) Check if the changes are appearing in the page as mentioned in the proposed solution.

===Issue 3: Adding Color Schemes to Identify Updates to Review As Per Submission===

1) Login as an instructor

2) Navigate to review grader by doing this (Manage > Assignments)

3) Click on the “View review report” icon (the one with the spyglass and two people)

== '''Screencast''' ==

*

== '''References''' ==

Expertiza
* https://expertiza.ncsu.edu/

Expertiza Github
* https://github.com/expertiza/expertiza

Expertiza Documentation
* http://wiki.expertiza.ncsu.edu/index.php/Expertiza_documentation

File:Issue 2 final display1.png

2018-04-29T01:36:53Z

Bkarumu:

File:Issue 2 final display.png

2018-04-29T01:30:02Z

Bkarumu: uploaded a new version of "File:Issue 2 final display.png"

File:Issue 2 final display.png

2018-04-29T01:28:59Z

Bkarumu:

File:Issue 2 code snippet.png

2018-04-29T01:15:20Z

Bkarumu: uploaded a new version of "File:Issue 2 code snippet.png"

File:Issue 2 code snippet.png

2018-04-29T01:12:31Z

Bkarumu:

CSC/ECE 517 Spring 2018- Project E1815: Improvements to review grader

2018-04-08T16:52:35Z

Bkarumu:

User:Bkarumu

2018-04-03T03:23:37Z

Bkarumu:

= '''Mozilla Open Source Project''' =

----

=='''Implementing the Support for Creating HTTP archive files from Servo Sessions'''==

----

===='''Introduction'''====
Servo is a parallel web browser engine designed for both application and embedded use. Servo is written in programming language Rust. Mozilla Research sponsored Rust, a systems programming language which is parallel, secure and modular.

----

===='''Servo'''====
Servo is a prototype we browser engine written in Rust programming language. The motivation towards using rust is to achieve high-performance through parallelism, modularity and security.

----

===='''Rust'''====
Rust is a Mozilla Research sponsored open source programming language. It is syntactically similar to c++. The main idea to use rust is to ensure thread safety, atomicity of tasks, memory safety and high-parallelism.

----

===='''Project Description'''====
The Project is to Implement support for creating HTTP archive files from Servo sessions. All major browsers creating HTTP archive files or HAR files. HAR files are generated to analyze web requests. HAR files store log data that keeps track of interaction with web browser.
This Tracking of interaction is useful to troubleshoot issues like performance issues-timeout when performing task, slow page loading; Page Rendering issues- not loading certain information, incorrect page layouts etc.

----

===='''Steps Implemented so far'''====
Step 1: Understanding the Servo Implementation.

Step 2: Build Servo in local machine. The procedure to build servo is described in Readme file for different environment types.

Step 3: Added the path to include "Rust-Har" Library in net-traits/Cargo.toml

Step 4: Created an enum in the net-traits/lib.rs file. This enum will use your library, rust-har, to 'send' a HAR file.

Step 5: Modified the ResourceChannelManager in net/resource_thread.rs to accept the enum. All the modified code can be viewed in the recent commit.

Step 6: Modified the CoreResourceMsg::Exit message to contain an optional vector of har::Page values.

Step 7: Added the command line flag that accepts a filename as argument. This flag controls to store HAR data or not.

Step 8: In servo/lib.rs, in the function create_constellation pass an argument using the new global option when calling “new_resource_threads”.

Step 9: When processing the “CoreResourceMsg::Exit” message, sent an empty vector as JSON to an appropriate file depending on the member variable that was added earlier.

----

===='''Test Plan'''====
Step 1: Clone the repository into your local machine with URL: https://github.com/servo/servo.git.

Step 2: Build the Servo according to the guidelines presented in the README file in the github repository.

File:Dependency adding.png

2018-04-03T03:22:18Z

Bkarumu:

User:Bkarumu

2018-04-03T03:13:59Z

Bkarumu: Documentation-"Implementing the Support for Creating HTTP archive files from Servo Sessions"

= '''Mozilla Open Source Project''' =

----

=='''Implementing the Support for Creating HTTP archive files from Servo Sessions'''==

----

===='''Introduction'''====
Servo is a parallel web browser engine designed for both application and embedded use. Servo is written in programming language Rust. Mozilla Research sponsored Rust, a systems programming language which is parallel, secure and modular.

----

===='''Servo'''====
Servo is a prototype we browser engine written in Rust programming language. The motivation towards using rust is to achieve high-performance through parallelism, modularity and security.

----

===='''Rust'''====
Rust is a Mozilla Research sponsored open source programming language. It is syntactically similar to c++. The main idea to use rust is to ensure thread safety, atomicity of tasks, memory safety and high-parallelism.

----

===='''Project Description'''====
The Project is to Implement support for creating HTTP archive files from Servo sessions. All major browsers creating HTTP archive files or HAR files. HAR files are generated to analyze web requests. HAR files store log data that keeps track of interaction with web browser.
This Tracking of interaction is useful to troubleshoot issues like performance issues-timeout when performing task, slow page loading; Page Rendering issues- not loading certain information, incorrect page layouts etc.

----

===='''Steps Implemented so far'''====
Step 1: Understanding the Servo Implementation.
Step 2: Build Servo in local machine. The procedure to build servo is described in Readme file for different environment types.
Step 3: Added the path to include "Rust-Har" Library in net-traits/Cargo.toml
[[File:]]
Step 4: Created an enum in the net-traits/lib.rs file. This enum will use your library, rust-har, to 'send' a HAR file.
Step 5: Modified the ResourceChannelManager in net/resource_thread.rs to accept the enum. All the modified code can be viewed in the recent commit.
Step 6: Modified the CoreResourceMsg::Exit message to contain an optional vector of har::Page values.
Step 7: Added the command line flag that accepts a filename as argument. This flag controls to store HAR data or not.
Step 8: In servo/lib.rs, in the function create_constellation pass an argument using the new global option when calling “new_resource_threads”.
Step 9: When processing the “CoreResourceMsg::Exit” message, sent an empty vector as JSON to an appropriate file depending on the member variable that was added earlier.

----

===='''Test Plan'''====
Step 1: Clone the repository into your local machine with URL: https://github.com/servo/servo.git.
Step 2: Build the Servo according to the guidelines presented in the README file in the github repository.