Assignment Chef icon Assignment Chef

[SOLVED] Cs6250 spanning tree spring 2025

5.0 1 customer review Digital download

Digital download

$25.00

Availability
In stock
Checkout
One item

Need a hand?

Message us on WhatsApp for payment or download support.

WhatsApp QR code
Table of Contents PROJECT GOAL………………………………………………………………………………………………………………… 2 Part 1: Setup………………………………………………………………………………………………………………… 2 Part 2: Files Layout……………………………………………………………………………………………………….. 2 Part 3: TODOs………………………………………………………………………………………………………………. 3 Part 4: Testing and Debugging……………………………………………………………………………………….. 5 Part 5: Assumptions and Clarifications……………………………………………………………………………. 6 What to Turn In………………………………………………………………………………………………………………. 7 What you can and cannot share………………………………………………………………………………………… 7 Rubric…………………………………………………………………………………………………………………………….. 8    In the lectures, you learned about Spanning Trees which are used to prevent forwarding loops in a network. In this project, you will add to those concepts by developing a distributed algorithm that can run on an arbitrary layer 2 topology. We will simulate the communications between the switches with Messages. This project is NOT an implementation of the standard Spanning Tree Protocol, so be sure not to reference any outside material or concepts that could lead you astray. Referencing any outside material[1] is also a violation of the Honor Code. If you have questions about the project, post them on Ed Stem.Download the project files from Canvas. You can do this project on your host system if it has Python 3.11.x. The project does not have any dependencies outside of Python. You must be sure that your submission runs properly in Gradescope. Gradescope is the environment where your project will be graded. Gradescope and the VM are the only valid environments for this course. There are many files in the SpanningTree directory, but you should only modify Switch.py.The files in the project skeleton are described below. DO NOT modify these files. All of your work must be in Switch.py ONLY. You should study the other files to understand the project framework.msg = Message(claimedRoot, distanceToRoot, originID, destinationID, pathThrough, timeToLive)and assigning the correct value to each input. Message format may NOT be changed. See the comments in Message.py for more information about the variables. This is an outline of the code you must implement in Switch.py with suggestions for implementation. Keep in mind that certain update rules will take precedence over others.    To run your code on a specific topology (SimpleLoopTopo.py in this case) and output the results to a text file (out.txt in this case), execute the following command:python run.py SimpleLoopTopo “SimpleLoopTopo” is not a typo in the example command – don’t include the .py extension.  We have included several topologies with correct solutions for you to test your code against. You can (and are encouraged to) create more topologies and test suites with output files and share them on Ed Discussion. There will be a designated post where students can share these files.You will only be submitting Switch.py – your implementation must be confined to modifications of that file. We recommend testing your submission against a clean copy of the rest of the project files prior to submission.You may add print statements to facilitate debugging during your development process, but they should be removed or commented out prior to submission.You may assume the following: Submit ONLY your Switch.py file to Gradescope as a single file. Do not modify the name of Switch.py. You may make an unlimited number of submissions to Gradescope before the deadline. Your last submission will be your grade unless you activate a different submission.Before submission:After submission:Honor Code/Academic Integrity: Do NOT share any code from Switch.py with your fellow students, on Ed Discussion, or publicly in any form, even after the course ends. You may share log files for any topology, and you may share any code you write that will not be turned in, such as new topologies or testing suites.All work must be your own, and consulting Spanning Tree Protocol solutions, even in another programming language or just for reference, are considered violations of the honor code. Do not reference solutions on Github! Do not use IDE extensions (like Github Copilot or any AI) that write or recommend blocks of code to you (autocomplete for function names is fine). For more information see the Syllabus Definition of Plagiarism. We provide you with all the materials you need to complete this project without help from Google/Stack Overflow (Searching basic Python syntax is fine). Do not risk an honor code violation for a very doable project.Start early, ask questions in Ed Discussion, and attend TA chat sessions if needed.  [1] Searching general Python syntax is fine but do not search any material related to the Spanning Tree algorithm