The cards in an advanced zyLab provide information about the workspace and the work learners performed in them. Each card can be clicked anywhere to expand it, then click "Hide" to collapse it.
Instructors and TAs with proper permissions will see these cards under each advanced lab in a zyBook.
Template, Model Solution, Test Bench
Lab Statistics
Student Behavior Insights
Similarity Detection
Student Activity
Template, Model Solution, Test Bench
This view of the template, model, and test bench is read-only, but click the 'Edit' button at any time to switch to the edit side.
The Template is the workspace presented to learners with all the files and settings present there. Any changes made to the template after learners have begun working will require those learners to open the settings in the bottom right and reset to template to receive updates. Resetting will remove their current work and settings.
The model solution represents the ideal/expected workspace and can be used to confirm your tests work properly. Learn more about model solutions here.
The test bench is where you can create any automated and manual tests to check your learners code. Learn more about the test bench here.
Options contains settings like submission limits and model solution visibility that can be changed on the edit side. Learners will need to reset to template if you change these settings after they begin working.
Lab Statistics
The lab statistics card contains information about submissions, scoring, and allows downloading workspaces at the time of best submission or the specified submission date from the top of the card.
The workspace download can contain all files, or specific files for a smaller, more precise download.
A CSV of submissions tied to IP addresses can also be downloaded by clicking the button in the top right. Student names can also be anonymized to ID numbers for presentation purposes.
Student Behavior Insights (beta)
Student behavior insights provides an average of submissions, explore runs, time spent, and pasted code.
Click the edit button next to "Analyzed Files" to change the files being analyzed for student insights. Then confirm by clicking "Analyze".
The student activity outliers section at the bottom of the card provides a place to view any outliers among learners. This includes learners with time spent notably different than others, any percentage of pasted code at any time, and a percentage of pasted code when the learner submitted.
Click any learner to open that learner in student activity and view their work. Click History for more information, or click directly on any run or submission in their coding trail to jump to that point in History.
Learn more about coding trails here.
Similarity Detection
Similarity detection is an easy way to compare student's latest, best submission and determine if the amount of similarity is acceptable. Click "Add known solution" to also compare the model solution with their submissions. Anonymize names will convert student names to id numbers, for presentation purposes.
Note that the comparison is performed on the default file, and any additional files can be added, or the default file can be removed from the check. Exclusion would be necessary for any files that are not meant to be edited, because their contents are the same among all users.
After selecting "Run similarity check" or opening a previous check, the comparison will open. The top of the comparison is split between pairs of submitters, and a score from 0-10 with a higher score indicating more similarity. An option in the top right allows comparison with only the submissions containing the model solution.
The file comparison along the bottom of the screen will show a visual comparison of the work currently selected. The similarity checker strives to consider code that is similar but uses different variable names. At this time, these similarities aren't highlighted but are still counted towards the overall score.
Student Activity
Student activity displays the scoring results for all learners, along with a coding trail that displays the date of submission up front, an indicator for the day (M for Monday), a - for each development run, and a score for each submission. The total time spent in the workspace is indicated at the end of the coding trail.
Learn more about coding trails here.
Sorting and filtering student activity
Student activity defaults to sorting by name, but there are a number of other options available. Score is useful for sorting by learners that may be having trouble, and "needs grading" is a great option if you're using manually graded tests.
Additionally, learners can be filtered by their section, or by submission state.
Click on any learner to open their current workspace. Then, open their History in the top right corner, or click on any moment in the coding trail to examine their work further.
Instructors and TAs can also code directly in learner workspaces or add comments.
That's it!