Computational Research
Level 2: Applied Expertise
Grading Rubric
In order to be Wolfram Certified Level 2 in Computational Research, the applicant must successfully complete an independent project that demonstrates expertise in applying computational approaches to solving or exploring a complex problem. The computational essay must be submitted in the form of a Wolfram Notebook. Submissions are graded according to the following rubric. Level 2 certification requires a project score of 75 or greater.

Research and Analysis Skills (35 points)

Well-Defined Question or Problem (5 points)


  • Clearly define your problem statement (you may have more than one).
    • 
  • Ensure that your problem statement is relevant to the topic.
    • 
  • Ensure that your problem statement is novel, unique, creative or offers new insight into a topic.

    • Background and Motivation (5 points)

    
  • Clearly explain the topic and relevant background information, including some review of previous literature.
    • 
  • Clearly explain the motivation behind the question or problem being solved.
    • 
  • How does this fit with previous researchers’ explorations of this topic?
    • 
  • Why is this a relevant or interesting question or problem?

    • Methods (10 points)

    
  • Describe in detail the strategies and methodologies you used to answer the question or solve the problem.
    • 
  • Demonstrate understanding of empirical methods and articulate your reasons for your research choices.
    • 
  • Elaborate on failures and explorations.
    • 
  • Demonstrate understanding of and follow any ethical stipulations from relevant governing bodies.

    • Analysis and Discussion (10 points)

    
  • When data is used, demonstrate creative and critical handling of it, present it accurately and make meaningful inferences from it.
    • 
  • Provide compelling or accurate evidence to support your position, conclusion or solution.
    • 
  • Analyze your solution.
    • 
  • How far does it go toward solving your problem or answering your question?
    • 
  • What is missing?
    • 
  • What is uncertain?

    • Conclusions or Product (5 points)

    
  • Present your conclusions in the form of an answer to a question or an output to solve or explore a problem.
    • 
  • Analyze your contribution to the field.
    • 
  • What have you found?
    • 
  • Why is this interesting or important?

    • Proficiency in Wolfram Language (35 points)

    Appropriate Syntax (15 points)

    
  • Code uses standard Wolfram Language syntax.
    • 
  • Code is readable, concise and well formatted.
    • 
  • Functions and variables are defined and utilize clear naming conventions.
    • 
  • Avoid generic names like var123 or myFunction.
    • 
  • Avoid capitalizing the first letter of a variable or function, e.g. BuildingBridge, and utilize camel case, e.g. buildingBridge.
    • 
  • Utilize functions to avoid repetitive code.
    • 
  • Revise and rewrite code to make it simple and straightforward. Keep in mind the rule of thumb to make a cell no more than three lines of code; cells with complicated, lengthy code should be broken up into multiple segments or cells.

    • Use of Code (10 points)

    
  • Code accomplishes the stated goals in reasonable ways.
    • 
  • Outputs are visually engaging and relevant to the surrounding analysis.
    • 
  • Utilize visualizations, Grid, etc. to ensure output is interesting and readable.
    • 
  • Utilize Iconize or closed cells to hide necessary code/outputs that are not interesting or relevant to the reader.

    • Reproducibility (10 points)

    
  • Code is reproducible and self contained.
    • 
  • All code runs in a single notebook, including data and visualizations.
    • 
  • No file paths are used, and all data is stored in the Wolfram Cloud or other publically accessible location.
    • 
  • Initialization cells are used to ensure that running cells in order produces expected outputs.
    • 
  • Test your notebook by:
    • 
  • Evaluation → Quit Kernel → Local, then
    • 
  • Evaluation → Evaluate Notebook
    • 
  • Check that all code evaluates as expected.
    • 
  • Code is clearly commented using code text, such as:
    • Create a scatter plot of feature 1 vs. feature 2 using ListPlot:
    In[]:=
    ListPlot[RandomReal[10,{10,2}]]
    Out[]=
    
  • Remove incomplete/irrelevant code snippets (used to try out ideas while developing the project) from the final notebook.

    • Communication (30 points)

    Format (10)

    
  • Convey the final results of the analysis clearly in the form of a computational essay in a Wolfram Notebook with relevant text explanations, Wolfram Language code and visualizations.
    • 
  • This may be accompanied by a microsite or similar for people to use, explore or visualize your solution.
    • 
  • Essays should be clear, interesting and well structured, according to guidelines on writing computational essays.
    • 
  • Make appropriate use of titles, text, code, code text, visualizations and interactivity.
    • 
  • For this submission, you do not need to ensure that your notebook can be published to the Wolfram Cloud or Wolfram Community.

    • Clarity (15)

    
  • Include relevant, concise text explanations to describe every stage of the project.
    • 
  • Whenever possible, use simple visualizations to illustrate the topic and add visual interest.
    • 
  • Ensure that your essay is proofread and written in clear, understandable English.

    • Referencing (5)

    
  • Appropriately situate your contributions within the field.
    • 
  • Cite previous research performed by others to back up claims you make.
    • 
  • Cite any code you build on or edit.
    • 
  • If this project builds on someone else’s work or attempts to provide comparative analysis, highlight the work in a reference.
    • 
  • Acknowledge individuals or programs who have offered assistance with your project.
    • 
  • Include a full reference section detailing your sources.