Input: [Product Name] Wall Mounted Fume Extractor Sky Sentry -- SS-300-SKY [Notes]

Output: When space saving is a priority, a wall mounted fume extractor may be the optimal solution. The model 300 Sky Sentry offers an easy to maneuver, operator friendly, self-supportive flex...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Wall Mounted Fume Extractor Sky Sentry -- SS-400-SKY [Notes]

Output: When space saving is a priority, a wall mounted fume extractor may be the optimal solution. The model 400 Sky Sentry offers an easy to maneuver, operator friendly, self-supportive flex...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Laminar Flow Hood Negative Pressure Winged Sentry w/ Lid -- SS-200-WSL [Notes]

Output: When the application calls for an air cleaner with a customized enclosure, the Model 200 Winged Sentry (Laminar Flow Hood) may be an excellent choice. The "Wing Flaps" move in...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Laminar Flow Hood Negative Pressure Winged Sentry -- SS-300-WS [Notes]

Output: When the application calls for an air cleaner with a customized enclosure, the Model 300 Winged Sentry (Laminar Flow) may be an excellent choice. The "Wing Flaps" move in and...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Benchtop Fume Extractor Winged Sentry -- SS-200-WS [Notes]

Output: When the application calls for an air cleaner with a customized enclosure, the Winged Sentry may be an excellent choice. The "Wing Flaps" move in and out to provide infinitely...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Fume Extractor Snorkel Sentry -- SS-200-SS [Notes]

Output: When the application requires a flexible source capture solution, the Snorkel Sentry may be an excellent choice. This unit features a self supporting adjustable hood, a "no tool" mounting bracket,...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Mounted Fume Extractor for Enclosed Machinery Mounted Sentry -- SS-300-MS [Notes]

Output: When the situation calls for mounting a small but powerful air cleaner directly to a workbench, a hood, or even to enclosed machinery; the Mounted Sentry may be an excellent...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Product Name] Compact Mounted Fume Extractor Mounted Sentry -- SS-200-MS [Notes]

Output: When the situation calls for mounting a small but powerful industrial air cleaner directly to a workbench, a hood, or even to enclosed machinery; the Mounted Sentry may be an...

Sentry Air Systems, Inc. Mist Collectors and Fume Collectors Data Sheets | IHS Engineering360


Input: [Note] Ability to dim backlight, turn on and off GSM, GPS, and other devices outside the CPU Huge (700mW) [Status] Implemented [Option]

Output: External peripheral control

Neo 1973 GTA01 Power Management - Openmoko

Required kernel mode power saving, and relative saving of battery life.


Input: [Note] The CPU clock is 12MHz, this is the lowest power mode with the CPU awake Huge(300mW) [Status] Not implemented [Option]

Output: Slow Mode

Neo 1973 GTA01 Power Management - Openmoko


Input: [Note] Dynamically alter CPU core voltage according to frequency Large(50mW) [Status] Not implemented [Option]

Output: Variable CPU core voltage

Neo 1973 GTA01 Power Management - Openmoko


Input: [Note] Turn off CPU clock while rest of SoC remains awake Moderate(150mW) [Status] Not implemented [Option]

Output: CPU Idle mode

Neo 1973 GTA01 Power Management - Openmoko


Input: [Note] Vary CPU frequency to lower power consumption. Huge(250mW) [Status] Not implemented [Option]

Output: Variable CPU frequency ~20Mhz to 266Mhz

Neo 1973 GTA01 Power Management - Openmoko


Input: [Note] Remove periodic timer interrupts in kernel Modest(10mW?) [Status] Not implemented [Option]

Output: Tickless Kernel

Neo 1973 GTA01 Power Management - Openmoko


Input: [Note] Suspend CPU totally and resume when required in under 1s. Huge (50mW) [Status] Not implemented [Option]

Output: Rapid Suspend-RAM

Neo 1973 GTA01 Power Management - Openmoko


Input: [key] :buckets [default] 10 [description] Number of buckets for histogram [type]

Output: int

Reusable filtering plug-in in Rails - Stanford University Wiki

Optional parameters (options)


Input: [key] :width [default] 400 [description] Width of histogram image in px [type]

Output: int

Reusable filtering plug-in in Rails - Stanford University Wiki

Optional parameters (options)


Input: [key] :height [default] 100 [description] Height of histogram image in px [type]

Output: int

Reusable filtering plug-in in Rails - Stanford University Wiki

Optional parameters (options)


Input: [key] :space [default] 0 [description] Space between bars in the histogram image [type]

Output: int

Reusable filtering plug-in in Rails - Stanford University Wiki

Optional parameters (options)


Input: [key] :rescale [default] true [description] Use log scale for y-axis when true, linear axis otherwise [type]

Output: boolean

Reusable filtering plug-in in Rails - Stanford University Wiki

Optional parameters (options)


Input: [key] :submit [default] 'search_submit' [description] id of submit button to use after histogram is manipulated [type]

Output: string

Reusable filtering plug-in in Rails - Stanford University Wiki

Optional parameters (options)


Input: [Start] 6:22pm [Artist] Psychic TV [Album] A Saucer Full Of Pink [Label] Cleopatra [Track]

Output: Set The Controls For The Heart Of The Sun


Input: [Start] 6:14pm [Artist] Zodiac Youth/Orb [Album] Auntie Aubrey's Excursions Beyond The Call Of Duty [Label] Deviant [Track]

Output: Fast Forward The Future (Orb Remix)


Input: [Start] 6:07pm [Artist] Killing Joke [Album] Hosannas From The Basements Of Hell [Label] Cooking Vinyl [Track]

Output: Grattitude


Input: [Start] 6:01pm [Artist] Porcupine Tree [Album] Stars Die [Label] Kscope [Track]

Output: And The Swallows Dance Around The Sun


Input: [Start] 5:56pm [Artist] The Boyzz [Album] Too Wild To Tame [Label] Cleveland International Records [Track]

Output: Too Wild To Tame


Input: [Start] 5:53pm [Artist] Max Webster [Album] Universal Juveniles [Label] Anthem Records [Track]

Output: Chalkers


Input: [Start] 5:47pm [Artist] How To Destroy Angels [Album] Welcome Oblivion [Label] Columbia [Track]

Output: Keep It Together


Input: [Start] 5:42pm [Artist] Pretty Things [Album] Heavy Mod [Label] Mojo [Track]

Output: Baron Saturday


Input: [Start] 5:31pm [Artist] Liberation Thru Herring [Album] Pick & Mix [Label] Delerium [Track]

Output: The Root Verses Of The Six Bardos


Input: [Start] 5:16pm [Artist] Ghost [Album] Lama Rabi Rabi [Label] Drag City [Track]

Output: Mastillah/RabiRabi


Input: [Start] 5:09pm [Artist] Offspring/Lard [Album] Ixnay/Pure Chewing Satisfaction [Label] ?/Alternative Tentacles [Track]

Output: The Disclaimer/Faith, Hope and Treachery


Input: [Start] 5:04pm [Artist] Cevin Key [Album] Wild Planet [Label] Subconscious Communications [Track]

Output: I Still Ate Her`


Input: [Start] 4:58pm [Artist] Nazareth [Album] Play N The Game [Label] A&M [Track]

Output: Somebody To Roll


Input: [Start] 4:54pm [Artist] Bubble Puppy [Album] Heavy Mod [Label] Mojo [Track]

Output: Hot Smoke And Sassafras


Input: [Start] 4:49pm [Artist] Painkiller [Album] Buried Secrets [Label] Earache [Track]

Output: Buried Secrets


Input: [Start] 4:31pm [Artist] Electric Masada [Album] At The Mountains Of Madness [Label] Tzadik [Track]

Output: Karaim


Input: [Start] 4:25pm [Artist] Alice Cooper [Album] Flush The Fashion [Label] Warner Bros. Records [Track]

Output: Talk Talk/Clones


Input: [Start] 4:19pm [Artist] Prong [Album] Rude Awakening [Label] Epic [Track]

Output: Controller


Input: [Start] 4:11pm [Artist] Download [Album] A Homage To Neu! [Label] Cleopatra [Track]

Output: Hallo Gallo


Input: [Start] 4:09pm [Artist] Test Dept. [Album] Drug Test 2 [Label] Invisible [Track]

Output: Chillio


Input: [PC] mroemzh [Effect]

Output: Gang members spawn much faster

Difference between revisions of "Cheats in GTA San Andreas" - Grand Theft Wiki, the GTA wiki


Input: [PC] n/a [Effect]

Output: Gang wars break out all over the streets

Difference between revisions of "Cheats in GTA San Andreas" - Grand Theft Wiki, the GTA wiki


Input: [PS2] n/a [PC] mroemzh [Xbox] n/a [Effect]

Output: Gangs and workers

Difference between revisions of "Cheats in GTA San Andreas" - Grand Theft Wiki, the GTA wiki


Input: [PC] bifbuzz [Effect]

Output: No citizens or cops, only gang members having gun fights

Difference between revisions of "Cheats in GTA San Andreas" - Grand Theft Wiki, the GTA wiki


Input: [PC] sjmahpe [Effect]

Output: Recruit anyone into gang with Pistols

Difference between revisions of "Cheats in GTA San Andreas" - Grand Theft Wiki, the GTA wiki


Input: [PC] ssoxfsq/rocketmayhem [Effect]

Output: Recruit anyone into gang with rocket launchers

Difference between revisions of "Cheats in GTA San Andreas" - Grand Theft Wiki, the GTA wiki


Input: [Description] Requests fetched from the server [Filter]

Output: Normal finished requests


Input: [Description] Requests currently being fetched from the server [Filter]

Output: Loading requests


Input: [Description] Requests with response coming from the browser cache (HTTP status code 304) [Filter]

Output: Cached requests


Input: [Description] Requests with response coming from the BFCache [Filter]

Output: BFCached requests


Input: [Description] Requests, which returned an HTTP error (HTTP status code 4xx or 5xx) [Filter]

Output: Erroneous requests


Input: [Description] Requests, which were aborted [Filter]

Output: Aborted requests


Input: [0] Su [6-9 AM] Available [9-12 AM] Available [3-6 PM] Available [6-9 PM] Available [9-12 PM] Available [12-6 AM] Not Available [12-3 PM]

Output: Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [0] Mo [6-9 AM] Available [9-12 AM] Available [3-6 PM] Available [6-9 PM] Available [9-12 PM] Available [12-6 AM] Not Available [12-3 PM]

Output: Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [0] Tu [6-9 AM] Not Available [9-12 AM] Not Available [3-6 PM] Not Available [6-9 PM] Not Available [9-12 PM] Not Available [12-6 AM] Not Available [12-3 PM]

Output: Not Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [0] We [6-9 AM] Available [9-12 AM] Available [3-6 PM] Available [6-9 PM] Available [9-12 PM] Available [12-6 AM] Not Available [12-3 PM]

Output: Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [0] Th [6-9 AM] Not Available [9-12 AM] Not Available [3-6 PM] Not Available [6-9 PM] Not Available [9-12 PM] Not Available [12-6 AM] Not Available [12-3 PM]

Output: Not Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [0] Fr [6-9 AM] Available [9-12 AM] Available [3-6 PM] Available [6-9 PM] Available [9-12 PM] Available [12-6 AM] Not Available [12-3 PM]

Output: Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [0] Sa [6-9 AM] Available [9-12 AM] Available [3-6 PM] Available [6-9 PM] Available [9-12 PM] Available [12-6 AM] Not Available [12-3 PM]

Output: Available

Samantha W. - Dunkirk Pet Care Provider - Sittercity.com


Input: [Type of information] Gate change [Information channel] SMS E-mail* [When?] From 2 hours before departure [Requirements]

Output: Mobile phone number in your Miles & More profile or in your booking; passengers with mobile boarding pass by SMS

Information via SMS - Lufthansa ® Nigeria


Input: [Type of information] Seat change because of a change of aircraft [Information channel] SMS E-mail* [When?] Immediately [Requirements]

Output: Mobile phone number in your Miles & More profile

Information via SMS - Lufthansa ® Nigeria


Input: [Type of information] Delay > 30 min. [Information channel] SMS E-mail* [When?] Immediately [Requirements]

Output: Mobile phone number in your Miles & More profile or in your booking; passengers with mobile boarding pass by SMS

Information via SMS - Lufthansa ® Nigeria


Input: [Type of information] Cancellation [Information channel] SMS E-mail* [When?] Immediately [Requirements]

Output: Mobile phone number in your Miles & More profile or in your booking; passengers with mobile boarding pass by SMS

Information via SMS - Lufthansa ® Nigeria


Input: [Type of information] Allocation to alternative flight in case of flight disruptions [Information channel] SMS [When?] Immediately [Requirements]

Output: Mobile phone number in your Miles & More profile or in your booking; passengers with mobile boarding pass by SMS

Information via SMS - Lufthansa ® Nigeria


Input: [Type of information] Sending out a new mobile boarding pass after allocation is made [Information channel] E-mail SMS [When?] Immediately [Requirements]

Output: Mobile boarding pass already requested for the original flight

Information via SMS - Lufthansa ® Nigeria


Input: [Task ID] 3 [Resource Name] Project Management [Task Name]

Output: Develop engagement letter & proposal for requirements analysis phase


Input: [Task ID] 6 [Resource Name] Project Management [Task Name]

Output: Project Kickoff meeting


Input: [Task ID] 8 [Resource Name] Project Management [Task Name]

Output: Identify Customer Project Management and Team Members


Input: [Task ID] 9 [Resource Name] Project Management [Task Name]

Output: Identify Partner Team: Sales, Project Team members


Input: [Task ID] 10 [Resource Name] Project Management [Task Name]

Output: Develop Client Communication Plan


Input: [Task ID] 11 [Resource Name] Project Management [Task Name]

Output: Develop Contingency Plan


Input: [Task ID] 12 [Resource Name] Project Management [Task Name]

Output: Prepare Work Environment


Input: [Task ID] 13 [Resource Name] Project Management [Task Name]

Output: Prepare Project Binder


Input: [Task ID] 15 [Resource Name] Project Management [Task Name]

Output: Establish Change Control Process


Input: [Task ID] 16 [Resource Name] Project Management [Task Name]

Output: Establish Issue Management Process


Input: [Task ID] 17 [Resource Name] Project Management [Task Name]

Output: Establish Status Tracking and Reporting Process


Input: [Task ID] 51 [Resource Name] Client [Task Name]

Output: Review and document current network and application e-infrastructure


Input: [Task ID] 52 [Resource Name] Consultant [Task Name]

Output: Review needed technology application, hardware, software and network requirements


Input: [Task ID] 53 [Resource Name] Consultant [Task Name]

Output: Document Disparities between existing environment and recommended


Input: [Task ID] 59 [Resource Name] Consultant [Task Name]

Output: Create Development Environment


Input: [Task ID] 60 [Resource Name] Consultant [Task Name]

Output: Build Development Database


Input: [Task ID] 61 [Resource Name] Consultant [Task Name]

Output: Set up Development Workstation


Input: [Task ID] 62 [Resource Name] Consultant [Task Name]

Output: Install ERP, Site Commerce Server, Dev tools & other needed applications


Input: [Task ID] 83 [Resource Name] Consultant [Task Name]

Output: Develop and iteratively review requirements and design document


Input: [Task ID] 91 [Resource Name] Consultant [Task Name]

Output: Define basic site requirements


Input: [Task ID] 93 [Resource Name] Consultant [Task Name]

Output: Design and document screen configuration requirements


Input: [Task ID] 124 [Resource Name] Project Management [Task Name]

Output: Define Success Criteria


Input: [Task ID] 124 [Resource Name] Client [Task Name]

Output: Define Success Criteria


Input: [Task ID] 125 [Resource Name] Consultant [Task Name]

Output: Design User Test Scenarios


Input: [Task ID] 126 [Resource Name] Consultant [Task Name]

Output: Design Integration Test Scenarios


Input: [Task ID] 127 [Resource Name] Consultant [Task Name]

Output: Design System Test Scenarios


Input: [Task ID] 128 [Resource Name] Consultant [Task Name]

Output: Assess Test Environment: hardware & software requirements


Input: [Task ID] 129 [Resource Name] Consultant [Task Name]

Output: Design process for tracking bugs found in testing


Input: [Task ID] 130 [Resource Name] Consultant [Task Name]

Output: Design process to build test data


Input: [Task ID] 131 [Resource Name] Project Management [Task Name]

Output: Review Systems & Integration Test Plan


Input: [Task ID] 134 [Resource Name] Consultant [Task Name]

Output: Report Tests


Input: [Task ID] 135 [Resource Name] Consultant [Task Name]

Output: Query Tests


Input: [Task ID] 136 [Resource Name] Consultant [Task Name]

Output: Application Interface Tests


Input: [Task ID] 137 [Resource Name] Consultant [Task Name]

Output: Web user tests


Input: [Task ID] 138 [Resource Name] Consultant [Task Name]

Output: Back Office Integration Tests


Input: [Task ID] 139 [Resource Name] Consultant [Task Name]

Output: Conduct System Tests


Input: [Task ID] 140 [Resource Name] Project Management [Task Name]

Output: Review Testing Results


Input: [Task ID] 141 [Resource Name] Client [Task Name]

Output: Test Support Operations


Input: [Task ID] 142 [Resource Name] Project Management [Task Name]

Output: Final validation review


Input: [Task ID] 154 [Resource Name] Consultant [Task Name]

Output: Turn on Back Office Integration


Input: [Task ID] 159 [Resource Name] Consultant [Task Name]

Output: User Support and Guidance


Input: [Task ID] 163 [Resource Name] Project Management [Task Name]

Output: Obtain Implementation Signoff.


Input: [Task ID] 165 [Resource Name] Project Management [Task Name]

Output: Manage Financial Information


Input: [Task ID] 166 [Resource Name] Project Management [Task Name]

Output: Write Status Reports


Input: [Task ID] 167 [Resource Name] Project Management [Task Name]

Output: Manage Project Plan & Actuals


Input: [Task ID] 168 [Resource Name] Project Management [Task Name]

Output: Manage Change Control


Input: [Task ID] 169 [Resource Name] Project Management [Task Name]

Output: Review and Maintain Issue Log


Input: [Task ID] 170 [Resource Name] Project Management [Task Name]

Output: Maintain Risk Log


Input: [Task ID] 171 [Resource Name] Project Management [Task Name]

Output: Conduct Project Status Meetings


Input: [Task ID] 172 [Resource Name] Project Management [Task Name]

Output: Conduct Client Briefings


Input: [Task ID] 173 [Resource Name] Project Management [Task Name]

Output: Conduct User Communications


Input: [Task ID] 174 [Resource Name] Project Management [Task Name]

Output: Perform Day to Day Meetings and Issue Management


Input: [Job Title] Assistant Director of Student Diversity Programs [Office] Student Diversity [Job Type] Unclassified [Category] Staff [Closing Date] Until Filled [FT/PT]

Output: Full Time

Job Opening Details - Pittsburg State University


Input: [Job Title] Instructor, Full-Time Temporary--Nursing [Office] School of Nursing [Job Type] Unclassified [Category] Faculty [Closing Date] Until Filled [FT/PT]

Output: Full Time

Job Opening Details - Pittsburg State University


Input: [Job Title] Adjunct Instructor - Fall 2015 - Environmental Life Science [Office] Biology [Job Type] Unclassified [Category] Faculty [Closing Date] Until Filled [FT/PT]

Output: Part Time

Job Opening Details - Pittsburg State University


Input: [Job Title] Part-time Temporary Instructor--Biology [Office] Biology [Job Type] Unclassified [Category] Faculty [Closing Date] Until Filled [FT/PT]

Output: Part Time

Job Opening Details - Pittsburg State University


Input: [Job Title] Phonathon Coordinator [Office] Development [Job Type] Unclassified [Category] Staff [Closing Date] Until Filled [FT/PT]

Output: Part Time

Job Opening Details - Pittsburg State University


Input: [Job Title] Full-time Temporary Instructor- Automotive Technology [Office] Automotive Technology [Job Type] Unclassified [Category] Faculty [Closing Date] Until Filled [FT/PT]

Output: Full Time

Job Opening Details - Pittsburg State University


Input: [Job Title] Adjunct Instructor-Fall 2015-Automotive Technology [Office] Automotive Technology [Job Type] Unclassified [Category] Faculty [Closing Date] Until Filled [FT/PT]

Output: Part Time

Job Opening Details - Pittsburg State University


Input: [remedy] META.yml does not conform to any recognised META.yml Spec. Take a look at the META.yml Spec at http://module-build.sourceforge.net/META-spec-v1.4.html (for version 1.4) or http://search.cpan.org/perldoc?CPAN::Meta::Spec (for version 2), and change your META.yml accordingly. [metric]

Output: meta yml conforms to known spec


Input: [remedy] This distribution has dot underscore files which may cause various problems. If you use Mac OS X, set COPYFILE_DISABLE (for OS 10.5 and better) or COPY_EXTENDED_ATTRIBUTES_DISABLE (for OS 10.4) environmental variable to true to exclude dot underscore files from a distribution. [metric]

Output: no dot underscore files


Input: [remedy] This distribution does not have a license defined in the documentation or in a file called LICENSE Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution. [metric]

Output: has human readable license


Input: [remedy] Does not have license information in any of its source files Add =head1 LICENSE and the text of the license to the main module in your code. [metric]

Output: has license in source file


Input: [remedy] MANIFEST does not match the contents of this distribution. Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually. [metric]

Output: manifest matches dist


Input: [remedy] This distribution does not 'use strict;' (or its equivalents) in all of its modules. Note that this is not about the actual strictness of the modules. It's bad if nobody can tell whether the modules are strictly written or not, without reading the source code of your favorite clever module that actually enforces strictness. In other words, it's bad if someone feels the need to add 'use strict' to your modules. Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written. [metric]

Output: use strict


Input: [remedy] This distribution uses a module or a dist that's not listed as a prerequisite. List all used modules in META.yml requires [metric]

Output: prereq matches use


Input: [Dark] Dark [Artsy] Not Artsy or Stylish [The Goth Girl] The Brooding Poet [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Dark [Artsy] Stylish [The Goth Girl] The Mistress [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Not Dark or Light [Artsy] Artsy [The Goth Girl] The Hippie Chick [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Not Dark or Light [Artsy] Not Artsy or Stylish [The Goth Girl] The Hot Friend [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Not Dark or Light [Artsy] Stylish [The Goth Girl] The Sorority Girl [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Light [Artsy] Artsy [The Goth Girl] The Actress [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Light [Artsy] Not Artsy or Stylish [The Goth Girl] Your Friend's Sister [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Light [Artsy] Stylish [The Goth Girl] The Prom Queen [Sexy]

Output: Sexy

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Dark [Artsy] Artsy [The Goth Girl] The Suicide Girl [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Dark [Artsy] Not Artsy or Stylish [The Goth Girl] The Bad Girl [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Dark [Artsy] Stylish [The Goth Girl] The Bettie Page Girl [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Not Dark or Light [Artsy] Artsy [The Goth Girl] The Art Student [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Not Dark or Light [Artsy] Not Artsy or Stylish [The Goth Girl] The Girl Next Door [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Not Dark or Light [Artsy] Stylish [The Goth Girl] The Debutante [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Light [Artsy] Artsy [The Goth Girl] The New Age chick [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Light [Artsy] Not Artsy or Stylish [The Goth Girl] The Favorite Friend [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [Dark] Light [Artsy] Stylish [The Goth Girl] The Cheerleader [Sexy]

Output: Cute

Take The Your Type of Girl Test | OkCupid


Input: [1] 73 [Most Commented]

Output: OLD MACDONALD’S SMARM

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] 66 [Most Commented]

Output: FOREVER IN THE PAST

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] 63 [Most Commented]

Output: DOMINANT INVADER LASHES OUT

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] 55 [Most Commented]

Output: NATION HORRIFIED BY EVERYTHING

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] 53 [Most Commented]

Output: HE HAS LODGED A COMPLAINT

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] 44 [Most Commented]

Output: SHARING CARING

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] 36 [Most Commented]

Output: A MINNESOTA DENTIST DID IT

BALACLAVA OF PEACE | Daily Telegraph Tim Blair Blog


Input: [1] bus [2] fill [3] Boyd [4] side [5] off [6] fish [7] beg [8] heat [9] fell [10] dad [11] key [12] hate [13] bath [14] tie [15] house [16] hit [17] on [18] duck [19] full [20] cow [21] mice [23] go [24] choice [25] pest [26] heed [27] tape [22]

Output: sock

**Please do not duplicate without permission**


Input: [1] height [2] big [3] head [4] Kay [5] bad [6] set [7] heed [8] fast [9] eyes [10] aid [11] kid [12] bike [13] south [14] cough [15] bug [16] fight [17] cab [18] fool [19] shop [20] suit [21] goat [23] oat [24] boy [25] up [26] hid [27] awed [22]

Output: heard

**Please do not duplicate without permission**


Input: [0] Word [1] night [2] down [3] bag [4] egg [5] face [6] say [7] sit [8] mad [9] hide [10] pin [11] Ett [12] other [13] dog [14] mouse [15] mess [16] caught [17] tight [18] had [19] hot [20] life [21] dull [23] bee [24] Hode [25] food [26] past [27] spice [22]

Output: who�d

**Please do not duplicate without permission**


Input: [0] List [1] how�d [2] toast [3] best [4] hut [5] beat [6] spike [7] sat [8] out [9] right [10] paw [11] miss [12] sad [13] hood [14] talk [15] now [16] fur [17] nice [18] job [19] nut [20] day [21] school [23] noise [24] take [25] ought [26] vice [27] time [22]

Output: father

**Please do not duplicate without permission**


Input: [1] good [2] left [3] Hoyt [4] bait [5] park [6] pen [7] bowl [8] home [9] moss [10] tore [11] dawn [12] back [13] pa [14] bone [15] family [16] pipe [17] Hudd [18] dew [19] toy [20] rider [21] son [23] zoo [24] put [25] hall [26] voice [27] tongue [22]

Output: cot

**Please do not duplicate without permission**


Input: [1] move [2] dead [3] car [4] boat [5] goal [6] cook [7] toe [8] do [9] see [10] fan [11] hurt [12] sort [13] funny [14] pal [15] foot [16] mouth [17] bite [18] Don [19] sky [20] hoot [21] chew [23] door [24] moist [25] ton [26] tour [27] type [22]

Output: odd

**Please do not duplicate without permission**


Input: [Number] 25-15 [Office] ANM-111 [Date] 11-20-1989 [Title]

Output: Approval of Flight Management Systems in Transport Category Airplanes This advisory circular (AC) provides guidance material for the airworthiness approval of flight management systems (FMS) in transport category airplanes. Like all AC material, this AC is not mandatory and does not constitute a regulation. It is issued for guidance purposes and to outline a method of compliance with the rules. In lieu of following this method without deviation, the applicant may elect to follow an alternate method, provided the alternate method is also found by the Federal Aviation Administration (FAA) to be an acceptable means of complying with the requirements of Part 25. Because the method of compliance presented in this AC is not mandatory, the terms "shall" and "must" used herein apply only to an applicant who chooses to follow this particular method without deviation.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-16 [Office] ANM-111 [Date] 09-25-1987 [Title]

Output: Electrical Fault and Fire Prevention and Protection This advisory circular (AC) provides information on electrically caused faults, overheat, smoke, and fire in transport category airplanes. Acceptable means are provided to minimize the potential for these conditions to occur, and to minimize or contain their effects when they do occur. These means are not mandatory. An applicant may elect to use any other means found to be acceptable by the Federal Aviation Administration for compliance with the Federal Aviation Regulations (FAR).

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-20 [Office] ANM-111 [Date] 09-10-1996 [Title]

Output: Pressurization, Ventilation and Oxygen Systems Assessment for Subsonic Flight including High Altitude Operation Provides guidance on methods of compliance with the requirements of part 25 of the Federal Aviation Regulations pertaining to pressurization, ventilation, and oxygen systems, especially as they pertain to high altitude subsonic flight. As with all AC material, it is not mandatory and does not constitute a regulation. The applicant may elect to follow alternate methods provided that these methods are also found by the FAA to be an acceptable means of complying with the requirements of part 25. Because the guidance on the methods of compliance presented in this AC are not mandatory, the terms "shall" and "must" when used herein, apply only to an applicant that chooses to follow a particular method without deviation.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1302-1 [Office] ANM-111 [Date] 05-03-2013 [Title]

Output: Installed Systems and Equipment for Use by the Flightcrew This advisory circular (AC) provides guidance for the design and methods of compliance for installed equipment on transport airplanes intended for use by the flightcrew. The guidance provided by this AC is intended to minimize the occurrence of design-related errors by the flightcrew and to enable the flightcrew to detect and manage errors that do occur. This AC provides recommendations for the design and evaluation of controls, displays, system behavior, and system integration that are all part of human factors considerations. AH Bahrami

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1523-1 [Office] ANM-111 [Date] 02-02-1993 [Title]

Output: Minimum Flightcrew Sets forth a method of compliance with the requirements of Section 25.1523 of the FAR, which contains the certification requirements for minimum flight crew on transport category airplanes.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.703-1 [Office] ANM-111 [Date] 03-17-1993 [Title]

Output: Takeoff Configuration Warning Systems Provides guidance for the certification of takeoff configuration warning systems installed in transport category airplanes.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.773-1 [Office] ANM-111 [Date] 01-08-1993 [Title]

Output: Pilot Compartment View Design Considerations Provides guidance for demonstrating compliance with the airworthiness standards for transport category airplanes pertaining to pilot compartment view. These criteria include the properties of transport materials necessary to assure adequate visibility from the flight deck.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.672-1 [Office] ANM-110B [Date] 11-15-1983 [Title]

Output: Active Flight Controls Sets forth an equivalent means of complying with the provisions of Part 25 of the Federal Aviation Regulations (FAR) pertaining to the certification requirements of active flight controls. The procedures set forth herein apply to load alleviation systems (SAS), and flutter suppression systems (FSS). These procedures provide compliance with Part 25 under the equivalent safety provisions of Section 21.21(b)(1) in addition to compliance with the applicable sections of Part 25.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1457-1A [Office] ANM-110A [Date] 11-03-1969 [Title]

Output: Cockpit Voice Recorder Installations Sets forth one acceptable means of compliance with provisions of FAR 25.1457 (b), (e), and (f) pertaining to area microphones, cockpit voice recorder location, and erasure features.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.253-1A [Office] ANM-110A [Date] 12-27-1976 [Title]

Output: High-Speed Characteristics Sets forth an acceptable means, but not the only means, by which compliance may be shown with FAR 25.253 during certification flight tests.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-7C [Office] ANM-110 [Date] 10-16-2012 [Title]

Output: Flight Test Guide For Certification Of Transport Category Airplanes This advisory circular (AC) provides guidance for the flight test evaluation of transport category airplanes. This AC includes flight test methods and procedures to show compliance with the regulations contained in subpart B of Title 14, Code of Federal Regulations (14 CFR) part 25, which address airplane performance and handling characteristics. This revision, AC 25-7C, is a complete revision to reduce the number of differences from the European Aviation Safety Agency’s Flight Test Guide, provide acceptable means of compliance for the regulatory changes associated with amendments 107, 109, 113, 115, 119, and 123 to part 25, respond to National Transportation Safety Board recommendations, and to provide a general update to reflect current FAA and industry practices and policies.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-12 [Office] ANM-110 [Date] 11-02-1987 [Title]

Output: Airworthiness Criteria for the Approval of Airborne Windshear Warning Systems in Transport Category This advisory circular (AC) provides guidance for the airworthiness approval of airborne windshear warning systems in transport category airplanes. Like all advisory circular material, this advisory circular is not, in itself, mandatory and does not constitute a regulation. It is issued for guidance purposes and to outline a method of compliance with the rules. In lieu of following this method without deviation, the applicant may elect to follow an alternate method, provided the alternate method is also found by the Federal Aviation Administration (FAA) to be an acceptable means of complying with the requirements of Part 25 of the Federal Aviation Regulations (FAR). Because the method of compliance presented in this AC is not mandatory, the terms "shall" and "must" used in this AC apply only to an applicant who chooses to follow this particular method without deviation.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-21 [Office] ANM-110 [Date] 09-01-1999 [Title]

Output: Certification of Transport Airplane Structure Provides guidance to airplane manufacturers, modifiers, foreign regulatory authorities, and FAA transport airplane type certification engineers and their designees.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-25A [Office] ANM-110 [Date] 10-27-2014 [Title]

Output: Performance and Handling Characteristics in Icing Conditions This advisory circular describes an acceptable means of showing compliance with the airplane performance and handling characteristics certification requirements for flight in the icing conditions defined in Appendices C and 0 of Title 14, Code of Federal Regulations part 25.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-28 [Office] ANM-110 [Date] 10-27-2014 [Title]

Output: Compliance of Transport Category Airplanes with Certification Requirements for Flight in Icing Conditions This advisory circular (AC) describes an acceptable means of showing compliance with the supercooled large drop condition requirements of § 25.773, Pilot compartment view, § 25.1323, Airspeed indicating system, § 25.1324 Angle of attack system and § 25.1325, Static pressure system, as well as the requirements of § 25.1419, Ice protection, and § 25.1420, Supercooled large drop icing conditions, of Title 14, Code of Federal Regulations (14 CFR) part 25. Part 25 contains the certification requirements for transport category airplanes. The compliance means described in this document are intended as guidance. They are meant to supplement the engineering judgment that must form the basis of any compliance findings for the supercooled large drop icing conditions in §§ 25.773, 25.1323, 25.1324, and 25.1325, as well as the compliance findings for §§ 25.1419 and 25.1420.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25-869.1A [Office] ANM-110 [Date] 10-22-2007 [Title]

Output: Fire Protection Systems

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1329-1C [Office] ANM-110 [Date] 10-27-2014 [Title]

Output: Approval of Flight Guidance Systems This advisory circular (AC) describes an acceptable means for showing compliance with certain requirements of Title 14, Code of Federal Regulations (CFR) 25.1329, Flight guidance systems. While part 25 contains the airworthiness standards applicable to transport category airplanes, the guidance in this AC pertains to the functions of autopilots, flight directors, and automatic thrust control as well as any interactions with stability augmentation and trim functions. This revision incorporates minor changes associated with issuance of the final rule for Airplane and Engine Certification Requirements in Supercooled Large Drop, Mixed Phase, and Ice Crystal Icing Conditions.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1419-2 [Office] ANM-110 [Date] 10-27-2009 [Title]

Output: Compliance with the Ice Protection Requirements of §§ 25.1419(e), (f), (g), and (h) This advisory circular (AC) describes an acceptable means for showing compliance with the requirements of Title 14, Code of Federal Regulations (14 CFR), 25.1419(e), (f), (g), and (h), Ice protection. Part 25 contains the airworthiness standards applicable to transport category airplanes a. Installing a primary ice detection system; b. Developing visual cues and installing an advisory ice detection system to alert the flightcrew that the airframe ice protection system (IPS) must be activated; c. Identifying conditions conducive to airframe icing through the use of temperature and visible moisture cues; and d. Including in the airplane flight manual (AFM) procedures for activating and deactivating the airframe IPS.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1435-1 [Office] ANM-110 [Date] 05-21-2001 [Title]

Output: Hydraulic System Certification Tests and Analysis This advisory circular (AC) provides guidance material for use as an acceptable means, but not the only means, of demonstrating compliance with the airworthiness standards for transport category airplanes that contain hydraulic system requirements. It is not mandatory and does not constitute a regulation.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.1581-1 [Office] ANM-110 [Date] 07-14-1997 [Title]

Output: Airplane Flight Manual Identifies the information that must be provided in Airplane Flight Manual (AFM) under the airworthiness regulations and provides guidance as to the form and content of the approved portion of an AFM.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.335-1A [Office] ANM-110 [Date] 09-29-2000 [Title]

Output: Design Dive Speed Sets forth an acceptable means , but not the only means, of demonstrating compliance with the provisions of part 25 of the Federal Aviation Regulations (FAR) related to the minimum speed margin between design cruise speed and design dive speed for transport category airplanes.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.491-1 [Office] ANM-110 [Date] 10-20-2000 [Title]

Output: Taxi, Takeoff and Landing Roll Design Loads Sets forth acceptable methods of compliance with provisions of Part 25 of the FAR dealing with the certification requirements for taxi, takeoff, and landing roll design loads. Guidance information is provided for showing compliance with section 25.491 of the FAR relating to structural design for airplane operation on paved runways and taxiways normally used in commercial operations.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.562-1B [Office] ANM-110 [Date] 01-10-2006 [Title]

Output: Dynamic Evaluation of Seat Restraint Systems and Occupant Protection on Transport Airplanes Provides information and guidance regarding compliance with the provisions of Part 25 of the Federal Aviation Regulations applicable to dynamic testing of seats intended for use in transport category airplanes.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.723-1 [Office] ANM-110 [Date] 05-25-2001 [Title]

Output: Shock Absorption Tests This advisory circular (AC) sets forth an acceptable means, but not the only means, of demonstrating compliance with the provisions of part 25 of the Federal Aviation Regulations (FAR) related to the use of landing gear shock absorption tests and analyses to determine landing loads for transport category airplanes.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [Number] 25.775-1 [Office] ANM-110 [Date] 01-17-2003 [Title]

Output: Windows and Windshields Sets forth an acceptable means, but not the only means, of demonstrating compliance with the provisions of Title 14, Code of Federal Regulations (14 CFR) part 25 pertaining to the certification requirements for windshields, windows, and mounting structure. Guidance information is provided for showing compliance with § 25.775(d), relating to structural design of windshields and windows for airplanes with pressurized cabins. Terms used in this AC, such as “shall” or “must,” are used only in the sense of ensuring applicability of this particular method of compliance when the acceptable method of compliance described herein is used. Other methods of compliance with the requirements may be acceptable. While these guidelines are not mandatory, they are derived from extensive Federal Aviation Administration (FAA) and industry experience in determining compliance with 14 CFR. This AC does not change, create any additional, authorize changes in, or permit deviations from, regulatory requirements.

Advisory Circulars – Airworthiness Standards: Transport Category Airplanes

Search results


Input: [0] Min [2] Tot [3] Total rebounds [4] BS [5] Blocked shots [1]

Output: Minutes played


Input: [0] M/A [2] AS [3] Assists [4] Pts [5] Points [1]

Output: Made/Attempts


Input: [0] % [2] PF [3] Personal fouls [4] * [5] Starters [1]

Output: Shooting percentage


Input: [0] O [2] TO [3] Turnovers [4] DNP [5] Did Not Play [1]

Output: Offensive rebounds


Input: [0] D [2] ST [3] Steals [4] FG [5] Field Goals [1]

Output: Defensive rebounds


Input: [0] +/- [2] C [3] Committed fouls [4] D [5] Drawn fouls [1]

Output: Team's net points while on court


Input: [Type of Unit] Noise [Airwise Purifier] None [HEPA Filter] High [Electrostatic Filter] Medium [Ozone] Medium [Ionizer] None [UV]

Output: Medium

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Maintenance [Airwise Purifier] Low [HEPA Filter] Medium [Electrostatic Filter] High [Ozone] Medium [Ionizer] Low [UV]

Output: Low

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Reliability [Airwise Purifier] Excellent [HEPA Filter] Good [Electrostatic Filter] Good [Ozone] Poor [Ionizer] Good [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Mold [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Good [Ozone] Poor [Ionizer] Poor [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Bacteria [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Good [Ozone] Poor [Ionizer] Poor [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Dust Mites [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Poor [Ozone] Poor [Ionizer] Poor [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Gases [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Poor [Ozone] Good [Ionizer] Poor [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Odors [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Good [Ozone] Good [Ionizer] Good [UV]

Output: Poor

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Smoke [Airwise Purifier] Excellent [HEPA Filter] Good [Electrostatic Filter] Good [Ozone] Good [Ionizer] Excellent [UV]

Output: Poor

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] VOCs [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Poor [Ozone] Good [Ionizer] Poor [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Pet Dander [Airwise Purifier] Excellent [HEPA Filter] Good [Electrostatic Filter] Good [Ozone] Good [Ionizer] Good [UV]

Output: Good

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Large Particles, 0.3 - 10 micron [Airwise Purifier] Excellent [HEPA Filter] Good [Electrostatic Filter] Poor [Ozone] Poor [Ionizer] Excellent [UV]

Output: Poor

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Type of Unit] Small Particles, < .3 micron [Airwise Purifier] Excellent [HEPA Filter] Poor [Electrostatic Filter] Poor [Ozone] Poor [Ionizer] Good [UV]

Output: Poor

Airwise Purifier 2200 for Large Room - Healthy Hair Care - Personal Care


Input: [Powered by (Data Sources)] Student Interchange Web entry [Files/Entry Needed] Student Demographic file Student School Association file Web entry of score related data [Snapshot]

Output: 11th Grade Alternate Assessment


Input: [Powered by (Data Sources)] Staff Interchange [Files/Entry Needed] Staff Assignment file Staff Profile file [Snapshot]

Output: Human Resources


Input: [Powered by (Data Sources)] Participation List Student Interchange Teacher Student Data Link [Files/Entry Needed] MSP Participation List file Student Demographic file Student School Association file TSDL Course Enrollment file TSDL Course Instructor file [Snapshot]

Output: Math and Science Partnership


Input: [Powered by (Data Sources)] READ data file Student Interchange Student October Snapshot (for some districts) [Files/Entry Needed] READ data file Student Demographic file (for some districts) Student School Association file (for some districts) [Snapshot]

Output: READ


Input: [Powered by (Data Sources)] IEP Interchange Staff Interchange Student Interchange [Files/Entry Needed] Special Education Child file Special Education Participation file Staff Assignment file Staff Profile (Demographic) file Student Demographic file Student School Association file [Snapshot]

Output: Special Education December Count


Input: [Powered by (Data Sources)] Discipline Interchange IEP Interchange Student Interchange [Files/Entry Needed] Discipline Action file Discipline Incident file Special Education Participation file Student Demographic file Student School Association file [Snapshot]

Output: Special Education Discipline


Input: [Powered by (Data Sources)] Special Education IEP Interchange Student Interchange [Files/Entry Needed] Special Education Child file Special Education Participation file Special Education Student Parent Association file Student Demographic file (only certain fields from this file) Student School Association File (only grade level comes from this file) [Snapshot]

Output: Special Education End of Year


Input: [Powered by (Data Sources)] Special Education IEP Interchange Student Interchange Title I Interchange [Files/Entry Needed] Adjustment file (only required for adjustments) Advanced Course Completion file Special Education Participation file Student Demographic file Student School Association file Title I (only required for certain districts) [Snapshot]

Output: Student End of Year


Input: [Powered by (Data Sources)] Non-funded Home-based Education entry Student Interchange Title I Interchange [Files/Entry Needed] Non-Funded Home-Based Education entry (student counts entered by grade in Data Pipeline) Student Demographic file Student School Association file Title I (only required for certain districts) [Snapshot]

Output: Student October


Input: [Powered by (Data Sources)] TSDL Interchange [Files/Entry Needed] TSDL Course Enrollment file TSDL Course Instructor file [Snapshot]

Output: Teacher Student Data Link


Input: [Column 18] farm laborer [Column 18_2] commercial traveler [Column 19_3] dry goods [Column 19]

Output: working out

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] farm laborer [Column 18_2] salesman [Column 19_3] department store [Column 19]

Output: home farm

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] laborer [Column 18_2] bookkeeper [Column 19_3] department store [Column 19]

Output: odd jobs

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] laborer [Column 18_2] cash girl [Column 19_3] department store [Column 19]

Output: street work

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] laborer [Column 18_2] cashier [Column 19_3] department store [Column 19]

Output: garden

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] laborer [Column 18_2] cashier [Column 19_3] bank [Column 19]

Output: nursery

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] laborer [Column 18_2] conductor [Column 19_3] steam railroad [Column 19]

Output: railroad

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] brakeman [Column 18_2] conductor [Column 19_3] street car [Column 19]

Output: railroad

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] weaver [Column 18_2] farmer [Column 19_3] general farm [Column 19]

Output: cotton mill

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] laborer [Column 18_2] farmer [Column 19_3] truck farm [Column 19]

Output: cotton mill

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] doffer [Column 18_2] gardener [Column 19_3] private estates [Column 19]

Output: cotton mill

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] engineer [Column 18_2] lawyer [Column 19_3] general practice [Column 19]

Output: locomotive

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] engineer [Column 18_2] manager [Column 19_3] general farm [Column 19]

Output: lumber mill

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] fireman [Column 18_2] overseer [Column 19_3] truck farm [Column 19]

Output: lumber mill

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] fireman [Column 18_2] president [Column 19_3] life insurance co. [Column 19]

Output: fire department

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] civil engineer [Column 18_2] president [Column 19_3] bank [Column 19]

Output: general practice

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] electrical engineer [Column 18_2] superintendent steel works [Column 19_3] cotton mill [Column 19]

Output: street railway

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] carpenter [Column 18_2] foreman [Column 19_3] street [Column 19]

Output: car factory

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] carpenter [Column 18_2] newsboy [Column 19_3] store [Column 19]

Output: ship yard

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] carpenter [Column 18_2] newsdealer [Column 19_3] groceries [Column 19]

Output: house

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] blacksmith [Column 18_2] wagon driver [Column 19_3] express [Column 19]

Output: carriage factory

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] blacksmith [Column 18_2] wagon driver [Column 19_3] express wagon [Column 19]

Output: own shop

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] agent [Column 18_2] chauffeur [Column 19_3] private family [Column 19]

Output: real estate

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] agent [Column 18_2] chauffeur [Column 19_3] coal miner [Column 19]

Output: insurance

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] cook [Column 18_2] miner [Column 19_3] coal mine [Column 19]

Output: hotel

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] servant [Column 18_2] laborer [Column 19_3] marble [Column 19]

Output: private family

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] retail merchant [Column 18_2] quarryman [Column 19_3] house [Column 19]

Output: groceries

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Column 18] wholesale merchant [Column 18_2] janitor [Column 19]

Output: leather

Census Questionnaires and Instructions: 1790 to 2000 - Measuring America: The Decennial Censuses From 1790 to 2000 - Survey Census 1880 - Social Explorer


Input: [Contrasting Traits] Violet and White [Offspring Traits] Violet [Characteristics]

Output: Flower Colour

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Contrasting Traits] Axial and Terminal [Offspring Traits] Axial [Characteristics]

Output: Flower Position

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Contrasting Traits] Tall and Dwarf [Offspring Traits] Tall [Characteristics]

Output: Plant Height

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Contrasting Traits] Round and Wrinkled [Offspring Traits] Round [Characteristics]

Output: Seed Texture

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Contrasting Traits] Green and Yellow [Offspring Traits] Yellow [Characteristics]

Output: Seed Color

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Contrasting Traits] Inflated and Constricted [Offspring Traits] Inflated [Characteristics]

Output: Pea Pod Texture

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Contrasting Traits] Green and Yellow [Offspring Traits] Green [Characteristics]

Output: Pea Pod Color

Experiments on Plant Hybridization - Wikipedia, the free encyclopedia


Input: [Standard] 5 [Celestial] 50 [Membership Level]

Output: Number of Photos per Costume

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [Standard] 25 [Celestial] 100 [Membership Level]

Output: Number of Unsorted Photos Allowed

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [Standard] Original costumes, Non-Official Variations, Props [Celestial] No Restrictions [Membership Level]

Output: Costume Restrictions / Not Allowed

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [Standard] None [Celestial] Can mark costumes for sale Costumes for sale show up in search engine Can list commissions done for other people [Membership Level]

Output: Seller Features

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [Standard] None [Celestial] http://www.acparadise.com/loves/(NAME HERE) [Membership Level]

Output: Custom Cosplayer URL

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [Standard] None [Celestial] Less advertisements on cosplayer page Hit counters and statistics for photos and costumes Custom views for Cosplayer Page (Sort by most views, most comments, etc) VIP Section for Cosplayer Page - Add members to your VIP club, and you can post photos that are VIP only, and also send exclusive messages Construction Section for Costume Photos - Special section dedicated to construction or in-progress photos of your costumes. Enhanced Convention History Section and ability to post con reports Priority access for cosplay-related industry events [Membership Level]

Output: Other Features

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [Standard] Free [Celestial] $20.00 (ONE TIME ONLY, NO ANNUAL FEE) [Membership Level]

Output: Cost

American Cosplay Paradise - Donations and Sponsoring Cosplayers


Input: [int] int [CLIP_TO_PADDING_MASK] FOCUS_AFTER_DESCENDANTS

Output: This view will get focus only if none of its descendants want it.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] FOCUS_BEFORE_DESCENDANTS

Output: This view will get focus before any of its descendants.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] FOCUS_BLOCK_DESCENDANTS

Output: This view will block any of its descendants from getting focus, even if they are focusable.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] LAYOUT_MODE_CLIP_BOUNDS

Output: This constant is a layoutMode.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] LAYOUT_MODE_OPTICAL_BOUNDS

Output: This constant is a layoutMode.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] PERSISTENT_ALL_CACHES

Output: Used to indicate that all drawing caches should be kept in memory.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] PERSISTENT_ANIMATION_CACHE

Output: Used to indicate that the animation drawing cache should be kept in memory.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] PERSISTENT_NO_CACHE

Output: Used to indicate that no drawing cache should be kept in memory.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [int] int [CLIP_TO_PADDING_MASK] PERSISTENT_SCROLLING_CACHE

Output: Used to indicate that the scrolling drawing cache should be kept in memory.

We clip to padding when FLAG_CLIP_TO_PADDING and FLAG_PADDING_NOT_NULL are set at the same time.


Input: [Code] BLW1x [2] See details [Boat Class]

Output: U23 Lightweight Women's Single Sculls

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BLW2x [2] See details [Boat Class]

Output: U23 Lightweight Women's Double Sculls

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BLW4x [2] See details [Boat Class]

Output: U23 Lightweight Women's Quadruple Sculls

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BW1x [2] See details [Boat Class]

Output: U23 Women's Single Sculls

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BW2- [2] See details [Boat Class]

Output: U23 Women's Pair

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BW2x [2] See details [Boat Class]

Output: U23 Women's Double Sculls

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BW4- [2] See details [Boat Class]

Output: U23 Women's Four

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BW4x [2] See details [Boat Class]

Output: U23 Women's Quadruple Sculls

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [Code] BW8+ [2] See details [Boat Class]

Output: U23 Women's Eight

2014 World Rowing U23 Championships / Results - worldrowing.com


Input: [0] nominative [singular] gospa [plural]

Output: gospe


Input: [0] genitive [singular] gospe [plural]

Output: gospa


Input: [0] dative [singular] gospi [plural]

Output: gospama


Input: [0] accusative [singular] gospu [plural]

Output: gospe


Input: [0] vocative [singular] gospo [plural]

Output: gospe


Input: [0] locative [singular] gospi [plural]

Output: gospama


Input: [0] instrumental [singular] gospom [plural]

Output: gospama


Input: [Category] 27842 [Summary] Batch processing broken [Link]

Output: Administration


Input: [Category] 27844 [Summary] Version Module for Admin to show Joomla version in Footer admin Template [Link]

Output: Administration


Input: [Category] 27868 [Summary] Joomla 1.7.x batch processing allow move items to trashed categories [Link]

Output: Administration


Input: [Category] 27893 [Summary] New version module interferes with license notice in Hathor [Link]

Output: Administration


Input: [Category] 27941 [Summary] Add warning/no warning icons on Database screen [Link]

Output: Administration


Input: [Category] 27818 [Summary] Update 1.7 strings to 2.5 [Link]

Output: Code Quality


Input: [Category] 27829 [Summary] $app variable can possibly not be set causing a PHP error [Link]

Output: Code Quality


Input: [Category] 26986 [Summary] Batch processing of articles doesn't work for users with restricted rights [Link]

Output: Components


Input: [Category] 27581 [Summary] Basic Search contact search is broken [Link]

Output: Components


Input: [Category] 27700 [Summary] com_redirect redirects should use 301 redirect not 303 [Link]

Output: Components


Input: [Category] 27872 [Summary] Error in Banner Track Clicks [Link]

Output: Components


Input: [Category] 27886 [Summary] An unpublished linked contact leads to articles not being displayed. [Link]

Output: Components


Input: [Category] 27774 [Summary] Joomla on Windows Azure - Load time is slow [Link]

Output: Database


Input: [Category] 27890 [Summary] mod_menu invalid rendering of items of type alias and url [Link]

Output: Front End


Input: [Category] 27887 [Summary] Extension Manager: Database does not fix update problem [Link]

Output: Installation


Input: [Category] 27895 [Summary] Version Number Module Not Assigned to Menus [Link]

Output: Installation


Input: [Category] 27916 [Summary] Path of home sub-menu items contain "News Feeds" [Link]

Output: Installation


Input: [Category] 27919 [Summary] Extension Manager: Database does not fix text filter problem [Link]

Output: Installation


Input: [Category] 27920 [Summary] Update SQL query requires temp table permissions [Link]

Output: Installation


Input: [Category] 27880 [Summary] Please first make a selection from the lis't: Huge error on 40+ sites [Link]

Output: Javascript


Input: [Category] 27905 [Summary] Upgrade MooTools to version 1.4.3 [Link]

Output: Javascript


Input: [Category] 27796 [Summary] COM_USERS_FITLER_NOTES [Link]

Output: Languages


Input: [Category] 27929 [Summary] *Installing sample data and defining as site lang another lang then English breaks links [Link]

Output: Languages


Input: [Category] 27864 [Summary] User profile page does not HTML escape the user's name [Link]

Output: Layouts


Input: [Category] 27873 [Summary] The related articles modules (mod_related_items) are not showing [Link]

Output: Modules


Input: [Category] 27896 [Summary] mod_search head search link title not escaped [Link]

Output: Modules


Input: [Category] 27662 [Summary] Can't update #__update_sites table at extension install on SQL Server [Link]

Output: Plugins


Input: [Category] 27862 [Summary] Code error plgUserProfile line 188 [Link]

Output: Plugins


Input: [Category] 27885 [Summary] TinyMCE settings in SQL don't reflect recent changes in options. [Link]

Output: SQL Files


Input: [Category] 27938 [Summary] labels missing for Smart Search / Finder module [Link]

Output: Templates


Input: [0] affable [1] depraved [3] slope [2]

Output: meal


Input: [0] awkward [1] ditch [3] slow [2]

Output: mild


Input: [0] beautiful [1] easy [3] stage [2]

Output: oats


Input: [0] benign [1] elegant [3] suave [2]

Output: ramp


Input: [0] bowl [1] fitness [3] tact [2]

Output: rank


Input: [0] canal [1] goof [3] trade [2]

Output: rice


Input: [0] charm [1] grit [3] ugly [2]

Output: scale


Input: [0] civil [1] happy [3] unite [2]

Output: select


Input: [0] corn [1] incline [3] west [2]

Output: shelf


Input: [0] cruel [1] kind [3] will [2]

Output: slender


Input: [0] degree [1] luck [2]

Output: slight


Input: [Category] Concurrency Management [Description] You can rework the SvcUtil or VS generated proxy so that the same proxy will offer both synchronous and asynchronous calls. To download demonstrates the required code changes, as well as where to place the fault contracts. [Last Updated] 9/7/2006 [Title]

Output: Asynchronous and Synchronous calls

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] WCF offers a the client a facility for dispatching calls to the service asynchronously. This is strictly a client-side feature, and the service itself is completely unaware that it is being called asynchronously. The client obviously needs a way to be notified when the calls complete and be able to harvest returned values or catch exceptions. All that is doe using a simple directive to SvcUtil: the /asyc switch that generates an asynchronous proxy. The download contains a sample asynchronous and synchronous proxy and a matching client, that uses a complete method to be notified when the call returns. [Last Updated] 7/30/2007 [Title]

Output: Asynchronous calls

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] By default WCF will not let a service callback within a service operation to its clients. The reason is that by default the service uses single-threaded access – only one client is allowed to call it at a time. If the service were to allow to call back to its client it could result with a deadlock if the client will call to the service as a result of the callback to the client. To allow callbacks, you need to configure the service for reentrancy – that is, release the lock before the callback, as show in the demo. [Last Updated] 9/7/2006 [Title]

Output: Callbacks and Reentrancy

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] The solution demonstrates IDesign CallbackThreadAffinityBehavior - a custom endpoint behavior attribute that makes all callback instances (regardless of the worker threads used for the callbacks) execute on the same thread. The attribute uses IDesign custom .NET 2.0 synchronization context that always marshals the calls to the same thread. This is instrumental is advanced cases such as thread local storage and COM interop as well as advanced synchronization needs. [Last Updated] 2/24/2007 [Title]

Output: Callbacks thread Affinity Attribute

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] By default, WCF calls execute in the order received by the service. This solution contains CallsPriorityBehavior attribute - a custom attribute that relies on a custom synchronization context, which marshals the calls to a pool of threads. The calls are sorted based on priority, then executed. The client provides the priority to the proxy constructor. [Last Updated] 10/21/2007 [Title]

Output: Calls Priority Attribute

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] Instead of having a service update a form, how about making the form itself the service? The solution demonstrates IDesign FormHost - an abstract class that simply by deriving from it makes your Windows Forms form a WCF singleton. [Last Updated] 2/28/2007 [Title]

Output: Form Host

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] When a service needs to update UI, if the service is not using the UI synchronization context, the service must manually marshal the call (which comes in on a worker thread) to the UI thread. The easiest way of doing that is using an anonymous method and a synchronization context, as shown in the download. [Last Updated] 1/9/2007 [Title]

Output: Manual UI Updates

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] You can quite easily have your service update some UI on the host side. All you have to do is open the host on the UI thread after establishing the Windows Forms synchronization context. In fact, nothing prevent you from having multiple UI threads, each with its own set of Forms and services, as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Multiple UI Threads

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] While the main motivation for reentrancy configuration is callbacks, it has its use in with cyclic calling: Service A calling B calling C calling back into A. Without reentrancy this would mean a deadlock, as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Reentrancy

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] by default, the completion callback of an asynchronous WCF call comes in on a thread from the thread pool. If the callback needs to execute on a particular thread (such as updating the UI with Windows Forms), you must marshal the call. The solution is IDesign's AsyncClientBase proxy base class, that will automatically marshal the call to the client synchronization context (if present). [Last Updated] 7/15/2007 [Title]

Output: Safe Asynchronous Calls

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] Calls enter the service on worker threads. If the service needs to update Windows Forms forms and controls, it must marshal the update to the UI thread(s). Instead of using the synchronization context directly which serializes all calls to the service, you can use IDesign set of thread-safe Windows Forms controls - any service can access them as if running on the UI thread. This enables the same service to update multiple forms on multiple threads, and only marshal when necessary. [Last Updated] 9/7/2006 [Title]

Output: Safe Controls

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] By default, WCF will establish an affinity between the service host and the synchronization context it was created on. Since by default there is no synchronization context, client calls are services on arbitrary worker threads. The download contains IDesign custom .NET 2.0 synchronization context that always marshals the calls to the same thread. By installing the custom synchronization context and then opening the host, all client calls are always routed to the same thread, thus establishing thread affinity between all instances and all endpoints of the service. [Last Updated] 9/7/2006 [Title]

Output: Thread Affinity

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] The solution demonstrates IDesign ThreadAffinityBehaviorAttribute - a custom service behavior attribute that makes all service instances (regardless of the service instance mode or concurrency mode) execute on the same thread. The attribute uses IDesign custom .NET 2.0 synchronization context that always marshals the calls to the same thread. This is instrumental in advanced cases such as thread local storage and COM interop as well as advanced synchronization needs such as when creating a window (or a popup window) to be updated by the service. [Last Updated] 10/21/2007 [Title]

Output: Thread Affinity Attribute

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] By default, WCF calls execute on threads from the I/O completion ports thread pool. For some high-end scenarios, you may want to allocate a dedicated pool of threads to all calls of your service. This solution contains the ThreadPoolBehavior attribute which lets you specify the size of that pool. A pool size of one will generate thread affinity. The technique used here is a custom synchronization context that marshals all incoming calls to the dedicated pool of threads. [Last Updated] 10/21/2007 [Title]

Output: Thread Pool Attribute

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] The download contains an interesting concept – a service that acts like a timer, calling back to its clients on requested intervals. The service actually uses the .NET timer and delegates, and is a nice demo of how to bridge the two technologies - the timer delegates and the WCF callbacks. In addition, it demonstrates WCF ability to marshal the callbacks correctly to the UI thread the client it running on. [Last Updated] 9/7/2006 [Title]

Output: Timer Service and UI callbacks

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] By default callbacks enter the client on worker threads. If the client is a Windows Forms object, you must marshal the calls to the UI thread. By default this is exactly what WCF will do if the client is a Windows Forms form. But if the client uses a worker thread to dispatch the calls, there will be no marshaling. The client may do so to avoid a deadlock if the service tries to call back during a service call. The download shows such a client that uses its own synchronization context to post messages back to its own UI thread to process the callbacks and avoid a deadlock. [Last Updated] 9/7/2006 [Title]

Output: UI Client and Worker Thread Callbacks

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Concurrency Management [Description] When callbacks enter the client, they do so on a worker thread. If the callback object is a Windows Forms object, that worker thread cannot access the form directly, and instead, the call must be marshaled to the UI thread. Fortunately, WCF can do that automatically for you. Simply call the proxy on the UI thread, and the callback will be marshaled to the UI thread in turn. The download demonstrates this behavior. [Last Updated] 9/7/2006 [Title]

Output: Windows Forms and Callbacks

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Contracts [Description] While C# and VB will let you overload interface methods, by default, WCF will not let you overload contract operations. However, using simple aliasing you could provide both the service and the client the overloaded programming model, as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Contract Overloading

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Contracts [Description] The MetadataHelper class provided for a runtime way of parsing and querying the contracts of a running service. It allows the client to find out programmatically if the service supports a specified contract, it obtains all contracts of a running service, or the operations of a specified contract. These powerful and useful features are often required during setup or in administration applications and tools. [Last Updated] 9/7/2006 [Title]

Output: Metadata Helper

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Contracts [Description] On the service side, WCF lets you define and use a contract hierarchy simply by applying the ServiceContract attribute at every level of the interface hierarchy, deriving and implementing it. The service can even expose a single endpoint for all contracts. However, the imported metadata definitions on the client side do not maintain the interface hierarchy. The solution shows the simple steps required to rework the client side definitions to reflect correctly the contract hierarchy and maintain an is-a relationship between the imported contracts. [Last Updated] 9/7/2006 [Title]

Output: Service Contract Inheritance

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Contracts [Description] Even after reworking the imported definitions of a contract hierarchy, you still have a single proxy class. You can however have the client use a hierarchy of proxies that provided an is-a relationship between the proxies, yielding a much smoother programming model. The solution demonstrates this technique we call proxy-chaining. [Last Updated] 9/7/2006 [Title]

Output: Service Contract Inheritance with proxy chaining

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] When serializing a data contract type into or from a service operation, the compiler will gladly let you pass in a sub class of the data type. However, this will by default fail the call because WCF will not know how to serialize or deserialize the sub class. For that, you have to apply the KnownTypeAttribute at the proxy or contract level, as show in The download. You will also need to apply the attribute on the service side if the service needs to return matching sub classes. [Last Updated] 9/7/2006 [Title]

Output: Class Hierarchy

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] WCF will let the service define a contract that returns a custom collection. While you cannot share the definition of the custom collection across the service boundary, you can apply the CollectionDataContract attribute to have it exposed to the client as a custom generic list, as shown in The download. [Last Updated] 9/7/2006 [Title]

Output: Custom Collection

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] While the default behavior of a data contract type is to simply ignore extraneous unexpected members, you can instruct it to still store and pass it along to and from the service by implementing IExtensibleDataObject. This enables a round-trip scenario, where a new client is calling an old service with the new data contract, and the service can even pass the data contract unaffected to another service or client, as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Data Extensions and Round Trip

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] The download demonstrates WCF ability to use ADO.NET data tables as-is in operation parameters. You can even use type-safe data tables, and the imported proxy file contains an imported data table definition. You can remove that definition if the client has a local definition already of the table. [Last Updated] 9/7/2006 [Title]

Output: Data Tables

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] While WCF lets you freely pass ADO.NET data tables to and from a service, it is a questionable practice at best if the service needs to work with non-.NET clients. It is better in such cases to rerun the items in a neutral array. The solution demonstrates the use of the IDesign helper class DataTableHelper which converts the table to an array. [Last Updated] 9/7/2006 [Title]

Output: Data Tables as arrays

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] The EnumMemberAttribute allows data contract developers to alias the values of an enum and even to omit them from the data contract, as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Enums

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] The WCF provided known type resolver requires dedicated coding for each and every sub class, and also to manually install the resolver on the host and the client. IDesign's generic resolver addresses all that, and to a large extent, makes the whole issue of known types simply go away. The generic resolver uses reflection to find all possible known types in all referenced assemblies and as long as the compiler allowed them, the resolver resolves it automatically. You can also instruct it to resolve only specific known types. On the service side, you can use the GenericResolverBehaviorAttribute to allow the service to accept any sub class of its data contracts. You can also use the AddGenericResolver() host extension method to attach the reso [Last Updated] 2/12/2011 [Title]

Output: Generic Resolver

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] With .NET 4.0, WCF provides for a simple programmatic way of resolving a known type issue. Whenever the serializer encounters a type it does not know how to resolve, allows the developer to resolve it at runtime by deriving from DataContractResolver and calling ResolveName() during deserialization to return the resolved type or TryResolveType() to return the name and namespace of a type being serialized. The demo shows how to implement such a resolver for a particular case. You will also see how to install the resolver on the host and the client sides. As you can see, it is very labor intensive. This issue is addressed with the Generic Resolver provided by IDesign. [Last Updated] 2/12/2011 [Title]

Output: Known Type Resolver

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] While you typically apply the KnownType attribute at design time to allow sub classes of your data contract, this is of no use when the client passes in a new sub type later on. You can compensate for that by including the known type information in the config file, as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Known Types in Config

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] When generating an equivalent data contract to an already existing one, it is insufficient to alias the type and the members. You also need to ensure that the order of serialization is maintained – first by class hierarchy then alphabetically. In case of a discrepancy, you can compensate by setting the Order property of the DataMember attribute as shown in the download. [Last Updated] 9/7/2006 [Title]

Output: Order and Equivalence

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Data Contracts [Description] WCF lets the client and the service version independently their definitions of the same data contract. If the client sends a type with a missing member the service expects, the missing member on the service side will be initialized to its default value. If the data type contains a member the service is unaware of, it will be silently ignored. In addition, WCF allows both sides to explicitly require a particular data member or else fail the call. The download contains three solutions demonstrating these behaviors. [Last Updated] 9/7/2006 [Title]

Output: Versioning

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Discovery [Description] The solution demonstrates several important points often used in conjunction with discovery. The service uses the standard MEX and discovery endpoints, as well as relying on the host to implement the discovery and metadata exchange endpoints. This means you have to explicitly add the default endpoints. The service also picks up an available TCP port on the fly, dynamically. The client uses two techniques to invoke the service. The first is regular discovery of the address while having a priori knowledge of the binding. The second is with the IDesign DiscoveryFactory, which first discovers the service metadata address, then obtains the metadata, and uses the address and the binding in the metadata to create the proxy. [Last Updated] 1/22/2010 [Title]

Output: Ad-hoc Discovery

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Discovery [Description] The demos shows how to configure all hosts in the process to automatically announce their state (Hello/Bye). The client uses the IDesign AnnouncementSink<T> to receive the announcements. While AnnouncementSink<T> hosts internally an instance of AnnouncementService, it improves on its deficiencies. First, AnnouncementSink<T> offers two event delegates for notifications. Unlike the raw AnnouncementService, AnnouncementSink<T> fires these delegates concurrently. In addition, AnnouncementSink<T> disables the synchronization context affinity of AnnouncementService, so that it can accept the announcements on any incoming thread, making it truly concurrent. AnnouncementSink<T> filters the contract types and only fires its events when compatible en... [Last Updated] 1/22/2010 [Title]

Output: Announcements

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Discovery [Description] If the service knows the clients will use discovery, then there is no need to deploy the service pre-configured ports or pipes. The host can simply pick up any available port or pipe on the fly, at runtime. This is exactly what you can do with the IDesign helper class DiscoveryHelper and its properties AvailableTcpBaseAddress and AvailableIcpBaseAddress. provide those to the host as base addresses and enable discovery. [Last Updated] 1/22/2010 [Title]

Output: Dynamic Addresses

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Discovery [Description] Using raw duplex for events couples the publishers to the subscribers. They each have to know where the other is, both have to be running to publish or receive events, subscribers cannot subscribe to a type of event, and publishers cannot broadcast an event to subscribers they do not know about. The publish-subscribe design pattern decouples the publishers from the subscribers by introducing a dedicated subscription service and a dedicated publishing service in between. You can also have transient subscribes which are live subscribers using callbacks and persistent subscribers which are services to invoke like any other service, and can even be not-running. The download contains IDesign framework for implementing in only a few lines of code [Last Updated] 1/22/2010 [Title]

Output: Publish-Subscribe Framework

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Discovery [Description] A simple demonstrations of using scopes to filter on the discovered service endpoints. [Last Updated] 1/22/2010 [Title]

Output: Scopes

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Discovery [Description] With WCF 4.0, developers could leverage discovery for easy deployment and literally config file-free applications. Simply move the bits to the target machines and everything works. Discovery acts as the ultimate class factory, connecting clients to services. But WCF discovery uses UDP - a noisy unreliable protocol often blocked in many Enterprise environments. However, at the heart of all discovery mechanisms is the broadcasting of a query for available compatible services, and with the proper infrastructure you can substitute TCP for UDP. This download contains an alternative discovery technique based on TCP, along with the helper classes that streamline the discovery both on the client and the service side. The file demonstrates both plain discovery and announcements. You can use this as your own dynamic distributed configuration repository, deployed with one or two lines of code. [Last Updated] 6/23/2014 [Title]

Output: TCP-Based WCF Discovery

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] When calling ServiceHost.Close(), calls in progress are allowed to complete gracefully, and only future calls are denied. ServiceHost.Abort() on the other hand is an ungraceful exit, and it aborts calls in progress, resulting with an error on the client side. This simple demo lets you experiment with the differences between Close() and Abort(). [Last Updated] 9/7/2006 [Title]

Output: Aborting the Host

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] By default, the service host class creates the service instance in the same app domain as its caller. This solution contains the IDesign custom service host AppDomainHost that injects the service instance in a new app domain, thus better catering for fault and security isolation. [Last Updated] 10/21/2007 [Title]

Output: App Domain Host

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] With .NET 3.5, WCF provides three context bindings (BasicHttpContextBinding, NetTcpContextBinding, WSHttpContextBinding). These support a context protocol for passing custom parameters from the client to the service in the form of a dictionary of strings keys and values. This is a general technique for passing out-of-band parameters to the call, in effect giving the service a custom context, not unlike the other WCF contexts, such as transaction or security. Using the context binding on both sides requires intricate interaction with the operation context and the proxy. To automate, IDesign provides the ContextManager helper class which streamlines reading and writing into the context binding and ContextClientBase, which derives ClientBas [Last Updated] 10/30/2008 [Title]

Output: Context bindings as custom context

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] The solution contains an IDesign helper class called InProcFactory - a WCF factory designed to streamline and automate hosting services in the same process as the client. There is no need for any config file or programmatic calls to create the host or configure the binding. All the in-proc factory requires is the type of the service and the type of the requested contract. It is as close as you can get in WCF to the Win32 API of LoadLibrary() and it is the easiest way to shim up a class as a service instead of using the class as a traditional CLR class. [Last Updated] 2/24/2007 [Title]

Output: In-Proc Factory

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] WCF lets the service execute in the client’s process. This hosting mode is called In-Proc hosting. You should use named pipe binding, and you can even have a single config file for both the client and the host. This simple demo demonstrates in-proc hosting. [Last Updated] 9/7/2006 [Title]

Output: In-Proc Hosting

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] A WCF client can add into the message headers any custom information, and the service can in turn read those headers. Message headers are a general techniques for passing out-of-band parameters to the call, in effect giving the service a custom context, not unlike the other WCF contexts, such as transaction or security. Using the headers on both sides requires intricate interaction with the message, the operation context and the proxy. To automate, IDesign provides the GenericContext<T> helper class which streamlines reading and writing into the headers any custom context, and HeaderClientBase<T,H>, which derives IDesign's InterceptorClientBase<T> and automates passing the parameters from the client. The demo shows how to provide for a simp... [Last Updated] 10/30/2008 [Title]

Output: Message headers as custom context

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] The Metadata Explorer is a helper utility that visualizes the available service endpoints of a running service. This is done using metadata exchange - roughly the WCF equivalent of .NET reflection. Metadata contains not just contracts and operations but also information about security, transactions, reliability and faults. WCF makes it easy to programmatically query and discover the metadata of a service. The tool uses WCF's MetadataExchangeClient and MetadataImporter, and WsdlImporter to obtain and parse the metadata into endpoints. The Metadata Explorer tool simply visualizes the information returned and is very useful in seeing what a service has to offer without resorting to development tools. The tools also utilizes discovery, allowing [Last Updated] 1/9/2010 [Title]

Output: Metadata Explorer

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] A service is not limited to a single endpoint. As The download demonstrates, the service can have any number of embonpoints with any combination of addresses, bindings, and contracts. Similarity, the client can decide to consume a particular endpoint or all of them. The demo shows the required configuration on both the service and the client side. [Last Updated] 9/7/2006 [Title]

Output: Multiple Endpoints

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] While .NET 3.5 provides the NetTcpContextBinding, NetBasicHttpContextBinding and WSHttpContextBinding, it does not provide a matching support for IPC. IDesign rectifies this oversight by providing NetNamedPipeContextBinding. The demo shows both the steps required to implement such a custom binding, the supporting configuration-enabling types and also how to register it so that you could use it like the built-in binding in a config file. [Last Updated] 1/24/2009 [Title]

Output: NetNamedPipeContextBinding

IDesign: Excellence. Professional Growth. Leadership.


Input: [Category] Essentials [Description] Both the service and the client can use either a configuration file to list the endpoints and the related binding or behavior configuration or they can use programmatic calls to achieve the same effect. The solution contains a simple client and service that configure themselves programmatically. It is the same demo of the multiple endpoints only programmatically. [Last Updated] 2/24/2007 [Title]

Output: Programmatic Configuration

IDesign: Excellence. Professional Growth. Leadership.