OpenLLM-France/wikimedia huggingface dataset:
# GNU Data Language

GNU Data Language (GDL) is a free software project hosted at Source Forge (GDL - GNU Data Language).
A free IDL (Interactive Data Language) compatible incremental compiler (i. e. runs IDL programs). IDL is a registered trademark of ITT Visual Information Solutions.
Features
Full syntax compatibility with IDL up to version 7.1 (for 8.0 and later see below).
ALL IDL language elements up to IDL version 7.1 are supported, including:
* objects, pointers, structs and arrays,
* system, common block and assoc variables,
* all operators and datatypes,
* _EXTRA, _STRICT_EXTRA and _REF_EXTRA keywords...
Supported IDL 8.0 language elements:
* FOREACH loop
* negative array indices
* garbage collection pointers and objects
* call methods on an object using "." (e. g. object.aMemberProcedure,arg1)
The file input output system is fully implemented (Exception: For formatted I/O the C sub-codes are not supported yet)
netCDF files are fully supported.
HDF files are partially supported.
Basic support for HDF5 files.
Overall more than 400 library routines are implemented.
SAVE and RESTORE are supported through Craig Markwardt's CMSVLIB library.
Graphical output is partially implemented. The PLOT, OPLOT, CONTOUR, PLOTS, XYOUTS, SURFACE, TVRD and TV commands (along with WINDOW, WDELETE, SET_PLOT, WSET, TVLCT, CURSOR) work (important keywords, some !P system variable tags and multi-plots are supported) for X windows, z-buffer and postscript output.
GDL has an interface to python (python routines can be called from GDL).
GDL can be build as a python module (GDL subroutines can be called from python).
GUI support (widgets) is officially provided since the 0.9 version (but it's not complete yet).
GDL is free software licensed under the GPL.

## Language Syntax
### Data Structures
### Control structures

* 3.1 Compound statements
* 3.2 Selection statements
* 3.3 Iteration statements
* 3.4 Jump statements
** 3.4.1 Storing the address of a label

### Functions

* 4.1 Syntax
** 4.1.1 Function Pointers
* 4.2 Global structure
* 4.3 Argument passing
** 4.3.1 Array parameters

### Miscellaneous

* 5.1 Reserved keywords
* 5.2 Case sensitivity
* 5.3 Comments
* 5.4 Command-line arguments
* 5.5 Evaluation order
* 5.6 Undefined behavior

## Function List
### Library procedures

Total number of library procedures available from the GDL base system (>400) is dependent on compile-time configuration (see the GDL documentation draft for a list) .
* AXIS
* BYTEORDER
* CALL_METHOD
* CALL_PROCEDURE
* CATCH
* CD
* CLOSE
* CONTOUR
* DEFSYSV
* DEVICE
* ERASE
* EXIT
* FREE_LUN
* GET_LUN
* H5D_CLOSE
* H5F_CLOSE
# GNU Data Language/AXIS

AXIS,[3 Args],CHARSIZE,CHARTHICK,COLOR,DATA,DEVICE,FONT,NODATA,NOERASE,NORMAL,SUBTITLE,T3D,TICKLEN,XCHARSIZE,XGRIDSTYLE,XMARGIN,XMINOR,XRANGE,XSTYLE,XTHICK,XTICKFORMAT,XTICKLEN,XTICKNAME,XTICKS,XTITLE,YCHARSIZE,YGRIDSTYLE,YMARGIN,YMINOR,YRANGE,YSTYLE,YTHICK,YTICKFORMAT,YTICKLEN,YTICKNAME,YTICKS,YTITLE,ZCHARSIZE,ZGRIDSTYLE,ZMARGIN,ZMINOR,ZRANGE,ZSTYLE,ZTHICK,ZTICKFORMAT,ZTICKLEN,ZTICKNAME,ZTICKS,ZTITLE,ZVALUE,SAVE,XAXIS,YAXIS,ZXIS,XLOG,YNOZERO,YLOG

##### PARAMETERS

* [3 Args]
* CHARSIZE
* CHARTHICK
* COLOR
* DATA
* DEVICE
* FONT
* NODATA
* NOERASE
* NORMAL
* SUBTITLE
* T3D
* TICKLEN
* XCHARSIZE
* XGRIDSTYLE
* XMARGIN
* XMINOR
* XRANGE
* XSTYLE
* XTHICK
* XTICKFORMAT
* XTICKLEN
* XTICKNAME
* XTICKS
* XTITLE
* YCHARSIZE
* YGRIDSTYLE
* YMARGIN
* YMINOR
* YRANGE
* YSTYLE
* YTHICK
* YTICKFORMAT
* YTICKLEN
* YTICKNAME
* YTICKS
* YTITLE
* ZCHARSIZE
* ZGRIDSTYLE
* ZMARGIN
* ZMINOR
* ZRANGE
* ZSTYLE
* ZTHICK
* ZTICKFORMAT
* ZTICKLEN
* ZTICKNAME
* ZTICKS
* ZTITLE
* ZVALUE
* SAVE
* XAXIS
* YAXIS
* ZXIS
* XLOG
* YNOZERO
* YLOG
# GNU C Compiler Internals/Stackguard 4 1

Stackguard is implemented in the following files.
These files translates GIMPLE to RTL.They take advantage of the CFG to instrument function prolog and epilog.
1) cfgexpand.c
Stackguard is created in function expand_used_vars. Depending on stackguard flag either all arrays or character arrays only are allocated first.
tree_expand_cfg takes care of prolog when it calls stack_protect_prologue. The corresponding function stack_protect_epilogue is called from calls.c to take care of tail calls and from tree_expand_cfg;
2) function.c
stack_protect_prologue, stack_protect_epilogue
The functions use machine definition targetm.
3) targhooks.c
Contains default initializers of target architecture hooks.
default_stack_protect_guard builds a VAR_DECL tree node that represents variable __stack_chk_guard.
default_stack_protector_fail builds a call to function __stack_chk_fail.
These ASTs are converted into RTL trees using expand_expr_stmt. The prolog and epilog functions add RTL expressions directly as well. For example, to detect a compromise function epilog generates a conditional statement that compares the canary word on the stack with its initial value:
where x and y are corresponding declaration RTLs:
Stackguard implements a certain amount of static analysis to make sure that suspicious functions with arguments of fixed length do not have vulnerabilities. The underlying mechanism is that of builtins. Stackguard has file strcpy.h that defines functions of interest, for example strcpy. The new definition uses builtins __ssp_bos to find out object size and __builtin___strcpy_chk:
* define __ssp_bos(ptr) __builtin_object_size (ptr, __SSP_FORTIFY_LEVEL > 1)
* define strcpy(dest, src) \
The builtins are evaluated at compile time. Function warning called in maybe_emit_chk_warning prints out a message if the destination buffer is overflown.
In case when Stackguard is unable to find out statically if the buffer is overrun function __strcpy_chk is called at run-time. Library libssp provides the function. However, the protected program does not require linking with this library explicitly. Instead, GCC instructs the loader to use a shared library.
| Prev: GNU C Compiler Architecture | Stackguard | Next: GEM Framework |
# GNU Data Language/CALL PROCEDURE

CALL_PROCEDURE,[inf. Args],_REF_EXTRA

##### PARAMETERS

* [inf. Args]
* _REF_EXTRA
# GNU Data Language/CLOSE

CLOSE,[inf. Args],EXIT_STATUS,FORCE,FILE,ALL

##### PARAMETERS

* [inf. Args]
* EXIT_STATUS
* FORCE
* FILE
* ALL
# Inorganic Chemistry/Chemical Bonding/Ionic Bond

As we know, atoms tend to attain the octet electronic configuration of minimum energy and maximum stability. One way of attaining this configuration is by transfer of electrons between two atoms. This transfer results in the formation of Ionic Bond.
File:Bonding Page6.gif
# Inorganic Chemistry/Chemical Bonding

* Introduction
* Ionic Bond
* Fajan's Rule
* Introduction to covalent Bond
* Lewis Dot Structures
* VSEPR theory
* Orbital hybridization
* Molecular orbital theory
* MO Diagram
* Metallic Bonding
* Ionic Bonding
* Hydrogen Bonding
# Inorganic Chemistry/Chemical Bonding/Ionic Bonding

Ionic bonding takes place when the metal atom contributes electrons to the non-metal atom. By doing this they both gain stable electronic configurations like the nearest noble gas.
# History of Rail Transport/Early Rail Transportation

Early Rail Transportation
Contents | Previous Chapter | Next Chapter

## Wagonways

Wagonways, which preceded steam powered railways, were the tracks, horses and equipment used for hauling wagons of coal, ore, or stone from mines and quarries to waterways or ports.
Wagonways were built in England as early as the 16th Century. Although wagonways merely consisted of parallel planks of wood, they allowed horses pulling them to achieve greater speeds and pull larger loads than on the slightly more rough roads of the day. Crossties were introduced fairly early to hold the tracks in place. Gradually, however, it was realized that tracks would be more efficient if they had a stip of iron on the top. This became common practice, but the iron caused more wear on the wooden wheels of the wagons. Eventually, wooden wheels were replaced by iron wheels. In 1767, the first full-iron rails were introduced.
In the 19th Century, steam engines began to be trialed in England, however they were found to be more expensive to run than horses. However, steam engines gradually improved, and the wagonways transformed into railways.
Contents | Previous Chapter | Next Chapter
# History of Sindh

A province in the south Asian country of Pakistan, Sindh has long been the centre of legends where seafaring merchants charted courses to the remotest lands and villagers sold spices, the birth-place of a civilisation that rivalled those of Egypt and Mesopotamia. Throughout this book, we will explore what is known of the past of this magnificent land and its people. With the discovery of flint stones scattered throughout the region, it is believed that earliest hominid habitation dates as far back as the Palaeolithic and Mesolithic era.

## Part I
### The ancient Sindh

* Early farming cultures
* Birth of a civilisation
* Language of the lost
* The Persian Achaemenid Empire
* Alexander and the Greeks
* Mauryan Empire
* The Islamic invasion
# History of Spain/Contributors

* History of Spain
* Introduction • References • Contributors • Print version
* Ancient Spain • Roman Spain • Visigoths • Spain Divided • Habsburg Spain
* Bourbon Spain • Napoleonic Wars • First Restoration • First Republic
* Second Restoration • Second Republic • Francoism • Third Republic
The following is a list of all contributors, past and present, to this Wikibook. For a list containing only those contributors who are currently active in its development, please refer to the Infobox.
# History of Spain/Introduction

* History of Spain
* Introduction • References • Contributors • Print version
* Ancient Spain • Roman Spain • Visigoths • Spain Divided • Habsburg Spain
* Bourbon Spain • Napoleonic Wars • First Restoration • First Republic
* Second Restoration • Second Republic • Francoism • Third Republic
# History of Rail Transport/Contents
## History of Rail Transport
### Chapters

* Preface
* Introduction
   * Early Rail Transportation
   * First Railways
   * Steam Locomotives
   * Development of the British Railway Network
   * Development of Railways in other Countries
   * Electric Railways
   * Diesel Locomotives
* Bibliography
* Authors and Contributers
# Georgia Water/Regional Plans/Contributors' Recommendations

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Contributors' Recommendations

## Activities to be included in the Regional Plans

* Hiking Trails (see: American Hiking Society's | Southern Appalachian Initiative)
* Greenspace Plan (Example: Etowah Regional Greenspace Plan)
* Southeastern US Ecological Framework, to identify ecologically significant areas.
* Aquatic Species Habitat Conservation Plan
* Total Maximum Daily Load (TMDL) Implementation Plan
* Alternative Watershed Build-Out Analysis for the Upper Etowah Watershed
* Stormwater Management Plan
* SCORP - State Comprehensive Outdoor Recreation Plan
* Clean Water Act - Section 303e Basin Plan for Water Quality Management
# Georgia Water/Regional Plans/Oconee, Ocmulgee and Altamaha River Basins

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References

### Information
#### Maps and Data
#### Local Government Comprehensive Plans

Please provide a link to local government plans.

#### Other Basin Planning Links

* Basin Advisory Committee for Statewide Water Plan
* Regional Development Council, under Georgia Department of Community Affairs

#### Organizations

Please add names of organizations which influence target conditions in this area.

### References

* Northeast Georgia Source Water Assessment Project - Upper Oconee Basin
* Ocmulgee River Watershed Management Plan (Georgia DCA)
# Georgia Water/Regional Plans/Satilla, Suwannee and St. Marys River Basins

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References

### References

* Map of Suwannee River Basin
* Map of Upper Western Suwannee River Basin (Withlacoochee, Alapaha, Little Rivers)
* Suwannee River Basin and Estuary Initiative
* Suwannee River Basin Management Plan 2002
# Georgia Water/References

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
References, by Chapter
* References - Introduction
* References - Georgia Water Policy
* References - Management Programs
* References - Georgia Water Information
* References - Planning
* References - Statewide Plan
* References - Regional Plans
** References - Overview
** References - Savannah and Ogeechee Rivers
** References - Satilla, Suwannee and St. Marys Rivers
** References - Oconee, Ocmulgee and Altamaha Rivers
** References - Flint and Ochlockonee Rivers
** References - Chattahoochee River
** References - Coosa, Tallapoosa, Tennessee Rivers
** References - Georgia Coastal Area (Floridan Aquifer)
References - Combined Listing
# Georgia Water/Regional Plans/Chattahoochee River

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References

### External links

* Southwest Georgia Water Resources Task Force (very comprehensive list of links)
* The Essentials of Georgia Water Planning - The Relationship Between the Proposed Georgia State Comprehensive Water Plan and the Alabama-Georgia-Florida Water Sharing Dispute (the failure to agree on the two Compacts), Stephen E. Draper, October 28, 2003.
# Georgia Water/Regional Plans/Flint and Ochlockonee River Basins

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References

### External links

* Flint River Basin Plan
* Southwest Georgia Water Resources Task Force (very comprehensive links on ACF tri-state water negotiation topics)

### References

* Recommendations for the Flint River Regional Water Development and Conservation Plan, December 16, 2005 (draft), presented to the Georgia Environmental Protection Division Director by the Flint River Basin Stakeholder Advisory Committee, (based on the scientific findings of a six-year study of agricultural water use and its effects on the Flint River and its tributaries, with recommendations for improvements in water resource management, especially during times of drought ).
* Policy Research Reports from the Georgia Water Planning and Policy Center, Albany Georgia.
# Georgia Water/Regional Plans

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Chapter 7. Regional Plans
    Contributors
    7.1. Overview
    7.2. State Guidance for Regional Plans
    7.3. Contributors' Recommendations for Developing Regional Plans
    7.4. Savannah and Ogeechee Rivers
    7.5. Satilla, Suwannee and St. Marys Rivers
    7.6. Oconee, Ocmulgee and Altamaha Rivers
    7.7. Flint and Ochlockonee Rivers
    7.8. Chattahoochee River
    7.9. Coosa, Tallapoosa, Tennessee Rivers
    7.10. Georgia Coastal Area (Floridan Aquifer)
# Georgia Water/Regional Plans/Savannah and Ogeechee River Basins

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References
Note: This page is a stub, needing much additional information and editing. The Welcome page shows how you can help.

### River Basin Management Plan by Georgia EPD

This plan, prepared under the River Basin Planning Management Act of 1992, provides information for development of the regional basin plan as part of the Georgia Statewide Water Plan (2005-2008).

### References
#### State documents
#### News articles

"S.C. doesn't like Georgia water plan" (South Carolina's environmental agency has filed an official complaint about Georgia's plan to manage fresh water along the coast.) AP article from SC online newspaper, The State, January 16, 2006.
# Georgia Water/Regional Plans/Coosa, Tallapoosa, Tennessee River Basins

* Water Policy
* Management
* Information
* Planning
* Statewide Plan
* Regional Plans
* References

### References

* Project Management Plan for Feasibillity Study: Lake Allatoona / Etowah River Watershed Ecosystem Restoration and Resources Protection, Lake Allatoona, Georgia, U.S. Army Corps of Engineers - Mobile District, May 2002.
# IB Physics/Digital Technology Option
## C.2 Data capture; digital imaging using charge-coupled devices (CCDs)
### C.2.1 Define capacitance.
### C.2.5 Define quantum efficiency of a pixel.

Quantum efficiency is the ratio of the number of photoelectrons emitted to the number of photons incident on the pixel.

### C.2.11 Solve problems involving the use of CCDs.
## C.3 Electronics
### C.3.6 Solve problems involving circuits incorporating operational amplifiers.
## C.4 The mobile phone system
### C.4.1 State that any area is divided into a number of cells (each with its own base station) to which is allocated a range of frequencies.

Every area is divided into a number of cells (each with its own base station) to which is allocated a range of frequencies

### C.4.3 Discuss the use of mobile phones in multimedia communication.

* Vocal communication • Text communication (SMS, chatting etc.) • Communication through social networks on mobile phone (facebook, twitter etc.) • Communication can be one-to-one or one-to-many
Advantages: • Time efficient • Cost efficient • Best way to reach lots of people • Easy
Disadvantages: • No information is private • Lack of control of information • Less real life communication

### C.4.4 Discuss the moral, ethical, economic, environmental and international issues arising from the use of mobile phones.

Moral / Ethical – Firstly, less human interaction in between adolescents as they are now able to lie at home and speak through their phones. Secondly, employees are distracted by their mobile phones when at their workplace. Economic- Not every one are able to afford mobile phones.
International- It is now faster and simpler to communicate with people around the world. Environmental- Disposing of 15m phones each year just in the UK. Mobile phones contain cadmium, rhodium, palladium, beryllium and lead solder, which are all highly toxic.
# HydroGeoSphere/Solute Mass Balance
## Sample solute mass balance output

By default, solute mass balance information for each species is computed at each time step and written to the prefixo.lst file. Figure 5.18 shows some sample output as it appears in the .lst file:
    Figure 5.18: Sample Mass Balance Information for Example PM CD

## No solute mass balance

This instruction prevents solute mass balance information from being written to the listing file.
This detailed mass balance information is also written to a TECPLOT formatted ascii output file called, for example, prefixo.mass_balance_species_001 so that it can be easily visualized.

## Summary mass balance information

Summary mass balance information is written to a TECPLOT formatted ascii output file called, for example, prefixo.mass_balance_summary so that it can be easily visualized. For each timestep in the transport solution, one line per species is written to the file. Each line has columns labelled as follows:
* time Simulation time.
* Tmass Total mass in the system.
* dBoundary Change in mass due to sources and sinks.
* dStored Change in mass stored.
* dBoundary - dStored Error.
* (dBoundary - dStored)/Tmass*100) Normalized error.
* Species Species number.
Besides being plotted with TECPLOT, such output can be imported into an editor (e.g. Microsoft Excel) and sorted to facilitate, for example, the creation of a plot of mass balance error versus time for a given species.

## Cumulative mass balance information

Cumulative mass balance information is written to a TECPLOT formatted ascii output file called, for example, prefixo.mass_balance_cumulative so that it can be easily visualized. For each timestep in the transport solution, one line per species is written to the file. Each line has columns labelled as follows:
* time Simulation time.
* In (cumulative) Mass in since start of simulation.
* Out (cumulative) Mass out since start of simulation.
* Stored Change in mass stored since start of simulation.
* In+Out-Stored Error.
* Species Species number.
Besides being plotted with TECPLOT, such output can be imported into an editor (e.g. Microsoft Excel) and sorted to facilitate, for example, the creation of a plot of mass balance error versus time for a given species.
# HydroGeoSphere/Selecting Segments

We can use the following instructions to alter the set of chosen segments.

## Clear chosen segments

All segments in the domain are flagged as not chosen. This is recommended if you are unsure of which segments are chosen due to previously issued instructions.

## Choose segments all

All segments in the domain will be chosen. This is useful if you wish to assign a property to all segments in the grid.

## Choose segments line

* x1, y1, z1 xyz-coordinates of the first end point of the line.
* x2, y2, z2 xyz-coordinates of the second end point of the line.
Segments which fall on or close to the line are chosen. The routine finds the two nodes closest to the end points of the line and then finds the group of connected line segments which form the shortest path between the two nodes.

## Choose segments polyline

* npts The number of points defining the polyline, which should be entered in order from one end of the polyline to the other. Read the following npts times:
       (a) x1, y1, z1 xyz-coordinates of a point on the polyline.
Segments which fall on or close to the polyline are chosen. The routine proceeds along the polyline, considering two points at a time, finds the two nodes closest to the two current points and then finds the group of connected line segments which form the shortest path between the two nodes.
# HydroGeoSphere/Snowmelt

You can assign a snowmelt boundary condition to faces in the specified set. These faces should be part of the overland flow domain and are typically located on the outer boundary.
The following instructions can be used as input to the Type instruction inside the Boundary condition...End instruction group to assign snowmelt boundary conditions:

## Snowmelt

Sets the input type to be a snowmelt boundary condition.
For example:
This example shows the use of a time value table instruction to define the snowfall and air temperature values with the density of snow, melting constant, the rate of sublimation, threshold temperature, and the initial snow depth being assigned with snowmelt constants instruction.

## Snowmelt Constants

* snow_rho Snow density [M L−3]. the results of the previous flow solution.
* snow_melt Snow melting constant.
* snow_sublimation Snow sublimation constant.
* snow_threshold_temp Snow threshold temperature.
* snow_initial_depth Initial snow depth [L].
The snowmelt constants command requires 5 values for the snow density, melting constant, sublimation constant, threshold temperature, and initial snow depth. The five snow parameters must be listed in the above order for correct reading by grok.
# HydroGeoSphere/Simulation Control Options

* General
** Finite-Difference Options
** Matrix Solver
* Timestep Control
** Adaptive Timesteps
* Saturated Flow
* Variably-Saturated Flow
** Newton Iteration Parameters
* Discrete Fracture Flow
* Surface Flow
* Transport
* Density-Dependent Flow and Transport Solution
** Relative Concentration as Primary Variable
** Absolute Concentration and Temperature as Primary Variables
** Salt Mass Fraction as Primary Variable
* Heat Transfer
* Inactive Elements