13 SS13 Results
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | 1042.7 | 0.0 | 0.0 |
| 2 | 8 | TÄN | 1056.8 | 14.1 | 14.1 |
| 3 | 1 | OGI | 1070.7 | 28.0 | 13.9 |
| 4 | 16 | FOU | 1071.9 | 29.2 | 1.2 |
| 5 | 6 | SOR | 1072.6 | 29.9 | 0.7 |
| 6 | 11 | NEU | 1084.8 | 42.1 | 12.2 |
| 7 | 33 | EVA | 1088.0 | 45.3 | 3.2 |
| 8 | 44 | GRE | 1109.9 | 67.2 | 0.2 |
13.1 Stage SS13 Splits Analysis
Reports on splits
13.1.1 Split Locations
Length of each split section in km:
| full_split_distances | stage_dist | |
|---|---|---|
| split_1 | 4.03 | 4.03 |
| split_2 | 6.66 | 10.69 |
| split_3 | 4.12 | 14.81 |
| split_4 | 4.83 | 19.64 |
| split_5 | 2.63 | 22.27 |
| split_N | 1.10 | 23.37 |
13.1.2 Stage Split Times & Result
Summary of stage split times and overall stage result:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N | diffFirstS | position |
|---|---|---|---|---|---|---|---|---|
| ROV | 193.8 | 505.7 | 696.5 | 881.4 | 1004.3 | 1042.7 | 0.0 | 1 |
| TÄN | 198.0 | 516.1 | 707.2 | 894.3 | 1017.8 | 1056.8 | 14.1 | 2 |
| OGI | 199.4 | 519.3 | 714.5 | 905.2 | 1031.0 | 1070.7 | 28.0 | 3 |
| FOU | 197.8 | 522.0 | 717.0 | 907.1 | 1032.4 | 1071.9 | 29.2 | 4 |
| SOR | 199.9 | 522.6 | 716.1 | 907.9 | 1033.0 | 1072.6 | 29.9 | 5 |
| NEU | 203.5 | 527.8 | 721.3 | 916.5 | 1044.3 | 1084.8 | 42.1 | 6 |
| EVA | 202.9 | 528.9 | 725.0 | 919.4 | 1047.8 | 1088.0 | 45.3 | 7 |
| GRE | 208.8 | 540.2 | 740.1 | 940.1 | 1069.4 | 1109.9 | 67.2 | 14 |
13.1.3 Split Time Rankings
Rank of each split time:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 1 | 1 | 1 | 1 | 1 | 1 |
| TÄN | 3 | 2 | 2 | 2 | 2 | 2 |
| OGI | 4 | 3 | 3 | 3 | 3 | 3 |
| FOU | 2 | 4 | 5 | 4 | 4 | 4 |
| SOR | 5 | 5 | 4 | 5 | 5 | 5 |
| NEU | 7 | 6 | 6 | 6 | 6 | 6 |
| EVA | 6 | 7 | 7 | 7 | 7 | 7 |
| GRE | 8 | 8 | 8 | 8 | 8 | 8 |
Rank on each split section:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 1 | 1 | 1 | 1 | 1 | 1 |
| TÄN | 3 | 2 | 2 | 2 | 2 | 2 |
| OGI | 4 | 3 | 5 | 4 | 5 | 5 |
| FOU | 2 | 5 | 4 | 3 | 4 | 3 |
| SOR | 5 | 4 | 3 | 5 | 3 | 4 |
| NEU | 7 | 6 | 3 | 7 | 6 | 7 |
| EVA | 6 | 7 | 6 | 6 | 7 | 6 |
| GRE | 8 | 8 | 7 | 8 | 8 | 7 |
13.1.4 Split Section Pace
Pace is measured in seconds per kilometer, which is to say, how long it takes to complete each kilometer (lower is better):
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 48.09 | 46.83 | 46.31 | 38.28 | 46.73 | 34.91 |
| TÄN | 49.13 | 47.76 | 46.38 | 38.74 | 46.96 | 35.45 |
| OGI | 49.48 | 48.03 | 47.38 | 39.48 | 47.83 | 36.09 |
| FOU | 49.08 | 48.68 | 47.33 | 39.36 | 47.64 | 35.91 |
| SOR | 49.60 | 48.45 | 46.97 | 39.71 | 47.57 | 36.00 |
| NEU | 50.50 | 48.69 | 46.97 | 40.41 | 48.59 | 36.82 |
| EVA | 50.35 | 48.95 | 47.60 | 40.25 | 48.82 | 36.55 |
| GRE | 51.81 | 49.76 | 48.52 | 41.41 | 49.16 | 36.82 |
13.1.5 Pace Chart
Pace relative to the stage winner.
13.1.6 Ultimate Stage Comparisons
Split time comparisons relative to various ultimate stage time calculations.
These views provide various ways of comparing the performance of each driver to various ghost drivers:
- best recorded split time at each split (ultimate actuals): gives an estimate of how well the driver’s split times compare with each first ranked split time (time into stage at each split);
- fastest time going from one split to the next (ultimate sections): gives an estimate of how quickly each driver completed each split section relative to the quickest time recorded completing that split section (time taken to go from one split point to the next);
- accumulated ultimate sections times: gives and estimate of how quickly the driver is going relative to the fastest possible completion of the stage based on accumulated ultimate split section times.
<IP_ADDRESS> Ultimate Actuals
Driver times compared to the first ranked recorded split time at each split:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| TÄN | 4.2 | 10.4 | 10.7 | 12.9 | 13.5 | 14.1 |
| OGI | 5.6 | 13.6 | 18.0 | 23.8 | 26.7 | 28.0 |
| FOU | 4.0 | 16.3 | 20.5 | 25.7 | 28.1 | 29.2 |
| SOR | 6.1 | 16.9 | 19.6 | 26.5 | 28.7 | 29.9 |
| NEU | 9.7 | 22.1 | 24.8 | 35.1 | 40.0 | 42.1 |
| EVA | 9.1 | 23.2 | 28.5 | 38.0 | 43.5 | 45.3 |
| GRE | 15.0 | 34.5 | 43.6 | 58.7 | 65.1 | 67.2 |
| ultimate | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
<IP_ADDRESS> Ultimate Sections
Split durations rebased relative to the fastest transit of each split section:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| TÄN | 4.2 | 6.2 | 0.3 | 2.2 | 0.6 | 0.6 |
| OGI | 5.6 | 8.0 | 4.4 | 5.8 | 2.9 | 1.3 |
| FOU | 4.0 | 12.3 | 4.2 | 5.2 | 2.4 | 1.1 |
| SOR | 6.1 | 10.8 | 2.7 | 6.9 | 2.2 | 1.2 |
| NEU | 9.7 | 12.4 | 2.7 | 10.3 | 4.9 | 2.1 |
| EVA | 9.1 | 14.1 | 5.3 | 9.5 | 5.5 | 1.8 |
| GRE | 15.0 | 19.5 | 9.1 | 15.1 | 6.4 | 2.1 |
| ultimate | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
<IP_ADDRESS> Ultimate Accumulated Sections
Actual split times relative to the accumulated ultimate split section times:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| TÄN | 4.2 | 10.4 | 10.7 | 12.9 | 13.5 | 14.1 |
| OGI | 5.6 | 13.6 | 18.0 | 23.8 | 26.7 | 28.0 |
| FOU | 4.0 | 16.3 | 20.5 | 25.7 | 28.1 | 29.2 |
| SOR | 6.1 | 16.9 | 19.6 | 26.5 | 28.7 | 29.9 |
| NEU | 9.7 | 22.1 | 24.8 | 35.1 | 40.0 | 42.1 |
| EVA | 9.1 | 23.2 | 28.5 | 38.0 | 43.5 | 45.3 |
| GRE | 15.0 | 34.5 | 43.6 | 58.7 | 65.1 | 67.2 |
| ultimate | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
13.1.7 Split Section Pace Distribution
Distribution of pace values for each split section:
13.2 Text report
| code | identifier | entryId | stage | overall_pos | prev_position | retained_lead | lost_lead | gained_lead | overall_position_delta | overall_chase_code | overall_lead_code | overall_gap | overall_diff | overall_chase | overall_stage_pos | stage_position | stage_win | position | TimeInS | gap | diff | chase | chase_code | lead_code |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ROV | 69 | 23550 | SS13 | 1 | 1 | TRUE | FALSE | FALSE | 0 | TÄN | NA | 0.0 | NA | 44.9 | 1 | 1 | TRUE | 1 | 1042.7 | 0.0 | 0.0 | 14.1 | TÄN | NA |
| TÄN | 8 | 23551 | SS13 | 2 | 2 | FALSE | FALSE | FALSE | 0 | OGI | ROV | 44.9 | 44.9 | 23.3 | 2 | 2 | FALSE | 2 | 1056.8 | 14.1 | 14.1 | 13.9 | OGI | ROV |
| OGI | 1 | 23547 | SS13 | 3 | 3 | FALSE | FALSE | FALSE | 0 | SOR | TÄN | 68.2 | 23.3 | 91.1 | 3 | 3 | FALSE | 3 | 1070.7 | 28.0 | 13.9 | 1.2 | FOU | TÄN |
| FOU | 16 | 23555 | SS13 | 7 | 5 | FALSE | FALSE | FALSE | -2 | NEU | EVA | 408.4 | 11.2 | 101.3 | 4 | 4 | FALSE | 4 | 1071.9 | 29.2 | 1.2 | 0.7 | SOR | OGI |
| SOR | 6 | 23554 | SS13 | 4 | 4 | FALSE | FALSE | FALSE | 0 | GRE | OGI | 159.3 | 91.1 | 122.9 | 5 | 5 | FALSE | 5 | 1072.6 | 29.9 | 0.7 | 12.2 | NEU | FOU |
| NEU | 11 | 23549 | SS13 | 8 | 8 | FALSE | FALSE | FALSE | 0 | LOU | FOU | 509.7 | 101.3 | NA | 6 | 6 | FALSE | 6 | 1084.8 | 42.1 | 12.2 | 3.2 | EVA | SOR |
| EVA | 33 | 23548 | SS13 | 6 | 7 | FALSE | FALSE | FALSE | 1 | FOU | GRE | 397.2 | 115.0 | 11.2 | 7 | 7 | FALSE | 7 | 1088.0 | 45.3 | 3.2 | 21.9 | GRE | NEU |
| GRE | 44 | 23553 | SS13 | 5 | 6 | FALSE | FALSE | FALSE | 1 | EVA | SOR | 282.2 | 122.9 | 115.0 | 14 | 8 | FALSE | 8 | 1109.9 | 67.2 | 0.2 | NA | LOU | EVA |
| LOU | 7 | 23556 | SS13 | NA | 9 | FALSE | FALSE | FALSE | NA | NA | NEU | NA | NA | NA | NA | 9 | FALSE | 9 | NA | NA | NA | NA | NA | GRE |
Stage report for SS13:
ROV recorded the stage win and retained overall lead of the rally making a time of 1042.7s.
TÄN was in second position on stage, 14.1s behind stage winner ROV .
OGI was in third place on stage, 13.9s behind TÄN .
FOU took fourth place on stage, 29.2s behind ROV dropped two places to seventh overall.
SOR took fifth on stage, with a time of 1072.6s, just 0.7s off FOU.
NEU took sixth on stage, with a time of 1084.8s .
EVA was in seventh on stage, 45.3s behind ROV and moved up one place to sixth overall.
GRE was in fourteenth on stage, 67.2s behind ROV and moved up one place to fifth overall, only 0.2s further back behind EVA.
13.3 Driver Report, SS13 - OGI
OGI was in third place on stage, 13.9s behind TÄN .
Stage report for OGI.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -28.0 | -28.0 | 0.0 |
| 2 | 8 | TÄN | -13.9 | -13.9 | 14.1 |
| 3 | 1 | OGI | 0.0 | 0.0 | 13.9 |
| 4 | 16 | FOU | 1.2 | 1.2 | 1.2 |
| 5 | 6 | SOR | 1.9 | 1.9 | 0.7 |
| 6 | 11 | NEU | 14.1 | 14.1 | 12.2 |
| 7 | 33 | EVA | 17.3 | 17.3 | 3.2 |
| 14 | 44 | GRE | 39.2 | 39.2 | 0.2 |
13.3.1 Rebased Split Times
OGI’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -5.6 | -13.6 | -18.0 | -23.8 | -26.7 | -28.0 |
| TÄN | -1.4 | -3.2 | -7.3 | -10.9 | -13.2 | -13.9 |
| OGI | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| FOU | -1.6 | 2.7 | 2.5 | 1.9 | 1.4 | 1.2 |
| SOR | 0.5 | 3.3 | 1.6 | 2.7 | 2.0 | 1.9 |
| NEU | 4.1 | 8.5 | 6.8 | 11.3 | 13.3 | 14.1 |
| EVA | 3.5 | 9.6 | 10.5 | 14.2 | 16.8 | 17.3 |
| GRE | 9.4 | 20.9 | 25.6 | 34.9 | 38.4 | 39.2 |
13.3.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.3.3 Within-Split Duration Deltas
OGI’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -5.6 | -8.0 | -4.4 | -5.8 | -2.9 | -1.3 |
| TÄN | -1.4 | -1.8 | -4.1 | -3.6 | -2.3 | -0.7 |
| OGI | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| FOU | -1.6 | 4.3 | -0.2 | -0.6 | -0.5 | -0.2 |
| SOR | 0.5 | 2.8 | -1.7 | 1.1 | -0.7 | -0.1 |
| NEU | 4.1 | 4.4 | -1.7 | 4.5 | 2.0 | 0.8 |
| EVA | 3.5 | 6.1 | 0.9 | 3.7 | 2.6 | 0.5 |
| GRE | 9.4 | 11.5 | 4.7 | 9.3 | 3.5 | 0.8 |
13.3.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -1.39 | -1.20 | -1.07 | -1.20 | -1.10 | -1.18 |
| TÄN | -0.35 | -0.27 | -1.00 | -0.75 | -0.87 | -0.64 |
| OGI | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| FOU | -0.40 | 0.65 | -0.05 | -0.12 | -0.19 | -0.18 |
| SOR | 0.12 | 0.42 | -0.41 | 0.23 | -0.27 | -0.09 |
| NEU | 1.02 | 0.66 | -0.41 | 0.93 | 0.76 | 0.73 |
| EVA | 0.87 | 0.92 | 0.22 | 0.77 | 0.99 | 0.45 |
| GRE | 2.33 | 1.73 | 1.14 | 1.93 | 1.33 | 0.73 |
13.3.5 Within-Split Pace Map
13.4 Driver Report, SS13 - EVA
EVA was in seventh on stage, 45.3s behind ROV and moved up one place to sixth overall.
Stage report for EVA.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -45.3 | -45.3 | 0.0 |
| 2 | 8 | TÄN | -31.2 | -31.2 | 14.1 |
| 3 | 1 | OGI | -17.3 | -17.3 | 13.9 |
| 4 | 16 | FOU | -16.1 | -16.1 | 1.2 |
| 5 | 6 | SOR | -15.4 | -15.4 | 0.7 |
| 6 | 11 | NEU | -3.2 | -3.2 | 12.2 |
| 7 | 33 | EVA | 0.0 | 0.0 | 3.2 |
| 14 | 44 | GRE | 21.9 | 21.9 | 0.2 |
13.4.1 Rebased Split Times
EVA’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -9.1 | -23.2 | -28.5 | -38.0 | -43.5 | -45.3 |
| TÄN | -4.9 | -12.8 | -17.8 | -25.1 | -30.0 | -31.2 |
| OGI | -3.5 | -9.6 | -10.5 | -14.2 | -16.8 | -17.3 |
| FOU | -5.1 | -6.9 | -8.0 | -12.3 | -15.4 | -16.1 |
| SOR | -3.0 | -6.3 | -8.9 | -11.5 | -14.8 | -15.4 |
| NEU | 0.6 | -1.1 | -3.7 | -2.9 | -3.5 | -3.2 |
| EVA | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| GRE | 5.9 | 11.3 | 15.1 | 20.7 | 21.6 | 21.9 |
13.4.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.4.3 Within-Split Duration Deltas
EVA’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -9.1 | -14.1 | -5.3 | -9.5 | -5.5 | -1.8 |
| TÄN | -4.9 | -7.9 | -5.0 | -7.3 | -4.9 | -1.2 |
| OGI | -3.5 | -6.1 | -0.9 | -3.7 | -2.6 | -0.5 |
| FOU | -5.1 | -1.8 | -1.1 | -4.3 | -3.1 | -0.7 |
| SOR | -3.0 | -3.3 | -2.6 | -2.6 | -3.3 | -0.6 |
| NEU | 0.6 | -1.7 | -2.6 | 0.8 | -0.6 | 0.3 |
| EVA | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| GRE | 5.9 | 5.4 | 3.8 | 5.6 | 0.9 | 0.3 |
13.4.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -2.26 | -2.12 | -1.29 | -1.97 | -2.09 | -1.64 |
| TÄN | -1.22 | -1.19 | -1.21 | -1.51 | -1.86 | -1.09 |
| OGI | -0.87 | -0.92 | -0.22 | -0.77 | -0.99 | -0.45 |
| FOU | -1.27 | -0.27 | -0.27 | -0.89 | -1.18 | -0.64 |
| SOR | -0.74 | -0.50 | -0.63 | -0.54 | -1.25 | -0.55 |
| NEU | 0.15 | -0.26 | -0.63 | 0.17 | -0.23 | 0.27 |
| EVA | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| GRE | 1.46 | 0.81 | 0.92 | 1.16 | 0.34 | 0.27 |
13.4.5 Within-Split Pace Map
13.5 Driver Report, SS13 - NEU
NEU took sixth on stage, with a time of 1084.8s .
Stage report for NEU.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -42.1 | -42.1 | 0.0 |
| 2 | 8 | TÄN | -28.0 | -28.0 | 14.1 |
| 3 | 1 | OGI | -14.1 | -14.1 | 13.9 |
| 4 | 16 | FOU | -12.9 | -12.9 | 1.2 |
| 5 | 6 | SOR | -12.2 | -12.2 | 0.7 |
| 6 | 11 | NEU | 0.0 | 0.0 | 12.2 |
| 7 | 33 | EVA | 3.2 | 3.2 | 3.2 |
| 14 | 44 | GRE | 25.1 | 25.1 | 0.2 |
13.5.1 Rebased Split Times
NEU’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -9.7 | -22.1 | -24.8 | -35.1 | -40.0 | -42.1 |
| TÄN | -5.5 | -11.7 | -14.1 | -22.2 | -26.5 | -28.0 |
| OGI | -4.1 | -8.5 | -6.8 | -11.3 | -13.3 | -14.1 |
| FOU | -5.7 | -5.8 | -4.3 | -9.4 | -11.9 | -12.9 |
| SOR | -3.6 | -5.2 | -5.2 | -8.6 | -11.3 | -12.2 |
| NEU | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| EVA | -0.6 | 1.1 | 3.7 | 2.9 | 3.5 | 3.2 |
| GRE | 5.3 | 12.4 | 18.8 | 23.6 | 25.1 | 25.1 |
13.5.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.5.3 Within-Split Duration Deltas
NEU’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -9.7 | -12.4 | -2.7 | -10.3 | -4.9 | -2.1 |
| TÄN | -5.5 | -6.2 | -2.4 | -8.1 | -4.3 | -1.5 |
| OGI | -4.1 | -4.4 | 1.7 | -4.5 | -2.0 | -0.8 |
| FOU | -5.7 | -0.1 | 1.5 | -5.1 | -2.5 | -1.0 |
| SOR | -3.6 | -1.6 | 0.0 | -3.4 | -2.7 | -0.9 |
| NEU | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| EVA | -0.6 | 1.7 | 2.6 | -0.8 | 0.6 | -0.3 |
| GRE | 5.3 | 7.1 | 6.4 | 4.8 | 1.5 | 0.0 |
13.5.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -2.41 | -1.86 | -0.66 | -2.13 | -1.86 | -1.91 |
| TÄN | -1.36 | -0.93 | -0.58 | -1.68 | -1.63 | -1.36 |
| OGI | -1.02 | -0.66 | 0.41 | -0.93 | -0.76 | -0.73 |
| FOU | -1.41 | -0.02 | 0.36 | -1.06 | -0.95 | -0.91 |
| SOR | -0.89 | -0.24 | 0.00 | -0.70 | -1.03 | -0.82 |
| NEU | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| EVA | -0.15 | 0.26 | 0.63 | -0.17 | 0.23 | -0.27 |
| GRE | 1.32 | 1.07 | 1.55 | 0.99 | 0.57 | 0.00 |
13.5.5 Within-Split Pace Map
13.6 Driver Report, SS13 - ROV
ROV recorded the stage win and retained overall lead of the rally making a time of 1042.7s.
Stage report for ROV.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | 0.0 | 0.0 | 0.0 |
| 2 | 8 | TÄN | 14.1 | 14.1 | 14.1 |
| 3 | 1 | OGI | 28.0 | 28.0 | 13.9 |
| 4 | 16 | FOU | 29.2 | 29.2 | 1.2 |
| 5 | 6 | SOR | 29.9 | 29.9 | 0.7 |
| 6 | 11 | NEU | 42.1 | 42.1 | 12.2 |
| 7 | 33 | EVA | 45.3 | 45.3 | 3.2 |
| 14 | 44 | GRE | 67.2 | 67.2 | 0.2 |
13.6.1 Rebased Split Times
ROV’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| TÄN | 4.2 | 10.4 | 10.7 | 12.9 | 13.5 | 14.1 |
| OGI | 5.6 | 13.6 | 18.0 | 23.8 | 26.7 | 28.0 |
| FOU | 4.0 | 16.3 | 20.5 | 25.7 | 28.1 | 29.2 |
| SOR | 6.1 | 16.9 | 19.6 | 26.5 | 28.7 | 29.9 |
| NEU | 9.7 | 22.1 | 24.8 | 35.1 | 40.0 | 42.1 |
| EVA | 9.1 | 23.2 | 28.5 | 38.0 | 43.5 | 45.3 |
| GRE | 15.0 | 34.5 | 43.6 | 58.7 | 65.1 | 67.2 |
13.6.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.6.3 Within-Split Duration Deltas
ROV’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| TÄN | 4.2 | 6.2 | 0.3 | 2.2 | 0.6 | 0.6 |
| OGI | 5.6 | 8.0 | 4.4 | 5.8 | 2.9 | 1.3 |
| FOU | 4.0 | 12.3 | 4.2 | 5.2 | 2.4 | 1.1 |
| SOR | 6.1 | 10.8 | 2.7 | 6.9 | 2.2 | 1.2 |
| NEU | 9.7 | 12.4 | 2.7 | 10.3 | 4.9 | 2.1 |
| EVA | 9.1 | 14.1 | 5.3 | 9.5 | 5.5 | 1.8 |
| GRE | 15.0 | 19.5 | 9.1 | 15.1 | 6.4 | 2.1 |
13.6.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| TÄN | 1.04 | 0.93 | 0.07 | 0.46 | 0.23 | 0.55 |
| OGI | 1.39 | 1.20 | 1.07 | 1.20 | 1.10 | 1.18 |
| FOU | 0.99 | 1.85 | 1.02 | 1.08 | 0.91 | 1.00 |
| SOR | 1.51 | 1.62 | 0.66 | 1.43 | 0.84 | 1.09 |
| NEU | 2.41 | 1.86 | 0.66 | 2.13 | 1.86 | 1.91 |
| EVA | 2.26 | 2.12 | 1.29 | 1.97 | 2.09 | 1.64 |
| GRE | 3.72 | 2.93 | 2.21 | 3.13 | 2.43 | 1.91 |
13.6.5 Within-Split Pace Map
13.7 Driver Report, SS13 - TÄN
TÄN was in second position on stage, 14.1s behind stage winner ROV .
Stage report for TÄN.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -14.1 | -14.1 | 0.0 |
| 2 | 8 | TÄN | 0.0 | 0.0 | 14.1 |
| 3 | 1 | OGI | 13.9 | 13.9 | 13.9 |
| 4 | 16 | FOU | 15.1 | 15.1 | 1.2 |
| 5 | 6 | SOR | 15.8 | 15.8 | 0.7 |
| 6 | 11 | NEU | 28.0 | 28.0 | 12.2 |
| 7 | 33 | EVA | 31.2 | 31.2 | 3.2 |
| 14 | 44 | GRE | 53.1 | 53.1 | 0.2 |
13.7.1 Rebased Split Times
TÄN’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -4.2 | -10.4 | -10.7 | -12.9 | -13.5 | -14.1 |
| TÄN | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| OGI | 1.4 | 3.2 | 7.3 | 10.9 | 13.2 | 13.9 |
| FOU | -0.2 | 5.9 | 9.8 | 12.8 | 14.6 | 15.1 |
| SOR | 1.9 | 6.5 | 8.9 | 13.6 | 15.2 | 15.8 |
| NEU | 5.5 | 11.7 | 14.1 | 22.2 | 26.5 | 28.0 |
| EVA | 4.9 | 12.8 | 17.8 | 25.1 | 30.0 | 31.2 |
| GRE | 10.8 | 24.1 | 32.9 | 45.8 | 51.6 | 53.1 |
13.7.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.7.3 Within-Split Duration Deltas
TÄN’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -4.2 | -6.2 | -0.3 | -2.2 | -0.6 | -0.6 |
| TÄN | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| OGI | 1.4 | 1.8 | 4.1 | 3.6 | 2.3 | 0.7 |
| FOU | -0.2 | 6.1 | 3.9 | 3.0 | 1.8 | 0.5 |
| SOR | 1.9 | 4.6 | 2.4 | 4.7 | 1.6 | 0.6 |
| NEU | 5.5 | 6.2 | 2.4 | 8.1 | 4.3 | 1.5 |
| EVA | 4.9 | 7.9 | 5.0 | 7.3 | 4.9 | 1.2 |
| GRE | 10.8 | 13.3 | 8.8 | 12.9 | 5.8 | 1.5 |
13.7.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -1.04 | -0.93 | -0.07 | -0.46 | -0.23 | -0.55 |
| TÄN | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| OGI | 0.35 | 0.27 | 1.00 | 0.75 | 0.87 | 0.64 |
| FOU | -0.05 | 0.92 | 0.95 | 0.62 | 0.68 | 0.45 |
| SOR | 0.47 | 0.69 | 0.58 | 0.97 | 0.61 | 0.55 |
| NEU | 1.36 | 0.93 | 0.58 | 1.68 | 1.63 | 1.36 |
| EVA | 1.22 | 1.19 | 1.21 | 1.51 | 1.86 | 1.09 |
| GRE | 2.68 | 2.00 | 2.14 | 2.67 | 2.21 | 1.36 |
13.7.5 Within-Split Pace Map
13.8 Driver Report, SS13 - KAT
No stage report for KAT.
13.9 Driver Report, SS13 - GRE
GRE was in fourteenth on stage, 67.2s behind ROV and moved up one place to fifth overall, only 0.2s further back behind EVA.
Stage report for GRE.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -67.2 | -67.2 | 0.0 |
| 2 | 8 | TÄN | -53.1 | -53.1 | 14.1 |
| 3 | 1 | OGI | -39.2 | -39.2 | 13.9 |
| 4 | 16 | FOU | -38.0 | -38.0 | 1.2 |
| 5 | 6 | SOR | -37.3 | -37.3 | 0.7 |
| 6 | 11 | NEU | -25.1 | -25.1 | 12.2 |
| 7 | 33 | EVA | -21.9 | -21.9 | 3.2 |
| 14 | 44 | GRE | 0.0 | 0.0 | 0.2 |
13.9.1 Rebased Split Times
GRE’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -15.0 | -34.5 | -43.6 | -58.7 | -65.1 | -67.2 |
| TÄN | -10.8 | -24.1 | -32.9 | -45.8 | -51.6 | -53.1 |
| OGI | -9.4 | -20.9 | -25.6 | -34.9 | -38.4 | -39.2 |
| FOU | -11.0 | -18.2 | -23.1 | -33.0 | -37.0 | -38.0 |
| SOR | -8.9 | -17.6 | -24.0 | -32.2 | -36.4 | -37.3 |
| NEU | -5.3 | -12.4 | -18.8 | -23.6 | -25.1 | -25.1 |
| EVA | -5.9 | -11.3 | -15.1 | -20.7 | -21.6 | -21.9 |
| GRE | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
13.9.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.9.3 Within-Split Duration Deltas
GRE’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -15.0 | -19.5 | -9.1 | -15.1 | -6.4 | -2.1 |
| TÄN | -10.8 | -13.3 | -8.8 | -12.9 | -5.8 | -1.5 |
| OGI | -9.4 | -11.5 | -4.7 | -9.3 | -3.5 | -0.8 |
| FOU | -11.0 | -7.2 | -4.9 | -9.9 | -4.0 | -1.0 |
| SOR | -8.9 | -8.7 | -6.4 | -8.2 | -4.2 | -0.9 |
| NEU | -5.3 | -7.1 | -6.4 | -4.8 | -1.5 | 0.0 |
| EVA | -5.9 | -5.4 | -3.8 | -5.6 | -0.9 | -0.3 |
| GRE | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
13.9.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -3.72 | -2.93 | -2.21 | -3.13 | -2.43 | -1.91 |
| TÄN | -2.68 | -2.00 | -2.14 | -2.67 | -2.21 | -1.36 |
| OGI | -2.33 | -1.73 | -1.14 | -1.93 | -1.33 | -0.73 |
| FOU | -2.73 | -1.08 | -1.19 | -2.05 | -1.52 | -0.91 |
| SOR | -2.21 | -1.31 | -1.55 | -1.70 | -1.60 | -0.82 |
| NEU | -1.32 | -1.07 | -1.55 | -0.99 | -0.57 | 0.00 |
| EVA | -1.46 | -0.81 | -0.92 | -1.16 | -0.34 | -0.27 |
| GRE | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
13.9.5 Within-Split Pace Map
13.10 Driver Report, SS13 - SOR
SOR took fifth on stage, with a time of 1072.6s, just 0.7s off FOU.
Stage report for SOR.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -29.9 | -29.9 | 0.0 |
| 2 | 8 | TÄN | -15.8 | -15.8 | 14.1 |
| 3 | 1 | OGI | -1.9 | -1.9 | 13.9 |
| 4 | 16 | FOU | -0.7 | -0.7 | 1.2 |
| 5 | 6 | SOR | 0.0 | 0.0 | 0.7 |
| 6 | 11 | NEU | 12.2 | 12.2 | 12.2 |
| 7 | 33 | EVA | 15.4 | 15.4 | 3.2 |
| 14 | 44 | GRE | 37.3 | 37.3 | 0.2 |
13.10.1 Rebased Split Times
SOR’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -6.1 | -16.9 | -19.6 | -26.5 | -28.7 | -29.9 |
| TÄN | -1.9 | -6.5 | -8.9 | -13.6 | -15.2 | -15.8 |
| OGI | -0.5 | -3.3 | -1.6 | -2.7 | -2.0 | -1.9 |
| FOU | -2.1 | -0.6 | 0.9 | -0.8 | -0.6 | -0.7 |
| SOR | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| NEU | 3.6 | 5.2 | 5.2 | 8.6 | 11.3 | 12.2 |
| EVA | 3.0 | 6.3 | 8.9 | 11.5 | 14.8 | 15.4 |
| GRE | 8.9 | 17.6 | 24.0 | 32.2 | 36.4 | 37.3 |
13.10.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.10.3 Within-Split Duration Deltas
SOR’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -6.1 | -10.8 | -2.7 | -6.9 | -2.2 | -1.2 |
| TÄN | -1.9 | -4.6 | -2.4 | -4.7 | -1.6 | -0.6 |
| OGI | -0.5 | -2.8 | 1.7 | -1.1 | 0.7 | 0.1 |
| FOU | -2.1 | 1.5 | 1.5 | -1.7 | 0.2 | -0.1 |
| SOR | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| NEU | 3.6 | 1.6 | 0.0 | 3.4 | 2.7 | 0.9 |
| EVA | 3.0 | 3.3 | 2.6 | 2.6 | 3.3 | 0.6 |
| GRE | 8.9 | 8.7 | 6.4 | 8.2 | 4.2 | 0.9 |
13.10.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -1.51 | -1.62 | -0.66 | -1.43 | -0.84 | -1.09 |
| TÄN | -0.47 | -0.69 | -0.58 | -0.97 | -0.61 | -0.55 |
| OGI | -0.12 | -0.42 | 0.41 | -0.23 | 0.27 | 0.09 |
| FOU | -0.52 | 0.23 | 0.36 | -0.35 | 0.08 | -0.09 |
| SOR | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| NEU | 0.89 | 0.24 | 0.00 | 0.70 | 1.03 | 0.82 |
| EVA | 0.74 | 0.50 | 0.63 | 0.54 | 1.25 | 0.55 |
| GRE | 2.21 | 1.31 | 1.55 | 1.70 | 1.60 | 0.82 |
13.10.5 Within-Split Pace Map
13.11 Driver Report, SS13 - FOU
FOU took fourth place on stage, 29.2s behind ROV dropped two places to seventh overall.
Stage report for FOU.
| Pos | Car | Code | Time (s) | Gap | Diff |
|---|---|---|---|---|---|
| 1 | 69 | ROV | -29.2 | -29.2 | 0.0 |
| 2 | 8 | TÄN | -15.1 | -15.1 | 14.1 |
| 3 | 1 | OGI | -1.2 | -1.2 | 13.9 |
| 4 | 16 | FOU | 0.0 | 0.0 | 1.2 |
| 5 | 6 | SOR | 0.7 | 0.7 | 0.7 |
| 6 | 11 | NEU | 12.9 | 12.9 | 12.2 |
| 7 | 33 | EVA | 16.1 | 16.1 | 3.2 |
| 14 | 44 | GRE | 38.0 | 38.0 | 0.2 |
13.11.1 Rebased Split Times
FOU’s delta at each split compared to other drivers.
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -4.0 | -16.3 | -20.5 | -25.7 | -28.1 | -29.2 |
| TÄN | 0.2 | -5.9 | -9.8 | -12.8 | -14.6 | -15.1 |
| OGI | 1.6 | -2.7 | -2.5 | -1.9 | -1.4 | -1.2 |
| FOU | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| SOR | 2.1 | 0.6 | -0.9 | 0.8 | 0.6 | 0.7 |
| NEU | 5.7 | 5.8 | 4.3 | 9.4 | 11.9 | 12.9 |
| EVA | 5.1 | 6.9 | 8.0 | 12.3 | 15.4 | 16.1 |
| GRE | 11.0 | 18.2 | 23.1 | 33.0 | 37.0 | 38.0 |
13.11.2 Off-the-Pace Chart
Accumulated stage time deltas at each split:
13.11.3 Within-Split Duration Deltas
FOU’s delta in time to complete each split section compared to other drivers:
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -4.0 | -12.3 | -4.2 | -5.2 | -2.4 | -1.1 |
| TÄN | 0.2 | -6.1 | -3.9 | -3.0 | -1.8 | -0.5 |
| OGI | 1.6 | -4.3 | 0.2 | 0.6 | 0.5 | 0.2 |
| FOU | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| SOR | 2.1 | -1.5 | -1.5 | 1.7 | -0.2 | 0.1 |
| NEU | 5.7 | 0.1 | -1.5 | 5.1 | 2.5 | 1.0 |
| EVA | 5.1 | 1.8 | 1.1 | 4.3 | 3.1 | 0.7 |
| GRE | 11.0 | 7.2 | 4.9 | 9.9 | 4.0 | 1.0 |
13.11.4 Within-Split Pace Deltas
| code | split_1 | split_2 | split_3 | split_4 | split_5 | split_N |
|---|---|---|---|---|---|---|
| ROV | -0.99 | -1.85 | -1.02 | -1.08 | -0.91 | -1.00 |
| TÄN | 0.05 | -0.92 | -0.95 | -0.62 | -0.68 | -0.45 |
| OGI | 0.40 | -0.65 | 0.05 | 0.12 | 0.19 | 0.18 |
| FOU | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 | 0.00 |
| SOR | 0.52 | -0.23 | -0.36 | 0.35 | -0.08 | 0.09 |
| NEU | 1.41 | 0.02 | -0.36 | 1.06 | 0.95 | 0.91 |
| EVA | 1.27 | 0.27 | 0.27 | 0.89 | 1.18 | 0.64 |
| GRE | 2.73 | 1.08 | 1.19 | 2.05 | 1.52 | 0.91 |
13.11.5 Within-Split Pace Map
13.12 Driver Report, SS13 - LOU
No stage report for LOU.


Dear user,
*** This is a system generated email, do not reply to this email ***
Looks like there are some nodes which are missing one of the required labels:
| Node | Instance type | Creation date | Corresponding run/pool | Missing labels | Action proposed |
| $summary.nodeName | $summary.instanceType | $summary.creationTimestamp |
#set( $correspondingRunStatus = $summary.correspondingRunStatus )
#if ( $correspondingRunStatus )
#set( $statusCode = $correspondingRunStatus.status )
Run $correspondingRunStatus.runId [ #if( $statusCode )$statusCode#{else}UNKNOWN#end] #end #if ( $summary.correspondingPoolId ) Pool $summary.correspondingPoolId #end |
#foreach( $label in $summary.labels )
$label #end |
Delete instance in the $templateParameters["deploymentName"] console |
Those nodes won't be managed automatically by $templateParameters["fullPlatformName"] Platform, please verify nodes' state and terminate them manually.
Best regards,
$templateParameters["fullPlatformName"] Platform


| Values' Details |
A3
A3,
- Description
- specifies the paper format as A3.
|
|
A4
A4,
- Description
- specifies the paper format as A4.
|
|
A5
A5,
- Description
- specifies the paper format as A5.
|
|
B4
B4,
- Description
- specifies the paper format as B4.
|
|
B5
B5,
- Description
- specifies the paper format as B5.
|
|
LETTER
LETTER,
- Description
- specifies the paper format as Letter.
|
|
LEGAL
LEGAL,
- Description
- specifies the paper format as Legal.
|
|
TABLOID
TABLOID,
- Description
- specifies the paper format as Tabloid.
|
|
USER
USER,
- Description
- The real paper size is user defined in 100th mm.
|
|
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


Vert.x allows you to package up your applications or re-usable functionality into modules which can then be referenced by other applications or modules.
By default, Vert.x will assume that the modules for your project live in a local mods
directory relative to where you run Vert.x from. Having a project maintain its own set of modules is the recommended way to structure a Vert.x application.
If you prefer to store your modules in some other place, e.g. a module directory shared by different Vert.x applications you can set the environment variable VERTX_MODS
to point to that.
A module name can be any string. However, we recommend using the following convention:
prefix.<name>-v<version>
Where prefix
is a reversed domain name for your company or organisation (like a Java package name), name
is a descriptive name and version
is a version string.
If the module has been produced by the Vert.x project we use vertx
as the prefix.
Here are some examples:
org.myorg.coolproject.calculator-module-v1.1 com.acme.monitor-v2.0beta5 vertx.mongo-persistor-v1.0
Each actual module lives in its own child directory of the module root directory (given by mods
or VERTX_MODS
). The name of the directory is the full name of the module. Modules must not share a directory.
Inside the module directory you must also provide a file called mod.json
which contains some JSON which describes the module, for example:
{ "main": "mailer.js" }
Runnable modules must contain a field main
which specifies the main verticle to start the module. Main would be something like myscript.groovy
, app.rb
, foo.js
or org.acme.MyApp
. (See the chapter on "running vert.x" in the main manual for a description of what a main is.)
Non-runnable modules (see below) do not need a main
field.
If your main verticle is a worker verticle you must also specify the worker
field with value true
, otherwise it will be assumed it is not a worker.
By default when your module is executing it will see its working directory as the module directory when using the Vert.x API. This is useful if you want to package up an application which contains its own static resources into a module.
However in some cases, you don't want this behaviour, you want the module to see its working directory as the working directory of whoever started the module.
An example of this would be the web-server
module. With the web server, you use it to serve your own static files which exist either outside of a module or in your own module, they do not exist inside the web-server
module itself.
If you want to preserve current working directory, set the field preserve-cwd
to true
in mod.json
. The default value is false
.
You can configure a module to be auto-redeployed if it detects any files were modified, added or deleted in its module directory.
To enable auto re-deploy for a module you should specify a field auto-redeploy
with a value of true
in mod.json
. The default value for auto-redeploy
is false
.
Any scripts or classes you place in the module directory will be available to the module (placed on the module path). If you have any jar dependencies you can also place these in a directory called lib
and these will be added to the module path.
Here's an example JS module:
my-mod/mod.json my-mod/app.js my-mod/other-script.js my-mod/foo.json
In the above app.js
is the main for the module. other-script.js
and foo.json
are scripts/resources used by the module.
java-mod/mod.json java-mod/org/acme/MyMain.class java-mod/lib/other-jar.jar
The above is an example Java mod where org/acme/MyMain.class
is the main, and other-jar.jar
is a jar dependency of the module.
You can of course mix and match multiple languages in a single module.
Modules can be run directly by using the command vertx runmod
. Please see the main manual for a full description of this.
E.g.
vertx runmod org.myorg.mymod-v3.2
You can also run a module programmatically similarly to how you run any verticle programmatically. Please see the core manual for the appropriate language for a full description on how to do this.
E.g. (JavaScript)
vertx.deployModule('org.myorg.mymod-v3.2');
When you run a module using vertx run
or vertx deploy
your actual process working directory is wherever you were when you executed the command.
However the module will be located in the mods
(or VERTX_MODS
) directory. Consequently if your module contains static files - e.g. your module might be a web application that serves static files from the file system, then if your module expects the working directory to be set to module directory it won't find them!
For example, let's say you have a simple webapp that has an HTTP server that serves an index.html which is packaged as a module:
mods/my-web-app/server.js mods/my-web-app/web-root/index.html
And server.js serves the file with:
req.response.sendFile('web-root/index.html');
In the above case the web server expects the working directory to be the module directory.
To solve this we internally adjust all paths such that, if you use the vert.x API for all file access then it will appear as if your working directory is the module directory. I.e. your web app will just work irrespective of where the module is actually installed :)
If you don't want this behaviour you can set the field preserve-cwd
to true
in mod.json
. See above for a description of this field.
Packaging your own module is simple, simply create your vert.x application as normal, then put it all in a directory whose name is the module name, and provide a mod.json
file as described above.
To install it, simply copy the entire directory to your local mods
directory, or the directory specified by VERTX_MODS
if you have decided to set that.
Vert.x operates a module repository at http://github.com/vert-x/vertx-mods
. The idea is this contains various useful modules that you might want to use in your own Vert.x applications.
You can also submit your own modules to the module repository by sending a pull request to the repository.
To install a module manually from the repository use vertx install <module name>
. Try this now from the command line:
vertx install vertx.mongo-persistor-v1.0
You should now have the vertx.mongo-persistor
module version 1.0 installed in your local mods
directory (or VERTX_MODS
if you are using that).
If you attempt to run a module, either on the command line, or programmatically from within another verticle or module, then Vert.x will first look in your local mods
directory (or VERTX_MODS
) to see if it is already installed.
If it is already there, it will be deployed. If it is not already there, Vert.x will attempt to download it from the module repository, and install it.
If Vert.x can't find a module with that name, an error will be reported.
Because of this lazy installation, you can avoid manually installing modules completely, if you so wish, they will be installed automatically the first time they are requested by your application.
To uninstall a module from your local mods
directory (or VERTX_MODS
) use the vertx uninstall <module name>
command. E.g.
vertx uninstall vertx.mongo-persistor-v1.0
You can tell Vert.x to use a different module repository to the default at http://github.com/vert-x/vertx-mods
by specifying the -repo
option when running vertx run
, vertx runmod
or vertx install
. E.g.
vertx install com.acme.my-module-v2.1.beta -repo http://internalrepo.acme.com
This is useful if you want to maintain your own private module repository.
Sometimes you might find that different modules are using the same or similar sets of resources, e.g. .jar
files or scripts, or other resources.
Instead of including the same resources in every module that needs them, you can put those resources in a module of their own, and then declare that other modules includes
them.
The resources of the module will then effectively be put on the module path of the using module.
This is done by specifying an includes
field in the module descriptor.
Let's take an example. We have a jar foo.jar
and a script bar.js
which we want to be used by both com.acme.module1-v1.0
and com.acme.module2-v1.0
.
We create a module that contains bar.js
and foo.jar
(in the lib
directory). Let's call that module com.acme.common-stuff-v1.0
.
Then in the mod.json
of com.acme.module1-v1.0
and com.acme.module2-v1.0
we add an includes
, e.g.:
{ ... "includes":"com.acme.common-stuff-v1.0" }
A module can include many other modules - includes
is a comma-separated list of module names.
If modules that are included in turn include other modules, the entire graph of includes is walked (avoiding circular dependencies) to get the unique set of resources to include on the module path.
If a jar is include more than once from different modules, a warning will be issued.
Modules that only contain resources for re-use are called non-runnable modules and they don't require a main
field in mod.json
. It's also possible to include the resources of runnable modules into another module.
Configuration for a module (if any) should be specified using a JSON configuration file when deploying from the command line using vertx runmod
or passed in when deploying a module programmatically.
Applying configuration this way allows it to be easily and consistently configured irrespective of the language.


[1] by way of a trip down memory lane we caught the 15 bus about 9pp to spend a few hours if that 's all you 've got.
[2] upgraded on the airport there had been 4 of a trip down memory lane we caught the 15 bus about 9pp to spend a few hours if that 's all you 've got.


{{awsCostUsageNoDataMessage}}
{{awsCPUUsageNoDataMessage}}
You have not defined any cost allocation tags. You can learn more from The AWS documentation about Cost Allocation Reports.
{{awsCPUTagNoDataMessage}}


PSM.prysm.package
Superclass for forward models in the PRYSM Python suite
Description
The PSM.prysm.package class provides a superclass for the individual forward models within the PRYSM suite. This superclass is primarily used to hold information about the PRYSM suite and Github repository for use with the PSM.download and PSM information methods.
If you would like to actually implement a PRYSM forward model, please see the classes for specific PRYSM forward models.
Methods
Abstract Inherited
label - Optionally apply a label to a PSM object
rows - Indicate the state vector rows required to run a forward model
disp - Display a PSM object in the console
estimate - Run a forward model on inputs extracted from a state vector ensemble
name - Return a name for a PSM object for use in error messages
parseRows - Process and error check the inputs to the “rows” command


Addy Yeow. (2018). Bitnodes. Retrieved from https://bitnodes.earn.com
About the Ethereum Foundation. (2018). Retrieved from https://www.ethereum.org/foundation
Enterprise Ethereum Alliance. (2018). Retrieved from https://entethalliance.org/
Institute for the Future (IFTF). (2016, April 18). Understand Blockchain in Two Minutes. Retrieved from https://www.youtube.com/watch?v=r43LhSUUGTQ
The Economist. (2015, October 31). The Trust Machine. Retrieved from https://www.economist.com/news/leaders/21677198-technology-behind-bitcoin-could-transform-how-economy-works-trust-machine
Brian Armstrong. (2016, August 31). How Digital Currency Will Change the World. Retrieved from https://blog.coinbase.com/how-digital-currency-will-change-the-world-310663fe4332
Fred Wilson. (2016, July 31). The Golden Age of Open Protocols. Retrieved from http://avc.com/2016/07/the-golden-age-of-open-protocols/
Joseph Lubin. (2015, August 19). Darkest Before Ethereal Dawn. Retrieved from https://media.consensys.net/darkest-before-the-ethereal-dawn-63b351d0491c
Reid Hoffman. (2015, May 15). Why the Blockchain Matters. Retrieved from https://www.wired.co.uk/article/bitcoin-reid-hoffman
Deep Patel. (2017, June 4). Business in the Age of Ethereum. Retrieved from https://techcrunch.com/2017/06/04/business-in-the-age-of-ethereum/
Olaf Carlson-Wee. (2017, January 8). The Futuere is a Decentralized Internet. Retrieved from https://techcrunch.com/2017/01/08/the-future-is-a-decentralized-internet/
Vitalik Buterin. (2017, February 6). The Meaning of Decentralization. Retrieved from https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274
Jesse Grushack. (2015, November 5). Welcome to 3.0. Retrieved from https://medium.com/@ConsenSys/welcome-to-3-0-f4552fb02302
Klint Finley. (2017, April 4). Tim Berners-Lee, Inventor of the Web, Plots a Radical Overhaul of His Creation. Retrieved from https://www.wired.com/2017/04/tim-berners-lee-inventor-web-plots-radical-overhaul-creation/
Don Tapscott. (2016, September 16). How the blockchain is changing money and business. Retrieved from https://www.youtube.com/watch?v=Pl8OlkkwRpc
Bettina Warburg. (2016, December 8). How the blockchain will radically transform the economy. Retrieved from https://www.youtube.com/watch?v=RplnSVTzvnU
Satoshi Nakamoto. (2008, October 31). Bitcoin: A Peer-to-Peer Electronic Cash System. Retrieved from https://bitcoin.org/bitcoin.pdf
Nick Szabo. (2015, November 13). History of Blockchain. Retrieved from https://www.youtube.com/watch?v=7Y3fWXA6d5k
Andrew Keys. (2015, August 26). Here’s the Epoch of Blockchain. Retrieved from https://media.consensys.net/it-was-the-best-of-times-it-was-the-worst-of-times-3fc8c0865c6c
Cameron McLain. (2017, July 8). A Brief History of Blockchain: An Investor’s Perspective. Retrieved from https://medium.com/hummingbird-ventures/a-brief-history-of-blockchain-an-investors-perspective-387c440ad11c
Ethash. (2017, August 3). Retrieved from https://github.com/ethereum/wiki/wiki/Ethash
Block #5000171. (2018, January 30). Retrieved from https://etherscan.io/block/5000171
Yunyun Chen. (2016, June 1). Guide: An Introduction to Encryption. https://media.consensys.net/guide-an-introduction-to-encryption-9afd17f5da6d
Yunyun Chen. (2016, June 3). Guide: Hashing. https://media.consensys.net/guide-hashing-33dc0467c126
Collin Thompson. (2016, October 2). How does the Blockchain Work?. Retrieved from https://medium.com/blockchain-review/how-does-the-blockchain-work-for-dummies-explained-simply-9f94d386e093
Sean Au. (2016, November 29). If you understand Hash Functions, you’ll understand Blockchains. Retrieved from https://decentralize.today/if-you-understand-hash-functions-youll-understand-blockchains-9088307b745d
Tess Rinearson. (2017, July 21). Making Money Trustworthy. Retrieved from https://medium.com/@tessr/making-money-trustworthy-6c552a1cfc25
Aleksandr Bulkin. (2016, May 3). Explaining blockchain - how proof of work enables trustless consensus. Retrieved from https://keepingstock.net/explaining-blockchain-how-proof-of-work-enables-trustless-consensus-2abed27f0845
Vitalik Buterin. (2017, August 7). On Public and Private Blockchains. Retrieved from https://blog.ethereum.org/2015/08/07/on-public-and-private-blockchains/
R. Tyler Smith. (2017, February 28). Public and Private Blockchains: Enemies or Allies? Why the Enterprise Ethereum Alliance will prove the latter. Retrieved from https://medium.com/@rtylersmith/public-and-private-blockchains-enemies-or-allies-45f050c38fc0
Collin Thompson. (2016, October 4). Private Blockchain or Database? . Retrieved from https://medium.com/the-intrepid-review/private-blockchain-or-database-whats-the-difference-523e7d42edc
Matt Chwierut. (2016, July 21). Asking Permission: What’s the difference between a public and private blockchain?. Retrieved from https://www.smithandcrown.com/permission-blockchains/
Paul Kohlhaas. (2017, February 7). An Introduction to Polkadot and Parachains. Retrieved from https://keepingstock.net/a-dummies-guide-to-polkadot-and-parachains-93708bd90775
Joseph Chow, Simon de La Rouviere. (2015, December 9). Taking Stock: Bitcoin and Ethereum. Retrieved from https://medium.com/@ConsenSys/taking-stock-bitcoin-and-ethereum-4382f0a2f17
Jae Kwon, Ethan Buchman. (1899, December 30). Cosmos: A Network of Distrubted Ledgers. Retrieved from https://cosmos.network/dev/whitepaper
Daniel Finley. (2017, February 16). Dan’s Intro to How Ethereum Works. Retrieved from https://www.youtube.com/watch?v=-SMliFtoPn8
Daniel Oberhaus, Jordan Pearson. (2017, June 16).  Retrieved from https://motherboard.vice.com/en_us/article/newkqz/okay-wtf-is-ethereum
What is Ethereum?. Retrieved from http://www.ethdocs.org/en/latest/introduction/what-is-ethereum.html
Karl Floersch. (2016, December 8). Introduction to Ethereum: The Internet’s Government. Retrieved from https://karl.tech/intro-to-ethereum/
Fred Ehrsam. (2016, May 24). Ethereum is the Forefront of Digital Currency. Retrieved from https://blog.coinbase.com/ethereum-is-the-forefront-of-digital-currency-5300298f6c75
William Mougayar. (2015, May 24). The Business Imperative Behind the Ethereum Vision. Retrieved from https://blog.ethereum.org/2015/05/24/the-business-imperative-behind-the-ethereum-vision/
Vitalik Buterin. (2017, July 6). IMO the most valid criticisms of Ethereum as it currently stands are. Retrieved from https://www.reddit.com/r/ethtrader/comments/6lgf0l/vitalik_drops_the_mic_on_rbtc/dju1y8q/
Vitalik Buterin. (2018, January 2). Ethereum scalability research and development subsidy programs. Retrieved from https://blog.ethereum.org/2018/01/02/ethereum-scalability-research-development-subsidy-programs/
The Beam. (2017, December 7). The energy consumption of the crypto world. Retrieved from https://medium.com/thebeammagazine/the-energy-consumption-of-the-crypto-world-b20e3628e0d2
Giulio Prisco. (2017, November 29). The Ethereum Killer Is Ethereum 2.0: Vitalik Buterin’s Roadmap. Retrieved from https://bitcoinmagazine.com/articles/ethereum-killer-ethereum-20-vitalik-buterins-roadmap/
Vitalik Buterin. (2016, January 15). Privacy on the Blockchain. Retrieved from https://blog.ethereum.org/2016/01/15/privacy-on-the-blockchain/
OkayOKay. (2017, May 29). I accidently lost the key to my wallet. Retrieved from https://ethereum.stackexchange.com/questions/16785/i-acccidently-lost-the-key-to-my-wallet
Alex Hern. (2017, November 8). $300m in cryptocurrency’ accidentally lost forever due to bug. Retrieved from https://www.theguardian.com/technology/2017/nov/08/cryptocurrency-300m-dollars-stolen-bug-ether
Fred Ehrsam. (2017, June 27). Scaling Ethereum to Billions of Users. Retrieved from https://medium.com/@FEhrsam/scaling-ethereum-to-billions-of-users-f37d9f487db1
Anthony Lewis. (2017, March 7). Three common misconceptions about smart contracts. Retrieved from https://bitsonblocks.net/2017/03/07/three-common-misconceptions-about-smart-contracts/
William Mougayar. (2016, March 23). 9 Myths Surrounding Blockchain Smart Contracts. Retrieved from https://www.coindesk.com/smart-contract-myths-blockchain/
Alyssa Jarrett. (2016, September 9). Busting Myths around Blockchains . Retrieved from https://ripple.com/insights/busting-myths-around-blockchains/
Simon de La Rouviere, Ashley Taylor. (2015, December 2). A Token-Powered Future on Ethereum. Retrieved from https://medium.com/@ConsenSys/tokens-on-ethereum-e9e61dac9b4e
John Lilic. (2015, November 16). Ethereum Enabled Community Energy Market Sharing Economy Phase 2; Here’s How ConsenSys is Building The TransActive Grid. Retrieved from https://www.linkedin.com/pulse/ethereum-enabled-community-energy-market-sharing-economy-john-lilic-6071756565017305088?trk=pulse_spock-articles
Simon de La Rouviere. (2015, December 1). DEVCON1: Tokens - Simon de la Rouviere. Retrieved from https://www.youtube.com/watch?v=kE5oGw8oKsY
Fabian Vogelsteller & Vitalik Buterin. (2015, November 19). ERC-20 Token Standard. Retrieved from https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20.md
A Securities Law Framework for Blockchain Tokens. (2016, December 7). Retrieved from https://www.coinbase.com/legal/securities-law-framework.pdf
Nick Tomaino. (2017, March 14). The Token Economy. Retrieved from https://thecontrol.co/the-token-economy-81becd26b9de
Chris Dixon. (2017, June 1). Crypto Tokens: A Breakthrough in Open Network Design. Retrieved from https://medium.com/@cdixon/crypto-tokens-a-breakthrough-in-open-network-design-e600975be2ef
Balaji Srinivasan. (2017, May 27). Thoughts on Tokens. Retrieved from https://news.21.co/thoughts-on-tokens-436109aabcbe
Fred Ehrsam. (2017, August 1). Blockchain Tokens and the dawn of the Decentralized Business Model. Retrieved from https://blog.coinbase.com/app-coins-and-the-dawn-of-the-decentralized-business-model-8b8c951e734f
Fred Ehrsam. (2016, November 2). How to Raise Money on a Blockchain with a Token. Retrieved from https://blog.gdax.com/how-to-raise-money-on-a-blockchain-with-a-token-510562c9cdfa
Vitalik Buterin. (2017, June 9). Analyzing Token Sale Models. Retrieved from http://vitalik.ca/general/2017/06/09/sales.html
Steven McKie. (2017, June 14). Understanding the Ethereum ICO Token Hype. Retrieved from https://medium.com/blockchannel/understanding-the-ethereum-ico-token-hype-429481278f45
Will Warren. (2017, February 2). The Difference between App Coins and Protocol Tokens. Retrieved from https://medium.com/0x-project/the-difference-between-app-coins-and-protocol-tokens-7281a428348c
Token Summit I - State of Tokens with Erik Voorhees, ShapeShift CEO. (2017, June 3). Retrieved from https://www.youtube.com/watch?v=0dl6ahjoBm8
Dr. Christian Lundkvist, Andrew Keys. (2015, November 25). The Identity Crisis. Retrieved from https://medium.com/@ConsenSys/identity-is-defined-in-merriam-s-dictionary-as-who-someone-is-a3d6a69f5fa4
Michael Mainelli. (2017, March 16). Blockchain Will Help Us Prove Our Identities in a Digital World. Retrieved from https://hbr.org/2017/03/blockchain-will-help-us-prove-our-identities-in-a-digital-world
Albert Wenger. (2014, March 10). Decentralizing Identity. Retrieved from http://continuations.com/post/79187457919/decentralizing-identity
Anthony Lewis. (2017, May 17). A Gentle Introduction to Self Sovereign Identity. Retrieved from https://bitsonblocks.net/2017/05/17/a-gentle-introduction-to-self-sovereign-identity/
Noah Thorp, Harlan Wood. (2017, May 16). How Decentralized Reputation Can Help People Thrive. Retrieved from https://media.comakery.com/accessing-opportunity-with-portable-reputation-ae7112e64e97
Nick Tomaino. (2017, February 28). The Governance of Blockchains. Retrieved from https://thecontrol.co/the-governance-of-blockchains-5ba17a4f5da6
Token Summit I - Blockchain Governance (featuring Z Wilcox, D Zakrisson, L Xie, J Zawistowiski). (2017, June 3). Retrieved from https://www.youtube.com/watch?v=JNSYYJj03Q8
Patrick Murck. (2017, April 19). Who Controls the Blockchain?. Retrieved from https://hbr.org/2017/04/who-controls-the-blockchain
Vlad Zamfir. (2017, June 1). Some Thoughts on Blockchain Governance. Retrieved from https://medium.com/@Vlad_Zamfir/some-thoughts-on-blockchain-governance-4b88e63d4e64
Ralph C. Merkle. (2016, May 31). DAOs, Democracy and Governance. Retrieved from http://merkle.com/papers/DAOdemocracyDraft.pdf
Dominik Schiener. (2015, October 28). PublicVotes: Ethereum-based Voting Application. Retrieved from https://medium.com/@DomSchiener/publicvotes-ethereum-based-voting-application-3b691488b926
Nick Tomaino. (2013, June 4). Cryptoeconomics 101. Retrieved from https://thecontrol.co/cryptoeconomics-101-e5c883e9a8ff
Kyle Wang. (2017, July 21). Cryptoeconomics: Paving the Future of Blockchain Technology. Retrieved from https://hackernoon.com/cryptoeconomics-paving-the-future-of-blockchain-technology-13b04dab971
Vitalik Buterin. Introduction to Cryptoeconomics. Retrieved from https://edcon.io/ppt/one/Vitalik Buterin_Introduction to Cryptoeconomics_EDCON.pdf
ConsenSys. (2016, June 30). Decentralized Storage: The Backbone of the Third Web. Retrieved from https://media.consensys.net/decentralized-storage-the-backbone-of-the-third-web-d4bc54e79700
Dr. Christian Lundkvist, John Lilic. (2016, February 17). An Introduction to IPFS. Retrieved from https://medium.com/@ConsenSys/an-introduction-to-ipfs-9bba4860abd0
Viktor Trón, Aron Fischer, Dániel A. Nagy, Zsolt Felföldi, Nick Johnson. (2016, May). swap, swear and swindle:incentive system for swarm. http://swarm-gateways.net/bzz:/theswarm.eth/ethersphere/orange-papers/1/sw^3.pdf
Juniper Research. (2016, May 12). Cybercrime Will Cost Businesses Over $2 Trillion by 2019. http://www.juniperresearch.com/press/press-releases/cybercrime-cost-businesses-over-2trillion
Yunyun Chen. (2016, June 1). Guide: An Introduction to Encryption. https://media.consensys.net/guide-an-introduction-to-encryption-9afd17f5da6d
Yunyun Chen. (2016, June 3). Guide: Hashing. https://media.consensys.net/guide-hashing-33dc0467c126
Juan Benet. (2015, February 20). IPFS Alpha Demo. https://www.youtube.com/watch?v=8CMxDNuuAiQ
Protocol Labs. (2014, August 14). Filecoin: A Decentralized Storage Network. https://filecoin.io/filecoin.pdf
What is Storj?. (2016, September 28). Retrieved from https://medium.com/@storjproject/what-is-storj-part-1-of-3-the-storj-network-90fb1300112f
Max Kaplan. (2017, June 25). Sia: Blockchain’s Brightest Star. Retrieved from https://hackernoon.com/sia-blockchains-brightest-star-ab584992391
Simon de La Rouviere. (2015, December 16). Why & How Decentralized Prediction Markets Will Change Just About Everything. Retrieved from https://medium.com/@ConsenSys/why-how-decentralized-prediction-markets-will-change-just-about-everything-15ff02c98f7c
Matt Liston. (2016, May 4). Markets for the Future. Retrieved from https://medium.com/@ConsenSys/markets-for-the-future-c73fa73fe35d
Unclouded Vision.(2015, September 26). The Economist. Retrieved from https://www.economist.com/news/books-and-arts/21666098-forecasting-talent-luckily-it-can-be-learned-unclouded-vision
Cade Metz. (2017, March 22). Forget Bitcoin. The Blockchain Could Reveal What’s True Today and Tomorrow. Retrieved from https://www.wired.com/2017/03/forget-bitcoin-blockchain-reveal-whats-true-today-tomorrow/
Vitalik Buterin. (2014, August 21). Introduction to Futarchy. Retrieved from https://blog.ethereum.org/2014/08/21/introduction-futarchy/
Introducing AirSwap. (2017, May 10). Retrieved from https://media.consensys.net/introducing-swap-a-protocol-for-decentralized-peer-to-peer-trading-on-the-ethereum-blockchain-d4058f3179cf
Introducing Omega One. (2017, June 8). Retrieved from https://media.consensys.net/introducing-omega-one-a-cheaper-and-safer-way-to-trade-cryptocurrencies-and-tokens-b59b9ccf29c4
Linda Xie. (2017, July 3). A beginner’s guide to 0x. Retrieved from https://blog.0xproject.com/a-beginners-guide-to-0x-81d30298a5e0
Hadrien Charlanes. (2017, February 16). StabL Bringing Stable Tokens and Derivative Products to the Ethereum Blockchain. Retrieved from https://blog.variabl.io/stabl-bringing-stable-tokens-and-derivative-products-to-the-ethereum-blockchain-df4d5eba89d9
Nick Tomaino. (2017, April 3). Stablecoins: A Holy Grail in Digital Currency. Retrieved from https://thecontrol.co/stablecoins-a-holy-grail-in-digital-currency-b64f3371e111
Vitalik Buterin. (2014, November 11). The Search for a Stable Cryptocurrency. Retrieved from https://blog.ethereum.org/2014/11/11/search-stable-cryptocurrency/
Robert Sams. (2015, April 28). A Note on Cryptocurrency Stabilisation: Seigniorage Shares. Retrieved from https://github.com/rmsams/stablecoins/blob/master/paper.pdf
Rune Christensen, Nikolai Mushegian, Daniel Brockman, Kenny Rowe, Andy Milenius, Ryan Zurrer. (2017, October 17). The Dai Stablecoin System. Retrieved from https://github.com/makerdao/docs/blob/master/Dai.md
Rune4444. (2015, December 8). A list of stablecoin systems. Retrieved from https://www.reddit.com/r/Stablit/comments/3vzt82/list_of_stablecoin_systems/


Plugin Information |
|---|
View reFit on the plugin site for more information. |
A plugin for publishing Fit test reports created by reFit, an implementation of the Framework for Integrated Test (Fit).
Overview
The reFit plugin collects and archives the test output and summaries created by a Fit test suite. The reports of the latest build are published under http://JENKINS/jobs/YOURJOB/refit/. An icon on the job status page links to this URL:
Click on this icon to see the reFit test report, containing links to the individual test results:
FAQ
What is Fit and reFit?
See the reFit Wiki.
How does the reFit plugin relate to the Fit plugin?
- The Fit plugin was never released, the reFit plugin will available via Jenkins' update centre soon.
- The Fit plugin is based on the original Fit implementation. The reFit plugin is based on reFit, a recent alternative implementation of Fit.
How does the reFit plugin relate to the Fitnesse plugin?
It doesn't. Fitnesse is incompatible with Fit. It is one of the driving forces of reFit to go back to the Fit roots and to create an up-to-date and maintained version of Fit, without any of the incompatible extensions introduced in Fitnesse.
How can I run Fit tests in a Jenkins project?
If your project is based on Maven, just use the refit-maven-plugin. Otherwise, you can wrap your Fit tests in a JUnit suite or run reFit programmatically, e.g. from an Ant script. See Running Fit Tests for details.
Can I use the fit-maven-plugin or other old-school Fit runners instead?
No, the reFit plugin parses an XML report produced by reFit. This is an added feature of reFit. If you have an existing Fit suite, it should also run under reFit. You need reFit 1.7.0 or higher to produce XML reports.
Does the reFit plugin include reFit?
No, and it has no compile-time or run-time dependencies on reFit either. The Jenkins reFit plugin only works with the files generated by reFit. For this reason, the reFit plugin can be released under the MIT license used by Jenkins, whereas reFit is released under GPL, being a derived work from the original Fit framework which is also released under GPL.
Change History
Version 0.3 (5 Apr 2011)
- Reports get archived per build. Before, only the reports from the last build were archived for the project.
- There is a trend graph for the Fit test results.
Version 0.2 (28 Mar 2011)
- Initial public release.
- Archives Fit reports and publishes them via a link on the project page.
- Usable both for Maven and Freestyle builds, but the plugin does not automatically extract configuration info from the Maven POM.
- No aggregation for multi-module Maven builds. You can only publish the reports from one subproject.
- The plugin only archives the results of the last successful build.


(Route : Settings Menu, Communications Command, New Button)
The Run A Script dialog box allows you to specify a script to be run once a connection has been established using the connection card.
This is a Hot Spot image. Move your mouse pointer over the image
and when the mouse pointer changes to the shape of a hand click
the left mouse button once for extra help.
To run a script, choose the Yes, run the script option and use the browse button to choose the script that you wish to run.


|
| cloneVmName | xsd:string | Name for the new VM resource. |
| customizationScript | xsd:string | An optional customization script to be executed after the clone is finished. |
| datastoreName | xsd:string | Datastore name of the destination datastore, where the newly cloned VM to be created. |
| folderMoref | xsd:string | If specified, the folderMoref identifies the the same folder (for the cloned VM) as that of the source VM.
Otherwise, the new VM is placed in the default folder of the datacenter. |
| hostClusterMoref | xsd:string | VMWare ID for the destination virtual node (Host, Resource Pool, Cluster, Folder, etc).
Optional field for clone from VM/Snapshot to the local datastore. |
| vCenterName | xsd:string | Hostname of the destination vCenter, where the newly cloned VM to be created.
The vcenter host name must be a 'COMPUTE' resource which can be verified by using the
output from the
. |


Deleting an Event or Event Series
How to permanently delete an event from the Events module. Note: Module and Page Editors may only be able to delete their own events. This depends on the moderation settings configured by a Page Editor on the Settings page of this module.
- Go to the event details page of the required event. See "Viewing Event Details (List View)", See "Viewing Event Details (Month View)" or See "Viewing Event Details (Week View)"
- Select from these options:
- Click the Delete link to delete a onetime event or this instance of a recurring event. This displays the message "Are you sure you wish to Delete this entry?"
- Click the OK button to confirm.
- Click the Delete Series link to delete all instances of this recurring event.
- Click the OK button to confirm.


Dashboard
Deposits
Transfer
Settings
Support
Notifications
Transfer Funds
Who would you like to transfer
funds to?
or you select one of your frequent transfer receipts
Ogbuji Bright
━ 1500205
Adegoke David Afolabi
━ 1500205
Ogunfemi Micheal
━ 1400790
Next
How much do you want to
Wolemajekodumi Emeka Yakubu?
₦ 1000
₦ 2000
₦ 3000
₦ 5000
or enter a custom amount
Previous
Proceed
Transfer Summary
Wolemajekodumi Emeka Yakubu
Name
Reg number
2300070
Transfer Amount
NGN 7,500.00
Transaction fees
+0.79%
Total
NGN 7,556.25
Transfer


Your search query is listed below. Most relevant links are listed first . To improve searching, use mulitple keywords and be specific about the search query.
Use the Search form to find keywords in the @Mail documentation. Enter your search terms below and click the 'Search' button. Refine your search by specfying additional keywords an specific on the search query


Ocala events
-
viagra find online pages edinburgh free
History of zero? - Mathematics
Jun 3, 2011 . As a number in itself, for example in calculations like 5 - 3 - 2 = 0 . The Nothing That Is: A Natural History of Zero, written by Robert Kaplan, .
http://math.stackexchange.com/questions/42970/history-of-zeroZero - MacTutor History of Mathematics
The historical record, however, shows quite a different path towards the concept. Zero . The second use of zero is as a number itself in the form we use it as 0.
http://www-history.mcs.st-and.ac.uk/HistTopics/Zero.html
list all minnesota cities Upcoming events in Ocala
- Sponsored event
omaha hotel jacuzzi suite
Apr 6 - Dance It Studio
motorcycleing in myrtle beach california classics california millworks valencia
- Sponsored event
warehouse auto parts redding ca
Apr 6 - Downtown Disney
smoked salmon pasta with alfredo sauce sleeping men fondled by girls
fowler glass tampa fl Hottest Tickets
-
Apr 11fifa 08 in canada
Amway Center -
Apr 28spunky angels melanie peachyforum
Amway Center -
Jun 25bag of water flys
Bob Carr Performing Arts Center -
Mar 30kansas guidelines for marital dissolution
Amway Center -
Aug 27download festival castle donnington
Amway Center -
Jun 21mattress firm columbus ohio
Amway Center -
Sep 13archives washington historical society
Francis Field -
Mar 171603 north nimitz highway honolulu
St Augustine Amphitheatre -
Oct 8make multiple drives look like 1
Amway Center -
May 4royal omni new orleans
Bob Carr Performing Arts Center
Ocala's best venues
-
The importance of zero in mathematics - by Tim Peters - Helium
Jul 9, 2008 . The number zero (represented by the digit 0) serves double-duty as a placeholder and . The history of zero dates back long before Fibonacci.
http://www.helium.com/items/1106587-history-and-importance-of-zero -
Number - Wikipedia, the free encyclopedia
Traditionally, the sequence of natural numbers started with 1 (0 was not even considered a . The negative of a positive integer is defined as a number that produces zero when it is added to the . See also: History of writing ancient numbers .
http://en.wikipedia.org/wiki/Number -
Zero in Four Dimensions - University of Baltimore Home Page web ...
It is all about the number zero, its place in the history, philosophy, and world . This visitor seems to suggest that since both 2/0 and Â¥ are meaningless to use, .
http://home.ubalt.edu/ntsbarsh/zero/zero.htm3 blade rc props
98 people's favorite
-
Importance of zero
Apr 6, 2012 . Zero 266 views · Zero 496 views · History numbers 112 views · Story of . Zero Is A Special Number? If we add 0 to any number, the sum is the .
http://www.slideshare.net/malinibindra/importance-of-zero -
The Number Zero - Suite101
Feb 15, 2008 . As far as numbers go, zero has throughout history caused mathematicians no end of grief and discomfort, yet it remains a...
http://suite101.com/article/the-number-zero-a44688


#assign n0_docs="active"> <#assign n1_features="active"> <#assign n2_encryption="active">
Ebean has support for transparent Encryption/Decryption of specific properties.
We make mark the properties we want encrypted with @Encrypted
and these properties will be automatically encrypted and decrypted as needed.
Encryption/decryption can occur either on the client/application side or by
the database. When we use database encryption then we can use these properties
in queries as part of the where
and order by
clause.
Effectively the encryption of the property is fully transparent to the application.
When we use client/application side encryption/decryption then we should only use the
EQ (equal to) operator in the where
clause.
When using client/application encryption the properties are encrypted/decrypted by
a Java function - an implementation of the io.ebean.config.Encryptor
interface.
The default implementation uses AES 128 bit based implementation and we can also configure
Ebean to use another implementation.
Properties encrypted with client/application encryption should ONLY be used with EQ (equal to) operator
in where
clauses - other operators should not be used with client side encrypted properties.
package io.ebean.config; /** * Used for Java side encryption of properties when DB encryption is not used. * * By default this is used on non-varchar types such as Blobs. */ public interface Encryptor { /** * Encrypt the data using the key. */ byte[] encrypt(byte[] data, EncryptKey key); /** * Decrypt the data using the key. */ byte[] decrypt(byte[] data, EncryptKey key); /** * Encrypt the formatted string value using a key. */ byte[] encryptString(String formattedValue, EncryptKey key); /** * Decrypt the data returning a formatted string value using a key. */ String decryptString(byte[] data, EncryptKey key); }
When using Database side encryption/decryption we use database stored procedures to encrypt and decrypt
the properties. For example with Postgres Ebean uses pgp_sym_encrypt()
and
pgp_sym_decrypt()
.
The default DB encryption decryption functions used for each platform are:
The following are the types supported by database encryption. Any type not supported by database encryption will use client/application encryption.
Important: The following types are currently not supported:
Whenever a property is encrypted or decrypted a "Key" must be used. Ebean will internally ask the EncryptKeyManager for a key given the table and column name.
We must supply an implementation of the EncryptKeyManager.
package io.ebean.config; /** * Determine keys used for encryption and decryption. */ @FunctionalInterface public interface EncryptKeyManager { /** * Initialise the EncryptKeyManager. * * This gives the EncryptKeyManager the opportunity to get keys etc. */ default void initialise() {} /** * Return the key used to encrypt and decrypt a property mapping to the given * table and column. */ EncryptKey getEncryptKey(String tableName, String columnName); }
Mark a property to be encrypted with the @Encrypted
annotation.
By default the property will be dbEncryption = true
and we
explicitly set that false for client/application side encryption.
// use database side encryption @Encrypted String name; // use client side encryption (not db functions) @Encrypted(dbEncryption=false) String description;
// Use @Encrypted annotation to mark the encrypted properties @Entity @Table(name="patient") public class Patient { @Id long id; // database side encryption @Encrypted String name; // client side encryption @Lob @Encrypted(dbEncryption=false) String description; @Encrypted LocalDate dob; ...
List<|Patient> list = new QPatient() .name.eq("Rob") .findList();
Results in the following Postgres SQL:
select t0.id, pgp_sym_decrypt(t0.name,?) from patient t0 where pgp_sym_decrypt(t0.name,?) = ?
Specify the EncryptKeyManager implementation in the ebean.properties file like below:
ebean.encryptKeyManager=org.example.BasicEncyptKeyManager
Programmatically configure using DatabaseConfig.
DatabaseConfig config = DatabaseConfig(); ... EncryptKeyManager keyManager = ...; config.setEncryptKeyManager(keyManager); ... Database database = DatabaseFactory.create(config);
An example EncryptKeyManager is:
package org.example.encrypt; import io.ebean.config.EncryptKey; import io.ebean.config.EncryptKeyManager; public class BasicEncyptKeyManager implements EncryptKeyManager { public void initialise() { // can load keys or initialise source resources ... } public EncryptKey getEncryptKey(String tableName, String columnName) { // get the key for the given table and column String keyValue = ...; return new BasicEncryptKey(keyValue); } }
Ebean is detecting when an encrypted property is being used. It will call the EncryptKeyManager with the table and column of the property to get the encryption key. This key is then added as a bind variable to the prepared statement.
As the key is added as a bind variable into the statement we can not use encryption with 'positioned' parameters because it can effectively change the position of other parameters. We can use named parameters or the criteria api for building queries but, we can't use positioned (1,2,3,4..) parameters.


ggtitle |
Add title to the plot. fun ggtitle(title: String): OptionsMap |
labs |
Change plot title, axis labels and legend titles. fun labs(title: String? = null, x: String? = null, y: String? = null, alpha: String? = null, color: String? = null, fill: String? = null, shape: String? = null, size: String? = null, width: String? = null, height: String? = null, linetype: String? = null): FeatureList |
xlab |
Add label to the x axis fun xlab(label: String): Feature
|
ylab |
Add label to the y axis fun ylab(label: String): Feature
|


Register
First Name:
Last Name:
Male
Female
Other
Email:
Password:
Birthday:
Month
Jan
Feb
Mar
Day
1
2
3
Year
1991
1990
1989
I agree to the terms and conditions
Submit


About the Park
This is not a puzzle.
Founded in 1992, Penny Park has delighted countless visitors for almost three decades. Whether you're a thrill-seeking kid or simply young at heart, at Penny Park we guarantee you'll have a glorious day!
A highlight of everyone’s day is the celebratory opening of Penny Park. Here is a promotional video from 1993 showing this magical moment.
Judy Miller
Founder of Penny Park
A long-time lover of theme parks, Judy designed and built this magical place in 1992, naming it after her granddaughter Penny.
Penny Miller
Owner & Manager of Penny Park
For the last several years, Penny has run the show at the park. She is thrilled to be continuing the family tradition of bringing joy and wonder to people of all ages!
The Loonie Toonies
A Penny Park tradition, the Loonie Toonies are the lovable mascots of the park and can often be seen strolling around the grounds. If you see one, feel free to say hi!
King Jeon & Queen Paisa
Kobo the Big Bad Wolf
Centime the Flapper
Kopek the Clown
Luma the Astronaut
Dirham the Wizard
Park History
Our historians have recently discovered (and are in the process of digitizing) old videos showing the history of Penny Park and its owners. Be on the lookout for more updates as we continue this process!


Following on last week's discussion of Stereotype Threat, this week we were asked to consider our own values, and how they might help us combat it. From a list of about 100, I narrowed my most cherished down to: Adventure, Compassion, Courage, Effectiveness, Efficiency, Fairness, Freedom, Integrity, Loyalty, Responsibility, and Truth. Though not on the list of options, I would also add Empathy and Reason to the mix. Together, these words capture the essence of what drives me and motivates me as a person. They explain most of the decisions I make, big and small. I feel them in my thoughts, and try to live up to them in my words and in my actions.
For purposes of this post, I'm just going to explore two in detail: Courage and Empathy. These are two of the most foundational values to me, in that some of the others emanate from those in certain respects.
From Courage, I find the motivation to confront fears and face new challenges. I remind myself that most things worth having do not come easily -- they take hard work and usually involve risk. Just as it takes courage to stand up for things you believe in, it takes courage to make big changes in your own life, as they will always require work and involve risk. Comfort and complacency are the vices that threaten courage -- when those things are in abundance, I find it harder to motivate myself to grow in new ways. It's critical to find courage in those moments. Courage also underpins other values like Responsibility, because it takes courage to hold yourself accountable and admit the many things for which (and to whom) we are responsible. Not surprisingly, it is also difficult to find Adventure without first finding Courage.
From Empathy, I find the guide that informs my interactions and supports my connection with other living creatures. Empathy is the value on which principles like "Do unto others as you would have them do unto you" are built. I believe concepts of Justice and Morality would be largely vacant without empathy. Similarly for my values of Freedom, Compassion and Loyalty. Empathy is the value that reminds me to ask myself questions about others -- where are they coming from, what have their life experiences been, what is their context, what are their values? It also reminds me to put myself in others' shoes before passing judgment on them. And it extends to animals as well, as far as I'm concerned. I find great empathy with other living creatures, which in practical terms impacts my eating, buying, and giving behavior.
Of course these values often influence the advice I give others as well. Just days ago I discussed with a friend the pros and cons of him leaving his current job to pursue something more entrepreneurial, and the concept of courage was front and center. Similarly, in discussing year-end charitable giving with my family, I found myself promoting animal rights causes and programs to improve human quality of life in developing countries, because I feel great empathy with those afflicted humans and animals.
I expect these values to play an important part in my time at DBC, as they do in most parts of my life. In combatting Stereotype Threat specifically, I'll seek the courage to keep pushing when things feel overwhelming, and the empathy to remind myself that we are all fighting our own personal struggles, and feeling sorry for myself or trying to benchmark myself against others is a road to nowhere.


Need sync?
Create collaborative offline-first apps
Easy to get started
Coming soon: Dexie CloudBETA »


<glossentry>
The <glossentry> element defines a single sense of a glossary term. Glossary entries for different term senses can be reused independently of one another.
Category: Glossentry elements


Contact Information
If you have any queries about any of the products we provide on our website, please feel free to get in touch via email, post or telephone which you can find listed below!
To contact us via Email:
Email =<EMAIL_ADDRESS>At the moment, with Covid-19, our telephone lines are currently understaffed so please be aware that your call may not be answered immediately but we will get back to you as soon as possible!
Our telephone number is: 097-123456
If you wish to write us a letter, please send it to the address below:
Football Shirts Ireland,
Drundrum Shopping Centre,
Sandyford Rd,
Dublin 14
Co. Dublin
D14 A3C9
We look forward to hearing from you!
Return to Home


The sizes of the images are sufficient to keep them detailed enough on common size mobile devices.
Common size mobile device has a size of 6.39 inches, with screen resolution 1080 x 2340 pixels and 19.5:9 aspect ration.
It's possible to make them with higher or lower resolution too, but the aspect ratio of the image should not be changed.


Currently a 3rd year undergrad student at MACE Kothamangalam. I'm pursuing B.Tech in CSE.
I've been passionate about developing software in a way that it helps a lot of people.
I love coding👨💻, listening to music🎶🎧, playing football/soccer⚽, solving patterns🔢.
I love sci-fi movies or series. I've been
recently a lot into Dramas like Sweet Combat.
These are my main skills. Check out my linkedin profile to see more skills.
A data structure is like a container to hold a data, which container to chose depends on data
(same as in real life -> milk can is used for storing liquids not to hold sugar).
An algorithm is like a recipe,
but the fastest, easy to implement recipe/ algorithm/ path is prefered.
A mobile app is a software application designed to run on a mobile device such as a phone, tablet, or watch. Mobile app development is the act or process by which a mobile app is developed for mobile devices, such as personal digital assistants, enterprise
digital assistants or mobile phones.
This website/webpage has been develeoped using bootstrap. Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web development. It contains CSS- and JavaScript-based design templates for forms, buttons, navigation, etc.
Google Cloud Platform is a suite of cloud computing services that runs on the same infrastructure that Google uses internally for its end-user products, such as Google Search, Gmail, YouTube, etc. GCP's Core service categories include Compute, Networking, Storage and Databases, AI / ML, Big Data, etc.
The places where I made some good friends and had the previlege to be taught by some of the best and helpful teachers.
I spent 12 wonderful years from 2004-2016 while studying here. I won many things here and made beautiful memories.
Even though I could spend only 2 years (2016-2018) here, those 2 years were awesome. I saw extremely talented students here.
I'm currently studying B.Tech in CSE here. I joined MACE in 2018 and will complete my undergraduation in 2022.


#primary_key_type (private)
[ GitHub ]# File 'activerecord/lib/rails/generators/active_record/migration.rb', line 20
def primary_key_type key_type = [:primary_key_type] ", id: :#{key_type}" if key_type end
123456789_123456789_123456789_123456789_123456789_
| Relationships & Source Files | |
| Namespace Children | |
|
Modules:
| |
| Extension / Inclusion / Inheritance Descendants | |
|
Included In:
| |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
::ActiveSupport::Concern
|
|
|
Instance Chain:
|
|
| Defined in: | activerecord/lib/rails/generators/active_record/migration.rb |
::ActiveSupport::Concern
- Extended| class_methods | Define class methods from given block. |
| included | Evaluate given block in context of base class, so that you can write class macros here. |
| prepended | Evaluate given block in context of base class, so that you can write class macros here. |
| append_features, prepend_features |
::Rails::Generators::Migration
- Included::Rails::Generators::Migration
- Included| #create_migration, | |
| #migration_template | Creates a migration template at the given destination. |
| #set_migration_assigns! |
# File 'activerecord/lib/rails/generators/active_record/migration.rb', line 42
def configured_migrate_path return unless database = [:database] config = ActiveRecord::Base.configurations.configs_for( env_name: Rails.env, name: database ) config&.migrations_paths end
# File 'activerecord/lib/rails/generators/active_record/migration.rb', line 30
def db_migrate_path if defined?(Rails.application) && Rails.application configured_migrate_path || default_migrate_path else "db/migrate" end end
# File 'activerecord/lib/rails/generators/active_record/migration.rb', line 38
def default_migrate_path Rails.application.config.paths["db/migrate"].to_ary.first end
# File 'activerecord/lib/rails/generators/active_record/migration.rb', line 25
def foreign_key_type key_type = [:primary_key_type] ", type: :#{key_type}" if key_type end
# File 'activerecord/lib/rails/generators/active_record/migration.rb', line 20
def primary_key_type key_type = [:primary_key_type] ", id: :#{key_type}" if key_type end


ONBOARDING WORKSPACE
The onboarding workspace is the one you will use to learn the basic operation of the platform. Superalgos can trade with all major exchanges, and your selection will not affect which exchanges you may trade with in the future.
PARTNER EXCHANGES WORKSPACES
Partner exchanges have custom workspaces and offer preferential trading fees for Superalgos users. If your favorite exchange is on the list, then go for it! If you're not a customer yet, find the referral link in the corresponding Telegram group.
FALLBACK WORKSPACE
The fallback workspace uses Binance or Binance US as the active exchange. Use this workspace if you're not interested in trading with one of the Partner Exchanges to benefit from discounted trading fees. Later on, you may switch to any other exchange.


Game
Sources
Ez az első HTML+JS programunk. Sounds used:
Title: Bomb
Uploaded: 12.04.09 | License: Attribution 3.0 | Recorded by Mike Koenig
source
license


@* * Copyright 2023 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import uk.gov.hmrc.govukfrontend.views.html.components._ @import viewModels.sections.Section @this(govukSummaryList: GovukSummaryList) @(section: Section)(html: Html = Html("")) @if(section.rows.nonEmpty) { @section.sectionTitle.map { title =>


Fallen Angels Directed by Wong Kar-wai
A film review by Chris Loar
In this beautiful, baffling follow-up to CHUNGKING EXPRESS, Wong Kar-wai has lapsed once again into near-total disregard for coherence and linearity, serving up instead something like a visual symphony. Structured more around allusion and image than character and event, ANGELS lacks the tight coherence of EXPRESS, which makes it at once astonishing and incredibly frustrating; viewers may find themselves transfixed by this vision of Hong Kong and its denizens, even as they're baffled by plotlines and elements of story that seem without purpose or direction. Not every moment of the film is compelling, but taken as a whole, Wong has once again provided a fascinating statement about memory, longing, and human relationships in the urban world.
FALLEN ANGELS borrows from CHUNGKING EXPRESS its essential structure; it tells us two stories, both centering on peculiar love affairs. The first shows us a detached gun-for-hire, Wong Chi-Ming (Leon Lai) and his partner, known only as the Agent (Michele Reis). Wong and the Agent rarely meet, communicating by beeper code and fax, but they have an intimate connection nonetheless: the Agent maintains Wong's base of operations, and takes his rubbish home with her to peruse in private. The second tale shows us the antics of one He Zhiwu (CHUNGKING EXPRESS's Takeshi Kaneshiro), a mute ex-con who makes a strange living by impersonating shopkeepers after hours and forcing passers-by to consume his goods and services. He develops a relationship of sorts with Cherry (Charlie Young), a young, possibly deranged woman recently dumped by her lover; He obviously cares for her deeply despite the fact that it's never clear that she's actually aware of his presence.
These stories, which sound like B movie fodder, are brought to luscious life by amphetamine-paced editing and cinematography that's almost too good to believe. Wong is using his usual cinematographer, Christopher Doyle (also noted for his work on the recent TEMPTRESS MOON); their work together is consistently distinctive and provocative, and FALLEN ANGELS is no exception. In fact, the filmmakers have outdone themselves; using a hand-held camera, a few wide-angle lenses, and complex, suggestive lighting, Wong and Doyle have provided us with a Hong Kong that evokes the longings and languishings of its inhabitants. And, unlike EXPRESS, which tells its two stories sequentially, ANGELS tells its tales virtually simultaneously, driving home the point that Wong always seems to be making about life in the postmodern city -- that the urban lifestyle does not destroy the cords that tie people to others and to their culture, but rather transforms them into something less recognizable -- something complex, beautiful, and tragic.
The film's visual style is so suggestive as to be almost domineering, and it would make it easy to overlooks some impressive performances by its principals. Fans of CHUNGKING EXPRESS will hardly recognize Takeshi Kaneshiro as he videotapes his father or attempts to forcibly shampoo an innocent bystander; his hair, his costume, and his demeanor bear no resemblance to those of the lonely, noble Cop 223. But the actor retains his appealing, youthful exuberance, and he brings a credible humanity to a part that threatens to collapse into caricature. Michelle Reis also deserves special mention; her stoic, detached demeanor dovetails nicely with her character's quiet, private obsessions.
FALLEN ANGELS certainly has its weak moments; Wong doesn't always seem to know the difference between the quirky and the trivial, and some of his subplots are more than a little tedious. Moviegoers who demand that their films make easy sense and tell an entertaining story will probably come away frustrated or bored, or both. But the film remains immensely valuable for its virtuoso style and its lusty embrace of urban life.
Copyright 1998 Chris Loar
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Appreciating Hubble at Hyper-speed
Appreciating Hubble at Hyper-speed is a Java-based learning aid that uses the HST Cycle 14 Treasury Project PEARS (Probing Evolution And Reionization through Spectra) data to create a three-dimensional interactive simulation of the Hubble Ultra Deep Field. With galaxies visible from redshifts z = 0.05 to z = 6.5, the data represents the deepest optical image of the Universe ever obtained, spanning nearly 90% of its history. It is precisely this depth that makes the data uniquely suited for teaching cosmology.
The simulation allows you explore the HUDF using a virtual telescope which may be moved forward, backward, and side-to-side. As you change the telescope's redshift, angular sizes of galaxies adjust properly, taking into account the expansion of the Universe. You may also view the Universe using cosmology parameter values other than the currently accepted COBE/WMAP values.
The application is provided as a stand-alone Java archive available for download, along with with a series of short exercises for instructors or interested members of the public. For help regarding the application, an online manual is available, as well as a glossary of relevant terms. More information about the Hubble Space Telescope can be found on NASA's Hubblesite.


Pecha Kucha !
A small-sized text paragraph, when there is a lot to say (but not too much because we’re not here to read a lot).
normal
big
huge
multiple
paragraphs
wrapped
together
Conclusion !
Pecha Kucha !
A small-sized text paragraph, when there is a lot to say (but not too much because we’re not here to read a lot).
normal
big
huge
multiple
paragraphs
wrapped
together
Conclusion !


|
Asylo
|
Classes | |
| class | ExecTester |
| Executes a subprocess. More... | |
Typedefs | |
| using | AeadCryptor = ::asylo::AeadCryptor |
Functions | |
| StatusOr< EnclaveAssertionAuthorityConfig > | CreateSgxIntelEcdsaQeRemoteAssertionAuthorityConfig () |
| Creates configuration for the SGX Intel ECDSA QE remote assertion authority. More... | |
| StatusOr< EnclaveAssertionAuthorityConfig > | CreateSgxIntelEcdsaQeRemoteAssertionAuthorityConfig (CertificateChain pck_certificate_chain, SgxIdentity qe_identity) |
| Creates configuration for the SGX Intel ECDSA QE remote assertion authority. More... | |
| using asylo::experimental::AeadCryptor = typedef ::asylo::AeadCryptor |
AeadCryptor
has been moved to the asylo
top-level namespace.This type alias will be removed in an up-coming release.
| StatusOr<EnclaveAssertionAuthorityConfig> asylo::experimental::CreateSgxIntelEcdsaQeRemoteAssertionAuthorityConfig | ( | ) |
Creates configuration for the SGX Intel ECDSA QE remote assertion authority.
The returned configuration contains the Intel SGX Root CA Certificate for verifying assertion root of trust. Any generated assertions will include the certification data that the Intel DCAP library locates using the Platform Quote Provider Library, as documented in https://download.01.org/intel-sgx/latest/dcap-latest/linux/docs/Intel_SGX_ECDSA_QuoteLibReference_DCAP_API.pdf
This type of EnclaveAssertionAuthorityConfig is required when using the SgxIntelEcdsaQeRemoteAssertionVerifier and/or SgxIntelEcdsaQeRemoteAssertionGenerator.
| StatusOr<EnclaveAssertionAuthorityConfig> asylo::experimental::CreateSgxIntelEcdsaQeRemoteAssertionAuthorityConfig | ( | CertificateChain | pck_certificate_chain, |
| SgxIdentity | qe_identity | ||
| ) |
Creates configuration for the SGX Intel ECDSA QE remote assertion authority.
The returned configuration contains the Intel SGX Root CA Certificate for verifying assertion root of trust. Any generated assertions will include the given pck_certificate_chain
as certification data.
This type of EnclaveAssertionAuthorityConfig is required when using the SgxIntelEcdsaQeRemoteAssertionVerifier and/or SgxIntelEcdsaQeRemoteAssertionGenerator.
| pck_certificate_chain | The certification chain to include with any generated assertions. |
| qe_identity | The Intel ECDSA QE's identity. |


todoReact
TodoList in ReactJS
Learn more about ReactJS
here
star
this TodoList's repo on Github
Made with
favorite
in
Google CodeIn
with
FOSSASIA


If you’re using AWS to host your applications then you’d probably be treading carefully when it comes to the RDS instances. AWS has introduced this nice new feature that allows you to stop an RDS instance which essentially deletes it and keeps a snapshot and just deploys that snapshot again when you want to start it, but it makes life a lot easier especially if you put that kind of function in a batch file and just run that file whenever you need to.
In this article I’ll show you how to stop your RDS instances automatically every night and start them up again in the morning using AWS CLI.
Prerequisite: You have to have already setup your AWS CLI with your account and are able to run AWS commands, follow this link to set it up
Update your CLI to the latest version by running pip install --upgrade awscli
to upgrade or just download and install the latest version
Now when you type in aws --version
in your terminal you should see something like this:
C:\Users\nick>aws --version
aws-cli/1.11.109 Python/3.4.3 Windows/8 botocore/1.5.72
As I’m writing this on the 22nd of June 2017, the latest version for windows is 1.11.109
Create a new batch file .bat and write the following script
@echo off
set rdslist=rds-instance-1 rds-instance-2
:retryaction
set /P action=Would you like to (1)start or (2)stop these instances %rdslist%:
IF %action%==1 (
set command=start
goto :start
)
IF %action%==2 (
set command=stop
goto :start
)
goto :retryaction
:start
(for %%a in (%rdslist%) do (
call aws rds %command%-db-instance --db-instance-identifier %%a
))
pause
And replace the rds-instance
& rds-instance-2
with your own instances names.
What we’re doing here is that we’re creating a list of our RDS instances and then iterating over each one and either stopping or starting them. What you should see when you run this script is the following:
Would you like to (1)start or (2)stop these instances rds-instance-1 rds-instance-2:
once you choose the action you want to take the batch file will run the start-db-instance
or stop-db-instance
command on each of your RDS instances.
You need to maintain that file and add,edit or delete RDS instances in that line 2.
If you want to schedule it from your PC or windows server you can use the Task Scheduler
Once you open it click on Create a Basic Task and give it the name “Start RDS”. Continue with the wizard and select the trigger that you’re after, for example you may want the RDS instances to start when you start the computer, when you login or automatically at a particular time every day.
Keep going until you get to this screen
Add in the path to your batch file and the argument 1
Continue through the wizard and finish the task.
Now we need to add a small modification to our script to have it accept parameters instead of prompting a question:
@echo off
set rdslist=rds-instance-1 rds-instance-2
IF %1==1 (
set command=start
)
IF %1==2 (
set command=stop
)
(for %%a in (%rdslist%) do (
aws rds %command%-db-instance --db-instance-identifier %%a
))
That's it! You now have two bash files, one that you can run manually to shut down and start instances whenever you need them and one that can run on a scheduled time or trigger
Watch this space and I’ll publish how to do that using Linux pretty soon ;)