Skip to content

Process for adding new labs should be documented #13

Open
@cwpearson

Description

@cwpearson

Broadly:

  • each lab is in its own folder, with its own self-contained resources. Any folder should stand alone to facilitate reuse among our collaborators
  • create a standalone .cu source file (or as close to a single file as practical) with the skeleton code.
    • use either GNU make or CMake to drive configuration/compilation
    • do not commit the solution to this repository, as we will have to edit the history to remove it, which is annoying.
    • Strive to report any errors that are unrelated to the teaching goal of the lab, and report them early and with a clear error message. the goal is for the students to focus on the target lab content and not have to struggle with anything else
  • Create a README.md for the lab
  • create a corresponding solution in github.com/illinois-impact/gpu-algorithms-labs_solution

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions