OpenLLM-France/wikimedia huggingface dataset:
# Pokémon/Pokédex/Gothitelle
## Description

A tall Pokémon.

## Base Statistics

A Psychic type Pokémon.

## Type Matching

Moves that deal 200% of their damage to Gothitelle: bug, ghost, dark Moves that deal 50% of their damage to Gothitelle: fighting, psychic
# Pokémon/Pokédex/Gothorita
## Description

A small Pokémon.

## Base Statistics

A Psychic type Pokémon.

## Type Matching

Moves that deal 200% of their damage to Gothorita: bug, ghost, dark Moves that deal 50% of their damage to Gothorita: fighting, psychic
# Pokémon/Pokédex/Goomy
## Description

A small goo-like Pokémon.

## Base Statistics

A Dragon type Pokémon.

## Type Matching

Moves that deal 200% of their damage to Goomy: ice, dragon, fairy Moves that deal 50% of their damage to Goomy: fire, water, grass, electric
# Pokémon/Pokédex/Grafaiai
## Description

A monkeylike pokémon.

## Base Statistics

A poison and normal type Pokémon.

## Type Matching

Moves that deal 200% of their damage to Grafaiai: ground, psychic Moves that deal 50% of their damage to Grafaiai: grass, poison, bug, fairy Moves that deal 0% of their damage to Grafaiai: ghost

## How to Evolve

Evolves from Shroodle.

## Notes

Introduced in Pokémon Scarlet and Violet.
# Pokémon/Pokédex/Gorebyss
## Basic Statistics

* National Index: 368
* Johto Index: 368
* Hoenn Index: 178
* Stage: Stage 1
* Height: 1.8m/5'11"
* Weight: 22.6kg/50.0lb
* Gender Distribution: 50% Male
* Ability: Swift Swim
* Type: Water
* Species: South Sea
* Egg Group: Water 1
* Hatch Steps: 5120
* Catch Rate: 60
* Base Experience: 178
* Max Experience: 600000
| | HP | Attack | Defense | Speed | Special Attack | Special Defense |
| Base Stats (RB/Y) | - | - | - | - | - | - |
| Base Stats (GS/C) | - | - | - | - | - | - |
| Base Stats (RS/FL/E) | 55 | 84 | 105 | 52 | 114 | 75 |
| Base Stats (DP/PT/HGSS) | – | – | – | – | – | – |
| Base Stats (BW/B2W2) | – | – | – | – | – | – |
| Base Stats (XY/ORAS) | – | – | – | – | – | – |
| Base Stats (SM/USUM) | – | – | – | – | – | – |
| Base Stats (Sword/Shield/BDSP) | – | – | – | – | – | – |
| Max Stats (RB/Y) | - | - | - | - | - | - |
| Max Stats (GS/C) | - | - | - | - | - | - |
| Max Stats (RS/FL/E) | 314 | 293 | 339 | 223 | 359 | 273 |
| Max Stats (DP/PT/HGSS) | – | – | – | – | – | – |
| Max Stats (B/W/B2W2) | – | – | – | – | – | – |
| Max Stats (X/Y/ORAS) | – | – | – | – | – | – |
| Max Stats (SM/USUM) | – | – | – | – | – | – |
| Max Stats (Sword/Shield/BDSP) | – | – | – | – | – | – |
| Effort Points (Sword/Shield/BDSP) | – | – | – | – | – | – |

## Type Matching

Move types which are super effective on Gorebyss: Electric, Grass
Move types which are not very effective on Gorebyss:Fire, Ice, Steel , Water
All other move types are normal effectiveness on Gorebyss.

## Moveset

| Level | Ruby / Sapphire | Fire Red / Leaf Green |
| Start | Whirlpool | Whirlpool |
| 8 | Confusion | Confusion |
| 15 | Agility | Agility |
| 22 | Water Pulse | Water Pulse |
| 29 | Amnesia | Amnesia |
| 36 | Psychic | Psychic |
| 43 | Baton Pass | Baton Pass |
| 50 | Hydro Pump | Hydro Pump |

### TM/HM

* RS/FL: Attract, Blizzard, Dive, Double Team, Facade, Frustration, Hail, Hidden Power, Hyper Beam, Ice Beam, Protect, Psychic, Rain Dance, Rest, Return, Safeguard, Secret Power, Shadow Ball, Surf, Toxic, Water Pulse, Waterfall

### Evolution

* RS/FL: Barrier, Body Slam, Confuse Ray, Mud Sport, Refresh, Supersonic

## Trading Cards

* EX Hidden Legends #18 - Gorebyss
* EX Legend Maker #17 - Gorebyss
* Great Encounter #38 - Gorebyss
* Primal Clash #51 - Gorebyss
* Primal Clash #52 - Gorebyss
* Celestial Storm #43 - Gorebyss
* Fusion Strike #67 - Gorebyss
| Basic: Clamperl | Stage 1: Huntail | (No Stage 2) |
| Basic: Clamperl | Stage 1: Gorebyss | (No Stage 2) |
# Network Plus Certification/Management/Performance Monitoring

| « | Network Management Objective 4.4: Performance Monitoring | » |
| Objective 4.3: Documentation Implementation | Network Management Objective 4.4: Performance Monitoring | Objective 4.5: Performance Optimization |
Objective 4.4: Conduct network monitoring to identify performance and connectivity issues

## Network monitoring utilities
### Packet sniffers

See Objective 5.2: Software Tools.

### Throughput testers

A throughput tester measures the amount of data that can be transferred through a network or processed by a device (such as the amount of data that can be retrieved from disk in a specific period of time). On a network, a throughput tester sends a specific amount of data through the network and measures the time it takes to transfer that data, arriving at a measure of the actual bandwidth. Use a throughput tester to validate the bandwidth on your network, and to identify when the bandwidth is significantly below what it should be. Note: A throughput tester can help you identify when a network is slow, but does not give you sufficient information to identify why it is slow.
# Network Plus Certification/Devices/Wireless

| « | Network Devices Objective 3.4: Basic Wireless |
| Objective 3.3: Advanced Switch Features | Network Devices Objective 3.4: Basic Wireless |
Objective 3.4: Implement a basic wireless network
# Network Plus Certification/Management

| « | Network Plus Certification Domain 4: Network Management | » |
| Domain 3: Network Devices | Network Plus Certification Domain 4: Network Management | Domain 5: Network Tools |
The Network Management Domain consists of 20% of the CompTIA Network+ exam.
* Objective 4.1: The OSI Model
* Objective 4.2: Documentation Types
* Objective 4.3: Documentation Implementation
* Objective 4.4: Performance Monitoring
* Objective 4.5: Performance Optimization
* Objective 4.6: Troubleshooting Methodology
* Objective 4.7: Connectivity Issues
# Network Plus Certification/Management/Documentation Types

| « | Network Management Objective 4.2: Documentation Types | » |
| Objective 4.1: The OSI Model | Network Management Objective 4.2: Documentation Types | Objective 4.3: Documentation Implementation |
Objective 4.2: Identify types of configuration management documentation

## Wiring schematics

Wiring schematics are drawings of where all the wires and circuits are. It also shows where and how they are connected. A wiring schematic is used to troubleshoot problems and to make sure that all the connections have been made and that everything is present. It assists in the replacement of cabling in case of a short circuit and eases the process of determining where new wires can be installed when additional capacity is needed.
# Network Plus Certification/Management/Connectivity Issues

| « | Network Management Objective 4.7: Connectivity Issues |
| Objective 4.6: Troubleshooting Methodology | Network Management Objective 4.7: Connectivity Issues |
Objective 4.7: Given a scenario, troubleshoot common connectivity issues and select an appropriate solution

## Physical issues
### Crosstalk

Crosstalk refers to any phenomenon by which a signal transmitted on one circuit or channel of a transmission system creates an undesired effect in another circuit or channel. This can occur within the different pairs of wires in a cable and is mitigated by using twisted pair cabling. In a wireless environment, two different wireless access points that are broadcasting on channels too close together in frequency can reduce the quality of the connection between themselves and wireless users.
In telecommunications, crosstalk is often distinguishable as pieces of speech or signaling tones leaking from other people's connections. If the connection is analog, twisted pair cabling can often be used to reduce the effects of crosstalk. Alternatively, the signals can be converted to digital form, which is much less susceptible to crosstalk.

### Interference
## Logical issues
### Port duplex mismatch

A duplex mismatch occurs when two devices are using different duplex settings. In this case, one device will try to transmit using full duplex, while the other will expect half duplex communications. By default, devices are configured to use autonegotiation to detect the correct duplex setting to use. If a duplex method cannot be agreed upon, devices should default to using half duplex. A duplex mismatch can occur in the following cases: • Both devices are configured to use different duplex settings. • Autonegotiation does not work correctly on one device. • One device is configured for autonegotiation and the other device is manually configured for full duplex.
Symptoms of a duplex mismatch include very slow network communications. Ping tests might appear to complete correctly, but normal communications work well below the expected speeds, even for half duplex communications.

### Incorrect VLAN (Virtual Local Area Network)

Incorrectly assigning a port to a VLAN might prevent a device from communicating through the switch.

### Wrong gateway

If the gateway is configured incorrectly, remote clients can't access network resources, local hosts can't access the Internet and they can't access hosts outside the local subnet.
# Network Plus Certification/Management/Documentation Implementation

| « | Network Management Objective 4.3: Documentation Implementation | » |
| Objective 4.2: Documentation Types | Network Management Objective 4.3: Documentation Implementation | Objective 4.4: Performance Monitoring |
Objective 4.3: Given a scenario, evaluate the network based on configuration management documentation
# RAC Attack - Oracle Cluster Database at Home/Clusterware Testing
## RAC Attack - Oracle Cluster Database at Home (e)

    Overview
    Planning Your Time
    Events
    Creating Printed Lab Handbooks
    Local Manual of Style
    Bullpen (Newly Contributed Content)
    Expanded Table of Contents

#### Part I: Setting Up RAC

* Hardware and Windows Preparation
* Linux Install
* Create Cluster
* Grid Install (ASM)
* Grid Install (Shared Filesystem)
* RAC Install
* Create Database
* Rolling Patches

#### Part II: Exploring RAC

* Clusterware Testing
* Services, Failover and Load Balancing
* RAC SQL and PLSQL
* RAC Backups and Recovery
Prev: Rolling Patches

## Clusterware Testing

* Clusterware and Fencing
* Clusterware Callouts
Next: Services, Failover and Load Balancing
# RAC Attack - Oracle Cluster Database at Home/Configure Node 1

Prev: Linux Install
* Create Interconnect
* Create Shared Disks
* Copy VM
* Configure Disks
* Configure Node 1
* Configure Node 2
* SSH and CVU
Next: Grid Install (ASM or Shared Filesystem)
After completing the previous lab, you should already be logged in as the oracle user on collabn1. You should already have a terminal open, where you are currently switched to the root user.
* As the root user, CONFIRM that the IP address if eth0 starts with 192.168.78 and that the IP address of eth1 starts with 172.16.100. [root@collabn1 ~]# ifconfig|grep net eth0 Link encap:Ethernet HWaddr 00:0C:29:07:F5:C0 inet addr:192.168.78.128 Bcast:192.168.78.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe07:f5c0/64 Scope:Link eth1 Link encap:Ethernet HWaddr 00:0C:29:07:F5:CA inet addr:172.16.100.128 Bcast:172.16.100.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe07:f5ca/64 Scope:Link inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host
* Update the IP addresses by directly editing the linux network configuration files. Update the BOOTPROTO line and add the remaining lines. [root@collabn1 ~]# cd /etc/sysconfig/network-scripts [root@collabn1 network-scripts]# gedit ifcfg-eth0 BOOTPROTO=none IPADDR=192.168.78.51 NETMASK=255.255.255.0 GATEWAY=192.168.78.2 [root@collabn1 network-scripts]# gedit ifcfg-eth1 BOOTPROTO=none IPADDR=172.16.100.51 NETMASK=255.255.255.0
* Update the DNS search domain [root@collabn1 network-scripts]# gedit /etc/resolv.conf search vm.ardentperf.com nameserver 192.168.78.2
* As root, restart the network services by typing service network restart. Then confirm the new ip addresses with ifconfig. Also confirm the search domain by inspecting /etc/resolv.conf – if the file has reverted then edit it again. (When I wrote this lab, the change stuck after the second time I edited the file.) You must perform this step in VMware; do not use PuTTY.
* Edit /etc/ hosts. EDIT the line with 127.0.0.1 and then ADD all of the other lines below: [root@collabn1 etc]# vi /etc/hosts 192.168.78.51 collabn1 collabn1.vm.ardentperf.com 192.168.78.61 collabn1-vip collabn1-vip.vm.ardentperf.com 172.16.100.51 collabn1-priv collabn1-priv.vm.ardentperf.com 192.168.78.52 collabn2 collabn2.vm.ardentperf.com 192.168.78.62 collabn2-vip collabn2-vip.vm.ardentperf.com 172.16.100.52 collabn2-priv collabn2-priv.vm.ardentperf.com 192.168.78.250 collab-scan collab-scan.vm.ardentperf.com 192.168.78.251 collab-gns collab-gns.vm.ardentperf.com  ::1 localhost6.localdomain6 localhost6 127.0.0.1 localhost.localdomain localhost
# RAC Attack - Oracle Cluster Database at Home/Copy VM

Prev: Linux Install
* Create Interconnect
* Create Shared Disks
* Copy VM
* Configure Disks
* Configure Node 1
* Configure Node 2
* SSH and CVU
Next: Grid Install (ASM or Shared Filesystem)
* In Windows Explorer, browse to the folder [RAC11g] \collabn1. Copy all of the files to the folder [RAC11g] \collabn2. Make sure that you copy - not move - the files. Hold down CTRL to copy with drag-and-drop in windows.
** The location of [RAC11g] was determined in the first lab. In a class, the instructor may provide the location.
** If the collabn2 folder does not exist, then create it.
* Browse to [RAC11g] \collabn2. Edit the file collabn1.vmx (the VMware Configuration File). You can use notepad or wordpad to edit the file.
* Find the line displayName and change it to collabn2 (the new node name), then save and close the file. displayName = "collabn2"
# RAC Attack - Oracle Cluster Database at Home/Common Overview

RAC Attack is a free curriculum and platform for hands-on learning labs related to Oracle RAC (cluster database). We believe that the best way to learn about RAC is with a lot of hands-on experience. This curriculum has been used by individuals at home and by instructors in classes since 2008.
The original contributors were Jeremy Schneider, Dan Norris and Parto Jalili. The handbook was published at http://www.ardentperf.com for several years before its migration to this wikibook. All RAC Attack content was released under the CC-BY-SA license in May 2011 when this project was initiated.
To learn about upcoming RAC Attack events or to organize one yourself, visit the Events page. You can use the shortcut http://racattack.org/events to access this page at any time.
The goal of this workbook is to help students learn about Oracle RAC cluster databases through guided examples. It can be used by organizers of events, by instructors in classes or by individuals at home.
RAC Attack differs in depth from other tutorials currently available.
* Every keystroke and mouse click is carefully documented here.
* The process is covered from the very beginning to the very end - from the very first installation of the Virtual Hypervisor on your laptop to various experiments on your running cluster database... with everything in between.
* The labs in the main workbook have been tested thoroughly and repeatedly.
# RAC Attack - Oracle Cluster Database at Home/Clusterware and Fencing

Prev: Rolling Patches
* Clusterware and Fencing
* Clusterware Callouts
Next: Services, Failover and Load Balancing
The goal of this lab is to demonstrate Oracle Clusterware’s fencing ability by forcing a configuration that will trigger Oracle Clusterware’s built-in fencing features. With Oracle Clusterware, fencing is handled at the node level by rebooting the non-responsive or failed node. This is similar to the as Shoot The Other Machine In The Head (STOMITH) algorithm, but it’s really a suicide instead of affecting the other machine. There are many good sources for more information online.
* Start with a normal, running cluster with the database instances up and running.
* Monitor the logfiles for clusterware on each node. On each node, start a new window and run the following command: [oracle@<node_name> ~]$ tail –f \ > /u01/grid/oracle/product/11.2.0/grid_1/log/`hostname -s`/crsd/crsd.log [oracle@<node_name> ~]$ tail –f \ > /u01/grid/oracle/product/11.2.0/grid_1/log/`hostname -s`/cssd/ocssd.log
* We will simulate “unplugging” the network interface by taking one of the private network interfaces down. On the collabn2 node, take the private network interface down by running the following command (as the root user): [root@collabn2 ~]# ifconfig eth1 down Alternatively, you can also simulate this by physically taking the HostOnly network adapter offline in VMware.
* Following this command, watch the logfiles you began monitoring in step 2 above. You should see errors in those logfiles and eventually (could take a minute or two, literally) you will observe one node reboot itself. If you used ifconfig to trigger a failure, then the node will rejoin the cluster and the instance should start automatically. If you used VMware to trigger a failure then the node will not rejoin the cluster.
** Which file has the error messages that indicate why the node is not rejoining the cluster?
** Is the node that reboots always the same as the node with the failure? Why or why not?
# RAC Attack - Oracle Cluster Database at Home/Create Cluster
## RAC Attack - Oracle Cluster Database at Home (e)

    Overview
    Planning Your Time
    Events
    Creating Printed Lab Handbooks
    Local Manual of Style
    Bullpen (Newly Contributed Content)
    Expanded Table of Contents

#### Part I: Setting Up RAC

* Hardware and Windows Preparation
* Linux Install
* Create Cluster
* Grid Install (ASM)
* Grid Install (Shared Filesystem)
* RAC Install
* Create Database
* Rolling Patches

#### Part II: Exploring RAC

* Clusterware Testing
* Services, Failover and Load Balancing
* RAC SQL and PLSQL
* RAC Backups and Recovery
Prev: Linux Install

## Create Cluster

* Create Interconnect
* Create Shared Disks
* Copy VM
* Configure Disks
* Configure Node 1
* Configure Node 2
* SSH and CVU
Next: Grid Install (ASM or Shared Filesystem)
# RAC Attack - Oracle Cluster Database at Home/Configure Disks

Prev: Linux Install
* Create Interconnect
* Create Shared Disks
* Copy VM
* Configure Disks
* Configure Node 1
* Configure Node 2
* SSH and CVU
Next: Grid Install (ASM or Shared Filesystem)
* In the Inventory tab at the left, select collabn1.
* Choose the Console tab. Click on the play button to start the VM. When you see the square boxes, click anywhere to open a console window.
* Login as the oracle user with the password racattack.
* Open a terminal window.
* Switch to the root user with the "su -" command. (The password is racattack.) CONFIRM that two new disks exist and that they have the appropriate sizes. These two lines should exactly match!! [root@collabn1 ~]# cat /proc/partitions major minor #blocks name ... 8 16 3407872 sdb 8 32 3407872 sdc
* Create partitions on all of the newly created disks with fdisk. [root@collabn1 ~]# fdisk /dev/sdb Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-652, default 1): ^M [default] Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-652, default 652): ^M [default] Using default value 652 Command (m for help): t Selected partition 1 Hex code (type L to list codes): da Changed system type of partition 1 to da (Non-FS data) Command (m for help): w The partition table has been altered! WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. Syncing disks.
** run fdisk /dev/sdb You should see the message "Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel"
** type "n" to create a new partition.
** type "p" for a primary partition.
** type partition number 1.
** press enter twice to accept the default first/last cylinders.
** type "t" to set the partition type.
** enter partition type da (Non-FS data).
** type "w" to write the partition table to disk.
* Repeat the previous step for disk /dev/sdc
# On 2D Inverse Problems/An infinite example

$\Lambda _{G}={\sqrt {L}}.$
    Exercise (**). Prove that the Dirichlet-to-Neumann operator of the network on the picture w/the natural boundary satisfies the equation.
(Hint:) Use the fact that the operator/matrix is the fixed point of the Schur complement]]: $\Lambda _{G}={\begin{pmatrix}2I&B\\B^{T}&\Lambda +2I\end{pmatrix}}/(\Lambda +2I),$ where $B=-{\begin{pmatrix}1&0&0&\ldots &1\\1&1&0&\ldots &0\\0&\vdots &\ddots &\ddots &\vdots \\\vdots &\vdots &\ddots &1&0\\0&0&\ldots &1&1\\\end{pmatrix}}$ is the circulant matrix, such that $L_{G}=4I-BB^{T}.$
# On 2D Inverse Problems/Basic definitions and background

The main subjects of study of this book are the local and global characteristices of graphs embedded in surfaces (2D manifolds) and the connections b/w their discrete and continuous properties. This chapter gives the definitions and the overview of the main mathematical objects that are involved in the inverse problems discussed in the book. These include the domains of definitions of the functions and operators, the boundary and spectral data and interpolation/extrapolation and restriction techniques.
# On 2D Inverse Problems/Bibliography

[AP] Astala, K. and P¨aiv¨arinta, L. "Calder´on’s inverse conductivity problem in the plane"
* [BIMS] Biesel, O.D., Ingerman D.V., Morrow J.A. and Shore W.T. "Layered Networks, the Discrete Laplacian, and a Continued Fraction Identity"
* [BDK] Borcea, L., Druskin, V. and Knizhnerman, L. "On the continuum limit of a discrete inverse spectral problem on optimal finite difference grids", Communications on Pure and Applied Mathematics, Vol. 000, 0001–0048 (2000)
* [BDMV] Borcea, L., Druskin, V., Mamonov, A.V. and Vasquez, G.F. "Resistor network approaches to electrical impedance tomography", http://arxiv.org/abs/1107.0343
* [CM] Curtis, E.B. and Morrow, J.A. "Inverse Problems for Electrical Networks"
* [CIM] Curtis, E.B., Ingerman, D.V. and Morrow, J.A. "Circular Planar Graphs and Resistor Networks"
* [CMM] Curtis, E.B., Mooers, E. and Morrow J.A. "Finding the conductors in circular networks from boundary measurements", RAIRO Model Math. Anal. Numer. 28 (1994), pp. 781-814.
* [DeV1] De Verdière, Yves Colin, "Réseaux électriques planaires", Prépublications de l'Institut Fourier 225 (1992), 1-20
* [DeV2] De Verdière, Yves Colin, "Reseaux electrique planaires I"
* [DIK] Druskin, V., Ingerman D.V. and Knizhnerman, L. "Optimal finite difference grids and rational approximations of the square root I. Elliptic problems"
* [ES] Edelman, A. and Strang, G. "Pascal matrices"
* [F] Fomin, S. "Loop-erased walks and total positivity", http://arxiv.org/pdf/math.CO/0004083.pdf
Kernels and Small Vibrations of Mechanical Systems", Revised Edition] * [K] Kac, M. "Can one hear the shape of a drum?", American Mathematical Monthly 73 (4, part 2): 1–23, (1966), doi:10.2307/2313748
* [M] Marshall, D.E. "An elementary proof of the Pick-Nevanlinna interpolation theorem"
* [N] Nachman, A.I. "Global uniqueness for a two-dimensional inverse boundary value problem"