Repository navigation
Instructor Getting Started (December 2021)
Edugator Admin is a website that enables you to create coding problems for your students organized within modules. You can watch this video for a quick introduction to Edugator's functionality as of December 2021.
To access the instructor portion of Edugator, you must navigate to https://edugator.app/admin/login
You will be given a username and password. Enter the username and password. Once successfully validated, you will be logged in for 24 hours and will be redirected to the admin modules page.
From the Modules page you can go to manage accounts or add a module in the command bar to the right of the page's title.
You can also rename or delete an existing module by clicking on the triple dots to the left of a module.
To create a new problem for a module, you can click the "Add problem" button. Be careful though! You cannot transfer problems from one module to another (for now).
You can also edit or grade existing problems.
You can give your problem a title, due date, and hidden status here. The title is required. If you toggle the hidden option, students will not be able to see the problem. You can view the problem prior to its release to students here.
The problem editor enables you to write the problem description. You can use standard markdown syntax to add text bolding or italics, blockquotes, code boxes, images, etc... A template should be created for you when you create a problem with some markdown tips. A preview of the markdown is displayed in the right pane.
The template package is the code package that the students will receive that will enable them to download the starter code and program locally on their IDE.
Code for now is only available in c++ with .h and .cpp file extensions.
Code is separated into three types: header, body, and footer.
This is where you can import packages and create classes for the students like a Node or TreeNode class. Students will not be able to see the header code. If the student reimports any package or type using namespace std; again, it should not cause errors.
The body is what is visible to students. It is recommended to give them an empty class or function for their code.
The footer is usually where you will put the main function that will accept console input and output the result of the student's code. The main does not have to be in the footer. The main should remain in the footer if you don't want students to be able to see it nor change it.
Note: You should print out whatever the expected output should be. Be careful about whitespace. Ex: only put endl or \n if you add an new line in your expected output.
Here you can set the time limit and memory limit for the student submissions. You may also set the build command for the judge0 engine.
The test case editor allows you to designated the input and expected output for test cases. Test cases can have hints. Test cases have one of the following visibilities:
- Input and output visible
- Input visible, output hidden
- Input and output hidden
The first test case is required to have input and output visible, because it is used on the student side to auto-populate the run code input. Hints will be visible to students if the input and output are hidden. Hints are not required.
Then you may save your coding problem.
After selecting a problem to grade, you must upload a zip file containing all of the student submissions from Canvas. You also must enter an email to which the results will be sent. Once you submit the zip file for grading, a batch job will be run for all of the student submissions and the results will be output to a csv file and then emailed to the email that was provided.
To facilitate the creation and deletion of accounts of that can use our admin tools, we have a page that allows Administrators with "Professor" privileges (or higher) to see the existing accounts perform any desired changes.
To view existing accounts, currently you can click a button labeled "manage accounts" that appears on the Modules Page after logging in. Otherwise, replacing "/modules" with "/accounts" should do it as well.
To create an account, click "Add Admin User" and fill the necessary information. Professor accounts should be able to create TA accounts and the Administrator account creates other Professors.
There are two ways to do changes, one is to use the quick actions and the other one is to use the "edit" form. In the edit form, the account's email, name, and role can be modified. Due to privacy concerns more private information such as phone numbers are not being stored.
This is a list of quick actions that can be performed on the account that was selected. The actions include the following:
- Change the account's role to TA
- Change the account's role to Professor
- Delete this account
To modify an account, click the account to modify, and then click "edit" on the account information dialog. Perform the desired changes and then click "save".
Click the account, then use the "Administrative Actions" and select Delete Account.