Papyrus-RT and Simulink Technical Assignment Help
Description
There will be a total of 120 points available, broken down as follows:
Category | High Quality | Medium Quality | Low Quality | No Points |
Papyrus-RT Model | ||||
Papyrus-RT Implementation
– Structure Diagrams |
Structure diagrams are provided for Top capsule and 4 contained capsules, showing proper
connections, ports, etc. |
One or more structure diagrams are missing OR there are inconsistencies present in the diagrams. | Two or more structure diagrams are missing OR there are significant structural issues present. | No structure diagrams were submitted. |
12 Points | 8 Points | 4 Points | 0 Points | |
Papyrus-RT Implementation
– Main System State Machine |
State machine for main capsule shows proper states based on the provided requirements. | Main state machine is missing some of the key functionality. | Main state machine is does not reflect the desired behavior. | No main state machine submitted. |
10 Points | 6 Points | 3 Points | 0 Points | |
Papyrus-RT Implementation
– Main System Code Snippets |
Code snippets in the Main system accurately reflect the required behavior and make use of proper syntax
and semantics. |
Code snippets are missing some details to reflect all functionality. | Significant functionality is missing from the code snippets in the main system. | No code snippets for main system submitted. |
10 Points | 6 Points | 3 Points | 0 Points | |
Papyrus-RT Implementation
– 3 x Processing State Machines |
All three state machines correctly model the specified behavior of taking
in a number, processing, and sending back. |
1 or more state machine is missing or has minor errors in their behavior. | 2 or more state machines are missing or have minor errors in their behavior OR major
errors are present in any state machine. |
No processing state machines submitted. |
10 Points | 6 Points | 3 Points | 0 Points | |
Papyrus-RT Implementation
– 3 x Processing Code Snippets |
All three sets of code snippets accurately reflect the required behavior and make use of proper syntax
and semantics. |
Code snippets are missing some details to reflect all functionality. | Significant functionality is missing from the code snippets for any one processing system. | No code snippets for processing systems
submitted. |
10 Points | 6 Points | 3 Points | 0 Points | |
Simulink Model | ||||
Simulink Implementation
– Random Generation and Comparison |
The top level Simulink system shows clearly how numbers are generated, passed to systems, and the returned results compared for a winner. | There are several errors present in the logic of the main system causing some incorrect behavior in generating numbers or comparing the processed
values. |
Significant errors exist that cause the behavior of the main system not to reflect the system requirements. | No main system implementation was provided. |
14 Points | 8 Points | 4 Points | 0 Points | |
Simulink Implementation
– 3 x Processing Subsystems |
Each contained subsystem demonstrates correct behavior by performing the correct manipulation of the
input data. |
1 or more processing subsystem is missing from the model OR errors are present in 1 or more that
cause some issues. |
2 or more processing subsystems are missing from the model OR significant errors are present in any of
the subsystems. |
No processing subsystems were provided. |
16 Points | 9 Points | 5 Points | 0 Points | |
Simulink Implementation
– I/O Management |
The input and outputs are correctly handled using the right Simulink blocks. | Some of the input values and output values are handled incorrectly. | Significant input and output values are handled incorrectly, causing issues. | No management of I/O was done. |
12 Points | 7 Points | 3 Points | 0 Points |
Category | High Quality | Medium Quality | Low Quality | No Points |
Output Submissions | ||||
Output – Papyrus-RT runs x 3 | 3 Papyrus RT runs are provided clearly showing the winner each round and the overall winner. | 1 or more run is missing from the submission, or the runs are not different, indicating issues with
generation. |
2 or more runs are missing from the submission or significant errors in the output exist. | No Papyrus-RT output runs were submitted. |
10 Points | 6 Points | 3 Points | 0 Points | |
Output – Simulink Simulation Outputs | 2 Simulink Outputs are provided showing clearly the final counts for each
subsystem, and that other outputs were generated. |
One of the output runs is missing OR some minor errors are present in the resulting outputs. | Significant discrepancies are present in the outputs that demonstrate a lack of
conformance to the requirements. |
No Simulation outputs were provided. |
6 Points | 3 Points | 2 Points | 0 Points | |
Output – Simulink Generated Code Outputs | Generated output shows the success of generation of code, as well as the final counts of the run, and that other outputs were
generated. |
The generated outputs have minor errors in them. | Significant errors/discrepancies are present in the outputs. | No generated code outputs were provided. |
4 Points | 2 Points | 1 Point | 0 Points | |
Document Presentation | ||||
Professional Document | A well formatted, easy to read, professional
document was submitted. |
Minor issues with document in terms of presentation. | Significant issues with document in terms of
presentation. |
The submitted document is
unprofessional. |
6 Points | 4 Points | 2 Points | 0 Points |
Details
There will be 2 parts to this assignment. You will be creating a system to generate random numbers, process them in in some manner, then compare the results for output. You will implement the system in both Papyrus-RT and in Simulink.
- The following is the basic behavior of the system regardless of implementation:
- You must generate 3 random numbers between 1 and
- Each random number must be passed to some other component to process the number in some way:
- The first, called A, will double the
- The second, called B, will add 37 to the
- The third, called C, will square the number and subtract
- All three results will be stored for
- The highest of the three values will determine the winner:
- If A is the highest, then A wins; if B is the highest, then B wins,
- You will need to keep track of the winner in each round (A, B, or C), and a count for each of them to determine an overall
- Ultimately, your competition will have 100 values, thus 100 rounds of competition, and the number of winners should add up to
- The following should be considered for your Papyrus-RT implementation:
- You will need 4 capsules: 1 central capsule for the generator and comparison, and 1 for each of A, B, and
- You will need protocols for communication between the appropriate
- This assignment will require passing of parameters with messages – you will need to look into how to do
- A, B, and C should only receive messages with a number, process it in their own way, and send it back to the central
- The central capsule should wait to receive all three results back, compare them, and determine that round’s winner (logging output), as well as update counters for the winner.
- At the end of the 100 runs, the system should pick an ultimate winner; that is the system (A, B, or C) that had the most wins over the 100
- The following should be considered for your Simulink implementation:
- You will need a variable to keep track of wins for A, B, and
- You will also need to count the number of wins for each of A, B, and
- Processing for A, B, and C should take place in separate
- Your values should work for BOTH simulation AND generated
- Make sure to set all model properties as appropriate (things like solver type, step size, the type of output, )
- Once both are completed, you will need to “officially” run each 3 times as follows:
- Run your Papyrus-RT system by generating the code, and running it 3 times just as we did for Lab 5, redirecting output to files for inclusion in
- Simulate your Simulink model twice, then generate the code and run it once for the 3 runs. You will need to capture the output in the workspace after each
What to Submit
- Your Papyrus-RT Implementation
- Include all structure diagrams, state diagrams, and code snippets in the same manner and detail as for Lab
- Your Simulink Model Implementation
- A screenshot of the completed Simulink Model
- You must show the inside of any contained subsystems by opening them up and providing additional screenshots.
- Your Papyrus-RT Outputs
- The contents of the 3 files containing your output for the 3
- Your Simulink Outputs
- A screenshot of the workspace after the two simulation runs – delete all values after each run
- A screenshot of the workspace after generating and running the Executable file, and loading the resulting .mat file into the