OpenLLM-France/wikimedia huggingface dataset:
# Understanding Multitouch/Image Processing
## Processing

This chapter is designed to represent the computational model for the upcoming chapters. This is important as we may implement these algorithms as either software or hardware, in parallel or in serial. Before we go further, you should read the chapter on Image Acquisition, and understand our theoretical sensor model.

## Software Models

As of 2007, computer hardware has become very sophisticated, and has made inclusions specifically designed for signal processing, including both Single Instruction Multiple Data (SIMD) hardware and multiple cores and multiple threads in hardware (SMT). Both of these will influence the way we will want to import our data from our sensor, to make the best we can from our hardware.
One of the most important things to understand while implementing for an SIMD machine is the idea of Arrays of Structures verses Structures of Arrays. Inexperienced and older programmers will often miss optimization opportunities afforded to them by SIMD hardware by mistakenly using older concepts of storing the data in memory. The design idiom of Array of Structures is thusly rampant in older code as a way of improving readability.

### Example 1: Array of Structures

This makes inefficient use of our hardware because we cannot process these structures in parallel, and can cause problems with processor cache loading and unloading due to (mis)alignment. Processor companies have implemented instructions to aid in the reinterpretation of this kind of data (often called "swizzling" and "deswizzling"), but by simply designing the code correctly in the first place, we can avoid these slower instructions.

### Example 2: Structure of Arrays

The Structures of Arrays idiom takes advantage of our parallel hardware more efficiently. Because our structure encapsulates more data, we can get all of the data into the processor's cache earlier on. The alignment is now fixed and aligned to 4 bytes, we can skip swizzling and deswizzling.
# Understanding Multitouch

Multitouch computer interfaces revolutionized how people interact with computers. Products like smartphones and tablet computers have brought this technology to the masses. In this Wikibook we will look into the internals of it here, and describe how it works in detail.

## Prerequisites

This book will require that you have at least a rudimentary understanding of signal processing, and are competent in a programming language of your choice. This book will use pseudo-code to describe all of the algorithms and processes necessary to understand how this technology works, but to make it useful you will need to implement it in your own language.
To do the image processing components, you will need a digital web camera, or a multi-touch surface of your own devising (for the fearless). We will try to stay away from the mathematical descriptions of the algorithms whenever possible (as the pseudocode should be easier to understand from a programmer's/implementer's point of view, however this is a WikiBook, and if you can contribute material to the pure mathematical point of view, please feel free to do so.

## Table of Contents

* Overview
* Image Acquisition
* Image Processing
* Convolution and Deconvolution
* Point and Focal Recognition
* Image Segmentation
* Chording
* Hardware
# Understanding Darcs/Working with others
## The commands
### get

darcs get makes a copy of an entire darcs repository. Note that we only get the recorded patches (and pristine tree), not any of the pending stuff.

### pull/push

darcs pull copies from some other repository patches that you do not have. The patches are applied to your pristine tree and working directory. This may cause changes to be merged. Note that darcs push does the same thing, but in the other direction.

### send

Darcs send is sort of like push, only it doesn't actually apply the patches anywhere. Instead it generates a handy email to the person or people who own the repository. If it can't figure out who owns the repository, it will let you send to any email address you want. Note that you can also pass the -o command to "send" into a file, rather than a mail.

### apply

Apply is what you do to a patch that somebody darcs sends to you. You can also use it for the files you generated via send -o. Note: push is actually just apply in disguise, but with all the boring work of copying files over being done for you.

### put

Put enables to copy a local repository to remote location (for instance, via ssh). Think of put as the opposite of get.

## Dealing with conflicts

So you pulled a patch and you got a conflict. What do you do? See the chapter Dealing with conflicts
# Use the Source/BSD

* Discuss the starting of the BSD Unix variant.
* Discuss the startings of NetBSD and FreeBSD.
* Mention the starting of BSDi, but let the details be in the following chapter.
* Discuss where NetBSD and FreeBSD have gone since their founding
* Discuss the forking of NetBSD into OpenBSD and touch upon the conflict that caused it.
* Discuss the direction OpenBSD went in and why. Theo's Sun work and his license stance.
* Discuss 4.3BSD-Quasijarus, which is lead by Michael Sokolov. A strong supporter of VAX and the original BSD.
* Discuss the conflict that caused the forking of FreeBSD into DragonFlyBSD. The reasons for Matt Dillion's departure from FreeBSD and his history in Amiga and Linux work.
* Discuss the various dead BSD varients; why they started and why they died.
* Talk a little about Wasabi and Windriver.
Michael Sokolov is a hardcore backer of the VAX computer system as well as of the original ideals and code of the Berkeley Software Distribution, so in on December 27th, 1998 he began Quasijarus. Taking the code from the 4.3-Tahoe release of BSD UNIX Michael began to maintain and improve the 1988 code base for personal usage. As Michael believes in the ideal of a One True Unix, he completely avoids any and all GNU or GNU-like solutions within Quasijarus. Though the codebase is based on the Tahoe release of BSD, no work is done on the Tahoe specific code, VAX is the only architecture supported.
# Use the Source/Elite Hackers

| Use the Source | Edit template |
1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20
Try to go back to the origins of the names for as many common hacking terms; things like hacking, cracking, phreaking, l33t speak and the like.
Hackers versus Crackers
The quick run-down:
   * most hackers have university level training in computer sciences while crackers are largely untrained in any formal environment - predominately self-taught or peer reviewed.
   * crackers are viewed as pests by hackers while hackers are ignored or mocked by crackers
   * hackers build things while crackers break things (as in security)
   * Phreakers (a.k.a. phreaks), Phreaking - Phone intercepts, phone cracking, gaining control over phone networks.
Script Kitties
Script Kids, 'kiddies', or "kitties", use premade scripts in order to do as much damage as possible, these scripts are typically made by crackers so as to expand the amount of damage they do, without having to go to the work of actually cracking machines themselves.
Data Mining, (Ro)Bots: Some scripts -'Bots', replicate themselves, seek out specific information or data, copy it, and forward that information to a captive storage space on computers that have been previously taken over by the script kiddies ('owned', or 'Bot'ed', systems).
Sometimes involved in DataMining (a database search for keywords, email addresses), the 'bots' can reside in the "background' in a compromised computer, logging keystrokes, or collecting data, and forwarding it, until that computer is thoroughly cleaned of the bots by a knowledgeable technician.
# Use the Source/Counter-Culture

| Use the Source | Edit template |
1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20
"Linux is something for Windows haters, BSD is something for Unix lovers" - Heike S., February 1998
"Linux people do what they do because they hate Microsoft. We do what we do because we love Unix." - Theo de Raadt, founder of OpenBSD, quoted in "Is Linux For Losers?" at Forbes.com
"I view Linux as something that's not Microsoft-a backlash against Microsoft, no more and no less." - Ken Thompson, 1999
    Here are more slogans taken from Transwiki:Useful unix command.
Linux: the choice of a GNU generation.
Windows: where do you want to go today? Linux: where do you want to go tomorrow?
This program has performed an illegal operation and will be shut down: please reboot using Linux.
``When you say `I wrote a program that crashed Windows', people just stare at you blankly and say `Hey, I got those with the system, for free'.'' - Linus Torvalds
Windows 2000, from the company that brought you EDLIN!
Linux: because rebooting is for adding new hardware.
Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now [OK]?
Linux: transforms your microcomputer into a workstation. Windows NT: transforms your workstation into a microcomputer.
This page or section of Use the Source is a stub. You can help Wikibooks by expanding it.
# Use the Source

Welcome! You have come upon the beginning of a lighter-side look at Open Source, open source, Free Software, free software, Unix, Unix-likes and the whole mess known today as the Internet.
This book touches on the concepts of hacking, cracking, scripting and programming; illustrating the differences between them all and why there is a gap between the people doing these things and the masses unaware of the differences between them. Other topics will include the reasons for using different licenses for programs and what some of the more common ones mean to users and programmers.

## Contents

* What do you mean Open Source isn't Free Software? - Explaining the differences in the terms used for the various types of open source software.
* I have to give you what? - Talking about the rights given in licenses and those that are not.
* Theft or Copying? - Talking about "stealing" source, how it is actually copying with no loss of property involved.
* In the Beginning... - Explaining where the various open source movements began and the start of the Internet, do not go into detail the groups, just their basics - further detail will be in their specific chapters.
* Unix - The beginnings of Unix, it's relation to Multics and it's involvement with BSD. Mention Bell's K&R and the beginning of C.
* BSD - Talk about the BSDs, their founders and their strengths and weaknesses, go into more detail than In the Beginning....
* Let's get ready to RUMBLE! - The lawsuit involving BSDi, USL and the University of California; discuss the result of the suit as well as how it affected the BSD and Linux movements.
* BSD's Not Unix - The Unix trademark, Unix-likes, System V.
* Gnu's Not Unix - Talk about Richard Stallman and the Free Software Foundation and about the various licenses they have made and how they view other licenses.
* Linux - Talk about Linus Torvalds and the kernel he made, describe the relation to Minix and Unix.
* Gnu's Not Linux! - Talk about the mincing of words between the Linux and GNU camps.
* Gnu/Linux - The partial result of the GNU and Linux camps spat.
* OpenSolaris - Discuss OpenSolaris, what it means to other open source projects.
* Divide and Conquer - Talk about community friction, the concept of allies and enemies within the open source world.
* Cancer - Talk about the stance given by Microsoft regarding the General Public License, Linux and GNU.
* Counter-Culture - Talk about the rising of an anti-Microsoft movement, its relation to the open source groups and its effects on their usage and development.
* l33t |-|4X0rz!?! - Hacking, cracking, script kiddies and the like.
* Glossary - Definitions of words, technical and cultural terms, acronyms and notes.
* Licenses - A much more detailed look at licenses, will not be for the faint of heart
* Additional Information - A list of informational sources, the bibliography, thanks and contributors.

## Related wikibooks

* Open Source
# Use the Source/Divide and Conquer

| Use the Source | Edit template |
1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20
There are many factions within the world of open source, these include the Free Software and the Open Source pundits, the GPL and the BSD supporters, the libertarians and the communists.
These factions all have different reasons for the things they do and the things they don't; for some it is a matter of what is a right and what is practical, for others it is being altruistic to all people and for others it is getting the most out of a situation.
Briefly we shall sum up these groups:
The Free Software Foundation/GNU movement is a socio-political group for whom non-Free software is a social problem and Free Software is the solution.
The Open Source Inititive is a development methodology, to them non-Open Source software is a sub-par solution.
The BSDers (gotta get a better title than that) are a volunteer altruist group who give their work away for everyone. So everyone can get better. To them non-BSD code is irrelevant, it can be used and can be learnt from, but does not involved them.
The GPLers (still going to need another name) are volunteers who seek to receive reimbursement for their contributions. Getting back what others make of their work. To them non-GPL code is code which will die, that without the GPL license to protect the code it will not be able to maintain its competitive edge against proprietary software.
Outside of these groups, most people view them singularly as either open source or free software, but within there is a fair bit of bitterness and conflict, because of the different reasons for their actions. They all hold different views on how things should be done. This creates an image of a discordant open source community, when, in fact, it is actually many smaller communities which have only loose ties to one another.
# Use the Source/Let's get ready to RUMBLE

Summary:
AT&T was making and selling Unix and the University of California Berkley was making and giving away their own patches for Unix. A group of ex-Berkley students took the patches and formed a complete system and began selling it, trouble didn't start until they began advertising with a slogan of "It's Unix!".
A lawsuit resulted, which dragged in the University of California due to its releasing the code in the first place. The case went on for a long time, slowing the development of the BSD projects that had begun as completely open source operating systems.
It was LSU versus UoCB and BSDi.
During the case it was found that a large portion of the code in Unix was actually BSD code stripped of its license, thus breaking the terms of the license and placing LSU in an uncomfortable position. A settlement was made in which the whole of the results were kept from the public for several years, but for the most part freed the BSD code and any who use it from any legal action.
# Wings 3D/Tutorials/Box Modelling

note: Isn't extrusion modeling and box modeling the same thing? Shouldnt we make an article on other poly modeling techniques like adding components to a main object or cutting detail into geometry? Just putting out ideas here. ...-arquebus
# Wings 3D/Tutorials

Page added as a starting outline, if you can do better - go ahead and have at it. For those able to contribute, please do so and replace ??? with linked topic. Those of you seeking tutorials here, please be patient. You can still help by politely asking more experienced Wings3D users to contribute here.

## Quick Start Guide For Beginners

* Introduction to Wings 3D
* The Wings 3D Interface
** View Options
** Selection Modes
*** Universal Operations (Scale, move)
*** Vertex Operations (Vertex deformations, vertex bevelling)
*** Edge Operations (Cut operations, edge bevelling)
*** Face Operations (Inset, extrude, intrude, bridge)
*** Object Operations (Boolean operations, grouping, splitting, welding)
* Modelling with primitives
** Extrusion Modelling
** Box Modelling
** Subdivision Modelling
* Good modelling practice
** Smooth: use it wisely
* Adding color to your model
** Using Materials
** UV Mapping with AutoUV
** Texturing

## Organic Modeling

Humanoid Figures:
Animal Figures:
Mythological Figures:
Plants:
Other:

## Inorganic Modeling

Architecture:
* Commercial:
* Houses:
* Medieval:
* Industrial:
** Making pipe fittings with Wings/A different approach
** More pipe joints
* Other:
Vehicles:
* Aircraft:
** Modeling a generic helicopter
** Modeling a Junkers F13 from plan drawings
** Modeling a 2 Blade Propeller
* Automobiles:
** Box modeling a car with all Quad topography
* Other wheeled vehicles:
* Watercraft:
* Spacecraft:
* Misc.:
Weapons:
* Primitive/Medieval:
* Modern:
* Sci-fi:
Tools/Appliances:
* Antique:
* Modern:
* Futuristic/Sci-fi:

## Other / techniques

* PuzzledPaul's Magnets Tutorial
* Duplicating around a center
# Wings 3D

Wings 3D is a free, open source polygon modeler that was originally inspired by Nendo and later Mirai (both by Izware).
Once learnt, its clean, no-frills interface and wide-ranging (but unbloated!) toolset lets the user concentrate on their prime purpose: modeling.
The current release is available from the Wings 3D site. Other software is necessary to allow models made in Wings to be (properly) rendered and / or animated, although Wings does have an excellent feature-rich native UV unwrap facility.
Many industry standard import / export options are supported by Wings to allow it to communicate with the 'outside world'
* User Manual
* Tutorials
* Useful links

## Further reading

* Subject:Blender 3D
# Wings 3D/Tutorials/Introduction to Wings 3D

note: This is a rough draft, feel free to change, add on to, or correct spelling and grammar. -arquebus
Wings is probably the only 3D application (besides Nendo that was big inspiration for Wings developers) where you can learn just by using it, because the tools are accessed by right click menus rather than being spread out in toolbars. Only the tools you are currently able to use will be in the right click menu, depending on what selection mode your in. Wings is a box modeling application, which means polygonal modeling that grows out from a primitive object (usually a cube, hence box modeling) where you use four basic actions: move, extrude, scale and rotate. The geometry you create from these actions can be further refined by things like beveling, cutting edges, etc. Wings also has a smoothing function more popularly known as subdividing or sub-d. This not only gives you more geometry by dividing faces in half, but also smooths the shape of your model by rounding corners depending on closeness of edges.

### Second Life

Wings can be used to make sculpties (also known as "sculpted primitives") in Second Life. Currently, the best information is in the Second Life forums. If it becomes wider used, information specific to Second Life should be developed here.
# Wings 3D/Tutorials/Duplicating around a center

This tutorial is intended for users already familiar with Wings 3D commands to some extent. With the technique demonstrated, a Wings 3D user should be able to able to duplicate items around a center rather quickly.

## Starting point

Let's say we want to duplicate the twisted column on the right in a circle around the point indicated by the red spot.

## Setting up duplication

First figure out what number of times you want the object to go around the point. Create a new cylinder with the number of sides set to this number. To set the number of sides on a cylinder either right click on cylinder or on the adjacent box. You may need to enable advanced menus first in preferences. Place this cylinder so that its axis passes through the desired centerpoint.

## Make an extrusion

Pick a side on the cylinder and extrude it outward by an arbitrary amount.

## Loop cut

Loop cut the extrusion from the cylinder.

## Combine

Select the extruded bit and the object to be duplicated and combine them.

## Select interior face

Hide the cylinder. Select the face on the extruded bit that was facing the cylinder.

## Use Put-On

Without deselecting the face, unhide the cylinder. Right click on the Put-On command. Select all visible faces on the cylinder.

## Almost there

After executing the Put-On, you should see all your columns duplicated around the central cylinder. What's this? Something's not quite right. A column is missing.

## Select errant object

Fret not, fellow Wings3D user! There's a sort of bug in the Put-On command that occasionally makes it behave funny. On random occasions it will rotate items being put on. In this case the missing column is spotted poking through the bottom. Clicking on it in body (object) mode will select it and its corresponding extruded bit.

## Rotate to fix

Without deselecting the item from before, click rotate about selection. Select the face as shown. (It has the blue arrow sticking out of it, if not too clear otherwise.) Rotate 180°.

## Check placement

Now the "missing" column is rotated into its proper position. That wasn't so hard to fix, was it?

## Discard temporary objects

Select all the extruded bits in the center in body (object) mode. (All associated columns should select too.) Select separate from the menu. Go back and delete the cylinder and the extruded bits.

## End result

If completed correctly, you should have columns going around the center. This technique should be handy for anything that gets repeated in a circle, not just architectural columns. This could be lug nuts on a wheel, decorative stars, spokes, meat grinder spikes, tire treads, etc. Have fun!
--Pauljs75 00:42, 9 January 2006 (UTC)
# World Stamp Catalogue/Alawite State
## Alawite (Fr. Alaouite) State

* Postage stamps and postal history of Alawite State
# World Stamp Catalogue/Angola
## Postage Stamps by Year

1870-77 1881-85 1886 1893-94 1898-1901 1902 1903 1905 1911 1912 1914 1915 1921 1921-22 1925 1931 1932 1934 1935-36 1938 1942 1945 1946 1948 1949 1950s 1960s 1970s 1980s 1990s 2000s
* Postage stamps and postal history of Angola
# World Stamp Catalogue/Antarctica
## List of stamp-issuing entities in Antarctica

* British Antarctic Territory - BAT
* French Southern Antarctic Territory - FSAT
# World Stamp Catalogue/Aitutaki
## Aitutaki

* Postage stamps and postal history of Aitutaki
# World Stamp Catalogue/Albania
## Albania

* Postage stamps and postal history of Albania (English)
* Pulla postale shqiptare (Albanian)
| Date Issued | Denom. | Subject | Cat. No. Mi/Sc/Gi |
| | | | 455-57 |
| | | | 455-57 |
| 1913 | 25 pi | | |
| 1945 | 3 l | | |
| | | Gjergj Kastrioti Skanderbeg | |
| 1967 | | | |
| 1967 | | | |
# World Stamp Catalogue/Anjouan
## Anjouan

* Postage stamps and postal history of Anjouan
# World Stamp Catalogue/Annam and Tongkin
## Annam and Tongking

* Postage stamps and postal history of Annam and Tongking
# World Stamp Catalogue/Algeria
## Algeria

* Postage stamps and postal history of Algeria
A republic in North America
# World Stamp Catalogue/Allenstein
## Allenstein

* Postage stamps and postal history of Allenstein
# World Stamp Catalogue/Anguilla
## Anguilla

* Postage stamps and postal history of Anguilla
# World Tea Bag Catalogue/J
### Index of Brands / I

* SER Jadar-pak
* SRI Jolly
* NED Jumbo
* PRT Jumbo
Total : 3
# World Tea Bag Catalogue/Kazi & Kazi

Kazi & Kazi Tea Estate Ltd. is the only internationally certified organic tea grower in Bangladesh. their garden is located in Tetulia, in the northernmost district of Panchagarh, Bangladesh, only 50 km south of Darjeeling.
Kazi & Kazi Tea Estate Ltd. started its journey in 2000. They acquired virgin lands which had never before been used for cultivation. After extensive research and consultation with the Bangladesh Tea Board, the plantation began on August 6, 2000.
KK Tea entered the local market in 2006. It is esteemed to be one of the highest valued teas in the Chittagong tea auction since 2006. Their
garden produces only organic tea, manufacturing bio-fertilizers and bio-pesticides on-site with only natural and organic means.