Insta Love Pours In For Bvuma Despite Chiefs Loss
by SL SocialHe might have been on the losing side on the day, but that did not stop the Instagram love from pouring in for Kaizer Chiefs goalkeeper Bruce Bvuma.
The score line could have been much different had it not been for the heroics of the 24-year-old who was deputising for experienced campaigners, Itumeleng Khune and Daniel Akpeyi.
Download The Soccer Laduma Social Media App & Earn Airtime for Selfies!
Bvuma marshalled his defence and rose to the occasion whenever called upon in front of a packed Mbombela stadium. The youngster did not seem overawed by the magnitude of the occasion.
Although Amakhosi suffered defeat on the day, there were rave reviews on Instagram for the man they have billed as “the future of South African goalkeeping”
Compatriots like Bidvest Wits defender Zitha Macheke amongst others, took to Instagram to shower Bvuma with praise.
Do you think that Bvuma can take over the reins at Kaizer Chiefs in years to come?


In two weeks, to create a working protoype that articulated a better future and the art of the possible.
Working with a team from across MoD, we created a live service that showed a better way was possible. The output is supporting MoD in defining their requirements for a new system which will be procured in 2016.
A new workflow was tested - visitors could initate a vist by entering their details and submitting the request. MoD staff can accept or decline - no need to enter visitor details.
As well as the usual visitor booking features, the protoype implemented capabilities to improve control and operational efficiency.
Visitors numbers can be easily seen for each day to allow establishments to resource security and reception appropriately.
Integrated with Calendars Accepted meeting requests are synchronised to the visitor and MoD staff's calendars.
VIP Visitors highlighted for reception and Head of Establishment.
Text Message on Visitor Arrival with variants for needs escorting and security cleared.
Establishment Security can see if banned persons are trying to access a site.
Security Clearance details are stored and can be verified by reception and security staff.
The process started with discovery workshops to understand and document user needs.
Capturing requirements a half day workshop was run to capture high level requirements.
Trello was to turn requirements into user stories. Trello was also used for detailed sprint planning and progress reporting.
Weekly sprints deliver working software quickly. Our aim is a production ready update at least once a week. Project sponsors can attend any of the team and project meetings.
Virtual teams & distributed Agile allow us to leverage the skills of Atos UK and make progress most quickly.
The prototype is for INTERNAL ATOS and MOD USE ONLY and can be accessed as follows:
Use the following login IDs (David Dinsdale can provide the passowrds
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>Any Atos employee can self register to this portal.
IMPORTANT NOTE - The prototype is live. If you are testing the system remember that meeting requests WILL BE SENT to the sponsor you nominate.


502
Bad Gateway
It looks like the server you're trying to access isn't responding.
Please do not adjust your browser.
Click here
to go back to home page.


Copyright Bruce Wilcox<EMAIL_ADDRESS>www.brilligunderstanding.com
Revision 4/24/2022 cs12.1
Pattern matching information was introduced in the Beginner manual and expanded in the Advanced User Manual. Since pattern matching is of such importance, this concise manual lists everything about patterns in one place, including patterns not listed in the Advanced manual.
NOTE: despite the extraordinary range of weird matching abilities, almost all of my normal code is based on one of three patterns:
# rule 1
u: (![plastic] << bag trick >>)
# rule 2
u: (I * love * you)
# rule 3
t: What fruit do you like?
a: (~why)
a: (orange)
a: (apple)
a: (~vegetables)
Rule 1 - searches for key words in any order. While there is a normal
order to questions, e.g., where do you live, one can ask
you live where? so handling arbitrary order is generally
valuable. Just have all the keywords you need to detect a meaning and
use ![...]
to get rid of interpretations you don’t
want.
Rule 2 - requires an order when both first person and second person pronouns are involved, since order will matter.
Rule 3 - uses simple keywords or concept sets in rejoinders, since the context of the gambit constrains the input so highly.
Pattern matching can be done not just in a rule’s pattern component
but also in its output component, within an if
statement,
e.g.:
if ( PATTERN _~number ) { print( _0) }
That is, if the first word in the test condition is the word
PATTERN
, the rest is treated as a standard pattern of a
rule (not using AND
OR
etc). You can capture
data here or do anything a normal pattern does.
A pattern consists of tokens. By default, any normal word in canonical form can match any form of the word, so he in a pattern can match him, he, his. A pattern aborts when a token fails to match unless allowed to not match.
The performance cost of a pattern generally is linear in the number of tokens processed. That means these two rules take the same time to match (other than the imperceptable time difference to read the longer token).
u: (apple)
u: (~ten_thousand_names_of_fruits)
The system tracks current position in the sentence as it matches.
The first token of a pattern is allowed to match anywhere in the sentence. After that normally tokens are matched against words in consecutive order in the input. If a pattern starts to match and then fails, the system is allowed to retry matching later in the sentence once. It does this by freeing up the first matching word/concept token and letting it rebind later.
Given this rule:
u: ( I like apple )
The input Do you know that I like oranges and I like apples would match as follows.
The first pattern token I
would match the first
I partway into the sentence (because it is allowed to match
anywhere).
The next pattern token like
is required to match the
next input word in the sentence, which it does.
The third pattern word apple fails to match oranges. We just failed. But we have one retry left.
So I is sought deeper in the sentence and matched.
like
matches like and apple
matches
apples. So we match.
Had that not matched, no more retries exist so the failure sticks. There are tokens you can use that alter the rules/location around current position.
s:
?:
A responder beginning with s:
or ?:
implictly is testing that the sentence is a statement or a question. It
is built in even before the pattern. All other rules are not immediately
sensitive to kind of sentence.
~concept
$var
%sysvar
_0
@0
^var
?
~
Basic pattern matching is against words or concepts. Does this word or concept exist?
u: ( this ~animal )
matches this dog or this dogs but not this is my dog
You can also ask if a user variable is defined just by naming it:
u: ( $myvar help )
this only matches if input has help and $myvar
is not null.
one would not ask if they are defined (they almost always are) but would use in a relation instead.
Similarly, _0
by itself in a pattern means is it
defined, that is, not null.
u: ( _{apple orange} _0 )
matches only if apple or orange got matched. And @0
by
itself means does this fact-set have any facts stored in it.
You can also reference an argument to a function call, and its value will be used to decide what to do.
?
A stand-alone ?
means is this sentence a question.
!?
!?
would test if it is not a question.
~
A stand-alone ~
means the current topic is already on
the pending topic list (was recently considered an active topic).
(
)
[
]
{
}
<<
>>
(
… )
Parens mean the tokens within must be found “in sequence”. The notation of a pattern starts with parens, but has the unusual property of allowing the match to occur anywhere within the sentence, not just at the start. Any nested parens do not have that property, and still require in sequence.
u: ( this (is my) pattern)
matches this is my pattern and not this sometimes is my pattern
[
… ]
Brackets mean match one of contained tokens, in the order given. A bracket list tries all its members in sequence, stopping when it finds a match. For the input I go home for Christmas this will not match:
u: ( [~noun ~verb] * home )
because ~noun
will match to home and then
home cannot be found later. On a retry, ~noun
will
match to Christmas. Since ~noun
can match multiple
times, ~verb
never gets tried.
You can composite things like:
u: ( [ apple pear (favorite fruit) cherry ] )
to match I eat pear and my favorite fruit, but this form is unlikely to be used in normal CS.
Note that [ … ]
and ~concept
are similar
but different in important ways. Matching ~concept
is
faster than the corresponding list inside []
because naming
the concept only requires one token. But it takes more memory to store
the concept than it does to put the words inside the
[]
.
The other fundamental difference is in position. Words in
[]
are matched in the order given, possibly moving your
position mark deep into the sentence.
Words in a concept are all matched simultaneously,
so which one is found first in the sentence is what sets the position.
For an input I like beer but not wine
u: ( I like * ~drinks )
this would match beer if beer and wine are in that concept in any order.
u: ( I like * [wine beer] )
this would match wine even though it is farther in the sentence.
{
… }
Braces means match one of the contained tokens if you can, but don’t fail if you don’t.
Using {}
inside of angles is pointless (unless you put
an underscore in front to memorize something) because it makes no
difference to matching whether or not you had the {}
content.
Braces do not align position within a sentence. They are normally used to assist in positional alignment by swallowing words.
u: ( I go to {the} market )
matches both I go to the market and I go to market.
If you use underscore before braces to memorize the answer found,
then when no answer is found the match variable is set to
null
(no content) but it is set.
<<
…
>>
Angles mean match all of the contained tokens in any order.
Putting *
in this kind of pattern is illegal because it
has no meaning.
Position is not relevant anyway. Position is freely reset to the start following this sequence so if you had the pattern:
u: ( I * like << really >> photos )
and input photos I really like then it would match because
it found I * like then found anywhere really
and
then reset the position freely back to start and found
photos
anywhere in the sentence.
*
*~2
*3
*-2
*~2b
Wildcards allow you to relax the positional requirements for
matching. The classic wildcard *
allows you to have zero or
more words between other tokens in a pattern.
u: ( I * you )
matches I love chicken and hate you as well as I you they.
You can limit the unlimited range by adding ~n
after it.
So *~1
means 0 or 1 words may intervene.
*~2
is what I commonly use to restrict a range. This
allows a determiner and an adjective to fit before a noun, for example,
but not allow a pattern to match weirdly.
u: ( I like *~2 cat )
matches I like my cats or I like a yellow cat.
*~2b
is similar to *~2
except it tries to
match bidirectionally. First it tries to match behind it, and if that
fails, it tries forward (like *~2). You may not follow a bidirectional
wildcard with either {
or (
.
You can also request a match of a specific number of words in
succession using *n
. *1
means get the next
word. If you are already positionally on the end of the sentence, this
match fails.
If you aren’t sure how many words are left, you could do something like this:
u: ( apple _[*4 *3 *2 *1] )
which will grab the next 4 or 3 or 2 or 1 words, depending on how many are available.
Generally done with an underscore in front to memorize the sequence.
*-2
is like *2
, only it matchs backwards
instead of forwards. Valid thru *-9
.
!
and !!
and ‘!-’!x
means match only if x is not found anywhere in the
sentence later than where we are:
u: ( !not I love you )
This pattern says the word not cannot occur anywhere in the sentence.
!!x
means match only if x is not the next word.
This pattern says the word not cannot occur anywhere before us in the sentence.
!-x
means match only if x is not any prior word.
'
While CS normally matches both original and canonical forms of words when you give a pattern word in canonical form, you can require it only match the original form by quoting it.
u: ( I * 'take it )
does not match I am taking it
Likewise in a relation where you use a match variable, quoting it means use only its original value.
u: ( _~fruits '_0==apple )
matches I like apple but not I like apples
\
You can tell CS that a token should be considered a token, not a
special form, by putting a \
in front of it.
This applies to single characters like: \[ \]
and it
also applies to relational tokens like \tom=*
which means
do not treat this as a relational test, but instead as a token whose
name is wildcarded.
Note that the \
does not suppress detecting the
*
in a word and therefore allowing variant spelling.
There are sequences of words that have a specific meaning and are treated as a single word, e.g., batting cage.
In a dictionary these are often represented using an _
instead of a space, e.g., batting_cage.
When CS tokenized your input, it automatically converts your separated input words into ones with underscores in them when appropriate.
They are no longer single words, but instead a single composite word. This would normally mean that
u: ( batting cage )
would not match. But the script compiler does the same tokenization thing, so your actual internal pattern looks like:
u: ( batting_cage )
For clarity, it is recommended that when you know you are dealing with a composite word, you use the underscore notation.
Sequences of words can also be designated using double quotes.
u: ( "batting cage" )
CS converts a quoted string into the same underscore notation. The distinction between the two is generally one of documentation.
I use quoted strings for phrases to highlight the intention that they are a phrase. I also use them for multiple word proper names like Eiffel Tower.
It is particularly important to use the quoted notation when punctuation is embedded in the name like John’s Apple Pie because knowing where to put underscores when punctuation is involved is tricky.
By using quotes, you tell the system to manage things appropriately
(John_'s_Apple_Pie
)
When using the quoted notation, the system will actually try to match original and canonical, just like with ordinary words. If all words in phrase are canonical, the system will match any form of each word.
If one is not canonical, it can only match the original form.
u: ( "king of the jungle" )
cannot match kings of the jungle because the in pattern is not canonical.
u: ( "king of a jungle" )
but the above rule can match kings of the jungle since all words in the quote are canonical.
_
Placing an underscore means to memorize what was matched onto a match
variable. Match variables are allocated in sequence in a pattern,
starting with _0
and increasing to _1
etc for
each memorized match.
The system memorizes the original word, the canonical word, and the position in the sentence of the match.
>
<
?
==
!=
<=
>=
You can test relationships by conjoining a token with a relationship operator and another token, with no spaces. E.g.,
u: ( I am _~number > _0>18 ) You are of legal age.
The relationship operators are:
| operator | meaning |
|---|---|
== |
equal |
!= |
not equal |
< |
less than |
<= |
less than or equal to |
> |
greater than |
>= |
greater than or equal to |
& |
bit anded results in non-zero |
? |
is member of 2nd arg concept or topic or JSON array. If no argument occurs after, means is value found in sentence |
Using a compare with two text strings (not numbers) will evaluate based on case-independent alpha sorting.
For comparison against a number (< <= > >=) a null value will be treated as the number 0.
The ?
operator has two forms. xxx?~yyy
will
look for actual membership in the set whereas _n?~yyy
will
only see if the location of match detection of _n
is the
same as a corresponding match location for the concept. If the concept
has not been marked, then obviously no match is found.
Note: You can put !
before the tokens instead of using
!=
and !?
. E.g.,
u: ( _~noun !_0?~fruit ) if the noun is not in fruit concept
The stand-alone ?
is used with variables for dynamic
matching.
While you cannot do memorization in front of a comparison (because no
positional data is gained) you can in front of the ?
operator since finding where in the sentence something is will return a
position for memorization.
u: ( $var? )
means is the value of $var
found in the sentence
anywhere
Note that when $var
is a normal word, that is simple for
CS to handle.
If $var
is a phrase, then generally CS cannot match it.
This is because for phrases, CS needs to know in advance that a phrase
can be matched.
If you put take a seat as a keyword in a concept or topic or pattern, that phrase is stored in the dictionary and marked as a pattern phrase, meaning if the phrase is ever seen in a sentence, it should be noticed and marked so it can be matched in a pattern.
But if it is merely in a variable, then the dictionary is unaware of
the phrase and so $var?
will not work for it.
There is also a ?$var
form, which means see if the value
of the variable is findable. The value can be either a word or a concept
name.
You can directly assign to any variable from any other value using
:=
. You can even do arithmetic for these assignments (:+=
:-= “*= :/= :&= and any of the other numeric assignment operators)
.
$value = 5
( _some_test $value:=5 $value1:=_0 $value2:='_0 $value3:=%time )
( _some_test $value:+=5 $value1:-=_0 )
If you want to do function call assignment, you can do this:
$value:=^"^function(foo d)"
The reason you have to do an active string here, is because normally spaces break apart tokens, and a pattern token involving a function needs to have all arguments part of the same token. Hence assigning from an active string, where the double quotes around it prevents the token from breaking apart.
\
If you want to match a reserved punctuation symbol like
[
or (
, you must escape it by putting a
backslash in front. This is commonly done in matching out-of-band
information.
u: ( < \[ * \] ) ^respond(~determine_oob)
One also uses escape if you want to know if the sentence was punctuated with an exclamation.
s: ( \! )
means user did something like I love you!.
You may use either ?
or \?
when asking if
the sentence has a question in it. You would generally only do this in a
rejoinder.
If you join a word (or a concept) and one or more concepts, that represents the intersection of them. e.g., (animalstasty) will reference all animals considered tasty.
Note, you cannot use word~1 (meaning specification) or word~n (pos-tag specification) on your first word.
^xxx(...)
You can call a function from within a pattern. If the function returns a failure code of any kind, the match fails. If the function is a predefined system function, you are allowed relation operators on the result as well.
u: ( ^lastused(~ gambit)>5 )
NOTE:
User defined functions (patternmacros
) do not allow
relational operators after them.
Patternmacros do not generate answers. They are treated as in-line additional pattern tokens.
Patternmacro: ^testuse(^value) _~noun _0==^value
u: ( ~noun ^testuse(apple)) # matches "I like pear and apple"
A powerful use of function calling is to call
^respond(~topicname)
in a pattern. The topic can match
something and set up a variable for further guidance. E.g.,
u: ( ^respond(~finddelay) $$delay ) Wait for $$delay.
~finddelay
can hunt for time referred to in seconds,
minutes, hours, etc, or in words like next week or tomorrow or whatever
complex matching you want to do.
*ing
bottle*
8bott*
You can request a match against a partial spelling of an original word (not its canonical alternative) in various ways.
If you use *
somewhere after an alpha, it matches any
number of characters.
u: ( sag*us )
matches many misspellings of sagittarius.
If you use *
followed by an alpha, you get anything as a
prefix followed by what you request.
u: ( *tha )
matches Martha.
If you put a number in front, it means the word must be exactly that many characters long, matching your pattern.
u: ( 6sit* )
matches sitter.
When using an *
word, you can use .
to
indicate exactly one character of any value.
u: ( sit*u.tion )
matches situation.
<
>
@_0+
@_0-
@_0
When you put <
in your pattern, it doesn’t actually
match anything. It means “reset position” to the start of the
sentence.
u: ( < I love )
matches I love but not do I love.
When you put >
in your pattern, it does not alter
your position, but it tries to confirm you are on the last word of the
sentence.
u: ( I * > )
in this pattern >
is redundant, since *
would match to the end of the sentence anyway.
You may also use !>
to ask that we NOT be at the end
of the sentence.
@_1+
says to set the position to where the given match
variable (_1
) matched. Positional sequencing will continue
normally increasing thereafter.
You can suffix the match variable with -
instead, to
tell CS to begin matching in reverse order in the sentence, i.e.,
matching backwards to the start of the sentence.
When you use +
, the position starts at the end of the
match. When you use -
, the position starts at the start of
the match.
u: ( _home is @_0- pretty )
matches my pretty home is near here.
Note when you use -
for reverse matching, the behavior
of <
and >
changes. >
sets a position and <
confirms it instead of the way it
is for +
.
When you omit either + or -, you create a matchable anchor like
@_0
. It represents what was found at that position, and
during the pattern must also match at that location now.
u: ( _@0 is @_1 )
The above pattern says that the word is
must be
precisely found between the locations referenced by @0
and
@1
.
@retry
Normally one matches a pattern, performs the output code, and if you want to restart the pattern to find the next occurrence of a match, you use ^retry(RULE) or ^retry(TOPRULE). Well, if your pattern executes @retry as a token, it will retry on its own without needing to execute any output code. Useful in conjunction with ^testpattern.
:testpattern
The system inputs the sentence and tests the pattern you provide against it. It tells you whether it matched or failed.
:testpattern ( it died ) Do you know if it died?
Some patterns require variables to be set up certain ways. You can perform assignments prior to the sentence.
:testpattern ($gender=male hit) $gender = male hit me
Typically you might use :testpattern
to see if a subset
of your pattern that fails works, trying to identify what has gone
wrong. You can also name an existing rule, rather than supply a
pattern.
:testpattern ~aliens.ufo do you believe in aliens?
:prepare
Since CS may revise your input for various reasons, to know why a pattern fails you may need to know what actually say.
Using :prepare
will tell you what the final input words
were, and what concepts got marked.
:prepare This is a sentence.
:verify
In general all of your responders and rejoinders should have a sample input comment above them.
#! Do you believe in dogs?
?: ( << you believe dog >>) I do.
This allows you to do
:verify ~mytopic pattern
and have the system test if your rule would match your input.
:trace
You can get a trace of various system functions.
:trace pattern
will show you pattern matching and match variable binding. Also
useful if done before :testpattern
.
Sometimes you want to supplement the marking of concepts done by
adding your own marks. This is particularly useful handling idioms where
no keyword exists. I set $cs_prepass
to be a topic which
looks for idioms.
?: ( < what do you do > ) ^mark(~work)
This will cause the work topic to react later as though one of its keywords was given.
Likewise sometimes you want to disable some marking. For example, chocolate is both a flavor and a color. To avoid going to the color topic incorrectly I might do this:
u: ( << _chocolate [taste eat] >> ) ^unmark(~colorTopic _0)
If the above rule detects chocolate in the apparent context
of eating, it will unmark any reference to ~colortopic
found at the location of the word chocolate.
The pattern matching system of ChatScript has esoteric abilities. I was asked if I would implement an additional one that would look something like this:
<< green nose mucus >>~3
which he wanted to mean: find all those words, in any order, with each word after the first within a gap range of 3 from the previous word.
So it could recognize: green is the nose with my mucus or my nose puts forth green mucus and not match while green is my favorite color or I don’t want to see it in my nose mucus.
I replied it could probably already be done in CS as it stood, and a few minutes later had whipped up code to do that. Your advanced challenge, if you care to think about it and really warp your mind, is to think of a way to do it yourself. That will prove you really understand what can be done in pattern matching. Answer is on the next page.
patternmacro: ^nearbyword(^word)
[
(@_0+ *~3 _^word ^eval(_0 = _1))
(@_0- *~3 _^word ^eval(_0 = _1))
]
The macro contains two choices, a sequence that looks forward from
where you are and a sequence that looks backwards. Using a nested
()
the system will effectively treat that as a single
match, which makes it a single token to be used in a []
choice.
Whichever ()
finds the next word, it memorizes where it
is, then sets the current _0
location to the new word and
the choice ends.
While you can’t do code execution directly in a pattern, and you
can’t call out to user-defined outputmacros, you can call out to system
functions, and ^eval
lets you do any amount of normal code
execution. So this allows us to assign the new match variable to the
old. And assigning match variables means assigning all of their
attributes, including original value, canonical value, and actual
position data.
topic: ~test()
u: ( _green ^nearbyword(nose) ^nearbyword(mucus)) You have a disgusting nose.
The test pattern therefore, finds the first word and sets the current
_0
location. Then it uses the macro to find the next word
and change location, and then the next word.


Welcome to JavaScript DOM
This is the first DIV
Span 1!
Span 2
Span 3!
Span 4
Span 5!
Span 6
Span 7!
Hello World
Link One
Link Two
Link Three
Link Four
Link Five
Link Six
Link Seven


Created By: Anand Angalig
GitHub Username/URL:: https://github.com/anandangalig
Enter any number as the PING, and we will return a PONG by counting from 1 to your number with three exceptions:


Happ
me
Filter Posts?
Triggers:
Profanity
PTSD
Drug Use
Sexual Assault
Child Abuse
Self-harm
Contact Email:


South African airways strike enters day 2
South African Airways (SAA) and unions on Saturday met for talks on the troubled state-run carrier; which hopes to bring an end to a crippling strike that it says could push it to collapse.
Unions representing more than half of SAA’s workforce called the strike from Friday, forcing SAA to cancel hundreds of flights. According to the protesters they would continue until their demands were met.
The airline said the action would cost it 50 million rand ($3.36 million) per day.
The talks will be mediated by dispute resolution body ;The Commission for Conciliation, Mediation and Arbitration (CCMA). The unions’ demands include an 8% wage increase, and they also object to SAA’s plan to cut over 900 jobs.
SAA, which hasn’t made a profit since 2011, needs to cut costs to turn around – a mammoth task complicated by the huge sensitivity of job cuts in a country where unemployment is already close to 30%.
Phakamile Hlubi Majola, spokeswoman for the National Union of Metalworkers of South Africa (NUMSA), one of the unions that called the strike, said they also want SAA to commit to bringing costly outsourced services back in house, which are blowing a substantial hole in SAA’s budget.
SAA’s woes have left it reliant on state bailouts to survive, becoming a source of frustration for taxpayers who have forked out more than 30 billion rand since 2012 as well as for a cash-strapped government already propping up other ailing state firms.


Viewable with any Browser
DADS bears the "Viewable with any Browser" icon because the authors of
DADS agree with this campaign. We are participating in this effort by
avoiding tricks that may influence the portability of this
website. We are aware that some pages may look better in some browsers than
others, but are confident all our pages are readable with the vast majority of
browsers in use.
The following highlights some unavoidable problems and how we address
them:
- Fonts are not standardized. Most browsers are dependent on fonts
that are globally available on the machine where the browser is
running. Furthermore, different browsers have different heuristics
to determine the fall-back font to use if a specified font is not
available. We aim to achieve maximum consistency across browsers,
we do not make extensive use of fonts. When we specify fonts, we use
only fonts that are widely used and hence more likely to be
available. We explicitly specify a fall-back chain of fonts down to the best
known generic font in the font-family we prefer.
- Authors of websites as well as readers can specify style
preferences. A user's style preferences my override style
specifications for our site and style preferences that were
specified for previously viewed sites may have an effect on how our
site is rendered. We aim to minimize the possibility that these side
effects have a negative impact on the viewability of our site by
minimizing the number of styles we rely on and by resetting styles
that we are aware of that may have a harmful impact on our site.
If you experience any difficulty viewing any information in DADS in
your preferred way, we would like to know about it. include(`Pages/bitsFixDefn.m4')
The following is a list of other things we do to support the
cross-platform and cross-browser viewability of this site:
- Formatting specific settings are set in a cascading style sheet. If a
browser does not support cascading style sheets, the page will be
rendered with default settings for all tags, which is in most cases
the safest option.
- Formatting specific settings are kept to a minimum and only used
when we have confirmation that it is supported by most browsers. A
good reference we use for this purpose is at:
http://reference.sitepoint.com/css
- We minimize the use of images. When we use images, the dimensions of
the image is specified in pixels, an alternate text describing the
images is included that can be displayed if for some reason the
image is not shown. GIF format is widely supported, however, we
refrain from using images in GIF format in support of the GNU
guidelines. We prefer JPEG format. It seems to be
the most widely supported image format that has not been compromised
by copyright issues.
- We minimize the use of tables. Often tables are unreadable in browsers that
do not support tables. Instead we display tabular information as
preformatted text using mono-spaced fonts.
- We use lower case in HTML tags. Although, HTML
is not case sensitive, XHTML requires all tags to be in
lowercase. This improves the readability as well as the portability
of our code.
- We use alphabetical characters and digits when naming our
directories and files to minimize errors when other sites point to
our site. We also encode reserved characters in URLs specified in
outgoing links using their hexadecimal formats.
Updated
Mon May 21 08:27:45 2018
by Paul E. Black


Implements a spatiotemporal boundary detection model with a dissimilarity
metric for areal data with inference in a Bayesian setting using Markov chain
Monte Carlo (MCMC). The response variable can be modeled as Gaussian (no nugget),
probit or Tobit link and spatial correlation is introduced at each time point
through a conditional autoregressive (CAR) prior. Temporal correlation is introduced
through a hierarchical structure and can be specified as exponential or first-order
autoregressive. Full details of the package can be found in the accompanying vignette.
Furthermore, the details of the package can be found in "Diagnosing Glaucoma
Progression with Visual Field Data Using a Spatiotemporal Boundary Detection Method",
by Berchuck et al (2018), <arXiv:1805.11636>. The paper is in press at the Journal of
the American Statistical Association.
| Version: |
1.0.4 |
| Depends: |
R (≥ 3.0.2) |
| Imports: |
graphics, grDevices, msm (≥ 1.0.0), mvtnorm (≥ 1.0-0), Rcpp (≥ 0.12.9), stats, utils |
| LinkingTo: |
Rcpp, RcppArmadillo (≥ 0.7.500.0.0) |
| Suggests: |
coda, classInt, knitr, rmarkdown |
| Published: |
2018-12-04 |
| Author: |
Samuel I. Berchuck [aut, cre] |
| Maintainer: |
Samuel I. Berchuck <sib2 at duke.edu> |
| License: |
GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| NeedsCompilation: |
yes |
| Materials: |
NEWS |
| CRAN checks: |
womblR results |


--- layout: default ---
A community-curated collection.
Characterizing and contrasting service meshes and related technologies.


The Starting location is the directory where ReSearcher will open up to upon launching. For more information regarding browsing your library, see: Browsing.
The default Starting location is the user's 'home' directory: %userprofile%
Shown in Figure 1 is the panel for editing the Starting location.
To type in a location: click on the input box below the Open to: heading (shown in Figure 1).
Either begin typing or paste in the path from the clipboard (perform a right-click and select Paste or use the keyboard shortcut CTRL + V
).
To browse for a directory on your machine: click on the ... button to the right of the input box to open the Browse for folder dialogue box (shown in Figure 2).
Once you have selected the desired folder: click on the OK button to close the dialogue box.
Or to cancel (and leave the Starting location unchanged): click on the Cancel button.


Eye of Argos:
You've vanquished the dreaded Daimon, but he's not gone forever.
Someday, he shall rise and threaten the peace of the world again.
I pray when he does that we have many heroes like you.


{{#__}}Apache CouchDB, commonly referred to as CouchDB, is an open source database that focuses on ease of use and on being "a database that completely embraces the web".[1] It is a NoSQL database that uses JSON to store data, JavaScript as its query language using MapReduce and HTTP for an API.[1] One of its distinguishing features is easy replication. CouchDB was first released in 2005 and later became an Apache project in 2008.{{/__}}


Enumerations | |
| enum | CSL_armGicTrigType_t { CSL_ARM_GIC_TRIG_TYPE_HIGH_LEVEL, CSL_ARM_GIC_TRIG_TYPE_LOW_LEVEL, CSL_ARM_GIC_TRIG_TYPE_RISING_EDGE, CSL_ARM_GIC_TRIG_TYPE_FALLING_EDGE } |
| Enumerates the types different trigger types. More... | |
| enum | CSL_ArmGicBinPointVal_t { CSL_ARM_GIC_BPVAL0 = 0U, CSL_ARM_GIC_BPVAL1 = 1U, CSL_ARM_GIC_BPVAL2 = 2U, CSL_ARM_GIC_BPVAL3 = 3U, CSL_ARM_GIC_BPVAL4 = 4U, CSL_ARM_GIC_BPVAL5 = 5U, CSL_ARM_GIC_BPVAL6 = 6U, CSL_ARM_GIC_BPVAL7 = 7U } |
| Binary point value for priority grouping. More... | |
| enum | CSL_ArmGicIntrSupport_t |
| enum | CSL_ArmGicPriorLevel_t { CSL_ARM_GIC_PRIOR_LEVEL_256 = 0x0U, CSL_ARM_GIC_PRIOR_LEVEL_128 = 0x1U, CSL_ARM_GIC_PRIOR_LEVEL_64 = 0x2U, CSL_ARM_GIC_PRIOR_LEVEL_32 = 0x3U, CSL_ARM_GIC_PRIOR_LEVEL_16 = 0x4U } |
| Binary point value for priority grouping. More... | |
Binary point value for priority grouping.
Interrupt support cases.
Binary point value for priority grouping.
| Enumerator | |||
|---|---|---|---|
| CSL_ARM_GIC_PRIOR_LEVEL_256 |
Loads the GP Timer Period Register High.
| ||
| CSL_ARM_GIC_PRIOR_LEVEL_128 |
Loads the GP Timer Period Register High.
| ||
| CSL_ARM_GIC_PRIOR_LEVEL_64 |
Loads the GP Timer Period Register High.
| ||
| CSL_ARM_GIC_PRIOR_LEVEL_32 |
Loads the GP Timer Period Register High.
| ||
| CSL_ARM_GIC_PRIOR_LEVEL_16 |
Loads the GP Timer Period Register Low.
|
| enum CSL_armGicTrigType_t |


Spoilers: Corrie reveals sad death tragedy for Roy Cropper
Roy Cropper (David Neilson) hasn’t long lost his mother Sylvia and he is about to face further tragedy when another family member dies – just days after they meet. The Coronation Street cafe owner has discovered that he actually has a long lost brother as a result of an affair Sylvia had – and they meet through playing online Scrabble together.
Roy is keen to get to know Richard and the pair end up having a lot in common – including a shared enthusiasm for steam trains. But the joy is short lived as Richard’s daughter Nina has been forced to make it clear to Roy that Richard is terminally ill and doesn’t have long left.
That said, Richard is determined to make the most of the opportunity to get to know Roy and heads to Weatherfield to visit, despite Nina worrying about his ailing state. As his carer, Nina is all that Richard has and vice versa – so she is harbouring some resentment to Roy as she feels the excitement and the exertion aren’t good for her dad.
Advertisement Advertisement
As they visit Roy at the cafe, Roy offers to help them both as much as possible and be there for them but Nina is reluctant to accept his help. Roy later visits them and is horrified to see how frail Richard looks as he continues to deteriorate.
Nina blames Roy for Richard’s setback and he is overwhelmed by guilt and later, he admits to Carla Connor (Alison King) that he has made a huge decision – he will take Nina in and look after her after Richard’s death.
Roy returns to the flat and offers to help Nina move an air condenser but she is still adamant she can handle everything alone and injures herself in the process. As Roy gets the opportunity to step in and care for Richard, he realises the toll that it is taking on Nina and he takes it upon himself to call adult social services, leaving Nina furious.
As Roy’s interference with Richard’s carer leads to them quitting their job, Nina tells Roy he has made everythign worse but he is not giving up and decides he must spend more time with them so offers Aggie more shifts at the cafe.
As Roy makes it clear he is taking over Richard’s primary care, will stubborn Nina submit and accept his help?
One to watch: Wednesday 27th October at 7:30pm on ITV.


The European IoT Analytics Summit is a meeting place for both academia, government and industr y to discuss upcoming challenges of IoT data mining, machine learning and data science methods.
This event is organized and funded by the Big Data and Market Insights Chair at Institute Mines-Telecom.
The Internet of Things (IoT), the large network of physical devices that extends beyond the typical computer networks, will be creating a huge quantity of data in real time in the next future. The realization of IoT depends on being able to gain the insights hidden in the vast and growing seas of data available. Since current approaches don't scale to Internet of Things (IoT) volumes, new systems with novel mining techniques are necessary due to the velocity, but also variety, and variability, of such data. There is a great deal of interest in analyzing data from IoT.
The main goal for this year's event is to bring together top researchers from academia, as well as top data scientists from industry and government with the special focus of evolving infrastructures for IoT.
EuroIoTA 2017 will take place in Porto on November 24th.
The topics of interest include, but are not limited to:
+ IoT Data Analytics
+ Data Mining for IoT
+ Machine Learning for IoT
+ IoT & Data Stream Mining
+ Infrastructures for IoT
+ Communication Protocols
+ IoT for manufacturing
+ IoT Data Analytics applications
Smart cities
Healthcare
Energy/Smart Grids
Environment
Intelligent transportation systems
Green mobility
08:30 - 09:00 | Reception
09:00 - 09:15 | Opening
09:15 - 10:15 | Andy Smith (SAS) - The Role of Analytics in Enabling Smart Cities
10:15 - 10:45 | Coffee break
10:45 - 11:45 | Gille Betis (OrbiCité) - MaaS – Mobility as a Service, a new paradigm implementation
11:45 - 12:15 | Michel Ferreira (Geolink) - IoT in Cooperative Vehicles
12:15 - 14:00 | Lunch
14:00 - 15:00 | Michele Berlingerio (IBM Research Ireland)- Mining and leveraging traces of our digital selves
15:00 - 15:45 | Luís Moreira-Matias (NEC Laboratories Europe) - Real-Time Mobility Data Mining
15:45 - 16:15 | Nicolas Kourtellis (Telefonica) -Analyzing Data Streams Online: Process Challenges and Privacy Aspects
16:15 - 16:45 | Coffee break
16:45 - 17:15 | Raul Gomes Azevedo (WeDo) - In the mist of the Global Digital Transformation
17:15 - 18:00 | Ana Aguiar (Future Cities) - IoT for Smart Cities
18:00 | Closing
Registration is now suspended due to room limitations.
Please, visit this website regularly for possible updates.
Albert Bifet (Chair)
Telecom ParisTech
Michele Berlingerio
IBM Research Ireland
Talel Abdessalem
Telecom ParisTech
Pascal Thubert
Cisco
Joao Gama
University of Porto
Rosaldo Rossetti
University of Porto
João Moreira
University of Porto
Ricardo Sousa
LIAAD/INESCTEC (web chair)


Tailscale’s website reads:
A secure network that just works
Zero config VPN. Installs on any device in minutes, manages firewall rules for you, and works from anywhere.
gokrazy-based devices are no exception! This guide shows you how to use Tailscale with gokrazy.
Tailscale’s networking will come in handy when accessing your gokrazy server remotely (no static DHCP leases, port-forwarding and DynDNS required!), or even to secure your communication when gokrazy is connected to an unencrypted WiFi network.
We need to specify the following flags for the tailscaled
daemon (see
“Per-package configuration” if you’re unfamiliar
with this mechanism):
mkdir -p flags/tailscale.com/cmd/tailscaled
echo '--state=/perm/tailscaled/state' > flags/tailscale.com/cmd/tailscaled/flags.txt
echo '--tun=userspace-networking' >> flags/tailscale.com/cmd/tailscaled/flags.txt
tailscaled
requires the --state
flag, so we need to set it
explicitly. /perm/tailscaled
is the working directory of the tailscaled
process and will contain the tailscaled.sock
socket, so it makes sense to
place the state file into the same directory.
The --tun=userspace-networking
flag selects the Userspace
networking mode.
It would be nice to use the tun
-based networking eventually, but currently
Tailscale requires components that gokrazy does not provide for tun
mode. For
accessing the services on your gokrazy installation, the Userspace networking
mode works fine, though :)
In your gokr-packer
invocation (see Quickstart if you don’t
have one yet), include the Tailscale daemon and CLI Go packages:
gokr-packer \
-update=yes \
github.com/gokrazy/hello \
github.com/gokrazy/breakglass \
github.com/gokrazy/serial-busybox \
tailscale.com/cmd/tailscaled \
tailscale.com/cmd/tailscale
Log in to your gokrazy device interactively using
breakglass, change to the
/perm/tailscaled
directory and run tailscale up
to print the authentication
link:
% breakglass gokrazy
breakglass# cd /perm/tailscaled
breakglass# /user/tailscale up
(If you only want to connect to services on your gokrazy device, you don’t need this step.)
To make the github.com/stapelberg/dr
package able to connect to addresses on
the tailscale network, we need to first enable tailscaled
’s HTTP
proxy:
echo '--outbound-http-proxy-listen=localhost:9080' > flags/tailscale.com/cmd/tailscaled/flags.txt
And then set the proxy environment variables:
mkdir -p env/github.com/stapelberg/dr
echo 'HTTPS_PROXY=localhost:9080' > env/github.com/stapelberg/dr/env.txt
echo 'HTTP_PROXY=localhost:9080' >> env/github.com/stapelberg/dr/env.txt


RowPresenter
RDO.WPF automatically maps a collection of DataRow objects into a collection of RowPresenter objects. RowPresenter contains row level presentation logic which can be consumed by view elements such as RowView, or can be used as data binding source by providing both data values and view states. RowPresenter does not aware any view elements except holding a reference to its associated RowView.
Data Value Access
You can access data values via the following APIs of RowPresenter class:
| API | Description |
|---|---|
| GetValue | Gets the data value from specified column. |
| EditValue | Enters the editing mode and change value for specified column. |
These APIs can be used to provide data values as data binding source.
Row Level View States
Each RowPresenter object contains the following row level view states:
- IsSelected: Indicates whether this row is selected.
- IsCurrent: Indicates whether this row is current row. Only current row can be in editing mode.
- IsEditing: Indicates whether this row is in editing mode. Editing of the row can be saved or cancelled. If this property is true, the IsCurrent property must also be true.
- IsVirtual: Indicates whether this is a virtual row for inserting. Normally this row is displayed as an empty row at the end of the data grid.
- IsInserting: Indicates whether this row is in inserting mode. If this property is true, the property of IsVirtual and IsEditing are also be true.
- IsExpanded: Indicates whether this row is expanded with its Children.
These view states, together with others, can have different presentations, either via data binding or directly consumed by specific view element such as RowView. For example, the following shows the different presentations for IsSelected property:


Dr. Mario World getting new stages soon
by My Nintendo News AdminDr. Mario World for mobile devices is currently experiencing maintenance, but once it is all over, new stages will be added to the smartphone game. These levels are thought to be from World 9 Area 2 and include Stages 341 through 360. No new doctors are thought to be present this time but we shall endeavour to keep you updated if this changes.


| |
INTRO
DEF FILES
SHIP DESIGN
WEAPON DESIGN
CUSTOM MISSIONS
|
Basics
All of the files that make up a custom ship design must be placed in a
subdirectory of the Mods\Ships directory that bears the name of the ship
design. For example, to create a new destroyer class of starships called
the "Warrior", start by creating a directory named
Mods\Ships\Warrior . All models, texture bitmaps, and
other data files for the Warrior must be placed in this directory.
The properties for your ship design are defined in a text file called a
"Ship Definition File". This file can be created with any text editor
(e.g. notepad) and must have the same name as the ship design. For
our Warrior example, the ship definition file would be
Mods\Ships\Warrior\Warrior.def . The ship definition
file contains all of the physical properties of the ship (mass, hull
strength, turn rate, lift, drag, etc.) and also names the 3D mesh files
that define what the ship looks like.
All physical objects in Starshatter are modeled using 3D mesh files
created by the low-poly editor Magic, written especially for the game.
Magic stores meshes in files with .mag extensions. You can
use Magic to create ship designs from scratch, or you can import existing
designs created in another 3D modeling tool (3DStudio, LightWave, Maya,
Milkshape). Magic uses the popular Wavefront OBJ ASCII format for
importing geometry from 3rd party modeling tools. You can download a free,
unsupported copy of Magic 1.1 from the Downloads
Page of the official website.
Texture maps for your ship design must be stored in PCX format.
Textures must be square powers of two (e.g. 64x64 or 256x56) in size. You
should store your textures in 24 bit RGB format. You can use Adobe
Photoshop, JASC Paint Shop Pro, or any other bitmap graphics editor to
create textures for your models. Ship
Definition File
The ship definition file is a text file that has a .def
extension. All definition files in Starshatter use the same C-like
syntax. The ship definition file defines the logical,
graphical, physical, and functional properties of a class of ships.
Logical Properties
| name |
The name of the ship design. This is the same name as the
directory in which this file is stored. |
| display_name |
The name of the ship design as it should be displayed on the HUD
in the game itself. This parameter is optional. If no display_name
is specified, the design name will be used. |
| abrv |
The name of the ship type abbreviation as it should be displayed
on the HUD in the game itself (e.g. "F-15E"). This parameter is
optional. If no abrv is specified, no abbreviation will be
used. |
| class |
The displacement class of the ship. See below for a list of
valid class names. |
| map |
A structure containing a list of sprite file names to be used in
rendering this ship design in the navigation map. |
| beauty |
The name of the beauty shot bitmap file for this ship. This
image is used to represent the ship in pre-mission briefing screens.
If this attribute is not specified, the default is
"beauty.pcx". |
| hud_icon |
The name of the HUD icon bitmap file for this ship. This image
is used to represent damage to the ship at the bottom of the HUD. If
this attribute is not specified, the default is
"hud_icon.pcx". |
EXAMPLES:
name: Orion
display_name: Orion
class: carrier
beauty: "beauty.pcx"
hud_icon: "hud_icon.pcx"
map: {
sprite: "map0.pcx", // 9 oclock
sprite: "map1.pcx", // 10 oclock
sprite: "map2.pcx", // 12 oclock
sprite: "map3.pcx", // 2 oclock
sprite: "map4.pcx", // 3 oclock
sprite: "map5.pcx", // 4 oclock
sprite: "map6.pcx", // 6 oclock
sprite: "map7.pcx" // 8 oclock
}
|
VALID SHIP CLASSES Fighters and Shuttles:
Starships:
- Freighter
- Frigate
- Destroyer
- Cruiser
- Carrier
Space Stations:
Ground Units:
- Building
- Factory
- SAM
- EWR
- C3I
- Starbase
Graphical
Properties
| model |
The name of the 3D low-poly mesh file for a single level of
detail ship. |
| detail_n |
The name of the 3D low-poly mesh file for one level of detail in
a multi-LOD ship. The n can be 0, 1, 2, or 3 from lowest
detail to highest detail. |
| feature_n |
The characteristic feature size in model units for one level of
detail in a multi-LOD ship. The n can be 0, 1, 2, or 3 from
lowest detail to highest detail. |
| spin |
The 3D rate of spin in radians per second for one mesh component
file. There must be exactly as many spin attributes as there
are models per level of detail. For example, if a ship has three
levels of detail, and each level has two meshes (one spinning one
stationary) then there must be exactly two spin attributes in
the definition. |
EXAMPLES:
// TWO LOD MESHES:
detail_0: "lo-detail.mag"
feature_0: 0.1
detail_1: "hi-detail.mag"
feature_1: 0.4 |
// ONE STATIONARY AND TWO ROTATING SECTIONS, ONE LOD:
model: "s2.mag"
model: "s2mid.mag"
model: "s2end.mag"
spin: (0.0, 0.00, 0.0)
spin: (0.0,-0.10, 0.0)
spin: (0.0, 0.07, 0.0) | Physical Properties
| mass |
The mass of the ship in metric tonnes. |
| integrity |
Hull strength in "hit points". If the integrity of the ship
reaches zero, the ship is destroyed. |
| agility |
A general rating of the ship's ability to turn. Smaller numbers
mean the ship turns more slowly, larger numbers mean that it turns
more rapidly. |
| vlimit |
The exhaust velocity of the main drive in meters per second.
Beyond this velocity, the ship will accelerate much more
slowly. |
| roll_rate |
Similar to agility, but just sets the rate at which the ship
rolls about its long axis. |
| scale |
A number used to multiply the vertex coordinates in the mesh
when rendering the ship in the game engine. |
| acs |
Active Sensor Cross-section. A number that indicates how visible
this ship is to active sensors. Similar to radar cross section in
the real world. |
| trans_x |
Strength of the lateral (side-to-side) thrusters. Helps control
how rapidly the ship can turn. |
| trans_y |
Strength of the longitudinal (foreward/aft) thrusters. Helps
control how rapidly the ship can slow down. |
| trans_z |
Strength of the spinal/ventral (top/bottom) thrusters.  Used to calculate drag in flight regimes
that have drag (e.g. atmosphere, arcade space mode). |
| CL |
Coefficient of Lift. Realistic flight model, atmospheric
only. |
| CD |
Coefficient of Drag (Wings). Realistic flight model, atmospheric
only. |
| stall |
Stall onset angle of attack (radians). Realistic flight model,
atmospheric only. |
| bridge |
Vector location of bridge camera (F1 View) in model
coordinates. |
| chase |
Vector location of chase camera (F2 View) in model
coordinates. |
EXAMPLES:
mass: 517e3
agility: 2
vlimit: 220
roll_rate: 7
integrity: 75e3
scale: 5
acs: 1.5
trans_x: 1e6
trans_y: 5e5
trans_z: 1e6
drag: 1e-7
roll_drag: 1.2
pitch_drag: 1.2
yaw_drag: 1.2
chase: (0, -1800, 170)
bridge: (0, 600, 100)
| Ship
Systems
So far, we've only been looking at properties that affect the ship as a
whole. Much of the customization possible for a ship design comes in the
form of the dozen or more systems that give the ship its
specialized abilities. Each ship system is defined by a structure in the
ship definition file. All of the system structures have a few properties
in common, but they each have custom attributes as well.
COMMON SYSTEM PROPERTIES
| name |
The name of the system, used in the engineering screen. |
| abrv |
The abbreviation of the system, used in the master caution
panel. |
| design |
The name of the system design for this system. Starshatter
includes a catalog of standard system designs that are made up of
damageable/repairable components. |
| loc |
A vector providing the location of the system in model units.
This is used for system-specific damage modeling to determine if the
system was hit by incoming weapons fire. |
| size |
The radius of the system in model units. This is used for
system-specific damage modeling to determine if the system was in
range of the damage from incoming weapons fire. |
| hull_factor |
A number from 0.0 to 1.0 that identifies well protected this
system is by the ship's hull armor. 0 means the system is completely
exposed, 1 means that all damage will be absorbed by the hull
plating. |
Each system structure is introduced by a specific attribute name that
identifies the type of system being declared. For example, reactors are
declared with the name "power", like this: power: { /* reactor
attributes */ } . The following system types are supported.
SYSTEM TYPES: Click each name for more
info
| power |
Power supplies, reactors, and batteries. |
| drive |
Main fusion or plasma conventional (slower-than-light)
drive. |
| thruster |
Small turning and translation thrusters. |
| quantum |
Faster-than-light quantum jump drive. (Starships Only!) |
| shield |
Gravitational bias deflector shield. (Starships Only!) |
| weapon |
Primary (energy beam) or secondary (missile) weapons. |
| flightdeck |
Launch or recover deck for fighters (Carriers Only!) |
| sensor |
Combined passive/active sensor arrays. |
| probe |
Sensor probe launcher. |
| decoy |
Missile countermeasure decoy. |
| gear |
Fighter or shuttle landing gear. |
| nav |
Auto navigation system. |
| navlight |
Flashing navigation lights. |
| computer |
Various avionics and computer systems. |
The order that systems are listed in the ship definition file is
significant. Each system must draw power from a reactor in order to
operate (except for power sources themselves!). Each system is
automatically attached to the power source that was most recently declared
in the definition file. For example:
power: {
type: Fusion,
design: "Fusion Reactor",
// ...
}
drive: {
type: Plasma,
name: "Plasma Drive",
// ...
}
power: {
type: "Auxilliary Reactor",
design: "Auxilliary Reactor",
// ...
}
shield: {
type: 2,
design: "Grav Shield",
// ...
}
|
In the above listing, the plasma drive will draw power from the main
reactor, and the shield will be attached to the auxilliary reactor.
Starship captains can adjust power distribution and connection during the
game through the engineering screen. For example, a starship captain could
easily move the shield system from the aux reactor to the main fusion
reactor to help balance the load. However, fighter pilots do not have
access to the engineering screen, so fighter power routing is fixed at
design time. Weapons Hardpoints and
Loadouts
Starships are generally designed with fixed weapons systems. If the
ship definition file declares that a particular type of destroyer has two
x-ray laser mounts, and one torpedo launcher, all ships of that type will
always have those weapons.
Fighters, on the other hand, usually have underwing weapons hardpoints
that can carry a variety of different weapon types. You can configure each
fighter to carry an appropriate set of weapons each time one takes off
during the game. In order to do this, fighter ship designs use two
additional structures:
| hardpoint |
A system that can mount several different weapon types. |
| loadout |
A pre-defined list of weapons to be mounted. |
Death Spiral
Properties
All good things must come to an end, preferably in a suitably noisy and
colorful series of fireballs!
death_spiral: {
time: 5,
explosion_type: 10, // SMALL_EXPLOSION
explosion_time: 2,
explosion_loc: (-50, 50, 0),
explosion_type: 10, // SMALL_EXPLOSION
explosion_time: 1,
explosion_loc: (60, 40, 190),
explosion_type: 10, // SMALL_EXPLOSION
explosion_time: 0.5,
explosion_loc: (0, -48, -180),
explosion_type: 20, // LARGE_BURST (custom)
explosion_time: 0.1,
explosion_loc: (0, -48, -180),
explosion_type: 10, // SMALL_EXPLOSION
explosion_time: 0.3,
explosion_loc: (20, 80, -190),
explosion_type: 20, // LARGE_BURST (custom)
explosion_time: 0.1,
explosion_loc: (20, 80, -190),
final_type: 13, // LARGE_EXPLOSION
final_loc: (0, 0, 120),
final_type: 13, // NUKE_EXPLOSION
final_loc: (0, 0, -120),
final_type: 12, // LARGE_BURST
final_loc: (0, 0, 0),
debris: "Debris1.mag",
debris_loc: (0,0,350),
debris_mass: 100e3,
debris_count: 1,
debris_life: 600,
debris_fire: (-100,0,0),
debris_fire: (-35,20,-80),
debris: "Debris2.mag",
debris_loc: (-200,20,-300),
debris_mass: 100e3,
debris_count: 1,
debris_life: 500,
debris_fire: (64,0,120),
debris_fire: (85,20,0),
debris_fire: (65,-10,-60),
debris: "Debris3.mag",
debris_loc: (300,0,-320),
debris_mass: 100e3,
debris_count: 1,
debris_life: 400,
debris: "Debris5.mag",
debris_loc: (0,20,0),
debris_mass: 1,
debris_count: 12,
debris_life: 25,
debris: "Debris7.mag",
debris_loc: (10,0,0),
debris_mass: 1,
debris_count: 7,
debris_life: 15,
}
| Samples
Here are links to two sample ship design def files. The first one is a
fighter design, similar to the Stormhawk fighter from the game. The second
one is a fleet carrier design, based on the Orion class carrier:
Fighter.def
Carrier.def
You can use these samples as the basis for your own designs. Be sure to
rename them to match your mod design names. And remember to save the files
using a .def extension. |
|


Kanban Board
Upcoming
Your awesome text goes here. Your awesome text goes here.
-
iOS App home page
There are many variations of passages of Lorem Ipsum available.
-
Topnav layout design
Many desktop publishing packages and web page.
-
Invite user to a project
If you are going to use a passage of Lorem Ipsum.
-
Write a release note
There are many variations of passages of Lorem Ipsum available.
In Progress
Your awesome text goes here.
-
Enable analytics tracking
It has roots in a piece of classical Latin literature from 45 BC.
-
Kanban board design
All the Lorem Ipsum generators on the Internet tend to repeat predefined.
-
Code HTML email template
There are many variations of passages of Lorem Ipsum available.
Completed
Your awesome text goes here. Your awesome text goes here.
-
Brand logo design
Various versions have evolved over the years, sometimes by accident.
-
Improve animation loader
A handful of model sentence structures, to generate Lorem Ipsum which looks reasonable.
-
Dashboard Re-design
There are many variations of passages of Lorem Ipsum available.
-
iOS App home page
you need to be sure there isn't anything embarrassing hidden in the middle of text.


WITNESS LIST Appropriations-S/C on General Government Committee (Subcommittee on General Government) February 7, 2001-8:00A Budget On: Carlson Reed, Cassie (Texas Workforce Commission) Rath, Diane (Texas Workforce Commission) Townsend, Randy (Texas Workforce Commission)


Preparation time
less than 30 mins
Cooking time
over 2 hours
Serves
Serves 6-8
Dietary
Semifreddo is a delicious cross between ice cream and mousse. It melts in the mouth and never fails to impress but can be made well in advance to take the pressure off at a dinner party.
Equipment: You will need a 900g/2lb loaf tin and a hand-held electric whisk.
Double line a 900g/2lb loaf tin with cling film.
For the ganache, melt the chocolate and butter in a large heatproof bowl over a saucepan of simmering water (do not allow the bottom of the bowl to touch the water). Stir in the icing sugar and double cream. Set aside.
Meanwhile, place the egg, egg yolks, vanilla extract and sugar in a heatproof bowl and set it over a saucepan of simmering water, making sure the bowl doesn’t touch the water. Beat the mixture over the heat for about 8 minutes using a hand-held electric whisk, until it is thick and pale. Remove from the heat and set aside.
In a separate large bowl, whip the double cream until it is just stiff. Gently fold in the pale egg mixture until combined.
Pour half the mix into the prepared loaf tin. Make a shallow well along the centre and pour in the ganache. Pour the rest of the semifreddo mix over the top and use a knife to make swirls with the ganache. Cover with cling film and place in the freezer to set for 6 hours.
Just before serving, melt the chocolate pieces in a bowl standing over a pan of simmering water (do not allow the bottom of the bowl to touch the water). Set aside to cool to room temperature.
To serve, turn the semifreddo out onto a serving platter and carefully remove the cling film. Pour the cooled chocolate over the top, sprinkle with the toasted hazelnuts and serve in generous slices.


gh run
View, run and watch recent GitHub Actions workflow runs.
More information: home page
- Interactively select a run to see information about the jobs:
gh run view
- Display information about a specific run:
gh run view workflow_run_number
- Display information about the steps of a job:
gh run view --job=job_number
- Display the log of a job:
gh run view --job=job_number --log
- Check a specific workflow and exit with a non-zero status if the run failed:
gh run view workflow_run_number --exit-status && echo "run pending or passed"
- Interactively select an active run and wait until it's done:
gh run watch
- Display the jobs for a run and wait until it's done:
gh run watch workflow_run_number
- Re-run a specific workflow:
gh run rerun workflow_run_number


Robotics
Embedded Systems
Internet of Things
Intelligent Transport Systems
I was part of a team developing a smart-city structure capable of acquiring data from a multi-slave->master system, which will be then presented on a Web interface.
I spent two months at CEiiA on a team responsible for the development and optimization of low cost and eco-friendly monitoring buoys.
I spent a week at Critical Software (Coimbra) working on a team, developing an environmental sensor station, the senseBox. At the end of the week we did a pitch for the company CEO and other employees.
Development of a monitoring and data communication system for application in Pavement Energy Harvesting (continuation of the PEJENE 2020 internship)
I spent the second semester of the fourth year at University of Hull, England.
Controlling a servo motor using an infrared controller.
It's divided into two phases:
1) Decode the controller: obtain the code corresponding to each of the buttons so that the microcontroller knows which one is being pressed.
2) Send instructions to the servo, depending on which button is pressed.
View Project
Game in which the microcontroller will generate a random sequence that we have to memorize and repeat. Each level increases the sequence by one to a total of 10 steps.
Win and be congratulated by an awesome song.
The CheckMates project was developed in the context of Programming Laboratories, a 4th year course in FEUP’s MIEEC.
I worked with André Aragão, André Silva and José Pedro, who I hope are doing great in their careers.
The License Plate Recognition project was developed in the context of Vision-Based Systems, a 4th year course in FEUP’s MIEEC.
I worked with André Ribeiro, João Oliveira and Leonor Santos,
who I hope are doing great in their careers.


With data.world nodes for KNIME, you can automate data processing and analysis pipelines and build smart workflows with data.world data.
Using the available data.world nodes from KNIME's community extensions, you can connect with your data.world account:
You can find all relevant data.world nodes under Community Nodes in the KNIME Node Repository:
Here are a few things you can do with KNIME and data.world:


1 reference to PathIsNetworkPath
System.Management.Automation (1)
namespaces\FileSystemProvider.cs (1)
7154
return NativeMethods.
PathIsNetworkPath
(path); // call the native method


Deletion
Item to be deleted:
{{item.description}}
Are you sure you want to delete this item?
Sign Out
Cancel
and return to menu


{% extends 'hackathon/base.html' %} {% block head-content %} {% endblock %} {% block body %}
100 potential job interview questions. Skip to the full list


At the CSTUG general meeting, I gave a talk on responsive design and
automated typesetting using LuaLaTeX. I demonstrated the use of the
Responsive,
Luavlna,
Linebreaker, and
Lua-widow-control packages.
You can find a recording of the talk and slides on
the CSTUG website.
Unfortunately, they are only available in Czech, but I hope they can still be useful to someone.
I have a habit to start lot of projects in my hyper-focus seasons.
Unfortunately, I often left then unfinished, or mostly finished, but
without documentation. Here is a list of these, that are most interesting for me.
HTML parser for LuaXML. I
implemented the HTML parsing state machine, but the DOM tree building
mechanism is mostly missing.
Rmodepdf – typeset HTML files with LuaLaTeX. It can remove unnecessary content from web pages thanks to Rdrview (similarly to reader mode in Firefox).
Linemarkup – LuaLaTeX package for support of line oriented markup languages (such as Gemini or Subtext.
Responsive-LaTeX – idea is to allow design of page layout and font sizes in LaTeX document depending on the paper size, similar to responsive design in CSS.
Luaepubreader – Epub reader for LuaLaTeX. It should enable for direct typesetting of Epub files. It is in an early stage of development, it can read list of files in the Epub files, but nothing more. It depends on the finishing of the HTML parser.
Cooklang-lua – Lua parser for the Cooklang. Parser works, but it needs a LaTeX interface.
Luaspreadsheet – Lua module for reading of spreadsheet files. Currently, it supports only reading of XSLT files.
Lualiterate – support for API comments in LaTeX packages. In a proof-of-concept state.
TeXparser – Lua parser for LaTeX. Idea was to strip LaTeX commands, create a text file useful for grammar checking or other tools that don't support LaTeX syntax, and then apply changes in that text file back to LaTeX sources.
I am Michal, a librarian and FOSS developer from Prague, Czechia. I
have wanted to create a proper homepage for a long time, but I always had
overly ambitious plans, and I ended up procrastinating on other projects
instead. As it became evident that I was not going to accomplish all of
my plans, I decided to create a minimal page and start from there. I will
gradually add more information and, hopefully, also some articles in the
future.
What is Kodymirus
Kodymirus was an
arthropod that lived in the Lower Cambrian period in the area of today's
Brdy Hills in central Bohemia. It is one of the oldest fossils that can
be found in the Czech Republic. Why did I choose this name for this site?
It doesn't have any deep meaning. I just like the Brdy Hills and
paleontology and found this name amusing. That's all.


Hack4Climate
Climate Action Tracking
Start Bootstrap
Home
(current)
Orgs
Global Carbon Emission Heatmap
Click on your country/city to view the carbon emission around you.
Act now!


- Provider Dashboard
- My Dashboard
- Apps
- Provider Profile
- Patient List
Eligibility Screening
Referral Instructions
Here are the steps to follow to be able to access the Health enSuite Insomnia app:
Step 1: Copy this link http://healthensuiterefcode.000webhostapp.com/ exactly as it is printed here to be able to access the application on the web browser on your computer or any other device enabled with internet connectivity.
Step 2: You will be asked to enter the username and password, then your Referral code: Enter it exactly as it is printed here.
Step 3: When you have completed the above steps correctly, you will be navigated to the next steps in this study.
Step 4: If you misplace this instructions sheet, do not worry! You can either request your health care provider to issue a new one OR contact Health enSuite research team by email<EMAIL_ADDRESS>OR phone:<PHONE_NUMBER> or call toll-free number: 1-877-341-8309 press 5.
Best regards,
Health enSuite team
Record Exist
| Patient ID | First Name | Last Name | Age | Gender | Date of Referral | Taper Start Date |
|---|
Record Exist
| First Name | Last Name | Age | Gender | Date of Referral | Taper Start Date |
|---|
BZRAs Currently Prescribed
BZRA Regimen Details
Some BZRAs are not easily tapered due to dosage formulation limitation. This includes capsules (chlordiazepoxide, clorazepate, flurazepam, temazepam) and specially formulated tablets (zolpidem orally disintegrating tablets). You may wish to switch to an equivalent dose of an alternative BZRA available in multiple tablet strengths that can further split into smaller doses. Taper schedule are available for shorter (oxazepam), intermediate (lorazepam), and longer (clonazepam) half-life BZRAs.
Proposed Taper Schedule
Medication 1:
i
i
| Taper week | Provider recommended taper dose (mg) | Rounded taper dose (mg) | Recommended dose combinations (mg) |
|---|
Medication 2:
i
i
| Taper week | Provider recommended taper dose (mg) | Rounded taper dose (mg) | Recommended dose combinations (mg) |
|---|
Confirm Recommendation
The tapering schedule is ready to print. Please confirm that this patient has insomnia
and would benefit from cognitive behavioural therapy.
Print Schedule
Referral Instructions
Here are the steps to follow to be able to access the Health enSuite Insomnia app:
Step 1: Copy this link http://healthensuiterefcode.000webhostapp.com/ exactly as it is printed here to be able to access the application on the web browser on your computer or any other device enabled with internet connectivity.
Step 2: You will be asked to enter the username and password, then your Referral code: Enter it exactly as it is printed here.
Step 3: When you have completed the above steps correctly, you will be navigated to the next steps in this study.
Step 4: If you misplace this instructions sheet, do not worry! You can either request your health care provider to issue a new one OR contact Health enSuite research team by email<EMAIL_ADDRESS>OR phone:<PHONE_NUMBER> or call toll-free number: 1-877-341-8309 press 5
Best regards,
Health enSuite team
Recommended Sleep Medication Tapering Schedule
Provider information
Please taper as directed in the table on the next page.
Please consult your pharmacist for advice on how to best implement this schedule. Based on available pills strengths some modifications to this schedule may be needed. Changes recommended by your provider or pharmacist should be noted in the column labelled “Recommended Dose Combinations”.
Recommended Sleep Medication Tapering Schedule
Medication:
| Taper week | Provider recommended taper dose (mg) | Rounded taper dose (mg) | Recommended dose combinations (mg) |
|---|
Provider’s signature
Date
Print Schedule
Referral Instructions
Here are the steps to follow to be able to access the Health enSuite Insomnia app:
Step 1: Copy this link http://healthensuiterefcode.000webhostapp.com/ exactly as it is printed here to be able to access the application on the web browser on your computer or any other device enabled with internet connectivity.
Step 2: You will be asked to enter the username and password, then your Referral code: Enter it exactly as it is printed here.
Step 3: When you have completed the above steps correctly, you will be navigated to the next steps in this study.
Step 4: If you misplace this instructions sheet, do not worry! You can either request your health care provider to issue a new one OR contact Health enSuite research team by email<EMAIL_ADDRESS>OR phone:<PHONE_NUMBER> or call toll-free number: 1-877-341-8309 press 5.
Best regards,
Health enSuite team
Recommended Sleep Medication Tapering Schedule
Provider information
Please taper as directed in the table on the next page.
Please consult your pharmacist for advice on how to best implement this schedule. Based on available pills strengths some modifications to this schedule may be needed. Changes recommended by your provider or pharmacist should be noted in the column labelled “Recommended Dose Combinations”.
Recommended Sleep Medication Tapering Schedule
Medication:
| Taper week | Provider recommended taper dose (mg) | Rounded taper dose (mg) | Recommended dose combinations (mg) |
|---|
Medication:
| Taper week | Provider recommended taper dose (mg) | Rounded taper dose (mg) | Recommended dose combinations (mg) |
|---|
Provider’s signature
Date
Provider Quick Login
You have been away! Please sign in again. This is to ensure that your account is not access by someone else.
Copyright © Designed & Developed by Health enSuite Research Team 2020


Bringing order to the digital jungle.
Your one stop place to get informed about
the modern tech industry.
Headings & titles
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Rerum labore sit quas distinctio deserunt numquam delectus, error natus excepturi sed veritatis quisquam dolor molestias optio velit cum, impedit unde molestiae.
Paragraphs & links
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Rerum labore sit quas distinctio deserunt numquam delectus, error natus excepturi sed veritatis quisquam dolor molestias optio velit cum, impedit unde molestiae.
Your daily dosis of product, marketing, tech and startups news served as instant articles
(ĭn′flo͞o-əns) from Old French influence “emanation from the stars affecting one’s fate”
Your one-stop digital media access to all the relevant sources out in the wild
Stay updated with the good guys who unveil the secrets that rule the jungle


This package won't show up on your devlog-only game page. Switch your game page to early access or complete from the Overview/Setup page for it to show.
Go to Overview/Setup page
Package Preview
Edit Package Details
This package has builds that are still processing. They will be available in the package as soon as they're finished processing.


Central government organisations currently using GOV.UK Pay are:
- Ministry of Justice
- Office of the Public Guardian
- Companies House
- Home Office
GOV.UK Pay is not yet available to local authorities.
{% extends "_layouts/govuk-pay.html" %} {% set section = "index2" %} {% block content %}
GOV.UK Pay makes it quicker and easier for service teams to process payments online. It’s easy to integrate with and gives users a trusted GOV.UK branded payment experience.
Service teams using GOV.UK Pay can:
Teams building the service can:
Users paying for a government service will get:
GOV.UK Pay integrates with multiple payment service providers so that service teams don't have to. This means that switching suppliers or activating new payment methods won't require additional technical work for your team.
GOV.UK Pay provides technical documentation to help your service:
Central government organisations currently using GOV.UK Pay are:
GOV.UK Pay is not yet available to local authorities.
Contact the team to create an account and test GOV.UK Pay or ask a question.
GOV.UK Pay is built and supported by a full time team at the Government Digital Service. The service manager is Till Wirth.


PDBe API Workshop
European Bioinformatics Institute Cambridge, United KingdomProgrammatic Access to the Molecular Structure Information at EMBL-EBI Hinxton, November 20-21st.
Programmatic Access to the Molecular Structure Information at EMBL-EBI Hinxton, November 20-21st.
Workshop on data visualisation by Andy Kirk, the curator of Visualizing data.
Gulbenkian Training Programme in Bioinformatics with Allegra Via and Fabrizio Ferrè (Sapienza Università di Roma), May 2-6th.
Macromolecular Crystallography Laboratory, FCT-UNL, February 1-5th.


About Me
I was in the Navy for 6 years as a Fire Controlman and was in charge of maintaining and operating CIWS on FFG-42 USS Klakring. I've traveled all around Europe and South America and am tired of the ocean so don't ask me to go on a cruise because I will decline faster than you can ask me. After the military I went to school to become an Xray Tech, and worked fulltime doing that for a little over 3 years. I have 4 amazing crazy kids, 3 girls and 1 boy. I'm going on 13 years being married to my amazing and supporting wife. We have 1 dog named Bentley, who is 11 and just as crazy as my kids.


Students at Rural Universities Embrace Entrepreneurship Roadshow
Caption:Television celebrity Candice Modiselle presenting a motivational talk on entrepreneurship at the Walter Sisulu University in Mthatha during the #SEW2018 roadshow.
Photo:Courtesy Pride Factor
Thohoyandou, 8 October 2018:Hundreds of students at rural universities have embraced the entrepreneurship roadshow that has visited institutions of higher learning in Gauteng, North West Province, the Free State, the Eastern Cape and Limpopo over the past three weeks.
Building on the Student Entrepreneurship Week (#SEW2018) which was hosted at public universities countrywide throughout August, the roadshow comprises one day interactive workshops and has been organised by Entrepreneurship Development in Higher Education (EDHE).
Students in Vanderbijlpark, Mafikeng, Bloemfontein, Mthatha, East London, Butterworth, Grahamstown and Thohoyandou have flocked to the workshops to hear motivational presentations by high profile role-models and to participate in a ‘pitching competition’ with R10,000 at stake.
The messages have resonated with audiences with 95% agreeing that the content is practical and useful while 90% want more information from SEW and EDHE.
Feedback has included comments such as:
- • Inspires and revives our drive to thrive in this life
- • It was realistic and highly motivational
- • I gained more knowledge today and left with a helping hand
- • Helps us grab opportunities instead of waiting for them
- • Entrepreneurship breaks financial boundaries
- • Educates students on what to expect after we graduate
At the workshops the students hear personal insights of the road to success from the likes of TV celebrity Candice Modiselle, M&G Top 200 Young South African Zareef Minty, motivational speaker Fred Bohasu, founder of Sumting Fresh gourmet street food Hezron Louw, Future Leaders ambassador Lihle Nkosi and Pride Factor founder Dene Botha, who hosts the shows.
Alongside the motivational talks and guidance on entrepreneurial principles at each venue, a selection of students are invited to pitch their personal projects to a panel of experts from BeBold who evaluate all submissions and award the presenter of the best concept R10,000 in seed finance to develop their idea..
Adopting the theme ‘Student entrepreneurship – the best of both worlds’, the #SEW2018 roadshow raises awareness of entrepreneurship as a career and a springboard into the world of business upon graduating.
The roadshow is an EDHE initiative brought to students by Universities South Africa (USAf) and the Department Higher Education and Training (DHET). The edutainment programme is presented by the Pride Factor Life Skills Academy in partnership with BeBold, ENACTUS, Start-up Academy and It’s a Breeze. The roadshow is driven by Renault South Africa.
The SEW Roadshow will visit the University of Limpopo in Polokwane on Tuesday 9 October and wraps up at the Sefako Makgatho University of Health Sciences in Ga-Rankuwa on Friday 12 October.
#SEW2018 Roadshow dates and destinations:
Completed workshops
- • 20 September – Vaal University of Technology, Vanderbijlpark campus
- • 21 September – North-West University, Mafikeng campus
- • 25 September – University of the Free State, Bloemfontein
- • 28 September – Walter Sisulu University, Mthatha Campus
- • 1 October – University of Fort Hare, East London
- • 2 October – Walter Sisulu University, Butterworth Campus
- • 3 October – Rhodes University, Grahamstown
- • 8 October – University of Venda
Upcoming workshops:
- • 9 October – University of Limpopo, Polokwane
- • 12 October – Sefako Makgatho University of Health Sciences
Background information on EDHE
Established at the end of 2016 within the University Education Branch of the Department Higher Education and Training (DHET), EDHE was inspired by the growing graduate and youth unemployment, the resources available at universities, the national drive for SMEs and the need for third-stream income at universities. The programme was also motivated by the imperative to drive student and graduate entrepreneurship. The programme has since been included (from a funding perspective) in the University Capacity Development Programme (UCDP) of the DHET.
Recognising that universities as centres of entrepreneurship development are at the heart of the EDHE initiative, the programme has now been located within Universities South Africa (USAf) as the implementing body. Thus EDHE represents a partnership between USAf and DHET through a grant made to the former.
Enquiries:
Dr Norah Clarke
Programme Director: Entrepreneurship
Universities South Africa (USAf) & Department Higher Education and Training
Tel.:<PHONE_NUMBER> |<PHONE_NUMBER>
E-mail<EMAIL_ADDRESS>|<EMAIL_ADDRESS>www.edhe.co.zaPride Factor Pty Ltd
Contact:Dene Botha
Mobile:078 453 4600


=== Test case: lasp_SUITE:latency_with_reads_test/1 (click for source code) === Config value: [{watchdog,<0.4698.0>}<EMAIL_ADDRESS>{tc_group_properties,[]}, {tc_group_path,[]}, {data_dir,"/home/gcreupelandt/Documents/MEMOIRE/lasp/_build/test/lib/lasp/test/lasp_SUITE_data/"}<EMAIL_ADDRESS>=== Current directory is<EMAIL_ADDRESS>=== Started at 2020-09-27 16:49:52
*** User 2020-09-27 16:49:52.622 *** Beginning case: latency_with_reads_test
*** User 2020-09-27 16:49:52.646 *** 16:49:52.646 [info] Configured peer_service_manager partisan_pluggable_peer_service_manager on node 'runner@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:52.646 *** 16:49:52.646 [info] Using node name: 'runner@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:52.820 *** 16:49:52.820 [info] Partisan listening on {127,0,1,1}:47121 listen_addrs: [#{ip => {127,0,1,1},port => 47121}]
*** User 2020-09-27 16:49:52.829 *** 16:49:52.829 [info] Not using container orchestration; disabling.

*** User 2020-09-27 16:49:54.285 *** 16:49:54.285 [info] Disabling blocking sync...
*** User 2020-09-27 16:49:54.290 *** 16:49:54.290 [info] Configured peer_service_manager partisan_pluggable_peer_service_manager on node 'node-1@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:55.674 *** Loading applications on node: 'node-2@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:55.797 *** 16:49:55.796 [info] Enabling membership...
*** User 2020-09-27 16:49:55.798 *** 16:49:55.798 [info] Disabling blocking sync...
*** User 2020-09-27 16:49:55.803 *** 16:49:55.802 [info] Configured peer_service_manager partisan_pluggable_peer_service_manager on node 'node-2@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:57.138 *** Loading applications on node: 'node-3@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:57.245 *** 16:49:57.245 [info] Enabling membership...
*** User 2020-09-27 16:49:57.246 *** 16:49:57.246 [info] Disabling blocking sync...
*** User 2020-09-27 16:49:57.250 *** 16:49:57.250 [info] Configured peer_service_manager partisan_pluggable_peer_service_manager on node 'node-3@gcreupelandt-N551VW'
*** User 2020-09-27 16:49:57.510 *** Joining node: 'node-3@gcreupelandt-N551VW' to 'runner@gcreupelandt-N551VW' at listen_addr [#{ip => {127, 0, 1, 1}, port => 39639}]
*** User 2020-09-27 16:49:58.526 *** Joining issued: 'node-3@gcreupelandt-N551VW' to 'runner@gcreupelandt-N551VW' at listen_addrs [#{ip => {127, 0, 1, 1}, port => 39639}]
*** User 2020-09-27 16:49:58.527 *** Joining node: 'node-2@gcreupelandt-N551VW' to 'runner@gcreupelandt-N551VW' at listen_addr [#{ip => {127, 0, 1, 1}, port => 57061}]
*** User 2020-09-27 16:49:59.580 *** Joining issued: 'node-2@gcreupelandt-N551VW' to 'runner@gcreupelandt-N551VW' at listen_addrs [#{ip => {127, 0, 1, 1}, port => 57061}]
*** User 2020-09-27 16:49:59.581 *** Joining node: 'node-1@gcreupelandt-N551VW' to 'runner@gcreupelandt-N551VW' at listen_addr [#{ip => {127, 0, 1, 1}, port => 38875}]
*** User 2020-09-27 16:50:00.623 *** Joining issued: 'node-1@gcreupelandt-N551VW' to 'runner@gcreupelandt-N551VW' at listen_addrs [#{ip => {127, 0, 1, 1}, port => 38875}]
*** User 2020-09-27 16:50:00.684 *** Waiting for join to complete with manager: partisan_pluggable_peer_service_manager
*** User 2020-09-27 16:50:01.199 *** Finished.
*** CT 2020-09-27 16:50:01.199 *** COVER INFO Adding nodes to cover test: ['runner@gcreupelandt-N551VW']
*** CT 2020-09-27 16:50:01.205 *** COVER INFO Successfully added nodes to cover test: []
*** User 2020-09-27 16:50:01.205 *** Case finished: latency_with_reads_test
*** User 2020-09-27 16:50:08.246 *** 16:50:08.246 [info] Application lasp exited with reason: stopped
*** System report during lasp_SUITE:latency_with_reads_test/1 2020-09-27 16:50:08.246 *** =INFO REPORT==== 27-Sep-2020::16:50:08.246456 === application: lasp exited: stopped type: temporary
*** User 2020-09-27 16:50:08.249 *** 16:50:08.249 [info] Application partisan exited with reason: stopped
*** System report during lasp_SUITE:latency_with_reads_test/1 2020-09-27 16:50:08.249 *** =INFO REPORT==== 27-Sep-2020::16:50:08.249549 === application: partisan exited: stopped type: temporary
=== Ended at 2020-09-27 16:50:08 === successfully completed test case === === Returned value: ok
Test run history | Top level test index | Latest test result


ti-widget-dial demo
Each ti-widget-analoggauge's value property is bound to the value property of the dial to its left.
CSS styles control how the gauges and dials are displayed.


Word Definitions Game
This Android app allows you to define words and their definitions, and questions will be randomly shown with multiple choices for you to guess.
Macro Project
This is a macro program that expands shorter sequences of text into longer sequences that the user defines.
Game of Life
A Conway's Game of Life implementation using Java Swing.


Preparation time
overnight
Cooking time
less than 10 mins
Serves
Makes 4 pizzas
Dietary
San Marzano tomatoes have dense flesh and a rich, sweet flavour. They are considered by many chefs to make the best tomato sauce, but good quality plum tomatoes could be substituted.
To make the dough, place the flours, salt, sugar and yeast into a large bowl and stir. Make a well in the centre of the flour and pour in the water, gradually mixing in the flour to form a soft dough.
Tip out and knead on an oiled work surface for about 10 minutes or until the dough is smooth and elastic. Place it into a bowl, cover and leave to rise for 24 hours.
Preheat the oven to its highest temperature. Place a heavy baking tray or pizza stone in the oven and allow it to heat.
Remove the dough from the bowl and knead for a couple of minutes, then divide into four pieces. Allow to rest for five minutes, then stretch each piece over your hands to form a disc about 5mm/¼in thick.
Place the circles of dough onto upturned floured baking trays or a pizza peel if you have one.
Place the tinned tomatoes into a food processor and blend to a purée. Spoon the tomato purée thinly over the pizzas, scatter over the grated mozzarella, then drizzle over the oils. Season with sea salt and freshly ground black pepper.
Slide each pizza off the baking tray directly onto the heated baking tray or pizza stone in the oven and cook for 5 -10 minutes, or until golden-brown and crisp.
To serve, scatter the basil leaves, rocket and prosciuto (if using) over the pizza and drizzle with a little more peanut oil.


In general Oak aims to provide a smooth upgrade path that allows a new version of Oak to simply run on data written by an older version of Oak. In some cases additional manual steps are needed or recommended to ensure performance and reduce downtime of a system to a minimum.
Oak 1.8 introduced some changes in the DocumentNodeStore that require an one-time sweep of the DocumentStore per cluster node. This sweep is triggered automatically on startup when Oak detects an upgrade from an older version. Depending on the size of the repository, the sweep operation may take some time and prolong the downtime of the system during an upgrade. Alternatively, the one-time sweep operation can also be triggered for an inactive cluster node with the oak-run tool while the remaining cluster nodes are active and in use by the application. This is the recommended approach because it minimizes downtime.
The following instructions assume a cluster with two nodes C1 and C2 running on Oak 1.6 or older.
Remove documents potentially created by OAK-4345. The issue only affected deployments based on MongoDB. Connect to the database with a MongoDB shell and then execute:
> db.nodes.remove({_id:{$type:7}})
Run the revisions sweep command using the oak-run tool for C1. A sweep can only run on an inactive cluster node, otherwise the command will refuse to run. Assuming C1 used clusterId 1, the command line would look like this:
> java -Xmx2g -jar oak-run-1.8.0.jar revisions mongodb://localhost:27017/oak sweep --clusterId 1
For larger repositories it is recommended to be more generous with the cache size, which will speed up the sweep operation: --cacheSize 1024 More detailed progress is available when --verbose is added.
Once finished the tool will print a summary:
Updated sweep revision to r15d12cb1836-0-1. Branch commit markers added to 8907 documents. Reverted uncommitted changes on 19 documents. (7.94 min)
C1 is now ready for an upgrade to Oak 1.8.
Run the revisions sweep command using the oak-run tool for C2 (assuming it used clusterId 2):
> java -Xmx2g -jar oak-run-1.8.0.jar revisions mongodb://localhost:27017/oak sweep --clusterId 2
Start cluster node C2 with the new version of Oak and the application.
Create recommended indexes in MongoDB and remove old ones. For a more efficient Revision GC, the existing indexes on _deletedOnce and _sdType should be replaced. Please note, the partial index on _deletedOnce and _modified requires at least MongoDB 3.2.
> db.nodes.createIndex({_sdType:1, _sdMaxRevTime:1}, {sparse:true}) { "createdCollectionAutomatically" : false, "numIndexesBefore" : 5, "numIndexesAfter" : 6, "ok" : 1 } > db.nodes.dropIndex("_sdType_1") { "nIndexesWas" : 6, "ok" : 1 } > db.nodes.createIndex({_deletedOnce:1, _modified:1}, {partialFilterExpression:{_deletedOnce:true}}) { "createdCollectionAutomatically" : false, "numIndexesBefore" : 5, "numIndexesAfter" : 6, "ok" : 1 } > db.nodes.dropIndex("_deletedOnce_1") { "nIndexesWas" : 6, "ok" : 1 }
See also instructions how to build indexes on a replica set to minimize impact on the system.


{{ define "main" }} {{ $data := index .Site.Data .Site.Language.Lang }} {{ "" | safeHTML }} That page does not exist... Sorry, the page you were looking for could not be found. Please visit our home page or let us know if you can't find what you're looking for? {{ "" | safeHTML }} {{ end }}
Sorry, the page you were looking for could not be found.
Please visit our home page or let us know if you can't find what you're looking for?


pyncli.ldap
pyncli.ldap.admexept
AdminException
AdminException(self, value, code=None)
Root package exception class.
Args: value (str): Description of the exception.
NotEnoughParams
NotEnoughParams(self, value, code=None)
Exception class called in case of lack of necessary parameters in the constructor or method call.
Args: value (str): Description of the exception.
EmptyParam
EmptyParam(self, value, code=None)
Exception class called when a method is called with an empty parameter.
Args: value (str): Description of the exception.
WrongParam
WrongParam(self, value, code=None)
The exception class that is called when the method is called as a parameter of an invalid type or value.
Args: value (str): Description of the exception.
TooLong
TooLong(self, value, code=None)
Exception class called when the method is called with an invalid length parameter.
Args: value (str): Description of the exception.
ConnectionFailure
ConnectionFailure(self, value, code=None)
Exception class called when it is impossible to connect to the specified server.
Args: value (str): Description of the exception.
OperationFailure
OperationFailure(self, value, code=None)
Exception class called when it is impossible to perform the specified operation.
Args: value (str): Description of the exception.
NotFound
NotFound(self, value, code=None)
Exception class called in case of problems with the search.
Called when the desired object was not found.
Args: value (str): Description of the exception.
pyncli.ldap.operate2
A module that implements the admin class for working with LDAP.
admin
admin(self, ldap_admin, admin_pwd, ldap_server_list)
Class for administrative operations
pyncli.ldap.protogroup
protogroup
protogroup(self, name, org_unit, **kwargs)
base group class
pyncli.ldap.group
CleanSetAttrMeta
CleanSetAttrMeta(self, /, *args, **kwargs)
Metaclass to change setattr method
group
group(self, name, org_unit='ou=test_ou,dc=example,dc=com', description='', **kwargs)
common group class
pyncli.ldap.protoou
CleanSetAttrMeta
CleanSetAttrMeta(self, /, *args, **kwargs)
Metaclass to change setattr method
protoou
protoou(self, name, org_unit, **kwargs)
base Organisational Unit class
pyncli.ldap.ou
ou
ou(self, name, org_unit='ou=test_ou,dc=example,dc=com', description='', **kwargs)
Common Organizational Utit class
pyncli.ldap.protouser
protouser
protouser(self, login, **kwargs)
Base user class
pyncli.ldap.user
CleanSetAttrMeta
CleanSetAttrMeta(self, /, *args, **kwargs)
Metaclass to change setattr method
user
user(self, login, uid='', org_unit='OU=test,DC=example,DC=com', surname='', first_name='', middle_name='', company='', department='', division='', position='', mail='', mobile='', other_mailbox='0', other_mobile='0', comment='', employee_type='', acc_control=[<uac.NORMAL_ACCOUNT: 512>, <uac.ACCOUNTDISABLE: 2>], description='', principal_name='', **kwargs)
Common user class
uac
uac(self, /, *args, **kwargs)
userAccountControl Enumerator class
ACCOUNTDISABLE
userAccountControl Enumerator class
DONT_EXPIRE_PASSWORD
userAccountControl Enumerator class
DONT_REQ_PREAUTH
userAccountControl Enumerator class
ENCRYPTED_TEXT_PWD_ALLOWED
userAccountControl Enumerator class
hex
Get hex representation of uac instance
Returns: (str): hex representation of uac instance
HOMEDIR_REQUIRED
userAccountControl Enumerator class
INTERDOMAIN_TRUST_ACCOUNT
userAccountControl Enumerator class
LOCKOUT
userAccountControl Enumerator class
MNS_LOGON_ACCOUNT
userAccountControl Enumerator class
NORMAL_ACCOUNT
userAccountControl Enumerator class
NOT_DELEGATED
userAccountControl Enumerator class
PASSWD_CANT_CHANGE
userAccountControl Enumerator class
PASSWD_NOTREQD
userAccountControl Enumerator class
PASSWORD_EXPIRED
userAccountControl Enumerator class
SCRIPT
userAccountControl Enumerator class
SERVER_TRUST_ACCOUNT
userAccountControl Enumerator class
SMARTCARD_REQUIRED
userAccountControl Enumerator class
TEMP_DUPLICATE_ACCOUNT
userAccountControl Enumerator class
TRUSTED_FOR_DELEGATION
userAccountControl Enumerator class
TRUSTED_TO_AUTH_FOR_DELEGATION
userAccountControl Enumerator class
USE_DES_KEY_ONLY
userAccountControl Enumerator class
val
Get value of uac instance
Returns: (int): value of uac instance
WORKSTATION_TRUST_ACCOUNT
userAccountControl Enumerator class
get_status
uac.get_status(hex_status_code)
Get a list of userAccountControl flags names.
Args: hex_status_code (str): userAccountControl hex value
Returns: (list): userAccountControl flags names.
get_uac
uac.get_uac(hex_status_code)
Get a list of userAccountControl flags.
Args: hex_status_code (str): userAccountControl hex value
Returns: (list): userAccountControl flags.
get_control
uac.get_control(flag_list)
Get userAccountControl value.
Args: flag_list (list): userAccountControl list
Returns: (list): userAccountControl hex value or False.
pyncli.ldap.utill
Module with auxiliary functions.
download_file
download_file(url, local_path, user, pwd)
Download file
Downloads a file with basic authentication.
Args: url (str): URL local_path (str): file full name user (str): user name pwd (str): password
Returns: (str): file full name
Raises: ConnectionFailure: connection failure
upload_file
upload_file(url, data, login, pwd)
Upload file
Uploads a file with basic authentication.
Args: url (str): URL data (str): string or buffer to load login (str): user name pwd (str): password
Returns: (str): file full name
Raises: OperationFailure: operation failure
mailto
mailto(msg_from, msg_to_list, smpt, subject, text)
Simple mailto function
Sends a message to one or a group of recipients.
Args: msg_from (str): From whom msg_to_list (list): List of email recipients. smpt (str): SMTP server name or IP subject (str): subject of the message text (str): text of the message
Raises: ConnectionFailure: connection failure
trim
trim(text)
Removes extra spaces from text.
Args: text (str): text
Returns: (str): processed text
trim_low
trim_low(text)
Removes extra spaces from text and set it to lower case.
Args: text (str): text
Returns: (str): processed text
split_names
split_names(fullname)
Splits user fullname by surname, first name and middle name.
Args: fullname (str): full name (The first word is considered the surname, the second first name, all the rest go to the middle name. This is the Russian name record format.)
Returns: (dict): Dictionary with surname, first name and middle name as values.
date_str_to_generalize_time
date_str_to_generalize_time(date_str)
Converts date in string format to date in generalized time format.
Args: date_str (str): Date string in formats %Y-%m-%d, %Y/%m/%d or %d.%m.%Y
Returns: (str): Date in generalized time format.
Note: Time zone information is not supported.
is_generalized_time
is_generalized_time(date_str)
Checks is this string look like generalized time.
Args: date_str (str): Date string
Returns: (bool): True if input string is generalized time.
Note: Time zone information is not supported.
generalized_time_to_datetime
generalized_time_to_datetime(gen_time)
Converts date in generalized time format to datetime
Args: gen_time (str): Date string in generalized time format
Returns: (datetime): datetime object
Note: Time zone information is not supported.
datetime_to_generalized_time
datetime_to_generalized_time(date_time)
Converts datetime to generalized time format.
Args: date_time (datetime): datetime object
Returns: (str): Date in generalized time format.
Note: Time zone information is not supported.