Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

Assessment

Grade Composition

  • Basic Conversational Agent: 30%

  • Extensions to the Agent (quality and originality): 30%

  • Written Report: 30%

  • Individual Quiz: 10%

    • A pass adds 1 full point to the grade.

    • A fail adds no points.

  • Practical Attendance:

    • Pass or Fail

    • Mandatory pass. A failure will lead to failing the entire course.

  • Midway Check-In Presentation:

    • Pass or Fail

    • Mandatory pass. A failure will lead to failing the entire course.

To complete the project, you need to provide the following deliverables; make sure to follow the instructions for providing us with these deliverables at the end of this page:

Deliverables - Repository

Please ensure the following items are included and properly organized when submitting your project:


1. Git Repository

  • Main Branch:

    • Contains the full codebase for inclusion, exclusion, and all extensions.

    • Includes the final pipeline implementation.

  • Branch Structure:

    • inclusion_only: Contains the codebase focusing solely on inclusion logic.

    • inclusion_exclusion: Contains the codebase for inclusion and exclusion logic combined.


2. Report

  • A detailed report documenting the project’s development and results.

  • Submit the report in markdown.


3. Midway Check-In

  • Provide the PDF version of your slides from the midway check-in presentation.


4. Pipeline Results

  • Include the output/results from your pipeline to demonstrate functionality and performance.


5. Trained Model

  • Provide the trained model file:

    • Checkpoint File: model_checkpoint.pt.


6. Ontology

  • If any modifications were made to the ontology, ensure the updated version is included.


7. Data

  • If any changes or additions were made to the dataset, provide the updated or additional data files.


Key Notes

  • Ensure your Git repository is well-organized, with proper branch structure.

  • Verify that all files mentioned above are present, named appropriately, and accessible.


  • No labels