Quenya speech has a strong rhythm to it, and sometimes the sounds in Quenya words change to maintain that rhythm.
<IP_ADDRESS> Elision with two vowels: Quenya has a tendency to lose a vowel at the end of a word when the next word begins with a vowel, especially if the two vowels are similar. This process is called “elision”. We saw an example of this in our guided reading exercise from Chapter 2, Section §2.6:
The word tenna “until” appears before the word Ambar “World”. Since the next word begins with the same vowel, the final vowel of tenna disappears, leaving tenn’ Ambar-metta. The vowels don’t necessarily have to be the same, though: we also saw elision with elen síla lúmenn’ omentielvo “A star shines on the hour of our meeting” (LotR/81) in Chapter 1, Section §1.4. In this example, the final a of lúmenna “upon the hour” is lost before the vowel o.
Circumstances in which elision occurs include:
Speculative: For the last two cases, elision seem to be most likely in longer words if the result does not put the stressed syllables of the two words next to each other: márENN’ aLASsëo and VAnim’ ambaRÓnë are fine, but hrestann’ ailino is problematic because the two stressed syllables would be adjacent: hrestANN’ AIlino. In such cases I think elision is unlikely: hrestanna ailino “to the shore of a lake”. But hrestann’ ailinyo (hrestANN’ aiLINyo) “to the shore of his lake” is more likely to have elision because the stress patterns are amenable to it.
Elision may also occur if the words are particularly short and can be pronounced as a single unit; this is especially common if the following word is i “the”: minn’ i rotto “into the cave”, pronounced MINN’ i ROTto. Elision can occur with short words in other circumstances, especially with prepositions which tend to be weakly stressed, as with tenn’ Ambar (pronounced tenn’ AMbar) as seen above.
<IP_ADDRESS> Elision with i “the”: In general, monosyllabic words like ni “me” and i “the” do not undergo elision with following vowels, otherwise they might become indecipherable or disappear entirely: i intya “the notion”. However, i “the” sometimes disappears when it follows a vowel, especially an i or e. We have two examples of this:
See section <IP_ADDRESS> Forms of the Definite Article for further discussion of alternate forms of i.
<IP_ADDRESS> How do we know this? Tolkien did not discuss elision directly, so the rules above are deduced from attested examples. There are also some inconsistencies in how Tolkien applied elision. In Quenya prayers of the 1950s, Tolkien sometimes applied elision to suffixed pronouns (VT43/23). However, there are also examples in the same set of texts where elision does not occur and there are no other examples of elision of pronouns elsewhere in Tolkien’s later writings, so I consider this to have been a transient idea and ignore it.
The rule above where elision is prohibited in longer words if it would cause primary stresses to become adjacent is speculation on my part. It fits the available examples, but we have so few examples to work from that it could be wrong. However Quenya seems to have general preference for avoiding adjacent stressed syllables, so the proposed rule fits what we know about the language.
<IP_ADDRESS> Vowel loss in long compounds: Given the number of suffixes used in Quenya speech, Quenya words can grow long. Compound words in Quenya in particular can be quite long, and with further suffixes they grow even longer. As such, there is a tendency to reduce the final syllables of compounds to make them shorter and more manageable. One common example of this is words ending in -nórë “land”, as in Valinórë “Vali-land” and Númenórë “West-land”, both of which have simplified forms Valinor and Númenor that are used more frequently.
In general, the final vowel is lost and any long vowel in the non-final syllable is shortened. If the result is a final consonant cluster, that cluster is also reduced but is restored in the stem form. For example quendë is an older word for “elf”, which in compounds reduces to -quen as in Moriquen (Moriquend-) “Dark elf”. Something similar happens with már “home”, whose vowel also shortens in the final syllables of compounds: Eldamar “Elf-home”, Valimar “Vali-home”.
<IP_ADDRESS> Vowel shortening in suffixed words: When directional suffixes are added to longer words whose second-to-last syllable has a long vowel, that long vowel tends to shorten, as in Endorenna “to Middle-earth”, from Endórë “Middle-earth”. That’s because Quenya generally dislikes having adjacent heavy syllables, and one of the heavy syllables can be easily eliminated by shortening the vowel. This doesn’t happen with shorter words: lúmenna “upon [the] hour”.
<IP_ADDRESS> Long-voweled monosyllables: In some cases reducing the long vowel is not practical, especially in monosyllables like ná “to be” or vá “don’t/won’t” where the long vowel is characteristic of the word. In such cases, the vowel may remain long, even when suffixes with consonant clusters are added: nántë “they are”, válmë “we won’t”. Short-vowel variants are also possible if the word is deemphasized: nantë, valmë.
Something similar can be seen for long-voweled monosyllabic nouns like má “hand” with possessive suffixes: márya “his/her hand”, mánta “their hand” (remember: mánta indicates one hand for each member of a group, so Quenya says “their hand” and not “their hands”).
Speculative: There is a special variant for the subject suffix -ssë when added to such words. The double-s in the suffix reduces to a single s when added to monosyllables like ná, á, vá and ui: násë “he is”, ásë “let him”, vásë “he mustn’t”, uisë “he is not”. The short pronoun suffix -s is also possible: nás, vás, uis, except for the indirect imperative ásë (“let him”), which requires -së.
<IP_ADDRESS> How do we know this? Tolkien discussed the reduction of final syllables in compounds and vowel shortening in several places (PE17/106, PE21/32). The shortening of vowels when directional suffixes are added to nouns (Endorenna) was not discussed, but can be deduced from examples and fits Quenya phonology in general. The reduction of 3rd sg. -ssë after long-voweled monosyllable was described in a rough note from 1969:
When stem of noun or verb is long & long [?markers], double cons. was simplified after change of s > z. So nê-sse for nesse has nēse (VT49/28).
Likewise for the retention of the long vowel in má with possessive suffixes, as mentioned in a discussion of the negative verb lá:
lá is usually shortened to la before 2 consonants, according to the usual Q. procedure, but the long vowel can be retained, especially for additional emphasis, as in other cases where pronominal affixes follow a long vowel, as in márya “his hand” (PE22/160).
Tolkien vacillated on this approach. Examples like nanyë, nassë, nalmë with shortened vowels can also be found (VT49/30). Thus, it seems both nányë and nanyë are valid, as indicated in the note above.
Prosodic lengthening is a phenomenon that causes vowels to lengthen and is related to stress. Like stress, prosodic lengthening depends on whether the syllables in a word are heavy (with a long vowel, diphthong or two following consonants) or light (with a short vowel and a single consonant, or just a short vowel). This section discusses the basic mechanisms of prosodic lengthening; later sections will discuss the phenomenon along with the suffixes that are likely to cause it.
<IP_ADDRESS> Conditions Causing Vowel Lengthening: Just as Quenya dislikes having two adjacent heavy syllables, Quenya also dislikes having too many light syllables in a row. Such a sequence of short-vowel syllables can occur when suffixes are added to a longer word. Vowel lengthening can be triggered when the base word is trisyllabic or longer, and one of the following is also true:
Up until this point in the course, we have avoided suffixes that are likely to trigger such lengthening, but we will see a number of them in this chapter. Using the vocalic noun culuma “orange” as an example, noun suffixes that are likely to trigger lengthening when added to longer nouns ending in a vowel include:
Using the consonantal noun Atanatar “Father of Men” as an example, suffixes that are likely to trigger lengthening when added to longer nouns ending in a single consonant include:
Consonantal nouns long enough to trigger prosodic lengthening are rare, and usually are compounds. Consonantal nouns whose stems end in consonant clusters also show no lengthening: Moriquen (Moriquend-) “Dark Elf” → Moriquendion “of Dark Elves”. Finally, the suffixes -i, -in, -ion do not trigger lengthening when added to e-nouns, since they replace the final vowel rather than adding to the base word: telumi, telumin, telumion.
<IP_ADDRESS> Monosyllabic vs. Polysyllabic Suffixes: For monosyllabic suffixes like -va, lengthening is only triggered if both of the preceding syllables are light:
However, if the suffix is two syllables, it triggers lengthening even if the prior syllable is heavy. The genitive partitive plural suffix -lion is one such suffix:
The reason for this has to do with the rules for Quenya stress, which cannot fall further back than the third-to-last syllable. With a monosyllabic suffix, an original stress on the second-to-last syllable is still close enough to the end of the word to retain that stress and prevent lengthening: faLASseva. With a disyllabic suffix, the original stress is push far enough away from the end of the word that the original final vowel can accept the stress and lengthen as a result: falasSÉlion.
<IP_ADDRESS> Lengthening Before Word Boundaries: Another way to think about prosodic lengthening is that Quenya “wants” the stress to mark the boundary between the word and a suffix, by falling on the last syllable of the word. This can’t happen if the base word is disyllabic: the first syllable is already stressed, so the last syllable can’t be. Likewise this can’t normally happen if the second-to-last syllable of the word is stressed because the original stress is again too close to the end of the word. As noted above, it does become possible with the suffix itself is two syllables, because the original stress is now far enough away from the end.
If the suffix itself already begins with a consonant cluster, lengthening is not necessary. For example, with telumenna “to the roof”, the stress already falls on the word boundary: teluMENna. If, however, a suffix with a single consonant is added, then the normal stress rules of Quenya would retract the stress to the third-to-last consonant: without any lengthening **telumeli “some roofs” would be stressed teLUmeli, not on the word boundary. Lengthening fixes this problem: teluméli gets the stress in the right place: teluMÉli.
Strictly speaking, when the suffix is two syllables, the added length is not required because the normal Quenya stress rules would put it into the right place: **telumelion without lengthening would still be stressed on the boundary: teluMElion. But lengthening happens anyway in Quenya, to further emphasize that boundary: telumélion.
All the examples discussed so far have marked the boundaries of a word and a suffix, but the same thing can happen in compounds as well, such as with Cuiviénen “Water of Awakening” = cuivië “awakening” + nén “water” (note that nén also shortens its long vowel in the final syllable of the compound, in keeping with the principles of section §6.1.2 above).
<IP_ADDRESS> Retraction of Lengthening With Further Suffixes: As more suffixes are added to the word, the lengthened vowel may retract further back to mark the new boundary of the added suffix. For example, omentië “a meeting” lengthens its last vowel when the partitive plural suffix -li is added: omentiéli “some meetings”. The lengthened vowel moves back a syllable when the instrumental suffix -nen is added: omentielínen. Something similar happens with compounds: the genitive of Cuiviénen is Cuivienéno “of the Water of Awakening” (PE21/36). This does not happen for “combined” suffixes that are perceived as a unit, such as the genitive partitive plural suffix -lion, which is treated as a single disyllabic suffix.
<IP_ADDRESS> How do we know this? Tolkien used prosodic lengthening regularly in his writings, but did not describe it directly beyond a few hints in his earlier writings: “Where the simple forms occur in long words the preceding vowel is usually long in inflected forms: as falmarin ‘sea-fay’ (masc.), pl. falmaríni” (PE14/43). The rules above are deduced from research into the attested forms that show vowel lengthening, and I believe this is the best explanation for this phenomenon. The vowel lengthening was first noted by Nancy Martsch all the way back in Vinyar Tengwar #13 published in 1990 (VT13/2) and I believe (but have not been able to confirm) that the term “prosodic lengthening” was first used by Alexander Zapragajev.
The key difference between the theory proposed above and other descriptions of the phenomenon I’ve seen elsewhere is that it highlights the role of word and suffix boundaries as the mechanism for where the lengthening occurs. It is very likely that prosodic lengthening originally arose from cases where long vowels were preserved before suffixes but shortened without them. But this alone cannot explain all cases, such as Atanatári, where the ancient form was Atanatar in the singular and Atanatarī in the plural. This is why I think prosodic lengthening is best treated as a pattern that preserves rhythmic stress in modern Quenya words to mark word boundaries.
Here are some vocabulary words having to do with warfare:
Instrumental Summary (Refresher): Here is a quick refresher on the instrumental for the next exercise:
Combine the following elements and indicate how the sounds would change in the combined forms. Capitalized words are names from Tolkien’s Legendarium.
To practice vocabulary words, translate the following to Quenya.
Answers are in Answer Key 6.1 at the end of this chapter.
Quenya actually has two different plurals, a group or total plural (using -i or -r) and a partitive or partial plural (“some”) using -li.
<IP_ADDRESS> Function of the Partitive Plural: There are some interesting interactions in Quenya between the definite article i and the Quenya plural. A definite plural group (with i “the”) refers to a single (limited) group: i eldar matir massa “the elves eat bread” meaning a specific group of elves. Without an article the phrase becomes a general statement, referring to all of elvenkind: eldar matir massa “Elves eat bread”. In this context, the indefinite plural is also a total plural, referring to the entire class of Elves. The plural may still be qualified with other modifiers, as in eldar Lóriendo matir massa “Elves of Lórien eat bread”, but by default this phrase refers to all the elves of Lórien.
Quenya has a different plural suffix -li used to refer to part of a class; this is called the partitive or partial plural (Tolkien used both terms). Its meaning is roughly equivalent to English “some, many”, so eldali matir massa means “some/many elves eat bread”, which is less than all elves. Like English “some”, it also doubles as a way of specifying an indefinite group. For example, eldali túler i ostonna means “some elves came to the city”, that is some indefinite group of elves. You couldn’t say eldar túler i ostonna for an indefinite group, because that would imply all of elvenkind came to the city.
Speculative: Presumably once the indefinite group is mentioned, it would switch to the definite group plural for the rest of the discourse. For example: Eldali túler i ostonna. I eldar merner quetë i aranen. “Some elves (an unknown group) came to the city. The elves (the whole of the previously mentioned group) wanted to speak to the king”. The first instance uses the partitive plural -li for the indefinite group, and the second instance uses the normal plural -r and the definite article i for the now defined group.
<IP_ADDRESS> Forming the Partitive Plural: To form the partitive plural with vocalic nouns, simply add -li to the final vowel. This will trigger prosodic lengthening if the base noun has three or more syllables, but not if the noun has its stress on the second-to-last syllable:
With several consonants, the partitive plural suffix undergoes assimilations: n, r, s all become l when the partitive plural suffix is added. The result is -lli for these as well as nouns ending in l:
Speculative: Other consonants have no suitable assimilations. Those, along with noun stems ending in consonant clusters, use a joining vowel e:
<IP_ADDRESS> Definite Partitive Plurals: In English, “some” cannot be definite; you cannot say “the some elves”. You can, however, say “the many elves”, and this seems to be the connotation when the partitive plural is made definite: i eldali = “the many elves”. It seems this definite-partitive plural formation is rarely used, however, except in poetry where it may be useful for adding an additional syllable.
<IP_ADDRESS> Partitive Plurals and Noun Cases: The partitive plural combines with the Quenya noun cases in various ways; we’ve already seen one instance in Chapter 5, §5.3.1 where we described the dative partitive plural suffix -lin = -li + n “to/for some ...”. Rather than covering all the possibilities here, each combination will be discussed along with each individual noun case.
<IP_ADDRESS> How do we know this? Tolkien described the distinction between the general and partitive plural on numerous occasions (Let/178; PE17/62, 127, 135; PE21/73). For example:
... the two plural forms, the one casual and indefinite, the other particular and complete; so Eldar “Elves as a kind or people, or all the Elves concerned”; Eldali “some Elves, a lot of Elves” (PE17/135).
Thus in Q. Eldar (not with article!) = “Elves, The Elves, All Elves”; i Eldar = “(all) the Elves previously named” (and in some cases distinguished from other creatures); but Eldali “Elves, some Elves”. With Eldali the definite article is seldom used (PE21/73).
We do know the definite article was used at least occasionally with the partitive plural, since i falmalinnar “upon the many waves” appeared in the Namárië poem (LotR/377; RGEO/59). Given that the definite article “is seldom used”, I think it is reasonable to assume it is mainly a poetic devise.
The addition of the partitive plural suffix -li to vocalic nouns is straightforward: simply add the suffix to the vowel, the only complication being possible prosodic lengthening, as discussed above. With consonantal nouns things are less clear. We have only two examples: Casalli “some Dwarves” = Casar + -li (WJ/388) and elelli “some stars” = elen + -li (PE17/127). Both point to consonant assimilation rather than the use of a joining vowel. The other assimilations given above are speculative, based on what we know about the development of Quenya consonant combinations.
Assimilation becomes impossible when clusters are involved, and so a joining vowel is probably used, but we don’t know what it might be. The most common guess is that the joining vowel is e, as it is with the directional noun cases -(e)nna, -(e)llo, -(e)ssë. I think the same is true for individual consonants like t and m for which there are no suitable assimilations.
Here are some vocabulary words having to do with animals:
Partitive Plurals: Partitive plurals describe an indefinite group that is less than the entire class, using the suffix -li = “some, many”.
Translate the following to English:
Translate the following from English to Quenya. There are some new additional vocabulary words as well:
Answers are in Answer Key 6.2 at the end of this chapter.
Quenya has two distinct but similar noun cases, the genitive (using the suffix -o) and the possessive (using the suffix -va or -wa).
<IP_ADDRESS> Function of the Genitive: The genitive case serves a function similar to the English preposition “of”, indicating relationships between things. It can be used to indicate:
The genitive typically follows the noun it is related to, but may precede it also: i atano má “the man’s hand”.
<IP_ADDRESS> Forming the Genitive: The genitive is formed using the suffix -o, which combines with dual and plural suffixes as follows:
| Genitives | Sg. | Du. | Part. Pl. | Pl. |
|---|---|---|---|---|
| vocalic: cirya | ciryo | ciryato | ciryalion | ciryaron |
| e-noun: lasse | lasseo | lasseto | lasselion | lassion |
| consonantal: atar | ataro | ataruo | *atallion | atarion |
The plurals -ion, -ron and partitive plural -lion tend to trigger prosodic lengthening: Atanatárion “of Fathers of Men (Atanatar)”, culumáron “of oranges”, telumélion “of some roofs”. The genitive by itself may also trigger lengthening when added to long consonantal nouns: Ilúvatáro “of Ilúvatar”.
Genitives of nouns ending in -ië are awkward, since they would result in a sequence of three short vowels: márië → máriëo “of goodness”. To avoid this, a consonant n can be inserted before the genitive suffix; this will also trigger prosodic lengthening: máriéno (PE17/59). The extra n is unnecessary in the genitive plural: máriéron “of goodnesses (pl.)”.
<IP_ADDRESS> How do we know this? As with other noun cases, most of what we know about how the genitive is formed comes from the so-called Plotz Letter, a 1966 or 67 letter from J.R.R. Tolkien to Richard Plotz which included a table of noun cases (VT6/14). That letter indicated that the genitive of a-nouns changed the final a to o: ciryo “of a ship”. We have other examples indicating the genitive of o-nouns remains unchanged, such as: Indis i·Kiryamo “The Mariner’s Wife” (UT/8). See below for a discussion of how we know the function of the genitive.
<IP_ADDRESS> Function of the Possessive: The possessive case serves a function similar to the English apostrophe-s (’s), indicating possession, but it is also used for attributes and nouns-as-adjectives. Because of these two functions, Tolkien himself labeled this case the possessive-adjectival case (WJ/369). This case can be used to indicate:
The possessive typically follows the noun it is related to, but may precede it also: i atanwa macil “the man’s sword”.
<IP_ADDRESS> Forming the Possessive: The possessive is formed using the suffix -va or -wa, which combines with dual and plural suffixes as follows:
| Possessives | Sg. | Du. | Part. Pl. | Pl. |
|---|---|---|---|---|
| vocalic: cirya | ciryava | *ciryatwa | ciryalíva | ciryaiva |
| e-noun: lasse | lasseva | *lassetwa | lasselíva | lassíva |
| consonantal: atar | atarwa | *atarúva | *atallíva | *ataríva |
For longer vocalic nouns, the possessive suffix -va is likely to trigger prosodic lengthening: teluméva “roof’s”.
<IP_ADDRESS> Plurality of Possession: One interesting feature of the possessive case is that it behaves in some respects like an adjective (this was its original function). In particular, if the possessed noun is plural, the final -a in the possessing noun becomes -e just as if it were an adjective. Compare: i atanwa macil “the man’s sword” and i atanwe macili “the man’s swords”.
There are two possible dimensions of plurality, for both plural possessors and plural possessions. Either can be singular and plural independently:
<IP_ADDRESS> How do we know this? Again, most of what we know about how the possessive is formed comes from the so-called Plotz Letter (VT6/14). The possessives suffix -wa is fairly well attested for consonantal nouns with individual consonants: andamacilwa (PE17/147), sindarinwa (LotR/1123). It is less clear how the possessive suffix behaves after consonant clusters. Vocalized -ua is currently my best guess, following the suggestions of Raccoon: https://feophan.github.io/tenguesta_ngoldorinwa/morph/nou/#fifth-declension-nouns. The next section discusses how we know the function of the possessive-adjectival case.
<IP_ADDRESS> Distinguishing the Genitive and Possessive: A common shorthand to distinguish the genitive and possessive is that genitive -o is equivalent to English “of” and the possessive is equivalent to English apostrophe-s (’s), but this is misleading because in many circumstances English can use the two interchangeably. There is little difference between “a man’s sword” and “sword of a man” in English.
The clearest distinction between the two is that -va/-wa are used for possessions (things owned) and -o for most other relationships. A basic rules of thumb is that if the thing is a possession that could be given to someone else, use -va/-wa, otherwise use -o. For example, i atanwa macil “the man’s sword” can be given to someone else, and so uses the possessive. But i atano atar “the man’s father” or i atano má “the man’s hand” are relationships that cannot be given away, and so use the genitive.
However, the descriptive function of genitive -o and the adjectival function of -va are very similar, and in many circumstances either can be used. Both alcar Oromëo and alcar Oroméva means “Oromë’s glory” or “the glory of Oromë”. The only distinction between the two is that alcar Oromëo would imply that the glory was something originating from Oromë in the current situation, whereas alcar Oroméva would be the glory inherent to Oromë as a permanent attribute. In many circumstances this distinction is irrelevant, and the choice between the two purely aesthetic. When in doubt, genitive -o is used more frequently (with the exception of pure possession).
<IP_ADDRESS> Definite Genitives and Possessives: Quenya frequently omits the definite article with genitive and possessive constructions in cases where English would use “the”, for example: má atano “the hand of a man”, macil atanwa “the sword of a man”. This is less strange than it seems, because if you were to use a proper possessive in English, it would also omit “the”: atano má “a man’s hand”, atanwa macil “a man’s sword”. The possessive or genitive can be said to fill the determiner slot, making the definite article unnecessary, the difference being that in Quenya, the genitive or possessive is allowed to follow rather than precede the modified noun.
If a definite article is used, it typically marks the definiteness of the modifying noun rather than the modified noun: i atano má “the man’s hand”, i atanwa macil “the man’s sword”. The same is true if the order is reversed: má i atano “the hand of the man”, i macil atanwa “the sword of the man”. With the genitive, the article appears before the definite noun (i atano) but with the possessive it appears before the entire phrase (i macil atanwa). This is because of the adjectival nature of the possessive suffix: Quenya (like English) does not like to have i “the” intervening between an adjective and its noun. If it does, it implies a “to be” statement: i macil i atanwa “the sword [is] the man’s”.
<IP_ADDRESS> Loose Compounds as Genitives: It is possible to have a genitive-like construction simply by putting two words next to each other in a loose compound. Some examples Tolkien gave were cirya tyulma “a ship mast” (PE21/80) and Oromë róma “an Oromë horn” (WJ/368). The meanings are roughly the same as “a mast of a ship” and “a horn of Oromë”. English has a similar construction with roughly the same meaning. Quenya is particularly inclined to use this construction when the modified noun is indefinite, since ciryo tyulma “a ship’s mast” or tyulma ciryo “[the] mast of a ship” would imply a specific mast of the ship in question, the same way that “Orome’s horn” implies a specific horn in English, and “a horn of Orome” is needed to imply an indefinite horn.
<IP_ADDRESS> The Last Declinable Word: Like English, adjectives in Quenya usually precede the noun they modify, but in Quenya they may occasionally follow it instead. Where such a thing happens, any noun case it is added at the end of the noun phrase, not just on the noun itself. This might happen, for example, when an adjective is used as an epithet: Aracorno Turca “Aragorn [the] Strong”. If a noun case were applied to this phrase, the case ending would be added to turca: macil Aracorno Turco “sword of Aragorn the Strong”, quenten Aracorno Turcan “I spoke to Aragorn the Strong”.
This rule cannot apply if the last word in a noun phrase already has a case ending: quenten heston i arano “I spoke to the captain of the king”. Since arano is already in the genitive, it cannot take another case ending, so the dative ending -n is applied to hesto “captain”.
<IP_ADDRESS> How do we know this? Tolkien’s most detailed description on the function of both the genitive and possessive cases appears in the Quendi and Eldar essay written in 1959-60 (WJ/368-369). Most of the discussion above is based on that essay.
Tolkien mentioned the differing behavior of the definite article with genitive and possessive in a couple places (PE17/13, PE22/80). The second of these has a useful set of examples:
In some cases the meanings of singular -o coalesced with -va: as e.g. in kirya tyulma “a ship-mast, ship’s mast, mast of an unspecified or any ship”; tyulma kiryo “the mast from some ship, of some ship”; tyulma i kiryo “the mast of the ship” or i tyulma kiryava (PE22/80).
This example is the basis of the notion above that the definite article i cannot intervene between the possessed noun and the possessive. It also illustrates the function of loose compounds as genitive-like constructions.
“The Last Declinable Word” rule was mentioned by Tolkien in notes appearing with Cirion’s Oath: “as is usual in Quenya in the case of two declinable names in apposition only the last is declined” (UT/317).
Here are some vocabulary words having to do with time:
Genitive Summary: The genitive noun case is for relationships similar to those with English preposition “of”:
| Genitives | Sg. | Du. | Part. Pl. | Pl. |
|---|---|---|---|---|
| vocalic: cirya | ciryo | ciryato | ciryalion | ciryaron |
| e-noun: lasse | lasseo | lasseto | lasselion | lassion |
| consonantal: atar | ataro | ataruo | *atallion | atarion |
The genitive is used for:
Possessive Summary: The possessive noun case is for relationships similar to those with English apostrophe-s (’s):
| Possessives | Sg. | Du. | Part. Pl. | Pl. |
|---|---|---|---|---|
| vocalic: cirya | ciryava | *ciryatwa | ciryalíva | ciryaiva |
| e-noun: lasse | lasseva | *lassetwa | lasselíva | lassíva |
| consonantal: atar | atarwa | *atarúva | *atallíva | *ataríva |
As with adjectives, the final vowel a of the possessive becomes ë when the thing possessed is in the plural: atanwë macili “a man’s swords”, atanívë macili “men’s swords”.
The possessive is used for:
This second descriptive use is often interchangeable with the genitive. The main distinction in descriptive use is that -va tends to be used for innate attributes, while -o is used of attributes applicable in the moment: alcar Oromëo = “Orome’s glory (in the moment)” vs. alcar Oroméva = “Orome’s (inherent) glory”.
Translate the following from English to Quenya. Pay particular attention to cases where Quenya would use genitive -o vs. possessive -va, as well as cases where it is ambiguous.
Translate the following from Quenya to English as vocabulary practice:
Answers are in Answer Key 6.3 at the end of this chapter.
This section discusses the differences between definiteness and indefiniteness in Quenya, and how the use of the Quenya definite article i differs from English “the”.
<IP_ADDRESS> Function of the Definite Article: Before we can discuss the definite article, we must first discuss what it is used for in a sentence. Both English “the” and Quenya i are used to mark a definite or specific known thing within a discourse, as opposed to some unknown or unspecific thing. In both languages, if you were to say elda túlë i ostonna “an elf came to the city”, it would be some indefinite or unspecific elf, but if you were to say i elda túlë i ostonna “the elf came to the city”, it would mean the elf is specific and known to both the speaker and the listener.
The most common way for a noun to become definite is for it to have been introduced previously in the conversation. Consider:
The first mention of the elf is indefinite, because presumably he or she is unknown to at least one participant in the conversation. The second mention of the elf becomes definite, however, because it refers back to the (now specified) elf that was previously mentioned. Prior mention is not the only reason a word might be marked definite, however. In the second sentence i aranen “to the king” is also marked as definite, the implication being that there is some specific known king to whom the elf wished to speak, presumably the king of the city. If you were to say i elda mernë quetë aranen “the elf wanted to speak to a king”, then presumably the Elf did not care which king he or she would talk to. Consider also these two sentences:
The first sentence implies there are multiple windows in the room, and any of these windows may be opened. The second sentence implies there is one specific window that should be opened, either because it is the only one in the room, or it is the window next to the listener.
<IP_ADDRESS> Definite Article Usage: Quenya uses the definite article less often than English. The circumstances where both English and Quenya use a definite article are when:
Both English and Quenya do not use the definite article with proper names, even though it has a specific referent: Elerondo but not **i Elerondo “the Elrond”, except perhaps when distinguishing multiple Elronds: i Elerondo Imladrisso “the Elrond of Rivendel” (as opposed to some other Elrond). However, one difference between English and Quenya is that English uses “the” to mark unique things like the Sun, Moon or sky, while Quenya does not:
Something similar happens with epithets (nicknames) following a name: English uses “the” but Quenya omits the definite article:
English also uses “the” with a determining adjective like first, last, highest, etc, while Quenya does not:
Note that the i in the Quenya sentence above is not the definite article, but rather is the indeclinable relative pronoun i “who, which, that”.
<IP_ADDRESS> Forms of the Definite Article: The definite article almost always has the form i, and it is generally resistent to elision because otherwise it would vanish entirely. It sometimes causes elision for preceding vowels, however: ar’ i mindon “beside the tower”, á mat’ i massa “eat the bread”. There is also an alternate form of the definite article in which is used occasionally. We only have a couple examples of its use in Tolkien’s later writings:
For the second example, the phrase was deleted and the final version of the sentence had only (singular) i indo Sindicollo “the mind of Thingol”. Both these examples have two things in common: the following word begins with a vowel and the following word is plural. I think it is likely that in is an archaic plural form of the definite article, which is occasionally used before plurals beginning with vowels. There are plenty examples where in is not used, which makes me believe the use of in is optional: i eleni “the stars” (LotR/377), i arani “the kings” (WJ/369).
Finally, there is the unusual example:
Here ’n seems to be an elided variant of in, even though the following noun is not plural. Speculative: I think something different is going on here, because the use of the ordinary article would result in several sequential vowels: utúlië i aurë. This is difficult to pronounce, so my working theory is that when i is “squeezed” between two vowels it reduces to ’n. See the discussion in section <IP_ADDRESS> Elision with i “the” above.
<IP_ADDRESS> How do we know this?: Tolkien did not describe Quenya’s rules for when it does or does not use the definite article i. The above is largely deduced from observations of how Tolkien used Quenya i in actual sentences. My own interpretation of these rules is based largely on Raccoon’s research into the topic, which is much more thorough than mine. See https://feophan.github.io/tenguesta_ngoldorinwa/syntx/art/.
The occasional appearance of in was also not explained by Tolkien in his later writings. In his earliest iterations of Quenya grammar from the 1920s, in and n’ were variants of i “the” used before vowels and had nothing to do with plurality (PE14/42). However, shortly after this Tolkien introduced in as a plural definite article in the Sindarin branch of the Elvish languages (PE13/120). Tolkien largely abandoned the use of Quenya’s prevocalic n’ while retaining plural in for Sindarin. Our two known Quenya uses of in from Tolkien’s later writing are both (a) prevocalic and (b) plural, so I suspect that they represent remnants of an archaic plural definite article that had faded from use in Quenya but survived in Sindarin.
The definite article works differently with plurals. A definite group, i eldar “the elves”, implies a specific group of elves. An indefinite group, eldar “Elves”, implies the statement is applicable to any elf and hence is true of all of Elvenkind. Consider:
In the first, a specific known group of Elves is eating bread. In the second statement, since this group is not specified, the implication is that it is a general statement meaning all of Elvenkind eats bread. If you want to indicate an unspecified group that is less than all of Elvenkind, in English you use the word “some” and in Quenya you use the partitive plural suffix -li.
The partitive plural is usually indefinite, and only rarely is used with the definite article i. Speculative: When it is, however, the implication is that the definite group is large (“many”).
How do we know this?: See the discussion in section §<IP_ADDRESS> on where the information we have on the partitive plural comes from, and how it ties to (in)definite plurals.
According to Tolkien the “article = ‘the’ [i] is usually not used when noun is defined by a possessive [-va] or genitive [-o]” (PE17/13). This is consistent with Tolkien’s use of the possessive and genitive noun cases, where the modified noun rarely has the definite article. Thus where English would say “I saw the captain of the orcs”, Quenya would say tirnen hesto i orcoron. Here hesto does not need an article, because it is already defined by the qualifier i orcoron.
This is less strange than it seems. If the sentence were rearranged slightly, English would also omit the definite article: “I saw the orcs’ captain”, tirnen i orcoron hesto. In English, the possessive (the orcs’) fills the determiner slot, making a second “the” redundant: “I saw the orcs’ **the captain”. The same is true of Quenya, but since the genitive or possessive can both precede or follow the modified noun, the definite article i is redundant either way: atanwa macil or macil atanwa both mean “a man’s sword”.
While the definite article is typically not used with the modified noun, it can still be used with the modifying noun to mark whether it is definite. For example, with the possessive suffix -va, the article i can still be applied to the possessor. Thus atanwa macil mean’s “a man’s sword” (some unspecified man) but i atanwa macil means “the man’s sword”, referring to some specific man. The same is true of the genitive: i atano má “the man’s hand” vs. atano má “a man’s hand”.
Things are a bit more complex if the order is reversed. With the genitive, the definite article precedes the modifying noun: má i atano “the hand of the man”. With the possessive, however, the definite article precedes the entire phrase: i macil atanwa “the sword of the man”. This is because the possessive functions more like an adjective and the article cannot intervene between a noun and its adjective. In fact i macil i atanwa would likely be interpreted as a “to be” expression: “the sword [is] the man’s”.
Despite the discussion above, the definite article is sometimes applied to a noun modified by a possessive or genitive if there is a more general principle requiring it. Consider:
Here coimas “waybread” is being used as an abstract concept, not referring to any particular waybread, and so is analogous to phrases like i macil (ná) turwa tamma ohto “the sword is a powerful tool of war”. As such, it requires the definite article. If it referred to actual bread rather than the concept of bread, the i would not be required, because it would be defined by the genitive: camnelvë coimas i(n) Eldaron “we received [the] waybread of the Eldar” or “we received the Eldar’s waybread”.
How do we know this?: See the discussion in section §<IP_ADDRESS> on our sources of information for the relationship between the genitive/possessive and the definite article.
Here are some vocabulary words having to do with quantities:
Definite Article: The Quenya definite article is i “the”, but it is used less often than in English.
Translate the following to Quenya, paying particular attention to phrases where Quenya would omit the definite article even though English uses it:
Translate the following to English as vocabulary practice:
Answers are in Answer Key 6.4 at the end of this chapter.
This section discusses the Elvish numbering system, and how Elves go about counting and writing numbers.
The first twelve Quenya numbers are:
In the 1930s Tolkien used tolto for “eight” and cainen for “ten”. You might see both of these alternate forms in Neo-Quenya writing, but in the late 1960s he replaced these with toldo and quëan respectively. These numbers are used for counting things, but Quenya has two special alternate words for “one” and “two”:
The word er applies to a single thing that is unique (or is situationally unique), as opposed to min which applies to one out of a group or the first item counted in a list. If you were to say min macil “one sword” it would mean you want one sword out of a group of possible swords, but er macil would imply there is only one sword to begin with: “the one sword, the only sword”. Similarly, min oron would be one mountain in a mountain range but er oron would be one mountain standing alone; the number er is thus related to eressëa “lonely”. Similarly, yúyo “both” refers to pairs, so yúyo macil would mean “both swords” as a set, but macil atta “two swords” would mean any two swords will do.
The last example macil atta illustrates a peculiar feature of Quenya, a side effect of its dual formation: when referring to two of something, the singular form of the noun is used, which would be like saying “two sword” in English. See section <IP_ADDRESS> Noun Duals for further discussion. For numbers three and larger, the plural form is used: macili neldë “three swords”, macili canta “four swords”, etc.
Furthermore, for numbers two and larger, the number follows the noun rather than preceding it, as shown above. This makes numbers particularly prone to “The Last Declinable Word” rule (see section §<IP_ADDRESS>). However, only the number two (atta) can accept case endings; other numbers are indeclinable so the noun receives the case ending: quenten elda attan “I spoke to two elves” but quenten eldain neldë “I spoke to three elves”.
The numbers from the previous section, min, atta, neldë, etc., are cardinal numbers used for counting things. Quenya also has a set of ordinal numbers for ordering things:
The pattern for converting cardinals to ordinals is straightforward: simply change the final vowel to -ëa. The only exceptions are minya “first” and quainëa “tenth”, the latter because quëan [probably] becomes quain in compounds (see below). As discussed in section <IP_ADDRESS> Definite Article Usage, it seems Quenya (unlike English) does not use a definite article with determining adjectives like ordinals, so Quenya would say attëa elda ter i ando (without i “the”) whereas English would say “the second elf through the gate” using “the”.
Tolkien gave us examples of Quenya numbers from thirteen to nineteen, though some of these only appeared in their ancient Elvish form so that modern forms need to be extrapolated:
Speculative: Tolkien did not describe larger numbers in his later writings, but he did describe them in the 1920s when the Quenya word for “ten” was cainen: yucainen, nel(de)cainen, can(ta)cainen “twenty, thirty, forty” (PE14/49). Extrapolating these to the 1960s paradigm where “10” became quëan/-quain:
Also based on Tolkien’s earlier writing, it seems Quenya writes smaller number first and then larger numbers, so lempë yuquain “five twenty” = 25 instead of the English order “twenty five”. This is also consistent with how Quenya digit are written in reverse order from English: “nine thousand two hundred sixty four” would be written in Quenya with the order 4629 (ôöòù) rather than 9264.
Quenya has two different numbering systems, regular decimal numbers (base 10) and duodecimal numbers (base 12). Quenya uses the same set of digits for both:
The digit “zero” is 0 (we don’t know its Quenya name). As noted above, Quenya digits were written in the reverse order from English numbers, so decimal value 1000 would be written ðððñ. Underdots could be used to mark a duodecimal number, so ðOðOðOñO would be 100012 (base-12) or 1728 as a decimal number. If it is necessary to distinguish them, decimal numbers can be represented with overdots. Thus ðTðTðTñT would be 100010 (base-10) = “one thousand”.
Beyond their digits, we don’t know much else about duo-decimal numbers in Quenya. There is a word yurasta “24” = two twelves in notes from the 1930s (PE14/17). Speculative: It is possible that -rasta plays a role for duodecimal numbers similar to that of -quain for decimal numbers, so that:
But these are just guesses with no real evidence, so I’d recommend sticking to decimal numbers for purposes of Neo-Quenya.
Much of the discussion on Quenya numbers above is drawn for several documents Tolkien wrote on Eldarin Hands, Fingers & Numerals from the late 1960s (VT47/3-17; VT48/4-14). The discussion of ordinals is based on notes on Eldarin numerals (VT42/24-27) associated with an essay on The Rivers and Beacon-hills of Gondor, also from this same period.
These documents introduced a new name for “10”, the word quëan or quain, the latter given in parentheses (VT48/6). Tolkien abandoned earlier cainen “10” because this form was identical to cainen “I laid”, the 1st person past tense of caita- “to lay” (VT48/12). Since quain was in parenthesis, I think quëan is the independent word for “10” as derived from primitive kwayam (VT42/24), whereas quain is a reduced form used in compounds (< kway’m), as evidenced by its appearance in quainëa “tenth” (VT42/25).
These 1960s documents also included words for 13 to 19 (VT48/21), but two were only given in their primitive Elvish forms: nelekwe “13” and kanakwe “14”. The modern forms *nelquë and *canquë must be extrapolated from these, with *nelquë supported by nelquëa “thirteenth”. The third form tolokwe “18” might be a slip for modern *toloquë, or it might be a primitive form; I personally think it is primitive, and the modern form would be *tolquë.
Numbers larger than 19 only appear in Tolkien’s earlier writings from the period where the word for “10” was kainen. The Early Qenya Grammar of the 1920s gives numbers 20 to 90, with the pattern: yucainen, nel(de)cainen, can(ta)cainen “twenty, thirty, forty”, etc. (PE14/49). These can be readily updated by changing -cainen to -quain, with some other minor tweaks.
The placement of small numbers before larger ones is consistent both with Tolkien’s 1920s number system and how Quenya digits work. The placement of numbers after the noun they modify was mentioned in notes from the 1960s, as well as the unusual use of singular nouns with the number 2: elen atta “two star” vs. eleni neldë “three stars” (VT49/44-45). This same note also describes how atta “two” follows “The Last Declinable Word” rule but other numbers do not.
The existence of the alternate duodecimal number system is something Tolkien mentioned several times, including in The Lord of the Rings itself (LotR/1107). We don’t know much about this system other than a discussion of tengwar digits, first published in the magazine Quettar issues #13 and #14. Aside from that, we only have a few isolated words like yurasta “twenty four = two twelves” (PE14/17). This makes any use of the duodecimal system very speculative.
The numeral glyphs presented in the Quettar article are reproductions by Christopher Tolkien, not Tolkien’s original writing, so they may not be correctly represented. They may also not be the only system Tolkien considered: the number digits in the King’s Letter written around 1950 are quite different in form; see the discussion at https://www.forodrim.org/daeron/md_kl_num.html.
Number Summary: Smaller numbers are:
Larger numbers are:
Two special numbers are used for solitary items and pairs:
Numbers larger than one follow the noun:
Ordinal numbers (mostly) change the final vowel to -ëa:
Combined numbers put the smaller digit first, followed by the larger one: canta lepenquain “four fifty”, instead of the English order “fifty four”.
Translate the following to English:
Answers are in Answer Key 6.5 at the end of this chapter.
Cirion’s Oath was the promise of allegiance between Gondor and Rohan given by Cirion, steward of Gondor, to then king of Rohan Eorl in the 26th century of the Third Age (UT/305). Tolkien only translated the end of the oath into Quenya. This text has several examples of places where Quenya omits the definite article i in circumstances where English would include it (see section 6.4 Definite vs. Indefinite). Before discussing the oath proper, we introduce some vocabulary:
We break up the text into four phrases to simplify analysis:
Vanda sina termaruva Elenna-nóreo alcar enyalien
ar Elendil Vorondo voronwë.
Nai tiruvantes i hárar mahalmassen mi Númen
ar i Eru i or ilyë mahalmar ëa tennoio.
Broken down literally this is:
Vanda sina termar-uva Elenna-nórë-o alcar enyalie-n
Oath this endure-will Elenna-land-’s glory memory-for
ar Elendil Vorond-o voronwë
and Elendil Faithful-of faith
Nai tir-uva-nte-s i hára-r mahalma-sse-n mi Númen
May watch-will-they-it those (are sitting)-(pl.) throne-on-(pl.) in West
ar i Eru i or ilyë mahalma-r ëa tennoio
and the One who above all throne-(pl.) exists forever
First Phrase: Vanda sina termaruva Elenna-nóreo alcar enyalien. The beginning half of the first phrase is simple: vanda sina termaruva “this oath will endure”, the only unusual bit being the placement of sina “this” after the noun vanda “oath”. The second half is more tricky. The verb termar- “to endure” is an intransitive verb and cannot have a direct object, but it can have an indirect object: enyalien “for memory”. The preceding alcar is a loose compound used as a genitive (see section §<IP_ADDRESS>), so alcar enyalien “for glory-memory” = “for memory of glory”. The preceding Elenna-nórëo is an ordinary descriptive genitive meaning “Elenna-land’s”, so the closest translation that would be valid English is: “for Elenna-land’s glory-memory”.
This phrasing is pretty awkward English, however, so revising the phrase to use the preposition “of” (and also reversing the order) would result in “for memory of [the] glory of [the] land Elenna”; the definite article i is missing from the Quenya phrase because Quenya does not require a definite article for words governed by a possessive or genitive (see section §<IP_ADDRESS>). The entire phrase would translate as “This oath will endure for memory of the glory of the land Elenna”. Note that Elenna “Starwards” is another name for Númenor.
Second Phrase: ar Elendil Vorond-o voronwë. The second phrase has the name Elendil Voronda “Elendil [the] Faithful”, with Elendil being his name and Voronda “[the] Faithful” being an adjectival epithet, without i “the” because the definite article is not required before epithets in Quenya (see section §<IP_ADDRESS>). The phrase follows “The Last Declinable Word” rule (see section §<IP_ADDRESS>), so the genitive suffix -o is added to Voronda, changing the final a to o as usual (see section §<IP_ADDRESS>). The entire genitive phrase applies to voronwë “faith”, so that the meaning is “and Elendil the Faithful’s faith”. Again the English wording can be made less awkward by using “of” and reversing the order: “and the faith of Elendil the Faithful”.
Third Phrase: Nai tiruvantes i hárar mahalmassen mi Númen. The verb in the third phrase is tiruvantes, decomposing to tir-uva-nte-s = “they will watch it”. The preceding nai indicates this is a wish (see section §3.4.3), so a more complete translation would be “may they watch it”. The “it” being watched is the oath (vanda), and the “they” is specified by the remainder of the phrase: i hárar mahalmassen mi Númen “who sit on thrones in West”. Note how the verb hárar “sit” is plural to agree with its indirect referent -ntë “they”.
The word mahalmassen “on thrones” is a locative plural (mahalma-sse-n). In theory “in West” could be locative as well. However, Quenya feels awkward using repeated locatives, the same way English feels awkward with repeated prepositions. As such, the phrase uses the preposition mi “in” instead. Note that mi Númen “in [the] West” lacks the definite article i because it describes a unique location, and universally unique things do not use the definite article in Quenya (see section §<IP_ADDRESS>). A full translation of the phrase would be “May they watch it, [those] who sit on thrones in the West”; English requires an additional “those” to be grammatically correct. Based on context the “they” are clearly the Valar of the Uttermost West.
Fourth Phrase: ar i Eru i or ilyë mahalmar ëa tennoio. The i Eru is the main noun of the fourth phrase, but this noun has no associated verb because Eru is another participant in the watching of the third phrase: “they (the Valar) and Eru” are both watching the oath. It is odd that Eru is preceded by the definite article i, but here Eru is used as a title rather than a name, so that i Eru = “the One” much like how in English you might say “the Lord” in reference to God.
The remainder of the phrase further qualifies the identity of Eru: i or ilyë mahalmar ëa tennoio “who above all thrones exists forever”. Thus the translation of the fourth phrase is “and the One who above all thrones exists forever”.
Putting the above together, a full translation of the oath would be:
This oath will endure for memory of the glory of the land Elenna,
and the faith of Elendil the Faithful.
May they watch it, [those] who sit on thrones in the West,
and the One who above all thrones exists forever.
Tolkien’s actual translation was:
This oath shall stand in memory of the glory of the Land of the Star,
and of the faith of Elendil the Faithful,
in the keeping of those who sit upon the thrones of the West
and of the One who is above all thrones for ever.
This translation is somewhat loose, with various minor prepositional changes to make the English flow better. In two places Tolkien was quite liberal with the translation. The English phrase “of the Land of the Star” is based on the English meaning of the name Elenna “Starwards”, so “of the land Starwards” becomes “of the Land of the Star”. The English phrase “in the keeping of” is a rewording of “may they watch it” with the same general sense but a completely different set of words.
Warfare:
Animals:
Time:
Quantity:
Numbers:
Large Numbers:
Miscellaneous:
<IP_ADDRESS> Quenya Vowel Shifts Summary:
<IP_ADDRESS> Partitive Plural Summary: Partitive plurals describe an indefinite group that is less than the entire class, using the suffix -li = “some, many”.
<IP_ADDRESS> Genitive Case Summary: The genitive noun case is for relationships similar to those with English preposition “of”:
| Genitives | Sg. | Du. | Part. Pl. | Pl. |
|---|---|---|---|---|
| vocalic: cirya | ciryo | ciryato | ciryalion | ciryaron |
| e-noun: lasse | lasseo | lasseto | lasselion | lassion |
| consonantal: atar | ataro | ataruo | *atallion | atarion |
The genitive is used for:
<IP_ADDRESS> Possessive Case Summary: The possessive noun case is for relationships similar to those with English apostrophe-s (’s):
| Possessives | Sg. | Du. | Part. Pl. | Pl. |
|---|---|---|---|---|
| vocalic: cirya | ciryava | *ciryatwa | ciryalíva | ciryaiva |
| e-noun: lasse | lasseva | *lassetwa | lasselíva | lassíva |
| consonantal: atar | atarwa | *atarúva | *atallíva | *ataríva |
As with adjectives, the final vowel a of the possessive becomes ë when the thing possessed is in the plural: atanwë macili “a man’s swords”, atanívë macili “men’s swords”.
The possessive is used for:
This second descriptive use is often interchangeable with the genitive. The main distinction in descriptive use is that -va tends to be used for innate attributes, while -o is used of attributes applicable in the moment: alcar Oromëo = “Orome’s glory (in the moment)” vs. alcar Oroméva = “Orome’s (inherent) glory”.
<IP_ADDRESS> Definite Article Summary: The Quenya definite article is i “the”, but it is used less often than in English.
Tengwar answers:
Tengwar answers:
Tengwar answers:
Tengwar answers:


Preparation time
less than 30 mins
Cooking time
10 to 30 mins
Serves
Serves 4
James Martin serves up poached salmon with a classic English parsley sauce and sautéed leeks
In a saucepan over a medium heat, bring the milk, studded onion, bay leaf and peppercorns to a simmer.
Add the salmon to the pan, and bring back up to a simmer and poach the salmon for 10 minutes.
Remove the salmon from the milk and set aside, and strain the milk into a bowl.
In a separate saucepan melt half the butter over a medium heat, then stir in the flour and cook for a few minutes until light golden-brown.
Whisk in the reserved milk and bring to a simmer, whisking all the time until the sauce has thickened.
Whisk in the double cream and parsley.
Taste and adjust the seasoning with salt, black pepper and lemon juice.
Heat a frying pan until medium hot add the last of the butter and the leeks and sweat for 4-5 minutes until just softened.
Season with salt and black pepper.
To serve, spoon the diced leeks into the centre of the plate. Top with a piece of poached salmon then spoon the parsley sauce over. Halve the remaining lemons and wrap in clean muslin, then tie with a piece of string and serve alongside.


Ghostbusters: Afterlife’s first trailer channels Stranger Things
Avoid moving into creepy farmhouses
by Megan FarokhmaneshGhostbusters is returning to the big screen once more — this time with a true sequel to the original films. The first trailer for Ghostbusters: Afterlife sets the stage for a small town haunting as a single mom and her two kids try to start a new life.
While the family tries to settle down in their creepy old farmhouse, the town is plagued by strange earthquakes and unexplainable phenomena. Stranger Things-esque vibes aside, the trailer also teases a clear connection to the original Ghostbusters crew — particularly to the bespectacled Egon (played by the late Harold Ramis). The film’s original cast, including Bill Murray, Dan Aykroyd, and Ernie Hudson, are also expected to reprise their roles.
Ghostbusters: Afterlife stars Paul Rudd, Carrie Coon, Mckenna Grace, and Finn Wolfhard. It will arrive in theaters in July 2020.


{{template "header" .}}
{{template "navbar" .}}
2b2tq.
Revolutionizing Anarchy Markets
LEARN MORE
FAQ
♪ rainbow roads ♪
♪ lets-a-go ♪
♪ it's-a-me ♪
♪ Mario ♪
♪ Mushroom Kingdom ♪
♪ Peachy Mama ♪
♪ lets-a-go♪
♪ rainbow roads ♪


?Jamaica
I8aO
2
4.33T.
Det.-rev.
M.
Tniv
(B)
2001
Lisianthius
capitatus
Urb.
R.
E.
WEAVER,
JR.
19/0
Duke
University
Herbarium
'.ÔR.u.WÁlloon.
i
EX
HERB.
HORT.
BOT.
REG.
KEW.
IbEMbl?
1624617
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high


Pedregal is approx. 26 miles up an estuary/river from Boca Chica. It is the port for the large city of David. You will need to enter the river on a rising tide because of the shallow water and should plan on a 2 day trip up river to Pedregal because of that.
Known as "The Lost Coast” of The Republic of Panama, the Chiriqui Lowlands near the city of David are famous for dozens of little islands, world class fishing, scuba diving and boating. It is among the most picturesque regions of Panama.
The Chiriqui gulf region encompasses Coiba Island to the East, home to some of the best sport fishing in the Pacific, and stretches West to the Costa Rican border in the Province of Chiriqui. This area includes the 14,600 acre National Wildlife Reserve-La Barqueta Beach, the 36,400 acre Gulf of Chiriqui National Marine Park and the 667,000 acre Coiba Island National Park - which is only 20% terrestrial.
This is the closest place to refuel if coming from Costa Rica, however it is also possible to refuel at Boca Chica with advance warning.
Read Panama Formalities for detailed information on procedures for clearing into and out of Panama.
Pedregal has facilities for clearance.
On departure from Pedregal expect to pay US$25 for inspection of the boat and an anchoring fee and light dues (approx. US$20). An International Zarpe costs approx. US$13.
Note: For the latest updates from cruisers on immigration fees charged here, see the following report.
Last updated December 2012.
There is a marina here with fuel and good water. You can anchor out in front of the marina.
Last updated May 2012.


REVERSO
Copyright (c) 2003 Sébastien Blondiau
This game is played on the following 8x7 square board:
- TURN - On each turn, each player must move one of his friendly pieces.
- Zapperyellow (stack of size 1), or ZY:
- Moves forward or sideways to an (orthogonal or diagonal) empty cell.
- ZYs may capture enemy ZY stones by jumping over them (also forward or sideways) and landing on the immediate empty cell (which must be empty). The captured stone is removed. Captures are not mandatory but may be multiple (i.e., after the first capture, the piece may continue capturing if possible).
- A ZY in the player's first row cannot move sideways.
- When a ZY arrives at the last row, it cannot move.
- ZY may move onto friendly ZYs on the last row, up to the maximum of three pieces stacked together.
- ZY may also be used to activate an adjacent friendly ZG (check below). This counts as a move.
- Zapperblue (stack of size 2), or ZB:
- Moves to any adjacent (orthogonal or diagonal) empty cell.
- ZBs cannot move to cells in the first or last row.
- Captures enemy pieces (except deactivated ZGs) by replacement. Captures are not mandatory nor multiple.
- Zappergreen (stack of size 3), or ZG:
- Slides up to three cells in any orthogonal or diagonal line.
- ZGs cannot move to cells in the first or last row.
- ZGs capture as ZYs (with the exception that they can move up to three cells before he capturing jump). ZGs may capture ZYs, ZBs (which are removed) and also the activated ZG (which is not removed but becomes deactivated).
- GOAL - The winner is whoever brings more ZYs to his last row.
In the original rules, ZG would have an extra move range (it could move one more cell), if the player won the last game. However, this rule only makes things more unbalanced to the best player.


HEARTS IN ATLANTIS A film review by Mark R. Leeper
CAPSULE: In 1960 an eleven-year-old forms a friendship with an elderly man who boards at his house. Scott Hicks directs with a great deal of period feel. Anthony Hopkins stars as the mysterious Ted Brautigan. The story is told sentimentally and well until the script or perhaps the story falters in the final reel. Rating: 7 (0 to 10), low +2 (-4 to +4)
Stephen King made his reputation on writing horror and that still seems to be the major portion of his output. These days, however, the films made from his horror stories are definitely of secondary quality to those that do not have strong fantasy content. King is better when he concentrates on human drama than on the supernatural. This film based on only one part of his novel HEARTS IN ATLANTIS basically ignores most, though not all, of the fantasy elements of the book.
Robert Garfield (played by David Morse) is a photographer returning to the neighborhood where he grew up. He is visiting the funeral of a childhood friend. He asks about Carol Gerber, the girl who was the other close friend, only to discover that she had recently passed away. Robert thinks back to 1960 when he was eleven. Bobby (played just a little too maturely by Anton Yelchin) lived with his widowed mother. Then boarder Ted Brautigan (Anthony Hopkins) comes to live with the Garfields. Though his mother takes an immediate dislike to him, for Bobby the boarder opens up new worlds. Ted turns Bobby onto the world of literature and forever changes Bobby's outlook on the world.
Bobby and Ted's relationship is made difficult by Bobby's mother (Hope Davis), a woman who makes all the wrong decisions in her own life and blames the result on others.  Bobby's mother is right about Ted in at least one regard. There is something not normal about the recluse. He seems to have psychic powers that tell him things about the future. And Ted is on the run from men who know about those powers and want to use them. The book's fantasy element is much reduced in the William Goldman (MARATHON MAN, THE PRINCESS BRIDE) adaptation of one section of the book by Stephen King. Scott Hicks who directed SHINE and SNOW FALLING ON CEDARS directs here. In general his style is nostalgic and romanticized, though he somewhat unimaginatively creates a lot of the mood by playing the popular music of the 1960 period. Also though the cars we see seem a bit old for the setting. Goldman's or King's view of the "good kids" is a little too Simon Pure and cliched as he follows them down railroad tracks and swimming at the local water hole, slaking their thirsts with the carton of milk they brought along. Nobody I remember was that good a kid. Once he has lulled us into this idyllic view of 1960 the introduction of some nasty violence in the latter part of the film comes as something of a shock.
HEARTS IN ATLANTIS is a Castle Rock Entertainment production. They do the best adaptations of Stephen King, including the now classic THE SHAWSHANK REDEMPTION. HEARTS IN ATLANTIS is a cut below that film, but still a good production. I rate it 7 on the 0 to 10 scale and a low +2 on the -4 to +4 scale.
Mark R. Leeper<EMAIL_ADDRESS>Copyright 2001 Mark R. Leeper
-- Mark R. Leeper,http://www.geocities.com/markleeper/ Or try your search engine on "Mark Leeper"
========== X-RAMR-ID: 29536 X-Language: en X-RT-ReviewID: 251122 X-RT-TitleID: 1110107 X-RT-AuthorID: 1309 X-RT-RatingText: 7/10
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


I was born in Macao. I finished my primary and and secondary level at the Macao Sam Yuk School. HighSchool life was a quite boring since every one was very serious when it comes in studying. And now hoping I will finish my college level here in University of the Cordilleras.


#include <ObstacleAvoidanceModule.h>
| ObstacleAvoidance::ObstacleAvoidance |
( |
| ) |
|
class constructor
11 frontObstacle =
false;
14 rightObstacle =
false;
| void ObstacleAvoidance::detectObstacle |
( |
int |
front, |
|
|
int |
back, |
|
|
int |
left, |
|
|
int |
right |
|
) |
| |
Detects obstacles.
- Parameters
-
| front | front sensor reading |
| back | back sensor reading |
| left | left sensor reading |
| right | right sensor reading |
- Returns
- void function does not return anything
18 if (std::isless(front,0) || std::isless(back,0) || std::isless(left,0) || std::isless(right,0))
19 throw std::domain_error(
"Negative arguments are invalid");
21 std::cout <<
"Object Detected in forward path\n";
25 std::cout <<
"Object Detected in backward path\n";
29 std::cout <<
"Object Detected in left path\n";
33 std::cout <<
"Object Detected in right path\n";
| void ObstacleAvoidance::trnOnOffAvoid |
( |
int & |
frontSpd, |
|
|
int & |
backSpd, |
|
|
int & |
leftSpd, |
|
|
int & |
rightSpd |
|
) |
| |
Overrides speed.
- Parameters
-
| front | front speed |
| back | back speed |
| left | left speed |
| right | right speed |
- Returns
- void function does not return anything
40 if (std::isless(frontSpd,0) || std::isless(backSpd,0) || std::isless(leftSpd,0) || std::isless(rightSpd,0))
41 throw std::domain_error(
"Negative arguments are invalid");
44 std::cout <<
"Overriding Forward speed to 0........!\n";
45 frontObstacle =
false;
49 std::cout <<
"Overriding Backward speed to 0.......!\n";
54 std::cout <<
"Overriding Left speed to 0...........!\n";
59 std::cout <<
"Overriding Right speed to 0..........!\n";
The documentation for this class was generated from the following files:


To configure the ALM application, the following steps are necessary:
- add users (we need at least one admin user)
- configure sources
- add articles (or seed a set of sample articles)
- start workers (start collecting data from external APIs)
- configure maintenance tasks (only in production system)
Adding Users
The ALM application supports the following user roles:
- API user - only API key
- staff - read-only access to admin area
- admin - full access to admin area
The ALM application supports the following forms of authentication:
- username/password (Login) for admin and staff users
- authentication with Mozilla Persona for all user roles
- authentication with CAS (currently PLOS only)
The first user created in the system automatically has an admin role, and this user can be created with any of the authentication methods listed above. From then on all user accounts are created with an API user role, and users have to create their own account using third-party authentication with Persona (or CAS). Admin users can change the user role after an account has been created, but can't create user accounts
Third-party authentication is configured in config/settings.yml
. To use Persona, make sure the folling setting exists: persona: true
(the default). No other configuration is necessary. Authentication via username/password is always enabled.
Users automatically obtain an API key, and they can sign up to the monthly report in CSV format. Admin users can sign up for additional reports (error report, status report, disabled source report).
Configuring Sources
Unless this has already been done during installation, sources have to be installed and activated through the web interface Sources -> Installation
:
All sources can be installed, but some sources require additional configuration settings such as API keys before they can be activated. The documentation for sources contains information about how to obtain API keys and other required source-specific settings.
The following addiotional configuration options are available via the web interface:
- whether the source is automatically queueing jobs and not running via cron job (default true)
- whether the results can be shared via the API (default true)
- number of max. workers for the job queue (default 1)
- job_batch_size: number of articles per job (default 200)
- staleness: update interval depending on article publication date (default daily the first 31 days, then 4 times a month up until one year, then monthly)
- rate-limiting (default 10,000)
- timeout (default 30 sec)
- maximum number of failed queries allowed before being disabled (default 200)
- maximum number of failed queries allowed in a time interval (default 24 hours)
- disable delay after too many failed queries (default 10 sec)
Through these setup options the behavior of sources can be fine-tuned, but the default settings should almost always work. The default rate-limiting settings should only be increased if your application has been whitelisted with that source.
Adding Articles
Articles can be added in one of several ways:
- admin dashboard (admin user)
- seeding of sample articles
- command line rake task
- API
Adding or changing articles via the admin dashboard is mainly for testing purposes, or to fix errors in the title or publication date of specific articles.
Seeding articles
A set of about 30 sample articles is loaded during installation when using Vagrant and seed_sample_articles
in node.json
is set to true
. They can also be seeded later via rake task:
bundle exec rake db:articles:seed
Command line rake task
We can use a rake command line task to automate the import of a large number of articles. The import file (e.g. IMPORT.TXT) is a text file with one article per line, and the required fields DOI, publication date and title separated by a space:
DOI Date(YYYY-MM-DD) Title
The date can also be incomplete, i.e. YYYY-MMM
or YYYY
. The rake taks loads all these articles at once, ignoring (but counting) invalid ones and those that already exist in the database:
bundle exec rake db:articles:load <IMPORT.TXT
In a production environment this rake task (like all other rake tasks used in production) has to be slightly modified to:
bundle exec rake db:articles:load <IMPORT.TXT RAILS_ENV=production
The rake task splits on white space for the first two elements, and then takes the rest of the line (title) as one element including any whitespace in the title.
Most users will automate the importing of articles via a cron job, and will integrate the rake task into a larger workflow.
API
Articles can also be added (and updated or deleted) via the v4 API. The v4 API uses basic authentication and is only available to admin and staff users. A sample curl API call to create a new article would look like this:
curl -X POST -H "Content-Type: application/json" -u USERNAME:PASSWORD -d '{"article":{"doi":"10.1371/journal.pone.0036790","published_on":"2012-05-15","title":"Test title"}}' http://HOST/api/v4/articles
The DOI, publication date and title are again all required fields, but you can also include other fields such as the Pubmed ID. See the API page for more information, e.g. how to update or delete articles.
Starting Workers
The ALM application talks to external data sources to collect metrics about a set of articles. Metrics are added by calling external APIs in the background, using the delayed_job queuing system. The results are stored in CouchDB. This can be done in one of two ways:
Ad-hoc workers
To collect metrics once for a set of articles, or for testing purposes the workers can be run ad-hoc using the foreman utility that is installed with the ALM application. To make sure foreman detects the correct environment you are running (development
or production
), make sure the file .env
in the root folder of your application has the correct information:
RAILS_ENV=development
You then have to decide what articles you want updated. This can be either a specific DOI, all articles, all articles for a list of specified sources, or all articles published in a specific time interval. Issue one of the following commands (and include RAILS_ENV=production
in production mode):
bundle exec rake queue:one[10.1371/journal.pone.0036790]
bundle exec rake queue:all
bundle exec rake queue:all[pubmed,mendeley]
bundle exec rake queue:all START_DATE=2013-02-01 END_DATE=2014-02-08
bundle exec rake queue:all[pubmed,mendeley] START_DATE=2013-02-01 END_DATE=2014-02-08
You can then start the workers with:
script/delayed_job -n 3 start
You might have to run this command with sudo
. -n
tells you the number of workers you want to run in parallel. To stop the workers:
script/delayed_job stop
Background workers
In a continously updating production system we want to run the workers in the background with the above command. You can monitor the status of your workers in the admin dashboard (/admin
).
When we have to update the metrics for an article (determined by the staleness interval), a job is added to the background queue for that source. A delayed_job worker will then process this job in the background. We need to run at least one delayed_job to do this.
List of background jobs that ALM uses
The default priority for jobs is 5. We have the following background jobs sorted by decreasing priority:
- Disabled source alert. Queue name is
mailer
, priority is 1. - Updating sources and status cache. Queue names are
{name of source}-cache
andstatus-cache
, priority is 1. - Article imports. Queue name is
article-import
, priority is 2. - Deleting CouchDB documents. A one-time maintenance task, queue name is
couchdb
, default priority is 4. - Updating sources. Queue name is name of the source, priority can be any integer greater than 0, default priority is 5.
- Email reports. Queue name is
mailer
, default priority is 6.
Configuring Maintenance Tasks
The ALM application uses a number of maintenance tasks in production mode - they are not necessary for a development instance.
Many of the maintenance taks are rake
tasks, and they are listed on a separate page. All rake tasks are issued from the application root folder. You want to prepend your rake command with bundle exec
and RAILS_ENV=production
should be appended to the rake command when running in production, e.g.
bundle exec rake db:articles:load <IMPORT.TXT RAILS_ENV=production
Cron jobs
The ALM application uses the Whenever gem to make it easy to generate cron jobs. The configuration is stored in config/schedule.rb
:
env :PATH, ENV['PATH']
set :environment, ENV['RAILS_ENV']
set :output, "log/cron.log"
# Schedule jobs
# Send report when workers are not running
# Create alerts by filtering API responses and mail them
# Delete resolved alerts
# Delete API request information, keeping the last 1,000 requests
# Delete API response information, keeping responses from the last 24 hours
# Generate a monthly report
every 60.minutes do
rake "queue:stale"
end
every 4.hours do
rake "workers:monitor"
end
every 1.day, at: "1:00 AM" do
rake "filter:all"
rake "mailer:error_report"
rake "mailer:stale_source_report"
rake "db:api_requests:delete"
rake "db:api_responses:delete"
rake "db:alerts:delete"
end
every :monday, at: "1:30 AM" do
rake "mailer:status_report"
end
# every 9th of the month at 2 AM
every '0 2 9 * *' do
rake "pmc:update"
end
# every 10th of the month at 5 AM
every '0 5 10 * *' do
rake "report:all_stats"
rake "mailer:article_statistics_report"
end
You can display this information in cron format by:
bundle exec whenever
To write this information to your crontab file, use
bundle exec whenever --update-crontab alm
The crontab is automatically updated when you run capistrano (see Installation).
Filters
Filters check all API responses of the last 24 hours for errors and potential anti-gaming activity, and they are typically run as cron job. They can be activated and configured (e.g. to set limits) individually in the admin panel:
These filters will generate alerts that are displayed in the admin panel in various places. More information is available on the Alerts page.
Reports
The ALM application generates a number of email reports:
The Article Statistics Report is available to all users, all other reports only to admin and staff users. Users can sign up for these reports in the account preferences.
The ALM application installs the Postfix mailer and the default settings should work in most cases. Mail can otherwise me configure in config/settings.yml
:
mail:
address: localhost
port: 25
domain: localhost
We need to process CouchDB data for some sources (Mendeley, Pmc, Counter) in the Article Statistics Report, please install the CouchDB design document for this report:
curl -X PUT -d @design_doc/reports.json 'http://localhost:5984/alm/_design/reports'
The reports are generated via the cron jobs mentioned above. Make sure you have correct write permissions for the Article Statistics Report, it is recommended to run the rake task at least once to test for this:
bundle exec rake report:all_stats RAILS_ENV=production
This rake task generates the monthly report file at /public/files/alm_report.zip
and this file is then available for download at /files/alm_report.zip
. Users who have signed up for this report will see a download link in their account preferences. Additional reports are stored as zip file in the /data
folder.


Name : {{clinician.fullName}}.
Specialization : {{clinician.specialization}}.
Timings : {{clinician.timings}}.


Before Change
@staticmethod
def _find_match(cand_vecs, label_vec):
return ((cand_vecs == label_vec).sum(1) == cand_vecs.size(1)).nonzero()[0]
def share(self):
Share model parameters.
shared = super().share()
After Change
@staticmethod
def _find_match(cand_vecs, label_vec):
matches = ((cand_vecs == label_vec).sum(1) == cand_vecs.size(1)).nonzero()
if len(matches) > 0:
return matches[0]
raise RuntimeError(
"At least one of your examples has a set of label candidates "
"that does not contain the label. To ignore this error "
"set `--ignore-bad-candidates True`."


{% comment "License" %} % Copyright (c) 2019 ISP RAS (http://www.ispras.ru) % Ivannikov Institute for System Programming of the Russian Academy of Sciences % % Licensed under the Apache License, Version 2.0 (the "License"); % you may not use this file except in compliance with the License. % You may obtain a copy of the License at % % http://www.apache.org/licenses/LICENSE-2.0 % % Unless required by applicable law or agreed to in writing, software % distributed under the License is distributed on an "AS IS" BASIS, % WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. % See the License for the specific language governing permissions and % limitations under the License. {% endcomment %} {% load i18n %}
{% if tags.type == 'safe' %}green{% elif tags.type == 'unsafe' %}orange{% endif %} {% trans 'No results found' %}


public interface GraphOptionsOrBuilder
extends org.nd4j.shade.protobuf.MessageOrBuilder
| Modifier and Type | Method and Description |
|---|---|
long |
getBuildCostModel()
The number of steps to run before returning a cost model detailing
the memory usage and performance of each node of the graph. 0 means
no cost model.
|
long |
getBuildCostModelAfter()
The number of steps to skip before collecting statistics for the
cost model.
|
boolean |
getEnableBfloat16Sendrecv()
If true, transfer float values between processes as bfloat16.
|
boolean |
getEnableRecvScheduling()
If true, use control flow to schedule the activation of Recv nodes.
|
boolean |
getInferShapes()
Annotate each Node with Op output shape data, to the extent it can
be statically inferred.
|
OptimizerOptions |
getOptimizerOptions()
Options controlling how graph is optimized.
|
OptimizerOptionsOrBuilder |
getOptimizerOptionsOrBuilder()
Options controlling how graph is optimized.
|
boolean |
getPlacePrunedGraph()
Only place the subgraphs that are run, rather than the entire graph.
|
RewriterConfig |
getRewriteOptions()
Options that control the type and amount of graph rewriting.
|
RewriterConfigOrBuilder |
getRewriteOptionsOrBuilder()
Options that control the type and amount of graph rewriting.
|
int |
getTimelineStep()
If > 0, record a timeline every this many steps.
|
boolean |
hasOptimizerOptions()
Options controlling how graph is optimized.
|
boolean |
hasRewriteOptions()
Options that control the type and amount of graph rewriting.
|
findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof
boolean getEnableRecvScheduling()
If true, use control flow to schedule the activation of Recv nodes. (Currently ignored.)
bool enable_recv_scheduling = 2;
boolean hasOptimizerOptions()
Options controlling how graph is optimized.
.tensorflow.OptimizerOptions optimizer_options = 3;
OptimizerOptions getOptimizerOptions()
Options controlling how graph is optimized.
.tensorflow.OptimizerOptions optimizer_options = 3;
OptimizerOptionsOrBuilder getOptimizerOptionsOrBuilder()
Options controlling how graph is optimized.
.tensorflow.OptimizerOptions optimizer_options = 3;
long getBuildCostModel()
The number of steps to run before returning a cost model detailing the memory usage and performance of each node of the graph. 0 means no cost model.
int64 build_cost_model = 4;
long getBuildCostModelAfter()
The number of steps to skip before collecting statistics for the cost model.
int64 build_cost_model_after = 9;
boolean getInferShapes()
Annotate each Node with Op output shape data, to the extent it can be statically inferred.
bool infer_shapes = 5;
boolean getPlacePrunedGraph()
Only place the subgraphs that are run, rather than the entire graph. This is useful for interactive graph building, where one might produce graphs that cannot be placed during the debugging process. In particular, it allows the client to continue work in a session after adding a node to a graph whose placement constraints are unsatisfiable.
bool place_pruned_graph = 6;
boolean getEnableBfloat16Sendrecv()
If true, transfer float values between processes as bfloat16.
bool enable_bfloat16_sendrecv = 7;
int getTimelineStep()
If > 0, record a timeline every this many steps. EXPERIMENTAL: This currently has no effect in MasterSession.
int32 timeline_step = 8;
boolean hasRewriteOptions()
Options that control the type and amount of graph rewriting. Not currently configurable via the public Python API (i.e. there is no API stability guarantee if you import RewriterConfig explicitly).
.tensorflow.RewriterConfig rewrite_options = 10;
RewriterConfig getRewriteOptions()
Options that control the type and amount of graph rewriting. Not currently configurable via the public Python API (i.e. there is no API stability guarantee if you import RewriterConfig explicitly).
.tensorflow.RewriterConfig rewrite_options = 10;
RewriterConfigOrBuilder getRewriteOptionsOrBuilder()
Options that control the type and amount of graph rewriting. Not currently configurable via the public Python API (i.e. there is no API stability guarantee if you import RewriterConfig explicitly).
.tensorflow.RewriterConfig rewrite_options = 10;
Copyright © 2020. All rights reserved.


- Name: <%= name %>
- Created by: <%= creator %>
- Created on: <%= created %>
- Duration: <%= duration %> Day(s) - Start: <%= from %> → End: <%= to %>
- Groups: <%= groups.length %>
- Groups Composition: <% _.each(composition, function(criteria){ %> <%= criteria %> <% if (criteria !== _.last(composition)){ %> <%= ", " %> <% } %> <% }); %>
Delete


Human,
There is a difference between knowing the path and walking the path.
Example: mouseover
English


Before Change
np.array_equal(classes, [0]) or
np.array_equal(classes, [-1]) or
np.array_equal(classes, [1]))):
raise ValueError("Data is not binary and pos_label is not specified")
elif pos_label is None:
pos_label = 1.
// make y_true a boolean vector
After Change
np.array_equal(classes, [0]) or
np.array_equal(classes, [-1]) or
np.array_equal(classes, [1])))):
classes_repr = ", ".join(repr(c) for c in classes)
raise ValueError("y_true takes value in {{{classes_repr}}} and "
"pos_label is not specified: either make y_true "
"take integer value in {{0, 1}} or {{-1, 1}} or "


Toggle navigation
AACCUP DOCUMENT MANAGEMENT AND EVALUATION SYSTEM FOR BUKSU
About
Logout
Dashboard
Registered Users
Course
Registered Users
×
Register New User
Name
Lastname
Username
Password
Usertype
Choose Usertype
Administrator
Program Coordinator
Accreditor
Register
Cancel
Firstname
Lastname
Username
Usertype
Program
"; echo "
".$usersdata['name']."
"; echo "
".$usersdata['lastname']."
"; echo "
".$usersdata['user']."
"; //echo "
".$usersdata['utype']."
"; $sql2="SELECT * FROM usertype WHERE utype_id='".$usersdata['utype']."'"; $result2 = mysqli_query($db, $sql2); $udtype = mysqli_fetch_array($result2); echo "
".$udtype['usertype']."
"; $sql3="SELECT * FROM program WHERE program_id='".$usersdata['program_id']."'"; $result3 = mysqli_query($db, $sql3); $progtype = mysqli_fetch_array($result3); echo "
".$progtype['program_name']."
"; echo "
"; echo ""; } } ?>
Are you sure you want to delete this user?
Yes
No


+++ title = "The Weary Traveler, Tulum" slug = "the-weary-traveler-tulum" date = 2007-03-05T13:00:00+10:00 tags = ["accommodation"] locations = ["mexico/tulum"] draft = false summary = """
This hostel has the best communal set-up, and hence the best communal atmosphere, of anywhere I've stayed so far. The central courtyard, which dominates the place, houses a long row of tables, a few hammocks, a deluxe (and used-by-all) kitchen, and a bar. I met some great people here, and felt that I could really unwind as well.
""" +++This hostel has the best communal set-up, and hence the best communal atmosphere, of anywhere I've stayed so far. The central courtyard, which dominates the place, houses a long row of tables, a few hammocks, a deluxe (and used-by-all) kitchen, and a bar. I met some great people here, and felt that I could really unwind as well.
Rooms: average, no complaints.
People: really nice and friendly, if a bit hippie-inclined.
Staff: friendly, English-speaking, and good-looking.
Location: main street of Tulum.
Food: significantly above average — free eggs, pancakes, sausage, etc. for breakfast.
Internet: free, but never available (numerous good cafés nearby).


Home
Composer
Editor
☰
Text Editor
How to Create Text Brushes
Text brushes allow you to add tiles over the top of your compositions. Each time you tap on the screen in the composer the next word will be displayed. Hold down to control the duration of the display, when you release the text will fade away.
Text
Tapping the text will let you change the current item.
Font List
Choose which font you wish to use for the current text item.
Settings
This will let you adjust various settings for how your text is displayed.
Text Size
Use the slider to adjust the display size of the selected text.
Opacity
Lower the opacity with the slider if you wish to reveal your scene thru the text.
Color
Tapping this icon will let you pick the fill color for the current text item.
Add/Remove
Use the add and remove buttons to create a list of text items you wish to use. When adding new text, the settings of the current item will be cloned.


PennApps Mentorship wants to teach you how the hack. The program offers tech talks for new hackers, office hours by experienced mentors, and a special mentee prize for the best hack to come out of the mentorship program, all while letting participants experience the full PennApps hackathon in all its swag- and free food-filled glory.
Tech talks include:
- Basics of Git
- Intro to Android
- Intro to web apps
- Design, HTML/CSS
- Bootstrap/Foundation
- Intro to Node.js
- Implementing an API in your app
- Making a good demo


{% include 'includes/$head.html' %}
{% include 'includes/$bandeau_deco.html' %}
{% include 'includes/$header_nav.html' %} {% include 'includes/$menu.html' %}
Identification requise
Connexion
Mot de passe oublié?
{% include 'includes/$encadres.html' %}
{% include 'includes/$pied_deco.html' %}


Borderless banking service TransferWise gains Google Pay support
by Damien WildeTransferWise, the borderless banking service that allows you to create a local account in over 60 countries, has now officially added support for Google Pay.
The service is one of the easiest ways to lower worldwide money transfer and transaction fees by enabling you to open a bank account in a local currency, therefore lowering your direct costs. By adding Google Pay support, you’ll now be able to use your phone to make payments from all of your TransferWise accounts for even easier global travel.
Announced in an official blog post, the brand-new addition works as you would expect, with transactions appearing within your TransferWise activity list. You’ll also still get your regular notifications each time you make or receive a payment using Google Pay.
This also means that you can finally use Google Pay to make cross-border payments online and in person without having to grab your debit card. Unlike using the card alone, you also get the added bonus of Face and Fingerprint locking and unlocking for even more secure wireless payments.
It is worth noting that making TransferWise payments via Google Pay is only available to customers living in Belgium, Croatia, the Czech Republic, Denmark, Finland, France, Germany, Ireland, Italy, Norway, Poland, Slovakia, Spain, Sweden, Switzerland, the UK, and the US. The company hasn’t confirmed whether this will be extended or not.
For those of you already using TransferWise — myself included — it’s as easy as taking a snap of your fancy neon-green debit card to get started making mobile payments on your Android phone.
More on Google Pay:
- Google Pay support comes to the combo-card system Curve
- Google Pay gains support for Cubic transit cards, including San Francisco’s Clipper cards
- Google Pay ‘Spot’ platform enables new tools for businesses and job seekers in India
FTC: We use income earning auto affiliate links. More.


Build a Standalone App with Electron and Oracle JET
Oracle JET has great scaffolding and support for building native apps for mobile platforms such as iOS, Android or Windows 10, all from a single JET codebase. And of course you can build browser-based single-page apps that run on the desktop. But what about a native standalone desktop app?
Electron is a framework for building cross-platform native apps using web stack technologies. It’s the tool that the Atom editor is created with, and it underpins many other hip apps these days. Electron uses Node.js and the Chromium engine to run web framework code inside of native OS windows, without needing to launch a browser.
Could we use Electron to package up an Oracle JET app and make it a cross-platform desktop executable?
Learning about Electron
The best place to start is from the horse’s mouth, and Zeke Sikelianos of GitHub gave a good overview of Electron that was recorded at their recent Universe 2016 conference:
There are also a bunch of tutorials and references out on the web on how to build an electron app. We’ll be leaning on the simple electron-quick-start to wrap a Oracle JET project inside of Electron.
Putting JET in an Electron blanket
Start with a working JET app. We’ll use the generator to scaffold a plain template with just a header and footer so we feel at home:
yo oraclejet electronJet --template=basic
I added one of the cookbook visualizations to the code for my basic template. With a grunt serve
I’ve got a simple Oracle JET app:
You can follow along by cloning this repository, checking out the jetwebapp
tag, and running npm start
to automatically install all the npm and bower components:
git clone https://github.com/pthaden/electronJet.git
cd electronJet
git checkout jetwebapp
npm start
Now we have a working JET project with its own package.json
. Let’s tweak things to add Electron into the mix. Back at the command line, install the electron npm package as a dependency:
npm install electron --save-dev
Electron is a node.js app and expects an entry in the package.json
file for the startup script entry point. Edit the file to include a "main":
entry pointing at a to-be-created main.js file:
package.json
{
"name": "electronJet",
"version": "1.0.0",
"description": "A sample Oracle JavaScript Extension Toolkit (JET) web app wrapped in Electron",
"author": {
"name": "Paul Thaden"
},
"main": "main.js",
"scripts": { ...
Next we need some node.js code to spin up an electron window and stick our JET code inside of it. Create a file in the root of the project called main.js
(not to be confused with JET’s main.js
in the src/js
or web/js
folders).
main.js
const {app, BrowserWindow} = require('electron')
// Keep a global reference of the window object, if you don't, the window will
// be closed automatically when the JavaScript object is garbage collected.
let win
app.on('ready', () => {
// Create the browser window.
win = new BrowserWindow({
width: 800,
height: 600,
// turn off node integration in the Electron window to prevent conflicts with require.js
// see http://electron.atom.io/docs/faq/#i-can-not-use-jqueryrequirejsmeteorangularjs-in-electron
webPreferences: { nodeIntegration: false }
})
// and load the index.html of the built JET app.
win.loadURL('file://' + __dirname + '/web/index.html')
})
This is a bare-bones Electron app, but it will get the job done. Note the modification to the BrowserWindow
’s webPreferences
setting: I disabled nodeIntegration
in the Electron renderer process because of conflicts between the require()
function in Node and the Require.js loader in JET. You’ll also see that I’m pointing to the /web/index.html
in the JET project, which assumes you’ve executed grunt build
at least once.
To test it out, kick back to the command line at the root of the project and start Electron:
electron .
If all works well, you’ll have a native app window with your JET content running inside:
If you want to make it all build automatically, modify the npm start
in the scripts
section of the package.json file to call Electron instead of serving via Grunt:
package.json
{
"name": "electronJet",
"version": "1.0.0",
"description": "A sample Oracle JavaScript Extension Toolkit (JET) web app wrapped in Electron",
"author": {
"name": "Paul Thaden"
},
"main": "main.js",
"scripts": {
"postinstall": "bower install && grunt bowercopy",
"prestart": "npm install",
"start": "grunt build && electron ."
},
"devDependencies": { ...
Does it really make an executable?
I used electron-packager to create Mac, Win32 and Linux packaged executable bundles out of the electronJET app. I modified the main.js
code a bit to better match the electron-quick-start code and to support the MacOS window closing and quitting conventions.
Here’s the Windows version running native on that OS:
It’s all up on the GitHub repo, and you can download zips for each platform:
- electronJet-darwin-x64.zip for MacOS
- electronJet-win32-x64.zip for Windows
- electronJet-linux-ia32.zip for Linux


Execute an SPSS DATE command taking the starting date from the data.
STATS DATA DATE
SPSSDATE=variable*
DATESTRUCTURE = periodicities*
WEEKPERIOD=periodicity
BY=increment
/HELP
* Required
** Default
/HELP displays this text and does nothing else.
STATS DATA DATE SPSSDATE = datevar DATESTRUCTURE=YM.
constructs the starting date from variable datevar and assigns a period of 12.
SPSSDATE specifies an SPSS date-format variable.
DATESTRUCTURE specifies the date/time structure as a string of letters drawn from Y Q M W H I S with no spaces inbetween. The abbreviations are the same as for the DATE command except that MI (minute) is I, but CYCLE and OBS are not supported.
WEEKPERIOD applies only to W (week). The other periods are assumed to have their natural periodicity. W defaults to 7 but might usefully be set to 5. However, the starting week is calculated from the first date value based on a 7-day week where week 1 begins on January 1.
BY specifies the increment between observations and defaults to 1. With DATESTRUCTURE=YM, for example, BY = 2 would mean that the data are monthly but only observed every other month.
© Copyright IBM Corp. 1989, 2014