| /usr/local/lib/python2.7/dist-packages/MySQLdb/__init__ |
43 |
11 |
0 |
74% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/connections |
149 |
42 |
0 |
72% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/constants/CLIENT |
18 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/constants/FIELD_TYPE |
29 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/constants/FLAG |
16 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/constants/__init__ |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/converters |
58 |
29 |
0 |
50% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/cursors |
276 |
125 |
0 |
55% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/release |
3 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/MySQLdb/times |
87 |
64 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/_mysql_exceptions |
15 |
2 |
0 |
87% |
| /usr/local/lib/python2.7/dist-packages/appdirs |
250 |
219 |
0 |
12% |
| /usr/local/lib/python2.7/dist-packages/django/__init__ |
9 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/apps/__init__ |
2 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/apps/config |
84 |
21 |
0 |
75% |
| /usr/local/lib/python2.7/dist-packages/django/apps/registry |
186 |
75 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/conf/__init__ |
87 |
29 |
0 |
67% |
| /usr/local/lib/python2.7/dist-packages/django/conf/global_settings |
136 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/conf/locale/__init__ |
2 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/conf/urls/__init__ |
48 |
17 |
0 |
65% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/__init__ |
10 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/actions |
36 |
26 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/apps |
13 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/checks |
401 |
212 |
0 |
47% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/decorators |
12 |
11 |
0 |
8% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/exceptions |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/filters |
197 |
132 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/helpers |
225 |
161 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/migrations/0001_initial |
7 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/migrations/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/models |
57 |
21 |
0 |
63% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/options |
993 |
768 |
0 |
23% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/sites |
228 |
132 |
0 |
42% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/templatetags/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/templatetags/admin_static |
10 |
5 |
0 |
50% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/templatetags/admin_urls |
38 |
28 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/utils |
298 |
240 |
0 |
19% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/validation |
258 |
214 |
0 |
17% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/admin/widgets |
238 |
164 |
0 |
31% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/__init__ |
110 |
82 |
0 |
25% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/admin |
102 |
50 |
0 |
51% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/apps |
12 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/backends |
80 |
61 |
0 |
24% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/checks |
16 |
11 |
0 |
31% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/context_processors |
31 |
14 |
0 |
55% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/decorators |
38 |
28 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/forms |
178 |
100 |
0 |
44% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/hashers |
244 |
157 |
0 |
36% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/management/__init__ |
88 |
41 |
0 |
53% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/middleware |
50 |
32 |
0 |
36% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/0001_initial |
8 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/0002_alter_permission_name_max_length |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/0003_alter_user_email_max_length |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/0004_alter_user_username_opts |
6 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/0005_alter_user_last_login_null |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/0006_require_contenttypes_0002 |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/migrations/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/models |
249 |
108 |
0 |
57% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/signals |
4 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/auth/tokens |
34 |
22 |
0 |
35% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/__init__ |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/admin |
55 |
32 |
0 |
42% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/apps |
12 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/checks |
10 |
6 |
0 |
40% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/fields |
312 |
248 |
0 |
21% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/forms |
38 |
28 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/management |
37 |
18 |
0 |
51% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/migrations/0001_initial |
6 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/migrations/0002_remove_content_type_name |
13 |
7 |
0 |
46% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/migrations/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/models |
116 |
59 |
0 |
49% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/contenttypes/views |
53 |
45 |
0 |
15% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/__init__ |
3 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/api |
37 |
20 |
0 |
46% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/apps |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/constants |
7 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/context_processors |
4 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/middleware |
11 |
1 |
0 |
91% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/storage/__init__ |
4 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/storage/base |
84 |
47 |
0 |
44% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/storage/cookie |
83 |
60 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/storage/fallback |
29 |
18 |
0 |
38% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/storage/session |
23 |
10 |
0 |
57% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/messages/utils |
6 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/__init__ |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/apps |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/backends/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/backends/base |
184 |
106 |
0 |
42% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/backends/db |
53 |
37 |
0 |
30% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/exceptions |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/management/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/middleware |
34 |
12 |
0 |
65% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/migrations/0001_initial |
6 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/migrations/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/models |
29 |
8 |
0 |
72% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sessions/serializers |
11 |
4 |
0 |
64% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sites/__init__ |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sites/requests |
12 |
4 |
0 |
67% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/sites/shortcuts |
8 |
5 |
0 |
38% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/staticfiles/__init__ |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/staticfiles/apps |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/contrib/staticfiles/management/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/cache/__init__ |
72 |
23 |
0 |
68% |
| /usr/local/lib/python2.7/dist-packages/django/core/cache/backends/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/cache/backends/base |
108 |
57 |
0 |
47% |
| /usr/local/lib/python2.7/dist-packages/django/core/cache/backends/db |
133 |
110 |
0 |
17% |
| /usr/local/lib/python2.7/dist-packages/django/core/cache/backends/locmem |
109 |
82 |
0 |
25% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/__init__ |
9 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/compatibility/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/compatibility/django_1_7_0 |
11 |
7 |
0 |
36% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/messages |
54 |
21 |
0 |
61% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/model_checks |
28 |
19 |
0 |
32% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/registry |
51 |
15 |
0 |
71% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/security/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/security/base |
48 |
22 |
0 |
54% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/security/csrf |
16 |
7 |
0 |
56% |
| /usr/local/lib/python2.7/dist-packages/django/core/checks/security/sessions |
36 |
20 |
0 |
44% |
| /usr/local/lib/python2.7/dist-packages/django/core/exceptions |
87 |
47 |
0 |
46% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/__init__ |
2 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/base |
119 |
80 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/images |
43 |
34 |
0 |
21% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/locks |
57 |
46 |
0 |
19% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/move |
37 |
31 |
0 |
16% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/storage |
166 |
115 |
0 |
31% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/temp |
35 |
28 |
0 |
20% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/uploadedfile |
60 |
33 |
0 |
45% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/uploadhandler |
78 |
42 |
0 |
46% |
| /usr/local/lib/python2.7/dist-packages/django/core/files/utils |
19 |
1 |
0 |
95% |
| /usr/local/lib/python2.7/dist-packages/django/core/handlers/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/handlers/base |
155 |
72 |
0 |
54% |
| /usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi |
161 |
73 |
0 |
55% |
| /usr/local/lib/python2.7/dist-packages/django/core/mail/__init__ |
33 |
22 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/core/mail/message |
252 |
192 |
0 |
24% |
| /usr/local/lib/python2.7/dist-packages/django/core/mail/utils |
9 |
4 |
0 |
56% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/__init__ |
160 |
78 |
0 |
51% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/base |
250 |
118 |
0 |
53% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/color |
29 |
2 |
0 |
93% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/commands/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/commands/createcachetable |
61 |
40 |
0 |
34% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/commands/flush |
59 |
11 |
0 |
81% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/commands/loaddata |
181 |
70 |
0 |
61% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate |
197 |
77 |
0 |
61% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/commands/test |
49 |
6 |
0 |
88% |
| /usr/local/lib/python2.7/dist-packages/django/core/management/sql |
155 |
115 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/django/core/paginator |
90 |
57 |
0 |
37% |
| /usr/local/lib/python2.7/dist-packages/django/core/serializers/__init__ |
108 |
23 |
0 |
79% |
| /usr/local/lib/python2.7/dist-packages/django/core/serializers/base |
90 |
33 |
0 |
63% |
| /usr/local/lib/python2.7/dist-packages/django/core/serializers/json |
76 |
36 |
0 |
53% |
| /usr/local/lib/python2.7/dist-packages/django/core/serializers/python |
96 |
64 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/core/serializers/pyyaml |
40 |
36 |
0 |
10% |
| /usr/local/lib/python2.7/dist-packages/django/core/serializers/xml_serializer |
212 |
165 |
0 |
22% |
| /usr/local/lib/python2.7/dist-packages/django/core/servers/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/servers/basehttp |
106 |
76 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/core/signals |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/core/signing |
90 |
57 |
0 |
37% |
| /usr/local/lib/python2.7/dist-packages/django/core/urlresolvers |
379 |
115 |
0 |
70% |
| /usr/local/lib/python2.7/dist-packages/django/core/validators |
194 |
86 |
0 |
56% |
| /usr/local/lib/python2.7/dist-packages/django/core/wsgi |
5 |
2 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/db/__init__ |
26 |
6 |
0 |
77% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/base |
225 |
42 |
0 |
81% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/client |
6 |
1 |
0 |
83% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/creation |
285 |
184 |
0 |
35% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/features |
97 |
8 |
0 |
92% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/introspection |
75 |
35 |
0 |
53% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/operations |
179 |
85 |
0 |
53% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema |
413 |
157 |
0 |
62% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/base/validation |
14 |
8 |
0 |
43% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/base |
171 |
49 |
0 |
71% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/client |
33 |
27 |
0 |
18% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/compiler |
15 |
4 |
0 |
73% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/creation |
27 |
17 |
0 |
37% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/features |
46 |
13 |
0 |
72% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/introspection |
87 |
65 |
0 |
25% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/operations |
126 |
70 |
0 |
44% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/schema |
33 |
4 |
0 |
88% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/mysql/validation |
13 |
9 |
0 |
31% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/signals |
2 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/backends/utils |
128 |
82 |
0 |
36% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/__init__ |
2 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/autodetector |
538 |
494 |
0 |
8% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/executor |
122 |
57 |
0 |
53% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/graph |
141 |
44 |
0 |
69% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/loader |
191 |
78 |
0 |
59% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/migration |
82 |
32 |
0 |
61% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/__init__ |
4 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/base |
31 |
9 |
0 |
71% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/fields |
163 |
67 |
0 |
59% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/models |
290 |
165 |
0 |
43% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/special |
117 |
76 |
0 |
35% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/optimizer |
99 |
75 |
0 |
24% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/questioner |
103 |
77 |
0 |
25% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/recorder |
37 |
4 |
0 |
89% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/state |
303 |
130 |
0 |
57% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/topological_sort |
15 |
13 |
0 |
13% |
| /usr/local/lib/python2.7/dist-packages/django/db/migrations/writer |
291 |
247 |
0 |
15% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/__init__ |
35 |
8 |
0 |
77% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/aggregates |
87 |
44 |
0 |
49% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/base |
819 |
546 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/constants |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/deletion |
167 |
141 |
0 |
16% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/expressions |
573 |
353 |
0 |
38% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__ |
1320 |
705 |
0 |
47% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/fields/files |
253 |
174 |
0 |
31% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/fields/proxy |
10 |
6 |
0 |
40% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/fields/related |
1295 |
795 |
0 |
39% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/fields/subclassing |
24 |
15 |
0 |
38% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/lookups |
333 |
142 |
0 |
57% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/manager |
149 |
21 |
0 |
86% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/options |
387 |
107 |
0 |
72% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/query |
917 |
604 |
0 |
34% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/query_utils |
135 |
99 |
0 |
27% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/signals |
43 |
15 |
0 |
65% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/__init__ |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/compiler |
643 |
347 |
0 |
46% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/constants |
11 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/datastructures |
65 |
17 |
0 |
74% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/query |
1066 |
624 |
0 |
41% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/subqueries |
104 |
68 |
0 |
35% |
| /usr/local/lib/python2.7/dist-packages/django/db/models/sql/where |
243 |
165 |
0 |
32% |
| /usr/local/lib/python2.7/dist-packages/django/db/transaction |
121 |
53 |
0 |
56% |
| /usr/local/lib/python2.7/dist-packages/django/db/utils |
217 |
77 |
0 |
65% |
| /usr/local/lib/python2.7/dist-packages/django/dispatch/__init__ |
1 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/dispatch/dispatcher |
140 |
39 |
0 |
72% |
| /usr/local/lib/python2.7/dist-packages/django/dispatch/weakref_backports |
40 |
18 |
0 |
55% |
| /usr/local/lib/python2.7/dist-packages/django/forms/__init__ |
6 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/forms/fields |
723 |
493 |
0 |
32% |
| /usr/local/lib/python2.7/dist-packages/django/forms/forms |
354 |
264 |
0 |
25% |
| /usr/local/lib/python2.7/dist-packages/django/forms/formsets |
223 |
160 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/forms/models |
672 |
497 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/django/forms/utils |
98 |
58 |
0 |
41% |
| /usr/local/lib/python2.7/dist-packages/django/forms/widgets |
508 |
305 |
0 |
40% |
| /usr/local/lib/python2.7/dist-packages/django/http/__init__ |
5 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/http/cookie |
62 |
38 |
0 |
39% |
| /usr/local/lib/python2.7/dist-packages/django/http/multipartparser |
364 |
307 |
0 |
16% |
| /usr/local/lib/python2.7/dist-packages/django/http/request |
312 |
200 |
0 |
36% |
| /usr/local/lib/python2.7/dist-packages/django/http/response |
259 |
110 |
0 |
58% |
| /usr/local/lib/python2.7/dist-packages/django/http/utils |
15 |
8 |
0 |
47% |
| /usr/local/lib/python2.7/dist-packages/django/middleware/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/middleware/cache |
72 |
60 |
0 |
17% |
| /usr/local/lib/python2.7/dist-packages/django/middleware/clickjacking |
11 |
2 |
0 |
82% |
| /usr/local/lib/python2.7/dist-packages/django/middleware/common |
74 |
43 |
0 |
42% |
| /usr/local/lib/python2.7/dist-packages/django/middleware/csrf |
84 |
42 |
0 |
50% |
| /usr/local/lib/python2.7/dist-packages/django/middleware/security |
28 |
8 |
0 |
71% |
| /usr/local/lib/python2.7/dist-packages/django/shortcuts |
76 |
53 |
0 |
30% |
| /usr/local/lib/python2.7/dist-packages/django/template/__init__ |
10 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/template/backends/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/template/backends/base |
30 |
13 |
0 |
57% |
| /usr/local/lib/python2.7/dist-packages/django/template/backends/django |
34 |
12 |
0 |
65% |
| /usr/local/lib/python2.7/dist-packages/django/template/base |
785 |
505 |
0 |
36% |
| /usr/local/lib/python2.7/dist-packages/django/template/context |
149 |
59 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/template/context_processors |
35 |
17 |
0 |
51% |
| /usr/local/lib/python2.7/dist-packages/django/template/defaultfilters |
461 |
331 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/template/defaulttags |
659 |
533 |
0 |
19% |
| /usr/local/lib/python2.7/dist-packages/django/template/engine |
144 |
49 |
0 |
66% |
| /usr/local/lib/python2.7/dist-packages/django/template/loader |
73 |
49 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/template/loader_tags |
155 |
124 |
0 |
20% |
| /usr/local/lib/python2.7/dist-packages/django/template/loaders/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/template/loaders/app_directories |
24 |
2 |
0 |
92% |
| /usr/local/lib/python2.7/dist-packages/django/template/loaders/base |
20 |
4 |
0 |
80% |
| /usr/local/lib/python2.7/dist-packages/django/template/loaders/filesystem |
28 |
10 |
0 |
64% |
| /usr/local/lib/python2.7/dist-packages/django/template/loaders/locmem |
12 |
6 |
0 |
50% |
| /usr/local/lib/python2.7/dist-packages/django/template/response |
90 |
63 |
0 |
30% |
| /usr/local/lib/python2.7/dist-packages/django/template/smartif |
108 |
63 |
0 |
42% |
| /usr/local/lib/python2.7/dist-packages/django/template/utils |
68 |
9 |
0 |
87% |
| /usr/local/lib/python2.7/dist-packages/django/test/__init__ |
11 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/test/client |
315 |
161 |
0 |
49% |
| /usr/local/lib/python2.7/dist-packages/django/test/html |
166 |
128 |
0 |
23% |
| /usr/local/lib/python2.7/dist-packages/django/test/runner |
215 |
49 |
0 |
77% |
| /usr/local/lib/python2.7/dist-packages/django/test/signals |
96 |
71 |
0 |
26% |
| /usr/local/lib/python2.7/dist-packages/django/test/testcases |
636 |
434 |
0 |
32% |
| /usr/local/lib/python2.7/dist-packages/django/test/utils |
334 |
227 |
0 |
32% |
| /usr/local/lib/python2.7/dist-packages/django/utils/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/utils/_os |
60 |
24 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/utils/baseconv |
48 |
25 |
0 |
48% |
| /usr/local/lib/python2.7/dist-packages/django/utils/cache |
133 |
104 |
0 |
22% |
| /usr/local/lib/python2.7/dist-packages/django/utils/crypto |
87 |
63 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/utils/datastructures |
319 |
169 |
0 |
47% |
| /usr/local/lib/python2.7/dist-packages/django/utils/dateformat |
184 |
124 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/utils/dateparse |
50 |
33 |
0 |
34% |
| /usr/local/lib/python2.7/dist-packages/django/utils/dates |
9 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/utils/datetime_safe |
58 |
42 |
0 |
28% |
| /usr/local/lib/python2.7/dist-packages/django/utils/deconstruct |
25 |
9 |
0 |
64% |
| /usr/local/lib/python2.7/dist-packages/django/utils/decorators |
75 |
37 |
0 |
51% |
| /usr/local/lib/python2.7/dist-packages/django/utils/deprecation |
38 |
5 |
0 |
87% |
| /usr/local/lib/python2.7/dist-packages/django/utils/duration |
14 |
13 |
0 |
7% |
| /usr/local/lib/python2.7/dist-packages/django/utils/encoding |
116 |
43 |
0 |
63% |
| /usr/local/lib/python2.7/dist-packages/django/utils/formats |
125 |
100 |
0 |
20% |
| /usr/local/lib/python2.7/dist-packages/django/utils/functional |
231 |
102 |
0 |
56% |
| /usr/local/lib/python2.7/dist-packages/django/utils/html |
200 |
137 |
0 |
32% |
| /usr/local/lib/python2.7/dist-packages/django/utils/html_parser |
90 |
80 |
0 |
11% |
| /usr/local/lib/python2.7/dist-packages/django/utils/http |
138 |
84 |
0 |
39% |
| /usr/local/lib/python2.7/dist-packages/django/utils/ipv6 |
108 |
99 |
0 |
8% |
| /usr/local/lib/python2.7/dist-packages/django/utils/itercompat |
6 |
5 |
0 |
17% |
| /usr/local/lib/python2.7/dist-packages/django/utils/log |
67 |
28 |
0 |
58% |
| /usr/local/lib/python2.7/dist-packages/django/utils/lorem_ipsum |
31 |
22 |
0 |
29% |
| /usr/local/lib/python2.7/dist-packages/django/utils/lru_cache |
106 |
19 |
0 |
82% |
| /usr/local/lib/python2.7/dist-packages/django/utils/module_loading |
101 |
36 |
0 |
64% |
| /usr/local/lib/python2.7/dist-packages/django/utils/numberformat |
34 |
29 |
0 |
15% |
| /usr/local/lib/python2.7/dist-packages/django/utils/regex_helper |
188 |
131 |
0 |
30% |
| /usr/local/lib/python2.7/dist-packages/django/utils/safestring |
63 |
28 |
0 |
56% |
| /usr/local/lib/python2.7/dist-packages/django/utils/six |
442 |
197 |
0 |
55% |
| /usr/local/lib/python2.7/dist-packages/django/utils/synch |
56 |
39 |
0 |
30% |
| /usr/local/lib/python2.7/dist-packages/django/utils/termcolors |
57 |
22 |
0 |
61% |
| /usr/local/lib/python2.7/dist-packages/django/utils/text |
242 |
177 |
0 |
27% |
| /usr/local/lib/python2.7/dist-packages/django/utils/timesince |
30 |
22 |
0 |
27% |
| /usr/local/lib/python2.7/dist-packages/django/utils/timezone |
147 |
92 |
0 |
37% |
| /usr/local/lib/python2.7/dist-packages/django/utils/translation/__init__ |
119 |
48 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/utils/translation/trans_real |
419 |
274 |
0 |
35% |
| /usr/local/lib/python2.7/dist-packages/django/utils/tree |
52 |
21 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/utils/version |
42 |
17 |
0 |
60% |
| /usr/local/lib/python2.7/dist-packages/django/utils/xmlutils |
9 |
6 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/views/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/views/debug |
330 |
276 |
0 |
16% |
| /usr/local/lib/python2.7/dist-packages/django/views/decorators/__init__ |
0 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/django/views/decorators/cache |
27 |
18 |
0 |
33% |
| /usr/local/lib/python2.7/dist-packages/django/views/decorators/csrf |
27 |
5 |
0 |
81% |
| /usr/local/lib/python2.7/dist-packages/django/views/decorators/debug |
21 |
13 |
0 |
38% |
| /usr/local/lib/python2.7/dist-packages/django/views/static |
73 |
57 |
0 |
22% |
| /usr/local/lib/python2.7/dist-packages/packaging/__about__ |
10 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/packaging/__init__ |
3 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/packaging/_compat |
12 |
1 |
0 |
92% |
| /usr/local/lib/python2.7/dist-packages/packaging/_structures |
41 |
17 |
0 |
59% |
| /usr/local/lib/python2.7/dist-packages/packaging/markers |
130 |
73 |
0 |
44% |
| /usr/local/lib/python2.7/dist-packages/packaging/requirements |
72 |
25 |
0 |
65% |
| /usr/local/lib/python2.7/dist-packages/packaging/specifiers |
284 |
202 |
0 |
29% |
| /usr/local/lib/python2.7/dist-packages/packaging/version |
150 |
40 |
0 |
73% |
| /usr/local/lib/python2.7/dist-packages/pkg_resources/__init__ |
1508 |
901 |
0 |
40% |
| /usr/local/lib/python2.7/dist-packages/pyparsing |
2527 |
1442 |
0 |
43% |
| /usr/local/lib/python2.7/dist-packages/pytz/__init__ |
181 |
109 |
0 |
40% |
| /usr/local/lib/python2.7/dist-packages/pytz/exceptions |
6 |
0 |
0 |
100% |
| /usr/local/lib/python2.7/dist-packages/pytz/lazy |
97 |
56 |
0 |
42% |
| /usr/local/lib/python2.7/dist-packages/pytz/tzfile |
81 |
68 |
0 |
16% |
| /usr/local/lib/python2.7/dist-packages/pytz/tzinfo |
178 |
126 |
0 |
29% |
| /usr/local/lib/python2.7/dist-packages/six |
444 |
203 |
0 |
54% |
| Election/__init__ |
0 |
0 |
0 |
100% |
| Election/admin |
1 |
0 |
0 |
100% |
| Election/migrations/0001_initial |
5 |
0 |
0 |
100% |
| Election/migrations/__init__ |
0 |
0 |
0 |
100% |
| Election/models |
27 |
0 |
0 |
100% |
| Election/tests |
56 |
0 |
0 |
100% |
| Election/urls |
4 |
0 |
0 |
100% |
| Election/views |
324 |
269 |
0 |
17% |
| Election_portal/__init__ |
0 |
0 |
0 |
100% |
| Election_portal/settings |
18 |
0 |
0 |
100% |
| Election_portal/urls |
3 |
0 |
0 |
100% |
| manage |
6 |
0 |
0 |
100% |


You can download a .zip
containing all of the packages mentioned below here.
The easiest way to single-handedly make a block of code more readable is to align its contents, whether it's the values of a hash or the equals signs initializing a handful of variables at the beginning of a method. However, it's a pain the butt (and frankly not worth the time) to manually go through line-by-line adding the right spacing. With the Sublime alignment package, you can simply select the parts of the lines you want to be aligned and hold down cmd + ctrl + a
to achieve the same result. (In the short recorded example to the right, I held down the opt
button while dragging my mouse along the beginning of each line to select the relevant lines even faster.)
Thanks to John Backus for sharing this package with me.
Extends Sublime's autocompletion to find matches in all open files.
Auto-replaces obvious spelling mistakes in .md
and .txt
files.
Highlights or underlines the innermost brackets of the code you're currently editing. You can see it in action in the alignment video above.
Enables you to run quick diffs between any combination of open tabs, your clipboard, and files from the current project.
Quickly fold all comments in the current document.
Small, unobtrusive symbols to the left gutter of Sublime indicate the lines' git status (if you are in a git repository).
Allows you to split Sublime into panes however you like with simple keyboard shortcuts. You can find my custom key bindings below, which include extensions to Origami's default shortcuts.
Enables quick viewing and editing of all your packages. It's a bit shocking that this doesn't come with Sublime by default; without this, you have to manually go through the bowels of your file system to find any .tmLanguage
, .sublime-package
, etc. files that you wanted to edit. In contrast, this plugin gives you fuzzy search over all of these packages directly from Sublime. In short –– it's great!
Executes Ruby code and updates # =>
markers with the results. This one is particularly useful for demoing features of the language or testing the output of little scripts as you write them. If you've ever seen Ruby Tapas (and if you haven't, you should!!!!), Avdi uses xmpfilter
and rcodetools
with Emacs to get this same behavior for his mini tutorials.
Note that you may have to change the package settings from "ruby_manager": "auto"
to "ruby_manager": "rvm"
in order to get this to work.
Thanks to John Backus for sharing this package with me.
These two packages enable you to quickly cycle through color schemes and themes (respectively) from any file rather than having to open your preferences file, manually update their file paths, switch back to your original open file to see the changes, and repeat each time you want to test out a new style. These packages aren't so critical for long-term use (I haven't changed my theme in months, and I don't plan on doing so in the near future), but they are really nice when you are first setting up your coding environment.


Daytwo
Evening update
The heart pump (Impella) has successfully been removed and Gary is doing very well. The doctors believe he is making great progress and doing well without the heart pump.
Gary is able to answer direct questions by blinking and nodding. Vitals are improving and we are hopeful that he will have the intubation tube removed within the next few days.
The doctors have decided to sedate him for the night so he can relax post-procedure. For the rest of this evening and throughout the day tomorrow, they’re primary goal is to increase the dialysis fluid removal rate.
Morning update
Last night, a procedure was done to remove some more fluid from Gary’s lungs.
He is slightly more coherent and has shown, by nodding his head and blinking his eyes, that he recognizes Kimberly.
The heart pump is still scheduled to be removed later today, so we will provide another update after that procedure.


Interface to the Xethru X4M300 Application module This interface is used to control the XeThru X4M300 module. More...
#include <X4M300.hpp>
Public Member Functions | |
| X4M300 (LockedRadarInterfacePtr &radar_interface) | |
| Constructor. More... | |
| ~X4M300 () | |
| Destructor. More... | |
| int | set_debug_level (unsigned char level) |
| Sets debug level in the Xethru module. More... | |
| int | set_baudrate (uint32_t baudrate) |
| Set baudrate for serial communication during ModuleConnector operation. More... | |
| int | ping (uint32_t *pong_value) |
| Make sure there is a connection to FW on the Xethru X4M300 module. More... | |
| int | get_system_info (const uint8_t info_code, std::string *system_info) |
| Returns a string containing system information given by infocode: XTID_SSIC_ITEMNUMBER = 0x00 -> Returns the product Item Number, including revision. This is programmed in Flash during manufacturing XTID_SSIC_ORDERCODE = 0x01 -> Returns the product order code XTID_SSIC_FIRMWAREID = 0x02 -> Returns the installed Firmware ID. As viewed from the "highest" level of the software, "X4M300" XTID_SSIC_VERSION = 0x03 -> Returns the installed Firmware Version. As viewed from the "highest" level of the software XTID_SSIC_BUILD = 0x04 -> Returns information of the SW Build installed on the device XTID_SSIC_SERIALNUMBER = 0x06 -> Returns the product serial number XTID_SSIC_VERSIONLIST = 0x07 ->Returns ID and version of all components. Calls all components and compound a string E.g. "X4M300:<IP_ADDRESS>;XEP:<IP_ADDRESS>;X4C51:<IP_ADDRESS>;DSP:<IP_ADDRESS>". More... | |
| int | reset () |
| Resets and restart the module. More... | |
| int | module_reset () |
| Resets the module. More... | |
| int | reset_to_factory_preset () |
| Resets all parameters in the module to factory presets. More... | |
| int | start_bootloader () |
| Enters the bootloader for FW upgrades. More... | |
| int | system_run_test (const uint8_t testcode, Bytes *data) |
| Runs the different manufacturing tests identified by testcode. More... | |
| int | load_profile (const uint32_t profileid) |
| Loads the profile given by profileid. More... | |
| int | set_sensor_mode (const uint8_t mode, const uint8_t param) |
| Control the execution mode of the sensor. More... | |
| int | set_sensitivity (const uint32_t sensitivity) |
| Sets the overall sensitivity. More... | |
| int | set_detection_zone (const float start, const float end) |
| Sets the current detection zone. More... | |
| int | get_detection_zone (float *start, float *end) |
| Returns the actual detection zone. More... | |
| int | get_detection_zone_limits (float *min, float *max, float *step) |
| Returns the potential settings of detection zone from the module. More... | |
| int | set_led_control (const uint8_t mode, uint8_t intensity) |
| This command configures the LED mode. More... | |
| int | set_output_control (const uint32_t output_feature, const uint32_t output_control) |
| Control module profile output. More... | |
| int | peek_message_presence_single () |
| Return number of PresenceSingleData messages available in queue. More... | |
| int | read_message_presence_single (PresenceSingleData *presence_single) |
| Read a single PresenceSingleData item from the queue. More... | |
| int | peek_message_presence_movinglist () |
| Return number of PresenceMovingListData messages available in queue. More... | |
| int | read_message_presence_movinglist (PresenceMovingListData *presence_moving_list) |
| Read a single PresenceMovingListData item from the queue. More... | |
| int | peek_message_baseband_ap () |
| Return number of BasebandApData messages available in queue. More... | |
| int | read_message_baseband_ap (BasebandApData *baseband_ap) |
| Read a single BasebandApData item from the queue. More... | |
| int | peek_message_baseband_iq () |
| Return number of BasebandIqData messages available in queue. More... | |
| int | read_message_baseband_iq (BasebandIqData *baseband_iq) |
| Read a single BasebandIqData item from the queue. More... | |
Interface to the Xethru X4M300 Application module This interface is used to control the XeThru X4M300 module.
See the data sheet of the X4M300 module for more information on the X4M300 module.
| XeThru::X4M300::X4M300 | ( | LockedRadarInterfacePtr & | radar_interface | ) |
Constructor.
| [in] | radar_interface | internal object used to interface the radar |
| XeThru::X4M300::~X4M300 | ( | ) |
Destructor.
| int XeThru::X4M300::get_detection_zone | ( | float * | start, |
| float * | end | ||
| ) |
Returns the actual detection zone.
| [out] | start | start of detection zone in meters |
| [out] | end | end of detection zone in meters |
| int XeThru::X4M300::get_detection_zone_limits | ( | float * | min, |
| float * | max, | ||
| float * | step | ||
| ) |
Returns the potential settings of detection zone from the module.
| [out] | min | smallest value for detection zone start |
| [out] | max | largest value for detection zone end |
| [out] | step | detection zone start and end step size |
| int XeThru::X4M300::get_system_info | ( | const uint8_t | info_code, |
| std::string * | system_info | ||
| ) |
Returns a string containing system information given by infocode:
XTID_SSIC_ITEMNUMBER = 0x00 -> Returns the product Item Number, including revision. This is programmed in Flash during manufacturing
XTID_SSIC_ORDERCODE = 0x01 -> Returns the product order code
XTID_SSIC_FIRMWAREID = 0x02 -> Returns the installed Firmware ID. As viewed from the "highest" level of the software, "X4M300"
XTID_SSIC_VERSION = 0x03 -> Returns the installed Firmware Version. As viewed from the "highest" level of the software
XTID_SSIC_BUILD = 0x04 -> Returns information of the SW Build installed on the device
XTID_SSIC_SERIALNUMBER = 0x06 -> Returns the product serial number
XTID_SSIC_VERSIONLIST = 0x07 ->Returns ID and version of all components. Calls all components and compound a string E.g. "X4M300:<IP_ADDRESS>;XEP:<IP_ADDRESS>;X4C51:<IP_ADDRESS>;DSP:<IP_ADDRESS>".
| int XeThru::X4M300::load_profile | ( | const uint32_t | profileid | ) |
Loads the profile given by profileid.
If another profile is already loaded, the other profile is unloaded before the new profile is loaded. The profile does not start, the module remains idle.
profileid = 0x014d4ab8 : presence profile
| [in] | profileid | the id of the profile to load |
| int XeThru::X4M300::module_reset | ( | ) |
Resets the module.
The client must perform a close and then an open on the ModuleConnector to reeastablish connection.
| int XeThru::X4M300::peek_message_baseband_ap | ( | ) |
Return number of BasebandApData messages available in queue.
| int XeThru::X4M300::peek_message_baseband_iq | ( | ) |
Return number of BasebandIqData messages available in queue.
| int XeThru::X4M300::peek_message_presence_movinglist | ( | ) |
Return number of PresenceMovingListData messages available in queue.
| int XeThru::X4M300::peek_message_presence_single | ( | ) |
Return number of PresenceSingleData messages available in queue.
| int XeThru::X4M300::ping | ( | uint32_t * | pong_value | ) |
Make sure there is a connection to FW on the Xethru X4M300 module.
| int XeThru::X4M300::read_message_baseband_ap | ( | BasebandApData * | baseband_ap | ) |
Read a single BasebandApData item from the queue.
Blocks if queue is empty.
| [out] | baseband_ap | pointer to returned BasebandApData item |
| int XeThru::X4M300::read_message_baseband_iq | ( | BasebandIqData * | baseband_iq | ) |
Read a single BasebandIqData item from the queue.
Blocks if queue is empty.
| [out] | baseband_iq | pointer to returned BasebandIqData item |
| int XeThru::X4M300::read_message_presence_movinglist | ( | PresenceMovingListData * | presence_moving_list | ) |
Read a single PresenceMovingListData item from the queue.
Blocks if queue is empty.
| [in] | presence_moving_list | pointer to returned PresenceMovingListData item |
| int XeThru::X4M300::read_message_presence_single | ( | PresenceSingleData * | presence_single | ) |
Read a single PresenceSingleData item from the queue.
Blocks if queue is empty.
| [in] | presence_single | pointer to returned PresenceSingleData item |
| int XeThru::X4M300::reset | ( | ) |
Resets and restart the module.
This is a convenience method that calls module_reset(), disconnects the communication port, and then reestablishes connection with the module.
| int XeThru::X4M300::reset_to_factory_preset | ( | ) |
Resets all parameters in the module to factory presets.
| int XeThru::X4M300::set_baudrate | ( | uint32_t | baudrate | ) |
Set baudrate for serial communication during ModuleConnector operation.
| baudrate | enum representing the baudrate, defined in xtid.h |
| int XeThru::X4M300::set_debug_level | ( | unsigned char | level | ) |
Sets debug level in the Xethru module.
| [in] | level | New debug level. Valid range [0-9]. |
| int XeThru::X4M300::set_detection_zone | ( | const float | start, |
| const float | end | ||
| ) |
Sets the current detection zone.
Rules: See X4M300 datasheet. The actual detection zone is determined by profile configuration. Use the get_detection_zone command to get the actual values
| [in] | start | start of detection zone in meters |
| [in] | end | end of detection zone in meters |
| int XeThru::X4M300::set_led_control | ( | const uint8_t | mode, |
| uint8_t | intensity | ||
| ) |
This command configures the LED mode.
| [in] | mode | mode = 0 : OFF mode = 1 : simple mode = 2 : full (default) |
| [in] | intensity | 0 to 100, 0=low, 100=high, not implemented yet |
| int XeThru::X4M300::set_output_control | ( | const uint32_t | output_feature, |
| const uint32_t | output_control | ||
| ) |
Control module profile output.
Enable and disable data messages. Several calls can be made, one for each available output message the profile provides.
| [in] | output_feature | see values in xtid.h. Possible features are: PresenceSingle PresenceMovingList BasebandIQ BasebandAP |
| [in] | output_control | see values in xtid.h Typical values: 0 = disable 1 = enable |
| int XeThru::X4M300::set_sensitivity | ( | const uint32_t | sensitivity | ) |
Sets the overall sensitivity.
| [in] | sensitivity | : 0 to 9, 0 = low, 9 = high |
| int XeThru::X4M300::set_sensor_mode | ( | const uint8_t | mode, |
| const uint8_t | param | ||
| ) |
Control the execution mode of the sensor.
| [in] | mode | see xtid.h for profileid values. Run - 0x01: Start profile execution Idle - 0x11: Halts profile execution. Can be resumed by setting mode to Run. Stop - 0x13: Stops profile execution. Must do load_profile to continue. Manual - 0x12: Routes X4 radar data directly to host rather than to profile execution. Can then interact directly with XEP / X4Driver. Will disrupt profile performance. |
| [in] | param | Not used, ignored, can be 0. |
| int XeThru::X4M300::start_bootloader | ( | ) |
Enters the bootloader for FW upgrades.
| int XeThru::X4M300::system_run_test | ( | const uint8_t | testcode, |
| Bytes * | data | ||
| ) |
Runs the different manufacturing tests identified by testcode.
Can return any number of results depending on test_mode. Host must know how to parse test results.
| [in] | testcode | |
| [out] | data |


24-Hour Clock
This is the default clock setting.
12-Hour Clock
You can use a Meridian 12-hour clock by setting [meridian]="true"
.
The passed time object will still contain a 24-hour clock.
Clock Without Spinners
Use [spinners]="false"
to hide the spinners.
Clock Without Seconds
Use [displaySeconds]="false"
to hide the seconds input.
Disabled State
You can disable the entire component by setting [disabled]="true"
.
Internationalization
The time component uses a custom service called TimeI18nLabels to give aria-labels to the buttons and inputs.
Inspect the HTML elements to see the Spanish aria-labels.
Time in Form
The time component may also be used within a form. The values within the form may then be accessed through the
usual methods used for accessing data within Angular reactive forms.


--- layout: post status: publish published: true title: 'Hearts and Minds: An Admittedly Awkward Attempt at a Poem' author: Ryan Hayden wordpress_id: 1649 wordpress_url: http://www.pastorryanhayden.com/?p=1649 date: '2014-04-01 14:40:08 -0500' date_gmt: '2014-04-01 19:40:08 -0500' categories: - ministry tags: - poem ---
Don't try to kick them out of office
Don't call them names or rant on them
Don't blame them for all your problems
Don't treat them like the enemy
Treat them like people
People Christ died for
People being defeated by the same enemy that you are
You don't win people with politics
You don't win people with Facebook memes
You don't win people by calling them names
You don't win people with hate
You win people with love
So love them
Love them by walking across the room
Love them by sharing a meal
Love them by listening
Love them by sharing Christ with them
Love them still when they reject Him
They are not the enemy
They are deceived by the enemy
Love will help them see that
Stop trying to make casualties
Start trying to make converts
Everything is downstream of hearts and minds
So win hearts and minds
"And the servant of the Lord must not strive; but be gentle unto all men, apt to teach, patient, In meekness instructing those that oppose themselves; if God peradventure will give them repentance to the acknowledging of the truth; And that they may recover themselves out of the snare of the devil, who are taken captive by him at his will." 2 Timothy 2:24-26


--- layout: post title: croquis date: '2018-01-28T11:30:15+01:00' categories: - Sketchbooks picture_url: https://film-Storyboards.tumblr.com/post/170231565660/croquis ---


| Dans_Diffraction.tkgui (version 2.2, 27/04/20) | index c:\users\dgpor\dropbox\python\dans_diffraction\dans_diffraction\tkgui\__init__.py |
Dans_Diffraction tkGUI.py
Creates a graphical user interface for Dans_Diffraction software.
Based on tkinter.
Requires:
numpy, matplotlib, tkinter
By Dan Porter, PhD
Diamond
2019
Version 2.2
Last updated: 27/04/20
Version History:
10/11/17 0.1 Program created
23/02/19 1.0 Finished the basic program and gave it colours
09/03/19 1.1 Added properties, superstructure, other improvements
13/07/19 1.2 Added FDMNES windows
13/12/19 2.0 Changed to internal tkgui package
19/04/20 2.1 Added multi-crystal, write-cif buttons, changed layout of scattering gui
27/04/20 2.2 Added SelectionBox to basic_widgets and spacegroup entry to SymmetryGui
@author: DGPorter
| Package Contents | ||||||
|


|
width - width of the new image (or its frames)
height - height of the new image frames - optional number of frames (assumed to be a single frame) flags - optional image flags |
|
Sometimes you want to create a completely new graphic on the fly (using other images, drawing commands, etc.) instead of loading one. This command will let you create a new image with a single frame or multiple frames for animation. You specify the width, height, and optional number of frames. The example should be pretty self-explainatory.
The optional flags parameter can be one of: 1 : managed (image is frequently drawn but seldom modified - this is the default) 2 : dynamic (image is frequently drawn and modified) 4 : scratch (image is seldom drawn or modified) Managed images are the default. Dynamic images are the fastest, but can be 'lost' when the display mode changes. This means the contents of the image will be scrambled, and you will need to restore the image content. If you are frequently redrawing the image contents, this isn't really a problem. If not, you should use managed images!  These are good for things like title pages and 'temporary work' images. Note that canvas buffers and back buffers should be considered 'dynamic'. See also: LoadImage, DrawImage, SaveImage, Graphics. |
|
; CreateImage/TileImage/ImageBuffer example
; Again, we'll use globals even tho we don't need them here ; One variable for the graphic we'll create, one for a timer Global gfxStarfield, tmrScreen ; Declare graphic mode Graphics 640,480,16 ; Create a blank image that is 32 pixels wide and 32 high with 10 frames of 32x32 gfxStarfield=CreateImage(32,32,10) ; loop through each frame of the graphic we just made For t = 0 To 9 ; Set the drawing buffer to the graphic frame so we can write on it SetBuffer ImageBuffer(gfxStarfield,t) ; put 50 stars in the frame at random locations For y = 1 To 50 Plot Rnd(32),Rnd(32) Next Next ; Double buffer mode for smooth screen drawing SetBuffer BackBuffer() ; Loop until ESC is pressed While Not KeyHit(1) ; Only update the screen every 300 milliseconds. Change 300 for faster or ; slower screen updates If MilliSecs() > tmrScreen+300 Then Cls ; clear the screen ; Tile the screen with a random frame from our new graphic starting at ; x=0 and y=0 location. TileImage gfxStarfield,0,0,Rnd(9) Flip ; Flip the screen into view tmrScreen=MilliSecs() ; reset the time End If Wend |


The tooltip is now protected from script injection. If you hover the tooltip, you should not see a alert and everything should be kosher.


Void QuantConnect.Algorithm.QCAlgorithm.SetAlpha ( IAlphaModel alpha )
IAlphaModel
Sets the alpha model.
Void - This method provides no return.
Void
Definition at line 306 of file Algorithm/QCAlgorithm.Framework.cs.
Void QuantConnect.Algorithm.QCAlgorithm.SetAlpha ( PyObject alpha )
PyObject
Definition at line 31 of file Algorithm/QCAlgorithm.Framework.Python.cs.


DokeV is an oddball 'family-friendly' MMO from the makers of Black Desert
I'm weirdly curious
by Jordan DevoreSometimes a video game comes our way and I just want to tell you to watch the trailer because there's a whole lot going on and it's better seen than explained. That's definitely how I feel about DokeV, a wild new PC and console MMO for "all ages" from Pearl Abyss, the Black Desert Online people.
It's kinda like Pokémon or Yo-Kai Watch, but with a staggering visual fidelity to the proceedings.
The trailer is a trip. The 4K upload made my eyes melt a bit.
The game is called DokeV – that's "doh-keh-vee," by the way – and it's about creatures, Dokebi, "that grow and gain power from people's dreams." It's running on the studio's next-gen game engine.
Pearl Abyss is juggling multiple other projects right now (including a new fantasy IP, Crimson Desert, and an arena fighter, Shadow Arena), but this is the one I'm most into as a creature-collecting game fan. The developer sums up DokeV as an "open world adventure," and expects to run a beta test in 2020.


Retirement Calculator
Enter your information
Results
Using the information you provided. This is what you finanicial future looks like.- Retirement income:
-
This number is the same as the net income you would be living off of while saving. (net income - retirement savings) So it is effectivly the net income you will have the year you retire.
- Safe retirement balance:
-
Simpily. This is (25 * Net Income at retirement)
Why though? First a few assumptions.
- You will with draw 4% of the balance of your account each year after retirement.
- You will earn an average of 4% interest when you retire.
- There will be on average 3% inflation (high for US / Erope)
- You will not be receiving any supplimentary income after you retire (pention, social security, ect.).

If these assumptions hold true, and the averages over the last 125 years also hold true, than with 25 times your net income saved you have a 97% chance of your money will last at least 50 years. In most cases it will likely last forever, but the historical data does not go far enough back to make more assertive claims.
| Year | Age | Income | Savings |
|---|


If you have been using PHP to perform CRUD (Create, Read, Update, Delete) operations to your database, you've probably been writing a lot of code.
Whether you're a newbie to or a novice at PHP, you are most likely familiar with how much code is needed in order to connect to a database,
perform a simple operation such as reading data from a table, or log errors for debugging.
With ChapChapSQL, you can make your coding much easier by writing less code:
you don't need to worry if you've used prepared statements each time you make a CRUD operation,
if you've escaped the data to prevent a security breach, or if you've used the correct SQL syntax.
All this is handled for you so that you can concentrate on your project with your mind at ease, assured that issues such as SQL injection are already taken care of.
ChapChapSQL uses PHP 7.0, which is a powerful server scripting language.
JSON can be read and used as a data format by any programming language
ChapChapSQL uses the standard language for accessing databases.
Enjoy extra functionality such as logs minification, and backtrace objects.
ChapChapSQL employs PDO, which works on 12 different database systems.
ChapChapSQL is simple to use; just include it in your script and you're good to go!
ChapChapSQL is negligible in size (only 145 kb gzipped).
ChapChapSQL can work on any browser and server capable of processing PHP.


Galileo iOS Quick Start Guide Document
Welcome to the Galileo iOS Quick Start Guide for developers. The following information should help you get started with building Galileo compatible applications on the iOS platform. The examples in this guide were built using Xcode 5.1 and have been tested with iOS SDK 7.0 and later. Comments, corrections and suggestions should be sent to<EMAIL_ADDRESS>First time developers should read through Apple’s introductory guide on iOS app development, Start Developing iOS Apps Today. Experienced developers may want to take a look at the sample projects for more advanced uses of the SDK.
Table of Contents
Resources
Installing the SDK
Configuring your XCode project
Connecting to Galileo
Moving Galileo
Resources
Documentation
The full index of class references can be viewed on the GalileoControl index page. In this guide you will make use of the following classes:
GCGalileo
- Defines the gateway singleton object for connecting to Galileo and accessing motion controllers.GCGalileoDelegate
- Delegate protocol for notification of connection and disconnection events.GCPositionControl
- Control Galileo by moving to a specified position.GCVelocityControl
- Control Galileo by setting angular velocity.
Community
For the latest updates check out our developer blog our developer portal. Feel free to email comments and questions to<EMAIL_ADDRESS>If you would like to be notified of SDK updates then you can also send your requests to<EMAIL_ADDRESS>Sample projects
HelloWorldGalileo - Connect to Galileo and output simple pan and tilt commands when on-screen buttons are pressed.
UpdateGalileo - Check for new firmware updates and apply them over the air to Galileo.
RemoteControlGalileo - Two-way video calling and remote control over WiFi.
Installing the SDK
The SDK can be downloaded and added to your project manually. Git users can create a git submodule to stay up to date with future releases.
Manual installation
Installation is as easy as adding the SDK folder to you project directory.
- Download the SDK archive either in .zip format or .tar.gz.
- Extract the archive to somewhere appropriate in your project direcory. For this guide you will extract the contents of the archive to a folder called Galileo-iOS-SDK, located in the root of the project directory.
Installing as a git submodule
This method assumes you are using git for source control and have a git repository containing your Xcode project already set up.
Navigate to the root of you git repository and execute the following commands. This will create and initialise the submodule and commit the changes.
git submodule add https://github.com/motrr/Galileo-iOS-SDK.git git commit -m "Added Galileo iOS SDK submodule"
At some point in the future you may wish to update you project’s copy of the SDK to the latest version. To do this, again navigate to the root directory and execture the following.
cd Galileo-iOS-SDK git checkout master git pull cd .. git add Galileo-iOS-SDK git commit -m "Updated Galileo iOS SDK submodule"
Configuring your XCode project
Your Xcode project will need to be configured to include the GalileoControl framework and its dependencies. You will also need to declare the use of Galileo’s External Accessory protocols.
Adding the GalileoControl framework
Locate the GalileoControl.framework directory within your SDK folder. Drag and drop the .framework directory into the Frameworks group of your Xcode project.
When asked to confirm, ensure that “Copy items into destination group’s folder” is not selected.
Adding additional dependencies
The GalileoControl framework also depends on the following Apple frameworks and libraries.
- libxml2.dylib
- ExternalAccessory.framework
- CoreBluetooth.framework
- QuartzCore.framework
Adding them to your project can be done using the following steps.
- In the project editor, select the target to which you want to add a library or framework.
- Click Build Phases at the top of the project editor.
- Open the Link Binary With Libraries section.
- Click the Add (+) button to add a library or framework.
- Select a library or framework from the list and click Add.
See the Apple documentation on Linking to a Library or Framework for more details.
Declaring External Accessory protocols
motrr defines one External Accessory protocols which must be declared in you project’s Info.plist file under the Supported external accessory protocols
key.
com.motrr.galileo
Configure your Info.plist with the following steps.
- In the project explorer, locate you project’s Info.plist file. It will be prefixed with project’s name and is typically located in the Supporting Files group.
- In the property list editor, hold the pointer over an entry and click the Add (+) button.
- Choose the key name
Supported external accessory protocols
from the pop-up menu. - Add an entry for the motrr protocol
com.motrr.galileo
.
Connecting to Galileo
Connecting to Galileo is performed asynchronously. Notification of a succesful connection is provided using the GCGalileoDelegate
protocol whilst initiating a connection is done using the GCGalileo
shared instance. A notification based alternative to the delegate protocol is also available, please refer to the documentation for details.
To begin with, ensure you include the
GalileoControl.h
header in any source files which make use of the GalileoControl framework.#import <GalileoControl/GalileoControl.h>
To initiate a connection, access the shared Galileo instance and call the
waitForConnection
method. Typically you would also set the delegate prior to this call.[GCGalileo sharedGalileo].delegate = self; [[GCGalileo sharedGalileo] waitForConnection];
In order to be notified when a connection is established you must also implement the
GCGalileoDelegate
protocol. The following code snippet alerts the user when Galileo connects by implementing thegalileoDidConnect
method.- (void) galileoDidConnect { UIAlertView* galileoConnectedAlert = [[UIAlertView alloc] initWithTitle:@"Galileo connected!" message:nil delegate:nil cancelButtonTitle:@"OK" otherButtonTitles:nil]; [galileoConnectedAlert show]; }
It is also normally a good idea to handle Galileo disconnecting in the event that the device is removed from the accessory or runs out of battery. A typical reaction might be to start waiting for the next connection, amongst other things.
- (void) galileoDidDisconnect { [[GCGalileo sharedGalileo] waitForConnection]; }
Moving Galileo
Galileo can be controlled with two distinct modes: position control and velocity control. Both can be accessed using methods on the GCGalileo
shared instance.
An instance of
GCPositionControl
is obtained by callingpositionControlForAxis:
. A distinct position control instance exists for each axis the connected Galileo supports. The following delegate implementation would pan Galileo clockwise by 90 degrees as soon as a connection is established.- (void) galileoDidConnect { GCPositionControl* panPositionControl = [[GCGalileo sharedGalileo] positionControlForAxis:GCControlAxisPan]; [panPositionControl incrementTargetPosition:90.0 notifyDelegate:nil waitUntilStationary:NO]; }
Velocity control is performed in a similar fasion, using an instance of
GCVelocityControl
. The following example starts Galileo rotating the phone around it’s tilt axis at 100 degrees per second.GCVelocityControl* tiltVelocityControl = [[GCGalileo sharedGalileo] velocityControlForAxis:GCControlAxisTilt]; [tiltVelocityControl setTargetVelocity:100.0];
The library will attempt to switch control modes automatically, however using more than one mode for a single axis requires explicitly instructing the
<Galileo>
shared instance to switch modes using theselectMode:forAxis:
method.GCControlAxis axis = GCControlAxisPan; // GCVelocityControl* tiltVelocityControl = [[GCGalileo sharedGalileo] velocityControlForAxis:axis]; [[GCGalileo sharedGalileo] selectMode:GCModeVelocityControl forAxis:axis]; [tiltVelocityControl setTargetVelocity:100.0]; // GCPositionControl* tiltPositionControl = [[GCGalileo sharedGalileo] positionControlForAxis:axis]; [[GCGalileo sharedGalileo] selectMode:GCModePositionControl forAxis:axis]; [tiltPositionControl incrementTargetPosition:-90 notifyDelegate:nil waitUntilStationary:NO];


Class File
File
Namespace: Xvolutions\AdminBundle\Entity
Orm\entity
Orm\table()
Located at AdminBundle/Entity/File.php
Orm\entity
Orm\table()
Located at AdminBundle/Entity/File.php
public
integer
|
|
public
|
|
public
string
|
|
public
|
|
public
string
|
|
public
|
|
public
string
|
|
public
|
|
public
DateTime
|
|
public
|
|
public
integer
|


Outrage as cattle skulls found dumped next to bins in Strathaven
“They looked like the heads of bulls, with big thick horns. They looked rotten."
by Fraser N Wilson, https://www.dailyrecord.co.uk/authors/fraser-n-wilson/Residents in Strathaven have been left sickened after cattle skulls were dumped next to a bin.
The extreme fly-tipping saw two skulls ditched along with household waste just outside the town.
Doreen Dodds made the gruesome discovery near Caldermill and spoke with the News about the issue.
She said: “These are definitely not fake.
“They looked like the heads of bulls, with big thick horns. They looked rotten.
“But there they were, in amongst household rubbish and all. I don’t know what’s going on, but it’s pretty scary.”
A volunteer with Cat Concern and Cat Action, Doreen says there is a larger problem with animal abuse in the South Lanarkshire area.
She added: “I saw a grouse just dumped recently and a cat at the side of the road.
“Then there was the four starved puppies cruelly dumped at the side of a road in Dungavel.
“There’s a real problem here.”
Reacting to Doreen’s post on Facebook, Peter Kinnon wrote: “What an absolute disgrace this is, and fly-tipping in general.
“Our local MP and SLC need to look at this urgently, and initiate the appropriate actions and penalties against all those involved.”
Claire Shearer added: “Shocking, disgusting – also shows that the bins are not emptied enough.”
And Carol Brogan gave credence to some of Doreen’s concerns about a bigger issue.
She wrote online: “That is really shocking.
“I was out running last week in Strathaven and ran past a bin bag full of game birds at the side of the road on the stretch of road from Sandford to Strathaven.”
Doreen – who works at the Royal Infirmary Hospital – reported the matter to the SSPCA who said they were looking into the matter.
Scottish SPCA inspector Dawn Robertson told us: ‘We have been made aware of this incident and are investigating.
“Anyone with any information is urged to contact our confidential animal helpline on 03000 999 999.”


Display count of children at parent node.
The main puropse of this extension is to serve as an example for
Fanytree's the general extension concept:
See the
annotated source
to learn how to write a Fancytree extension.
Click the [View source code] link below, to see how an extension is used.
Status: pre-alpha
jquery.fancytree.js project home Link to this page Example Browser View source code


{{ header }}
{{ navbar }}
Date:
Time:
Repeat Option:
No Repeat
1 Time (Adds a session a week after the initial date)
2 Times (Adds 2 sessions, 7 and 14 days after the initial date)
3 Times
4 Times
5 Times
6 Times
Submit
{{ footer }}


Step 7: Go Live
Go Live is the point at which a vets.gov product is pushed to the public. Products undergo a process of continuous improvement in response to ongoing customer feedback and the addition of new capabilities.
Outputs
- Public Product
- Sunset Initiated
Leads
- VA Product Lead
- Project Team POC
- Technical Lead
Participants
- Engineering Team
- Design Team
- VA Business Owner
- VA Product Lead
- Help Desk POC
- VA Call Center POC
Stakeholder Engagement
- Deploy communications per plan
Team Activities
- Product Launch
- Deploy communications on both legacy websites and vets.gov to inform users of changes
- Help Desk prepared to monitor for issues
- Call Center prepared to monitor for issues
- Continuous improvements
- Assessment of success metrics/measurement
- Sunset strategy deployed


FIANCO
Copyright (c) 1987 Fred Horn
This game is played on a 9x9 square board with the following setup:
- TURN - A player must move one of his stones. A stone may:
- Move forwards or sideways to an adjacent empty cell.
- Capture by jumping (diagonally forward) over an enemy stone, landing on the immediate empty cell. Capturing is mandatory but not multiple (maximum of one captured stone per turn.)
- GOAL - A player wins if he places one of his stones on the last row.
An example Black's turn. He wins with e4-e3. White must capture d2:f4 (or c2:e4 and then e3:c1 wins) and Black moves d3-d2 winning on the next turn.
There's a website with information about the game (in Dutch). I wish to thank Hans Bodlaender for translating the rules.


SB-2
Darken the scrollbar thumbsIn this activity, we shall take the first of the two approaches discussed above and override the thumb rule’s background-color
style established in the default scrollbars stylesheet.
- Open the default scrollbars stylesheet, finbars.css, containing the styles we want to override, and place the window off to the side
- In the stylesheet, the default thumb background color in the “thumb style” rule is
lightgrey
(#d3d3d3
) - Switch to the Scrollbars tab and click its reset icon, if red (), to reload the empty custom stylesheet, which consists of all the commented selectors from the default stylesheet, except with all the CSS rules emptied (so, so far it’s overriding nothing)
-
Add a
background-color
override to the additional “thumb style” rule here (in the editor) with a darker color, such as mediumblack
, so it looks like this:/* thumb style */ div.finbar-vertical > .thumb, div.finbar-horizontal > .thumb { background-color: black; }
This is a stylesheet. We use CSS syntax here, not JSON or JavaScript. That is, do not use quotes; do not use camelCase. - Click the
style
element, which is appended to the DOM just below the default scrollbars stylesheetstyle
element
button to inject this text into a - Thumbs are now darker.


Starting with release 0.4, Julia makes it easy to write elegant and
efficient multidimensional algorithms. The new capabilities rest on
two foundations: a new type of iterator, called CartesianRange
, and
sophisticated array indexing mechanisms. Before I explain, let me
emphasize that developing these capabilities was a collaborative
effort, with the bulk of the work done by Matt Bauman (@mbauman),
Jutho Haegeman (@Jutho), and myself (@timholy).
These new iterators are deceptively simple, so much so that I’ve never
been entirely convinced that this blog post is necessary: once you
learn a few principles, there’s almost nothing to it. However, like
many simple concepts, the implications can take a while to sink in.
There also seems to be some widespread confusion about the
relationship between these iterators and
Base.Cartesian
,
which is a completely different (and much more painful) approach to
solving the same problem. There are still a few occasions where
Base.Cartesian
is necessary, but for many problems these new
capabilities represent a vastly simplified approach.
Let’s introduce these iterators with an extension of an example taken from the manual.
You may already know that, in julia 0.4, there are two recommended
ways to iterate over the elements in an AbstractArray
: if you don’t
need an index associated with each element, then you can use
for a in A # A is an AbstractArray
# Code that does something with the element a
end
If instead you also need the index, then use
for i in eachindex(A)
# Code that does something with i and/or A[i]
end
In some cases, the first line of this loop expands to for i =
1:length(A)
, and i
is just an integer. However, in other cases,
this will expand to the equivalent of
for i in CartesianRange(size(A))
# i is now a CartesianIndex
# Code that does something with i and/or A[i]
end
Let’s see what these objects are:
julia> A = rand(3,2)
julia> for i in CartesianRange(size(A))
@show i
end
i = CartesianIndex{2}((1,1))
i = CartesianIndex{2}((2,1))
i = CartesianIndex{2}((3,1))
i = CartesianIndex{2}((1,2))
i = CartesianIndex{2}((2,2))
i = CartesianIndex{2}((3,2))
A CartesianIndex{N}
represents an N
-dimensional index.
CartesianIndex
es are based on tuples, and indeed you can access the
underlying tuple with i.I
. However, they also support certain
arithmetic operations, treating their contents like a fixed-size
Vector{Int}
. Since the length is fixed, julia/LLVM can generate
very efficient code (without introducing loops) for operations with
N-dimensional CartesianIndex
es.
A CartesianRange
is just a pair of CartesianIndex
es, encoding the
start and stop values along each dimension, respectively:
julia> CartesianRange(size(A))
CartesianRange{CartesianIndex{2}}(CartesianIndex{2}((1,1)),CartesianIndex{2}((3,2)))
You can construct these manually: for example,
julia> CartesianRange(CartesianIndex((-7,0)), CartesianIndex((7,15)))
CartesianRange{CartesianIndex{2}}(CartesianIndex{2}((-7,0)),CartesianIndex{2}((7,15)))
constructs a range that will loop over -7:7
along the first
dimension and 0:15
along the second.
One reason that eachindex
is recommended over for i = 1:length(A)
is that some AbstractArray
s cannot be indexed efficiently with a
linear index; in contrast, a much wider class of objects can be
efficiently indexed with a multidimensional iterator. (SubArrays are,
generally speaking, a prime
example.)
eachindex
is designed to pick the most efficient iterator for the
given array type. You can even use
for i in eachindex(A, B)
...
to increase the likelihood that i
will be efficient for accessing
both A
and B
.
As we’ll see below, these iterators have another purpose: independent of whether the underlying arrays have efficient linear indexing, multidimensional iteration can be a powerful ally when writing algorithms. The rest of this blog post will focus on this latter application.
Let’s suppose we have a multidimensional array A
, and we want to
compute the “moving
average” over a
3-by-3-by-… block around each element. From any given index position,
we’ll want to sum over a region offset by -1:1
along each dimension.
Edge positions have to be treated specially, of course, to avoid going
beyond the bounds of the array.
In many languages, writing a general (N-dimensional) implementation of this conceptually-simple algorithm is somewhat painful, but in Julia it’s a piece of cake:
function boxcar3(A::AbstractArray)
out = similar(A)
R = CartesianRange(size(A))
I1, Iend = first(R), last(R)
for I in R
n, s = 0, zero(eltype(out))
for J in CartesianRange(max(I1, I-I1), min(Iend, I+I1))
s += A[J]
n += 1
end
out[I] = s/n
end
out
end
Let’s walk through this line by line:
out = similar(A)
allocates the output. In a “real” implementation,
you’d want to be a little more careful about the element type of the
output (what if the input array element type is Int
?), but
we’re cutting a few corners here for simplicity.
R = CartesianRange(size(A))
creates the iterator for the array,
ranging from CartesianIndex((1, 1, 1, ...))
to
CartesianIndex((size(A,1), size(A,2), size(A,3), ...))
. We don’t
use eachindex
, because we can’t be sure whether that will return a
CartesianRange
iterator, and here we explicitly need one.
I1 = first(R)
and Iend = last(R)
return the lower
(CartesianIndex((1, 1, 1, ...))
) and upper
(CartesianIndex((size(A,1), size(A,2), size(A,3), ...))
) bounds
of the iteration range, respectively. We’ll use these to ensure
that we never access out-of-bounds elements of A
.
Conveniently, I1
can also be used to compute the offset range.
for I in R
: here we loop over each entry of A
.
n = 0
and s = zero(eltype(out))
initialize the accumulators. s
will hold the sum of neighboring values. n
will hold the number of
neighbors used; in most cases, after the loop we’ll have n == 3^N
,
but for edge points the number of valid neighbors will be smaller.
for J in CartesianRange(max(I1, I-I1), min(Iend, I+I1))
is
probably the most “clever” line in the algorithm. I-I1
is a
CartesianIndex
that is lower by 1 along each dimension, and I+I1
is higher by 1. Therefore, this constructs a range that, for
interior points, extends along each coordinate by an offset of 1 in
either direction along each dimension.
However, when I
represents an edge point, either I-I1
or I+I1
(or both) might be out-of-bounds. max(I-I1, I1)
ensures that each
coordinate of J
is 1 or larger, while min(I+I1, Iend)
ensures
that J[d] <= size(A,d)
.
The inner loop accumulates the sum in s
and the number of visited
neighbors in n
.
Finally, we store the average value in out[I]
.
Not only is this implementation simple, but it is surprisingly robust:
for edge points it computes the average of whatever nearest-neighbors
it has available. It even works if size(A, d) < 3
for some
dimension d
; we don’t need any error checking on the size of A
.
For a second example, consider the implementation of multidimensional reductions. A reduction takes an input array, and returns an array (or scalar) of smaller size. A classic example would be summing along particular dimensions of an array: given a three-dimensional array, you might want to compute the sum along dimension 2, leaving dimensions 1 and 3 intact.
An efficient way to write this algorithm requires that the output
array, B
, is pre-allocated by the caller (later we’ll see how one
might go about allocating B
programmatically). For example, if the
input A
is of size (l,m,n)
, then when summing along just dimension
2 the output B
would have size (l,1,n)
.
Given this setup, the implementation is shockingly simple:
function sumalongdims!(B, A)
# It's assumed that B has size 1 along any dimension that we're summing
fill!(B, 0)
Bmax = CartesianIndex(size(B))
for I in CartesianRange(size(A))
B[min(Bmax,I)] += A[I]
end
B
end
The key idea behind this algorithm is encapsulated in the single
statement B[min(Bmax,I)]
. For our three-dimensional example where
A
is of size (l,m,n)
and B
is of size (l,1,n)
, the inner loop
is essentially equivalent to
B[i,1,k] += A[i,j,k]
because min(1,j) = 1
.
As a user, you might prefer an interface more like sumalongdims(A,
dims)
where dims
specifies the dimensions you want to sum along.
dims
might be a single integer, like 2
in our example above, or
(should you want to sum along multiple dimensions at once) a tuple or
Vector{Int}
. This is indeed the interface used in sum(A, dims)
;
here we want to write our own (somewhat simpler) implementation.
A bare-bones implementation of the wrapper is straightforward:
function sumalongdims(A, dims)
sz = [size(A)...]
sz[[dims...]] = 1
B = Array(eltype(A), sz...)
sumalongdims!(B, A)
end
Obviously, this simple implementation skips all relevant error
checking. However, here the main point I wish to explore is that the
allocation of B
turns out to be
type-unstable:
sz
is a Vector{Int}
, the length (number of elements) of a specific
Vector{Int}
is not encoded by the type itself, and therefore the
dimensionality of B
cannot be inferred.
Now, we could fix that in several ways, for example by annotating the result:
B = Array(eltype(A), sz...)::typeof(A)
However, this isn’t really necessary: in the remainder of this
function, B
is not used for any performance-critical operations.
B
simply gets passed to sumalongdims!
, and it’s the job of the
compiler to ensure that, given the type of B
, an efficient version
of sumalongdims!
gets generated. In other words, the type
instability of B
’s allocation is prevented from “spreading” by the
fact that B
is henceforth used only as an argument in a function
call. This trick, using a function-call to separate a
performance-critical step from a potentially type-unstable
precursor,
is sometimes referred to as introducing a function barrier.
As a general rule, when writing multidimensional code you should
ensure that the main iteration is in a separate function from
type-unstable precursors. Even when you take appropriate precautions,
there’s a potential “gotcha”: if your inner loop is small, julia’s
ability to inline code might eliminate the intended function barrier,
and you get dreadful performance. For this reason, it’s recommended
that you annotate function-barrier callees with @noinline
:
@noinline function sumalongdims!(B, A)
...
end
Of course, in this example there’s a second motivation for making this a standalone function: if this calculation is one you’re going to repeat many times, re-using the same output array can reduce the amount of memory allocation in your code.
One final example illustrates an important new point: when you index
an array, you can freely mix CartesianIndex
es and
integers. To illustrate this, we’ll write an exponential
smoothing
filter. An
efficient way to implement such filters is to have the smoothed output
value s[i]
depend on a combination of the current input x[i]
and
the previous filtered value s[i-1]
; in one dimension, you can write
this as
function expfilt1!(s, x, α)
0 < α <= 1 || error("α must be between 0 and 1")
s[1] = x[1]
for i = 2:length(a)
s[i] = α*x[i] + (1-α)*s[i-1]
end
s
end
This would result in an approximately-exponential decay with timescale 1/α
.
Here, we want to implement this algorithm so that it can be used to exponentially filter an array along any chosen dimension. Once again, the implementation is surprisingly simple:
function expfiltdim(x, dim::Integer, α)
s = similar(x)
Rpre = CartesianRange(size(x)[1:dim-1])
Rpost = CartesianRange(size(x)[dim+1:end])
_expfilt!(s, x, α, Rpre, size(x, dim), Rpost)
end
@noinline function _expfilt!(s, x, α, Rpre, n, Rpost)
for Ipost in Rpost
# Initialize the first value along the filtered dimension
for Ipre in Rpre
s[Ipre, 1, Ipost] = x[Ipre, 1, Ipost]
end
# Handle all other entries
for i = 2:n
for Ipre in Rpre
s[Ipre, i, Ipost] = α*x[Ipre, i, Ipost] + (1-α)*s[Ipre, i-1, Ipost]
end
end
end
s
end
Note once again the use of the function barrier technique. In the
core algorithm (_expfilt!
), our strategy is to use two
CartesianIndex
iterators, Ipre
and Ipost
, where the first covers
dimensions 1:dim-1
and the second dim+1:ndims(x)
; the filtering
dimension dim
is handled separately by an integer-index i
.
Because the filtering dimension is specified by an integer input,
there is no way to infer how many entries will be within each
index-tuple Ipre
and Ipost
. Hence, we compute the CartesianRange
s in
the type-unstable portion of the algorithm, and then pass them as
arguments to the core routine _expfilt!
.
What makes this implementation possible is the fact that we can index
x
as x[Ipre, i, Ipost]
. Note that the total number of indexes
supplied is (dim-1) + 1 + (ndims(x)-dim)
, which is just ndims(x)
.
In general, you can supply any combination of integer and
CartesianIndex
indexes when indexing an AbstractArray
in Julia.
The AxisAlgorithms package makes heavy use of tricks such as these, and in turn provides core support for high-performance packages like Interpolations that require multidimensional computation.
It’s worth noting one point that has thus far remained unstated: all of the examples here are relatively cache efficient. This is a key property to observe when writing efficient code. In particular, julia arrays are stored in first-to-last dimension order (for matrices, “column-major” order), and hence you should nest iterations from last-to-first dimensions. For example, in the filtering example above we were careful to iterate in the order
for Ipost ...
for i ...
for Ipre ...
x[Ipre, i, Ipost] ...
so that x
would be traversed in memory-order.
As is hopefully clear by now, much of the pain of writing generic multidimensional algorithms is eliminated by Julia’s elegant iterators. The examples here just scratch the surface, but the underlying principles are very simple; it is hoped that these examples will make it easier to write your own algorithms.


instance.upgrade.no_horti.detail
{{error}}
instance.upgrade.no_details
instance.upgrade.no_new_releases
instance.upgrade.no_betas
instance.upgrade.no_branches


With the service " pushover " and the corresponding app (7-day test phase free of charge, afterwards just once 276 INR for Android and 321 INR for iOS ) on your (Android / iOS) smartphone or tablet can be completely through an API Simply send push messages to your devices. Desktop systems / browsers are also supported. Practically, the correct library can also be sent via the ESP8266, so you can easily design IoT devices that will notify you about pushover. Examples are, for example, notifications when your washing machine is ready when someone rings the door or when a letter is thrown into your mailbox. To present the service here,
Set up the pushover account and plugin
First you must register with Pushover. This is, of course, free of charge and easy on this site . After successfully registering and activating the account, you will get an individual user key, which you need later, via the dashboard on the pushover page. So save it to yourself or write it down, to have it at hand later.
Then open this page to create a new pushover app:
You can now install the pushover app on your smartphone and log in to your previously created pushover account.
HARDWARE SETUP
Sketch For ESP8266:
Download code from github.
As with most projects with the ESP8266, I also use the Arduino IDE with the appropriate ESP8266 addon to fill the NodeMCU board with software. Setting up the development environment ", so I refer to this point if you have not already set up the environment for the ESP8266 on your computer. To communicate with the pushover API, there is an easy-to-use library that you can find in this GitHub repository . How to install the library in your Arduino IDE can be found on this documentary page of Arduino.
Now you can compile this sketch and transfer it to your board.
In addition to your WLAN data, you have to enter your user and API key in the pushover variable "po".
Push notification on your smartphone:
If you now press the button, you should pop up an appropriate notification on your smartphone. With me it looks like this:Setting up push messages from the ESP8266 to the smartphone is very easy thanks to the pushover and existing libraries to communicate with the API and can be integrated in many projects.


For more details and help see the SearchGUI home page: http://compomics.github.io/projects/searchgui.html.
To visualize and analyze SearchGUI results we recommend the use of PeptideShaker.
If you find any bugs or have any questions please contact the developers.
Please cite SearchGUI as Barsnes and Vaudel: J Proteome Res. 2018 Jul 6;17(7):2552-5.


--- title: Zbalermorna IME css: ime redirect_from: /test/ime.html nav: |
---Type any consonant to insert the zlm equivalent. Lowercase vowels are inserted as diacritics, unless they form semivowels. Uppercase vowels form full vowels. All diphthongs are automatic. h
or '
will insert a .y'ybu , and .
will insert denpabu . The attitudinal shorthand () is created automatically with ligatures.
,
will separate two full vowels from becoming a diphthong, or prevent a vowel from being self-dotted with a denpabu
-
inserts one character of silence
~
applies stretch to the previous character - use after the vowel
1234
adds the respective intonation to the previous character - use after the vowel
`
adds dynamics to the previous character - use after the vowel
Text can be typed or pasted in, but may take some time to transcribe - the result should be the same. Any text copied from the textarea will be encoded to the Zbalermorna Unicode space, and will only display correctly with Zbalermorna-compatible fonts.
You can select other fonts from the menu at the top, or drag and drop any font file into this window for it to be rendered in the textarea above.


Not Found
The requested URL /ng/journal/v38/n8/thumbs/ng0806-856-f1.gif was not found on this server.


Approximating circle area with Monte-carlo
Canvas not supported
Ratio:
Total area:
Circle area estimation:
Real circle area (Pi*r^2):


Question1: What is Xuan's nickname?
Question2: How old is Xuan?
Is Xuan a Male or Female? Male Female Bisexual
For Testing


---
layout: post
title: ! 'Software Development: Managing in the dirty trenches'
tags:
- Project Management
- Software Development
status: publish
type: post
published: true
meta: {}
---
When you talk to many consultants about managing projects then they tend to offer the 'helicopter' view of the world. The conversation is based around concepts like vision, planning, delivery, scope etc etc. Whilst this is key to project success -- you can't complete a successful project without a clear roadmap, there is often a disconnect between the management view of a project and the work that is going in in the trenches.
The reason? The devil is in the detail and someone needs to be down in the trenches tracking activity and issues on a daily basis.
What does that mean? It means someone needs to:
- Understand (the relevant portion of) the project plan at the detailed task level
- Identify and track all issues and risks
- Monitor daily progress (this can be a lot easier when using test driven development and testable features style approach)
- Have a good grasp of the technical and project impacts that issues create when they occur (NB -- The business impacts are the job of the project manager and customer)
- Have the courage to describe things as the really are and suggest unpalatable options
Now in my view that should be a major portion of the activity performed by a senior team lead. However in my experience team leads rarely have the inclination or authority to fulfil this vital role, they seem themselves as 'superior' developers focused primarily on technical and architectural issues (which are also important of course).
So it's up to the project manager to either do this work themselves or identify suitable individuals who can take on this role. It is important to think outside of the box and consider all possible options when looking for these people, they usually don't jump and down saying 'Oh me sir, please sir!'.
If you do find people with such potential then mentor them and nurture them well. They will become future project managers and will help save your bacon on the current project.


Code Club Coding Contest is a grassroots initiative which aims to bring coding and digital literacy to everybody in a fun and engaging way.
Today we live in a world that has been affected by rapid advances in technology. The way we work, communicate, shop and think has changed dramatically. In order to cope with these rapid changes and to make sense of the world around us, we need to not only develop our understanding of how technology works, but also develop skills and capabilities, that will help us to adapt to living in this new era. Learning to code helps us to make sense of how things work, explore ideas and make things, for both work and play. What’s more it helps us to unleash our creativity and work collaboratively with wonderful people both near us and all over the world.
Code-Club
You can code in more than 10 languages including java, c ,c++, c#, Javascript, python etc
Cause even the world Champion needs Practice
This is the plateform to prove yourself
These certifiates will put a positive impact on your resume
It can land you your dream job
Best institute for technical education in middle India
You are just one click away from it
Plateform Sponsor
Questions?
Shri Shankracharya Engineering college, Junvani, Bhilai
Chhattisgarh
<EMAIL_ADDRESS>+917389630407


{if embed:action_id} {exp:query sql=" SELECT DISTINCT exp_members.screen_name, exp_members.photo_filename, exp_members.member_id, exp_channel_data.field_id_23 as id_status_action FROM exp_members, exp_channel_data, exp_friends_status WHERE exp_members.member_id=exp_channel_data.field_id_16 AND exp_channel_data.field_id_15 = '{embed:action_id}' AND exp_friends_status.visible='0' "}


The 2,147,483,648 NoteId limit
Every Note in a Lotus Notes database has 2 identifiers: a 32Byte Hex Universalid (UNID) and a NoteId (actually there are some more). The UNID is assigned once, never changes (unless you force it), is derived from a timestamp and stays unique across all replicas.
The 128Bit (incidentially the same size as IPv6) are divided in the first 64Bit from the replicaID and the second 64Bit for the individual documents (but you could overwrite that). Normal use gives you 2 64 possible values ( = 1.8 19 = 1,800 quintillion) for documents.
The Noteid on the other hand is unique only to one given database and changes when you create a new replica or run
So you have 2 31 = 2,147,483,648 NoteIds at your disposal. A NoteId is assigned when a Note is saved in a database (could be design or data) and never reused even after a document is deleted and the resulting deleting stub expired and is removed.
When you have a very busy (large) database where many documents are constantly created and deleted you might hit that ceiling, even when the document count and database size seem moderate. The error condition is documented in Technote swg21220384 (the error can also occur in normal operation).
To my best knowledge you can't setup a DDM probe (or any other easy admin tool) to monitor " NoteId exhaustion". A suitable preventive remedy is to schedule regular
Be careful with that, since the dose makes the poison and running that task every day will compound the side effects. If your database does need a daily compact, you have a structural problem in your application - come and see me. Typical intervals are weekly or monthly. Smart admins spread them out (so some compact is running every day). The side effect for
The 128Bit (incidentially the same size as IPv6) are divided in the first 64Bit from the replicaID and the second 64Bit for the individual documents (but you could overwrite that). Normal use gives you 2 64 possible values ( = 1.8 19 = 1,800 quintillion) for documents.
The Noteid on the other hand is unique only to one given database and changes when you create a new replica or run
compact -c
. For performance reasons (Notes is around for a while) this is a 4 byte Hex number (where only even numbers are used). For backward compatibility in the API that hasn't changed yet.
So you have 2 31 = 2,147,483,648 NoteIds at your disposal. A NoteId is assigned when a Note is saved in a database (could be design or data) and never reused even after a document is deleted and the resulting deleting stub expired and is removed.
When you have a very busy (large) database where many documents are constantly created and deleted you might hit that ceiling, even when the document count and database size seem moderate. The error condition is documented in Technote swg21220384 (the error can also occur in normal operation).
To my best knowledge you can't setup a DDM probe (or any other easy admin tool) to monitor " NoteId exhaustion". A suitable preventive remedy is to schedule regular
compact -c
for your busy databases.
Be careful with that, since the dose makes the poison and running that task every day will compound the side effects. If your database does need a daily compact, you have a structural problem in your application - come and see me. Typical intervals are weekly or monthly. Smart admins spread them out (so some compact is running every day). The side effect for
compact -c
on Windows (applied to SAN too) is disk fragmentation. So make sure you take care of that.Posted by Stephan H Wissel on 08 September 2012 | Comments (3) | categories: Show-N-Tell Thursday


--- layout: page title: About header-img: "img/about-bg.png" ---
Aaron is a musician, a teacher, a father and a lover of technology.


Defender Cromwell:
Hark, who approaches the Dwarven Village? I'm Cromwell, in charge of guarding this entrance... You say you've heard of me, eh?
Have you heard about the beach north of here? It's a great place to go and relax.  You'd probably like it there.
"Who is the Lord of the manor and what is the tax rate?"
Quest