From c65ea0075effabf8de4c9e35e33c273f0fc995d9 Mon Sep 17 00:00:00 2001 From: Joeri Exelmans Date: Fri, 13 Dec 2024 14:58:40 +0100 Subject: [PATCH] update assignment --- assignment/doc/TIPS.txt | 24 -------------- assignment/doc/assignment.html | 57 +++++++++++++++++++++++++++++++--- 2 files changed, 53 insertions(+), 28 deletions(-) delete mode 100644 assignment/doc/TIPS.txt diff --git a/assignment/doc/TIPS.txt b/assignment/doc/TIPS.txt deleted file mode 100644 index d16e344..0000000 --- a/assignment/doc/TIPS.txt +++ /dev/null @@ -1,24 +0,0 @@ -CODING CONVENTIONS - -1. write your methods always in the following order: - - extTransition - timeAdvance - outputFnc - intTransition - - this reflects the order in which the methods are called by the simulator: - - extTransition always has highest priority (can interrupt anything) - timeAdvance is called before outputFnc - outputFnc is called right before intTransition - - -2. input/output port attributes start with 'in_' and 'out_' - - -TROUBLESHOOTING - - - did you forget to return `self.state` from intTransition or extTransition ? - - did you accidentally write to `self.x` instead of `self.state.x` ? - - did you modify the state in timeAdvance or outputFnc (NOT ALLOWED!!) diff --git a/assignment/doc/assignment.html b/assignment/doc/assignment.html index fe49409..6fd0bf3 100644 --- a/assignment/doc/assignment.html +++ b/assignment/doc/assignment.html @@ -1,3 +1,5 @@ + + DEVS Assignment @@ -85,7 +87,7 @@ The specification of the semantics of the Atomic DEVS blocks is entirely determi

Coupled DEVS

-

The system as a whole is modeled as a Coupled DEVS block. Many of its parameters are passed as-is to the underlying Atomic DEVS blocks, such as: +

The system as a whole is modeled as a Coupled DEVS block. Its parameters are mostly passed as-is to the underlying Atomic DEVS blocks. They are:

+
  • Write a report, where you: +
      +
    • explain and motivate the interfaces/protocol of the AtomicDEVS blocks
      • +
    • show the plotted results
      • +
    • interpret the plotted results
      • +
    +
    • +
  • Submit via BlackBoard, a ZIP file, containing: +
      +
    • Your code (only the assignment directory)
      • +
    • Your report (PDF)
      • +
    • The generated CSV- and SVG-files
      • +
    +
    • -

    Attention!

    -

    You must stick to the rules of DEVS:

    +

    Attention!

    +

    You must stick to the rules of DEVS:

    Any violation of these rules results in an incorrect solution. Points will be subtracted.

    +

    Coding Conventions

    + +

    Please follow these coding conventions:

    + + +

    Troubleshooting

    + +

    Common mistakes include: +

    +

    Extra Material

    - \ No newline at end of file + + + \ No newline at end of file