text:
Annotated Republic of China Laws/Organization Act of the Directorate-General of Personnel Administration, Executive Yuan

 * Article 1
 * The Executive Yuan shall establish a Directorate-General of personnel Administration (hereinafter referred to as the Directorate-General) under its purview to formulate policies and carry out and develop personnel administration.
 * The functions of the Directorate-General that pertain to the civil service examination and qualification reviews shall fall under the supervision of the Examination Yuan.

 * Article 2
 * The Directorate-General shall be charged with:
 * (1)conducting research and making proposals pertaining to personnel administration legal affairs and general planning of personnel administration for the Executive Yuan’s subordinate agencies;
 * (2)research, planning and implementation of personnel office establishment; management, training, and development of personnel officers; and management of human resource information systems in the Executive Yuan’s subordinate agencies and local government agencies;
 * (3)research and promotion of the organizational functions of the Executive Yuan’s subordinate agencies and the system of non- departmental public bodies;
 * (4)research, planning, supervision, and evaluation of government headcount management, and drafting and explanation of relevant regulations;
 * (5)planning and implementation of examination placement, appointment and removal, remuneration, and promotion of civil servants in the Executive Yuan’s subordinate agencies and local government agencies;and review of appointment and removal of chairpersons and managers at state-owned enterprises;
 * (6)planning, execution, and evaluation of work-related training, education,and development for civil servants at the Executive Yuan’s subordinate agencies and local government agencies;
 * (7)conducting research and making proposals on regulations for service and attendance; planning, reviewing, and drafting of office hours; planning and execution of regulations related to performance evaluation, reward, and punishment for civil servants at the Executive Yuan’s subordinate agencies and local government agencies;
 * (8)planning, reviewing, and drafting of civil service remuneration schemes;
 * (9)review, research, and proposals on retirement and compensation benefits; planning and execution of insurance, severance, and welfare payments to civil servants working at the Executive Yuan’s subordinate agencies and local government agencies; and (10)other affairs pertaining to the policy planning, execution, and development of personnel administration.

 * Article 3
 * The Directorate-General shall have one minister, specially appointed; and two deputy ministers, one of whom shall be a political appointee of equivalent ranking to Senior 14th grade and the other a civil servant ranked Senior 14th grade.

 * Article 4
 * The Directorate-General shall have one chief secretary, ranked Senior 12th grade.

 * Article 5
 * The official ranks, grades, and headcounts of personnel at the Directorate-General shall be regulated by a separate Personnel Establishment Table.

 * Article 6
 * This Act shall come into force on the date prescribed by the Executive Yuan.


text:
Annotated Republic of China Laws/Law on the Exclusive Economic Zone and the Continental Shelf of the Republic of China

 * Article 1
 * This law is enacted to preserve and exercise the rights in the exclusive economic zone and on the continental shelf of the Republic of China.
 * Matters not covered by this law shall be governed by the provisions of other related laws.

 * Article 2
 * The exclusive economic zone of the Republic of China denotes the sea area contiguous to the outer limits of the territorial sea and to a distance measuring outwardly 200 nautical miles from the baseline of the territorial sea.
 * The exclusive economic zone prescribed in the preceding paragraph comprises the water body, the seabed and the subsoil.
 * The continental shelf of the Republic of China is the submarine area that extends beyond its territorial sea through the natural prolongation of its land territory to the outer edge of the continental margin.
 * The submarine area prescribed in the preceding paragraph comprises the seabed and subsoil.

 * Article 3
 * The outer limits of the exclusive economic zone and the continental shelf of the Republic of China shall be decided by the Executive Yuan and may be promulgated in parts.

 * Article 4
 * In the event that the exclusive economic zone or the continental shelf of the Republic of China overlaps with the adjacent or opposite countries, the Republic of China may negotiate, on the principle of equality, a delimitation line with those of the adjacent or opposite countries.
 * Prior to agreements mentioned in the preceding paragraph, the Republic of China and the adjacent or opposite countries, in a spirit of understanding and co-operation, may reach a modus vivendi.
 * Such a modus vivendi as prescribed in the preceding paragraph shall be without prejudice to the final delimitation.

 * Article 5
 * The Republic of China shall, in its exclusive economic zone or on its continental shelf, enjoy and exercise the following rights:

 * 1) Sovereign rights for the purpose of exploring, exploiting, conserving, and managing the resources, living or non-living, of the waters superjacent to the seabed and of the seabed and its subsoil;
 * 2) Jurisdiction over the construction, use, modification, or dismantlement of artificial islands, installations or structures;
 * 3) Jurisdiction over marine scientific research;
 * 4) Jurisdiction over preservation of marine environment; and
 * 5) Other rights in accordance with international law.
 * The Republic of China shall enjoy and exercise sovereign rights of utilizing the energy stemming from the water, currents and winds or other activities.
 * The Republic of China shall enjoy and exercise jurisdiction over laying, maintaining, or modifying submarine cables or pipelines.

 * Article 6
 * For the undertaking of exploration, exploitation, conservation, or management of living or non-living resources in the exclusive economic zone or on the continental shelf of the Republic of China, an application for permissions shall be made in accordance with related laws and regulations of the Republic of China.

 * Article 7
 * For utilizing energy from the water, currents and winds or other activities in the exclusive economic zone of the Republic of China, a permission from the Government of the Republic of China shall be required. The related permission regulations shall be decided by the Executive Yuan.

 * Article 8
 * For the undertaking of construction, use, modification, or dismantlement of artificial islands, installations or structures in the exclusive economic zone or on the continental shelf of the Republic of China, a permission from the Government of the Republic of China shall be required. The related permission regulations shall be decided by the Executive Yuan.
 * Laws and regulations of the Republic of China shall apply to artificial islands, installations or structures prescribed in the preceding paragraph.
 * A safety zone shall be established around artificial islands, installations or structures prescribed in paragraph 1 where appropriate measures shall be taken to ensure the safety both of navigation and of the artificial islands, installations or structures.
 * The width of the safety zones prescribed in the preceding paragraph shall be in accordance with general international standards or as recommended by the related international organizations.

 * Article 9
 * For the undertaking of marine scientific research in the exclusive economic zone or on the continental shelf of the Republic of China, a permission from the Government of the Republic of China shall be required. Such research will be sjubject to the Government of the Republic of China's supervision. The Government of the Republic of China, when necessary, may withdraw permission or may suspend or cease marine scientific research activities in progress.
 * The undertaking of marine scientific research in the exclusive economic zone or on the continental shelf of the Republic of China shall comply with the following regulations:

 * 1) Not to interfere with the Republic of China's exercise of rights in its exclusive economic zone or on its continental shelf;
 * 2) To ensure the right of the Government of the Republic of China to designate its representatives for participation;
 * 3) To provide progress reports at all times, as well as preliminary conclusions and final conclusions;
 * 4) To furnish copied data, figures, or samples, complete and without detriment to their scientific value, and various assessment reports;
 * 5) To ensure not to prejudice the security and benefits of the Republic of China in using such research data;
 * 6) To inform the Government of the Republic of China immediately of any major change in the research project;
 * 7) Unless otherwise agreed, not to investigate marine resources;
 * 8) Not to harm the marine environment;
 * 9) Unless otherwise agreed, to dismantle research installations and equipment once the research is completed; and
 * 10) To comply with provisions of related laws and international agreements.
 * The regulations prescribed in paragraph 1 shall be decided by the Executive Yuan.

 * Article 10
 * Any activity concerning dumping, discharging or disposing of waste or other substances in the exclusive economic zone or on the continental shelf of the Republic of China shall comply with laws and regulations of the Republic of China.

 * Article 11
 * For any vessel navigating in the exclusive economic zone of the Republic of China which commits a discharge violation causing marine environmental pollution, the Republic of China may request that vessel to give information regarding its identity, its port of registry, its last and its next port of call and other relevant information required to establish whether a violation has occurred.
 * In case the suspected vessel prescribed in the preceding paragraph refuses to give information, or the information supplied by the vessel is manifestly at variance with the evident factual situation, or the vessel does not carry valid certificates and records, or the circumstances of the case justify such inspection, the Government of the Republic of China may undertake physical inspection of the vessel and, provided that the evidence so warrants, indict the vessel through due process.
 * For any inspected or indicted vessel as prescribed in the preceding paragraph, whenever appropriate procedures have been taken in accordance with international agreements, whereby compliance with requirements for any bond or other appropriate financial surety has been assured, that vessel shall be allowed to proceed.

 * Article 12
 * In order to meet special circumstances, the Republic of China, in explicitly defined areas of its exclusive economic zone, may adopt special mandatory measures for the prevention of pollution resulting from vessels, either discharge, navigation, or other practices of vessels.

 * Article 13
 * Unless otherwise provided in other laws and regulations, any activity conducted in the exclusive economic zone or on the continental shelf of the Republic of China shall not damage natural resources or harm natural ecology.
 * Whoever willfully or negligently damages or harms the natural resources or ecology of the exclusive economic zone or the continental shelf of the Republic of China shall be charged with their employer with joint responsibility for the compensation for the damage.

 * Article 14
 * The Government of the Republic of China reserves the right to conserve and manage fish stocks straddling both within and beyond its exclusive economic zone. Foreign fishing vessels conducting fishing of such stocks shall give due regard to the conservation and management measures of the Republic of China of these stocks.
 * The conservation and management measures of such fish stocks prescribed in the preceding paragraph shall be enacted and promulgated by the Executive Yuan.

 * Article 15
 * For delineating the course for the laying, maintaining, or modifying any submarine cables or pipelines on the continental shelf of the Republic of China, a permission of the Government of the Republic of China is required. The permission regulations shall be decided by the Executive Yuan.
 * The Government of the Republic of China may withhold such permission as prescribed in the preceding paragraph on the grounds of exploring, exploiting, managing, conserving the non-living or sedentary resources over its continental shelf, or preventing, reducing, controlling the pollution from such pipelines.

 * Article 16
 * Where the authorities of national defense, police, customs or other authorized agencies of the Republic of China consider that a person or an object, which is in its exclusive economic zone or on its continental shelf, is engaged in any activity violating laws and regulations of the Republic of China, such authorities may engage in hot pursuit, boarding, and inspection. When necessary, the aforementioned authorities may expel or arrest the suspected person, or detain the vessels, aircraft, equipment, or other articles belonging to the suspected person, and institute legal proceedings.

 * Article 17
 * Whoever dumps, discharges or disposes of waste or other substances in the exclusive economic zone or on the continental shelf without complying with laws and regulations of the Republic of China shall be punished with imprisonment not exceeding ten years, or detention in lieu thereof, or in addition thereto, a fine of not exceeding one hundred million New Taiwan Dollars.

 * Article 18
 * Whoever willfully damages or harms the natural resources or ecology of the exclusive economic zone or the continental shelf of the Republic of China shall be punished with imprisonment not exceeding five years or detention in lieu thereof, or in addition thereto, a fine of not exceeding fifty million New Taiwan Dollars.

 * Article 19
 * Whoever undertakes construction, use, modification, or the dismantling of artificial islands, installations or structures in the exclusive economic zone or on the continental shelf of the Republic of China without obtaining a permission from the Government of the Republic of China shall be punished with a fine of between ten million and fifty million New Taiwan Dollars. The court may confiscate the constructed artificial islands, installations or structures or order the said person to restore the environment to the original condition.
 * Whoever violates terms or objects of the granted permission shall be punished with a fine of between five million and twenty million New Taiwan Dollars and shall be set a time limit to remedy. Without improvement until then, the permission shall be cancelled and the artificial islands, installations or structures may be dismantled.

 * Article 20
 * Whoever conducts any one of the following activities without obtaining a permission from the Government of the Republic of China shall be punished with a fine of between one million and five million New Taiwan Dollars and the vessels, equipment, and catches belonging to the said person may be confiscated:

 * 1) Conducting exploration, exploitation, management, or conservation of living or non-living resources in the exclusive economic zone of the Republic of China;
 * 2) Conducting exploration, exploitation, management, or conservation of non-living resources or sedentary living resources on the continental shelf of the Republic of China.
 * Whoever violates the terms or objects of any permission granted shall be punished with a fine of between two hundred thousand and two million New Taiwan Dollars.　Products (catch or haul) may be confiscated.

 * Article 21
 * Whoever produces energy from the water, currents and winds or other activities in the exclusive economic zone or on the continental shelf of the Republic of China without obtaining a permission from the Government of the Republic of China shall be punished with a fine of between two hundred thousand and one million New Taiwan Dollars and the related equipment may be confiscated.

 * Article 22
 * Whoever undertakes marine scientific research in the exclusive economic zone or on the continental shelf of the Republic of China without obtaining a permission from the Government of the Republic of China shall be punished with a fine of between five hundred thousand and two million New Taiwan Dollars and the related exploring instruments and data may be confiscated.
 * The same penalty shall apply to whoever violates terms or objects of the granted permission or to whoever violates the provisions prescribed in paragraph 2 of article 9.

 * Article 23
 * Whoever undertakes the laying, maintaining, or modifying of submarine cables and pipelines on the continental shelf of the Republic of China without obtaining a permission on the delineation of the course shall be punished with a fine of between twenty million and one hundred million New Taiwan Dollars and the said person may be prohibited from using such cables and pipelines or be ordered to dismantle them.

 * Article 24
 * Whoever conducts the following activities in the exclusive economic zone or on the continental shelf of the Republic of China shall be punished in accordance with the Criminal Code of the Republic of China:

 * 1) Threats or violence against a public official who is engaged in the lawful discharge of his duties;
 * 2) Organizing an open assembly at which an offense specified in the preceding sub-paragraph occurs;
 * 3) Activities conducted to abandon, damage, hide, or render useless the letters, books, articles taken in its custody by a public official or entrusted by such a public official of the ROC to a third person;
 * 4) Activities conducted to damage, remove, stain the seal or notice affixed by a public official of the ROC;
 * 5) Public insults to a public official of the ROC during or with respect to the legal discharge of his duties; and
 * 6) Threats or violence with intent to compel a public official of the ROC to perform an act relating to his public duties or with intent to obstruct the lawful discharge of such public duties.
 * Article 25
 * Fines imposed in accordance with this law not paid within the designated time limit shall be transferred to the court for enforcement mandatory.

 * Article 26
 * This law shall enter into force on the date of promulgation.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
User:Deltaquadboi/Collections/Persian

 * Persian
 * Persian/Introduction
 * Persian/Lesson 1
 * Persian/Lesson 2
 * Persian/Lesson 3
 * Persian/Lesson 4
 * Persian/Lesson 5
 * Persian/Lesson 6
 * Persian/Lesson 7
 * Persian/Lesson 8
 * Persian/Lesson 9
 * Persian/Lesson 10
 * Persian/Lesson 11
 * Persian/Lesson 12
 * Persian/Lesson 13
 * Persian/Lesson 14
 * Persian/Lesson 15
 * Persian/Lesson 16
 * Persian/Lesson 17
 * Persian/Lesson 18
 * Persian/Persian Computing
 * Persian/Persian Handwriting
 * Persian/Phrasebook
 * Persian/Glossary

title: User:Deltaquadboi/Collections/Persian


text:
Wikibooks:Featured books/Nominations/Removal/Write Yourself a Scheme in 48 Hours

Write Yourself a Scheme in 48 Hours
This is outdated, not being worked on, and has been incorporated into the far better and already also featured Haskell Wikibook. It is not good to distract from the better book and clutter the bulk by keeping this in the featured list. —Preceding unsigned comment added by Backfromquadrangle (discuss • contribs) 06:04, 20 September 2015

 * I lean towards support due to outdatedness. It should be noted that Write Yourself a Scheme remains somewhat popular in the Haskell community, and while it largely covers the same ground as Haskell it does so in a very different, even opposite, manner. I believe updating this book would be a worthy endeavour (unfortunately I don't see myself doing much towards that in the near future, as my hands are full with Haskell already).--Duplode (discuss • contribs) 07:03, 23 September 2015 (UTC)

 * I'm vague on why this would be considered outdated. It's not obvious to me that featured-ness would necessarily come with an expiration date, so to speak, though I acknowledge there are some sorts of information that would, and am willing to keep an open mind on the point.  I'd be interested in feedback on this from either of the above commenters, though it looks like one of them might not be around now. --Pi zero (discuss • contribs) 14:32, 30 June 2019 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/Non-Programmer's Tutorial for Python 3

Non-Programmer's Tutorial for Python 3
I'm nominating this because this book is ridiculously hard to find compared to the other Python books yet is probably the best. I am not the creator, I however used this to learn python. It taught me more than my teachers did in the first six months of class. --Liberivore (discuss • contribs) 15:42, 11 July 2014 (UTC)
 * I agree. The book is also small, but still have what you need to get started.
 * I used this to learn Python a few months back, and found it to be very well written. Liam987  (t) 01:31, 13 March 2015 (UTC)
 * --Atcovi (talk ↔ contribs) 11:11, 23 April 2015 (UTC)
 * 86 pages seems to me too short for the domain. Furthermore, the Python 3 Google books are more like 300 pages long. JackPotte (discuss • contribs) 16:57, 14 April 2018 (UTC)
 * But on the other hand, we've already got the featured book Non-Programmer's Tutorial for Python 2.6 which is 88 pages long. JackPotte (discuss • contribs) 05:46, 16 April 2018 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/Data Mining Algorithms In R

Data Mining Algorithms In R
Really nice and crisp book. It has the following chapters

Dimensionality Reduction- Principal Component Analysis,Singular Value Decomposition,Feature Selection

Frequent Pattern Mining- The Eclat Algorithm,arulesNBMiner,The Apriori Algorithm,The FP-Growth Algorithm

Sequence Mining- SPADE,DEGSeq

Clustering- K-Means, Hybrid Hierarchical Clustering, Expectation Maximization (EM),Dissimilarity Matrix Calculation,Hierarchical Clustering,Bayesian Hierarchical Clustering,Density-Based Clustering, K-Cores, Fuzzy Clustering - Fuzzy C-means,RockCluster,Biclust, Partitioning Around Medoids (PAM),CLUES,Self-Organizing Maps (SOM), Proximus,CLARA

Classification- SVM,penalizedSVM,kNN, Outliers,Decision Trees,Naïve Bayes,adaboost,JRip

R Packages- RWeka,gausspred,optimsimplex,CCMtools,FactoMineR,nnet
 * A print version would be easier if the table of content wasn't split into six. JackPotte (discuss • contribs) 11:42, 31 July 2016 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/Coaching Youth Middle Distance Runners

Coaching Youth Middle Distance Runners
For this work, I set out to create a review of available and current literature on the subject, hence the large number of references (~200). If people wanted to read more, I wanted to make sure it was available vis-à-vis references and further information. Although presented in a somewhat different style than is typical on this site, it should be familiar to many in the field, and is consistently applied throughout each chapter.

I'm sure that there are some tweaks can be made here and there, and there's always the possibility of major expansion, but I believe this fits within the context of WB:WIW and it meets the guidelines listed in Good books, hence the reason I'm nominating this for FB status. Your thoughts and constructive criticism are greatly appreciated. – Runfellow (discuss • contribs) 15:46, 16 September 2013 (UTC)
 * I don't know why I'm the first to voice my opinion here but anyway, I like it. I think there could be more images but otherwise everything seems in order.--ЗAНИA [[Image:Flag_of_Estonia.svg|15px]]talk 19:34, 12 May 2014 (UTC)
 * --Atcovi (talk ↔ contribs) 11:10, 23 April 2015 (UTC)
 * Very well written and organised, although a little short. Liam987  talk 14:15, 23 April 2015 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/Sensory Systems

Sensory Systems
While this book was started by myself, it now contains chapters written by 18 other authors. It gives a comprehensive overview over sensory systems. Thereby not only the physiological aspects are covered, but also ways of simulating these systems with computers, and - for humans - ways of technically substituting for deficient sensory end organs (e.g. cochlear implants). Recently it has been expanded to include more information about sensory systmes in non-primates (spiders, fish, insects, ...). --Thomas.haslwanter (discuss • contribs) 16:13, 20 July 2014 (UTC)
 * I've gone through the book myself to finally put an end to this blankness here, and some problems I've found:

 * The navigation contain "underscores", which doesn't seem professional for a featured book.
 * Not a lot of pictures, may bore readers.
 * Comma problems (Run-on sentences):
 * "In general, bitterness is very interesting because a large number of bitter compounds are known to be toxic , so the bitter taste is considered to provide an important protective function".
 * "The Gustatory System, or sense of taste , allows us to perceive different flavors from substances like food, drinks, medicine etc. Molecules that we taste , or tastants , are sensed by cells in our mouth, which send sendS information to the brain."
 * ([])
 * "The free receptors, or type 4 joint receptors , are nociceptors"
 * (https://en.wikibooks.org/wiki/Sensory_Systems/Somatosensory_System#Joint_receptors)
 * Navigation for "Sensory Systems/Other Animals" looks unfit for a featured book: "Birds,Fish..." - That's something you'd usually see in developing books.
 * "In a dipole (the arguably most elementary magnet), the northern and southern poles are the sources of the field"
 * (https://en.wikibooks.org/wiki/Sensory_Systems/Other_Animals#The_geomagnetic_field)
 * HUGE paragraphs, blocks of texts.

 * Though very little things for such a huge book, I don't expect a featured book to have this many problems in it. I may have high standards, but hey, an opinion is an opinion! --Atcovi (Talk - Contribs) 12:56, 7 February 2017 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/RAC Attack - Oracle Cluster Database at Home

RAC Attack - Oracle Cluster Database at Home
This is a hands-on lab curriculum for learning about Oracle RAC cluster databases. I am the primary author. Just finished the print/pdf versions this week; finally feel that it's ready to suggest for featuring.

The book differs from most other wikibooks in that it heavily draws on "fair use" images. We discussed this a few years ago when I was first considering if wikibooks would be a good platform for the book. Unfortunately, it's not really possible to do a tutorial on this subject without drawing on fair use images. Not sure how this would impact the decision about whether it should be featured. ArdentPerf (discuss • contribs) 20:43, 5 April 2013 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/Climatology

Climatology
I nominate this book as this book as important book for UG/PG students of Geography and also one of the best geography books in Wikibooks. सीमा1 (discuss • contribs) 07:51, 7 May 2020 (UTC)
 * I don't have the capacity to actually go thru the book but at the very least, it shouldn't say that it's 25% complete if it's going to be featured. —Justin ( koavf ) ❤T☮C☺M☯ 20:52, 7 May 2020 (UTC)

its completed total syllabus of climatology in geography.climatology is a name of one paper in geography, and this is complete book for climatology.सीमा1 (discuss • contribs) 04:19, 8 May 2020 (UTC)

 * its complete 100% of syllabus of climatology.and this is also a featured book for B.A.(hons.) Geography and other general competition . सीमा1 (discuss • contribs) 07:33, 24 May 2020 (UTC)


text:
Wikibooks:Featured books/Nominations/Addition/English grammar

English grammar
English Grammar — Preceding unsigned comment added by 2409:4061:2E0C:5CA1:64CF:F476:2D93:A5E4 (talk • contribs)

 * This appears to me to be currently too incomplete for featured status. --Pi zero (discuss • contribs) 15:26, 18 July 2020 (UTC)


text: Wikibooks:Reading room/Bulletin Board/2013


text: Wikibooks:Reading room/Bulletin Board/2014


text: Wikibooks:Reading room/Bulletin Board/2015


text: Wikibooks:Reading room/Bulletin Board/2016


text: Wikibooks:Reading room/Bulletin Board/2017


text: Wikibooks:Reading room/Bulletin Board/2018


text:
Talk:Salute, Jonathan!/Capitul 1

Word frequency list
Generated from: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=146ec6cf4fd4139c0dbc8cb9ffee1518

 * bon | 8
 * cité | 43
 * di | 1
 * e | 11
 * es | 28
 * esque | 13
 * grand | 9
 * il | 42
 * in | 21
 * inteligent | 2
 * it | 3
 * jurnale | 24
 * li | 76
 * man | 1
 * mann | 41
 * may | 2
 * munich | 7
 * ne | 15
 * no | 8
 * nu | 1
 * pensa | 23
 * pri | 14
 * que | 4
 * quo | 5
 * salute | 1
 * scri | 22
 * sta | 17
 * tren | 9
 * u | 6
 * un | 42
 * unesim | 1
 * vide | 15
 * yes | 4

title: Talk:Salute, Jonathan!/Capitul 1


text:
Understanding Air Safety in the Jet Age/Air Florida Flight 90

On a freezing night in Washington, 74 people would die due to a simple error by the pilots. On January 13, 1982 Air Florida Flight 90 was scheduled to depart from Washington National Airport (now Ronald Reagan Washington National Airport) to Fort Lauderdale–Hollywood International Airport with an intermediate stopover at Tampa International Airport. Less than two minutes after the Boeing 737-222 left the runway it crashed into the 14th Street Bridge over the Potomac River, killing four motorists on the bridge, before falling into the river to drown most of the survivors. What went wrong? Like all air accidents, multiple things contributed to the outcome, but the root cause was forgetting it was cold outside - despite the snow.

Striking the bridge, which carries Interstate 395 between Washington, D.C. and Arlington County, Virginia, it hit seven occupied vehicles and destroyed nearly 100 ft of guard rail before plunging through the ice into the Potomac River. The aircraft was carrying 74 passengers and five crew members. Only four passengers and one crew member (a flight attendant) were rescued from the crash and survived. Another passenger, Arland D. Williams, Jr., assisted in the rescue of the survivors but drowned before he could be rescued. Four motorists on the bridge were killed. The survivors were rescued from the icy river by civilians and professionals. President Ronald Reagan commended these acts during his State of the Union speech a few days later.

The National Transportation Safety Board (NTSB) determined that the cause of the accident was pilot error. The pilots failed to switch on the engines' internal ice protection systems, used reverse thrust in a snowstorm prior to takeoff, tried to use the jet exhaust of a plane in front of them to melt their ice, and failed to abort the takeoff even after detecting a power problem while taxiing and having ice and snow buildup on the wings.

Aircraft
The aircraft involved, a Boeing 737-222, registered as N62AF, was manufactured in 1969 and previously flown by United Airlines under the registration N9050U. It was sold to Air Florida in 1980. The aircraft was powered by two Pratt & Whitney JT8D-9A turbofan engines and had recorded over 27,000 hours before the crash.

Cockpit crew
The pilot, Captain Larry M. Wheaton, aged 34, was hired by Air Florida in October 1978 as a first officer. He upgraded to captain in August 1980. At the time of the accident, he had about 8,300 total flight hours, with 2,322 hours of commercial jet experience, all logged at Air Florida. He had logged 1,752 hours on the Boeing 737, the accident-aircraft type, 1,100 of those hours as captain.

Wheaton was described by fellow pilots as a quiet person, with good operational skills and knowledge, who had operated well in high-workload flying situations. His leadership style was described as similar to those of other pilots. On May 8, 1980, though,  he was suspended after failing a Boeing 737 company line check and was found to be unsatisfactory in these areas: adherence to regulations, checklist usage, flight procedures such as departures and cruise control, and approaches and landings. He resumed his duties after passing a retest on August 27, 1980. On April 24, 1981, he received an unsatisfactory grade on a company recurrent proficiency check when he showed deficiencies in memory items, knowledge of aircraft systems, and aircraft limitations. Three days later, he satisfactorily passed a proficiency recheck.

The first officer, Roger A. Pettit, aged 31, was hired by Air Florida on October 3, 1980, as a first officer on the Boeing 737. At the time of the accident, he had around 3,353 flight hours, 992 with Air Florida, all on the 737. From October 1977 to October 1980, he had been a fighter pilot in the US Air Force, accumulating 669 hours as a flight examiner,  instructor pilot, and  ground instructor in an F-15 unit.

The first officer was described by personal friends and pilots as a witty, bright, outgoing individual with an excellent command of physical and mental skills in aircraft piloting. Those who had flown with him during stressful flight operations said that during those times, he remained the same witty, sharp individual, "who knew his limitations." Several persons said that he was the type of pilot who would not hesitate to speak up if he knew something specific was wrong with flight operations.

Alternating the role of "primary pilot" between the pilot in command (PIC), the captain, and second in command (SIC), the first officer, is customary in commercial airline operations, with pilots swapping roles after each leg. One pilot is designated the pilot flying (PF) and the other as pilot not flying (PNF); however, the PIC retains the ultimate authority for all aircraft operations and safety. The first officer was on the controls as the PF during the Air Florida Flight 90 accident.

Weather conditions
On Wednesday, January 13, 1982, Washington National Airport (DCA) was closed by a heavy snowstorm that produced 6.5 in (16.5 cm) of snow. It reopened at noon under marginal conditions as the snowfall began to slacken.

That afternoon, the plane was to return to Fort Lauderdale–Hollywood International Airport in Dania, Florida, with an intermediate stop at Tampa International Airport. The scheduled departure time was delayed about 1 hour and 45 minutes because of a backlog of arrivals and departures caused by the temporary closing of Washington National Airport. As the plane was readied for departure from DCA, a moderate snowfall continued and the air temperature was well below freezing.

Improper de-icing procedures
The Boeing 737 was de-iced with a mixture of heated water and monopropylene glycol by American Airlines, under a ground-service agreement with Air Florida. That agreement specified that covers for the pitot tubes, static ports, and engine inlets had to be used, but the American Airlines employees did not comply with those rules. One de-icing vehicle was used by two different operators, who chose widely different mixture percentages to de-ice the left and right sides of the aircraft. Subsequent testing of the de-icing truck showed that "the mixture dispensed differed substantially from the mixture selected" (18% actual vs. 30% selected). The inaccurate mixture was the result of the replacement of the standard nozzle, "...which is specially modified and calibrated, with a non-modified, commercially available nozzle." The operator had no means to determine if the proportioning valves were operating properly because no "mix monitor" was installed on the nozzle.

Flight
The plane had trouble leaving the gate when the ground-services tow motor could not get traction on the ice. For roughly 30 to 90 seconds, the crew attempted to back away from the gate using the reverse thrust of the engines (a powerback), which proved futile. Boeing operations bulletins had warned against using reverse thrust in those kinds of conditions.

Eventually, a tug ground unit properly equipped with snow chains was used to push the aircraft back from the gate. After leaving the gate, the aircraft waited in a taxi line with many other aircraft for 49 minutes before reaching the takeoff runway. The pilot apparently decided not to return to the gate for reapplication of deicing, fearing that the flight's departure would be even further delayed. More snow and ice accumulated on the wings during that period, and the crew was aware of that fact when they decided to make the takeoff. Heavy snow was falling during their takeoff roll at 3:59 pm EST.

Though the outside temperature was well below freezing and it was snowing, the crew did not activate the engine anti-ice system. This system uses heat from the engines to prevent sensors from freezing, ensuring accurate readings.

While running through the takeoff checklist, the following conversation snippet took place (CAM-1 is the captain, CAM-2 is the first officer):

{{quote|CAM-2 Pitot heat?

CAM-1 On.

CAM-2 Engine anti-ice?

CAM-1 Off.

Despite the icing condition with weather temperature of about 24 °F (-4 °C), the crew failed to activate the engine anti-ice systems, which caused the engine pressure ratio (EPR) thrust indicators to provide false readings. The correct engine power setting for the temperature and airport altitude of Washington National at the time was 2.04 EPR, but it was later determined from analysis of the engine noise recorded on the cockpit voice recorder that the actual power output corresponded with an engine pressure ratio of only 1.70.

Neither pilot had much experience flying in snowy, cold weather. The captain had made only eight takeoffs or landings in snowy conditions on the 737, and the first officer had flown in snow only twice.

Adding to the plane's troubles was the pilots' decision to maneuver closely behind a DC-9 that was taxiing just ahead of them prior to takeoff, due to their mistaken belief that the warmth from the DC-9's engines would melt the snow and ice that had accumulated on Flight 90's wings. This action, which went specifically against flight-manual recommendations for an icing situation, actually contributed to icing on the 737. The exhaust gases from the other aircraft melted the snow on the wings, but during takeoff, instead of falling off the plane, this slush mixture froze on the wings' leading edges and the engine inlet nose cone.

As the takeoff roll began, the first officer noted several times to the captain that the instrument panel readings he was seeing did not seem to reflect reality (he was referring to the fact that the plane did not appear to have developed as much power as it needed for takeoff, despite the instruments indicating otherwise). The captain dismissed these concerns and let the takeoff proceed. Investigators determined that plenty of time and space on the runway remained for the captain to have aborted the takeoff, and criticized his refusal to listen to his first officer, who was correct that the instrument panel readings were wrong. The pilot was told not to delay because another aircraft was 2.5 miles (4 km) out on final approach to the same runway. The following is a transcript of Flight 90's cockpit voice recorder during the plane's acceleration down the runway.

{{quote|15:59:32 CAM-1 Okay, your throttles.

15:59:35 [SOUND OF ENGINE SPOOLUP]

15:59:49 CAM-1 Holler if you need the wipers.

15:59:51 CAM-1 It's spooled. Really cold here, real cold.

15:59:58 CAM-2 God, look at that thing. That don't seem right, does it? Ah, that's not right.

16:00:09 CAM-1 Yes it is, there's eighty.

16:00:10 CAM-2 Naw, I don't think that's right. Ah, maybe it is.

16:00:21 CAM-1 Hundred and twenty.

16:00:23 CAM-2 I don't know.

16:00:31 CAM-1 V{{sub|1}}. Easy, V{{sub|2}}.|Transcript|Air Florida Flight 90 Cockpit Voice Recorder

As the plane became briefly airborne, the voice recorder picked up the following from the cockpit, with the sound of the stick-shaker (a device that warns that the plane is in danger of stalling) in the background:

{{quote|16:00:39 [SOUND OF STICKSHAKER STARTS AND CONTINUES UNTIL IMPACT]

16:00:41 TWR Palm 90 contact departure control.

16:00:45 CAM-1 Forward, forward, easy. We only want five hundred.

16:00:48 CAM-1 Come on forward....forward, just barely climb.

16:00:59 CAM-1 Stalling, we're falling!

16:01:00 CAM-2 Larry, we're going down, Larry....

16:01:01 CAM-1 I know!

16:01:01 [SOUND OF IMPACT]|Transcript|Air Florida Flight 90 Cockpit Voice Recorder }}

The aircraft traveled almost half a mile (800 m) farther down the runway than is customary before liftoff was accomplished. Survivors of the crash indicated the trip over the runway was extremely rough, with survivor Joe Stiley – a businessman and private pilot – saying that he believed that they would not get airborne and would "fall off the end of the runway". When the plane became airborne, Stiley told his co-worker (and survivor) Nikki Felch to assume the crash position, with some nearby passengers following their example.

Although the 737 did manage to become airborne, it attained a maximum altitude of just 350 ft before it began losing altitude. Recorders later indicated that the aircraft was airborne for just 30 seconds. At 4:01 pm EST, it crashed into the 14th Street Bridge across the Potomac River, less than a mile from the end of the runway. The plane hit six cars and a truck on the bridge, and tore away the bridge's rail and wall. The aircraft then plunged into the freezing Potomac River. It fell between two of the three spans of the bridge, between the I-395 northbound span (the Rochambeau Bridge) and the HOV north- and southbound spans, about 200 ft offshore. All but the tail section quickly became submerged.

Of the people on board the aircraft:

 * Four of the crew members (including both pilots) died.
 * One crew member was seriously injured.
 * Seventy of the 74 passengers died.
 * Nineteen occupants were believed to have survived the impact, but their injuries prevented them from escaping.

Of the motorists on the bridge involved:

 * Four sustained fatal injuries
 * One sustained serious injuries
 * Three sustained minor injuries

Clinging to the tail section of the broken airliner in the ice-choked Potomac River were flight attendant Kelly Duncan and four passengers: Patricia "Nikki" Felch, Joe Stiley, Arland D. Williams Jr. (strapped and tangled in his seat), and Priscilla Tirado. Duncan inflated the only flotation device they could find, and passed it to the severely injured Felch. Passenger Bert Hamilton, who was floating in the water nearby, was the first to be pulled from the water.

Crash response
Many federal offices in downtown Washington had closed early that day in response to quickly developing blizzard conditions. Thus, a massive backup of traffic existed on almost all of the city's roads, making reaching the crash site by ambulances very difficult. The Coast Guard's harbour tugboat Capstan (WYTL 65601) and its crew were based nearby; their duties include ice breaking and responding to water rescues. The Capstan was considerably farther downriver on another search-and-rescue mission. Emergency ground response was greatly hampered by ice-covered roads and gridlocked traffic, ambulances dispatched at 4:07 pm took 20 minutes to reach the scene of the crash. Ambulances attempting to reach the scene were even driven down the sidewalk in front of the White House. Rescuers who reached the site were unable to assist survivors in the water because they did not have adequate equipment to reach them. Below-freezing waters and heavy ice made swimming out to them impossible. Multiple attempts to throw a makeshift lifeline (made out of belts and any other things available that could be tied together) out to the survivors proved ineffective. The rescue attempts by emergency officials and witnesses were recorded and broadcast live by area news reporters, and as the accident occurred in the nation's capital, large numbers of media personnel were on hand to provide quick and extensive coverage.

Roger Olian, a sheet-metal foreman at St. Elizabeth's Hospital, a Washington psychiatric hospital, was on his way home across the 14th Street Bridge in his truck when he heard a man yelling that an aircraft was in the water. He was the first to jump into the water to attempt to reach the survivors. At the same time, several military personnel from the Pentagon—Steve Raynes, Aldo De La Cruz, and Steve Bell—ran down to the water's edge to help Olian.

"He only traveled a few yards and came back, ice sticking to his body. We asked him to not try again, but he insisted. Someone grabbed some short rope and battery cables and he went out again, maybe only going 30 feet. We pulled him back. Someone had backed up their jeep and we picked him up and put him in there. All anyone could do was tell the survivors was to hold on not to give up hope. There were a few pieces of the plane on shore that were smoldering and you could hear the screams of the survivors. More people arrived near the shore from the bridge, but nobody could do anything. The ice was broken up and there was no way to walk out there. It was so eerie, an entire plane vanished except for a tail section, the survivors, and a few pieces of plane debris. The smell of jet fuel was everywhere, and you could smell it on your clothes. The snow on the banks was easily two feet high and your legs and feet would fall deep into it every time you moved from the water."

At this point, flight controllers were aware only that the plane had disappeared from radar and did not respond to radio calls, but had no idea of either what had happened or the plane's location.

At approximately 4:20 pm EST, Eagle 1, a United States Park Police Bell 206L-1 Long Ranger helicopter (registry number N22PP), based at the "Eagles Nest" at Anacostia Park in Washington and manned by pilot Donald W. Usher and paramedic Melvin E. Windsor, arrived and began attempting to airlift the survivors to shore. At great risk to themselves, the crew worked close to the water's surface, at one time coming so close to the ice-clogged river that the helicopter's skids dipped beneath the surface.

The helicopter crew lowered a line to survivors to tow them to shore. First to receive the line was Bert Hamilton, who was treading water about 10 ft (3 m) from the plane's floating tail. The pilot pulled him across the ice to shore, while avoiding the sides of the bridge. By then, some fire/rescue personnel had arrived to join the military personnel and civilians who pulled Hamilton (and the next/last three survivors) from the water's edge up to waiting ambulances. The helicopter returned to the aircraft's tail, and this time Arland D. Williams Jr. (sometimes referred to as "the sixth passenger") caught the line. Williams, not able to unstrap himself from the wreckage, passed the line to flight attendant Kelly Duncan, who was towed to shore. On its third trip back to the wreckage, the helicopter lowered two lifelines, fearing that the remaining survivors had only a few minutes before succumbing to hypothermia. Williams, still strapped into the wreckage, passed one line to Joe Stiley, who was holding on to a panic-stricken and blinded (from jet fuel) Priscilla Tirado, who had lost her husband and baby. Stiley's co-worker, Nikki Felch, took the second line. As the helicopter pulled the three through the water and blocks of ice toward shore, both Tirado and Felch lost their grips and fell back into the water.

Priscilla Tirado was too weak to grab the line when the helicopter returned to her. A watching bystander, Congressional Budget Office assistant Lenny Skutnik, stripped off his coat and boots, and in short sleeves, dove into the icy water and swam out to successfully pull her to shore. The helicopter then proceeded to where Felch had fallen, and paramedic Gene Windsor stepped out onto the helicopter skid and grabbed her by the clothing to lift her onto the skid with him, bringing her to shore. When the helicopter crew returned for Williams, the wreckage he was strapped into had rolled slightly, submerging him; according to the coroner Williams was the only passenger to die by drowning. His body and those of the other occupants were later recovered.

While the weather had caused an early start to Washington's rush-hour traffic, frustrating the response time of emergency crews, the early rush hour also meant that trains on the Washington Metro were full when, just 30 minutes after Flight 90 crashed, the Metro suffered its first fatal crash at Federal Triangle station. This meant that Washington's nearest airport, one of its main bridges in or out of the city, and one of its busiest subway lines were all closed simultaneously, paralyzing much of the metropolitan area.

NTSB investigation and conclusion
The 737 had broken into several large pieces upon impact - the nose and cockpit section, the cabin up to the wing attachment point, the cabin from behind the wings to the rear airstairs, and the empennage. Although actual impact speeds were low and well within survivability limits, the structural breakup of the fuselage and exposure to freezing water nonetheless proved fatal for all persons aboard the plane except those seated in the tail section. The National Transportation Safety Board concluded that the accident was not survivable. Determining the position of the rudder, slats, elevators, and ailerons was not possible due to impact damage and the majority of the flight control system having been destroyed.

The National Transportation Safety Board determined that the probable cause of the crash included the flight crew's failure to enforce a sterile cockpit during the final preflight checklist procedure. The engines' anti-ice heaters were not engaged during the ground operation and takeoff. The decision to take off with snow/ice on the airfoil surfaces of the aircraft, and the captain's failure to reject the takeoff during the early stage when his attention was called to anomalous engine instrument readings also were erroneous.

The NTSB further stated:

""Contributing to the accident were the prolonged ground delay between deicing and the receipt of ATC takeoff clearance during which the aircraft was exposed to continual precipitation, the known inherent pitch up characteristics of the B-737 aircraft when the leading edge is contaminated with even small amounts of snow or ice, and the limited experience of the flight crew in jet transport winter operations."


text:
Talk:Salute, Jonathan!/Capitul 2

Word frequency list
Generated from: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=b2ebc48022131b76e00e2da9041c3ee7

 * a | 2
 * ama | 8
 * amar | 1
 * amat | 1
 * bon | 21
 * cité | 55
 * cités | 3
 * de | 11
 * deman | 4
 * di | 3
 * die | 2
 * duesim | 3
 * e | 35
 * es | 62
 * esque | 18
 * esser | 3
 * esset | 6
 * grand | 12
 * hodíe | 5
 * il | 67
 * in | 57
 * inteligent | 5
 * it | 8
 * jonathan | 5
 * jurnale | 30
 * jurnales | 1
 * li | 112
 * ma | 9
 * man | 1
 * mann | 49
 * mannes | 1
 * may | 4
 * mult | 5
 * munich | 36
 * ne | 22
 * no | 9
 * nov | 3
 * nu | 12
 * old | 8
 * pensa | 47
 * pensat | 3
 * pri | 21
 * que | 5
 * quo | 5
 * salute | 2
 * scri | 30
 * scrir | 2
 * scrit | 2
 * sta | 17
 * star | 1
 * stat | 1
 * tren | 32
 * trenes | 6
 * u | 6
 * un | 63
 * unesim | 1
 * va | 7
 * viage | 4
 * viagea | 3
 * viages | 2
 * vide | 15
 * vienna | 18
 * yer | 10
 * yes | 7
 * yo | 30

title: Talk:Salute, Jonathan!/Capitul 2


text:
Salute, Jonathan!/Capitul 2 - with notes

Contenete - Capitul 1 - Capitul 2 - Capitul 3

Duesim may (= 2 may)
Nu li mann es in li tren. Il ne es in Munich; il es in un tren. Il viagea. Il pensa: "Nu yo viagea de Munich a Vienna. It es un bon viage. Yo ama viages."

Il pensa pri Munich. Il pensa: “Nu yo es in li tren, ma yer yo esset in Munich. E nu yo scri un jurnale in li tren, ma yer yo scrit un jurnale in Munich. E nu yo pensa in li tren, ma yer yo pensat in Munich. Yer yo pensat pri Munich in Munich, e nu yo pensa pri Vienna in li tren. Nu yo es in li tren, ne in Vienna. Ma yo pensa e scri pri Vienna.”

Esque li mann nu pensa in Munich? No, il nu ne pensa in Munich. Il pensa in li tren. Yer il pensat in Munich. Il di: “Salute, tren!”

Li mann es in li tren, e il viagea a un cité. Li cité ne es Munich; Munich es li cité de yer. Li cité es Vienna; Vienna es li cité de hodíe.

Li mann pensa pri Munich e Vienna. Il pensa: “Munich esset li cité de yer, e Munich esset bon. Nu it es hodíe, e yo es in un tren; li tren es bon. Esque Vienna va esser bon?”

Li mann pensa pri Munich: Munich esset li cité de yer. Il pensa in li tren: il es in li tren hodíe. E il pensa pri Vienna: Vienna va esser li cité de deman.

E il pensa: “Munich esset grand. Li tren es grand. Esque Vienna va esser grand?”

E il pensa: “In Munich yo scrit in un jurnale. In li tren yo scri in un jurnale. Esque in Vienna yo va scrir in un jurnale? Yes, deman in Vienna yo va scrir in un jurnale. Yo ama jurnales.” Li mann pensa mult (il pensa mult = il pensa e pensa e pensa), e il scri mult. Yes, il es un inteligent mann. Inteligent mannes scri mult, e pensa mult. Il es Jonathan; Jonathan es un inteligent mann.

Il scri: “Yo es Jonathan. Yo es in un tren. Yer yo stat in Munich; deman yo va star in Vienna.”

Il pensa, e scri: “Li tren...it es bon, ma old. It ne es nov; it es old. Esque in Munich li trenes es old? Yes, li trenes de Munich es old. Ma li trenes de Munich es bon, e yo ama li trenes de Munich. Yer yo amat li tren in Munich, e hodíe yo ama li tren nu, e deman yo va amar li tren in Vienna. Yo ama trenes!”

Jonathan scri: "Munich es un bon cité e un old cité, e Vienna es un bon cité e un old cité. Munich e Vienna ne es nov, ma es bon. Munich e Vienna es old, ma bon cités. Li cités ne es nov, ma bon. Yo ama cités!"

Jonathan pensa, que li duesim die de viage es bon. Il di: “Hodíe esset un bon duesim die de viage. Yo ama viages!”

yer, hodíe, deman

 * yer = unesim may (05.01)
 * hodíe = duesim may (05.02)
 * deman = triesim may (05.03)

-t

 * scri: hodíe yo scri, yer yo scrit
 * pensa: hodíe yo pensa, yer yo pensat
 * vide: hodíe yo vide, yer yo videt

va -r

 * scri: hodíe yo scri, deman yo va scrir
 * pensa: hodíe yo pensa, deman yo va pensar
 * vide: hodíe yo vide, deman yo va vider

esser

 * verbes in i: scri, scrit, va scrir
 * verbes in e: vide, videt, va vider
 * verbes in a: pensa, pensat, va pensar
 * verbe esser: es, esset, va esser

de, a

 * De Munich a Vienna:
 * Munich → Vienna
 * De Vienna a Munich:
 * Munich ← Vienna

Vocabularium

 * ama
 * deman (yer → hodíe → deman)
 * hodíe (yer → hodíe → deman)
 * mult
 * nov
 * nu
 * old
 * va
 * viage
 * viagea
 * yer ↔ (yer → hodíe → deman)

Di:

 * g = g
 * grand: grand
 * grammatica: grammatica
 * gi, ge: ji, je
 * viage: viaje
 * inteligent: intelijent


text:
Trainz/refs/KUIDs Geneologies-- groundtextures

Background, Introductory history
Trainz, almost from its inception, used a data structure introduced with Trainz 1.0 SP3, the to allow Content to be superseded by a different, presumably newer better version of an asset. By the time Trainz UTC was coming together, the KUID and KUID2 succession system was invented, leaving both methods as legal alternatives.

Issues of connectivity
There are several problems with the use of obsolete-tables — and most of them emanating from Auran/N3V's inhouse content creation team's over use of the tables to maintain kuid identifiers with negative author indexes. This dubious strategy has long outlived its utility, and should have been retired with the introduction of the kuid2 capabilities, which always point both forward and back in time to related generations of changed asset releases and by inference, to any later iteration. The base kuid identifier is applicable to the same asset, so a parent-child relationship is always explicit, and unlike obsolete-table enclosing kuids, which have their own base kuid with no specific relationship to the older kuid, assets sharing the same base kuid identifier are predictable--the newer generation is of a higher suffix, not a different (and unknowable!) random kuid.

On its face, this may seem like small beer, but in the multiplication of the practices by numbers of content creator over twenty years, in absolute terms, the numbers of disconnected next generation kuids is simply staggering. The great majority of missing assets in any sizable downloaded route will suffer from this problem with about 50% of the unknown kuids being precisely because until both assets are in the local Content Manager data base, there is no way to know that relationship exists between two different base kuid identifiers. The problem has also been exacerbated by N3V's nearly consistent practice of upping the iteration with each major retail release (and Major TBV plateau)—again (per differential binary comparison) with no particularly significant change to base component files except the identity within the new kuid and the revised obsolete-table. As illustrative of the problem, consider the succession of an gravel-less 'bridge track' (key word "bridgetrack" in fact in dependent bridge kinds!) used as a linked resource asset in dozens, possibly hundreds of bridges (Some content creators create their own, others default to the N3V built-ins, swelling the count and size of the problem!): Which one came first, and in what order did they replace the previous? When an asset only knows what is in its kuid-table and obsolete-table, and the two don't both show in CM, there is an information gap which the GUI's can't overcome... they don't know what on-hand kuid to substitute for the older number in the.
 * This list was generated by TANE :by requesting all versions of the 'obsoleted'  1 track wood damp—which was the built-in replacement for the previous TS10 iterations, and the situation further gets confused because the TANE ' TANE 1Trk Wood' is actually MERGING two lines of different tracks, one wet wood and the other consistent with the general wood track with the several built-in gravel ballasts.

To be complete, this problem may be mitigated with changes to the data communication with the DLS and post-TS2012 Content Managers. There appears to be extra information available, probably in a 'side list of linked kuids' that is available to TANE and TRS19 which does not get reported to or used by the design of the older Content Managers. This is evident in the reported content of the above list. The list returned by TS12 for the very same 'show asset versions' query is quite different: 1 track wood damp, 1 track wood damp, (Obsolete) So we can conclude  superseded TS09/TS10 era's , and nothing more. Certainly not that its grandparent was a particular specific ubiquitous kuid dating back to TBV 1.3 and Trainz 1.0—which is what that newly downloaded older route or bridge may list as a dependency. Bam, information gap, even to the software. Which segues into the other related issue. Generally superseding assets were assigned the very same (TBV), likely to expand international visibility and utility to a new language group added to the standard releases' asset queues.

Identification
Specifically the most common Auran 'Author Identifier' kuid-parts, spanning twenty years of growth are: {id#: -1, -3, -10, -12, -14, -16, -18, -25, -26, -101, -105 and lately many +523}; emphasis added to the ones with the most codes.  Ironically, testing and comparisons have shown the most of the successor kuids in the Auran genealogies are graphically and pragmatically identical assets, with the iterative changes mainly being focused on adding new internationalization data-names and descriptions (See: and ) when a release was translated into other languages.
 * Kuid (base kuid) format:
 * Kuid2 format:

Independent 3rd Party CCs
Other independent creators, '3rd Party Content' originators, causing widespread problems using obsolete tables rather than a generational kuid are a handful of the oldest group of content creators, including two of the most prolific steam engine originating modelers, maestros paulhobbs and bdaneal, who specialize in British and North American steam locomotives and rolling stock, respectively. Unfortunately, generally locating a specific missing kuid is problematic, and many are shrouded as unindexed parts of kits. But which kit should be looked for and downloaded? Others, especially a few key dependencies by Mr. Paul Hobbs were only released as part of a payware route of yesteryear—which aren't available now, and have been superceded in the routes replacement by a payware 'alleged upgrade', leaving the poor sod simply desiring to use a derivative reskinned asset with a missing dependency. In this case, perhaps one that is incurable.

Decentralized base kuids, and source locations
In the case of the later type, there seems to be an overreliance on private 3rd party websites to distribute full data sets. Many of their locomotives in particular utilize a low poly, often invisible mesh as an anchor mesh providing orientation and the origin, axes of a coordinate system to provide anchor points to which other meshes attach. This sort of mesh can grow organically as parts are added, or have a particular anchor point moved in 3D spatial co-ordinates. In the case of such gorgeous steam locomotives as both are known for, there is a definite mechanical advantage to the method: when the separately configured bits of something as bulging, bulky, and possessing so many moving parts, each with their own motion to animate, working a data set individually enables them to debug each part as they progress each subsystem over the months it takes to complete such a model. The same degree of complexity rarely applies to most Auran/N3V sourced models, which in the greatest cases generally have a much more mundane and uncomplicated mission.

Table of groundtexture geneology
 TS09_53_Concrete  TS09_53_Concrete  TS09_54_Asphalt  TS09_54_Asphalt  TS09_55_Asphalt  TS09_55_Asphalt  TS09_56_Asphalt  TS09_56_Asphalt  TS09_57_Asphalt <kuid2:523:1467:1> TS09_57_Asphalt <kuid2:407941:1048:3> SeasonalGrass4 <kuid2:407941:1048:2> SeasonalGrass4 <kuid2:407941:1048:1> SeasonalGrass4 <kuid:407941:1048> SeasonalGrass4 <kuid2:407941:100040:1> SeasonalGrass8 <kuid:407941:100040> SeasonalGrass8 <kuid2:407941:100040:2> SeasonalGrass8 <kuid:407941:1044> SeasonalGravel2 <kuid2:407941:1044:1> SeasonalGravel2 <kuid2:407941:1044:2> SeasonalGravel2 <kuid2:407941:1044:3> SeasonalGravel2 <kuid2:407941:1043:2> SeasonalGravel4 <kuid2:407941:1043:1> SeasonalGravel4 <kuid:407941:1043> SeasonalGravel4 <kuid:-25:1291> hayfield


text:
Salute, Jonathan!/Capitul 3 - with notes

Contenete - Capitul 2 - Capitul 3 - Capitul 4

Duesim may (= 2 may)
Jonathan sta in Vienna: li cité de Vienna. Jonathan pensa que Vienna es bon, e que Vienna es bell. Jonathan ne pensa que Vienna es desbell; il pensa que Vienna es bell. Il di: “Vienna es un bell cité! Yo va scrir pri it!” E il scri in li jurnale pri Vienna. In li jurnale il scri: “Mi triesim die es tre bon! In li duesim die yo stat in Munich. Ma nu yo sta in Vienna: Vienna ne es Munich. Munich e Vienna es du cités; Munich ne es Vienna e Vienna ne es Munich. Yo sta in Vienna e li cité es tre bell. Yo ama Vienna; li cité ne es desbell. Quam bell es Vienna! Ma yo have un problema.”

Quo? Jonathan have un problema? Quel problema? Nu il ne vide li jurnale; il vide li cité e pensa. Il pensa mult pri li problema.

Li problema de Jonathan es que il ama Vienna, ma il ne have témpor.

Il pensa: “Hmm. Nu it es sett (7) horas. Ye deci (10) horas li tren departe. Deci (10) horas minus sett (7) horas es tri (3) hores. Tri hores ne es mult témpor por un bell cité! Yo ne have témpor. Haver témpor es bon, ma yo ne have it! Scrir un jurnale es bon, ma yo ne have témpor por scrir it! Quo far in Vienna?”

Il pensa: "Yo ne have mult témpor. Quo far - scrir un jurnale, o manjar, o vider li cité? Quo yo va far?"

Il pensa plu, e di: “Yo have un bon idé! Un moment...yo pensa. Mi tren departe a deci (10) horas. Esque hay un tren plu tard, a deciun (11) horas, o decidu (12), decitri (13), deciquar (14) o deciquin (15) horas?"

Il vide…yes! Hay un tren quel departe a deciquin horas. Nu Jonathan es felici.

Jonathan di: “Deciquin (15) minus sett (7) es ott (8). Nu yo have ott hores de témpor! Quo yo va far?”

Il di: “Yo save! Yo va manjar un bifstec. E yo va trincar un bir. Un moment...no, yo va trincar du bires, o tri bires. Bon idé!”

Nu Jonathan trinca un bir in Vienna, e manja un bifstec. Il es felici. Il di: “Quam yo es felici! Yo ama li cité de Vienna. Quam yo ama viages!”

Verbes

 * Li ínfinitive de un verbe es -r. Pensa = pensar, scri = scrir, manja = manjar, have = haver.
 * Jonathan pensa: "quo manjar?" e il manja un bifstec.
 * Jonathan pensa: "haver témpor es bon!" Il ne have témpor.

de

 * Jonathan pensa: mi tren va departer. = Li tren de Jonathan va departer.
 * Jonathan scri in un jurnale. Il scri it; it es li jurnale de Jonathan.

hay

 * hay = es
 * Esque hay un mann in li tren? Yes, hay un mann; it es Jonathan.
 * Esque hay un jurnale in li bifstec? No, ne hay un jurnale in li bifstec.

plu tard

 * It es 10 horas. Plu tard, it va esser 11 horas.
 * Jonathan esset in Munich. Plu tard, il esset in Vienna.
 * Jonathan pensat: "Yo va manjar." Plu tard, il manjat.

ye
Ye = a
 * Ye deci horas = a deci horas

1) quel?

 * Jonathan ama un tren. Quel tren Jonathan ama? Jonathan ama li old tren.
 * Jonathan vide un cité. Quel cité Jonathan vide? Jonathan vide li cité de Vienna.

2) quel

 * Jonathan es in un old tren. Jonathan ama li tren. Li tren quel Jonathan ama es old.
 * Jonathan vide Vienna. Vienna es un cité. Li cité quel Jonathan vide es Vienna.

quam

 * Li tren es tre, tre old. Jonathan di: "Quam li tren es old!"
 * Li bifstec es tre, tre bon. Jonathan di: "Quam li bifstec es bon!"
 * Jonathan have un grand, tre grand problema. Jonathan di: "Quam mi problema es grand!"

hor, hora
hora hor = 60 minutes. Un hor = 60 minutes, du hores = 120 minutes. 6:00 es six horas e 2:00 es du horas. 6:00 minus 2:00 es quar hores.
 * It es six horas: 6:00
 * It es du horas deci: 2:10

quam
quam = !

 * Li tren es bell. Quam bell es li tren!
 * Jonathan es inteligente. Quam inteligent il es!

Departer

 * Li tren departet de Munich. Plu tard, li tren esset in Vienna.
 * Tri hores plu tard, Jonathan va departer.

Un, du, tri...

 * 1: un
 * 2: du
 * 3: tri
 * 4: quar
 * 5: quin
 * 6: six
 * 7: sett
 * 8: ott
 * 9: nin
 * 10: deci
 * 11: deciun
 * 12: decidu...

Vocabularium

 * bell
 * de
 * departer
 * desbell: ne bell
 * die = 24 horas
 * far
 * felici
 * have
 * hay
 * hor
 * hora
 * idé
 * manjar
 * mi
 * minus
 * moment: ne mult témpor
 * plu tard
 * problema
 * quam
 * quel
 * save
 * témpor
 * tre: mult
 * trincar

Di:

 * qu = k w
 * que: k w e
 * (que ≠ ke)
 * quel: k w el
 * quo: k w o
 * quin: k w in
 * hay: hay
 * (hay ≠ ay)


text:
User talk:148.253.186.234

Hi Halliford Students.

title: User talk:148.253.186.234


text: Template:Goodbook/OpenSSH

title: Template:Goodbook/OpenSSH


text:
Bioinformatics/Protein Structure

 * Proteins
 * Protein structure
 * Amino acids
 * Protein Secondary structure

 * Protein

title: Bioinformatics/Protein Structure


text:
User:Payamkermanshahi/sandbox

Powerlifting Rules of the World Powerlifting Federation for Powerlifting Athletes, Empires and Referees/practice1

title: User:Payamkermanshahi/sandbox


text:
User:SharperThanHaskell

Hey.

title: User:SharperThanHaskell


text:
Applied Programming/Dictionaries and Sets

Data Structure
In computer science, a data structure is a data organization, management, and storage format that enables efficient access and modification. More precisely, a data structure is a collection of data values, the relationships among them, and the functions or operations that can be applied to the data.

Data structures provide a means to manage large amounts of data efficiently for uses such as large databases and internet indexing services. Usually, efficient data structures are key to designing efficient algorithms. Some formal design methods and programming languages emphasize data structures, rather than algorithms, as the key organizing factor in software design. Data structures can be used to organize the storage and retrieval of information stored in both main memory and secondary memory.

Data structures are generally based on the ability of a computer to fetch and store data at any place in its memory, specified by a pointer—a bit string, representing a memory address, that can be itself stored in memory and manipulated by the program. Thus, the array and record data structures are based on computing the addresses of data items with arithmetic operations, while the linked data structures are based on storing addresses of data items within the structure itself.

The implementation of a data structure usually requires writing a set of procedures that create and manipulate instances of that structure. The efficiency of a data structure cannot be analyzed separately from those operations. This observation motivates the theoretical concept of an abstract data type, a data structure that is defined indirectly by the operations that may be performed on it, and the mathematical properties of those operations (including their space and time cost).

There are numerous types of data structures, generally built upon simpler primitive data types:

 * An array is a number of elements in a specific order, typically all of the same type (depending on the language, individual elements may either all be forced to be the same type, or may be of almost any type). Elements are accessed using an integer index to specify which element is required. Typical implementations allocate contiguous memory words for the elements of arrays (but this is not always a necessity). Arrays may be fixed-length or resizable.
 * A linked list (also just called list) is a linear collection of data elements of any type, called nodes, where each node has itself a value, and points to the next node in the linked list. The principal advantage of a linked list over an array is that values can always be efficiently inserted and removed without relocating the rest of the list. Certain other operations, such as random access to a certain element, are however slower on lists than on arrays.
 * A record (also called tuple or struct) is an aggregate data structure. A record is a value that contains other values, typically in fixed number and sequence and typically indexed by names. The elements of records are usually called fields or members.
 * A union is a data structure that specifies which of a number of permitted primitive types may be stored in its instances, e.g. float or long integer. Contrast with a record, which could be defined to contain a float and an integer; whereas in a union, there is only one value at a time. Enough space is allocated to contain the widest member datatype.
 * A tagged union (also called variant, variant record, discriminated union, or disjoint union) contains an additional field indicating its current type, for enhanced type safety.
 * An object is a data structure that contains data fields, like a record does, as well as various methods which operate on the data contents. An object is an in-memory instance of a class from a taxonomy. In the context of object-oriented programming, records are known as plain old data structures to distinguish them from objects.

Dictionary (Data Structure)
In computer science, an associative array, map, symbol table, or dictionary is an abstract data type composed of a collection of (key, value) pairs, such that each possible key appears at most once in the collection.

Operations associated with this data type allow:

 * the addition of a pair to the collection;
 * the removal of a pair from the collection;
 * the modification of an existing pair;
 * the lookup of a value associated with a particular key.

Implementing associative arrays poses the dictionary problem, a classic computer science problem: the task of designing a data structure that maintains a set of data during 'search', 'delete', and 'insert' operations. The two major solutions to the dictionary problem are a hash table and a search tree. In some cases it is also possible to solve the problem using directly addressed arrays, binary search trees, or other more specialized structures.

Many programming languages include associative arrays as primitive data types, and they are available in software libraries for many others. Content-addressable memory is a form of direct hardware-level support for associative arrays.

Associative arrays have many applications including such fundamental programming patterns as memoization and the decorator pattern.

The name does not come from the associative property known in mathematics. Rather, it arises from the fact that we associate values with keys.

In an associative array, the association between a key and a value is often known as a "mapping", and the same word mapping may also be used to refer to the process of creating a new association.

The operations that are usually defined for an associative array are:

 * Add or insert: add a new $$(key, value)$$ pair to the collection, mapping the new key to its new value. The arguments to this operation are the key and the value.
 * Reassign: replace the value in one of the $$(key, value)$$ pairs that are already in the collection, mapping an existing key to a new value. As with an insertion, the arguments to this operation are the key and the value.
 * Remove or delete: remove a $$(key, value)$$ pair from the collection, unmapping a given key from its value. The argument to this operation is the key.
 * Lookup: find the value (if any) that is bound to a given key. The argument to this operation is the key, and the value is returned from the operation. If no value is found, some associative array implementations raise an exception, while others create a pair with the given key and the default value of the value type (zero, empty container...).

Often then instead of add or reassign there is a single set operation that adds a new $$(key, value)$$ pair if one does not already exist, and otherwise reassigns it.

In addition, associative arrays may also include other operations such as determining the number of mappings or constructing an iterator to loop over all the mappings. Usually, for such an operation, the order in which the mappings are returned may be implementation-defined.

A multimap generalizes an associative array by allowing multiple values to be associated with a single key. A bidirectional map is a related abstract data type in which the mappings operate in both directions: each value must be associated with a unique key, and a second lookup operation takes a value as an argument and looks up the key associated with that value.

Suppose that the set of loans made by a library is represented in a data structure. Each book in a library may be checked out only by a single library patron at a time. However, a single patron may be able to check out multiple books. Therefore, the information about which books are checked out to which patrons may be represented by an associative array, in which the books are the keys and the patrons are the values. Using notation from Python or JSON, the data structure would be: A lookup operation on the key "Great Expectations" would return "John". If John returns his book, that would cause a deletion operation, and if Pat checks out a book, that would cause an insertion operation, leading to a different state: The basic definition of the dictionary does not mandate an order. To guarantee a fixed order of enumeration, ordered versions of the associative array are often used. There are two senses of an ordered dictionary:

 * The order of enumeration is always deterministic for a given set of keys by sorting. This is the case for tree-based implementations, one representative being the  container of C++.
 * The order of enumeration is key-independent and is instead based on the order of insertion. This is the case for the "ordered dictionary" in .NET Framework and Python.

The latter sense of ordered dictionaries are more commonly encountered. They can be implemented using an association list, or by overlaying a doubly linked list on top of a normal dictionary. The latter approach, as used by CPython before version 3.6, has the advantage of keeping the potentially better complexity of another implementation. CPython 3.6+ makes dictionaries ordered by splitting the hash table into an insertion-ordered array of k-v pairs and a sparse array ("hash table") of indices.

Key-Value Database
What is it?

A key-value database is a type of nonrelational database that uses a simple key-value method to store data. A key-value database stores data as a collection of key-value pairs in which a key serves as a unique identifier. Both keys and values can be anything, ranging from simple objects to complex compound objects. Key-value databases are highly partitionable and allow horizontal scaling at scales that other types of databases cannot achieve.

Compared to relational databases?

Relational databases organize data using tables. Tables are structures that impose a schema on the records that they hold. Each column within a table has a name and a data type. Each row represents an individual record or data item within the table, which contains values for each of the columns. Relational databases get their name from mathematical relationships that use tuples (like the rows in a table) to represent ordered sets of data.

What does this mean?

Key–value databases work in a very different fashion from the better known relational databases (RDB). RDBs predefine the data structure in the database as a series of tables containing fields with well defined data types. Exposing the data types to the database program allows it to apply a number of optimizations. In contrast, key–value systems treat the data as a single opaque collection, which may have different fields for every record. This offers considerable flexibility and more closely follows modern concepts like object-oriented programming. Because optional values are not represented by placeholders or input parameters, as in most RDBs, key–value databases often use far less memory to store the same database, which can lead to large performance gains in certain workloads.

Activities
1) Write a program that creates a dictionary where the keys are even integers between 2 and 20 and the values are the corresponding key multiplied by the odd integer before it.

Example output: {2: 2, 4: 12, 6: 30, 8: 56...}

2) Write a program that takes two lists and merges them into a single dictionary.

Example: Result: {5: 'a', 10: 'b', 15: 'c', 20: 'd'}

3) Write a program that searches for the minimum value and returns the corresponding key.

Example: Result: 'Nachos'

Key Terms
Dictionary / Associative array / Hash / Map - An abstract data type that can hold data in (key, value) pairs.

Frozen Set - A native data type in Python that have the qualities of sets — including class methods — but are immutable like tuples.

Hash collision - Occur when two entries are generated using the same index key. This has a high chance of occurring when hashing a random subset of a large set of possible keys.

Hash table - A type of data structure that stores key-value pairs. The key is sent to a hash function that performs arithmetic operations on it. The result (commonly called the hash value or hash) is the index of the key-value pair in the hash table.

Key - A field, or combination of fields, in a database table used to retrieve and sort rows in the table based on certain requirements. Keys are defined to speed up access to data and, in many cases, to create links between different tables.

Load factor - A critical statistic for hash tables that references how quickly the hash table can be accessed. A higher load factor indicates the table may become slower or fail to work at all.

Merge algorithm - A family of algorithms that take multiple sorted lists as input and produce a single list as output, containing all the elements of the inputs lists in sorted order. These algorithms are used as subroutines in various sorting algorithms, most famously merge sort.

Multimap - A generalization of a map or associative array abstract data type in which more than one value may be associated with and returned for a given key.

Multiset - A type of associative containers similar to set, with an exception that multiple elements can have same values.

Serialization - Produces a text or binary representation of the original objects that can be written directly to a file and offers a solution to use associative arrays in permanent form.

Set - An unordered, mutable data type where each value must be unique.


text:
History of video games/Platforms/CT510

Development
Development of the console began in 2008 by Lenovo, a major computer manufacturer in Beijing, China. Beijing Eedoo Technology was founded on the 1st of July, 2010,  as an offshoot of the S&P division of Lenovo  and operated out of the Haidian district of Beijing in the Shangdi Information Park. Lenovo continued to support the project following the split, dedicating 40 engineers to the project. Further financial backing was provided by Legend Holdings and Legend Capital.

Development of the system suffered multiple delays which pushed the launch of the console from 2011, to early 2012 to mid 2012. Development of the console was costly, with $15 million spent on R&D. A critical issue during development was making the system friendly to beginners, as motion gaming was uncommon in China at the time and typical conventions in motion games at the time proved strange or even insulting to casual Chinese gamers during testing. The console was initially referred to as the eBox during development, and later had its name changed to the iSec and also the Sports Entertainment Center. Eedoo had planned to sell 12 million consoles in China.

Launch
The console was launched on April 29th, 2012 in 11 Chinese cities, with the base model CT510 costing a sizable 3,799 yuan. The higher spec CT520 cost 3,999 yuan. This high price put it at a disadvantage when compared to cheaper imported consoles. On launch the system was notably difficult to buy, both in person, and online.

The device was widely mocked on Chinese websites on launch. The console even received accidental criticism from a director of it's own manufacturer on social media, though this statement was later retracted.

The system did not target hardcore gamers, and the company explicitly avoided the device a console, likely to dodge a ban on gaming consoles at the time. Eedoo advertised the system in upscale shopping malls with small experience centers.

By November 2012 the system had notedly poor market performance, and the CT310 price reduced model was launched for 2,999 yuan. Given that a worldwide release had been planned once the console sold a million units in China, and such a release never occurred, the console presumably sold less then this target.

At some point later, Eedoo had ceased operations.

Technology
The system had a dual core CPU clocked at 1.8 gigahertz, and additionally used a 3D capable GPU.

The system used a Belgian SoftKenetic 3D camera for gameplay, integrating a which uses a CMOS digital camera with a resolution of 320 by 240 pixels and an LED to emit light for time of flight measurements. Despite the system commonly being compared with the Xbox Kinect, it should be noted that this is technologically quite different from the hardware used by the Kinect. The system also used a remote control for normal navigation.

There were three different models of the system, with the differing storage sizes and case colors. At launch the system shipped with either a 250 (CT510 ) or 320 (CT520 ) gigabyte capacity hard disk drive was used for system storage. Later the CT310 was released, which contained a paltry 32 gigabyte capacity storage drive with a reduced price.

The system had four USB 2.0 ports divided evenly between the front and back of the system.

The console used Beckon middleware and the Beckon Development Suite by Omek Interactive for gesture recognition.

The system could use an online store, and came equipped with a "LAN port".

Games
"We have localized this product for Chinese users. This is our advantage."

The console featured 8 included games, which used a camera controllerless setup similar to the Xbox Kinect for exercise games. The exergaming activities were localized, and included regional focused activities such as Taichi. While some game developers for the system were based in China, two games for the system were developed by the Israeli company Side-kick, with other official game developers for the system being based in Europe and North America.

 * Green Exercise
 * Maya Fit - A game noted for it's similarity to Wii Fit.
 * Dance Wall
 * Hole in the Wall
 * Fun Park Adventure
 * Bumper Cars
 * Flyer's Story
 * Kung Fu - Variant of Kung Fu Live

Models

 * CT310 - 32 gigabytes of storage
 * CT510 - 250 gigabytes of storage
 * Black CT510
 * White CT510 - Case made of Aluminum
 * CT520 - 320 gigabytes of storage

title: History of video games/Platforms/CT510


text:
Salute, Jonathan!/Capitul 4 - with notes

Contenete - Capitul 3 - Capitul 4 - Capitul 5

Quaresim capitul (4.esim capitul)
U es Jonathan? Esque il sta in Vienna? No, il sta in un diferent cité. Il sta in Bistritz. Quo es Bistritz? It es un cité in Rumania. Nu comensa li viage in Rumania.

Jonathan scri in su jurnale: “Li unesim may yo esset in Munich. Li duesim may yo esset in Vienna. Poy yo esset in Budapest. Budapest esset bell. Ma yo ne havet témpor in Budapest. Yo videt li strade in Budapest. In Budapest yo pensat: ci fini li west, e ci comensa li ost. Budapest es diferent.”

Il pensa un poc plu pri Budapest. Il pensa: “Yo es un person quel veni de Anglia, de London. Yo parla anglés, nam li persones in Anglia parla anglés. Ma in Budapest yo ne parlat con li persones in anglés; yo parlat in german. Mi german ne es bon, ma li persones in Budapest ne parla anglés. Noi parlat in german. It es interessant que li persones in Budapest parla german.”

Nu Jonathan pensa pri su viage. Il pensa: “Yo esset in li muséo in London. In li muséo esset libres pri un altri land. Yo leet li libres. In li muséo esset cartes pri un altri land. Yo videt li cartes. Li libres e li cartes dit que li altri land es lontan, ma interessant. In li altri land es mult persones, mult diferent persones.”

Nu Jonathan pensa plu pri su viage. Il pensa: “Yer yo esset in Klausenburg. Yo manjat in Klausenburg. Li nómine del manjage esset “paprika hendl”. It es tre bon, li manjage in Klausenburg. Li hotel esset bon, ma yo ne dormit bon. Ma li land es tre bell! In li tren yo videt mult borgos e mult castelles. Un cité es plu grand quam un borgo, ma li borgos es tre bell. Un castelle es plu grand quam un hotel, e plu bell quam un hotel! Borgos es minu grand quam cités, ma ili es bell, e hoteles es minu grand quam castelles.” Jonathan scri plu in su jurnale: “Bistritz es un interessant loc. Bistritz es un old loc, plu old quam altri locs. Anc mi hotel in Bistritz es old, plu old quam altri hoteles. In li hotel yo dit mi nómine: “Yo es Jonathan Harker.” e ili dit me: “Benevenit al hotel.” In li hotel yo videt un lettre por me. Nu yo va leer mi lettre.”

Jonathan lee su lettre. It di:

“Mi amíco. - Benevenit. Dormi bon. Yo es in Bukovina, ples venir a Bukovina. Esque li viage de London esset bon? Mi land es tre bell. Benevenit a mi land.

Vor amico, DRACULA.”

Jonathan lee li lettre e pensa pri su amico Comto Dracula. Qui il es? Il ne save. Ma su amico es interessant. Anc li borgo Bistritz es interessant. Jonathan es felici, e pensa pri su amico. Poy il dormi.

plu quam, minu quam

 * plu quam: >
 * Jonathan es plu grand quam un jurnale. = Jonathan > jurnale (Jonathan es grand, li jurnale ne es grand)
 * Manjar un bifstec es plu bon quam ne manjar un bifstec. = Manjar un bifstec > Ne manjar un bifstec (Manjar un bifstec es bon, ne manjar un bifstec ne es bon)
 * minu quam: <
 * Un dom es minu grand quam un castelle. = dom < castelle (Un castelle es grand, un dom ne es grand)
 * Manjar un jurnale es minu bon quam manjar un bifstec. = manjar un jurnale < manjar un bifstec (Manjar un bifstec es bon; manjar un jurnale ne es bon)

plurale (-s, -es)
Li plurale es -s, anc -es.

 * -s:
 * Un libre. Du, tri, quar....libres
 * Un loc. Du, tri, quar...locs.
 * Un cité. Du, tri, quar...cités.
 * -es:
 * Un mann, un hotel, un land, un person. Du, tri, quar mannes, hoteles, landes, persones.

del
de + il = del.

su
il, it -> su
 * Jonathan lee un lettre. It es li lettre de Jonathan. It es su lettre.
 * Li cité have un muséo. It es li muséo del cité. It es su muséo.

ili

 * Un mann es il. Du, tri, quar...mannes es ili.
 * Un libre es it. Du, tri, quar...libres es ili.
 * Un mann e un libre es ili.

vu, vor

 * Jonathan manja un manjage. Un person di: "Vu manja. Esque vor manjage es bon?" (vor = de Jonathan)
 * Jonathan pensa pri Dracula. Il pensa: "Dracula, vu es un bon mann. Vor land es tre bell."

altri

 * Jonathan veni de Anglia. Il ne veni de Rumania. Rumania es un altri land. (= Rumania ne es Anglia, it es un altri land).

lontan

 * Jonathan es in li tren hodie, il esset in li tren yer, il va esser in li tren deman. Rumania es lontan.

Vocabularium

 * altri
 * amíco
 * anglés, Anglia
 * angl·és
 * Angl·ia
 * benevenit
 * (bene·veni·t)
 * borgo: un ne grand cité
 * carte
 * castelle
 * ci
 * comensar
 * comto: un mann quel have un castelle
 * diferent: ≠
 * dormir
 * german, Germania
 * german
 * German·ia
 * hotel
 * ili
 * land
 * lettre
 * libre:
 * loc
 * lontan
 * muséo: un grand dom quel have old libres e cartes
 * nómine
 * ost
 * parlar: 💬
 * person
 * strade
 * su
 * un poc: ne mult (1, 2, 3 = un poc)
 * veni
 * west

Di:

 * ss = s
 * esset: eset
 * interessant: interesant
 * vocale (a, e, i, o, u) + s + vocale = z
 * muséo: muzéo
 * quaresim: quarezim


text:
Active Learning In Virtual Environment

Table of Contents

 * /Introduction/

Methods

 * /Polling/
 * /Minute Paper/
 * /Pro and Con Grid/
 * /Peer Review/
 * Think-Pair-Share
 * The Muddiest Point
 * Collaborative Note Taking
 * Case Study
 * /Flipped Classroom/
 * What's Missing
 * /Debate/
 * Mind Maps/Concept Maps
 * /The Jigsaw Technique/
 * /Brainwriting/
 * /Reflective Journals/
 * Thinking-Aloud Pair Problem Solving
 * /Team Learning/
 * /Reciprocal Questioning/
 * /Snowball Technique/
 * /Kinesthetic Learning/
 * /Role Playing/

title: Active Learning In Virtual Environment


text:
Active Learning In Virtual Environment/Polling

Activity: #in-class/short-term, #individual-work, #quick-preparation

Outline
Polling can be used as a fast method to explore students’ opinions on a certain subject. What makes it convenient is Zoom’s polling feature that allows students to post their responses during the class. Therefore, teachers are able to view the answers right away. A variety of polling types is available to choose from, such as multiple choice polls, true or false statements or Likert-type questions. Additionally, it helps a teacher to keep track of students’ attendance or prevent any miscomprehensions at any time throughout the class. As a matter of fact, there are alternative online polling platforms to choose from: SurveyMonkey, Poll Everywhere and Google Forms.

Activity arrangement
Once students start answering the questions, you will be able to view the responses simultaneously.
 * create a poll in one of the platforms
 * decide on the approximate time for students to answer during the class
 * check that the questions are understandable and set correctly
 * provide students with verbal instruction (or/and written if needed)
 * end the poll.

Pointers

 * easy to arrange in large groups of students.
 * less pressure on students that don't like active participation.
 * engages students to stay attentive.

How to use this method in online class?
One of the most common options to use polling during the class is Zoom polling feature. There are certain necessary aspects you should keep in mind, before creating a poll in Zoom. For example, there are such limitations as max 10 questions in one poll and the number of participants being max 25. In addition, you have to make sure you created a meeting using your Personal Meeting ID. A detailed step-wise instruction is available on their website.

If a meeting is done through Google Meet, a Google Forms feature would be the most convenient feature to use. Besides, unlike Zoom polling feature, google forms can be conducted offline.


text:
Active Learning In Virtual Environment/Minute Paper

Activity: #in-class/short-term, #individual-work, #feedback, #discussion

Outline
A minute paper is a teaching tool in which students have to provide responses or thoughts about the class held or about the homework that they had. The main goal of the minute paper is to understand what the students have learned or what they found interesting and even what subject they found difficult in class. A minute paper gives an idea to the teacher of what the students have actually learned and whether the outcomes of the students’ learnings correspond to what the teacher had in mind. Results of the minute paper can be discussed in the class which gives the students even more possibilities to reflect on what they have learned, what other students have learned, and even learn from those other students. This can be used in various platforms, for example Moodle. The teacher can upload the questions in Moodle and the students can go and provide answers to the questions.

Activity arrangement

 * inform the students that they may have to provide answer to a minute paper during the end of the class or in the beginning of the class for example for homework
 * stop the lecture at the time of your choosing
 * ask questions which require broader thinking about the topic of the class, avoid yes and no questions
 * students provide their answers, look into them
 * provide feedback and discussion about the answer either in the class or before the next class

Pointers

 * extremely quick way of collecting feedback.
 * provides results if the students perceived the teachers main point or ideas that the teacher had in mind for the class.
 * the students must self-reflect on what was studied in the class and therefore analyse what they’ve learned.


text:
User:EDG 543/EditCounterOptIn.js

//hi

title: User:EDG 543/EditCounterOptIn.js


text:
Mirad Thesaurus/Fauna

= Fauna =
 * The names of animals in Mirad all contain the letters p, meaning mobile, and end in the letter t for creature. The ordinal vowel in the stem relates to a geophysical domain, such as air, water, land, or combinations of these.

 * Note the following details from the above chart:
 * Stems of all flying creatures (except reptiles) end in -at
 * Stems of birds of prey or raptors end in -yat.
 * Stems of aquatic birds end in -iat.
 * Stem of flying insects end in -lat.
 * Stems of all land animals and non-flying insects end in -ot or -et.
 * Wild land animals end in -yot.
 * Less wild land animals end in -ot.
 * Less wild aquatic land animals end in -iot.
 * Domesticated land animals end in -et.
 * Non-flying reptiles end in -yet.
 * Flying reptiles end in -ayet.
 * Amphibians or batrachians end in -iyet.
 * Marsuplials end in -let.
 * Non-flying insects end in -elt.
 * Worms end in -eyet.
 * All sea and river creatures end in -it, especially fish proper.
 * Game or predatory fish end in -yit.
 * Crustaceans or shellfish end in -iit.
 * Marine mammals end in -eit.
 * Mollusks end in -yeit.
 * The feminine counterpart of animals is derived by following the last stem vowel with -y-.
 * The offspring of an animal is derived by suffixing -ud to the stem.
 * A small version of an animal is derved by suffixing -og to the stem.
 * A pet version of an animal is derived by suffixing -if to the stem.

title: Mirad Thesaurus/Fauna


text:
Mirad Thesaurus/Flora

= Flora =
 * Words with the f...b pattern refer to plants, fruits, and nuts; those with the v...b pattern refer to grasses and cereals; and those with v...l refer to vegetables.

Colors

 * Most color names in Mirad are derived from flowers, fruits, or other things in nature. The basic word skeleton is v...za.

 * Dark versions of a color have the format vy...za, while lighter or -ish forms have the format v...yza, e.g.:

 * vaza=green
 * vayza=light green, greenish
 * vyaza=dark green

title: Mirad Thesaurus/Flora


text:
Talk:Linear Algebra/Solving Linear Systems

This page is incredibly confusing. As an example, I'm an engineer with 30 years of work experience, and while I can solve the 2 systems of equations, I have no idea what the text talking about.

In the first example, there appear to be masses balanced on a level. The text immediately below it is talking about torque. Why? What is the connection of torque and forces with the masses in the picture? And regardless of what it's talking about the wording of the paragraph immediately below the pictures is difficult to follow with that long parenthetical. The first sentence also appears to be a sentence fragment.

The picture is also confusing. When I first looked at it, I had no idea what the numbers represented. The 15 and 25 below the images seemed completely disconnected from the masses and distances shown at the top of the image. It would be more clear if they were above the masses like the other numbers.

Since I'm not a physicist and don't understand the text about torque, I have no idea where the value 100 comes from in the first equation, or where the 50 comes from in the second equation. It's not the sum of the 3 distances. It's not the sum of the masses. What is it? These things could all be explained in the text to make it more clear what's going on. 108.185.142.199 (discuss) 06:32, 18 March 2021 (UTC)

 * Hi I agree it could be expanded, and hopefully it will one day. For what torque is see torque, but for a balance is merely force X distance. Jules  (Mrjulesd) 23:05, 21 March 2021 (UTC)


text:
Wikibooks:Reading room/Administrative Assistance/Archives/2021/January

Block request
— vandalism-only account. Thanks. —Hasley (discuss • contribs) 19:22, 26 January 2021 (UTC)
 * Done. --Pi zero (discuss • contribs) 19:34, 26 January 2021 (UTC)


text:
Portuguese/Contents/BP Introduction

Why is English similar to Portuguese
Due to the Norman conquest of England starting in 1066, the old English language was over the period a few hundred years creolized approximately 30% with French words, 30% with Latin words (Italian/Spanish/Portuguese) to form a new language called Middle English. For this reason English speakers today will find many of the words of Portuguese familiar and cognate with English words Having similar meanings.

title: Portuguese/Contents/BP Introduction


title: User:AnotherEditor144/sandbox


text:
User:Galkinletter

User:Galkinletter

title: User:Galkinletter


text:
User talk:41.113.175.133

ʻ

title: User talk:41.113.175.133