text:
Editing Wikitext/Pictures/The Quick Course

The Quick Course
his first Pictures page is intended for a quick study or for revision and will not bore you too much with discussion.. This page will show a Wiki writer how to fit images into their work using the most usual layout methods. For those who need only a coding summary, go straight to the image code examples in the drop-box of the section Insert the Image Code. A summary of image code options can be found in the section Adjust the Options. For those who need more complicated methods, for example, tables, gallery, or drop-control methods, refer to the Other pages links.

As the reader will realize, formatting in Wiki uses Wikitext mark-up code. To make the learning task a bit easier, code modules have been prepared for the various parts of the work. At various points in the text there are panels or drop-down boxes that contain the blocks of code. The code is easily pasted into the, to try the formats for yourself. As a general rule, the best method for new formatting is to carry out the testing of your ideas in the safety of the Sandbox, before pasting them into your work.

Find a Wikimedia Image
Many thousands of images are already stored in the Wikimedia Commons image database. The main pieces of data to obtain about the image are its exact name and its copyright status, and these and other image details can be found in two ways.

 * The first method makes use of image lists on the Wikimedia Commons website.  The same images that were in the past to be found using the Mayflower search engine are now found in categories on the  Wikimedia Commons.   This site has various categories to browse, including Wikimedia Public Domain Images, and many others.   Collect the details, name, size, etc, of any images that interest you, ready for working on your page.
 * The second method is simply to get the details of an image that you like from some other Wiki page.  (Wikipedia or Wikibooks). To find all of the details of any image on a Wiki page, just left-click it with the mouse to go to its image description page. If you just need to know the name or the rendered size of an image on a page, then right-click the image and read the details in the image properties.

Finally, because users might need some samples to study image layouts, the drop-box below has a set of code lines that can be used to produce high quality images in either your pages or while experimenting in the. You can modify these lines of code at will, on any page, to see how their options affect the display.

Upload Your Own Image
our own images can be uploaded to the Wikimedia Commons image database, for use on any Wikibooks page. In fact, they will become available to any user. It works like this.

The edit this page version of each Wikibooks page, including this page's edit page, has a link in its margin called Upload file, but images can only be uploaded by users who are first logged-on. Following that link leads to the Commons upload pages, where instructions can be found. Perhaps the best current method of making an upload is to access the Wikimedia Commons home page, then by selecting the Upload file link it its left margin, you can follow your way through the upload wizard, making life much easier.

When there is a choice, images are best uploaded in the largest available size. This gives the user the greatest possible choice as to its dimensions on the page. Images can always be reduced in size on the work pages themselves, by specifying their sizes in pixels within the mark-up code. As soon as an image is uploaded, its own dedicated image page is shown. This page repeats all of the data given by the contributor, including the copyright status. Once the image file is uploaded, it is available immediately for use in your work, and by others.

Insert the Image Code mages are placed on a page by typing an image code along with any other text. As with the typing of text, this is done in the editing window of the page being edited. Selecting the edit this page tab at the top of the page accesses the editing panel, and all of the user's preferences and other links can be found at the top of each page as soon as the user signs-on.

The Basic Image Code
Without more ado, this section introduces the most comprehensive image code first. It contains all of the features likely to be of interest to the writer. The standard form includes an image name and file type suffix, a page position, a border type, an image size, and a caption.

The vertical-bar separators in the code are called pipe symbols. It is important to learn where these are on the keyboard since they are used in all image work. On some keyboards they are not located in the marked positions. Shift-backslash and Ctrl-Alt- top-left are common locations on keyboards for this symbol. In any case, if it cannot be found on the keyboard, there is a selection of such symbols to copy, at the bottom of each editing page. The standard form for the most useful image code looks like this:

The practical format of a typical image line, suitable for a page is like this:

The image to the right of this text was made with the above code line. The coding makes an image at the right margin of the page, (right). It is in the style of a thumbnail, (thumb), which by default, has a border; there is a link to its image page. It has a base dimension of 200 pixels, (200px), and a caption beneath the image, within the border, (Pink Gerbera). If the caption were made longer, then the text would wrap neatly on several lines. The text of the page itself wraps neatly around the image also. In fact, depending upon the position of the image code line on the page, the point from which the accompanying text starts to wrap can be changed. This point will become more clear with the examples in the drop-box below. Beware of transferring your work from word processors, since some characters may not be supported by the Wiki editor. If in doubt, first copy the code into the Sandbox for testing. To back-up your unfinished mark-up code, you can copy your text from the sandbox editing window and save it in Notepad, the windows accessory. Notepad is a plain text device, and affects the mark-up code least. Note also that all of the saved page versions are available in the History tab, should they ever need to be restored to the form that existed at an earlier date.

The basic image placement examples are given in the drop-box below: When such a line of image code is in place, press the Show preview button at the bottom of the editing window and wait for the system to display the reformatted page. If the image position is left or right then the text will be seen to wrap. If the center is selected, (or none), then the text cannot wrap, and the text will move to a point below the image.

In any case, if the rendered result is not as expected, then the text can be changed as often as is necessary, until it is right. When the work is right, press the Save page button at the bottom of the page to store the revised page for other web users to see.

Adjust The Options
hese notes describe the image options in detail, and are correct at the time of writing.

The sequence of image options is unimportant, and with the sole exception of the image name these entries are insensitive to case. However, it is recommended that a size is always included, to avoid enormous image sizes. The general coding format and the most useful options for the image syntax are again given below:

 * When position is not specified...: The default position is right when the border type is set to frame or thumb, else it is left.
 * The position options...: These are right, left, center, or none.
 * To wrap text around images...: Choose either the left or right image positions, or one image set to each, for wrapping between two images.
 * To force text to follow-on...: Choose center or none since these cannot wrap text.
 * To fix an image without wrapping...: Choose none. This forces the image onto a new line at the left.
 * For an image in a table cell...: Set the position to center within the image code, and if necessary, set the vertical position with a CSS style in the respective table element.
 * Additional note...: The positioning of images at left, right, and center, when there is a similar image already occupying some space, can result in these terms being interpreted as relative to the remaining space. These images are said to float.   By contrast, an image set to none is non-floating, and it does not permit anything alongside it.

 * When type is not specified...: An image with no border is produced.
 * The type options...: These are thumb, frame, or border.
 * For a border, caption, and scaling...: Use Thumb since it has the most scope.
 * For a border, caption, but no scaling...: Use Frame, but only for same-sized images.
 * For a very faint border...:Use border. This is useful when an otherwise border-less, pale image needs a slight color separation from a pale background.
 * Make a user-sized thumbnail on the right...:Set thumb with only the image details. The size will be set in accordance with the user-set preferences.  The size will be seen locally, and others will see their own, or its default.
 * Images on colored backgrounds...: Avoid thumb, since an unwanted white margin might be seen. Consider the use of a frame-less image to avoid it.
 * Images for table cells...: These should be border-less.  There are problems with framed image captions, and the borders are best made with table properties.
 * Image captions...:These are possible only with thumb and frame, though the template set Noframeleft, Noframeright, Noframecenter, and Noframenone permits captions for frame-less images and gives more scope in the making of custom borders.

 * When size is not specified...:The image will be full-sized, and in most cases would be too big.  However see comments about user-set thumbnail type.
 * Resizing an image...: This is possible for all option types except when the frame type is chosen.
 * Units of image measurement...:The units used for images are pixels, and the size of an image applies to the image only; any borders add to the overall layout.
 * There are two image size formats...: The required image size can be specified as just its width, or as its width and height.  It cannot be specified as height alone.
 * The single size format...: This is the pixel size of the image's base, with the shape preserved.  Screens render images as about 70 to 100 pixels to the inch.  A typical entry is e.g. 240px.
 * The double size format...: This is the base dimension times the height, e.g. 240x150px, when both are known.
 * When there is an inconsistent dimension given...: That is to say, when one of a pair of dimensions seem to be trying to change the shape, only the smaller of the two possible image sizes is produced.
 * Equalizing heights of mixed image shapes...: Knowing the exact dimensions is unnecessary. For example, to equalize the heights of mixed-shape images, use the double format with all of the size code set for the required common height, and their widths greatly exaggerated. This forces an inconsistent scaling that achieves the required result. For example, two images that are 350x150px and 700x450px are clearly of different shape.  To display the two side by side, both with a height of 100px, we set their image code to say 900x100px and 900x100px.   The obvious 900px inconsistency is ignored and the 100px is taken as the useful dimension for scaling.   The shape of each image will nonetheless be preserved without having to re-calculate the exact dimensions.

 * When caption is not specified...: Only thumb and frame permit captions, and they can be omitted to leave an empty space.
 * Format caption text...:Use HTML tags, Wikitext and hyperlinks to format captions.
 * Use text templates ...: Templates can be used to format captions. They can reduce the effort and add consistency to the appearance.
 * Options that are not recognized...: When an image option is misspelled or otherwise not understood, it will be taken as a caption, or as alternative text for the image placeholder.  When there are two possibilities only the first is taken.
 * What is alternative text?...:The empty box for an image is called a placeholder, and text can sometimes be found in it; this is the alternative text. When the image is not available, or when software for the disabled reads the page, this text can be used.
 * Alternative text or captions...:  When captions are impossible because of the border type, an attempt at adding a caption is taken as alternative text.   When a caption is possible, it is also used as the alternative text.  Having different captions and alternative texts in images is not possible.

Use Image Templates
here are occasional inconveniences in the use of the basic image syntax.

These points, when necessary, can be overcome by displaying the image within a template. In particular, the Wikibooks templates Noframeleft, Noframeright, Noframecenter, and Noframenone were made for this purpose, and images made with them behave in much the same way as the basic image examples.

Each template in the set is made for the appropriate position on the page. Two examples of template use can be seen on the left and the right of the page; The left image is an example of a frame-less image with a caption and was made with Noframeleft. The image on the right was given a border with Noframeright. Compare the absence of white margins with the orchid and gerbera images shown elsewhere on this page.

The code to make use of these templates for this specific result is just:

It should be stressed that the white margins for thumbnails do not pose any problems for the default page coloring, and that colored backgrounds are comparatively rare in the Wikibooks project.

Find Other Methods
here are other image layout techniques. The tiling of images is covered in Tiled Images, and explains how to overlap images and how to line them up across the page. A separate page on image containers has been provided at Images in Containers, and gives methods for tables, galleries and drop-down boxes. For example, the top section of this page is made with an invisible table container, and the colored background is made by placing the page within styled HTML div tags.

As was described in the previous section, writers have developed templates. Examples include caption-making, text-formatting, and image placement. Templates allow laborious formatting to be done without the need for the coding that usually accompanies such work. The writer need only add text to a few key words for the formats to be added automatically.

Specific examples of templates in use may make the point more clearly. The drop capitals on this page make use of a template called Drop. The what to type panels of whatever color use the template Block, and the drop-control boxes for the examples use Dropimage. The template Hiddenh3 has made various hidden headings, headings with the correct formats but without a listing in the table of contents.

It is not proposed here to explain template making but rather to provide a link to a page that does so. See Templates A101. To see a few examples of existing templates, see Templates Ready to Use.


text:
Editing Wikitext/Pictures/Tiled Images

{{thetop|ha1=center|bd=floralwhite|w2=37%|w3=38%|1= {{tocbox|width=150px|align=center|Other pages|The Quick Course Images in Containers}}|2={{caption|Pelargonium: | 'Geranium'; 300x225 pixels}}|3={{caption|Pink Gerbera: | 300x225 pixels}}|trailer=

All in a Line
mages are easily placed in a line without the use of an image container, and most associate this kind of line-up with the notion of floating images; that is to say, if one too many of these images is added, the last one will just float to another page position rather than anchoring itself where it was put. The simplest method for an image line-up depends on limiting the image options to the minimum. Specify only the image names and their sizes, and disregard all other options, otherwise the method might become problematic. The image syntax can be written all in one line, or in successive lines, and an example of the coding to use has been included in a drop-box for the adjacent line-up of images.

Notice that the example shown has no captions, since captions can only be used in the frame or thumbnail format. However, by using templates such as Noframeleft for the images in such a lineup, tiled images with captions can be obtained. A set of these templates has been made to include all of the image positions.

A thin dividing space has been made between adjacent images by inserting a single space character between the image definitions. To set the images edge to edge without any space between them, simply omit the space characters. Because we rarely want to start an image line-up at the left margin of the page, it is useful to have a means of padding out the images. In fact, a transparent, blank image has been uploaded to the image collection for that purpose; it is called  Padding.gif , and it can be sized on the page like any other image. Refer to the code notes for an example of its use. (Another method, capable of precise positioning, is described in the next section). Images are rarely the size that you would prefer them to be and this is especially the case when the images are set side by side. There is a method to get the images standardized. Consider the image line-up. Because these images were greatly different in their initial shapes, and their exact dimensions were laborious to find, it was decided to set their heights to be the same, and to allow the widths to be scaled accordingly. The method to do this, shown in the code box below, is to specify the important dimension exactly, in this case the height, while greatly exaggerating the size of the less important dimension, the width. Note that some dimension for width is required, but its exact value need not be known. The software will use the smaller and more practical possibility, ignoring the implied larger scaling. In this way the vastly different shapes can be scaled without having to make calculations based on both width and height.

Relative Positioning
ost image positioning is restricted to the three preset locations. These of course are, left, right, and center. However, with the help of a little in-line HTML, images, tables, text paragraphs and other structures can be placed anywhere on the page. In particular, this means that an image can be placed at a point relative to its position as expected by other code. To explain further, if the usual position for an image is at the left margin, according to the syntax used, then the addition of relative positioning code allows it to be shifted relative to that point, up or down, right or left, even beyond the margin. The pixel values for the vertical and horizontal shifts specify the exact extent of the displacements.

The main problem with this method, apart from its complexity, is that it will not deliver wrapped text for the placements. Like centered images, the text is restricted to following-on. Another problem concerns frames for the images; because shifting is applied to images within their immediate containers, all types of borders must be avoided. As a result of losing frames and thumbnail borders, all of the captions have to be arranged by other means.

To expand on the matter of text having to follow-on, it is perhaps helpful to note the sequence of events for relative positioning. When the image, box or other structure is first placed, it is allocated to the space without relative positioning; that is, as if the shifting code were missing or set to zeros. Then the code shifts the item to its new position by the amounts given by the shifting code. A space is left at the first location, equal in size to the item that was moved. When the next line of text or another item is added to the work, it must take account of that allocated space. As a result, when a large image or block of text is moved vertically, the following text cannot be located until after the gap.

Although it is theoretically possible to shift tables and large blocks of text, the above mentioned limitation renders it less useful. Relative positioning works best when the shifts and texts are fairly small. The method meets these requirements for shifting images that are initially tiled across the page, and for overlapping effects.

An example of overlapping images is given below. The normal position for these images, without shifting,would have been in-line, starting from the left margin, and the padding image has been omitted for this example. The images were shifted from these tiled positions by the required amounts to create the overlapping effect.

The paleness or density of images can be varied. The code for twenty percent opacity can be found in the drop-box along with an example of shifted text.

 This is the text.

Mouse-hover Images
Two images can occupy the same space provided that only one of them is seen at a time. The usual way to do this is to hover the mouse over the default image, the one that is stable and seen most of the time. When this is done the alternative image replaces it, and when the mouse is removed, the original image reappears.

This technique is available using the template HoverImage. The names of the two images are provided to the template, along with any other image options, and two separate captions can be made. The method works best with images that are the same shape; that is, have the same aspect ratio. Then, with one base size setting, both will be scaled to the same size. When the shapes differ and the images change, the height or the width of the presented work changes too. Because the text adjusts in wrapping around the images the effect is not necessarily bad, and you can see this best for yourself by trying it in the sandbox. As was suggested elsewhere on this page, a method exists to allow fixing of image heights instead of widths, and this might suit some better.

In all other respects the template can be used as if it were a single image, with for example, text wrapping for the left and right positioned images. The template can be used in any situation that needs the full image syntax; for example, it could not be used to build gallery entries, since these use only an abbreviated image syntax; the image name. It could be used on a page, within tables and drop-boxes, and anywhere else that can make use of the full image syntax.

The image on the right shows an example of the template's use; more detailed notes can be found on the page Templates Ready to Use, and on the template page itself.

Other Pictures Pages

 * The Quick Course
 * Images in Containers

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

title: Editing Wikitext/Pictures/Tiled Images


text:
Editing Wikitext/Pictures/Images in Containers

Images in a table
n-line, tiled images are simple to do, though they lack the positional stability of images in table cells. Although the matter rarely becomes important for images placed at the left or right of a page, when a more ambitious layout is needed, tables come into their own.

Tables allow many formatting options but do require some knowledge of Wiki's table-making code. To learn how to make tables see the page Tables, and to remind yourself of the styles used, see the drop-box later on this page.

After trying different methods, it is found best to use a table with two rows; one for the images, and the row below that for their captions. This allows the captions to be formatted separately from anything in the image cells and generally gives the best flexibility in working. When table borders are removed in such an arrangement, the images seem to stand on their own without the table being visible at all. The first example below uses this method, with the mark-up code for its implementation shown nearby.

To space out the images across the page against the prevailing background it is best to add extra columns to the tables. Do this by adding extra cells in the existing rows, and set their widths to achieve the necessary spacings. To avoid the need for additional styling of the table's background it can be made transparent. In this way the page color shows though, regardless of what color is set. An example using these points is shown, and the code to produce it is also displayed nearby.

For those who find tables a bit awkward to use, the image gallery may be more to their liking. It is much simpler, and quite good results are to be had without formatting. It is described below with varying complexity.

In addition, the images at the top of this article are both housed in table cells, with the table of contents, (TOC), in another; this was deemed necessary to constrain the positioning of the TOC in its various contortions. The code can be found in the drop-down box and if required, can be pasted into an editing window, or the Sandbox for modification. For those who are unfamiliar with table handling, a set of templates, Imageontop, Image1ontop, Image2ontop, and Image3ontop,have been prepared and allow the user to make similar top sections to the one on this page. If the requirement is just for a table of contents with text all the way to the top, then use the template Textontop.

The Image Gallery
onsider the three image gallery examples in the drop-down box. In the most simple example of its use, the user need not even scale the images, and need not know their sizes. The software makes all of the calculations and adjusts all of the dimensions to fit the images neatly into the gallery layout. Captions are available for both the images and the gallery itself, and any reasonable number of images can be added, with each image's coding typed onto a separate line. If required, a small amount of text can be inserted instead of an image.

The first example is the simplest and is ordered in rows of four images. This four-to-a-row format is provided by default, but can be adjusted as will be shown in the second example. Blank places are left for any unused image space in a row, e.g.; for a gallery of seven images, there would be one blank space in the second row. Although this gallery uses an HTML align attribute in an attempt to center it, centering has failed within the drop-box and it merely appears to be centered because it is the widest inclusion, and has simply been expanded to the size that is needed by this block element.

There are problems with the centering of the gallery function within a drop-box, though not necessarily when galleries are used on the open page. The problem seems to be connected with the use of the HTML align attribute. It is likely that a CSS style in a style sheet has invoked a priority in drop-boxes over the use of an HTML attribute. However there is a way to overcome the problem within a drop-box; in the second example below the HTML align attribute has been replaced by CSS styles for width and margin, and the use of this alternative styling overcomes the problem. The method can use percentages as dimensions to allow for different container (screen) widths, but the styles need careful adjustment for each gallery that is to be displayed. Notice too that whereas the relative percentages for values of width always refer to the immediate container, the values used for margin refer to percentages of the table width. Once the point is understood, there is rarely any confusion.

Note the use of the CSS width style; this allows an adjustment of the image masks; e.g., by setting a gallery width, any difference between it and the width calculated for the layout, is adjusted by changing the widths of the image masks.

In the second example, row height, column width, and the number of images per row have been added as options. In this way the layout can be changed greatly, and in this particular case, the display made smaller. The position is centered, using CSS styles. Since some viewing screens are narrower than others, reducing the number of images across the gallery with this method helps to keep the whole thing visible at the same time.

In the third example, many other font and formatting options have been added. These formats use many style-sheet rules. (See CSS2 Properties Reference  for more). In this way all of the font family, style, color, etc., can be adjusted, as well as the text padding. Some properties remain obstinate; the notion of background color does not extend to the off-white photo mask, but can work on the space between the border and the mask. In addition, some slight difference in appearance for backgrounds has been noted between galleries on a page and galleries in a drop-down box.

The Wikitext markup code used to produce the three results is given in another drop-down box with descriptive notes. The modules can be copied into the Sandbox  for further testing and use. Bear in mind that not all of the available text rules have been included. There is some distance still to go in experimenting with useful formats, and some kind soul might even devise a way to expose the photo mask for background coloring.

Drop-down Images
t can be useful to save space or to un-clutter a page. For all the space saving qualities of tables or the gallery, it can be useful to save even more. An image or even a gallery of images can be tucked away in a drop-down box. The display will appear when the bar is clicked with the mouse; clicking it again closes the control and restores the page to a more tidy state.

For those writing within WikiBooks, there is a template ready-made to make things easy. Refer to Template : Dropimage  for its use, limitations, and options. All of the drop-boxes on this page made use of it.

For those who write within Wikipedia there is also a version of Dropimage. In addition, for Wikipedia, Wikimedia, and WikiBooks, there are collapsible tables. See Collapsible Tables, and Tables, for the details.

Whether the enclosure is text, an image, an animation, or a whole gallery of images, the method of using the Dropimage template is the same. The code that will produce the text, image, or gallery is placed in the last parameter space, and the message for the top heading goes into the first parameter. Although it is sometimes found useful to use the named parameter method, (2=parameter text), for most text and images it will be OK to just place the material as it is. If the parameter text is very complicated, it is often a good idea to view it first on its own to make sure it is as expected.

Avoid using Wiki heading codes for your first characters since this messes things up; i.e.; use the HTML   tags instead of the equals signs. If your intention is to place a table in a drop box, be sure that it is an HTML table, since the pipe symbols of a Wiki table might be misinterpreted. Refer to the WikiBooks  page for an example.

The typical syntax for the Dropimage template and its result are shown below.

When previewed in a page being edited or in the Sandbox, the above code block makes a drop control identical to the one above; the control is centered, has a top caption of Press me !, and an inside caption also. The initial width of the control is 120 pixels, though the image within it is greater, with a base width of 200 pixels. Take time to change the image and the other settings to see how the template works.

WikiBooks templates will work in other projects, such as Wikipedia, provided that they are first imported by their administrator, though in the case of Dropimage it was easier to simply reproduce it there instead.


text: Category:Book:English as an Additional Language


text:
Talk:Ido/Lesson III4

Untitled
This page is a stub. Do not delete! Lakaoso (talk) 17:39, 30 March 2008 (UTC)

title: Talk:Ido/Lesson III4


text:
Proteomics/Proteolytic Processing

Previous chapter: Proteomics and Drug Discovery

 * 1) Introduction
 * 2) Proteomics/Proteolytic processing/Proprotein
 * 3) Proteomics/Proteolytic processing/Specificity of proteolytic processing
 * 4) Proteomics/Proteolytic processing/Proteolytic processing in Secretory Pathway
 * 5) Proteomics/Proteolytic processing/Examples of proteolytic processing in various organs of our body
 * 6) Proteomics/Proteolytic processing/Proteolytic processing of the Human Immunodeficiency Virus type 1
 * 7) Proteomics/Proteolytic processing/Proteolytic processing- role in therapeutics
 * 8) Proteomics/Proteolytic processing/Autoprocessing
 * 9) Proteomics/Proteolytic processing/Lethal effects of proteolytic processing

title: Proteomics/Proteolytic Processing


text:
Proteomics/Proteolytic processing

Introduction
Proteolytic processing in the broad sense means a protein or a protein complexing processing another protein or protein complex to modify its activity. This processing may lead of activation, inhibition or modulation of the protein activity. Much of the cellular processes are triggered by proteolytic processing. Proteolytic processing is the major part of post translational modification of a protein to make a functional protein complex.

Next section: Proteomics/Proteolytic processing/Proprotein

title: Proteomics/Proteolytic processing


text:
Khepera III Toolbox/Examples/odometry calibration

In this tutorial, you will learn how to calibrate the odometry of your robot. There are various ways to calibrate the odometry of a differential-drive robot. The procedure we show here is perhaps not the most precise, but certainly one of the simplest to quickly get decent calibration values.

Odometry in a Nutshell
Your Khepera III robot is equipped with two DC motors with an encoder each. These encoders allow to obtain the current position of the robot in very small increments (~ 2760 steps for one tour of the wheel). By recording how the wheels turn, it is possible to estimate the trajectory of the robot. This procedure is commonly termed odometry (or position estimation with odometry), and implemented in the program odometry_track.

The major problem of this procedure is error accumulation. At each step (each time you take an encoder measurement), the position update will involve some error. This error accumulates over time and therefore renders accurate tracking over large distances (> 10 m) impossible. Over short distances (< 1 m on a flat surface), however, the odometry can provide extremely precise results.

To get these good results, it is crucial to calibrate the robot. Tiny differences (~ 1 micrometer) in wheel diameter will result in important errors after a few meters, if they are not properly taken into account. Note that each robot (if you have several of them) has to be calibrated individually, preferably on the same type of floor it is being used later on.

Setup
Boot a Khepera III robot and make sure it is connected to your computer via WLAN. In the following text, we assume that you are working with robot 203.

You will need a couple of motor programs and the odometry_goto program for the calibration. Copy these onto your robot with cd Programs k3put +203 motor* odometry_goto Log onto the robot (k3go +203) and initialize the motors: cd your_username ./motors_initialize You are now ready to calibrate the odometry of your robot.

Odometry Calibration
There are 3 free parameters in a differential-drive system which have to be known to estimate the position using odometry:
 * The distance per increment (conversion factor) for the left wheel.
 * The distance per increments (conversion factor) for the right wheel.
 * The distance between the two wheels (axis length).

As these parameters are difficult to measure directly, we will instead measure 4 parameters which allow us to derive the parameters above. These 4 parameters, in the order we measure them, are: The necessary parameters can then be derived as follows: distance_per_increment_left = wheel_diameter_left * scaling_factor * 2 * PI / increments_per_tour distance_per_increment_right = wheel_diameter_right * scaling_factor * 2 * PI / increments_per_tour axis_length = axis_wheel_ratio * (wheel_diameter_left + wheel_diameter_right) / 2 * scaling_factor These equations are implemented in calibration.pl, which will create a calibration file and upload it on a robot.
 * 1) increments_per_tour: The number of increments per wheel tour.
 * 2) axis_wheel_ratio: The ratio between the axis length and the mean wheel diameter.
 * 3) diameter_left and diameter_right: The two wheel diameters, up to a scaling factor. (Actually, the ratio between the two wheel diameters - this is why these two values count as only one parameter.)
 * 4) scaling_factor: A scaling factor.

Step 1: Increments per Wheel Tour
The number of increments per wheel tour is a constant, depending only on the encoder and the gearbox used. For the Khepera III robot, this value is 2764.8 (4 * 16 * 1.6 * 27).

You can experimentally verify this number by marking the wheels at one point, and let them move by this number of steps: ./motor_setposition 0 0 ./motor_gotoposition 2765 2765 Your marker should be back at exactly the same position.

Step 2: Ratio between Axis Length and Wheel Diameter
Both axis length and wheel diameter can only be measured approximately with standard measurement tools. However, their ratio can be measured very precisely by letting the robot turn on the spot and counting the number of steps. This number divided by 2764.8 directly yields the ratio we are looking for. Of course, to get a more precise value, we will let the robot make several rotations.

From rough measurements with a ruler we know that this ratio is about 2.11 (88.5 mm / 42 mm), so let's start with this value and let the robot turn 10 times on the spot. The position value for that would be: 10 * 2.11 * 2764.8 = 58337.28 Put the robot on the ground, mark its orientation, and type: ./motor_setposition 0 0 ./motor_gotoposition -p 58337 -58337 The -p option will enable the trapezoidal speed profile. Once the robot has stopped, it should have almost the same orientation as in the beginning, but is likely to be a few degrees off. Play with the position value until it has exactly the same orientation (as far as you can judge visually). Once you've found a good value (assume it was 58255), just do the math backwards to find out the ratio: 58255 / (10 * 2764.8) = 2.1070

If you want to get a more precise value, you can repeat the above experiments with 100 turns.

Step 3: Wheel Diameters
To experimentally find out diameter differences between the two wheels, we will load our current odometry model onto the robot and then let it move around in your arena while keeping track of its position. At the end, we let the robot move back to where it thinks it started, and note the offset with the real initial position.

To to start with, we need to upload the current odometry values. Edit calibration.pl and execute it: ./calibration.pl If you set a robot IP address inside this script, it will upload the odometry values onto the robot. (Note that any existing odometry values there will be overwritten without merci.) Otherwise, you have to edit the file /etc/khepera/odometry on the robot by yourself.

The odometry_goto program which you uploaded at the beginning will now use these values to keep track of the position. Put the robot in an open area with at least 1 m space around it, mark its position and type: ./odometry_goto position 1 0 1 1 0 1 0 0 The robot will now move to all corner points of a square with 1 m width, and hence cover a distance of about 4 m. At the end, the robot believes being back at the initial position (with a different heading, though), but is most likely up to 30 cm off. Compare the final position with the initial position (disregard the heading), and ajust the wheel diameter difference as follows:
 * If the robot is on the right of its initial position (i.e. the square is not closed), increase the diameter of the right wheel by increasing the wheel_diameter_difference in calibration.pl.
 * If the robot is on the left of its initial position, increase the diameter of the left wheel by decreasing the wheel_diameter_difference in calibration.pl.

Then, upload the new odometry values and repeat this step until the distance between the initial and final position is less than 5 cm. If you have enough space, you can increase the size of the rectangle to get more precise measurements.

Step 4: Scaling Factor
The scaling factor is again very easy to find out. Put the robot on your floor, which an open area of 1 m in front of it, mark its initial position and type: ./odometry_goto position 1 0 The robot will stop approximately 1 m in front of its initial position. Measure that distance precisely with a measuring tape, and calculate the corresponding scaling factor as follows: scaling_factor = real_distance / 1 m You can of course choose a longer distance if you have enough space.

Adjust the scaling factor in calibration.pl, and execute that script again to upload the newest odometry calibration values onto the robot. Your robot is now calibrated!


text:
Proteomics/Proteolytic processing/Proprotein

ProProtein
Protein in its inactive state is called proprotein. Proproteins are converted into active protein by many post translational modification steps among them the most important being proteolytic processing.

Next section: Proteomics/Proteolytic processing/Specificity of proteolytic processing


text:
Talk:Proteomics/Proteolytic Processing

Chapter edited and updated by: Priyanka Yadlapati and Vrunda Sheth

Contact pxy8519@rit.edu, vns4483@rit.edu

title: Talk:Proteomics/Proteolytic Processing


text:
Proteomics/Proteolytic processing/Specificity of proteolytic processing

Specificity of proteolytic processing
Proteolytic processing is highly specific process. Mechanism of proteolytic processing varies according to the protein being processed, location of the protein, and protein processing it. There is no general rule of the thumb for proteolytic processing. This section therefore gives examples of different proteolytic processing approaches to get the basic idea

Next section: Proteomics/Proteolytic processing/Proteolytic processing in Secretory Pathway


text:
Proteomics/Proteolytic processing/Proteolytic processing in Secretory Pathway

Proteolytic processing in Secretory Pathway
Proteolysis of Precursor proteins regulates many cellular processes like gene expression, embryogenesis, cell cycle, programmed cell death, intracellular protein targeting and endocrine/neural functions. All these processes needs proteolytic cleavage of the precursor protein and in this context this can be done by serine proteases in the secretory pathway. These proteases are calcium dependent serine endoproteases and are related to yeast and subtilisin proteases and therefore called Subtilisin-like Proprotein Convertases (SPCs) or PCs. Till now they identified & characterized seven members of this family in mammals and they have conserved signal peptides, pro-regions, catalytic and P-domains but they differ in C-terminal domains. These proteases get activated by autocatalytic cleavage of an N-terminal propeptide just like Subtilisin which is required for folding and activity. Studies predict that an eight-stranded beta barrel is formed due to folding of the P domain which interacts through a hydrophobic patch to a catalytic domain. Folding and activity requires a downstream domain of 150 amino acids named P- or Homo B-domain which plays a regulatory role, influencing both the calcium dependence and pH optima. Here the C-terminal regions play a minor in subcellular routing. Furin, one of the seven members of the SPCs, serves as a model for other PCs. The autoactivation mechanism involves intramolecular cleavage of prodomain that allows furin to exit the endoplasmic reticulum (ER). Until the cleaved inactive proenzyme reaches the trans Golgi Network (TGN) where dissociation of prodomain is facilitated by calcium-enriched environment and acidic pH conditions, the prodomain remains attached noncovalently to it. For full activation, further inhibitory reactions takes place within the prodomain by a second cleavage. Proinsulin, Proglucagon and POMC are the well studied peptide hormone precursors. PCs are responsible for the cleavage at specific sites in each of these precursors. The most frequent sites for cleavage are KR and RR. Proglucagon is processed by PC2 in the alpha cells and by PC1/PC3 in the intestinal L cells and releases active forms of glucagons-like peptides namely GLP-1 and GLP-2. The convertases PC2 and PC1/PC3 are majorly expressed in brain and neuroendocrine system to act on neuropeptide precursors in the secretory pathway. Glucose, the second messengers in the neuroendocrine cells regulates the transcription and translation of PC2 and PC1/PC3. Other convertases like PC4 expressed in testis and an isoform of PC6 that lacks a TM domain belong to PC family. Recently discovered convertases are PC7, furin, PACE4 and PC6B. These are expressed in tissues like liver, gut, brain, neuroendocrine system. There are still many unidentified enzymes that participate in cleavages at single basic residues and unusual sites, other than the subtilisin-like Proprotein Convertases.

Next section: Proteomics/Proteolytic processing/Examples of proteolytic processing in various organs of our body


text:
Proteomics/Proteolytic processing/Examples of proteolytic processing in various organs of our body

Examples of proteolytic processing in various organs of our body
In concern with the proteolytic processing with respect to kidney the human prorenin is considered. The proteolytic processing of human prorenin in renal tissues is discussed here. The mouse proprotein convertase also known as PC1 accurately cleaves the prorenin and generates active rennin. The human Proprotein Convertase also known as PC3 can also process the prorenin to generate rennin but not as efficiently as mPC1 does. This is because of the differences in the sequences of the carboxy terminus from PC1 to hybrid hPC1/mPC1. The cleavage of prorenin bay PC1 in humans takes place at a pair of basic amino acids by removal of 43 amino acid prosegment from the amino terminus of the it along with identification of a functionally important site in the hPC1. Also PC1 generates active rennin in other tissues like adrenal medulla and certain adrenal tumors. If human prorenin has either in Lys or Arg residues at the cleavage site then the hPC1 cannot generate active rennin.
 * Renal proteins

The Kell Blood Group Protein belongs to family of metalloendopeptidases. It’s a membrane glycoprotein which shares a pentametric zinc-binding consensus sequence. It conserves all the amino acids required for the endopeptidase activity. Kell Blood Group proteins have a homology with M13 family in which a disulphide bond is covalently linked to a protein named XK, this spans the membrane 10 times, whereas kell proteins is linked to XK present is fifth extracellular loop. Activation of endothelins and processing of bioactive peptides can be done by Kell proteins.
 * Blood protein

Fodrin, Human Brain Alpha Spectrin plays an important role in the nervous system yet its mechanism is not completely understood. Its isoforms are present within the cells and in some neurotransmitter neurons. It is proteolytically processed by the calcium dependent proteases. This processing of fodrin is a central molecular mechanism does the development of long term memory. Foldrin has a proteolytically hypersensitive site in its centre for cleavage. Calcium-dependent binding of calmodulin takes place at this site.
 * Human Brain Spectrin

Next section: Proteomics/Proteolytic processing/Proteolytic processing of the Human Immunodeficiency Virus type 1


text:
User talk:Priyanka1031

Welcome, Priyanka1031!

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Νεοπτόλεμος ( talk | email | contribs ) 18:29, 30 March 2008 (UTC)

title: User talk:Priyanka1031


text:
Proteomics/Proteolytic processing/Proteolytic processing of the Human Immunodeficiency Virus type 1

Proteolytic processing of the Human Immunodeficiency Virus type 1
Polyprotein precursors translates the proteins that forms the retroviral particle. One of these precursors has viral protease that processes the precursors itself. This viral protease cleaves the retroviral precursor proteins during the virus assembly. Fully infectious viral particles are produced by precise Protease-mediated precursor processing and if the order of the cleavage changes, it results in the less infectious viral particle. To become active the protease has to be localized along with the requirement of enzyme dimerization. Enzymes come from PR(Protease) domains of GagPol precursors. The processing events are first carried out by the embedded PR, prior to the release from the GagPol precursor.The activated protease domain on one pair of GagPol molecules cleaves initial sites on those same molecules. Further substitutions at the first amino acid in the protease, a proline, lift this constraint and free the protease domain within GagPol to cleave additional native processing sites in the precursor not cleaved by the wild-type embedded protease.

Next section: Proteomics/Proteolytic processing/Proteolytic processing- role in therapeutics


text:
Proteomics/Proteolytic processing/Proteolytic processing- role in therapeutics

Proteolytic processing- role in therapeutics
The fact that certain proteins can modify others by binding to specific site and alter its activity is used as a principle in the development of certain modern therapeutics. Here is an example of how the process of proteolytic processing has been used to find possible cure for diseases. Human coronavirus is the causative agent of the common respiratory disease in adults and children. There are no current cure for CoV as a result proteolytic processing is being exploited to find new drug targets. Biochemical analysis of HCoV –NL63 virus showed 2 viral papain like protease PLP1 and PLP2 which process viral replicase polyprotein. In this case they generated polyclonal antisera against 2 of replicase non structural proteins nsp3 and nsp4. It was found that PLP1 processes clevage site to release 1 to release nsp1 whereas PLP2 released nsp2 and nsp3. Also by using hexa ubiquitin substrate and ubiquitin vinylsulphonate inhibitor specific to deubiquitinization enzyme further show that CoV has deubiquititination activity. Understanding the concept of proteolytic processing and deubiquitinating of PLP’s can pave a way to the development of novel antisera regents directed against HCoV.

Next section: Proteomics/Proteolytic processing/Autoprocessing


text:
Proteomics/Proteolytic processing/Autoprocessing

Autoprocessing
This is the process in which a protein modifies itself to convert a proprotein into an active protein. Classic example of this is the autoprocessing of furin family of endoprotease. Furin the most widely used proteolytic processing enzyme and functions mainly for cleavage of proproteins needed to maintain cellular physiology.Furin family of protease is also called the PACE family. Furin is transmembrane protein which is synthesized as a 100KDa protein. This protein undergoes catalytic cleavage in the Endoplasmic reticulum to become acxtive furin which is 94 KDa. The proprotein however remains bound to the protein and acts as the furin inhibitor. The polypeptide release then occurs in the trans golgi network where furin becomes active.

Next section: Lethal effects of proteolytic processing


text:
Proteomics/Proteolytic processing/Lethal effects of proteolytic processing

Lethal effects of proteolytic processing
Proteolytic processing not only helps in carrying out normal cellular processes but it also can cause processing of proteins to give lethal proteins. A classic example of proteolytic processing which develops lethal protein is development of Netherton syndrome. Netherton syndrome is a autosomal recessive congenital syndrome which causes ichthyosiform erythroderma caused by a mutation in the human SPINK5. Biochemical analysis of Netherton syndrome have shown an increase in the proteolytic processing of profilggrin into its constituent filaggrin monomers. Defects in filaggrin processing cause congenital disorders like icthyosis. SPINK5 undergoes extreme proteolytic processing furin is assumed to be involved in the proteolytic processing of SPINX5 however the exact extent of processing is yet to be determined.In the absence of serine protease inhibitor SPINK5 there is abnormal increase in the processing of profilaggrin resulting in the increased production of filaggarin monomers causing severely compromised epidermal barrier function.


text: User talk:142.161.251.238

title: User talk:142.161.251.238


text:
Talk:Spanish/Thesaurus of Spanish Cognates/Everyday Vocabulary/Conversational Forms

Isn't the literal translation of "lo siento" supposed to be "it I regret"? —The preceding unsigned comment was added by 67.169.98.59 (talk • contribs).
 * No, sentir means to feel, and the conjugation "siento" means "I feel", literally. Νεοπτόλεμος ( talk | email | contribs ) 19:27, 30 March 2008 (UTC)
 * So basically lo siento means I feel it (I feel your pain, etc). Also I changed the English of salud to "bless you" from generic toast, since that is how it's used. I don't think most people would understand "generic toast". - 71.109.149.49 (talk) 05:21, 4 August 2009 (UTC)


text:
Wikibooks:Reading room/Administrative Assistance/Archives/2008/March

Special:Import
Why is this Special page not allowed to all users? I would like to use it, because I use the stuff and I cannot quickly import it. Thoughts? Laleena (talk) 19:46, 23 February 2008 (UTC)
 * I asked this about a year ago. The Import tool is sort of in beta testing right now, and it still doesn't work perfectly.  But the real reason it's not generally available (or so I've been told) is because it chews up a lot of bandwidth on the servers.  But methinks the best way to get that tool in your hands is by making you an admin.  Shall I nominate you? --Jomegat (talk) 22:18, 23 February 2008 (UTC)

 * I'm don't know the exact reason why this wouldn't be available to all users, but there are a couple possible reasons why:
 * It does eat up a lot of bandwidth, as Jim mentioned. It has, therefore, been limited in software.
 * It has legal implications because improper use can create works which are not in compliance with the GFDL. This is, at least partially, because of the hard limits imposed in number #1.
 * Because importing a page over an existing page would cause the original page to be overwritten, and histories merged. History mergers are currently only allowed by admins. History mergers cannot, currently, be undone.
 * Maybe the case could be made that this should be opened up to more users, but considering the potential problems, and the bugginess that Jim mentioned, I think it's probably better to keep it for just admins for now. --Whiteknight (Page) (Talk) 01:47, 25 February 2008 (UTC)
 * To Jomegat: If you think I am suitably admin-enough, then go ahead and nominate me, I would love to have the permissions. To WK: I thought that all Wikis were GFDL. How can you create a page (unless form a non-wiki site) that isn't GFDL? Thanks, Laleena (talk) 01:53, 25 February 2008 (UTC)
 * It is possible to import incorrectly; the tool is not foolproof. Since that's the case, it's possible to do an import which doesn't comply with the GFDL. Such cases might include an accidental history merge or a partial import. – Mike.lifeguard  | talk 20:37, 1 March 2008 (UTC)

Bot Run, Appoligies RC Patrollers
I used my bot to fix links on the entire Muggles Guide tonight, it was about 500 edits in the space of 10 minutes or less. I watched the RC list myself live, so the RC patrollers won't miss anything if you skip over that patch in the logs.

In retrospec, I probably should have given myself the botflag for the event, but I wasn't sure if that was something I should do without prior discussion, so i didnt. Maybe for tasks like this in the future, giving the botflag temporarily to bot operators might be a good idea.--Whiteknight (Page) (Talk) 02:51, 28 February 2008 (UTC)
 * I never did understood why the flag was removed. – Mike.lifeguard  | talk 00:09, 6 March 2008 (UTC)

Vandal
User:65.185.186.183 has continued after being warned. Νεοπτόλεμος ( talk | email | contribs ) 03:25, 10 March 2008 (UTC)

 * Blocked. Thanks for the heads-up. --Whiteknight (Page) (Talk) 03:27, 10 March 2008 (UTC)

 * Thanks! Νεοπτόλεμος ( talk | email | contribs ) 03:27, 10 March 2008 (UTC)

strange issue on page
if you go to http://en.wikibooks.org/wiki/Aros you will notice that some of the links link directly to the edit form when I viewed the source of the wiki page content the links are all of the same format. Something in your wikiContent -> HTML rendering is making them edit links rather than going to "This page doesn't exist please ..."

Thanks

Aldur (talk) 16:49, 13 March 2008 (UTC)

 * Hello Aldur, welcome to Wikibooks. "Red links", links which are red in color, point to pages which do not currently exist. When you go to a page which does not exist yet, you are taken to the page editor, so that you can create the page. I don;t know of any way to change this behavior. --Whiteknight (Page) (Talk) 16:59, 13 March 2008 (UTC)

 * As Microsoft would say, "this behaviour is by design". Webaware talk 23:31, 13 March 2008 (UTC)

Thats fine, any wiki I've used sends you to the page then you have to hit the create this page button., Unfortunately I've been talking with the AROS team and they feel that the licence of your wiki content conflicts with their licence for AROS so I won't be updating this content to the same extent that I was for.

== 69.141.23.32 ( talk | email |  contribs | [ logs ] ) ==

Non-constructive edits and garbage page creation. I cleaned up what he's done so far but there might be more. -within focus 00:23, 17 March 2008 (UTC)

spambots on the rise?
Today I have noticed that several pages have been edited by anonymous IP's replacing huge amounts of text with "Nice site!" or some garbage followed by "Cool, bro!" In some cases, the page is created rather than edited. I assume this generator of insincere compliments is some sort of spambot that has been loosed upon us. I blocked several of these for 3 months on March 18. But I wonder if that's long enough. Any thoughts? --Jomegat (talk) 04:29, 19 March 2008 (UTC)
 * 3 months should be fine. I'll check if any are open proxies and perhaps block for longer if so. – Mike.lifeguard  | talk 04:45, 19 March 2008 (UTC)
 * I did find 3 open proxies; I reblocked them for 1 year. Hope you don't mind. The rest are not active cross-wiki (or at least I can't see it; replag is bad for s3). Good eyes on the pattern there; I missed it. – Mike.lifeguard  | talk 05:00, 19 March 2008 (UTC)
 * Thanks Mike. Of course I don't mind - that's kinda why I brought it up. --Jomegat (talk) 12:29, 19 March 2008 (UTC)
 * Before blocking for such long periods of time, check to see whether they are dynamic/allocated/pooled IP or assigned. There is no point in blocking a dynamic/allocated/pooled IP address for any longer than a week (or even a day!) because the IP will be given to someone else in short order, and they'll be blocked instead. To check, you can use whois from a *nix shell, or the tools at DNSStuff – although the level of information seems to be dropping (probably due to privacy concerns, ironically). Webaware talk 13:02, 19 March 2008 (UTC)

images from Wikipedia to Wikibood Prealgebra_for_Two-Year_Colleges
I want to copy public-domain drawings from http://en.wikipedia.org/wiki/Proportional_reasoning to Wikibooks, but I don't know how to fill out the licensing.
 * Image:MrShortMrTall.JPG
 * Image:Water-triangle.JPG
 * Image:Left-right-graph.JPG
 * Image:Tall-short-graph.JPG

Can someone please help?

--Dr.enh (talk) 05:02, 19 March 2008 (UTC)
 * I've moved those images to Commons, so you should be able to use them as normal now. You don't need to upload them to Wikibooks. The software will get the image from Commons if it doesn't exist here. – Mike.lifeguard  | talk 05:08, 19 March 2008 (UTC)

Spam filter
I just reverted a vandal who went on a page-blanking spree. Halfway through my rollbacks, I was stopped from doing so by the spam filter. Is there a way to get rollbacking to not get blocked by this filter so vandal sprees can get taken care of more effectively? Νεοπτόλεμος ( talk | email | contribs ) 20:12, 18 February 2008 (UTC)

 * The SPAM blacklist will stop you saving a page with a hyperlink that matches an expression in the blacklist. Either your rollback would have saved a version with a hyperlink to a SPAM website, or we have an expression error. If it was the latter, then you need to report the hyperlink that tripped the blacklist (just the url without the http:// stuff) and one of the admins will fix it. If it was the former, then just edit a version of the page prior to the vandalism you're trying to rollback, and remove the SPAM link too. Webaware talk 01:27, 19 February 2008 (UTC)

 * I don't think that's what the problem was. I don't remember exactly what it said, I think it was something about making too many edits during a short period of time. If someone could edit my sandbox, I'll do rollback on it until it blocks me again and paste the message I get here. Νεοπτόλεμος ( talk | email | contribs ) 01:40, 19 February 2008 (UTC)

 * Okay, I edited your sandbox. It's my best vandalism impression! Try reverting that, and see what it says. --Whiteknight (Page) (Talk) 01:46, 19 February 2008 (UTC)

 * Oh noes! I R teh n00b. Here's the message I got:

Action throttled From Wikibooks, the open-content textbooks collection Jump to: navigation, search As an anti-spam measure, you are limited from performing this action too many times in a short space of time, and you have exceeded this limit. Please try again in a few minutes. Return to User:Neoptolemus/Sandbox. Thanks, WK. Not bad with the vandalism. :D Νεοπτόλεμος ( talk | email | contribs ) 01:49, 19 February 2008 (UTC)

 * Glad to help! I just tried it myself, and i didnt see a throttle error. It may only affect people with rollback, and not admins. I'm trying to ask the devs on IRC, but nobody is responding right now. I'll let you know as soon as I hear an answer. --Whiteknight (Page) (Talk) 01:59, 19 February 2008 (UTC)

 * All right, thanks! Νεοπτόλεμος ( talk | email | contribs ) 02:09, 19 February 2008 (UTC)

 * Interesting - per mw:Manual:$wgRateLimitsExcludedGroups, we'll need to get rollback group added to this list. Learn something new every day :-) Webaware talk 02:31, 19 February 2008 (UTC)

 * Yes, I just talked to brion, briefly, and he mentioned that there was a limit of 5 edits per minute. Now, I'm not sure if that is for all edits, or just rollback edits. I'll ask him about lifting this limit for our rollbackers, so you can fight vandalism better. --Whiteknight (Page) (Talk) 02:49, 19 February 2008 (UTC)

 * Sounds good. Not that I typically average an edit every ten seconds, but it'd be easier to quickly revert vandal sprees. Νεοπτόλεμος ( talk | email | contribs ) 02:52, 19 February 2008 (UTC)

 * I agree. There is no reason why our vandal fighters should be limited to making edits less frequently then our vandals! This is why... --Whiteknight (Page) (Talk) 03:02, 19 February 2008 (UTC)

Raise Edit Limits for Rollbackers
After the discussion above, I talked with some devs on IRC, and it turns out that our rollbackers are limited to 5 edits per minute. Admins are exempt from all editing limits, so this isn't an issue for them. I'm also not entirely certain if the 5/minute limit is for all edits, or if it is just for rollbacks. Regardless, there is no reason why our rollbackers should be limited like this, especially when our vandals can easily circumvent an edit throttle by creating sock puppets. I propose, therefore, that we ask the devs to increase the edit limit of our rollbackers from 5/minute to something much more reasonable for vandal fighters. 20 per minute or so would be 1 edit every 3 seconds, which is pretty impressive by any standards, should be good enough. What do people think about this? --Whiteknight (Page) (Talk) 03:02, 19 February 2008 (UTC)

 * It would probably be applied through $wgRateLimits affecting all edits and moves, but admins and 'crats are spared this through $wgRateLimitsExcludedGroups - and we should add rollbackers to that. My local wiki has the default 'null' on all rate limits, but I'd guess that there would be a limit set in LocalSettings.php for Wikibooks and other WikiMedia projects. 5/min would basically require a script or at least a fast-keying mindless vandal, as I know I haven't exceeded 3/min in past I'm-a-robot editing efforts :-) Webaware talk 03:16, 19 February 2008 (UTC)

 * per above thread. Νεοπτόλεμος ( talk | email | contribs ) 03:19, 19 February 2008 (UTC)

 * - I'd say 20/min is plenty, or just remove the limit. OTOH, If a rollbacker is getting anywhere close to 20/min then they should be hollering for some backup cuz there's some blocking to do :) Still, I see no reason to limit our rollbackers like this.
 * While we're at it (and I'm thinking about it), we might think about giving our patrollers the autopatrolled permission, as admins and bots currently have. If we trust them to mark pages as patrolled, I think we can trust them to not make garbage pages. This change would mean that all pages created by patrollers would be automatically marked as patrolled, as is currently done for admins and bots. – Mike.lifeguard  | talk 03:21, 19 February 2008 (UTC)

 * I agree with Mike, patrollers should not have to patroll other patrollers. Νεοπτόλεμος ( talk | email | contribs ) 03:37, 19 February 2008 (UTC)

 * Just a point about the limit rate: 5/minute is equivalent to one edit every 12 seconds. IMHO, that's already beyond the bounds of sane, reliable manual page editing. It could only be achievable via a script. As noted above, I've managed 3/min or one edit per 20 seconds when doing mindless page or image tagging, and even that requires a modicum of mental participation to ensure that the page is suitable for the action being taken. What we're talking about here is dropping the limit completely for rollbackers who might be using scripts to automate some actions. Talk of 20/min limit rates, i.e. one edit per 3 seconds, is pointless here IMHO as it's probably faster than transaction speed unless your script is running on a computer inside WikiMedia's LAN. Webaware talk 03:56, 19 February 2008 (UTC)

 * Just a note: I'm able to rollback much faster than that by opening new pages on each button hit (then closing them before they even load). Still couldn't get more than 12 or 13 a minute though. Also, we could ask for Special:Nuke to be enabled here as well... this rools back all of a users contribs with one click (and would have been handy yesterday). -- SB_Johnny | PA! 11:27, 20 March 2008 (UTC)

 * I thought that extension wasn't ready for production use yet, but looking at the documentation... apparently it is. So yes, I'd support enabling the extension. It doesn't let admins do anything they can't do already, it just makes it easier to do. – Mike.lifeguard  | talk 13:56, 20 March 2008 (UTC)

 * I think the rate limit is for rollbacks (there is a separate one for moves, for edits etc, I think). If that's the case, then we either need a very high rate limit on rollback (or none at all) to avoid just this sort of situation. – Mike.lifeguard  | talk 03:59, 19 February 2008 (UTC)

 * We'll have to see what the dev's say, but AFAICT there are separate rate limits for edit, move and mailpassword; rollback would be an edit. My point above was simply that beyond 5/min you might as well drop the rate limit for that group of users, as anything faster would be approaching transaction speed across the Internet anyway. It would be interesting to know why rollback is triggering this, however, because my reading of the doc for $wgRateLimits suggests that we must either have a small number of edits per a small number of seconds specified, or a rollback is doing quite a number of edits in a single transaction. Webaware talk 04:42, 19 February 2008 (UTC)
 * In response to a few points made above, I've clocked my bot at just under 60 edits per minute (slightly more then 1 second between edits). This was done during a relative lull in activity, so the servers had some bandwidth to spare. I personally, without bot help, have pushed between 12-20 edits per minute for repetitive tasks, such as rolling back a large list of malicious edits, or copy+pasting templates on multiple pages. I won't say that it's common, and I also won't say it's reasonable, but it has happened. --Whiteknight (Page) (Talk) 13:37, 19 February 2008 (UTC)
 * I'd say that is certainly unreasonable - did you have someone following behind to read / check for errors? Not something I'm happy to hear coming from a 'crat, I have to say! Webaware talk 01:18, 20 February 2008 (UTC)
 * FYI: I confirmed that there are separate rate limits for edits and rollbacks; the documentation is (as always) out of date. – Mike.lifeguard  | talk 17:16, 19 February 2008 (UTC)
 * Cool, should be an easy fix then. I hope the doco catches up soon too :D Webaware talk 01:18, 20 February 2008 (UTC)

FYI: - The rate limit on rollback was raised to 20/min globally (sysops are still unlimited). – Mike.lifeguard  | talk 18:12, 2 March 2008 (UTC)

 * Well today Chazz hit the 20/min rollback rate limit, and was stopped. While 20/min seems like a lot, it really isn't considering that a) these are not normal edits, they're rollbacks and b) our rollbackers must be able to go at least as fast as the vandals. Even a single vandal can make enough edits that a rollbacker would hit the 20/min rate limit. I'd like to ask the developers to remove the rollback rate limit for this project. – Mike.lifeguard  | talk 02:02, 20 March 2008 (UTC)

New book: Prealgebra for Two-Year Colleges
I'm new to Wikibooks and I am starting a book called Prealgebra for Two-Year Colleges.

I think it belongs on the Mathematics_bookshelf under Basic Math, but I don't know how to put it there.

I also uploaded two images

Image:half.png and Image:quarter.png

Now I realize that they probably belong in Prealgebra for Two-Year Colleges/half.png and Prealgebra for Two-Year Colleges/quarter.png but I don't know how to move them there. (I could upload them to Prealgebra for Two-Year Colleges/ but I don't know how to delete the old images.)

I also don't know how to delete my scratch pages, such as User:Dr.enh/Prealgebra for Two-Year Colleges Thanks for your help!

--Dr.enh (talk) 18:26, 17 March 2008 (UTC)

 * Hi there; welcome to Wikibooks!
 * Image are always located as Image:name.ext, so there's no problem there. As for adding your book to the bookshelf, you won't be able to until your account is 4 days old. I'll add it for you now. If you need help, come on back here! – Mike.lifeguard  | talk 18:34, 17 March 2008 (UTC)

 * I've deleted the subpages for you and removed the resulting redlink above. Νεοπτόλεμος ( talk | email | contribs ) 00:57, 20 March 2008 (UTC)

Delete all this users contributions and block
http://en.wikibooks.org/wiki/Special:Contributions/F0ckT4rd Thanks --Remi (talk) 06:31, 26 March 2008 (UTC)

 * Got it, thanks. Webaware talk 07:11, 26 March 2008 (UTC)

Cookbook, search for Labskaus
Liebe gemeinde, wenn ich unter wikibooks auf cookbook gehe und den suchbegrif  Labskaus eingebe finde ich nichts

in der Deutschen Hauptseite finde ich aber Labskaus warum werdet ihr nicht verknüpft? danke und Gruß Thomas Wagner

translation:

Dear community, I can't find anything if I search for Labskaus in the cookbook of Wikibooks. On the German mainpage i find it, though. [Why isn't it linked?/Why isn't this linked to?/Why aren't you linked?]

Thanks and greeting from Thomas Wagner

 * I suspect this might be the dish that originates in Liverpool called Scouse whose name originated from Labskaus (not certain of the spelling). Indeed you'll see a reference to it on Cookbook:Cuisine_of_the_United_Kingdom although the page hasn't been created which is suprising considering that the dish is so popular and so easy to make.  Maybe one of our German speaking editors would like to copy it over to our Cookbook and add an inter-wiki language link. --Xania [[Image:Flag_of_Italy.svg|15px]]talk 22:13, 31 March 2008 (UTC)

67.49.250.19
Some vandalism of talk pages and others. Seems to have got bored and left. Have cleaned up. Could somebody block? --AdRiley (talk) 09:05, 27 March 2008 (UTC)

 * Done. thanks, Webaware talk 09:13, 27 March 2008 (UTC)


text: User talk:68.37.96.230

title: User talk:68.37.96.230


text:
Ido/Lesson I1

Konversado
Here is a conversation between two people. A: '''Bona jorno! Quale vu standas?''' Hello! How are you? M: '''Tre bone, danko. Quale vu nomesas?''' Very well, thank you. What is your name? A: '''Me nomesas Andre. E vu?''' I am (called) Andre. And you? M: '''Me nomesas Mei Hwa Wang. Ube vu habitas?''' My name is Mei Hwa Wang. Where do you live? A: '''Me habitas Paris. Ka vu anke?''' I live in Paris. Do you also? M: '''No, me habitas Atlanta, Usa. Me lojas en Paris nur por un monato.''' No, I live in Atlanta, Usa. I am staying in Paris only for a month. A: '''Bone! Ho! Yen la autobuso. Me mustas irar. Til rivido!''' Great! Oh! Here comes the bus. I must go. Good-bye! M: Til rivido! Good-bye!

title: Ido/Lesson I1


text:
User:Kj

kj - a sysop from Polish Wikibooks. More about me (pl).

title: User:Kj


text:
User talk:Battlebison~enwikibooks

Welcome, Battlebison!

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.--Whiteknight (Page) (Talk) 21:34, 30 March 2008 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Battlebison. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Battlebison~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:01, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:37, 19 April 2015 (UTC)

title: User talk:Battlebison~enwikibooks


text: User talk:71.196.215.142

title: User talk:71.196.215.142


text: User talk:207.38.251.38

title: User talk:207.38.251.38


text:
How To Build A Teardrop Trailer/The Hatch

The Hatch

For some reason, the construction of the hatch evokes fear in a lot of new builders. I have read builders delaying the hatch until the very end of their build. There is a point to their fear. The hatch is constructed by bending luan over a wooden frame, and one problem with that is a problem called "bow-back".

Bow-back is where the force of the bent luan pulls the whole hatch out of shape and causes a gap at the bottom. This is due to builders attempting to build the hatch with contoured ribs, so that the hatch is thin (the ribs being 1.5" - 2" wide). If the ribs can not withstand the force of the luan bent around them, the ribs bend. Many builders make a second hatch after the first one failed.

For our simple teardrop, we will avoid the entire bow-back issue by keeping the back edge of the rib straight. With a straight edge there is no possibility of bow back (via simple engineering mechanics). It behaves like a form of triangulation. The downside is that, as you can see, the ribs are rather bulky. The upside is that they are so strong you only need two, one on each end.

Making a Cardboard Hatch Rib Template
First you need to make a cardboard pattern for the end ribs. The shape is too complex to try to measure out, it is easier to try, cut, and fit the pattern (see image for reference):
 * 1) Get a piece of cardboard.
 * 2) Trace the curve of the sidewall for the length of the opening onto the cardboard and cut it out.
 * 3) Hold the cardboard up to the sidewall and mark and trim to the angles of the floor and the angle of the spar at the top of opening for the basic rib length.
 * 4) Cut a straight back on the rib template allowing for a hatch spar at the bottom and at the top (about 2" from the curve on the angled lines).
 * 5) The end result should look like this.

Check the template on both sides of the hatch opening to make sure all the angles and edges fit well. It doesn't have to be perfect. You should be able to pivot it from the top outside corner of the template (from where the hinge will be on the body) without any interference on the bottom with the floor. The bottom of the rib should come to rest on the floor with curve remaining flush with the sidewall all the way to the top. With the rib resting on the floor and the template curve flush with the curve of the sidewall, the top of the template should only have about a 1/8" gap between it and the body spar at the top. If the template works for one side but not the other, then simply make a second template for the other side.

The Luan will overlap the hatch frame on both sides and the bottom. This overlap will be a surface for weather stripping and will contact the edges of the sidewalls and the end of the wood bed. The luan on the top will be cut flush with the hatch frame.

You can then use the template(s) to cut out 2 ribs from the same 3/4" plywood material as the sidewalls. The next step is to attach four 2"x2" spars horizontally between the ribs (2 on the top and bottom and 2 evenly spaced in the middle) to form the complete hatch frame. Spar length should be chosen so that there is about 3/8" clearance between the outside of the end ribs and the inside of the teardrop sidewalls. Screw and polyurethane glue these items together.

With the glue still wet, position the frame inside the teardrop hatch opening and use long wood screws to screw through the ribs from the inside out into the teardrop sidewalls to hold the frame square in place while the glue dries (Be careful not to screw all the way through the outside teardrop sidewall!). The frame should be positioned so there is equal distance on both sides between the hatch end ribs and sidewalls; and the top of the hatch frame is in the position required for fastening the hatch hinge (i.e. the gap is about 1/8" at top).

After the hatch frame dries overnight, you can cut a piece of luan so that extends from the bottom of the wooden bed (overlapped) to the top of the hatch frame flush with the top edge of the hatch frame spar (and there should be about 1/8" inch gap between the top spar of the hatch frame and the teardrop body spar which is at the top of the hatch opening.). As was done with the luan roofing allow the luan to completely overlap the sidewalls to be trimmed flush later.

With the hatch frame still held in place by temporary screws, you can then glue and screw the luan skin over the back of the hatch frame while it is positioned in the teardrop hatch opening on the trailer.

The next step is to use the router again with the laminate trim bit to trim the overlapped luan of the hatch to the teardrop exterior sidewalls. The hatch construction is complete and can be freed from its temporary screws after the glue dries.

>>Next:Joints


text:
Template:Caption

''' '

Use, Limitations, and Parameters

 * Purpose: This template named Caption is used for placing of external image captions beside an image. It highlights the title line in bold, and presents the remainder of the caption in (override-able) italics.

Usage is:

Parameters

 * 1)   :   the main caption-(bold)
 * 2)   :   the remainder of the caption-(italic)
 * Non-italic output can be achieved by prefacing and suffixing the string with reverse ordered  and  tags at the string beginning and end respectively.

Tecnical note
Displayed text is wrapped in styled paragraph tags <p> ... </p> and integration with image sizing is in the hands of the editors. Proof your output by zooming in and out before accepting your edit use.

Example-1 of its use given the below with typesetters check text, including following bullet delimited paragraphs all around the above code is:

Example-1 of its use code: And so begins:

An example of its use with a clear or - command below is: a
 * Example 2 - with a HTML or to avoid text wrapping about the image:

gives with typesetters check text around it:

Example-3 of its use given the below with typesetters check text, including following bullet delimited paragraphs all around the above code is:

Example-3 of its use code:
 * (Similar to the First repeated with right situated image and deitalicised |2= parameter)

And so begins:

title: Template:Caption


text: Template:Horn/NavGeneral

title: Template:Horn/NavGeneral


text: Category:Book:Horn/Templates

title: Category:Book:Horn/Templates


text: Template:Horn/MusicBox

title: Template:Horn/MusicBox


text:
How To Build A Teardrop Trailer/Hatch Hinge

Hatch Hinge
For our simple teardrop we will use a novel hinge. The hinge is called a "Harsh-Environment Plastic Piano Hinge" and is available from McMaster-Carr on the web. This is a very durable 2" wide hinge that is waterproof and can be fastened simply by driving wood screws through it (I used the same screws as for securing the luan). The process is simple enough:
 * Obtain 2 pieces of 3/4" x 1/8" x 48" aluminum and drill holes every 6 inches for the wood screws.
 * Position the hatch in the desire location.
 * Place the plastic piano hinge in place.
 * Place the aluminum strips in place and drive wood screws through the plastic hinge into the body and hatch.
 * Caulk around edges.


text: User talk:189.33.54.161

title: User talk:189.33.54.161


text:
User talk:Mishboy2

Welcome message
G'day, welcome to Wikibooks. Please don't type in all capital letters, as it comes across as SHOUTING. Thanks, and here's our standard welcome message:

Welcome, Mishboy2!

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. Webaware talk 02:05, 31 March 2008 (UTC)

title: User talk:Mishboy2


text:
Horn/Glossary

Contents: C G I P

C

 * Concerto
 * (plural concertos or concerti) usually refers to a musical work in which one solo instrument is accompanied by an orchestra. The concerto, as understood in this modern way, arose in the Baroque period side by side with the concerto grosso, which contrasted a small group of instruments with the rest of the orchestra. While the concerto grosso is confined to the Baroque period, the solo concerto has continued as a vital musical force to this day.

G

 * Genre
 * (French: "kind" or "sort" from Latin: genus (stem gener-)) is a loose set of criteria for a category of composition.

I

 * Instrumentation
 * in the context of this Wikibook refers to the combinations and properties of instruments and/or voices used in a piece of music.

P

 * Premiere
 * (French: "first") generally means a first public performance of a piece of music.

title: Horn/Glossary


text:
Proteomics/Alternative splicing and its impact on protein identification

Alternative splicing: Biological function
Alternative splicing is the process in which the primary transcript of a gene is reorganized to produce a different protein than the primary transcript. By manipulating of the exons, the sequence of the amino acids produced from the mRNA is affected, resulting in a different protein sequence, and protein structure.[] This can have a drastic effect on the protein that is produced. Alternative splicing has been observed as a mechanism to produce tissue specific proteins from a signe gene. Depending on the tissue different proteins can be produced in different tissues from a single gene. This process can be thought of a multiplication process that increases the possible proteins that are produced from a single gene.

Alternative Splicing is a major source of protein diversity in living organisms. It has been estimated that at least 30% of all genes in the human genome are alternatively spliced and this number continues to expand. It was originally thought that the number of alternatively spliced genes accounted for only 5% of proteins in humans. With the unveiling of the human genome it was revealed that the human genome contains less than 30,000 genes[]. This could potentially account for the huge gap between the number of genes and the proteome.

It has been suggested that alternative splicing is the source of higher level complexity in eukaryotes[]. This idea is based on the thought that more complex organisms will alternatively splice their genes more often to obtain more possible mRNA sequences. However evidence shows that the level of alternative splicing between different complexities of organisms is not significant. Providing evidence of the contrary. This study was done using ESTs (expressed sequence tags *link to EST page*). As more EST studies are done, it has become apparent that there is a greater number of alternatively spliced genes than previously thought. ESTs were compared to mRNA sequences using BLAST.

Examples of Alternative Splicing
Alternative splicing has been implicated in several diseases. An example of a disease that plays a role in alternative splicing is Rett syndrome. This disease is found primarily in girls and is characterized by problems in forming connections between neurons, or synapses[]. It is believed that the gene MECP2 produces a protein that regulates alternative splicing of some proteins. When this gene is disrupted, transcripts of other genes that would normally be spliced by MECP2 are not spliced, leading to Rett the phenotype of the syndrome.

Splicing Mechanism
Splicing occurs through the mechanism of the Spliceosome. The spliceosome consists of a number of proteins and snRNA components. snRNAs U1, U2, U3, U4, U5 and U6[]. These snRNAs recognize the splice sites and then recruit other proteins that connect the splice sites. These splice sites are then brought together through the interaction of these proteins which form the spliceosome. Once the spliceosome has formed, the sites are cleaved to bring the correct exons (or introns) together.

There are 4 common types of alternative splicing, they are as follows:

 * Alternative promoter selection: A different promoter is used for different splice variants. This results in a different start of the mRNA transcript.

 * Alternative selection of cleavage/polyadenylation sites: Different exons are spliced based on recognition of different cleavage or polyadenylation sites, entire exons can be skipped.  Results in a different exon at the 3’ end of the transcript.

 * Intron retaining: Introns are used as coding regions. A sequence that is normally considered an Intron is retained in the final transcript that serves as a template for translation.
 * Exon cassette: Entire exons can be skipped in the middle of the protein, resulting in a different transcript

The Growing Need for Protein Identification:
Proteins are the basic unit of structure and function within living systems. Consequently the field of proteomics has taken on added significance in the modern study of biology. The genomic revolution, which culminated in the sequencing of many genomes, has generated a tremendous amount of data. The field of proteomics [] has unfortunately been lagging behind, resulting in a disconnect between genomic information and observable phenotypes. Originally, proteins and protein dependent pathways were studied individually. Recently an emphasis on systems biology has lead to changes in this methodology. Entire cells are being characterized with high throughput techniques.

Mass spectroscopy has become the golden standard of protein identification ([]) []. Briefly, proteins are broken down into peptides, suspended into a gas phase by one of a various number of methods, ionized, and sent through a detector which can determine the mass to charge ratio of various peptides. Mass spectroscopy can be easily automated and combined with other forms of protein separation, making it an ideal candidate for high throughput analysis. In addition, thousands of peptides can be identified from a single source at one time, making this technique much more applicable to systems biology then older techniques such as Edman degradation. Mass spectroscopy can also be used to identify single proteins of interest that have been isolated using other techniques, such as chromatography.

Splicing and Protein Identification
A major drawback of mass spec analysis, and even identification by Edman degredation, is that proteins must be digested into peptides before identification. Often for use with shotgun sequencing [], proteins are digested before any form of isolation process is done. In order to confirm identifications protein databases are searched in order to match unique peptides to entire proteins. This process is made more complicated by the immense level of sequence homology shared by peptides produced by alternative splicing. []. These proteins, although sharing similar primary structures may have very different or even antagonist functions, making their identification critical from a biological perspective. What is more, the level of alternative splicing that occurs is not well characterized so it is not even well known which proteins cannot be unambiguously identified. These problems will likely remain until alternative splicing is well documented or can be predicted efficiently computationally.

Efforts to analyze alternative splicing:
In vivo analysis is currently the most accurate way to identify alternative splicing, either at the transcript, or in some cases at the protein level. Numerous databases exist that document proteins known to undergo alternative splicing, including the Alternative Splicing Database []. and the Alternative Splicing and Transcript Diversity database []. Well these are good references, as discussed above, the estimates of even the amount of alternative splicing present in eukaryotic organisms vary dramatically. There is therefore, very little information on how complete these databases are. Steps have also been taken to computationally predict alternative splicing []. Generally these algorithms combine gene finding approaches with experimental data. Splice sites are recognized and rated in efficiency based on consensus sequences. Sequences are then matched to known expressed sequence tags to make predictions. Tools such as BLAT, Spidey, and SIM4 can be adapted for these processes. Most modern computational tools encounter difficulty in comparing genomic data to sequences as small and variable as splice sites. False positives and negatives are fairly common []). New approaches are still being developed.


text:
How To Build A Teardrop Trailer/Joints

Joints
There are many ways to cover the seams in the luan skin on the teardrop body. Builders use aluminum, wood, and RV trim bought commercially.

However, for our simple teardrop trailer we will create a moulding over the seam with Bondo. Step one is to apply masking tape on either side of the seam. Once that is done, mix some bondo according to the directions and apply a thick layer (about 1/8" thick) across the seam and over the edges of the masking tape.

With this technique, you don't have to worry about doing it all at one time. In fact its better not to try because you need to pull the masking tape prior to the bondo starting to cure. So as soon as you are done applying it, start pulling the tape. If the Bondo starts to cure before you pull the tape, chunks of bondo may come off the edges.

When you pull the tape it will leave the nice straight edge. You can continue on with masking tape and more Bondo as required to cover the entire seam. After you are finished, let the Bondo fully cure. You can then carefully sand the bondo smooth so that it looks like a moulding. You can try painting it if you like but try it on a test piece first. Its really better just to leave it plain. Later you will apply urethane varnish over the trailer and over the Bondo seams.

>>Next:Assembling the Doors

title: How To Build A Teardrop Trailer/Joints