text:
CAT-Tools/MemoQ/Wishlist

Actual wishes
For any problem and workaround see also the page CAT-Tools/MemoQ/Tips and Tricks. Please choose the appropriate section to add a wish.

General workflow

 * It would also be good if tags could be deleted at the translator's discretion. As the software now stands, the translator is not given full credit as an intelligent participant. If it really is not possible to delete unwanted tags, it would be nice if they were hidden in the source text as soon as Alt + F8 is pressed. Then the translator can focus on what matters and not be bothered by what doesn't. (Rod Walters)
 * Server Administrator, Server projects: Would it be possible to add a status feature here? E.g. in the form of colours that can be given to projects by right-clicking them in the overview pane (for example like the categorize feature in Microsoft Outlook). This would help in the workflow. You could give a project which has been translated but is pending feedback and possible changes from the client the colour red, and then change it to green once the project was completely finanlised. Green would then indicate that project was ready for updating/sending segments to a final/proofread TM. I suspect the possibility to categorize projects according to five different colours would be sufficient. No need to define categories/statuses for each colour; in that way people can use the colours to fit their specific workflow. (ditbal)
 * Reset format: a command (and shortcut) to reset a format of segments (bold/italic/underlined)

Propagation

 * Confirm without propagation: a command (and shortcut) to confirm a segment without propagation (if propagation is enabled)
 * The settings for auto-propagation should be specific to a project (instead of applying generally, as it is now) // tsca [re] 14:00, 18 July 2008 (UTC)
 * Conditional propagation: prompt user if subsequent segment is translated differently, empty, confirmed (like Trados Studio)
 * Propagation for comments: an option to propagate comments for repetitions so that a comment would be visible in all identical segments which were propagated

Statistics

 * Include name of analyzed file in Overview/Reports after performing statistics on single file from Translations
 * Show statistics history in Statistics window - an option to view previous statistics reports in Statistics window
 * Weighted word count - done in current version of memoQ
 * Automatic copy of statistics in project folder or at least a reminder/confirmation before closing the statistics' windows (T. Rox)
 * [Automatic] saving intermediate reports - an option to measure hourly productivity by comparing different reports
 * Analysis percentages with decimal places - rounding everything down makes the percentages useless for character/word counts
 * Productivity measurement - a tool to measure how many words are translated/proofread per hour.
 * Translating time - similar to editing time (for each user role)
 * Options for setting up Editing time - inactive mouse, overlaid screen etc.
 * Customize columns in Statistics report - ability to rearrange and exclude columns (and add calculated columns)
 * Word count calculation in background - linguist has to wait for a long time while memoQ is counting statistics

Project management

 * Create project template from existing project or several projects (combining resources from them)
 * Assign role of translator/reviewer to the whole folder in the structure view
 * Remember which folders were collapsed in structure view when re-opening project
 * Assign the whole folder in structure view
 * Structure view by different attributes: show Structure view not only for folders by also for dates, file formats, translators etc.
 * Different profiles for translation and proofreading: an option to switch between proofreading and translating profile
 * Automatically open the last project: an option to open automatically the last project
 * Grouping and labeling documents in Project Home: an option to label and group document (creating folder structure) for batch tasks and filtering
 * Prioritizing of documents: an option to mark different priorities for processing
 * A quick way to open original: an option to open original document quickly; the translator often needs to look at the original to see the actual format in the native application since html preview is not perfect for certain files. Now the easiest way, if you are not sure about file path, is to go to "Translations," select document, click "details" panel, copy the import path, go to file explorer, and paste it; which is not very practical.
 * Hide/unhide TM/TB/project: an option to hide TM/TB/project having possibility to restore its visibility in resources
 * Profiles for creating projects: In general there are too many clicks necessary for creating a new server project. In a profile you could determine the source language, target languages, translator(s), project manager(s), etc. In a "normal" company the source language never changes, so why it has to be selected with every new project. There should also be a checkbox in order to use the file name as the project name, or it would be even better if the project name were defined through variables (project manager initials, date, running number, etc.). (Carsten) - memoQ 2014 has templates for projects
 * Password protection for the memoQ application: There should be a native way to password-protect memoQ with options such as simple password protection against children or novice users, and even advanced encryption of confidential projects.

Navigation

 * Bookmarks in order to quickly mark entries (e.g. in order to return quickly to the last edited segment after scrolling up and down in the text) (TilovdB)
 * Insert "Rich" Bookmarks in Translation file when several people do several tasks on the same document and on the same PC, allowing later review/proofreading of specific parts. Each BookMark could include information like : Who, did What (translation, proofreading, etc...), on Which part (X segments from A to B, representing Y source words), When, for How Long . This information could also be used later for project accounting purposes (on a larger project, who contributed in how many % to reach the goal) (MartinB)
 * Being able to click on hyperlinks to webpages and be sent to the page directly instead of having to highlight the link and copy it into the browser (Anette)
 * Go to original segment from translation results: an option to go to the original segment within the same project from translation results (e. g. a translator notices some errors in translation results and need to go to the original segment to correct it). Such feature exists in SDL Passolo.
 * Clickable repetition icon: clicking on the repetition icon in the document view allows to filter other repetitions of this segment in the document/project (e.g. show them in view pane).
 * Jump to view: an option that is opposite to "jump to" option in view (to go from document to view)
 * Easily maximize memoQ from taskbar memoQ is often stuck in the taskbar and refuses to be maximized; even alt+tab is useless. Sometimes the only option is to use Task Manager's "Bring to front." (Noticed in several Windows versions, such as Vista, 7, and 10)

Communication/Comments
Saving comments together with translations in TM Thanks to TMs, translators can save and reuse segment translations. However, when translators write a comment next to a translated segment, they need to type (or copy-paste) the comment manually again if the segment reappears later on in the project. If it were possible to save and reuse the comment together with the segment translation, the translator would save time. Moreover, the translation would be more consistent since the reviewer’s attention would systematically be caught each time the problematic segment appears. (MIPS-CAT)  Communication add-in for the translation manager As a translation manager it would be nice to have a communication window always open and always on top. Or put it into the task bar. If there several projects with documents into several languages, I would like to get an instant notification of a new chat entry or a forum thread. So can answer immediately. (Carsten)
 * Communication add-in
 * Email notification when somebody posts a message in the forum. Subscribe option for new messages. New posts will be sent to the user's email address which is stored in the user profile on the MemoQ server.
 * Possibility to delete messages (Carsten)
 * Comments function: possibility to export all comments made to a document (or project) to a file that can be edited and e.g., submitted to the client as queries. (ditbal)
 * Notepad to add notes for each project (in most cases to collect and forward them to the client) (T.Rox)
 * Status for comment: an option to set a status for comment (accepted, rejected, replied and user-defined lists with different statuses). An option for filter comments by its status
 * Tree-like structure for comments
 * Show comments in QA results
 * A flag for files with comments - a mark for files with comments to see in the file list which files have comments inside (without opening them)
 * Extra column for comments - a "comment view" - an option to see comments in a separate column
 * Navigation panel in Active comments tab - an option to go to the next/previous commented segments
 * Filter comments in Active comments tab - an option to filter comments by different attributes (user, date, category etc).
 * Change font size in Active comments tab
 * Filter comments by its category (error, warning, information, other)
 * Comments for the whole folder in structure view
 * Show number of comments in the status bar
 * Add comments to multiple segments at once

General QA

 * Different number of sentences in source and target": could help in detecting of partially translated segments
 * Several tabs "Resolve errors and warnings": currently each new QA closes the previous tab
 * Check for unchanged fuzzy matches
 * Log for all QA checks and spellchecks: logging of date&time for all checks (to see that the file was checked after the last change)
 * Skipping segments which are identical to source in QA: an option to skip segments which are identical to source during QA (except notice "identical to source")
 * Differences between translated segment and TM entry: an option to see a differences between translated segment and TM entry. It is very useful when proofreading in memoQ translations which were made externally in other CAT. Some segments in TM could have "approved status" and they should not be changed in translation. This feature would help to track such "illegal" changes
 * Check web-addresses: an option to check web-addresses (and recognize them as non-translatable)
 * Check ™, ®, ©, *, >, <, ≥, ±, +: an option to check whether both source and target have these characters
 * Check acronyms: an option to check acronyms (and recognize them as non-translatable)
 * Save sort order in QA results: memoQ always resets a sort order by table column in QA results when you change anything.
 * Identification of duplicated punctuation marks: double colon, double semicolon etc.
 * Check words before sign ® and TM: ensure that trademarks are not translated
 * Recognize chemical formulas
 * Detection of imperial measures: imperial measures are usually converted into metrical system so imperial measures in translation should generate a warning.

Reduction of false errors in QA

 * Source and target ends with different punctuation - exclude quotes and brackets from this check as it is always a false error

Spellchecking

 * Group identical spelling errors in QA report: an option to process all identical spelling errors together (skip etc).
 * Spellcheck in background: spellcheck takes quite a lot of time but confirmed segments could spellchecked in background to create an instant report.
 * Spellcheck all CAPS: an option to check spelling of words which are in all caps (frequency of spelling errors in all CAPS words is rather high).
 * Skip the whole segment: an option to skip not only one word but the whole segment during spellchecking. E. g. "Skip segment" button in spellchecker window.
 * Skip identical to source segments: an option not to check spelling in segments which are identical to source. Such segments are usually left in a source language and do not need to be checked.
 * QA report for spellcheck: right-click menu with options similar to spellchecker window in QA results table
 * Improve speed of spell checker (TilovdB)
 * Spellcheck TM: even if spellcheck is enabled for QA, memoQ now does not check spelling in TM
 * Instant creation of spellcheck report: if spellcheck is done in background, spellcheck QA report could be created immediately
 * Consider glossary terms as spellchecked: an option to skip TB entries during spellcheck considering them correct
 * Automatically add TB entries to spellchecker dictionary:

AutoCorrect

 * Make end of target segment punctuation equal to source: replace end punctuation mark in the target with the one from source segment
 * Autocapitalization for segments starting with tag: autocapitalization currently does not work if a segment starts with tag
 * Do not reapply autocapitalization if user undoes autocapitalization by Ctrl+Z
 * Smart rules for autocapitalization: do not apply after colon, semicolon or some other punctuation marks
 * Autocorrection of multiple spaces
 * Autodeletion of spaces at the end of the segment
 * Autocorrection of space to non-breaking space in special cases (between number and unit etc)

View

 * Renaming of views: an option to rename views rather then create them a new - this feature will be in the next version of memoQ
 * Defining the order of documents when gluing them together: an option to select an order of documents in a view composed of several documents (drag-n-drop would be fine).
 * Creating view from selected segments: an option to create view from segments selected in work area via right-click menu
 * Refresh view status: an option to refresh status of views (it is currently possible to refresh files only)
 * Create view from view: an option to create a view from other views rather than documents
 * Creating view from filtered segments: an option to create view from segments filtered in work area via right-click menu (or button on filter panel)
 * Creating view by dragging file onto tab "Views"

Filter/Sort

 * Filter segments with Patch Match (fuzzy match repair): they should be checked more careful
 * Filter segments "containing numbers": show segments which include at least 1 number to check numbers throughout the text - this can be done by enabling regex and filtering for \d
 * Filter "number only" segments and "excluding number only" segments: it is more comfortable to translate without number only segments
 * Reapply the last filter: an option to reapply the last filter
 * Templates and history for filters: an option to save templates and history for filters to use them by single click
 * Filtering segments by formatting: an option to filter segments by present of formatting (contain bold/italics)
 * Filtering segments by script: an option to filter segments by script (Latin, Arabic, etc.)
 * Filtering segments where target is identical to source: an option to filter segments where target is identical to source (it would be a good complement for QA which could find such segments)
 * Filtering documents by its status in Project Home: an option to filter documents by different status and properties (extension, degree of completeness, translated, proofed, size, name)
 * Inverting filter: an option to invert filter (to see hidden by filter segments and hide visible segments)
 * Filter all respective repetitions in the project (or file) by clicking on the repetition icon of segment
 * Filter/sort segments in view by file name: memoQ 2013 now shows file names in views; it would be useful to filter/sort segments in view by file name
 * Ask to restore filter when reopening file: an option to restore filter if file was closed when filter was used

Translation memory/Corpora

 * Block annoying matches from Muses: an option to block some undesirable matches from Muses (when memoQ offers the same wrong matches for predictive typing, I have to reject them again and again. What is about blocking some of them?)
 * Forbidden segments: an option to mark segments in TM as forbidden (similar to forbidden terms). It allows to leave such segments in TM for tracking purposes but excludes them from pretranslation.
 * Select TMs for pretranslation: an option to select TM for pretranslation in Pretranslate window (now I have to change TMs for the whole project)
 * Number and punctuation differences should be distinguished in pretranslation: This can be very useful if the translator is pressed for time, and the document has many matches with minor punctuation differences, such as extra spaces. Unfortunately, the "good match" option in Pretranslate makes no distinction between number and punctuation differences, which is crucial; while the translator should reasonably be able to automatically confirm 99% matches with only minor punctuation differences, 99% matches with number differences must be revised one by one to check whether memoQ has replaced numbers correctly. A simple checkbox such as "Ignore minor punctuation differences" next to the "exact match" radio button in Pretranslate dialog should solve this problem.
 * More options for TM-driven segmentation: such as an option to join a fourth and even a fifth segment (which can help in malformed documents with too many misplaced line breaks), and an option to perform only joining or only splitting for more control over segmentation
 * Subsegment confirming mode: when importing an Excel sheet on a cell-by-cell basis using the option "import linebreaks as inline tags," and we have the memoQ segment "Paragraph1  Paragraph2," it is useful to be able to confirm three translation units at once with the confirm shortcut depending on the   tag location: (1) the whole memoQ segment, (2) Pargraph1 subsegment, and (3) Paragraph2 subsegment. These should result in more future matches, and better fragment assembly.
 * Fixing the never stopping loading circle in corner of results pane noticed in memoQ 2015 7.8.52; it is very annoying for someone used to seeing it stop/disappear at scan completion in earlier versions.
 * Save segments with tracked changes in TM: show tracked changes in TM results to facilitate consistent editing
 * Show differences between translation in TM and document in compare control: to facilitate consistent editing of similar segments
 * Ranking of TMs like TBs: an option to rank TMs like TBs in memoQ 2013 R2
 * Penalizing all TMs except primary one: an option to add penalties to all TMs except primary one (it is easier than add penalties for each TM separately)
 * Transferring context information between TM: moving context data between TM to get 101% matches.
 * Colour-coding to distinguish between exact and fuzzy matches in the Translation Results window and in the translation grid after e.g. pretranslation. (Grzegorz Harbaszewski)
 * Merging 2 or more TMs: an option to merge 2 or more TMs with one command taking into account meta-data (without import/export by mean of tmx)
 * Locked segments in TM: an option to protect some segments from editing in TM.
 * Show penalties in meta-information area: an option to show TM's penalties in meta-information area.
 * Plug-in for using Trados TMs directly: an option to connect to Trados TMs.
 * Select several TMX for import - it is not possible to select more than 1 TMX-file to import into TM
 * Highlight segment attributes in Meta-information box - highlight segment attributes that match the current project (it will help promptly recognize TM segments created in the current project or which are very similar to current project). Ideally it should be customizable to highlight segments made within particular time/date range etc.
 * TM maintenance - automatically delete number-only segments from TM
 * Show which TBs and TMs are associated to projects: When moving or deleting a TB or TM it would be convenient to know in which projects the TB or TM is used. (Carsten)
 * Elimination of duplicates (same target, same source) from termbases and translation memory (David Turner) - current memoQ version can identify duplicates but can not clean them automatically
 * Marking matches that require only deletion of contiguous text: Sometimes a match ranked down the list is actually better than matches ranked higher because it has contiguous "blue" text and is more accurate; such matches (with contiguous "blue" text) should be marked clearly, e.g. with a "+" next to the match rate, when they are not the first on the list.
 * Revert patch matches: button/short cut/right click menu to revert patch matches and get "normal" TM matches

Muses/Predictive Typing/Autopick

 * Block some words from Muses in Predictive typing: some incorrect variants are rather annoying when you have to delete them again and again.
 * Turn off Predictive typing when typing in the middle of word: if you need to correct a spelling error in the middle of word, predictive typing tries to insert the whole word. Such behavior is confusing.
 * Time delay for predictive typing: an option to set up a delay for displaying prompts
 * Exclude from predictive typing words which are already typed in the segment
 * Use content of active document/project for predictive typing: it is strange that memoQ does not offer words from segments translated above.
 * Turn off predictive typing when the word is mostly typed: predictive typing is not required for short words or when 1-3 letters are left
 * Predictive typing for numbers + units: it is logical to offer not only number but number + % sign (or localized units - mg, m, kg etc)
 * Turn off case-sensitive predictive typing: predictive typing currently does not work if you start typing word with capital letter which is entered into the glossary uncapitalized - case sensitivity option for predictive typing has been added in a recent update
 * Predictive typing for Machine Translation suggestions: it would be great if Predictive Typing could suggest full sentences, phrases, and words from various MT resources. Of course, the user could switch on/off the function.
 * Train Muse in background: this task could be done in background
 * Predictive typing for proper names: an incredibly useful feature, which would prevent translators from making spelling mistakes in proper names. Of course it wouldn't be faultless, but could be triggered by words starting with capital letters in a sentence.
 * Predictive typing/autopick for number ranges, formulas etc: it is more handy to insert ranges (or other group of numbers) rather than individual numbers
 * Show resources used to create Muses in their properties

Term base

 * A possibility to add extra columns
 * Define the order of the columns (e.g. Subject > column 3, Domain > column 1, Note > column 2, etc.)
 * Save the export setting so the user doesn't have to select, deselect, order, select TXT or CVS, or whatever setting the next time she exports.
 * Easy access to the term base for terminologists. In our case, terminologists are marketing people and developers. Neither of them is interested in foreign languages, translation memories, alignment functions, translation projects, etc. They just want to
 * enter and/or release terms in the source language
 * look up and/or export terms of any language.
 * Web based access to the terms (read-only would be sufficient for our needs). At the moment we use the Typo3 extension sg_dictionary which is enough. See http://www.rohloff.de/de/info/woerterbuch/english/index.html for an implementation at Rohloff (sorry, our dictionary access is password protected). (Carsten)
 * Ignore accents (e.g. recognize "categorie" for TB entry "catégorie" and "habitaciones" for "habitación" (Torsten)
 * A thing DéjàVu never offered, as an alternative for fuzzy term recognition: morphological reduction/recognition (language specific). First language to start with, (of course ;-)): German - So: Dictionary has 'Baum', in the text 'Baumes' (Genitiv), Baumes is recognized as Baum+es. (Transit offers this.) (Hans List)
 * MemoQ now stores it's dictionaries in a text file (we've discussed this), should be moved to a MySQL or MS Jet. DéjàVu users speak of big mama when they talk about terminology databases of 100 000 entries or more. They all use large databases that should work fast. (Hans List)
 * Context sensitive terminology recognition. Some kind of 3 dimensional terminology database. Example: If computer and Apple are in one segment, do not translate Apple (or: translate it with Apple). If Apple and Tree are in one segment, translate it with 'green fruit growing on a tree'. I know subject codes can help, but my suggestion is nicer. (Hans List)
 * Selecting TB entries to be exported. Instead of exporting the complete TB content, there could be a functionality to specify selected entries to be exported, for instance, all entries where the subject is "Finances" or "Project management". Such a functionality could also be helpful to quickly create a glossary intended for clients. A termbase is mainly intended to assist translators, but all terms would not be useful in a glossary. If I can mark some entries as "Glossary" and extract these specific entries, the creation and update process of client glossaries would be greatly enhanced. (Ariane)
 * Ability to add new fields, as for instance "Source" (F. Vidal)
 * Possibility of viewing and changing all termbases during translation. Right-click on term in results pane and change destination of term. Edit term in termbase and see a list of all termbases to choose from. (Anette)
 * It would also be very useful to be able to filter on things such as "case sensitivity" and "prefix matching" and "domain" ... so that we can fix things like double entries in our term bases, and edit/maintain them... That is, filtering on columns in the actual window that opens when we click on "edit" a term base, like in a spreadsheet, rather than having to use the confusing: Term Base -> Filter -> Filter and sorting interface, which I find rather unintuitive. (wordbook.nl)
 * Preferred terms: an option to mark a term as preferred. It could have a special icon in translation results. A preferred term could hide all other variants.
 * Join 2 terms entries via right click menu in translation results: currently it is not possible.
 * Being able to move a term from one termbase to another termbase in one click (Anette)
 * Add terms to TB from concordance window
 * Open TB for editing with double click - it does not work
 * arabterm.org plugin - English, French, German, Arabic
 * Show all variants of terms from TB when mouse is over highlighted term: currently only 1 variant is shown.
 * Ignore a list of stop words: They could be present in a term base converted from a full dictionary that has such words that the user cannot easily locate and delete. This could be an extension of the similar function used when extracting terms.
 * Indicating the source of term translation in the translation grid. The translator should be able to set an abbreviation for each termbase, which can be displayed next to the term translation in the tooltip. This way the translator will not have to waste time by clicking in the translation result pane to view the source of the term translation.
 * Distinct colors for different TMs. Suppose that there are two TMs available in a given translation project. While TM1 is only advisory, the terminology of TM2 has to be observed. In the source part of the translation grid, (sequences of) words belonging to TM2 are highlighted in red, (sequences of) words belonging to TM1 are highlighted in blue. This would ensure that translators do not overlook any important, fixed translation. Additionally translators would save time (cf. previous wish "no time wasted with looking for the source of the term translation"). (MIPS-CAT)
 * Exclude some terms from predictive typing - check-box "Exclude from predictive typing" on tab "Usage" of term editing window (some terms are for reference only and should not be inserted into translation)

Web search

 * Option to use mobile user agent: an option to use a mobile user agent, similar to the function of the "User Agent Switcher" add-on for Firefox; this enables loading light versions of many websites, i.e. faster and more efficient web search.
 * Option to load only one xpath: an option to easily define one xpath for loading, which removes distracting elements from webpages, and makes web search more stable. Defining the xpath should be easy, as in popular web scraping software.
 * Adding arabterm.org technical dictionary: English, French, German, Arabic
 * Adding Librairie du Liban Publishers dictionaries: several premium dictionaries are offered for free, involving the languages Arabic, English, French, German, and Spanish. The pairs with most results are English <-> Arabic, and French <-> Arabic. The URL is http://www.ldlp-dictionary.com.

Machine translation

 * Ability to set up MT correction rules: an option to set up simple and complex rules for the correction of MT results. This feature can be very useful when the source is repetitive, which may lead to repetitions of the same error in the MT results. e.g., a simple rule such as "always replace bishop with ceilings" can greatly improve the English MT result of an Arabic construction document since the Arabic word "أسقف" can mean either "ceilings" or "bishop." For complex rules, regex could be used.

Full support of high resolution displays (4K, 2160p, 3840 x 2160)

 * Fix of current bugs with UI: Find & Replace, edit of comments, reports etc. A lot of UI elements are not usable now.
 * UI is extremely slow on 4K displays: working with memoQ on 4K display is not comfortable

Translation memories panel

 * Customization of columns shown for TM properties : configure the number of shown columns for TM properties (project, client, domain etc). Now they are shown below for selected TM only.

Meta-data area

 * Hide/show meta information: to configure which meta-data are to be shown (moving of separation bar is not flexible enough)

Translation result window
Setting up the number of visible rows in translation results - only 2 rows are visible now. In some cases it is more convenient to see 3-4 rows with fewer hits Translation results should have special icons for translator, reviewer 1 and reviewer 2 An option to remove the src segment from the results pane, and display it only once with comparison info in the translation grid. Colors should be studied extensively to solve issues such as highlighting a term and indicating that it is different from, or an addition to the selected hit. Complete freedom in dragging and dropping interface elements may be required so that the user may juxtapose the src segment with the hit. Indicating with a caret (‸) where to insert words in hit src segment in the translation result pane; hovering over the caret should show missing text in a tooltip. This way the translator will have a complete picture of required modifications: blue for what should be deleted, red for what should be changed, and (‸) for the point where something should be inserted.

Tags
 Option "Omit embedded codes" when retrieving fragments from "Translation Results" (TilovdB)  Omit tags when copy/paste from translation results manually - strange symbols are now inserted which should be deleted manually  Clear all tags from source segment - this can save time and effort when dealing with malformed documents, and is much better than modifying the original, reimporting, and then x-translating. A warning message should appear by default when the translator uses this feature.  Tag cleaning options in filter configuration - there should be options for minimizing tags caused by the complex formatting applied by OCR and PDF conversion tools, similar to the options offered by TransTools Tag Cleaner, and the CLEAN function offered by MS Excel.

Preview
Preview window should have an option to show ONLY source text, i.e., not both src + increasingly more trgt as you work your way down through the translation, which can be confusing, esp. when src and trgt have opposite directions (wordbook.nl) Preview window should have an option to darken cell borders for Excel sheet preview; clearer cell borders help in segment merging/splitting decisions. <li>Better rendering of bidi texts is needed, esp. when rtl text has a combination of numbers, punctuation, and ltr text. (This improvement is also needed for grid view.) <li> Switch between source and target in file preview

Status bar
<li>Show the number of locked segment in the status bar

Fonts
<li> Font adaptation similar to Trados Studio - font color, size etc (not only bold, italic and underlined)

<li> Font contrast adaptation similar to Trados Studio - contrast font hurts eyes

Options and Settings

 * Rethinking and simplifying options and settings - e.g. instead of showing options for resources in three locations (namely, Options > Default Resources, Resource Console, and Project Home > Settings), Default Resources could be incorporated into the Resource Console, Options renamed to Universal Options (i.e. for old and new projects), and Settings under Project home renamed to Project Settings.

Others
<li> Copy of formatting from DOC and HTML - ability to copy text from WORD or browser with format (bold, italic etc) (only plain text is now inserted)

<li> Drag & drop for opened document tabs - it is not possible to change order of opened tabs with translatable documents

<li> Support of high-resolution displays - 4K and 2K displays are becoming more popular but memoQ still does not offer comfortable work with high-resolution displays

<li> Alternating row colors according to Excel row: e.g. white for segments from Excel row 1, gray for segments from Excel row 2, then white for row 3, etc.; this way the context of each segment will be much clearer.

<li> Ability to resize dialogues in the: Edit term base entry dialogue, such as: Definition, Usage, Notes. (Michael J.W. Beijer)

<li>It would be nice to have the number of words not started in the Project Status bar at the bottom of the screen. [Requested Nov 2007 by Karin Adamczyk]

<li> "Projects" button in "Project Manager" (under "Settings") which gives direct access to other projects (TilovdB)

<li>Edit TUs directly in concordance window (T.Rox)</li>

<li> Being able to use MemoQ on two screens (Anette) <li>

<li> Make all the File Filter settings available via Tools > Options (Thomas V.) <li>

<li> Provide a GUI to edit the smart quote replacements (Thomas V.) <li>

<li> Separate Translator editor area into 2 zones by horizontal bar: to see 2 different parts of document (like Adobe Reader or MS Word)

<li> Show the number of repetitions next to the repetition icon - it is often not clear whether it is a repetition within project or document when you need to change it after propagation

<li> Add regex option to search & replace - it is very useful for structured and repetitive documents, and may save hours of work depending on the size of the document. The option should be unchecked or hidden by default so as not to confuse those unfamiliar with regex - this was added in a recent update

<li> Add "keep confirmed segment status" checkbox to search & replace - It should always be unchecked by default; the translator must tick it for each operation at his/her own discretion.

<li> Option to override Goto next settings - While Search & Replace is open, and after modifying and confirming a segment, the translator should have the option to jump to next instance instead of the segment type set in Goto next dialog with Automatically jump after confirmation checked.

<li> Better display of bidi texts in translation grid - When the source is rtl, such as Arabic and Hebrew, memoQ indiscriminately enforces rtl direction/alignment, even if the segment has only Latin characters or numbers and is an independent paragraph. This brute enforcement results in misplacement of punctuation, such as parentheses etc., and numbers; the translator often has to open the original to make sense of a segment.

Keyboard Shortcuts
<li>Add keyboard shortcuts for concordance window (for: Move hits up and down, insert selected) (T.Rox)</li> <li> Move word(s) left/right keyboard shortcut as an editing workaround for MQ's lack of drag'n'drop (cut selection (word if insertion point), move left/right, paste, retain selection for next move). (David Turner, May 2008) <li> A shortcut key for Export Active Document (Anette) <li> Ability to Quickly Add terms to specific term bases with customisable shortcuts. (wordbook.nl) <li>Shift+F3 in Add new term window: an option to change case in Add new term window by using shortcut Shift+F3 <li>Close Quick find and Quick find and replace windows by pressing the Esc key: it is not possible to close these windows conveniently without using the mouse <li>Pressing the Enter key in the Quick find and Quick find and replace windows should move the cursor to the next match: it is more natural to enter some text to find and then press Enter to find it rather than press two keys (Alt+F). Both shortcuts (Enter and Alt+F) could have the same function.
 * Ctrl+Shift+L in QA tab: an option to use a shortcut for lock/unlock segments in QA results tab

Collaborative work

 * P2P protocol to share TMs and TBs (and other resources): affordable solution to share TMs which are stored on the main PC which allows teamwork

XTM (TIPP)

 * Extract TM from TIPP: an option to extract TM from TIPP to create tmx-export or project TM (and use memoQ features like concordance with this TM)
 * Highlight differences for TM matches from XLIFF:doc: now all matches look the same way

SDL Trados Studio

 * Compatibility of tracked changes in memoQ and Trados Studio: more and more clients needs review of SDLXLIFF in tracked changes. So it is impossible to use memoQ for this growing number of projects (20-30% of my jobs)
 * Preserve match % in exported SDLXLIFF: it is not convenient to review in Trados Studio the SDLXLIFF files which were translated in memoQ as segments do not have match %.

Import/Export

 * Import/Export of Transit files, I think (when autoassemble/ebmt is covered) that this will be the crucial feature for MemoQ, the 'killer application thing'. Never understood why Atril doesn't offer this, I believe it's because of old ties. (Hans List)
 * VBA-like macro language that allows us to communicate with the interace (pop-up dialogs etc.) and create our own goodies that we can share via this WIKI. My suggestion: Basic Script is Visual Basic for Application™ compatible language built on top of popular SAX Basic engine. The Basic Script comes with powerful editor (features syntax highlighting, tool tips), debugger, dialog editor, language reference help and other tools necessary for comfortable scripts development. Basic Script features more commands then native macro language and allows user to write more complex scripts: use OLE, DDE, create dialogs, use mathematical functions and much more. (Hans List)
 * Would be great if you could just select all the TMs and TBs in one swift click (Anette, August 2010)
 * Exclude from import number-only segments: an option not to import number-only segments
 * Import of files into Corpora via drug&drop: an option to add documents to Corpora by drug&drop from Windows Explorer (or any other file manager)
 * Automatic use of Process TRADOS TMX for best results in memoQ: it is strange to check this option manually when memoQ determined that TMX was created by Trados
 * Keep table direction: an option not to switch table direction when src and trgt languages have opposite directions; this can make for easier comparison between the original and the translation.
 * Importing an Excel spreadsheet on a “cell-by-cell” basis: a clear and effective option should be available in the Excel filter configuration, such as "No segmentation for cell contents," or "Import on cell-by-cell basis." The option “Import linebreaks as inline tags” is not very clear, and still results in some segmentation of cell contents due to punctuation; in addition, even when "empty" segmentation rules are used together with the mentioned option, some segmentation of individual cell contents is observable.

Others
<li> Ability to edit and delete portions and matches directly in the Translation Results window (David Turner)

<li> After running the "Resolve errors and warnings function", you are still taken to a blank "Resolve errors and warnings" window even if there are no errors to correct. It would be better to have a "No errors or warnings" message. (David Turner)

<li> Enable "Add all" button in "Mark selected ranges" (XLS-Import) to select multiple tab sheets subsequently (TilovdB)

<li>AutoAssemble and EBMT. (Hans List)

<li>Working area - moving windows from inside MemoQ (like translator's grip, automatic translation results or translation preview) out of MemoQ (for example to another screen) - Grzegorz Kowalski

<li> An "Align from here" function, that would align from a certain part of the text, ignoring previous text. Also being able to edit the text would be a great leap (Mat Holway)

<li> A vocabulary collecting all the file extensions and invented jargon that stand between user comprehension and effective utilization of the expensive product. For instance, I am still trying to discover the file extension used for memory files. (interpreter)

<li> "SDL will connect all its translation tools through open APIs and enabling Translators using Trados to easily connect to TDA and benefit from industry-wide sharing of TMs". (www.tausdata.org) I hope MemoQ will consider implementing something similar. (Rod Walters)

<li> Being able to export all translations in a project at the same time (actually a function that used to be there) (Anette and Tine)

<li> Being able to export a document without forced automatic correction of tag errors; this is useful if the translator is sure s/he has ignored useless/incorrect tags in a malformed document, and does not want to revise this automatic "correction."

<li> Embedded troubleshooter, or at least tips for solving most common errors. e.g. When a user tries in vain to use Export (Stored Path) to export a document that was imported from an xliff from another computer, why not suggest to try Export (Dialog)?

<li> Option to clear only src script from target either in "Search & Replace" or "Clear Translations" dialogs. This could be very helpful after "Copy Source" into multiple segments.

Solved issues or workarounds
For any problem and workaround see also the page CAT-Tools/MemoQ/Tips and Tricks.

Issues solved in current memoQ version
<li> Reduce clutter in Translation Results window (numbers, number of fuzzy matches, etc. (David Turner) <li>Find & Replace - adding option with ability to find a source string only in confirmed/edited segments (T. Rox) Source language should always be selected. The second language should be remember from the last editing session. (Carsten) Scenario: The project manager defines new terms and releases them. During translation the terms show up as not yet translated. (Carsten) <li>Import filter to import Trados(TM)-TMs in txt format. (T.Rox) - can be resolved with PlusToyz, XBench or Olifant.
 * Customization of buttons on panel - current memoQ version has QuickAccess tab
 * Delete all comments in a file/view - current memoQ version does it
 * Drag & drop for folders: an option to import files by drag & drop of folders
 * Display file extensions: (and maybe Windows-file-type-icons) in Project Manager (TilovdB)
 * Better compatibility with SDLXLIFF generated by Studio 2014: Studio can not open and clean SDLXLIFF generated in Studio 2014 and translated in memoQ
 * Ribon stretchable interface - aka MS Office 2010 ribon
 * Copying projects: In most cases a new project is similar to an existing project: project manager, translator, source language, target language, client, etc. So copying a project makes sense (Carsten) - templates are available in current memoQ version
 * Show QA warnings in view pane
 * Editing the source: Since there are often mistakes in source texts, it would be convenient to be able to correct the source on the fly. Otherwise, wrong source text is enshrined in the memory.
 * A possibility to add pictures and to link pictures (pictures may exist in a media asset management system or on the web site of a company)
 * An alignment function for importing word lists or adding a language
 * Export functions
 * Project dashboard to have an overview of running projects (T.Rox) - current memoQ version has overview of projects
 * Tabular report for spellchecking: spellchecking gives a tabular report with summary of errors. It could have a design similar to QA report and have different columns. It could be placed on a separate tab in QA results. It would save time when spellchecking a large document (doing it in a background)- memoQ 2014 has structure view for files
 * Hide common file path: an option to hide in Import/Export path column on Project Home tab file path which is common for all files - memoQ 2014 has structure view for files
 * Saving the TB content to Word or PDF (or another format), to automate and speed up the creation of glossaries.(Ariane)
 * Termbase compatibility to the TBX standard format. It will be nice, if MemoQ were able to import and export files with the TBX standard termbase exchange format. (Paul Bouvier)
 * Being able to quickly find double entries in the TB or just a function that prevents one or more terms from being added more than once to the same TB (A. Jakobsen)
 * New projects: For us as a company, the source language never changes. The target languages are fixed. Only once in a while we will add a new target language. It would be nice if one could: 1. prefill the fields when creating a new project (e.g. saved settings from last project, so the French translator is already selected when creating a French project) 2. Hide target languages you don't need; e.g., deselect languages in a global settings dialog so they don't show up when creating a new project, term base, etc.
 * support for document formats:
 * .odt / Open Office Writer (workaround: save as doc)
 * .ods / OpenOffice.org Calc (workaround: save as xls)
 * Preferred TB: an option to mark TB as preferred. It could have a special icon and higher priority in translation results and QA (e. g. client's glossaries which should be strictly followed).
 * Remember selected languages when directly editing a term base
 * Term base: terms show up even if they don't have a translation
 * Hide languages
 * Formatting/adding/inserting of bold, italics and underlined is fine (great), but for a technical translator supscript and superscript are necessary too (a lot of m², m³, m-1 etc. in technical texts). (Hans List)
 * Set the language of exported documents to the target language (instead of leaving the original source language setting). Currently 100% of the text in exported doc files is underlined in red. (tsca)
 * Delete term from TB via right click menu in translation results: currently one needs to do several steps for it.
 * Identification of duplicated words: like MS Word does it
 * Filter segments by change date and user: an option to filter only those segments translated e.g. by user XY on 1/1/2012 so as to allow proofreading of segments actually translated by particular person
 * Reply to comment: an option to reply to comment (each comment should be signed by user name)
 * Add new words via right-click menu: an option to add an unknown word to dictionary via right-click menu.

<li> Add sublanguages for Dutch (TilovdB) - Version 2.2 does this job (Belgium and Netherlands).

<li>Special characters - This function is available in the most recent version, see menu Edit → Insert symbol.

<li> Include spaces in character count (Grzegorz Harbaszewski)

<li> View: All except locked rows and View: Locked rows (TilovdB) - memoQ filter can do it in the current version <li>'Case sensitive term recognition'. Some won't use it, but for languages like German it is very useful (the Verb 'schrauben' is translated different from the noun 'Schrauben' (plural)). (Transit offers this, but it's implementation has severe bugs.) (Hans List) <li>Larger or adjustable font for the Translation Results area. [Requested Nov 2007 by Karin Adamczyk]

Allow keeping only the last translations for every segment.
<li>DVX cannot perform this trick (neither can Transit, Trados does it, when re-importing an exporting TM). (Hans List) <li>See the solution Gábor Ugray provided under CAT-Tools/MemoQ/Tips and Tricks!

Auto correct as you type.
<li>Current workaround is to use PhraseExpander, PhraseExpress, Texter, AutoHotkey or similar (Requested Nov 2007 by Karin Adamczyk) - done in current memoQ version

Automatic insertion of exact/best matches from TM
<li>Pretranslation should do the job (can be configured in different ways) (Grzegorz Harbaszewski)

Hide target languages you don't need
<li> Edit the LangInfo.xml file and comment out or delete the languages you don't need. You can use Notepad or an XML editor, your choice. Note: Be sure to save a copy of your edited file in a safe place, because a program update will overwrite it. - The file is found here: C:\Documents and Settings\All Users\Application Data\MemoQ\LangInfo.xml Workaround by Gregory - confirmed by Gábor Ugray of Killgray on the MemoQ2 list: http://tech.groups.yahoo.com/group/MemoQ2/message/2009.

Shortcut: delete entire contents in current translation segment
<li>Current workaround is to use PhraseExpander, PhraseExpress, Texter, AutoHotkey, or similar (TilovdB)

Outdated/Obsolete wishes
<li> Switching between different tag view: an option to switch between different tag views (in-line/memoQ tags) while saving all segments intact without "real" re-import. - current memoQ version supports only 1 type of tags
 * Export comments for TTX-files - TTX is an outdated file format

title: CAT-Tools/MemoQ/Wishlist


text:
CAT-Tools/MemoQ/Activation

The activation logic of memoQ
In the activation logic of memoQ a serial number is not the 'code', it is just your ID card. Every user can apply for a serial number either through memoQ or via email.

Serial numbers carry licenses, i.e. specific time-limited permissions to use different products/product functionality. When you apply for a demo version, you get two licenses automatically, a never-expiring memoQ 4Free license and a 90-day memoQ Network license. If you buy a license, you get an additional license to your existing serial number. So if you suspect there is a new license for you, click Update licenses online in the Help / Activation dialog.

If a firewall prevents you from activating online, you can Retrieve activation data for sending in e-mail and send it to Kilgray's info address.

Changing the serial number
If, for any reason, you entered the wrong serial number, you can still change it; however, this requires a bit of technical wizardry.

To delete the serial number under version 3.x and 4.x, please do the following:

 * 1) Check whether you can see Hidden files and folders. If not, open the Control Panel, select Folder options and on the View tab enable showing hidden files and folders.
 * 2) Under C:\Documents and Settings\All Users\Application Data\memoQ, delete License11.dat, License12.dat and License13.dat. If you are using Windows Vista, these files are found under C:\ProgramData\memoQ.
 * 3) Start memoQ again, and enter your new serial number.

To delete the serial number under version 2.x, please do the following:

 * 1) Check whether you can see Hidden files and folders. If not, open the Control Panel, select Folder options and on the View tab enable showing hidden files and folders.
 * 2) Under C:\Documents and Settings\(your username)\Application Data\memoQ, delete License01.dat and License02.dat
 * 3) Start memoQ again, and enter your new serial number.

Important note: If you have active licenses tied to your original serial number, make sure to copy and save the serial so you can revert to it later. memoQ will not allow you to request a second serial number on the same computer.

Using memoQ on a different computer
memoQ's activation scheme uses the serial number to tie licenses to a particular physical computer. This means that if you enter the same serial number after installing memoQ on a different computer, the activation server will say No valid licenses when you hit Update licenses online.

But what happens if you buy a new PC? You can enter your existing serial number and update your licenses, provided that a certain amount of time has passed since you last updated your licenses on your original computer.

If you purchased a license, the activation scheme also allows you to install memoQ on more than one computer (so that you can use it in the office and on your laptop as well). When installing memoQ on the second computer, make sure that you change the extra number at the end when you type your serial number. By default, the extra number is "1"; on the second computer, use "2" instead.

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

title: CAT-Tools/MemoQ/Activation


text:
Talk:Horticulture/Brassica

cut from wp article, might be good source of more info

 * Cruciferous vegetables for more edible plants of the Brassicaceae family.

title: Talk:Horticulture/Brassica


text:
Horticulture/Brassica

Brassica is the type genus of the mustard family, ../Brassicaceae/. The members of the genus may be collectively known either as cabbages, or as mustards.

This genus is remarkable for containing more important agricultural and horticultural crops than any other genus. It also includes a number of weeds, including both wild taxa and escapees from cultivation. It includes over 30 wild species and hybrids, and numerous additional cultivars and hybrids of cultivated origin. Most are annuals or biennials, but some are small shrubs.

The genus is native in the wild in western Europe, the Mediterranean and temperate regions of Asia. In addition to the cultivated species, which are grown worldwide, many of the wild species grow as invasive or naturalised weeds, especially in North America, South America, and Australia.

Almost all parts of some species or other have been developed for food, including the root (../Rutabaga/, ../Turnip/), stems (../kohlrabi/), leaves (../Cabbage/, brussels sprouts), flowers (../cauliflower/, ../broccoli/), and seeds (many, including mustard seed, oilseed rape). Some forms with white or purple foliage or flowerheads, are also sometimes grown for ornament.

Brassica species are sometimes used as food plants by the larvae of a number of Lepidoptera species - see List of Lepidoptera which feed on Brassicas.

Species
There is some disagreement among botanists on the classification and status of Brassica species and subspecies. The following is an abbreviated list, with an emphasis on economically important species.

 * ../Brassica carinata/ - Abyssinian Mustard or Abyssinian Cabbage
 * ../Brassica elongata/ - Elongated Mustard
 * ../Brassica fruticulosa/ - Mediterranean Cabbage
 * ../Brassica juncea/ - Indian Mustard, Brown and leaf mustards, Sarepta Mustard.
 * ../Brassica napus/ - Oilseed rape, Canola, Rutabaga (Swede Turnip)
 * ../Brassica narinosa/ - Broadbeaked Mustard
 * ../Brassica nigra/ - Black Mustard
 * ../Brassica oleracea/ - Kale, Cabbage, Broccoli, Cauliflower, Kai-lan, Brussels sprouts
 * ../Brassica perviridis/ - Tender Green, Mustard Spinach
 * ../Brassica rapa/ - Chinese cabbage, Turnip, Rapini, Mustard
 * ../Brassica rupestris/ - Brown Mustard
 * ../Brassica septiceps/ - Seventop Turnip
 * ../Brassica tournefortii/ - Asian Mustard

Deprecated species names

 * B. kaber (Wild Mustard or Charlock) - see ../Sinapis arvensis/
 * B. alba or B. hirta (White or Yellow mustard) - see ../Sinapis alba/

Pests and diseases
Bacteria: Fungi: Phytoplasma: Nematodes: Nutrient Deficiencies: ../Aphids/ ../Whiteflies/ ../Bugs/ ../Thrips/ ../Maggots/ ../Beetles/ ../Weevils/ ../Caterpillars/ ../Slugs and Snails/
 * ../Bacterial Leaf Spot/ caused by ../Xanthomonas/ spp.
 * ../Powdery Mildew/
 * ../Fungal Leaf Spot/ caused by ../Alternaria/ sp.
 * ../Downy Mildew/
 * ../White Mold/
 * ../Black Leg/
 * ../Soft Rot/
 * ../Bottom Rot/
 * ../White Mold/ caused by ../Sclerotinia/ sp.
 * ../White Rust/
 * ../Clubroot/ caused by ../Plasmidiophora brassicae/
 * ../Damping Off/
 * ../Texas Root Rot/
 * ../Yellows/ caused by a phytoplasma
 * ../Root Knot Nematodes/
 * ../Potassium/ Deficiency
 * ../Calcium/ Deficiency
 * ../Boron/ Deficiency
 * ../Magnesium/ Deficiency
 * ../Molybdenum/ Deficiency
 * Green Peach Aphid: ../Myzus persicae/
 * Cabbage Aphid: ../Brevicoryne brassicae/
 * Turnip Aphid: ../Lipaphis pseudobrassicae/
 * Greenhouse Whitefly: ../Trialeurodes vaporariorum/
 * Silverleaf Whitefly: ../Bemisia argentifolii/
 * False Cinch Bug: ../Nysius raphanus/ Western North America
 * Harlequin Bug: ../Murgantia histrionica/ Southern US
 * Stink Bugs
 * Onion Thrips: ../Thrips tabaci/
 * American Serpentine Leaf Miner: ../Liriomyza trifolii/
 * Cabbage Leaf Miner: ../Liriomyza brassicae/ (Warm climates)
 * Cabbage Maggot: ../Delia radicum/ Northern US and Canada
 * European Crane Fly: ../Tipula paludosa/ Europe, Northwest US and Western Canada
 * Pea Leafminer: ../Liriomyza huidobrensis/
 * Radish Root Maggott: ../Delia planipalpis/ Western North America
 * Cabbage Flea Beetle ../Phyllotreta albionica/
 * Colorado Potato Beetle: ../Leptinotarsa decemlineata/
 * Crucifer Flea Beetle: ../Phyllotreta cruciferae/
 * Hop Flea Beetle: ../Psyllioides punctata/
 * Palestriped Flea Beetle: ../Systena blanda/
 * Red Turnip Beetle: ../Entomoscelis americana/ Northwest Us and Western Canada
 * Striped Flea Beetle: ../Phyllotrete striolata/
 * Western Black Flea Beetle: ../Phyllotreta pusilla/
 * Western Striped Flea Beetle: ../Phyllotreta ramosa/
 * Whitefringed Beetles: ../Naupactus/ spp.
 * Yellowmargined Beetle: ../Microtheca ochroloma/
 * Vegetable Weevil: ../Listroderes difficilis/
 * Cabbage Looper: ../Trichoplusia ni/
 * Alfalfa Looper: ../Autographa californica/ Western US
 * Beet Armyworm: ../Spodoptera exigua/
 * Cabbage Butterfly Caterpillar (Cabbage White, Imported Cabbageworm): ../Pieris rapae/
 * Cabbage Webworm: ../Hellula rogatalis/
 * Cross-striped Cabbageworm: ../Evergestis rimosalis/
 * Diamondback Moth Caterpillar: ../Plutella xylostella/
 * Purplebacked Cabbageworm: ../Evergestis pallidata/
 * Southern Cabbageworm (Checkered white butterfly): ../Pontia protodice/
 * Zebra Caterpillar: ../Ceramica picta/
 * Angle Shades (../Phlogophora meticulosa/)
 * Cabbage Moth (../Mamestra brassicae/)
 * Common Swift (../Korshceltellus lupulina/)
 * Foxglove Pug (../Eupithecia pulchellata/) - recorded on Brassica in Malta
 * Garden Carpet (../Xanthorhoe fluctuata/)
 * Garden Dart (../Euxoa nigricans/)
 * Ghost Moth (../Hepialus humuli/)
 * Giant Leopard Moth (../Ecpantheria scribonia/)
 * The Gothic (../Naenia typica/)
 * Heart and Club (../Agrotis clavis/)
 * Heart and Dart (../Agrotis exclamationis/)
 * ../Hypercompe abdominalis/
 * ../Hypercompe indecisa/
 * Large Yellow Underwing (../Noctua pronuba/)
 * The Nutmeg (../Discestra trifolii/)
 * Setaceous Hebrew Character (../Xestia c-nigrum/)
 * Turnip Moth (../Agrotis segetum/)

title: Horticulture/Brassica


text:
User talk:209.66.200.65

Welcome to Wikibooks. We invite everyone to contribute constructively to our collection. Take a look at the welcome page if you would like to learn more about contributing. However, unconstructive edits are considered vandalism, and if you continue in this manner you may be blocked from editing without further warning. Please stop, and consider improving rather than damaging the hard work of others. Thanks. -- Herby talk thyme 16:38, 12 February 2007 (UTC)

You are blocked, when the block expires we hope you will return and contribute positively. -- Herby talk thyme 16:44, 12 February 2007 (UTC)

title: User talk:209.66.200.65


text:
Template:Tlx/doc

becomes →

 Purpose and naming:  Mnemonically 'Template list expanded'... named after 'Template list'

Usage

 * {{|template name}}
 * {{|template name|param}}
 * {{|template name|param=value}}
 * {{|template name|param&#61;value}}

 * This template takes a template-name and an optional number of associated parameters (or 'pass parameters'), and aggregates them into an 'example demonstration' of how the template might be used. It's primary use is in instruction and documentation such as this passage.
 * Additionally, tlx can be used to demonstrate templates on other sister projects.

title: Template:Tlx/doc


text:
Horticulture/Aster

The genus Aster (syn. Diplopappus Cass.) includes some 600 species of widely distributed flowering plants in the family Asteraceae. Aster comes from the Greek word for "star", and refers to the shape of the flower head. Many species and a variety of hybrids and varieties are now popular as garden plants because of their showy flower heads.

The genus Aster is now generally restricted to the Old World species, with Aster amellus being the type species of the genus (and of the family Asteraceae). The New World species have now been reclassified in the genera ../Almutaster/, ../Canadanthus/, ../Doellingeria/, ../Eucephalus/, ../Eurybia/, ../Ionactis/, ../Oligoneuron/, ../Oreostemma/, ../Sericocarpus/ and Symphyotrichum (see : List of Aster synonyms on Wikipedia), but are still widely referred to as "Asters" in the horticultural trade.

In the United Kingdom there are only two native members of the genus of which one, Goldilocks is very rare, the other being the Sea aster, ../Aster tripolium/.

Description
The flowers are heads, borne in generally large terminal clusters. Rays female and strap-shaped, disk flowers perfect, usually yellow. Involcure green and of several rows. The seeds are achenes with a bristly pappus.

The leaves are alternate and simple.

Species
Some common species are:
 * ../Aster alpinus/
 * ../Aster amellus/ ('European Michaelmas Daisy' or 'Italian Aster')
 * ../Aster cordifolius/ ('Blue Wood Aster')
 * ../Aster divaricatus/ ('White Wood Aster')
 * ../Aster ericoides/ ('Heath Aster')
 * ../Aster laevis/
 * ../Aster lateriflorus/ ('Lady in Black')
 * ../Aster linosyris/ ('Goldilocks Aster')
 * ../Aster novae-angliae/ ('New England Aster')
 * ../Aster novi-belgii/ ('New York Aster')
 * ../Aster pilosus/ ('Frost Aster')
 * ../Aster pringlei/
 * ../Aster scaber/
 * ../Aster sibericus/
 * ../Aster tataricus/
 * ../Aster tongolensis/
 * ../Aster tripolium/ ('Sea Aster')

The China aster is in a related genus, ../Callistephus/.

Uses
Asters make good fresh cut flowers. In the garden they are an excellent nectar source for attracting pollinators and beneficial insects.

Propagation
Division, seed.

Pests and Diseases
../Powdery Mildew/ ../Leaf Spots/ ../Downy Mildew/ ../Gray Mold/ ../Wilt/ ../Cankers/ ../Rusts/ ../White Smut/
 * Erisiphe cichoracearum
 * Alternaria
 * Ascochyta compositarium
 * Cercospora asterata
 * Cercospora cana
 * Discosphaerina pseudimantia
 * Leptothyrium doellingeriae
 * Ovularia asteris
 * Ovularia virgaureae
 * Phyllachora asterigens
 * Ramularia asteris
 * Septoria asteris
 * Septoria astericola
 * Basidiophora entospora
 * Fusarium oxysporum f. callistephi
 * Verticillium
 * Coleosporium solidagnis: Alternate hosts 2/3 needle pines
 * Puccinia asteris: Alternate hosts grasses and sedges
 * Puccinia extensicola var. asteris: Alternate hosts grasses and sedges
 * Puccinia grindeliae: Alternate hosts grasses and sedges
 * Puccinia stipae:
 * Uromyces compactus: Alternate hosts grasses and sedges
 * Uromyces junci: Alternate hosts grasses and sedges

../Aster Yellows/

../Dodder/

../Aphids/ ../Hoppers/ ../Bugs/ ../Earwigs/ ../Whitefly/ ../Maggots/ ../Beetles/ ../Weevils/ ../Caterpillars/ (list of Lepidoptera which feed on Aster) ../Mites/ ../Slugs and Snails/
 * Leaf Curl Plum Aphid: ../Brachycaudus helichrysi/
 * Brown Ambrosia Aphid: ../Dactynotus ambrosiae/
 * Aphid: ../Macrosiphum artemesiae/
 * Aphid: ../Macrosiphum asterifoliae/
 * Crescent-marked Lily Aphid: ../Neomyzus circumflexus/
 * Petiole Gall Aphid: ../Pemphigus/ spp.:
 * Erigeron Root Aphid: ../Aphis middletoni/
 * Western Aster Root Aphid: ../Aphis armoraciae/
 * Aster Leaf Hopper: ../Macrosteles facifrons/
 * Treehopper: ../Entylia carniata/
 * Tarnished Plant Bug: ../Lygus lineolaris/
 * Chrysanthemum Lace Bug: ../Corythucha marmorata/
 * European Earwig: ../Forficula auricularia/
 * Greenhouse Whitefly: ../Trialeurodes vaporariorum/
 * Silverleaf Whitefly: ../Bemisia argentifolii/
 * Iris Whitefly: ../Aleyrodes spiraeoides/
 * Leafminer: ../Amauromyza maculosa/
 * American Serpentine Leaf Miner: ../Liriomyza trifolii/
 * Japanese Beetle: ../Popillia japonica/
 * Blister Beetles: ../Epicauta/ spp.
 * Black Vine Weevil: ../Otiorhynchus sulcatus/
 * Clearwing Borer: ../Carmenta corni/
 * European Corn Borer: ../Ostrinia nubilalis/
 * Soybean Looper: ../Pseudoplusia includens/
 * Cyclamen Mite: ../Steneotarsonemus pallidus/

title: Horticulture/Aster


text:
X-Plane Flight Simulator

Table of Contents

 * Introduction to X-Plane
 * Part One: Flight
 * /Getting Started/
 * System Requirements
 * Installation
 * /Basic Piloting/
 * Flight Instruments
 * Six Pack
 * /Advanced Piloting/
 * /Basic Customizing/
 * Part Two: Content
 * /Creating Aircraft/
 * /Building Buildings/
 * /Refining Airports/
 * /Adding Capabilities/
 * /Appendices/
 * /Glossary/
 * /Keyboard Quick Reference/
 * /Bibliography/
 * /About/

title: X-Plane Flight Simulator


text:
A-level Chemistry/OCR (Salters)/Colour by Design

Colour by Design is the eleventh unit in the Salters Advanced Chemistry course.

Chemical Storylines sections

 * CD1 Ways of making colour
 * CD2 The Monastral Blue story
 * CD3 Chrome Yellow
 * CD4 Chemistry in the art gallery
 * CD5 At the start of the rainbow
 * CD6 Chemists design colours
 * CD7 Colour for cotton
 * CD8 High-tech colour
 * CD9 Summary

Chemical Ideas sections

 * 6.7 Where does colour come from? (revision)
 * 5.1 Ions in solids and solutions (revision)
 * 6.8 Ultraviolet and visible spectroscopy
 * 13.6 Oils and fats
 * 7.3 Chromatography
 * 6.1 Light and electrons (revision)
 * 12.3 Arenes
 * 12.4 Reactions of arenes
 * 13.10 Azo compounds
 * 6.9 Chemistry of colour

Activities

 * CD1 Changing colours chemically
 * CD3 Seeing colours
 * CD4.1 Using reflectance spectra to identify pigments
 * CD4.2 What factors affect the drying potential of an oil?
 * CD4.3 Investigating paint media
 * CD4.4 Identifying a pigment
 * CD4.5 Finding a perfect match
 * CD5 Comparing hydrocarbons
 * CD6 Making azo dyes
 * CD7.1 Dyeing with a direct dye and a reactive dye
 * CD7.2 Different dyes for different fibres
 * CD9 Check your notes on Colour by Design


text:
User talk:150.243.49.62

Welcome to Wikibooks. We invite everyone to contribute constructively to our collection. Take a look at the welcome page if you would like to learn more about contributing. However, unconstructive edits are considered vandalism, and if you continue in this manner you may be blocked from editing without further warning. Please stop, and consider improving rather than damaging the hard work of others. Thanks. -- Herby talk thyme 19:02, 12 February 2007 (UTC)

title: User talk:150.243.49.62


text:
Microprocessor Design/Single Cycle Processors

Single-cycle processors are what we have been studying so far: an instruction is fetched from memory, it is executed, and the results are stored all in a single clock cycle.

The benefits of single-cycle processors is that they tend to be the most simple in terms of hardware requirements, and they are easy to design. Unfortunately, they tend to have poor data throughput, and require long clock cycles (slow clock rate) in order to perform all the necessary computations in time.

Cycle Times
The length of the cycle must be long enough to accommodate the longest possible propagation delay in the processor. This means that some instructions (typically the arithmetic instructions) will complete quickly, and time will be wasted each cycle. Other instructions (typically memory read or write instructions) will have a much longer propagation delay.

As this image shows, an instruction is not over until all 5 components have acted. This means that the length of the cycle must be the length of the longest instruction. The longest path from one end of the processor to the other is called the critical path and is used to determine the cycle time.

Redundant Hardware
Single cycle processors typically require a number of ALUs (or a single master ALU, and smaller ALUs) to handle the increment operations on the instruction pointer, and the memory address calculations for the data memory. When resources are at a premium, having multiple ALU units in your design can be costly and pointless. It requires nearly as many resources to construct an adder that adds a constant value as it does to construct a more general purpose adder unit.

Single Cycle Designs
It is very rare, if not completely unheard of, for a modern processor unit to have a single-cycle design. The reasons for this are the long cycle times, the wasted resources, and the large amount of wasted time in each cycle. What the single-cycle lacks in timing and efficiency, it makes up for in simplicity and elegance. It is for this reason that single-cycle processors work as a good teaching tool, but are not often employed in actual designs.


text:
Microprocessor Design/Multi Cycle Processors

Single-cycle processors suffer from poor speed performance. Control and data signals must propagate completely through the processor in a single cycle, which means that cycle times need to be long, and many parts of the hardware tend to be dormant for much of the cycle.

Multi-Cycle Stages
Multi-cycle processors break up the instruction into its fundamental parts, and executes each part of the instruction in a different clock cycle. Since signals have less distance to travel in a single cycle, the cycle times can be sped up considerably.

Typically, an instruction is executed over at least 5 cycles, which are named as such: This is just a textbook example, and modern processors tend to use much more steps than this to execute an instruction.
 * IF: Fetch the instruction from memory
 * ID: Decode the instruction, and generate the necessary control signals
 * EX: Feed the necessary control signals into the ALU and produce a result
 * MEM: Read from memory, if specified
 * WB: Write the result back to the register file or to memory.

Hardware Reuse
The primary benefit to a multicycle design is to be able to share hardware elements, specifically the ALU, among various tasks. In a multicycle processor, a single ALU can be used to update the instruction pointer (in the IF cycle), perform the operation (in the EX cycle), and calculate a necessary memory address (in the MEM cycle). Multicycle processors also allow computers that have a single memory unit, instead of the two separate instruction and data memory units of the traditional harvard machine. This is because the instructions are loaded on one cycle, and the data memory is interfaced on another cycle.

Multi-cycle processors are typically used in applications where resources are at a premium, and speed is not as important.


text:
Microprocessor Design/Superscalar Processors

In a superscalar design, the processor actually has multiple datapaths, and multiple instructions can be executed simultaneously, one in each datapath. It is not uncommon for a superscalar CPU to have multiple ALU and FPU units, for each datapath.

In this image, all the stages highlighted in green are executing simultaneously. As we can see from this image, there are two execution cores operating simultaneously.


text:
Microprocessor Design/Vector Processors

Vector processors, or SIMD processors are microprocessors that are specialized for operating on vector or matrix data elements. These processors have specialized hardware for performing vector operations such as vector addition, vector multiplication, and other operations.

Modern graphics processors and GPUs tend to be vector-based processors. Modern Intel-based chips also have SIMD capabilities known as SSE or MMX operations.

Parallel Execution
Vector processors which perform an instruction on all data elements simultaneously are said to execute in parallel.

Each EX in this image shows a separate execution core (typically an ALU) operating in parallel with one another.

Non-Parallel Execution
Vector processors which reuse a single ALU for a vector operation look like this:

As this diagram shows, each EX stage is a new set of data from the first instruction being loaded into the execution core. The next instruction will not be fetched until all the data has been acted upon.

title: Microprocessor Design/Vector Processors


text:
Template:Algebra/Page

Algebra

title: Template:Algebra/Page


text:
User talk:Xharze

Hello, Welcome to Wikibooks! I see that you've been doing alot of work on the Linear Algebra book, and I really appreciate that. As you might have guessed from the messages on that page, I had started work on that book several months ago, but was not able to finish the project. A combination of work and school has kept me pretty busy, but now i think i have some time to help.

You've done a very good job so far, from what I can see, and I dont want to jump in and take over your project. I'll add some fixes where I can, and If you need any help at all, please don't hesitate to ask me. --Whiteknight (talk) (projects) 22:45, 12 February 2007 (UTC)

 * Have you considered merging A First Course in Linear Algebra in ites entirety, and wikifying the results? It is a perfectly lovely and complete 700+-page text with an existing maintainer.  Cheers, Sj 01:27, 3 June 2007 (UTC)

title: User talk:Xharze


text:
Advanced Mathematics for Engineers and Scientists/Scale Analysis

Scale Analysis
In the chapter on nondimensionalization, variables (both independent and dependent) were nondimensionalized and at the same time scaled so that they ranged from something like $$0$$ to $$1$$. "Something like $$0$$ to $$1$$" is the mentality.

Scale analysis is a tool that uses nondimensionalization to:

 * Understand what's important in an equation and, more importantly, what's not.
 * Gain insight into the size of unknown variables, such as velocity or temperature, before (even without) actually solving.
 * Simplify solution process (nondimensional variables ranging for $$0$$ to $$1$$ are very amiable).
 * Reduce dependence of the solution on physical parameters.
 * Allow higher quality numeric solution since variables that are of the same range maintain accuracy better on a computer.

Scale analysis is very common sense driven and not too systematic. For this reason, and since it is somewhat unnatural and hard to describe without endless example, it may be difficult to learn.

Before going into the concept, we must discuss orders of magnitude.

Orders of Magnitude and Big O Notation
Suppose that there are two functions $$f(x)$$ and $$g(x)$$. It is said (and notated) that:

 * $$f(x) \ \mbox{ is } \ \mathcal{O}(g(x)) \ \mbox{ as } \ x \to a\ \quad \mbox{if} \quad \limsup_{x \to a} \left|\frac{f(x)}{g(x)}\right| < \infty\,$$

It's worth understanding fully this possibly obscure definition. $$\mbox{lim sup}$$, short for limit superior, is similar to the "regular" limit, only it is the limit of the upper bound. This concept, alongside limit inferior, is illustrated at right. This intuitive analysis will have to suffice here, as the precise definition and details of these special limits are rather complicated.

As a further example, the limits of the cosine function as $$x$$ increases without bound are:

 * $$\limsup_{x \to \infty} \ \cos(x) = 1\,$$

 * $$\liminf_{x \to \infty} \ \cos(x) = -1\,$$

 * $$\lim_{x \to \infty} \cos(x) \ \mbox{ does not exist}\,$$

With this somewhat off topic technicality hopefully understood, the statement that:

 * $$f(x) \ \mbox{ is } \ \mathcal{O}(g(x)) \ \mbox{ as } \ x \to a\,$$

Is saying that near $$x = a$$, the order (or size, or magnitude) of $$f(x)$$ is bounded by $$g(x)$$. It's saying that $$|f(x)|$$ isn't crazily bigger then $$|g(x)|$$ near $$x = a$$, and this is precisely notated by saying that the limit superior is bounded (the "regular" limit wouldn't work since oscillations would ruin everything). The notation involving the big O is rather surprisingly called "big O notation", it's also known as Landau notation.

Take, for example, $$f(x) = 3 x^2 - 100 x + 2$$ at different points:

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(x^2) \ \mbox{ as } \ x \to \infty\,$$

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(x^0) \ \mbox{ as } \ x \to 0\,$$

In the first case, the $$x^2$$ term will easily dominate for large $$x$$. Even if the coefficient on that term is very near zero, for large enough x that term will dominate. Hence, the function is of order $$x^2$$ for large $$x$$.

In the second case, near $$x = 0$$ the first two terms are limiting to zero while the constant term, $$2$$, isn't changing at all. It is said to be of order $$1$$, notated as order $$x^0$$ above. Why O(1) and not O(2)? Both are correct, but O(1) is preferred since it is simpler and more similar to $$x^0$$.

This may put forth an interesting question: what would happen if the constant term was dropped? Both of the remaining terms would limit to zero. Since we are looking at x near zero and not at zero,

 * $$3x^2 - 100 x \ \mbox{ is } \ \mathcal{O}(x) \ \mbox{ as } \ x \to 0\,$$

This is because as $$x$$ approaches zero, the quadratic term gets smaller much faster then the linear term. It would also be correct, though kind of useless, to call the quantity O(1). It would be incorrect to state that the quantity is of order zero since the limit would not exist, not under any circumstance.

As implied above, $$g(x)$$ is by no means a unique function. All of the following statements are true, simply because the limit superior is bounded:

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(\sinh(x)) \ \mbox{ as } \ x \to \infty\,$$

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(500 \cdot 2^{2^x} - \sin(x)) \ \mbox{ as } \ x \to \infty\,$$

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(x) \ \mbox{ as } \ x \to 0\,$$

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(x^2) \ \mbox{ as } \ x \to 0\,$$

While technically correct, these are very misleading statements. Normally, the simplest, smallest magnitude function g(x) is selected.

Before ending the monotony, it should also be mentioned that it's not necessary for $$f(x)$$ to be smaller then $$g(x)$$ near $$x = a$$, only the limit superior must exist. The following two statements are also true:

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(0.00001) \ \mbox{ as } \ x \to 0\,$$

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(1000000000) \ \mbox{ as } \ x \to 0\,$$

But again, these are misleading and it's most proper to state that:

 * $$3x^2 - 100 x + 2 \ \mbox{ is } \ \mathcal{O}(1) \ \mbox{ as } \ x \to 0\,$$

A relatively simple concept has been beaten to death, to the point of being confusing. It'll be more clear in context, and it'll be used more in later chapters for different purposes.

Scale Analysis on a Two Term ODE
Previously, the following BVP was considered:

 * $$\frac{d^2 u}{d y^2} = \frac{P_x}{\nu \rho}\,$$

 * $$u(0) = 0\,$$

 * $$u(D) = 0\,$$

Wipe away any memory of solving this simple problem, the concepts of this chapter do not look at the actual solution. The variables are nondimensionalized by defining new variables:

 * $$u = u_s \hat u \ \mbox{, } \ y = D \hat y\,$$

So that $$y$$ is scaled by $$D$$, and $$u$$ is scaled by an unknown scale $$u_s$$. Now note that, thanks to the scaling:

 * $$\hat y \ \mbox{ is } \ \mathcal{O}(1) \ \mbox{, and } \ \hat u \ \mbox{ is } \ \mathcal{O}(1)\,$$

These are both true near zero. $$u$$ will be O(1) (this is read "of order one") when its scale is properly chosen. Using the chain rule, the ODE was turned into the following:

 * $$\frac{u_s}{D^2} \frac{d^2 \hat u}{d \hat y^2} = \frac{P_x}{\nu \rho}\,$$

Now, if both $$u$$ and $$y$$ are of order one, then it is reasonable to assume that, at least at some point in the domain of interest:

 * $$\frac{d^2 \hat u}{d \hat y^2} \ \mbox{ is } \ \mathcal{O}(1)\,$$

This is by no means guaranteed to be true, however it is reasonable.

To identify the velocity scale, we can set the derivative equal to one and solve. There is nothing "illegal" about purposely setting the derivative equal to one since all we need is some equation to specify an unknown constant, $$u_s$$. There is much freedom in defining this scale, because what this constant is and how it's found has no effect on the validity of the solution of the BVP (as long as it's not something stupid like $$0$$).

 * $$\frac{u_s}{D^2} \cdot 1 = \frac{P_x}{\nu \rho} \Rightarrow u_s = \frac{D^2 P_x}{\nu \rho}\,$$

Since:

 * $$\hat u \ \mbox{ is } \ \mathcal{O}(1)\,$$

It follows that:

 * $$u \ \mbox{ is } \ \mathcal{O}(u_s) \Rightarrow u \ \mbox{ is } \ \mathcal{O}\left(\frac{D^2 P_x}{\nu \rho}\right)\,$$

This velocity scale may be thought of as a characteristic velocity. It's a number that shows us what to expect the velocity to be like. The velocity could actually be larger or smaller, but this gives a general idea. Furthermore, this scale tells us how changing various physical parameters will affect the velocity; there are four of them summarized into one constant.

Compare this result to the coefficient (underlined) on the complete solution, with u dimensional and $$y$$ nondimensional:

 * $$u(\hat y) = \underline{\frac{D^2 P_x}{2 \nu \rho}} (\hat y^2 - \hat y)\,$$

They differ by a factor of $$2$$, but they are of the same order of magnitude. So, indeed, $$u_s$$ characterizes the velocity.

Words like "reasonable" and "assume" were used a few times, words that would normally lead to the uglier word "approximate". Relax: the BVP itself hasn't been approximated or otherwise violated in any way. We just used scale analysis to pick a velocity scale that:

 * Turned the ODE into something very easy to look at: $$\tfrac{d^2 \hat u}{d \hat y^2} = 1 \quad ; \quad u(0) = u(1) = 0\,$$
 * Gained good insight into what kind of velocity the solution will produce without finding the actual solution.

Note that a zero pressure gradient can no longer show itself in the ODE. This is by no means a restriction, since a zero pressure gradient would result in a zero velocity scale which would unconditionally result in zero velocity.

Scale Analysis on a Three Term PDE
The last section was still more of nondimensionalization then it was scale analysis. To just begin getting deeper into the subject, we'll consider the pressure driven transient parallel plate IBVP, identical to the above only with a time component:

 * $$\frac{\partial u}{\partial t} = \nu \frac{\partial^2 u}{\partial y^2} - \frac{P_x}{\rho}\,\,$$

 * $$u(0, t) = 0\,$$

 * $$u(D, t) = 0\,$$

 * $$u(x, 0) = 0\,$$

See the change of variables chapter to recall the origins of this problem. Scales are defined as follows:

 * $$u = u_s \hat u \ \mbox{, } \ y = D \hat y \ \mbox{ , } \ t = t_s \hat t\,$$

Again, the scale on $$y$$ is picked to make it an order one quantity (based on the BCs), and the scales on $$u$$ and $$t$$ are just letters representing unknown quantities.

The chain rule has been used to define derivatives in terms of the new variables. Instead of taking this path, recall that, given variables $$x$$ and $$y$$ (for the sake of example) and their respective scales $$x_s$$ and $$y_s$$:

 * $$\frac{\partial^n y}{\partial x^n} = \frac{\partial^n \hat y}{\partial \hat x^n} \frac{y_s}{x_s^n} \qquad

 * \quad x = x_s \hat x \, \ y = y_s \hat y\,$$

So that makes things much easier. Performing the change of variables:

 * $$\frac{\partial \hat u}{\partial \hat t} \frac{u_s}{t_s} =

\nu \frac{\partial^2 \hat u}{\partial \hat y^2} \frac{u_s}{D^2} - \frac{P_x}{\rho}\,\,$$

In the previous section, there was one unknown scale and one equation, so the unknown scale could be easily and uniquely isolated. Now, there are two unknown scales but only one equation (no, the BCs/IC will not help). What to do?

The physical meaning of scales may be taken into consideration. Ask: "What should the scales represent?"

There is no unique answer, but good answers for this problem are:

 * $$u_s$$ characterizes the steady state velocity.
 * $$t_s$$ characterizes the response time: the time to establish steady state.

Once again, these are picked (however, for this problem there really aren't any other choices). In order to determine the scales, the physics of each situation is considered. There may not be unique choices, but there are best choices, and these are the "correct" choices. An understanding of what each term in the PDE represents is vital to identifying these "correct" choices, and this is notated below:

 * $$\underbrace{\frac{\partial \hat u}{\partial \hat t} \frac{u_s}{t_s}}_{\text{acceleration}} =

\underbrace{\nu \frac{\partial^2 \hat u}{\partial \hat y^2} \frac{u_s}{D^2}}_{\text{viscosity}} - \underbrace{\frac{P_x}{\rho}}_{ \begin{smallmatrix} \text{driving}\\ \text{force} \end{smallmatrix} }\,$$

For the velocity scale, a steady state condition is required. In that case, the time derivate (acceleration) must small. We could obtain the characteristic velocity associated with a steady state condition by requiring that the acceleration be something small (read: zero), stating that the second derivative is $$O(1)$$, and solving:

 * $$0 = \frac{u_s}{D^2} \cdot 1 - \frac{P_x}{\nu \rho} \Rightarrow u_s = \frac{D^2 P_x}{\nu \rho}\,$$

This is the same as the velocity scale found in the previous section. This is expected since both situations are describing the same steady state condition. The neglect of acceleration equates to what's called a balance between driving force and viscosity since driving force and viscosity are all that remain.

Getting the time scale may be a little more elusive. The time associated with achieving steady state is dictated by the acceleration and the viscosity, so it follows that the time scale may be obtained by considering a balance between acceleration and viscosity. Note that this statement has nothing to do with pressure, so it should apply to a variety of disturbances. To balance the terms, pretend that the derivatives are $$O(1)$$ quantities and disregard the pressure:

 * $$1 \cdot \frac{u_s}{t_s} = \nu \cdot 1 \cdot \frac{u_s}{D^2} + 0 \Rightarrow t_s = \frac{D^2}{\nu}\,$$

This is a statement that:

 * The smaller the viscosity, the longer you wait for steady state to be achieved.
 * The smaller the separation distance, the less you wait for steady state to be achieved.

Hence, the scale describes what will affect the transient time and how. The results may seem counterintuitive, but they are verified by experiment if the pressure is truly a constant capable of combating possibly huge viscosity forces for a high viscosity fluid.

Compare these scales to constants seen in the full, dimensional solution:

 * $$u(y, t) = \frac{D^2 P_x}{2 \rho \nu} \left(\frac{y^2}{D^2} - \frac{y}{D} - \sum_{n=1}^{\infty} e^{-\frac{\nu (n \pi)^2}{D^2} \cdot t} \cdot \frac{4 (-1)^n - 4}{n^3 \pi^3} \sin(\frac{n \pi}{D} y) \right)\,$$

The velocity scales match in order of magnitude, nothing new there. But examine the time constant (extracted from the exponential factor) and compare to the time scale:

 * $$\mbox{time constant} = \frac{D^2}{\nu (n \pi)^2} \quad ; \quad t_s = \frac{D^2}{\nu}\,$$

They are of the same order with respect to the physical parameters, though they'll differ by nearly a factor of 10 when $$n = 1$$. This result is more useful then it looks. Note that after determining the velocity scale, all three terms of the equation may have been considered to isolate a time scale. This would've been a poor choice that wouldn't have agreed with the time constant above since it wouldn't be describing the required settling between viscosity and acceleration.

Suppose that, for some problem, a time dependent PDE is too hard to solve, but the steady state version is easier and it is what you're interested in. A natural question would be: "How long do I wait until steady state is achieved?"

The time scale provided by a proper scale analysis will at least give an idea. In this case, assuming that the first term of the sum in the solution is dominant, the time scale will overestimate the response time by nearly a factor of 10, which is priceless information if you're otherwise clueless. This overestimate is actually a good (safe) overestimate, it's always better to wait longer and be certain of the steady state condition. Scales in general have a tendency to overestimate.

Before closing this section, consider the actual nondimensionalization of the PDE. During the scale analysis, the coefficients of the last two terms were equated and later the coefficients of the first two terms were equated. This implies that the nondimensionalized PDE will be:

 * $$\frac{\partial \hat u}{\partial \hat t} = \frac{\partial^2 \hat u}{\partial \hat y^2} - 1\,\,$$

And this may be verified by substituting the expressions found for the scales into the PDE. This dimensionless PDE, too, turned out to be completely independent of the physical parameters involved, which is very convenient.

Heat Flow Across a Thin Wall
Now, an important utility of scale analysis will be introduced: determining what's important in an equation and, better yet, what's not.

As mentioned in the introduction to the Laplacian, steady state heat flow in a homogeneous solid may be described by, in three dimensions:

 * $$\nabla^2 = 0 \qquad \xrightarrow{\mathrm{It's \ 3D.}} \qquad \frac{\partial^2 u}{\partial x^2} + \frac{\partial^2 u}{\partial y^2} + \frac{\partial^2 u}{\partial z^2} = 0\,$$

Now, suppose we're interested in the heat transfer inside a large, relatively thin wall, with differing temperatures (not necessarily uniform) on different sides of the wall. The word 'thin' is crucial, write it down on your palm right now. You should suspect that if the wall is indeed thin, the analysis could be simplified somehow, and that's what we'll do.

Not caring about what happens at the edges of the wall, a BVP may be written:

 * $$\frac{\partial^2 u}{\partial x^2} + \frac{\partial^2 u}{\partial y^2} + \frac{\partial^2 u}{\partial z^2} = 0\,$$

 * $$u(x, y, 0) = f(x, y)\,$$

 * $$u(x, y, D) = g(x, y)\,$$

$$D$$ is the thickness of the wall (implication: $$z$$ is the coordinate across the wall). Suppose that the wall is a boxy object with dimensions $$s \times s \times D$$. Using the box dimensions as scales,

 * $$x = s \hat x \, \quad y = s \hat y \ , \quad z = D \hat z \ , \quad u = u_s \hat u\,$$

Only the scale of $$u$$ is unknown. Substituting into the PDE,

\frac{\partial^2 \hat u}{\partial \hat x^2} \frac{u_s}{s^2} + \frac{\partial^2 \hat u}{\partial \hat y^2} \frac{u_s}{s^2} + \frac{\partial^2 \hat u}{\partial \hat z^2} \frac{u_s}{D^2} = 0\,$$

\left( \frac{\partial^2 \hat u}{\partial \hat x^2} + \frac{\partial^2 \hat u}{\partial \hat y^2} \right) \left(\frac{D}{s}\right)^2 + \frac{\partial^2 \hat u}{\partial \hat z^2} = 0\,$$

Note that the scale on $$u$$ divided out — so a logical choice must be made for it's scale; in this case it'd be an extreme boundary value (ie, the maximum value of $$\mathrm{max}(f, g)$$), let's say it's chosen and taken care of. Thanks to this scaling and the rearrangement that followed, we may get a good idea of the magnitude of each term in the equation:

\bigg( \underbrace{\frac{\partial^2 \hat u}{\partial \hat x^2}}_{\mathcal{O}(1)} + \underbrace{\frac{\partial^2 \hat u}{\partial \hat y^2}}_{\mathcal{O}(1)} \bigg) \cdot\underbrace{\left(\frac{D}{s}\right)^2}_{?} + \underbrace{\frac{\partial^2 \hat u}{\partial \hat z^2}}_{\mathcal{O}(1)} = 0\,$$

Each derivative is approximately $$O(1)$$. But what about the squared ratio of dimensions? This is called a dimensionless parameter. Look at your palm now (the one you don't write with), recall the word "thin". "Thin" in this case means exactly the same thing as:

 * $$\frac{D}{s} \ll 1\,$$

And if the ratio above is much smaller then $$1$$, then the square of this ratio is even smaller. Our dimensionless parameter is called a small parameter. When a parameter is small, there are many opportunities to simplify analysis; the simplest would be to state that it's too small to matter, so that:

\bigg( \underbrace{\frac{\partial^2 \hat u}{\partial \hat x^2}}_{\mathcal{O}(1)} + \underbrace{\frac{\partial^2 \hat u}{\partial \hat y^2}}_{\mathcal{O}(1)} \bigg) \cdot \underbrace{\left(\frac{D}{s}\right)^2}_{ \begin{smallmatrix} \text{really}\\ \text{small} \end{smallmatrix} } + \underbrace{\frac{\partial^2 \hat u}{\partial \hat z^2}}_{\mathcal{O}(1)} = 0 \quad \Rightarrow \quad \frac{\partial^2 \hat u}{\partial \hat z^2} = 0 \,$$

What was just done couldn't have been justified without scaling variables so that their derivatives are (likely) $$O(1)$$, since you have no idea what order they are otherwise. We know that each derivative is hopefully $$O(1)$$, but some of these $$O(1)$$ derivatives carry a very small factor. Only then can terms be righteously dropped. The dimensionless BVP becomes:

 * $$\frac{\partial^2 \hat u}{\partial \hat z^2} = 0\,$$

 * $$\hat u(s \hat x, s \hat y, 0) = \hat f(s \hat x, s \hat y)\,$$

 * $$\hat u(s \hat x, s \hat y, 1) = \hat g(s \hat x, s \hat y)\,$$

Note that it's still a partial differential equation (the $$x$$ and $$y$$ varialbes haven't been made irrelevant – look at the BCs). Also note that scaling on $$u$$ is undone since it cancels out anyway (the scale could've still been picked as, say, a maximum boundary value). This problem may be solved very simply by integrating the PDE twice with respect to $$z$$, and then considering the BCs:

 * $$\int \frac{\partial^2 \hat u}{\partial \hat z^2} \ d\hat z = 0\,$$

 * $$\int \frac{\partial \hat u}{\partial \hat z} \ d\hat z = C_1(s \hat x, s \hat y)\,$$

 * $$\hat u(x, y, z) = z C_1(s \hat x, s \hat y) + C_2(s \hat x, s \hat y)\,$$

$$C_1$$ and $$C_2$$ are integration "constants". The first BC yields:

 * $$\hat u(x, y, 0) = \hat f(s \hat x, s \hat y)\,$$

 * $$0 \cdot C_1(s \hat x, s \hat y) + C_2(s \hat x, s \hat y) = \hat f(s \hat x, s \hat y)\quad

\Rightarrow C_2(s \hat x, s \hat y) = \hat f(s \hat x, s \hat y) \,$$

And the second:

 * $$\hat u(x, y, 1) = \hat g(s \hat x, s \hat y)\,$$

 * $$1 \cdot C_1(s \hat x, s \hat y) + \hat f(s \hat x, s \hat y) = \hat g(s \hat x, s \hat y)\quad

\Rightarrow C_1(s \hat x, s \hat y) = \hat g(s \hat x, s \hat y) - \hat f(s \hat x, s \hat y) \,$$

The solution is:

 * $$\hat u(x, y, z) = z \cdot (\hat g(s \hat x, s \hat y) - \hat f(s \hat x, s \hat y)) + \hat f(s \hat x, s \hat y)\,$$

It's just saying that the temperature varies linearly from one wall face to the other. It's worth noting that in practice, once scaling is complete, the hats on variables are "dropped" for neatness and to prevent carpal tunnel syndrome.

Words of Caution

"Extreme caution" is more fitting.

In the wall heat transfer problem, we took the partial derivatives in $$x$$ and $$y$$ to be $$O(1)$$, and this was justified by the scaling: $$\hat x$$, $$\hat y$$ and $$\hat u$$ are $$O(1)$$, so the derivatives must be so as well. Right?

Not necessarily. That they're $$O(1)$$ is a linear approximation, however if the function $$u(x, y, z)$$ is significantly nonlinear with respect to a variable of interest, then the derivatives may not be as $$O(1)$$ as thought. In this problem, one way that this can happen is if the temperature at each wall face (the functions $$f(x, y)$$ and $$g(x, y)$$) have large and differing Laplacians. This will result in three dimensional heat conduction.

Examine carefully the image at right. Suppose that side length is ten times the wall thickness; $$f(x, y)$$ and $$g(x, y)$$ have zero Laplacians everywhere except along circles where temperatures suddenly change. At these locations, the Laplacian can be huge (unbounded if the sudden changes are discontinuities). This will suggest that the derivatives in question are not O(1) but much greater, so that these terms become important even though in this case:

 * $$\frac{D}{s} = 0.1 \Rightarrow \left(\frac{D}{s}\right)^2 = 0.01 \ll 1\,$$

Which is as required by the scale analysis: the wall is clearly thin. But apparently, the small thinness ratio multiplied by the large derivatives leads to significant quantities.

Both the exact solution and the solution to the problem approximated through scaling are shown at the location of a cutting plane. The exact solution shows at least two dimensional heat transfer, while the solution of the simplified solution shows only one dimensional heat transfer and is substantially different.

It's easy to see why the 1D approximation fails even without knowing what a Laplacian is: this is a heat transfer problem involving the diffusion of temperature, and the temperature will clearly need to diffuse along $$x$$ near the sudden changes within the wall (can't say the same about the BCs since they're fixed).

The caption of the figure starts with the word "failure". Is it really a failure? That depends on what you're looking for, it may or may not be. Note that if the wall were even thinner and the sudden jumps not discontinuities, the exact and 1D solutions could again eventually become indistinguishable.


text:
User:Curtbeckmann~enwikibooks

Contact:
 * home wiki: http://www.Appropedia.org
 * blog: http://wannaresolution.blogspot.com
 * email: Click "E-mail this user" in the toolbox at left

title: User:Curtbeckmann~enwikibooks