The purpose here is to add a pointer to the first time and to the last time in the model.
What I mean by first/last time:
First time: the first moment where a snapshot is taken, i.e the model is no longer empty. Before the model is empty (no snapshot taken), after there is at least one element.
Last time: the time of the last snapshot. So, after that time, the "model resolution" always needs to "predict" each element.
My need: I am currently implement a parser of logs of a state machine. The time of my model elements are the time of the log. Thus, my start time is the time of the first log that I analyse. So, I don't know it in advance. After that, I create a web page where I have a slider to select the time at which I want to display my model. So, I need a start time and also a end time.
(The end time could be useful to know if we are in a "full predictive" mode or not.)
But my question is: is it a specific requirement or a more global requirement?
I think that it could be useful when we use the real time to model a system, i.e. we don't start the model at 0.
What do you think?
(By the way, the start/end time could be managed manually. So the question behind is: do we add this feature in KMF or let us users handle it manually?)
The purpose here is to add a pointer to the first time and to the last time in the model.
What I mean by first/last time:
My need: I am currently implement a parser of logs of a state machine. The time of my model elements are the time of the log. Thus, my start time is the time of the first log that I analyse. So, I don't know it in advance. After that, I create a web page where I have a slider to select the time at which I want to display my model. So, I need a start time and also a end time.
(The end time could be useful to know if we are in a "full predictive" mode or not.)
But my question is: is it a specific requirement or a more global requirement?
I think that it could be useful when we use the real time to model a system, i.e. we don't start the model at 0.
What do you think?
(By the way, the start/end time could be managed manually. So the question behind is: do we add this feature in KMF or let us users handle it manually?)