| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/materialize.py |
16 |
12 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/max.py |
7 |
1 |
0 |
86% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/maxby.py |
8 |
2 |
0 |
75% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/merge.py |
77 |
70 |
0 |
9% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/min.py |
11 |
4 |
0 |
64% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/minby.py |
37 |
31 |
0 |
16% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/multicast.py |
13 |
7 |
0 |
46% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/never.py |
6 |
3 |
0 |
50% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/observeon.py |
8 |
4 |
0 |
50% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/of.py |
4 |
1 |
0 |
75% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/onerrorresumenext.py |
32 |
26 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/pairwise.py |
18 |
15 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/partition.py |
6 |
2 |
0 |
67% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/pluck.py |
6 |
2 |
0 |
67% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/publish.py |
10 |
4 |
0 |
60% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/publishvalue.py |
10 |
5 |
0 |
50% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/range.py |
18 |
12 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/reduce.py |
7 |
3 |
0 |
57% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/repeat.py |
17 |
8 |
0 |
53% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/replay.py |
10 |
5 |
0 |
50% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/retry.py |
6 |
1 |
0 |
83% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/returnvalue.py |
24 |
17 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/sample.py |
28 |
21 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/scan.py |
17 |
13 |
0 |
24% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/select.py |
16 |
12 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/selectmany.py |
27 |
20 |
0 |
26% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/selectswitch.py |
4 |
1 |
0 |
75% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/sequenceequal.py |
68 |
61 |
0 |
10% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/single.py |
6 |
1 |
0 |
83% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/singleordefault.py |
21 |
16 |
0 |
24% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skip.py |
15 |
11 |
0 |
27% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skiplast.py |
16 |
13 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skiplastwithtime.py |
22 |
17 |
0 |
23% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skipuntil.py |
26 |
22 |
0 |
15% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skipuntilwithtime.py |
23 |
16 |
0 |
30% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skipwhile.py |
20 |
16 |
0 |
20% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/skipwithtime.py |
19 |
13 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/slice.py |
29 |
24 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/some.py |
14 |
10 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/start.py |
5 |
1 |
0 |
80% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/startasync.py |
8 |
5 |
0 |
38% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/startswith.py |
10 |
6 |
0 |
40% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/statistics.py |
20 |
12 |
0 |
40% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/subscribeon.py |
14 |
10 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/sum.py |
7 |
3 |
0 |
57% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/switchlatest.py |
37 |
33 |
0 |
11% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/take.py |
20 |
15 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takelast.py |
16 |
13 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takelastbuffer.py |
16 |
13 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takelastwithtime.py |
24 |
19 |
0 |
21% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takeuntil.py |
12 |
7 |
0 |
42% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takeuntilwithtime.py |
18 |
11 |
0 |
39% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takewhile.py |
23 |
19 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/takewithtime.py |
14 |
8 |
0 |
43% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/thendo.py |
5 |
1 |
0 |
80% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/throttlefirst.py |
23 |
18 |
0 |
22% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/throw.py |
12 |
7 |
0 |
42% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/timeinterval.py |
17 |
11 |
0 |
35% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/timeout.py |
50 |
43 |
0 |
14% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/timeoutwithselector.py |
57 |
52 |
0 |
9% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/timer.py |
63 |
50 |
0 |
21% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/timestamp.py |
12 |
4 |
0 |
67% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/toasync.py |
20 |
14 |
0 |
30% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/toblocking.py |
5 |
1 |
0 |
80% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/todict.py |
27 |
22 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/tofuture.py |
24 |
18 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/toiterable.py |
13 |
10 |
0 |
23% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/tolist.py |
13 |
8 |
0 |
38% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/toset.py |
12 |
8 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/transduce.py |
26 |
17 |
0 |
35% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/using.py |
16 |
12 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/when.py |
28 |
24 |
0 |
14% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/where.py |
19 |
15 |
0 |
21% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/whiledo.py |
6 |
2 |
0 |
67% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/window.py |
78 |
65 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/windowwithcount.py |
48 |
38 |
0 |
21% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/windowwithtime.py |
71 |
62 |
0 |
13% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/windowwithtimeorcount.py |
58 |
50 |
0 |
14% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/withlatestfrom.py |
42 |
36 |
0 |
14% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/zip.py |
64 |
58 |
0 |
9% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/linq/observable/ziparray.py |
7 |
4 |
0 |
43% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/__init__.py |
4 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/anonymoussubject.py |
14 |
7 |
0 |
50% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/asyncsubject.py |
76 |
64 |
0 |
16% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/behaviorsubject.py |
68 |
56 |
0 |
18% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/innersubscription.py |
12 |
8 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/replaysubject.py |
102 |
83 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/rx/subjects/subject.py |
65 |
51 |
0 |
22% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/__init__.py |
1 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/common/__init__.py |
1 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/common/exceptions.py |
84 |
8 |
0 |
90% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/__init__.py |
21 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/android/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/android/webdriver.py |
5 |
1 |
0 |
80% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/blackberry/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/blackberry/webdriver.py |
41 |
29 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/chrome/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/chrome/options.py |
78 |
53 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/chrome/remote_connection.py |
8 |
5 |
0 |
38% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/chrome/service.py |
9 |
5 |
0 |
44% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/chrome/webdriver.py |
40 |
27 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/action_chains.py |
128 |
102 |
0 |
20% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/action_builder.py |
49 |
31 |
0 |
37% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/input_device.py |
13 |
7 |
0 |
46% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/interaction.py |
19 |
5 |
0 |
74% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/key_actions.py |
26 |
16 |
0 |
38% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/key_input.py |
23 |
11 |
0 |
52% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/mouse_button.py |
4 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/pointer_actions.py |
66 |
47 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/actions/pointer_input.py |
32 |
19 |
0 |
41% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/alert.py |
22 |
13 |
0 |
41% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/by.py |
10 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/desired_capabilities.py |
15 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/html5/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/html5/application_cache.py |
13 |
2 |
0 |
85% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/keys.py |
67 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/proxy.py |
141 |
94 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/service.py |
105 |
60 |
0 |
43% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/touch_actions.py |
43 |
26 |
0 |
40% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/common/utils.py |
67 |
48 |
0 |
28% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/edge/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/edge/service.py |
12 |
8 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/edge/webdriver.py |
23 |
14 |
0 |
39% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/extension_connection.py |
41 |
22 |
0 |
46% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/firefox_binary.py |
120 |
100 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/firefox_profile.py |
237 |
192 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/options.py |
90 |
48 |
0 |
47% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/remote_connection.py |
10 |
7 |
0 |
30% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/service.py |
10 |
1 |
0 |
90% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/webdriver.py |
105 |
55 |
0 |
48% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/firefox/webelement.py |
6 |
2 |
0 |
67% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/ie/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/ie/options.py |
119 |
58 |
0 |
51% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/ie/service.py |
13 |
9 |
0 |
31% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/ie/webdriver.py |
39 |
25 |
0 |
36% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/opera/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/opera/options.py |
41 |
25 |
0 |
39% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/opera/webdriver.py |
17 |
7 |
0 |
59% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/phantomjs/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/phantomjs/service.py |
26 |
17 |
0 |
35% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/phantomjs/webdriver.py |
21 |
14 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/command.py |
126 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/errorhandler.py |
169 |
124 |
0 |
27% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/file_detector.py |
21 |
11 |
0 |
48% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/mobile.py |
28 |
10 |
0 |
64% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/remote_connection.py |
113 |
89 |
0 |
21% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/switch_to.py |
54 |
37 |
0 |
31% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/utils.py |
41 |
31 |
0 |
24% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/webdriver.py |
385 |
281 |
0 |
27% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/remote/webelement.py |
204 |
136 |
0 |
33% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/safari/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/safari/remote_connection.py |
7 |
4 |
0 |
43% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/safari/service.py |
22 |
15 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/safari/webdriver.py |
45 |
32 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/support/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/support/select.py |
125 |
107 |
0 |
14% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/support/ui.py |
2 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/support/wait.py |
50 |
40 |
0 |
20% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/webkitgtk/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/webkitgtk/options.py |
36 |
23 |
0 |
36% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/webkitgtk/service.py |
9 |
4 |
0 |
56% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/selenium/webdriver/webkitgtk/webdriver.py |
23 |
15 |
0 |
35% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/six.py |
492 |
247 |
0 |
50% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/smmap/__init__.py |
7 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/smmap/buf.py |
74 |
57 |
0 |
23% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/smmap/mman.py |
243 |
174 |
0 |
28% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/smmap/util.py |
102 |
61 |
0 |
40% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/__init__.py |
25 |
11 |
0 |
56% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/cli.py |
66 |
55 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/compat.py |
21 |
9 |
0 |
57% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/engine/__init__.py |
4 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/engine/filter_stack.py |
25 |
17 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/engine/grouping.py |
256 |
223 |
0 |
13% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/engine/statement_splitter.py |
50 |
44 |
0 |
12% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/exceptions.py |
2 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/__init__.py |
13 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/aligned_indent.py |
79 |
61 |
0 |
23% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/others.py |
73 |
57 |
0 |
22% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/output.py |
74 |
62 |
0 |
16% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/reindent.py |
169 |
148 |
0 |
12% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/right_margin.py |
28 |
20 |
0 |
29% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/filters/tokens.py |
38 |
24 |
0 |
37% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/formatter.py |
123 |
118 |
0 |
4% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/keywords.py |
13 |
2 |
0 |
85% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/lexer.py |
35 |
26 |
0 |
26% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/sql.py |
334 |
231 |
0 |
31% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/tokens.py |
37 |
2 |
0 |
95% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/sqlparse/utils.py |
58 |
38 |
0 |
34% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/unidecode/__init__.py |
45 |
36 |
0 |
20% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/__init__.py |
34 |
8 |
0 |
76% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/_collections.py |
181 |
133 |
0 |
27% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/_version.py |
1 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/connection.py |
171 |
118 |
0 |
31% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/connectionpool.py |
313 |
253 |
0 |
19% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/contrib/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/contrib/_appengine_environ.py |
11 |
1 |
0 |
91% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/contrib/socks.py |
75 |
66 |
0 |
12% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/exceptions.py |
100 |
23 |
0 |
77% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/fields.py |
90 |
70 |
0 |
22% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/filepost.py |
43 |
30 |
0 |
30% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/packages/__init__.py |
3 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/packages/six.py |
473 |
232 |
0 |
51% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/packages/ssl_match_hostname/__init__.py |
11 |
6 |
0 |
45% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/poolmanager.py |
177 |
135 |
0 |
24% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/request.py |
39 |
28 |
0 |
28% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/response.py |
401 |
328 |
0 |
18% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/__init__.py |
10 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/connection.py |
66 |
45 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/queue.py |
14 |
5 |
0 |
64% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/request.py |
50 |
37 |
0 |
26% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/response.py |
35 |
29 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/retry.py |
152 |
104 |
0 |
32% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/ssl_.py |
153 |
113 |
0 |
26% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/timeout.py |
60 |
42 |
0 |
30% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/url.py |
199 |
150 |
0 |
25% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/urllib3/util/wait.py |
77 |
59 |
0 |
23% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/__init__.py |
3 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/base.py |
174 |
136 |
0 |
22% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/media_types.py |
16 |
11 |
0 |
31% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/middleware.py |
106 |
78 |
0 |
26% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/responders.py |
166 |
128 |
0 |
23% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/runserver_nostatic/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/runserver_nostatic/management/__init__.py |
0 |
0 |
0 |
100% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/whitenoise/string_utils.py |
11 |
8 |
0 |
27% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/__init__.py |
182 |
128 |
0 |
30% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/composer.py |
92 |
76 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/constructor.py |
477 |
370 |
0 |
22% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/cyaml.py |
46 |
44 |
0 |
4% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/dumper.py |
23 |
12 |
0 |
48% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/emitter.py |
838 |
769 |
0 |
8% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/error.py |
58 |
48 |
0 |
17% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/events.py |
61 |
32 |
0 |
48% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/loader.py |
47 |
30 |
0 |
36% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/nodes.py |
29 |
17 |
0 |
41% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/parser.py |
352 |
312 |
0 |
11% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/reader.py |
122 |
105 |
0 |
14% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/representer.py |
246 |
176 |
0 |
28% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/resolver.py |
134 |
97 |
0 |
28% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/scanner.py |
757 |
676 |
0 |
11% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/serializer.py |
85 |
70 |
0 |
18% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/yaml/tokens.py |
76 |
27 |
0 |
64% |
| /home/hasan/virtualenvironment/project_1/lib/python3.5/site-packages/zipp.py |
114 |
64 |
0 |
44% |
| book_info/__init__.py |
0 |
0 |
0 |
100% |
| book_info/admin.py |
5 |
0 |
0 |
100% |
| book_info/forms.py |
11 |
0 |
0 |
100% |
| book_info/migrations/0001_initial.py |
6 |
0 |
0 |
100% |
| book_info/migrations/0002_auto_20200301_0451.py |
4 |
0 |
0 |
100% |
| book_info/migrations/0003_book_info_created.py |
5 |
0 |
0 |
100% |
| book_info/migrations/0004_auto_20200720_0402.py |
5 |
0 |
0 |
100% |
| book_info/migrations/0005_auto_20200727_1223.py |
5 |
0 |
0 |
100% |
| book_info/migrations/0006_auto_20200727_1334.py |
4 |
0 |
0 |
100% |
| book_info/migrations/__init__.py |
0 |
0 |
0 |
100% |
| book_info/models.py |
18 |
1 |
0 |
94% |
| book_info/serializers.py |
11 |
0 |
0 |
100% |
| book_info/tests.py |
49 |
10 |
0 |
80% |
| book_info/urls.py |
4 |
0 |
0 |
100% |
| book_info/views.py |
104 |
76 |
0 |
27% |
| buy/__init__.py |
0 |
0 |
0 |
100% |
| buy/admin.py |
5 |
0 |
0 |
100% |
| buy/forms.py |
13 |
0 |
0 |
100% |
| buy/migrations/0001_initial.py |
7 |
0 |
0 |
100% |
| buy/migrations/0002_order.py |
6 |
0 |
0 |
100% |
| buy/migrations/0003_card_order.py |
4 |
0 |
0 |
100% |
| buy/migrations/0004_remove_card_order.py |
4 |
0 |
0 |
100% |
| buy/migrations/0005_card_order.py |
5 |
0 |
0 |
100% |
| buy/migrations/0006_auto_20200227_1130.py |
6 |
0 |
0 |
100% |
| buy/migrations/0007_auto_20200227_1133.py |
5 |
0 |
0 |
100% |
| buy/migrations/0008_auto_20200227_1413.py |
6 |
0 |
0 |
100% |
| buy/migrations/0009_order_date.py |
4 |
0 |
0 |
100% |
| buy/migrations/0010_auto_20200301_0406.py |
4 |
0 |
0 |
100% |
| buy/migrations/0011_auto_20200301_0408.py |
4 |
0 |
0 |
100% |
| buy/migrations/__init__.py |
0 |
0 |
0 |
100% |
| buy/models.py |
25 |
2 |
0 |
92% |
| buy/urls.py |
4 |
0 |
0 |
100% |
| buy/views.py |
103 |
76 |
0 |
26% |
| cgpa/__init__.py |
0 |
0 |
0 |
100% |
| cgpa/admin.py |
7 |
0 |
0 |
100% |
| cgpa/forms.py |
18 |
0 |
0 |
100% |
| cgpa/migrations/0001_initial.py |
7 |
0 |
0 |
100% |
| cgpa/migrations/0002_auto_20200802_0804.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0003_course_result_student.py |
7 |
0 |
0 |
100% |
| cgpa/migrations/0004_auto_20200802_0819.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0005_course_result_student.py |
7 |
0 |
0 |
100% |
| cgpa/migrations/0006_auto_20200802_0933.py |
5 |
0 |
0 |
100% |
| cgpa/migrations/0007_auto_20200802_1004.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0008_auto_20200802_1009.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0009_course_university.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0010_auto_20200802_1058.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0011_auto_20200802_1058.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0012_remove_course_university.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0013_course_university.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0014_auto_20200802_1537.py |
4 |
0 |
0 |
100% |
| cgpa/migrations/0015_auto_20200802_1740.py |
5 |
0 |
0 |
100% |
| cgpa/migrations/__init__.py |
0 |
0 |
0 |
100% |
| cgpa/models.py |
26 |
3 |
0 |
88% |
| cgpa/urls.py |
4 |
0 |
0 |
100% |
| cgpa/views.py |
132 |
102 |
0 |
23% |
| manage.py |
12 |
2 |
0 |
83% |
| online_bookshop/__init__.py |
0 |
0 |
0 |
100% |
| online_bookshop/settings.py |
28 |
0 |
0 |
100% |
| online_bookshop/urls.py |
14 |
1 |
0 |
93% |
| online_bookshop/views.py |
36 |
23 |
0 |
36% |


--- title: How to Start Investing in Stocks layout: default locale: hi image: assets/images/fincz-default-image.png excerpt: "Best Blog For Business and Investment Tips for Share market, Online Earning, Loans, Credit Cards, Insurance Etc." permalink: "/hindi/" --- {% if page.url == "/hindi/" %}


Prison Profiteer Global Tel Link Charges Prisoners by the Minute for Reading
by Andrew OrrPrison libraries of paper books are slowly disappearing. In their place prisoners are getting tablets. But profits are being made when prisoners send emails, videoconferencing with family, listening to music, and reading.
In West Virginia, a company called Global Tel Link has the contract to provide prisoners in ten prisons with “free” tablets, for which they charge $0.05/minute for reading ebooks, primarily drawn from Project Gutenberg, a free online service of volunteer-produced, public domain and CC-licensed ebooks.
Check It Out: Prison Profiteer Global Tel Link Charges Prisoners by the Minute for Reading


RAND() → randomNumber
Return a pseudo-random number between 0 and 1.
RAND() // 0.3503170117504508
RAND() // 0.6138226173882478
Complex example:
LET coinFlips = (
FOR i IN 1..100000
RETURN RAND() > 0.5 ? "heads" : "tails"
)
RETURN MERGE(
FOR flip IN coinFlips
COLLECT f = flip WITH COUNT INTO count
RETURN { [f]: count }
)
Result:
[
{
"heads": 49902,
"tails": 50098
}
]


Police to debrief on the 'Produce' series' manipulation investigations later today
by jennywillThe police will be debriefing about their 'Produce 101' series investigations.
The Seoul Police District's Cyber Security Team revealed that they would be holding a debriefing related to the investigations on the 'Produce 101' series. During the course of their investigations, their area was broadened to include 'Idol School' as well.
Stay tuned for more on the debriefing.


ice shelf Antarctic ocean warming EAP SOT Holocene temperature Peninsula water melting data {border-style TEX surface \documentclass[pt]{minimal} \setlength{\oddsidemargin}{-pt} \usepackage{amsbsy} \usepackage{amsfonts} \usepackage{amsmath} \usepackage{amssymb} \usepackage{mathrsfs} \usepackage{upgreek} \usepackage{wasysym} px;} years #ffffff;} (Fig. waters shelves subsurface warm Larsen recent Nature based changes SAT climate impact increase regional using Ekman Geophys. Supplementary \begin{document}$${\mathrm{TEX}}_{}^{\mathrm{L}}$$\end{document} depth major wind . °C Antarctica Ocean Sci. [], century circulation continental deep temperatures values Res. basal core early grid.. model reanalysis record relatively retreat ./nature atmospheric computed estimated forcing history models observed period proxy pumping px; study variability variations {font-family Figure GLORYS RCP. SOTs Southern change collapse cooling font-size future heat melt net past projections results suggest used (Supplementary (i.e., GDGT Gustav Lett. Prince SWW Science coastal double; driven large mean northern observations probably rate records sea site trend trends (see Clim. Fig. Indeed, JRI Rev. WDW Weddell anomalies associated atmosphere border-color border-width calibration collapses current decades different distribution enhanced following lack parameterization reanalyses reconstructed sea-ice sea-level sheet similar solid; strongly thinning upwelling use warmer wind-driven {font-style {font-weight – m ./j.quascirev... ./science. CDW Change Channel Climate Commons Creative GDGTs Given Holland However, Ice JPC- LINK Netherlands Quat. Research Sea South Université area average bold conditions continuous controlling correspond courier; dominant eastern em; estimate events evolution funded i.e., ice-sheet iceberg including intensity length linear low main marine near order penetration polar position project pt;} remains represent role scenarios shift supported terms time transport version {{\mathrm{GDGT}} −);


2019
1. Xu Han, Tianyu Gao, Yuan Yao, Demin Ye, Zhiyuan Liu, Maosong Sun.
OpenNRE: An Open and Extensible Toolkit for Neural Relation Extraction. EMNLP 2019. Demo paper.
2.
Ruidong Wu, Yuan Yao, Xu Han, Ruobing Xie, Zhiyuan Liu, Fen Lin, Leyu Lin, Maosong Sun. Open
Relation Extraction: Relational Knowledge Transfer from Supervised Data to Unsupervised Data. EMNLP 2019.
Long paper.
3.
Tianyu Gao, Xu Han, Hao Zhu, Zhiyuan Liu , Peng Li, Maosong Sun, Jie Zhou. FewRel 2.0: Towards More
Challenging Few-Shot Relation Classification. EMNLP 2019. Short paper.
4.
Xiaozhi Wang, Ziqi Wang, Xu Han, Zhiyuan Liu, Juanzi Li, Peng Li, Maosong Sun, Jie Zhou, Xiang Ren.
HMEAE: Hierarchical Modular Event Argument Extraction. EMNLP 2019. Short paper.
5.
Xin Lv, Yuxian Gu, Xu Han, Lei Hou, Juanzi Li, Zhiyuan Liu. Adapting Meta Knowledge Graph
Information for Multi-Hop Reasoning over Few-Shot Relations. EMNLP 2019. Short paper.
6. Zhengyan Zhang, Xu Han*, Zhiyuan Liu, Xin Jiang, Maosong Sun, Qun Liu (* indicates equal
contribution). ERNIE: Enhanced Language Representation with Informative Entities. ACL 2019. Long paper.
7. Jie Zhou, Xu Han, Cheng Yang, Zhiyuan Liu, Lifeng Wang, Changcheng Li, Maosong Sun.
GEAR: Graph-based Evidence Aggregating and Reasoning for Fact Verification. ACL 2019. Long paper.
8. Yuan Yao, Deming Ye, Peng Li, Xu Han, Yankai Lin, Zhenghao Liu, Zhiyuan Liu, Lixin
Huang, Jie Zhou, Maosong Sun. DocRED: A Large-Scale Document-Level Relation Extraction Dataset. ACL 2019.
Long paper.
9. Weize Chen, Hao Zhu, Xu Han, Zhiyuan Liu, Maosong Sun. Quantifying Similarity between
Relations with Fact Distribution. ACL 2019. Long paper.
10. Shun Zheng, Xu Han, Yankai Lin, Peilin Yu, Lu Chen, Ling Huang, Zhiyuan Liu, Wei Xu.
DIAG-NRE: A Neural Pattern Diagnosis Framework for Distantly Supervised Neural Relation Extraction. ACL
2019. Long paper.
11. Xiaozhi Wang*, Xu Han*, Zhiyuan Liu, Maosong Sun, Peng Li (* indicates equal
contribution). Adversarial Training for Weakly Supervised Event Detection. NAACL-HLT 2019. Long paper.
12. Tianyu Gao*, Xu Han*, Zhiyuan Liu, Maosong Sun (* indicates equal contribution).
Hybrid Attention-based Prototypical Networks for Noisy Few-Shot Relation Classification. AAAI 2019. Long
paper.


(Re) Generate a list of strong passwords you can find again and again with parameters that you have in mind !
Nickname, pet name or simple password ?
Date (ex: event, birthday, etc.)?
A size in cm (ex: size of someone)?
Locking pattern that you will remember ?
Schéma :
Lenght of passwords (>10 characters):
Number of passwords (expandable: [10-10 000])
1. Enter a code name (a nickname, nickname, password etc.)
2. Enter a date you know.
3. Enter your height or a number you know.
4. Enter a locking scheme that you will remember.
=> With these same fields that you will remember, the expandable list of generated passwords will always be the same..
NB : each password in the list can be used temporarily by retaining its hint....
The number of possible input combinations of this calculator greatly exceeds 10 billion. The Password Generator uses a special pseudo-random number generator (PRNG). This one admits inputs of unbounded sizes (an unbounded space of seeds).
(More information: PULS-PRNG).


Chapter 1: Nutrition in Plants
Aratrik Pal
April 9, 2021
Autotrophic
- Make own food
- Green leaves b.c. Chlorophyll
Heterotrophic
Parisitic
- Food from other organism
- E.g.:
- Cuscuta
- Rafflesia
- Corpse Flower
Saprophitic
- Food from dead or decaying subst.
- E.g.:
Symbiotic
- Share shelter and food
- E.g.:
- Rhizobium bacteria & leguminous plants
- Algae & Fungi => Lichen
Insectivorous
- Eat insects
- Colourful
- Body parts modified to trap
- Need insects b.c.:
- Complex form -> simple form (nutrients)
- E.g.:


Preparation time
less than 30 mins
Cooking time
10 to 30 mins
Serves
Serves 2
Posh fried fish is the order of the day with this easy recipe for beer-battered perfection.
For the batter, sift the plain flour and cornflour together into a bowl.
Whisk in the ale and the soda water until the mixture is smooth and well combined. Set aside to rest for 10 minutes, then whisk again for 30 seconds.
Meanwhile, for the tartare sauce, mix together all of the tartare sauce ingredients until well combined. Chill in the fridge until needed.
To cook the fish, pour enough vegetable oil into a deep-sided, heavy-based pan to fill it by about two-thirds. Heat the oil until a breadcrumb sizzles and turns golden-brown when dropped into it. (CAUTION: hot oil can be dangerous. Do not leave unattended.)
Sprinkle a little flour onto a plate and press both sides of each of the lemon sole strips into the flour until completely covered.
Dip the floured lemon sole strips into the batter, then gently lower them into the hot oil and fry until crisp and golden-brown. Remove from the pan using a slotted spoon and set aside to drain on kitchen paper.
To serve, place a few lemon sole goujons onto each of four serving plates. Spoon a dollop of tartare sauce alongside each portion. Garnish with a handful of watercress leaves.


See: Description
AI platform for the card game Hanabi.
This projects aims to provide a set of java classes and interface to facilliate agents playing the card game: Hanabi. This project is designed for use in the unit CITS3001 Algorithms, Agents and Artificial Intelligence at The University of Western Australia. Students may use and modify these files to reserach different artificial intelligence agents in the game Hanabi. There will also be an AI bot tournament with the additional rules specified below.
Hanabi is a cooperative game for 2 to 5 players, that is,
a game where the players do not play against each other but work together towards a common goal.
In this case they are absent minded firework manufacturers who accidentally mixed up powders, fuses and rockets from a firework display.
The show is about to start and panic is setting in. They have to work together to stop the show becoming a disaster!
The pyrotechnicians have to put together 5 fireworks, 1 white, 1 red, 1 blue, 1 yellow, 1 green),
by making series rising in number (1, 2, 3, 4, 5) with the same coloured cards.
Place the 8 blue tokens in the lid of the box and the 3 red tokens just next to it.
Shuffle the 50 cards to make a deck and put them face down. Deal a hand of cards to each player:
If there are 2 or 3 players, each player receives 5 cards.
If there are 4 or 5 players, each player receives 4 cards.
Important :The players should not look at the cards which are dealt to them!
They pick them up so that the other players can see them but so that they cannot see them themselves
(so back to front!)
They are not allowed to look at their own cards at all during the game.
This would dishonour them and taint their reputation as master pyrotechnicians!
The players then take their turn going in a clockwise direction.
On their turn, a player must complete one, and only one, of the following three actions (you are not allowed to skip your turn):
1. Give one piece of information:
In order to carry out this task, there must be a blue token in the box lid:
The player takes a blue token from the lid of the box and puts it at the side with the red tokens.
They can then tell a teammate something about the cards that this player has in their hand.
The player can either:
- Give information about a single colour.
The player says "these cards are of colour X" and points to every X coloured card in the players hand.
The player cannot say another payer has no cards of some colour.
- Give information about a single number.
The player says "these cards have number Y" and points to every Y numbered card in the players hand.
The player cannot say another payer has no cards of some number.
2. Discard a card:
Performing this task allows a blue token to be returned to the lid of the box.
The player discards a card from his hand and puts it in the discard pile (next to the box, face up).
They then takes a new card and adds it to their hand without looking at it.
3. Play a card:
The player takes a card from their hand and puts it face up on the table.
Two options are possible:
- The card either begins or completes a firework and it is then added to this firework
- Or the card does not complete any firework it is then discarded and a red token is added to the lid of the box
The player then takes a new card and adds it to his hand without looking at it
There can only be one firework of each colour. The cards for a firework have to be placed in rising order (1, then 2, then 3, then 4 and finally 5). There can only be one card of each value in each firework (so 5 cards in total).
When a player completes a firework i.e. plays the card with a value of 5, the player puts a blue token back in the lid of the box.
There are 3 ways to end the game of Hanabi :
1. The game ends immediately and is lost if the third red token is placed in the lid of the box (everyone scores 0 points).
2. The game ends immediately and it is a stunning victory if
the firework makers manage to make the 5 fireworks before the cards run out.
The players are then awarded the maximum score of 25 points.
3. The game ends if a firework maker takes the last card from the pile.
each player plays one more time, including the player who picked up the last card
In order to calculate their scores, the players add up the largest value card for each of the 5 fireworks. Artistic impression is determined by the Firework Manufacturers International Federation reference scale:
| Points | Overall Impression |
|:----------:|-----------------------------------------------------------|
| 0-5 | horrible, booed by the crowd. |
| 6-10 | mediocre, just a spattering of applause. |
| 11-15 | honourable, but will not be remembered for very long... |
| 16-20 | excellent, crowd pleasing. |
| 21 - 24 | amazing, will be remembered for a very long time! |
| 25 | legendary, everyone left speechless, stars in their eyes |
Good luck.
javac -d bin src/*/*.java
java -cp bin hanabAI.Hanabi


This version of the Dublin Core Elements is not endorsed or supported by the Dublin Core Metadata Inititive. Copyright of the Dublin Core Elements remains with the Dublin Core Metadata Inititive under their original terms. Copyright © 2008 Dublin Core Metadata Initiative. All Rights Reserved. http://www.dublincore.org/about/copyright/
This document provides ready reference for the Dublin Core DL Element Set, Version 1.1 written in the Web Ontology Language. This eases the use of the elements in an OWL DL ontology. For more detailed documentation and links to historical versioning information, see the document "DCMI Metadata Terms".
This is version 1.0 This document is subject to change depending on changes to the original Dublin Core Element Set. Comments are very welcome, please send them to<EMAIL_ADDRESS>Thank you.
The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name "Dublin" is due to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" because its elements are broad and generic, usable for describing a wide range of resources.
The fifteen element "Dublin Core" described in this standard is part of a larger set of metadata vocabularies and technical specifications maintained by the Dublin Core Metadata Initiative (DCMI). The full set of vocabularies, DCMI Metadata Terms [DCMI-TERMS], also includes sets of resource classes (including the DCMI Type Vocabulary [DCMI-TYPE]), vocabulary encoding schemes, and syntax encoding schemes. The terms in DCMI vocabularies are intended to be used in combination with terms from other, compatible vocabularies in the context of application profiles and on the basis of the DCMI Abstract Model [DCAM].
All changes made to terms of the Dublin Core Metadata Element Set since 2001 have been reviewed by a DCMI Usage Board in the context of a DCMI Namespace Policy [DCMI-NAMESPACE]. The namespace policy describes how DCMI terms are assigned Uniform Resource Identifiers (URIs) and sets limits on the range of editorial changes that may allowably be made to the labels, definitions, and usage comments associated with existing DCMI terms.
This document, an excerpt from the more comprehensive document "DCMI Metadata Terms" [DCTERMS] provides an abbreviated reference version of the fifteen element descriptions that have been formally endorsed in the following standards:
Since 1998, when these fifteen elements entered into a standardization track, notions of best practice in the Semantic Web have evolved to include the assignment of formal domains and ranges in addition to definitions in natural language. Domains and ranges specify what kind of described resources and value resources are associated with a given property. Domains and ranges express the meanings implicit in natural-language definitions in an explicit form that is usable for the automatic processing of logical inferences. When a given property is encountered, an inferencing application may use information about the domains and ranges assigned to a property in order to make inferences about the resources described thereby.
Since January 2008, therefore, DCMI includes formal domains and ranges in the definitions of its properties. So as not to affect the conformance of existing implementations of "simple Dublin Core" in RDF, domains and ranges have not been specified for the fifteen properties of the dc: namespace (http://purl.org/dc/elements/1.1/). Rather, fifteen new properties with "names" identical to those of the Dublin Core Metadata Element Set Version 1.1 have been created in the dcterms: namespace (http://purl.org/dc/terms/). These fifteen new properties have been defined as subproperties of the corresponding properties of DCMES Version 1.1 and assigned domains and ranges as specified in the more comprehensive document "DCMI Metadata Terms" [DCTERMS].
Implementers may freely choose to use these fifteen properties either in their legacy dc: variant (e.g., http://purl.org/dc/elements/1.1/creator) or in the dcterms: variant (e.g., http://purl.org/dc/terms/creator) depending on application requirements. The RDF schemas of the DCMI namespaces describe the subproperty relation of dcterms:creator to dc:creator for use by Semantic Web-aware applications. Over time, however, implementers are encouraged to use the semantically more precise dcterms: properties, as they more fully follow emerging notions of best practice for machine-processable metadata.
An alphabetical index of Dublin Core Elements, is given below. All the terms are hyperlinked to their detailed description for quick reference.
%sThe Dublin Core DL Elements definitions presented here are taken from the original ...
Here is a very basic document describing a foo:
<rdf:RDF />
...


XCTestCase Class Reference
| Inherits from | XCTest : NSObject |
|---|---|
| Declared in | XCTestCase.h |
Overview
- @class XCTestCase
- XCTestCase is a concrete subclass of XCTest that should be the override point for
- most developers creating tests for their projects. A test case subclass can have
- multiple test methods and supports setup and tear down that executes for every test
- method as well as class level setup and tear down. *
- To define a test case: *
- • Create a subclass of XCTestCase.
- • Implement -test methods.
- • Optionally define instance variables or properties that store the state of the test.
- • Optionally initialize state by overriding setUp
- • Optionally clean-up after a test by overriding tearDown. *
- Test methods are instance methods meeting these requirements:
- • accepting no parameters
- • returning no value
- • prefixed with ‘test’ *
For example:
- (void)testSomething;
Test methods are automatically recognized as test cases by the XCTest framework.
- Each XCTestCase subclass’s defaultTestSuite is a XCTestSuite which includes theses
- tests. Test method implementations usually contain assertions that must be verified
for the test to pass, for example:
@interface MathTest : XCTestCase { @private float f1; float f2; }
- (void)testAddition;
@end
@implementation MathTest
(void)setUp { f1 = 2.0; f2 = 3.0; }
(void)testAddition { XCTAssertTrue (f1 + f2 == 5.0); } @end
@category AsynchronousTesting
@discussion This category introduces support for asynchronous testing in XCTestCase. The mechanism allows you to specify one or more “expectations” that will occur asynchronously as a result of actions in the test. Once all expectations have been set, a “wait” API is called that will block execution of subsequent test code until all expected conditions have been fulfilled or a timeout occurs.
Other Methods
+ testCaseWithInvocation:
@method +testCaseWithInvocation:
+ (instancetype)testCaseWithInvocation:(nullable NSInvocation *)invocation
Discussion
@method +testCaseWithInvocation:
Declared In
XCTestCase.h
– initWithInvocation:
@method -initWithInvocation:
- (instancetype)initWithInvocation:(nullable NSInvocation *)invocation
Discussion
@method -initWithInvocation:
Declared In
XCTestCase.h
+ testCaseWithSelector:
@method +testCaseWithSelector:
+ (instancetype)testCaseWithSelector:(SEL)selector
Discussion
@method +testCaseWithSelector:
Declared In
XCTestCase.h
– initWithSelector:
@method -initWithSelector:
- (instancetype)initWithSelector:(SEL)selector
Discussion
@method -initWithSelector:
Declared In
XCTestCase.h
invocation
@property invocation The invocation used when this test is run.
@property (strong, nullable) NSInvocation *invocation
Discussion
@property invocation The invocation used when this test is run.
Declared In
XCTestCase.h
– invokeTest
@method -invokeTest Invoking a test performs its setUp, invocation, and tearDown. In general this should not be called directly.
- (void)invokeTest
Discussion
@method -invokeTest Invoking a test performs its setUp, invocation, and tearDown. In general this should not be called directly.
Declared In
XCTestCase.h
continueAfterFailure
@property continueAfterFailure The test case behavior after a failure. Defaults to YES.
@property BOOL continueAfterFailure
Discussion
@property continueAfterFailure The test case behavior after a failure. Defaults to YES.
Declared In
XCTestCase.h
– recordFailureWithDescription:inFile:atLine:expected:
@method -recordFailureWithDescription:inFile:atLine:expected: Records a failure in the execution of the test and is used by all test assertions.
- (void)recordFailureWithDescription:(NSString *)description inFile:(NSString *)filePath atLine:(NSUInteger)lineNumber expected:(BOOL)expected
Parameters
description |
The description of the failure being reported. |
|---|---|
filePath |
The file path to the source file where the failure being reported was encountered. |
lineNumber |
The line number in the source file at filePath where the failure being reported was encountered. |
expected |
YES if the failure being reported was the result of a failed assertion, NO if it was the result of an uncaught exception. |
Discussion
@method -recordFailureWithDescription:inFile:atLine:expected: Records a failure in the execution of the test and is used by all test assertions.
Declared In
XCTestCase.h
+ testInvocations
@method +testInvocations Invocations for each test method in the test case.
+ (NSArray<NSInvocation*> *)testInvocations
Discussion
@method +testInvocations Invocations for each test method in the test case.
Declared In
XCTestCase.h
+ defaultPerformanceMetrics
@method +defaultPerformanceMetrics The names of the performance metrics to measure when invoking measureBlock:. Returns XCTPerformanceMetric_WallClockTime by default. Subclasses can override this to change the behavior of measureBlock:
+ (NSArray<NSString*> *)defaultPerformanceMetrics
Discussion
@method +defaultPerformanceMetrics The names of the performance metrics to measure when invoking measureBlock:. Returns XCTPerformanceMetric_WallClockTime by default. Subclasses can override this to change the behavior of measureBlock:
Declared In
XCTestCase.h
– measureBlock:
- @method -measureBlock: *
- Call from a test method to measure resources (defaultPerformanceMetrics) used by the
- block in the current process.
- (void)measureBlock:(void ( ^ ) ( void ))block
Discussion
- @method -measureBlock: *
- Call from a test method to measure resources (defaultPerformanceMetrics) used by the
block in the current process.
(void)testPerformanceOfMyFunction {
[self measureBlock:^{ // Do that thing you want to measure. MyFunction();
}]; }
@param block A block whose performance to measure.
Declared In
XCTestCase.h
– measureMetrics:automaticallyStartMeasuring:forBlock:
- @method -measureMetrics:automaticallyStartMeasuring:forBlock: *
- Call from a test method to measure resources (XCTPerformanceMetrics) used by the
- block in the current process. Each metric will be measured across calls to the block.
- The number of times the block will be called is undefined and may change in the
- future. For one example of why, as long as the requested performance metrics do
- not interfere with each other the API will measure all metrics across the same
- calls to the block. If the performance metrics may interfere the API will measure
- them separately.
- (void)measureMetrics:(NSArray<NSString*> *)metrics automaticallyStartMeasuring:(BOOL)automaticallyStartMeasuring forBlock:(void ( ^ ) ( void ))block
Discussion
- @method -measureMetrics:automaticallyStartMeasuring:forBlock: *
- Call from a test method to measure resources (XCTPerformanceMetrics) used by the
- block in the current process. Each metric will be measured across calls to the block.
- The number of times the block will be called is undefined and may change in the
- future. For one example of why, as long as the requested performance metrics do
- not interfere with each other the API will measure all metrics across the same
- calls to the block. If the performance metrics may interfere the API will measure
them separately.
(void)testMyFunction2_WallClockTime { [self measureMetrics:[[self class] defaultPerformanceMetrics] automaticallyStartMeasuring:NO forBlock:^{
// Do setup work that needs to be done for every iteration but you don't want to measure before the call to -startMeasuring SetupSomething(); [self startMeasuring]; // Do that thing you want to measure. MyFunction(); [self stopMeasuring]; // Do teardown work that needs to be done for every iteration but you don't want to measure after the call to stopMeasuring TeardownSomething();
}]; }
Caveats:
- • If YES was passed for automaticallyStartMeasuring and startMeasuring is called
- anyway, the test will fail.
- • If NO was passed for automaticallyStartMeasuring then startMeasuring must be
- called once and only once before the end of the block or the test will fail.
- • If stopMeasuring is called multiple times during the block the test will fail. *
- @param metrics An array of NSStrings (XCTPerformanceMetrics) to measure. Providing an unrecognized string is a test failure. *
- @param automaticallyStartMeasuring If NO, XCTestCase will not take any measurements until startMeasuring is called. *
- @param block A block whose performance to measure.
Declared In
XCTestCase.h
– startMeasuring
@method -startMeasuring Call this from within a measure block to set the beginning of the critical section. Measurement of metrics will start at this point.
- (void)startMeasuring
Discussion
@method -startMeasuring Call this from within a measure block to set the beginning of the critical section. Measurement of metrics will start at this point.
Declared In
XCTestCase.h
– stopMeasuring
@method -stopMeasuring Call this from within a measure block to set the ending of the critical section. Measurement of metrics will stop at this point.
- (void)stopMeasuring
Discussion
@method -stopMeasuring Call this from within a measure block to set the ending of the critical section. Measurement of metrics will stop at this point.
Declared In
XCTestCase.h
AsynchronousTesting Methods
– expectationWithDescription:
@method +expectationWithDescription:
- (XCTestExpectation *)expectationWithDescription:(NSString *)description
Discussion
@method +expectationWithDescription:
@param description This string will be displayed in the test log to help diagnose failures.
@discussion Creates and returns an expectation associated with the test case.
Declared In
XCTestCase+AsynchronousTesting.h
– waitForExpectationsWithTimeout:handler:
@method -waitForExpectationsWithTimeout:handler:
- (void)waitForExpectationsWithTimeout:(NSTimeInterval)timeout handler:(nullable XCWaitCompletionHandler)handler
Discussion
@method -waitForExpectationsWithTimeout:handler:
@param timeout The amount of time within which all expectations must be fulfilled.
@param handler If provided, the handler will be invoked both on timeout or fulfillment of all expectations. Timeout is always treated as a test failure.
@discussion -waitForExpectationsWithTimeout:handler: creates a point of synchronization in the flow of a test. Only one -waitForExpectationsWithTimeout:handler: can be active at any given time, but multiple discrete sequences of { expectations -> wait } can be chained together.
-waitForExpectationsWithTimeout:handler: runs the run loop while handling events until all expectations are fulfilled or the timeout is reached. Clients should not manipulate the run loop while using this API.
Declared In
XCTestCase+AsynchronousTesting.h
– keyValueObservingExpectationForObject:keyPath:expectedValue:
@method keyValueObservingExpectationForObject:keyPath:expectedValue:
- (XCTestExpectation *)keyValueObservingExpectationForObject:(id)objectToObserve keyPath:(NSString *)keyPath expectedValue:(nullable id)expectedValue
Discussion
@method keyValueObservingExpectationForObject:keyPath:expectedValue:
@discussion A convenience method for asynchronous tests that use Key Value Observing to detect changes to values on an object. This variant takes an expected value and observes changes on the object until the keyPath’s value matches the expected value using [NSObject isEqual:]. If other comparisions are needed, use the variant below that takes a handler block.
@param objectToObserve The object to observe.
@param keyPath The key path to observe.
@param expectedValue Expected value of the keyPath for the object. The expectation will fulfill itself when the keyPath is equal, as tested using [NSObject isEqual:]. If nil, the expectation will be fulfilled by the first change to the key path of the observed object.
@return Creates and returns an expectation associated with the test case.
Declared In
XCTestCase+AsynchronousTesting.h
– keyValueObservingExpectationForObject:keyPath:handler:
@method keyValueObservingExpectationForObject:keyPath:handler:
- (XCTestExpectation *)keyValueObservingExpectationForObject:(id)objectToObserve keyPath:(NSString *)keyPath handler:(nullable XCKeyValueObservingExpectationHandler)handler
Discussion
@method keyValueObservingExpectationForObject:keyPath:handler:
@discussion Variant of the convenience for tests that use Key Value Observing. Takes a handler block instead of an expected value. Every KVO change will run the handler block until it returns YES (or the wait times out). Returning YES from the block will fulfill the expectation. XCTAssert and related APIs can be used in the block to report a failure.
@param objectToObserve The object to observe.
@param keyPath The key path to observe.
@param handler Optional handler, /see XCKeyValueObservingExpectationHandler. If not provided, the expectation will be fulfilled by the first change to the key path of the observed object.
@return Creates and returns an expectation associated with the test case.
Declared In
XCTestCase+AsynchronousTesting.h
– expectationForNotification:object:handler:
@method expectationForNotification:object:handler:
- (XCTestExpectation *)expectationForNotification:(NSString *)notificationName object:(nullable id)objectToObserve handler:(nullable XCNotificationExpectationHandler)handler
Discussion
@method expectationForNotification:object:handler:
@discussion A convenience method for asynchronous tests that observe NSNotifications.
@param notificationName The notification to register for.
@param objectToObserve The object to observe.
@param handler Optional handler, /see XCNotificationExpectationHandler. If not provided, the expectation will be fulfilled by the first notification matching the specified name from the observed object.
@return Creates and returns an expectation associated with the test case.
Declared In
XCTestCase+AsynchronousTesting.h
XCTestSuiteExtensions Methods
+ defaultTestSuite
@method +defaultTestSuite Returns a test suite containing test cases for all of the tests in the class.
+ (XCTestSuite *)defaultTestSuite
Discussion
@method +defaultTestSuite Returns a test suite containing test cases for all of the tests in the class.
Declared In
XCTestCase.h
+ setUp
@method +setUp Setup method called before the invocation of any test method in the class.
+ (void)setUp
Discussion
@method +setUp Setup method called before the invocation of any test method in the class.
Declared In
XCTestCase.h
+ tearDown
@method +testDown Teardown method called after the invocation of every test method in the class.
+ (void)tearDown
Discussion
@method +testDown Teardown method called after the invocation of every test method in the class.
Declared In
XCTestCase.h


Grammar rules are best explained in terms of an interpreter. The
semantics of phrase/3
is shown as if defined by the interpreter
shown below. The interpreter's case analysis is as follows:
-->/2
,
unified against, and its body is interpreted.
If none exists, this is treated as a procedure call to
a predicate N/A+2.
The following points are worth noting:
S0
and S
. -->/2
is not a predicate.
The interpreter is as follows, slightly simplified:
phrase(M:Body, S0, S) :- phrase(Body, M, S0, S). phrase(Var, M, S0, S) :- \+callable(Var), !, must_be(Term, callable, phrase(M:Var,S0,S), 1). phrase(M:Body, _, S0, S) :- !, phrase(Body, M, S0, S). phrase(!, _, S0, S) :- !, cut relevant choicepoints, S0 = S. % unification AFTER action phrase((A, B), M, S0, S) :- !, phrase(A, M, S0, S1), phrase(B, M, S1, S). phrase((A -> B), M, S0, S) :- !, ( phrase(A, M, S0, S1) -> phrase(B, M, S1, S) ). phrase((A -> B ; C), M, S0, S) :- !, ( phrase(A, M, S0, S1) -> phrase(B, M, S1, S) ; phrase(C, M, S0, S) ). phrase((A ; B), M, S0, S) :- !, ( phrase(A, M, S0, S) ; phrase(B, M, S0, S) ). phrase(\+(A), M, S0, S) :- !, ( phrase(A, M, S0, _) -> fail ; S0 = S ). phrase(_^A, M, S0, S) :- !, phrase(A, M, S0, S). phrase(if(A,B,C), M, S0, S) :- !, if(phrase(A, M, S0, S1), phrase(B, M, S1, S), phrase(C, M, S0, S)). phrase(once(A), M, S0, S) :- !, ( phrase(A, M, S0, S1) -> S1 = S % unification AFTER call ). phrase([], _, S0, S) :- !, S0 = S. phrase([H|T], M, S0, S) :- !, S0 = [H|S1], phrase(T, M, S1, S). phrase({G}, M, S0, S) :- !, call(M:G), S0 = S. % unification AFTER call phrase(NT, M, S0, S) :- \+ \+(M:NT --> Rhs), !, % grammar rule exists? (M:NT --> Rhs), phrase(Rhs, M, S0, S). phrase(NT, M, S0, S) :- call(M:NT, S0, S). % otherwise, treat as procedure call
As mentioned above, grammar rules are merely a convenient abbreviation for ordinary Prolog clauses. Each grammar rule is translated into a Prolog clause as it is compiled. This translation is exemplified below.
The procedural interpretation of a grammar rule is that it takes an
input list of symbols or character codes, analyzes some initial
portion of that list, and produces the remaining portion (possibly
enlarged) as output for further analysis. The arguments required for
the input and output lists are not written explicitly in a grammar
rule, but are added when the rule is translated into an ordinary
Prolog clause. The translations shown differ from the output of
listing/[0,1]
in that internal translations such as variable
renaming are not represented. This is done in the interests of
clarity. For example, a rule such as (A) will be depicted as
translating into (B) rather than (C).
p(X) --> q(X). (A)
p(X, S0, S) :- q(X, S0, S). (B)
p(A, B, C) :- q(A, B, C). (C)
If there is more than one non-terminal on the right-hand side, as in (D) the corresponding input and output arguments are identified, translating into (E):
p(X, Y) --> q(X), r(X, Y), s(Y). (D)
p(X, Y, S0, S) :- (E) q(X, S0, S1), r(X, Y, S1, S2), s(Y, S2, S).
Terminals are translated using the built-in predicate =/2
.
For instance, (F) is translated into (G):
p(X) --> [go, to], q(X), [stop]. (F)
p(X, S0, S) :- (G) S0 = [go,to|S1], q(X, S1, S2), S2 = [stop|S].
Extra conditions expressed as explicit procedure calls, enclosed in curly braces, naturally translate into themselves. For example (H) translates to (I):
p(X) --> [X], {integer(X), X > 0}, q(X). (H)
p(X, S0, S) :- (I) S0 = [X|S1], integer(X), X > 0, q(X, S1, S).
Terminals on the left-hand side of a rule, enclosed in square brackets, also translate into a unification. For example, (J) becomes (K):
is(N), [not] --> [aint]. (J)
is(N, S0, S) :- (K) S0 = [aint|S1], S = [not|S1].
Disjunction and other control constructs have a fairly obvious translation. For example, (L), a rule that equates phrases like “(sent) a letter to him” and “(sent) him a letter”, translates to (M):
args(X, Y) --> (L) dir(X), [to], indir(Y) | indir(Y), dir(X).
args(X, Y, S0, S) :- (M) ( dir(X, S0, S1), S1 = [to|S2], indir(Y, S2, S) | indir(Y, S0, S1), dir(X, S1, S) ).
In order to look at these translations, declare the grammar rules
dynamic and use listing/[0,1]
. However, bear in mind that
a grammar rule with head functor N/A is transformed to a Prolog
clause with head functor N/A+2. For example, the following declaration for
grammar rule (L) would enable you to list its translation, (M):
:- dynamic args/4.


All the resources successfully uploaded and processed onto the server can be edited and managed below.


10th standard details missing..
12th standard details missing..
Graduation standard details missing..
Graduation standard details missing..
Graduation standard details missing..
Graduation standard details missing..
Graduation standard details missing..
Graduation standard details missing..
Graduation standard details missing..


public enum RestStatus extends java.lang.Enum<RestStatus>
| Enum Constant and Description |
|---|
ACCEPTED
The request has been accepted for processing, but the processing has not been completed.
|
BAD_GATEWAY
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it
accessed in attempting to fulfill the request.
|
BAD_REQUEST
The request could not be understood by the server due to malformed syntax.
|
CONFLICT
The request could not be completed due to a conflict with the current state of the resource.
|
CONTINUE
The client SHOULD continue with its request.
|
CREATED
The request has been fulfilled and resulted in a new resource being created.
|
EXPECTATION_FAILED
The expectation given in an Expect request-header field (see section 14.20) could not be met by this server,
or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the
next-hop server.
|
FAILED_DEPENDENCY
The 424 (Failed Dependency) status code means that the method could not be performed on the resource because
the requested action depended on another action and that action failed.
|
FORBIDDEN
The server understood the request, but is refusing to fulfill it.
|
FOUND
The requested resource resides temporarily under a different URI.
|
GATEWAY_TIMEOUT
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server
specified by the URI (e.g.
|
GONE
The requested resource is no longer available at the server and no forwarding address is known.
|
HTTP_VERSION_NOT_SUPPORTED
The server does not support, or refuses to support, the HTTP protocol version that was used in the request
message.
|
INSUFFICIENT_STORAGE
The 507 (Insufficient Storage) status code means the method could not be performed on the resource because
the server is unable to store the representation needed to successfully complete the request.
|
INTERNAL_SERVER_ERROR
The server encountered an unexpected condition which prevented it from fulfilling the request.
|
LENGTH_REQUIRED
The server refuses to accept the request without a defined Content-Length.
|
LOCKED
The 423 (Locked) status code means the source or destination resource of a method is locked.
|
METHOD_NOT_ALLOWED
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI.
|
MOVED_PERMANENTLY
The requested resource has been assigned a new permanent URI and any future references to this resource
SHOULD use one of the returned URIs.
|
MULTI_STATUS
The 207 (Multi-Status) status code provides status for multiple independent operations (see Section 13 for
more information).
|
MULTIPLE_CHOICES
The requested resource corresponds to any one of a set of representations, each with its own specific
location, and agent-driven negotiation information (section 12) is being provided so that the user (or user
agent) can select a preferred representation and redirect its request to that location.
|
NO_CONTENT
The server has fulfilled the request but does not need to return an entity-body, and might want to return
updated meta information.
|
NON_AUTHORITATIVE_INFORMATION
The returned meta information in the entity-header is not the definitive set as available from the origin
server, but is gathered from a local or a third-party copy.
|
NOT_ACCEPTABLE
The resource identified by the request is only capable of generating response entities which have content
characteristics not acceptable according to the accept headers sent in the request.
|
NOT_FOUND
The server has not found anything matching the Request-URI.
|
NOT_IMPLEMENTED
The server does not support the functionality required to fulfill the request.
|
NOT_MODIFIED
If the client has performed a conditional GET request and access is allowed, but the document has not been
modified, the server SHOULD respond with this status code.
|
OK
The request has succeeded.
|
PARTIAL_CONTENT
The server has fulfilled the partial GET request for the resource.
|
PAYMENT_REQUIRED
This code is reserved for future use.
|
PRECONDITION_FAILED
The precondition given in one or more of the request-header fields evaluated to false when it was tested on
the server.
|
PROXY_AUTHENTICATION
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with
the proxy.
|
REQUEST_ENTITY_TOO_LARGE
The server is refusing to process a request because the request entity is larger than the server is willing
or able to process.
|
REQUEST_TIMEOUT
The client did not produce a request within the time that the server was prepared to wait.
|
REQUEST_URI_TOO_LONG
The server is refusing to service the request because the Request-URI is longer than the server is willing
to interpret.
|
REQUESTED_RANGE_NOT_SATISFIED
A server SHOULD return a response with this status code if a request included a Range request-header field
(section 14.35), and none of the range-specifier values in this field overlap the current extent of the
selected resource, and the request did not include an If-Range request-header field.
|
RESET_CONTENT
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the
request to be sent.
|
SEE_OTHER
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on
that resource.
|
SERVICE_UNAVAILABLE
The server is currently unable to handle the request due to a temporary overloading or maintenance of the
server.
|
SWITCHING_PROTOCOLS
The server understands and is willing to comply with the client's request, via the Upgrade message header field
(section 14.42), for a change in the application protocol being used on this connection.
|
TEMPORARY_REDIRECT
The requested resource resides temporarily under a different URI.
|
TOO_MANY_REQUESTS
429 Too Many Requests (RFC6585)
|
UNAUTHORIZED
The request requires user authentication.
|
UNPROCESSABLE_ENTITY
The 422 (Unprocessable Entity) status code means the server understands the content type of the request
entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request
entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the
contained instructions.
|
UNSUPPORTED_MEDIA_TYPE
The server is refusing to service the request because the entity of the request is in a format not supported
by the requested resource for the requested method.
|
USE_PROXY
The requested resource MUST be accessed through the proxy given by the Location field.
|
| Modifier and Type | Method and Description |
|---|---|
int |
getStatus() |
static RestStatus |
readFrom(StreamInput in) |
static RestStatus |
status(int successfulShards,
int totalShards,
ShardOperationFailedException... failures) |
static RestStatus |
valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name.
|
static RestStatus[] |
values()
Returns an array containing the constants of this enum type, in
the order they are declared.
|
static void |
writeTo(StreamOutput out,
RestStatus status) |
public static final RestStatus CONTINUE
public static final RestStatus SWITCHING_PROTOCOLS
public static final RestStatus OK
public static final RestStatus CREATED
A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19.
public static final RestStatus ACCEPTED
The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.
public static final RestStatus NON_AUTHORITATIVE_INFORMATION
public static final RestStatus NO_CONTENT
If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated meta information SHOULD be applied to the document currently in the user agent's active view.
The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
public static final RestStatus RESET_CONTENT
public static final RestStatus PARTIAL_CONTENT
The response MUST include the following header fields:
If the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see 13.5.4.
A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.
public static final RestStatus MULTI_STATUS
A Multi-Status response conveys information about multiple resources in situations where multiple status codes might be appropriate. The default Multi-Status response body is a text/xml or application/xml HTTP entity with a 'multistatus' root element. Further elements contain 200, 300, 400, and 500 series status codes generated during the method invocation. 100 series status codes SHOULD NOT be recorded in a 'response' XML element.
Although '207' is used as the overall response status code, the recipient needs to consult the contents of the multistatus response body for further information about the success or failure of the method execution. The response MAY be used in success, partial success and also in failure situations.
The 'multistatus' root element holds zero or more 'response' elements in any order, each with information about an individual resource. Each 'response' element MUST have an 'href' element to identify the resource.
public static final RestStatus MULTIPLE_CHOICES
Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
If the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
public static final RestStatus MOVED_PERMANENTLY
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
public static final RestStatus FOUND
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
public static final RestStatus SEE_OTHER
The different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
public static final RestStatus NOT_MODIFIED
The response MUST include the following header fields:
If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.
public static final RestStatus USE_PROXY
public static final RestStatus TEMPORARY_REDIRECT
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.
If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
public static final RestStatus BAD_REQUEST
public static final RestStatus UNAUTHORIZED
public static final RestStatus PAYMENT_REQUIRED
public static final RestStatus FORBIDDEN
public static final RestStatus NOT_FOUND
public static final RestStatus METHOD_NOT_ALLOWED
public static final RestStatus NOT_ACCEPTABLE
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable.
If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.
public static final RestStatus PROXY_AUTHENTICATION
public static final RestStatus REQUEST_TIMEOUT
public static final RestStatus CONFLICT
Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.
public static final RestStatus GONE
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner.
public static final RestStatus LENGTH_REQUIRED
public static final RestStatus PRECONDITION_FAILED
public static final RestStatus REQUEST_ENTITY_TOO_LARGE
If the condition is temporary, the server SHOULD include a Retry-After header field to indicate that it is temporary and after what time the client MAY try again.
public static final RestStatus REQUEST_URI_TOO_LONG
public static final RestStatus UNSUPPORTED_MEDIA_TYPE
public static final RestStatus REQUESTED_RANGE_NOT_SATISFIED
When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content-type.
public static final RestStatus EXPECTATION_FAILED
public static final RestStatus UNPROCESSABLE_ENTITY
public static final RestStatus LOCKED
public static final RestStatus FAILED_DEPENDENCY
public static final RestStatus TOO_MANY_REQUESTS
public static final RestStatus INTERNAL_SERVER_ERROR
public static final RestStatus NOT_IMPLEMENTED
public static final RestStatus BAD_GATEWAY
public static final RestStatus SERVICE_UNAVAILABLE
public static final RestStatus GATEWAY_TIMEOUT
public static final RestStatus HTTP_VERSION_NOT_SUPPORTED
public static final RestStatus INSUFFICIENT_STORAGE
public static RestStatus[] values()
for (RestStatus c : RestStatus.values()) System.out.println(c);
public static RestStatus valueOf(java.lang.String name)
name
- the name of the enum constant to be returned.java.lang.IllegalArgumentException
- if this enum type has no constant with the specified namejava.lang.NullPointerException
- if the argument is nullpublic int getStatus()
public static RestStatus readFrom(StreamInput in) throws java.io.IOException
java.io.IOException
public static void writeTo(StreamOutput out, RestStatus status) throws java.io.IOException
java.io.IOException
public static RestStatus status(int successfulShards, int totalShards, ShardOperationFailedException... failures)


Restart Applications
Application:
Select Application
fpgaManager.js
syncclient.js
cloudclient.js
reboot now
Station:
Particular Station
All Stations
Select Station:
Restart
Transaction_Create