OpenLLM-France/wikimedia huggingface dataset:
# United States Postage Meter Stamp Catalog/GROUP OA – Official Armed Forces government business mail franks/Sub-group OA-FPO: Stamps with "FPO" (Fleet Post Office) in the town mark but without indication of which military service used the meter
#### Sub-group AR-FPO: Official Mail meter stamps with "FPO" (Fleet Post Office) in the town mark but without indication of which military service used the meter

* Some of these stamps are quite elusive but their actual rarity is not known.
Type OO-IC4 or OO-A2.2 in previous editions
OA-FPO1. "Pitney Bowes 5313".
    Corresponds to Type IC4.1, OO-A2.2 (part).
    Value figures with wide wavy-line triad at left and no symbol at right (does not print fractions of a cent).
    When printing dollar values a narrow wavy-line triad appears left of the dollar number.
    Meter numbers: 3020000 series
    V/F: .00 ≋1.00$^♦$ (range: .01 to 9.99)
♦ Stamps with dollar values show a small wavy-line triad at left of the dollar number. These stamps resemble Type OO-A2.1 stamps. They can be differentiated by the placement of the decimal and the right-most number. See close-up scans at right.
       a. Town and state at top of town mark, "FPO" and 5-digit number at bottom
       b. As a but with 9-digit number at bottom
       c. "FPO" and town name or abbreviation at top of town mark, 5-digit number at bottom
       d. As c but with 9-digit number at bottom
Type OO-IE1 or OO-A4 in previous editions
OA-FPO2. "Pitney Bowes 6500" series.
    Corresponds to Type IE1, OO-A4.
    As previous OO-A types but the value box is much wider than tall.
       A. Wavy lines at left in value figures, 2mm tall (≋)
    Meter numbers: 6250000 series
    V/F: ≋ 0 .00 ≋ (range: .00$^1$ to 99.99$^9$)
       a. Town mark with town and state at top,FPO and 5-digit number at bottom
       b. As a, but with 9-digit number at bottom
       c. Town mark with FPO and town designation at top with 5-digit number at bottom
       d. As c, but with 9-digit number at bottom
       e. Town mark with FPO AP or FPO AE at top, 5-digit number at bottom
       f. Town mark reads:FPO SAN FRANCISCO / 96654 (without state) (6250128)
# United States Postage Meter Stamp Catalog/GROUP OA – Official Armed Forces government business mail franks/Sub-group OA-NGD: Stamps used by the National Guard for official business
#### Sub-group AR-NGD: Official Mail meter stamps used by the National Guard for official business

* AR-NGD stamps are identified by the slogan since the town mark contains no indication of military use.
* The National Guard offices come under the jurisdiction of both the Army and the Air Force.
* First seen in the 1980s.
NOTE: Since a systematic accounting of National Guard meter stamps has not been attempted before, it is likely that more types and varieties exist than those cataloged here.
Type OO-IC4 or OO-A2.2 in previous editions
OA-NGD1. "Pitney Bowes 5313",
    Corresponds to Type IC4.1 and OO-A2.2.
    Value figures with wide wavy-line triad at left and no symbol at right (does not print fractions of a cent).
    When printing dollar values a narrow wavy-line triad appears left of the dollar number.
    Meter numbers: 3020000 series
    V/F: .00 ≋1.00$^♦$ (range: .01 to 9.99)
♦ Stamps with dollar values show a small wavy-line triad at left of the dollar number. These stamps resemble Type OO-A2.1 stamps. They can be differentiated by the placement of the decimal and the right-most number. See close-up scans at right.
       a. ZIP code at bottom of town mark:
          - MCENTIRE ANG BASE, SC / 29044(979325) [RR]
Type OO-LA1 and OO-D1.1 in previous editions
    Frank shape corresponds to Group LA1. Value figures correspond to Types LA1.1 and LB1.1.
    The three stars at right have one arm pointing up.
    Distance between the right edge of the date and the left edge of the value figures is approximately 25-26 mm. The right-most digit in the value figures falls under the "M" of "MAIL".
    Meter numbers in 288000-546000 and 2000000 series
    V/F: 00.00 (range: 0.01 to 99.99)
    Large single circle town mark, 27 mm in diameter
    Town mark without state designation: OTIS ANGB / 02542 (2373939) [R-RRRR]
# United States Postage Meter Stamp Catalog/GROUP OA – Official Armed Forces government business mail franks
## GROUP AR: Meter stamps used by the Armed Forces

Click here to return to the United States Postage Meter Stamp Catalog
* Group OA describes "OFFICIAL MAIL" format meter stamps used by the military for official business formerly listed under "Group OO".
* Such stamps have town marks that contain "APO" (Army Post Office) or "FPO" (Fleet Post Office) or are mailed from Zipcodes that are known APO or FPO zipcodes.
* Also included are meter stamps that have the name of a U.S. Navy ship in the town mark. These stamps are from meters located aboard ship.
* Additionally any "OFFICIAL MAIL"meter stamp with "NAVY", "ARMY", "AIR FORCE", or "MARINE" referencing the armed services is included.
* There are eight sub-groups based on the branch of the armed services using the meter. Click on those you want to see:
       • Sub-group OA-NAV – U.S. Navy
       • Sub-group OA-ARM – U.S. Army
       • Sub-group OA-AIR – U.S. Air Force
       • Sub-group OA-MAR – U.S. Marine Corps
       • Sub-group OA-APO – overseas Army and Air Force Post Offices
       • Sub-group OA-FPO – overseas Navy and Marine Fleet Post Offices
       • Sub-group OA-NGD – National Guard
# United States Postage Meter Stamp Catalog/GROUP OA – Official Armed Forces government business mail franks/Sub-group OA-ARM: Stamps used primarily for Army official business
#### Sub-group AR-ARM: Official Mail meter stamps used primarily for Army official business

* Some of these stamps are quite elusive but their actual rarity is not known.
Type OO-IE1, OO-A4 in 2001 edition
OA-ARM1. "6500" series.
    Corresponds to Types IE1, OO-A4.
    As previous OO-A types but the value box is much wider than tall.
       A. Wavy lines at left in value figures, 2mm tall (≋)
       B. Smaller wavy lines at left in value figures, 1mm tall (≋) (2310000 and 6090000 series)
       C. The lines of the value box are thicker than the town mark circle line. (2310000 and 6090000 series) [RR]
    Meter numbers: 2310000, 6000000, and 6250000 series
    V/F: ≋ 0 .00 ≋ (range: .00$^1$ to 99.99$^9$)
       a. Town mark with U.S. ARMY at top, APO and 5-digit number at bottom
# United States Postage Meter Stamp Catalog/GROUP OA – Official Armed Forces government business mail franks/Sub-group OA-MAR: Stamps used primarily for Marine Corps official business
#### Sub-group OA-MAR: Official Mail meter stamps used primarily for Marine Corps official business

* Some of these stamps are quite elusive but their actual rarity is not known.
Type OO-IC3B(sub d, e, f) in 2001 edition
OA-MAR1.1. "Pitney Bowes 5303, 5336, 5382", 1979.
    Corresponds to Type IC3.1., OO-A2.1.
    V/F: ≋0 .00 (range: 0.01 to 99.99)
       a. Town mark contains "U.S.M.C." (U.S. Marine Corps) and no town name: U.S.M.C. / FPO 98773(3315230) [R]
       b. Town mark contains "USMC" and no town name: USMC FPO / 98773(3315230) [R]
       c. Town mark reads: U.S. MARINE CORPS FPO / 96310 (3315233) [R]
Type OO-IC4 in 2001 edition
OA-MAR1.2. "Pitney Bowes 5313", 1979.
    Corresponds to Type IC4.1, OO-A2.2.
    Value figures with wide wavy-line triad at left and no symbol at right (does not print fractions of a cent).
    When printing dollar values a narrow wavy-line triad appears left of the dollar number.
    Meter numbers: 3020000 series
    V/F: .00 ≋1.00$^♦$ (range: .01 to 9.99)
♦ Stamps with dollar values show a small wavy-line triad at left of the dollar number. These stamps resemble Type OO-A2.1 stamps. They can be differentiated by the placement of the decimal and the right-most number. See close-up scans at right.
       a. ZIP code at bottom of town mark:
          - KANEOHE MCAS HAWAII / 96863(3025273) [R]
       b. Town mark reads:US MARINE CORPS / FPO 98764(3025523)
       c. Town mark has U.S.M.C. at top and 5-digit number at bottom:
          - 96607 (3025328, 3025516)
          - 98764 (3025465)
       d. Town mark reads:USMC 1STFSSG CAMP PENDELTON / CA. (3025266, 3025352, 3025493, 3025526)
Type OO-IE1, OO-A4 in previous editions
OA-MAR2. "Pitney Bowes 6500" series.
    Corresponds to Type IE1, OO-A4.
    As previous OO-A types but the value box is much wider than tall.
    Wavy lines at left in value figures, 2mm tall (≋)
    Meter numbers: 6250000 series
    V/F: ≋ 0 .00 ≋ (range: .00$^1$ to 99.99$^9$)
       a. Town mark reads:KANEOHE MCAS HAWAII / 96863(6251835)
# Webots Odor Simulation/Using the Wind and Odor Sensor on Robots

Using the sensors on a robot (or elsewhere in the environment) requires adding a sensor object onto the robot, and then reading the value of this sensor object in the robot controller. An example of this can be found in the files worlds/odor_test.wbt (world file) and controllers/odor_test/odor_test.cpp (robot controller).

## Adding an Odor and a Wind Sensor on the Robot

A general sensor in Webots can simply be created by adding a receiver object with a special DEF name onto the robot. The magic DEF names for our sensors are SENSOR_ODOR_# and SENSOR_WIND_#, where the # has to be replaced by a unique number between 1-16. (For more sensors, the corresponding definition in the odor_physics plugin can be modified.)
E.g. your Khepera III robot number 1 could have the following odor and wind sensors configured in the world file (see worlds/odor_test.wbt for an example):
Note the name property which is here set to "sensor_odor" and "sensor_wind" respectively. This name is used by the robot controller to find the sensor.
You may have noticed that the above code does not contain any sensor configuration values (e.g. noise level, type of odor, ...). The properties of the sensors (as well as all other properties of the simulation model) are configured directly in the odor simulation plugin.

## Reading the Sensors

In your robot controller, you can read the odor and the wind sensors as follows (see controllers/odor_test/odor_test.cpp for an example):
# Webots Odor Simulation/Deploying Odor Sources

Similar to the odor and wind sensors, an odor source is simply a normal Webots object with a special DEF name. The magic DEF name here is SOURCE_ODOR_#, where # must be a unique number (1-16), and the object to create is a solid.
Your first source could look like this in your world file (see worlds/odor_test.wbt for an example):
Just as for the sensors, the world field does not contain any configuration of the odor source. This is done in the odor simulation plugin. Hence, changing the shape or the size of the solid does not change the area in which the odor filaments are released.
# Welding

Welding is one of the most important trades of the world in which we live. Welding is defined as 'the fusing of two or more pieces of metal or plastic'. It binds the office buildings in which we work, the malls where we hang out, and in every car that we will ever drive.
Welding is most often a 'skilled trade', which means that not everyone can pick up a welding torch and build something, it must be learned. Because of this, welders using their individual skills are often paid well or above average wages. In the manufacturing industry where repetitive tasks are performed, welding operations are often performed by lower paid workers with limited skillsets or those operations are mechanized or automated.
Welding is a wide ranging and diverse process that incorporates many process and skills. Some of these are very simple while others are more complex.
Interested? It actually doesn't take too long to learn, in some cases a journey person status can be reached in as little as 3 years. The skilled welder has a steady hand, good hand-eye coordination, and a good work ethic.

## Content

* Safety
* History
* Overview of Techniques
** SMAW
** Oxy Fuel
** GTAW
# Welding/History
## History

Welding has been around in some form or another ever since people realized that metal could be useful. One of the oldest methods of welding was actually forging. A metal ore would be retrieved by mining, smelted in a hot fire, collected into a large quantity of almost pure metal, and hammered into shape by using different fire techniques. Different methods of kindling, stocking and airing a fire could control the heat that it would produce. For example, to forge a sword a fire would need to heat the metal (likely copper or bronze), to a red-orange glow. Eventually, mixed metals (alloys) were used for higher strength and a range of new uses.
# Webots Odor Simulation/Download and Installation
## Download

The plugin is currently under development and not available for download. Please contact the author to obtain the latest version of the plugin.

## Installation and Quick Start

To use the plugin, you need to have a recent version of Webots 2021b installed on your computer. Note that the EDU version does not support physics plugins, and is therefore not suitable to run the odor simulation plugin.
With Webots installed, you can launch the simulation as follows:
* Unzip the file webots_odor_simulation.zip that you obtained from the author. This will create a folder Webots.
* Launch Webots and open the file Webots/worlds/odor_test.wbt.
You should see an arena with a model of the Khepera III robot.
# Webots Odor Simulation/Changing Model Parameters

The odor simulation is implemented as a physics plugin for Webots, and therefore lies inside plugins/physics/odor_physics. This folder contains a multitude of files which implement a piece of the model each. The file which holds the whole simulation together is odor_physics.cpp, more precisely inside the function "webots_physics_init". All model parameters can be easily be configured there.
The parameter names should be mostly self-explanatory. In addition, there is short documentation in the file implementing that corresponding part of the model. (At some point in the future, a better documentation of these components will appear in this book.)
After changing the model configuration, the plugin needs to be recompiled by typing make in the folder of the plugin, and the Webots world needs to be reloaded.
# Welding/GTAW

GTAW or Gas Tungsten Arc Welding also more know as Tig Welding is a very popular welding method today. With this method you weld by heating up the base metal and create a weld puddle and at the same time add a filler material or filler rod into the welding pool. TIG (Tungsten Inert Gas) welding uses a non-consumable tungsten electrode to create heat and melt the surface of the workpiece and is used mostly on thin materials, also when quality is of highest importance.
With GTAW you will be able to weld the highest amount of different metals and because of that it is a good solution for a lot of people. The main difference between GTAW and other commonly used welding processes is that the arc is generated by a non-consumable tungsten electrode. Tungsten is used because it has a very high melting point, wich allows it to maintain an arc hot enogh to melt most metals bu without melting itself.
* ↑ https://www.alphaweld.com.au/blog/53-best-welder-for-a-beginner-mig-or-tig-welding-
* ↑ https://betaweld.com.au/
# Welding/Oxy Fuel
## Oxy Fuel

Oxy fuel refers to an oxygen and fuel gas mixture being burned rapidly from compressed sources, such as large acetylene cylinders or more commonly, a propane tank (one you may find on a barbecue). A variety of fuel gases can be used in this task, such as propane, acetylene, natural gas, compressed gasoline fumes or anything else easily combustible. However, each type of gas has its own unique pro's and con's of usage.
# Webots Odor Simulation/Model

The odor simulation plugin is based the filament-based atmospheric dispersion model proposed by Farrell et al. in 2002. That is, odor is simulated as filaments in the air, which represent odor packets of a certain size and concentration. The odor simulation plugin therefore consists of five main components: a wind model, an odor filament propagation model, an odor source model, as well as a wind sensor and an odor sensor model.

## Wind

Wind can be simulated in different ways:
* Constant wind field: In the simplest case the wind field is constant. This corresponds to a homogeneous laminar wind flow. Even though this model is not very realistic, it is very handy due to its simplicity and straightforward configuration.
* OpenFOAM wind field (to be tested): More realistic wind fields can be generated with OpenFOAM and then loaded by the odor simulation plugin. This allows to simulate turbulent flows with obstacles. The odor simulation plugin supports loaded a static wind field or a dynamic wind field. Using dynamics wind fields could be slow due to the enormous amount of data that has to be loaded from the disk.
* Wind model presented in Farrell's paper (to be implemented)
Note that none of the wind fields takes obstacles (i.e. the robots) that you place within webots into account.

## Odor Filament Propagation

Odor filaments motion is based on two mechanisms:
* Filaments are transported by the wind (large-scale advection).
* To model small-scale movements of the wind, a stochastic process is superimposed. (Details can be found in Farrell's paper.)
Each filament represents a gaussian-shaped cloud of molecules. When filaments age, this could gets wider, but the concentration drops (to keep the number of molecules in a filament constant). The odor concentration at one point is the sum of the concentrations contributed by all filaments.

## Odor Sources

The odor simulation plugin supports multiple odor sources to be placed in the environment. Each source can release a different type of chemicals. A source is modeled as a circular area in which filaments appear.

## Odor Sensors

Odor sensors are modeled as sensors which return a noisy concentration measurement at one precise point. The noise is gaussian around the actual concentration. In addition, odor sensors can be configured to return a running average of the actual concentration.

## Wind Sensors

Wind sensors return a 3d vector of the wind measured at one specific point. The vector is a combination of the wind vector interpolated from the wind field, and gaussian noise. The wind sensor can be configured to return a running average of that value.
# Structured Query Language/with clause

The WITH clause extends SELECT, UPDATE, INSERT or DELETE statements with the definition of one or more 'inline views'. The scope of such 'inline views' is limited to the actual statement. Hence they have a temporary nature. Their purpose is the rearrangement of complex statements in such a way that the intention of the complete statement gets more clearly represented. Primarily, it is a syntax element to support the maintenance of database applications. Secondarily, if complex statements contain identical phrases at different places, and they are rearranged by a single WITH clause, the DBMS has a better chance to find an optimal execution strategy.
In other words: The WITH clause does not offer any new feature - with the exception of recursive queries, which will be explained in the next chapter. It offers only a syntax element to express complex queries in a clearly arranged way.
Hint: WITH clause is the terminology of the SQL standard. In everyday speech, this language construct is mostly referred to as Common Table Expression (CTE) and sometimes as Inline View. Oracle calls it Subquery Factoring Clause. Even though it is not the official term, on this page of the Wikibook, we prefer the term CTE as it is an expressive abbreviation.

## Syntax

The keyword WITH introduces the definition of a CTE. First, the CTE gets an arbitrary name - 'cte_1' in our case. This is followed by a SELECT statement, which defines how to retrieve data from one or more tables into the CTE (please consider: it's only a definition - it is not necessary, that the data really is materialized in the CTE). Afterward, a normal SELECT, UPDATE, INSERT, or DELETE statement follows, where the previous defined name of the CTE is used directly in the FROM or at any other place, where view or table names are allowed.

## Examples

The first example is limited to report only the content of a CTE. In this case it contains information about days where more than one person is born and consists of rows with the date plus a counter.
The similarity between CTEs and views is obvious. The main difference is that view definitions keep alive after using the view name in a statement, whereas the scope of a CTE is limited to the statement, where it is defined. This is the reason why some people denote CTEs as Inline Views.
The second example uses the CTE within a SUBSELECT of the main SELECT. The CTE is further modified by a BETWEEN criterion.
The third example uses the CTE at different places within the statement.
The main SELECT retrieves all persons (more than two rows), which have the same birthdays as such identified by the CTE (two rows). And it amends every person with the number of ambiguous birthdays (which is '2').

## Extension

The WITH clause is the basis for recursive queries, which will be explained in the next chapter.
# Structured Query Language/UPDATE 1

Hint: Be careful and deactivate AUTOCOMMIT.
The UPDATE command modifies one or more existing rows.
Values are assigned to the named columns. Unmentioned columns remain unchanged. The search_condition acts in the same way as in the SELECT command. It restricts the coverage of the command to those rows that satisfy the specified criteria. If the WHERE keyword and the search_condition are omitted, all rows of the table are affected. It is possible to specify search_conditions which hit no rows. In this case, no rows are updated - and no error or exception occurs.
As shown previously in the introductory page, the UPDATE command is very flexible. Within one command , we can choose an arbitrary combination of the two features:
* change one or more columns
* change zero, one or more rows - depending on the search_condition.
Additionally, values can have a dynamic nature like system date, timestamp, or timezone - depending on your implementation.
For a recapitulation here is an example:

## Further Information

We present some more information about additional opportunities of the UPDATE command here.

## Exercises

Change column remark of row Fishing in table hobby to: 'Catching fishes with or without tools.'.
Change column remark of all rows in table hobby to: 'A creative leisure activity.'. Check the success of the command without COMMIT-ting. Revert the changes.
# Structured Query Language/SQLSTATE

Programs using a database API that conforms to the SQL standard receive an indication about the success or failure of the call. This return code - which is called SQLSTATE - consists of 5 bytes. They are divided into two parts: the first and second byte contains a class and the following three a subclass. Each class belongs to one of four categories: "S" denotes "Success" (class 00), "W" denotes "Warning" (class 01), "N" denotes "No data" (class 02) and "X" denotes "Exception" (all other classes).
The values of SQLSTATE are published and explained in Wikipedia.
# Structured Query Language/Snippets

This page offers SQL examples concerning different topics. You can copy/past the examples according to your needs.

## Create Table
### Data Types

    More Details

### Constraints

    More Details

### Foreign Key

    More Details

## Alter Table

    More Details
Concerning columns.
Concerning complete table.

## Drop Table

    More Details

## Select
### Basic Syntax

    More Details

### Case

    More Details

### Grouping

    More Details

### Join

    More Details

### Subquery

    More Details

### Set operations

    More Details

### Rollup/Cube

    More Details

### Window functions

    More Details

### Recursions

    More Details

## Insert

    More Details

## Update

    More Details

## Merge

    More Details

## Delete

    More Details

## Truncate

    More Details