Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ETM should expose their requirements #3

Open
MaximeCheramy opened this issue Jun 26, 2015 · 0 comments
Open

ETM should expose their requirements #3

MaximeCheramy opened this issue Jun 26, 2015 · 0 comments

Comments

@MaximeCheramy
Copy link
Owner

The various ETM require different informations, for instance, the Cache Model needs the SDP, API, etc, the ACET model requires the std dev and the average duration, the fixed penalty requires a preemption cost...

Each ETM should contains a list of parameters that are required, with their type. However, this is not easy as it sounds: sometimes it's a task field or a simulation field, or a processor field, but sometimes it can even be a new kind of data such as the description of the caches.

A first step could be to add several lists of required fields for the tasks, processors and the simulation. This will ease the work on the UI side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant