New Problem Type: Jupyter Notebooks Released

Created by Shubham Kumar, Modified on Thu, 18 Apr 2024 at 11:07 AM by Shubham Kumar

DoSelect has launched a new problem type "DataScience Jupyter Notebooks" for all the customers of the assessment products. Described below is the workflow on how to get started with the latest offerings.

 

  • Getting the Problem Type Enabled:
    • Contact your CSMs and get the problem types enabled for your account. Once you navigate to your library, you would be able to see the Jupyter problem type as shown below:




  • You can then navigate to the DoSelect library to see the DoSelect list of Jupyter type questions. Alternately, you can use the "+" button to add new Jupyter type questions to your own library.


  • Adding Jupyter Questions to Assessments: 
    • You can add Jupyter type questions to any assessment like any other problem type.
    • Currently, we don't support Jupyter with the following question types: Video Based, File Based, Project Based, UI/UX questions.
    • Apart from the questions mentioned above, you can create assessments with a mixture of all other question types (along with Jupyter) with your preferred proctoring type.

 

  • Candidate Reports for Jupyter:
    • Within the Jupyter type reporting, the recruiter would have access to the following data points:
      • Total Marks the Candidate Has received against the Question based on the file accuracy.
      • Standard Accuracy Metric Score (If the problem demanded a calculation of the standard metrics like: Accuracy, F-Score, Precision, Recall.
      • If the problem had a custom evaluation set, then no standard accuracy metric would appear. The marks allocated to the candidate in this case would be purely based on the test cases the problem creator has written.

 




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article