Comments (1)
Hello,
About your first question, it is possible that some of the optional constraints are enabled on the .jar file version, making your schedule different from what is generated when you run TSNsched on your IDE. I would have to double check that. Also, depending on how the solver handles the network that you give as input, the result can be slightly different, so even the order of creation of your devices can affect your output. Don't worry though, both schedules are valid.
About the slot duration (the transmission window size), TSNsched allows your transmission window to be greater than the transmission of a single packet. This can be useful to create more flexible schedules allowing the usage of a single transmission window to transmit more than one packet (given that they have the same priority/class). That said, TSNsched sometimes can create a slot with 50 microseconds of duration to transmit only one packet (that takes 13 microseconds to be transmitted). You can fine tune the duration of a slot controlling the maximumSlotDuration variable in the cycle. It is given as a parameter of the constructor method of the Cycle objects. Notice the "new Cycle(50);" commands on the GeneratedCode class, which basically means "create a new cycle where its slots cannot have their duration greater than 50".
I hope this clarifies your questions. Let me know if there is anything else that I can help you with.
from tsnsched.
Related Issues (20)
- Build a better command line output interface HOT 1
- Add configuration options at port level. HOT 1
- Enable ports with the same name in different switches
- Allow the usage of priorityValue without fixedPriority
- Make logging and console outputing optional HOT 1
- Enable control of the output file name
- Documentation of new features
- no output HOT 4
- The flow type setting problem HOT 3
- Java version issue when trying the example HOT 2
- generateSchedule.sh example.java HOT 1
- when set two flows with different periods,cant get the reult,which log the "The specified constraints MIGHT NOT be satisfiable"
- Two flows with different cycle merge into the same link HOT 2
- Incompatibilities with latest Z3 releases HOT 2
- Flows with the same source but different periods
- Failed to run the example HOT 1
- What went wrong? HOT 1
- There is a bug after modifying M1 chip HOT 2
- How to run the project under OMNet++ HOT 1
- Questions about Implementing TSNsched HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from tsnsched.