~~~{.py}
1 0
2 1
- WAITFOR 8
+ LOOPAFTER 8
~~~
- At time t=1, the host is turned off (value 0 means OFF)
- At time t=10, the history is reset (because that's 8 seconds after
the last event). So the host will be turned off again at t=11.
-If your trace does not contain a WAITFOR line, then your profile is
+If your trace does not contain a LOOPAFTER line, then your profile is
only executed once and not repetitively.
@section howto_multicore How to model multicore machines
2 62500000
4 31250000
-WAITFOR 6
+LOOPAFTER 6
4.199387092709633 1.0335587797993976E8
5.319464737378834 1.0591433767387845E7
7.237437222882919 7.037797434537312E7
-WAITFOR 0.76256277712
+LOOPAFTER 0.76256277712
# Wait until t=8
0 1.0
11 0.5
20 0.9
-WAITFOR 1
+LOOPAFTER 1
1 -1.0
2 1.0
-WAITFOR 8
+LOOPAFTER 8
0 1.0
10 0.8
20 0.4
-WAITFOR 10
+LOOPAFTER 10
break;
while ((event = future_evt_set->pop_leq(next_event_date, &value, &resource))) {
- if (value >= 0){
+ if (value >= 0)
resource->apply_event(event, value);
- }
}
}
continue;
if (sscanf(val.c_str(), "PERIODICITY %lg\n", &periodicity) == 1)
continue;
- if (sscanf(val.c_str(), "WAITFOR %lg\n", &periodicity) == 1)
+ if (sscanf(val.c_str(), "LOOPAFTER %lg\n", &periodicity) == 1)
continue;
xbt_assert(sscanf(val.c_str(), "%lg %lg\n", &event.date_, &event.value_) == 2, "%s:%d: Syntax error in trace\n%s",
std::vector<tmgr::DatedValue> got;
trace2vector("1.0 1.0\n"
"3.0 3.0\n"
- "WAITFOR 2\n",
+ "LOOPAFTER 2\n",
&got);
std::vector<tmgr::DatedValue> want;
std::vector<tmgr::DatedValue> got;
trace2vector("0.0 1\n"
"5.0 2\n"
- "WAITFOR 5\n",
+ "LOOPAFTER 5\n",
&got);
std::vector<tmgr::DatedValue> want;
0 1.0
11 0.5
20 0.8
-WAITFOR 1
+LOOPAFTER 1
1 -1.0
2 1.0
-WAITFOR 10
+LOOPAFTER 10
0 1.0
9 0.7
15 0.4
-WAITFOR 1
+LOOPAFTER 1
4 40000000
8 60000000
-WAITFOR 12
+LOOPAFTER 12
1 -1.0
2 1.0
-WAITFOR 10
+LOOPAFTER 10
1 0.001
2 0.01
3 0.001
-WAITFOR 5
+LOOPAFTER 5