OpenLLM-France/wikimedia huggingface dataset:
# Flora of New York/Clade lilioid monocots

| monocots   Acorales       Alismatales       Dioscoreales   Nartheciaceae—Aletris farinosa (white colicroot, unicorn root)     Dioscoreaceae    Dioscorea villosa (wild yam)     Dioscorea polystachya (Chinese yam, cinnamon vine)                Liliales   Melanthiaceae   Melanthieae     Anticlea elegans (white death camas)     Stenanthium leimanthoides (pine barrens death camas)           Veratrum viride (false hellebore, Indian corn lily)       Veratrum virginicum (Virginia bunchflower)†     Veratrum hybridum (crisped bunchflower)†         Amianthium muscitoxicum (fly poison)†               Heloniadeae—Helonias bullata (swamp pink)     Chionographideae—Chamaelirium luteum (fairywand, devil’s bit)       Parideaee—Trillium spp. (8 trilliums)           Colchicaceae—Uvularieae—Uvularia spp. (4 bellworts)       Smilacaceae—Smilax spp. (7 carrion flowers, greenbiers)     Liliaceae             Asparagales   Orchidaceae       Hypoxidaceae       Iridaceae       Asphodelaceae       Amaryllidaceae     Asparagaceae                     Poales       Zingiberales     Commelinales | alismatid monocots lilioid monocots commelinid monocots |
# Flora of New York/Contributors

Contributors to this document include:
Any and all with an interest in the subject are welcome to contribute.
# THREADBEGIN
## Statement

(+) Appearance (+) Standard (+) Console

## Syntax

THREADBEGIN FN name [, parameter& [, stackMin&]] === Revised === August, 2002 (Release 7)

## Description

What exactly is a thread? It is a function that performs a task. The difference between a threaded function and any other function is that the threaded version runs in the background. Your program (and other running processes) advance without interruption as the threaded task is performed. There are many reasons for using threaded functions. One that is becoming popular relates to functions that access Internet connections. Since logging in and downloading often take a good bit of time, it makes sense to hand such a task to a threaded function and go on about your business. You might handle other tasks like complex calculations, lengthy sorts, or time-consuming file loads. When a threaded function is called, it executes without stopping until it is complete—just like any other function. But at some point inside of the function, you yield to other processes by calling THREADSTATUS. The THREADSTATUS statement allows other actions to take place and optionally sets a timed delay for the number of ticks that should elapse before your function regains control. The parameter passed to a thread may be any long integer required by your program. It is for your use. If a parameter is sent, you should accept it in the named local function. For instance, if a parameter were used in the example below, we would create the function with LOCAL FN myThread(param AS LONG) instead of just plain LOCAL FN myThread. If the stackMin parameter is omitted, FutureBASIC sets a minimum stack space of 131072 bytes (128K). You may experiment with larger or smaller values for your specific needs. Example: This simple example creates a thread that prints a string of text, piece by piece, in a FOR/NEXT loop. The THREADSTATUS call installs a callback time of 10 ticks which makes the text appear slowly. You can type into the edit field as the threaded text is placed on the screen. LOCAL FN myThread
THE ABOVE SECTION IS EXTREMELY CONFUSING AND STILL NEEDS FIXING!!!

### See Also

THREADSTATUS; TIMER; ON TIMER;
# Futurebasic/Language/Reference/tron x
## TRON X
### Statement

(+) Appearance (+) Standard (+) Console

### Syntax

TRON X

### Description

The TRON X statement is a debugging tool. It examines the event queue for any recent Command-period keypresses by the user. If a Command-period keypress is found, TRON X displays a dialog giving the user the option to quit the program (this is the same dialog that is displayed by HANDLEEVENTS when the user pressed Command-period and there is no designated break-handling routine). TRON X is handy for manually breaking out of a loop. If your program seems to get "stuck" inside a loop for a long time, try inserting a TRON X statement inside the loop. The next time you run your program, you will be able to break out of the loop by pressing Command-period.

#### See Also

TRON/TROFF; HANDLEEVENTS; ON BREAK
# Futurebasic/Language/Reference/typeof
## TYPEOF
### Function

(+) Appearance (+) Standard (+) Console

### Syntax

dataType = TYPEOF({variable|typeName})

### Description

When FB compiles your program, it associates a unique integer with each data type that your program uses. The TYPEOF function returns the integer that's associated with the specified type. typeName should be the name of a type that was previously defined in a BEGIN RECORD statement or a #DEFINE statement; or the name of one of FutureBasic's built-in types (such as INT, LONG, etc.). variable can the name of any variable. In this case, TYPEOF returns the type ID number associated with the variable's type. Note that if the variable was not previously declared in a DIM statement, and has no type-identifier suffix, TYPEOF will assume that the variable's type is the default type (which is INT unless a DEF<type> statement applies). Example: This program uses TYPEOF to determine what kind of data a pointer points to.
END program output: The data you passed was: 1623 The data you passed was: 426193 The data you passed was: Hello Note: The integer values returned by TYPEOF are determined dynamically at compile time. You should not count on TYPEOF(someType) to return the same value every time your program is compiled.

#### See Also

SIZEOF; Appendix C: Data Types and Data Representation
# Futurebasic/Language/Reference/timer function
## TIMER
### Function

(+) Appearance (+) Standard (+) Console

### Syntax

secondsSinceMidnight& = TIMER

### Description

This function returns the current time of day expressed as a number of seconds since midnight. Its value ranges from 0 through 86399. Note: The TIMER function is useful for measuring elapsed time intervals, as long as you make appropriate adjustments in case the measured interval crosses the midnight boundary. To measure time intervals with a finer resolution than 1 second, use the Toolbox routines TICKCOUNT or MICROSECONDS. The TICKCOUNT function measures the number of "ticks" since startup (there are approximately 60.15 ticks per second), and the MICROSECONDS procedure measures the number of microseconds since startup.

#### See Also

TIME$
# Futurebasic/Language/Reference/ucase
## Syntax

UCASE$
UCASE$$

## Description

This function returns a copy of string$ or container$$ with all its lower-case letters converted to upper-case. This also applies to letters with diacritical marks; so for example the string "mágüey" will be converted to "MÁGÜEY". UCASE$ is useful when you want to compare two strings for equality without regard to their letter case. For example, suppose you want all of the following strings to be treated in the same way: STAZ Staz staz sTAz Any pair from the above set will be considered to "match" if they're compared as follows: IF UCASE$(str1$) = UCASE$(str2$) THEN PRINT "Names match." The comparison of containers requires the use of an additional function. See FN FBcompareContainers for more information. Note: To test whether one string is greater than or less than another without regard to letter case, an alternative method is to use the string comparison operators ">>" and "<<". See Appendix D: Numeric Expressions, for more information.

## See Also

FN FBcompareContainers; Appendix F: ASCII Character Codes
# Futurebasic/Language/Reference/tron
## TRON/TROFF
### Statements

(+) Appearance (+) Standard (+) Console

### Syntax

TRON [ALL] TRON BREAK TROFF

### Description

These statements affect which parts of your program can be traced with the Debugger tool. In order to build a program that can be traced in the Debugger, you must create your program as a project (using the Project Manager), and in the Project window you must select with a "bug icon" each file that you want to trace. By default, all the lines in the selected files can then be traced. However, there may be cases in which you want to limit the lines that can be traced, especially because treaceable lines make your compiled program's size larger and take somewhat longer to execute. TROFF cause subsequent lines to be untraceable. This is a non-executable statement, so it affects the lines that appear below it, regardless of their actual order of execution. It overrides previous occurrences of TRON [ALL]. TRON [ALL] causes subsequent lines to be traceable. This is the default condition for all lines in your file above the first occurrence of TROFF. This is a non-executable statement, so it affects the lines that appear below it, regardless of their actual order of execution. It overrides previous occurrences of TROFF. Note that the ALL keyword is optional. TRON BREAK is an executable statement which causes the Debugger window to appear (if it was previously hidden), and causes execution to pause. It has the same effect as setting a breakpoint in the Debugger. TRON BREAK is ignored if it appears within a section of code which is not traceable.

#### See Also

COMPILE LONG IF; TRON X
# THREADSTATUS
## Function

(+) Appearance (+) Standard (+) Console

## Syntax

abortBoolean = THREADSTATUS[(ticks&)]

## Revised

August, 2002 (Release 7)

## Description

In a threaded function, it is necessary to tell the Thread Manager when you wish to yield to other running processes. A thread which yields very little time will run faster, but will cause all other operations on the computer to run at a slower rate. The THREADSTATUS function returns a Boolean result to indicate whether or not the thread should continue operation. One reason that a thread might be asked to cease operation would be if the computer was about to shut down. When you receive a non-zero result from the THREADSTATUS statement, you should exit the threaded function immediately.

## See Also

THREADBEGIN; TIMER; ON TIMER
# Futurebasic/Language/Reference/timer statement
## TIMER
### Statement

(+) Appearance (+) Standard Console

### Syntax

TIMER = interval TIMER(0) OFF TIMER(0) END

### Revised

January 14, 2001 (Release 4)

### Description

If you have designated a timer-event handling routine (using the ON TIMER statement), the TIMER statement alters the interval at which timer events occur. If timer events have not yet been initiated (because your ON TIMER statement specified an interval of zero), then the TIMER statement also initiates timer events. If the interval parameter is greater than zero, it specifies the interval in seconds. If interval is less than zero, then ABS(interval) specifies the interval in ticks (a tick is approximately 1/60 second). If you set interval to zero, the TIMER statement is ignored; you cannot use the TIMER statement to disable timer events once they've been initiated. Timer events are internally queued by FB until your application is ready to accept them. If you are receiving events once per second and your program is occupied with other tasks for 10 seconds, you wll receive 10 timer events at the first available opportunity. If you wish to flush the timer event queue, use TIMER(0) OFF or TIMER(0) END.

#### See Also

ON TIMER
# Futurebasic/Language/Reference/timestring
## TIME$
### Function

(+) Appearance (+) Standard (+) Console

### Syntax

currentTime$ = TIME$

### Description

This function returns the current time of day as an 8-character string in this format: hh:mm:ss where hh is a 2-digit hour in 24-hour format ("00" through "23"), mm is a 2-digit minutes value ("00" through "59"), and ss is a 2-digits seconds value ("00" through "59"). Example: This program speaks one of three appropriate phrases depending on the time of day. hour = VAL(LEFT$(TIME$,2)) SELECT CASE hour
oserr = FN SPEAKSTRING("Good evening.")
oserr = FN SPEAKSTRING("Good afternoon.")
oserr = FN SPEAKSTRING("Good morning.") END SELECT WHILE FN SPEECHBUSY WEND Note: To get a time string which is formatted according to the user's "Date & Time" preferences, use the Toolbox procedure IUTIMESTRING. For example: DIM timeStr$, @ t& CALL GETDATETIME( t& ) CALL TIMESTRING( t&, _false, timeStr$ , _nil ) PRINT "The time is now "; timeStr$

### See Also

DATE$; TIMER function
# GNU Health/Sequences

← Models · Scheduler →
# GNU Health/The core module
## The Core Module

As we have mentioned already in previous sections of the book, GNU Health is composed of different modules which will provide specific functionality to your health center.
The module health is at the center of GNU Health. This module contains the core models and classes, so the rest of the modules will just inherit them. This gives modularity and scalability, without leaving behind the most important building blocks in public health. Some of the models found in the core module are:
* Individuals
* Families
* Domiciliary Units
* Operational Sectors
* Health Centers
* Diseases
* Patient
* Patient Evaluation / Encounters
* Medicaments
* Treatments
There are many others models in the core module, but this subset will give you an idea of the concept. If you are not a programmer, you don't really have to worry much about how GNU Health deals internally with dependencies and inter-module communication. For example, if you want to install the pediatrics module health_pediatrics, it will automatically mark the core module health for installation, as a dependency.
To learn more about GNU Health modules, please refer to the Modules chapter.
In this documentation, we will cover the functionality of the core module first before exploring the possibilities of the other modules.

## People before Patients

If we want to be good in a Public Health system, the first thing we need to do is knowing our population. As I say, we need to deal with people before patients . Whenever possible, the health center should have a census, and the list of domiciliary units (DU) and their conditions, at least of those habitants that are part of the operational sector covered by the health center.
From a functional and implementation point of view, we should see the GNU Health core module objects as the first ones to be assessed. The process of collecting this information will get our health center involved with the community. In the next chapters we will be covering how to setup a Domiciliary Unit (DU); an Individual; the habitants of a DU; Families ; Operational Areas and Operational Sectors.
Once you have that information in place, you will be able to give a new attribute to the individual when she or he first come to your office, the patient attribute. As you can see, there are precious information and actions that can be done in Public Health before dealing with a single patient.
← First Steps · Health Institutions →
# GNU Health/Socioeconomics
## Introduction to Socioeconomics

The module health_socioeconomics takes care of the input of all the socio-economic factors that influence the health of the individual / family and society.
Among others, GNU Health includes important factors such as living conditions, educational level, infrastructure, family affection (APGAR), drug addiction, hostile environment, teenage pregnancy, working children, etc.

## Main Tab

The Main factors assess the general quality of life through the housing conditions, education level, occupation, workplace and its conditions. The information in this menu is supplemented by a free text box where you can add relevant notes of interest. In each category, we found a wide spectrum that will allow us to accurately define the socioeconomic status of the patient and determine its living conditions.
In the particular case of this example, we see that the patient Ana Betz has a middle socioeconomic level, has completed university education and works as a teacher. Ana Betz also spends 10 hours away from home, does not work at home and her workplace is not a hostile area.

## Infrastructure Tab

Regarding the Infrastructure tab, we find the checklist of the patient basic services such as sanitary sewers, gas supply, telephone, internet...as we can see in the next example:
Note that the checklist is designed to uncheck the service that is lacking. All services are already tagged for an easier way to complete the list.

## Family Tab

The Family tab provides information about the family through the Family APGAR. The Family APGAR has been widely used to study the relationship of family function and health problems in family practice offices. This index will provide a score that assess adult satisfaction with social support from the family. We can also complete the information with Other Family issues such as drug adiction, family abuse, domestic violence, working children, etc.
← Patient Management · Lifestyle →
# GNU Health/Success Stories
### Success Stories

This section lists some implementations of GNU Health. Don't expect it to be complete.
| Year | Country | City | Hospital | Link | Description |
| 2010 | Worldwide | -- | GNU Solidario Hospital | GNU Health Demo Server | This is the GNU Health Demo Hospital |
# Introduction

Thalamus is the message and authentication server of the GNU Health Federation.
The Thalamus project provides a RESTful API hub to all the GNU Health Federation nodes. The main functions are:
* Message server: A concentrator and message relay from and to the participating nodes in the GNU Health Federation and the GNU Health Information System. Some of the participating nodes include the GNU Health HMIS, mobile PHR applications, laboratories, research institutions and civil offices.
* Authentication Server: Thalamus also serves as an authentication and authorization server to interact with the GNUHealth Information System
In order to communicate to the Health Information System, a node must go through Thalamus. The user/node must provide proper credentials, and after checking for the access level, it will grant access to the resource with the appropriate method.

## Installation Instructions

If you want to install Thalamus, or want detailed technical information, refer to the GNU Health Federation Technical Guide
# History of wireless telegraphy and broadcasting in Australia/Topical/Legislation/C1919A00004/FRLI
## WIRELESS TELEGRAPHY.

No. 4 of 1919.
An Act to amend Section Two of the Wireless Telegraphy Act 1905–1915.
[Assented to 8th September, 1919.]
BE it enacted by the King’s Most Excellent Majesty, the Senate, and the House of Representatives of the Commonwealth of Australia, as follows:—

#### Short title and citation.

1.—(1.) This Act may be cited as the Wireless Telegraphy Act 1919.
(2.) The Wireless Telegraphy Act 1905–1915, as amended by this Act, may be cited as the Wireless Telegraphy Act 1905–1919.

#### Interpretation.

2. Section two of the Wireless Telegraphy Act 1905–1915 is amended by inserting in the definition of “Wireless telegraphy”, after the word “telegraphic”, the words “or telephonic”.
# History of wireless telegraphy and broadcasting in Australia/Topical/Legislation/C1923L00097
## Wireless Telegraphy Regulations 1923

The commencement of the Wireless Telegraphy Regulations 1923 reflected the transition of regulation of wireless from the Department of Navy to the Postmaster-General's Department and enabled a new era of amateur activity which had effectively been quashed since early in the first World War.

### Resources

A comprehensive summary of matters pertaining to the Wireless Regulations 1923 has not yet been prepared, however the following resources have been assembled in preparation:
* Research - Wireless Telegraphy Regulations 1923 - Summary of research to date
* FRLI - Wireless Telegraphy Regulations 1923 - Transcription of the instrument from the Federal Register of Legislative Instruments
* Transcriptions and Notes - Wireless Telegraphy Regulations 1923 - More than 10 transcriptions and notes, primarily from the NLA's Trove
* Photos and other graphics - Wireless Telegraphy Regulations 1923 - Nothing uploaded as yet, no material identified as yet
* Incubator of Wikipedia Article on Wireless Telegraphy Regulations 1923 - Coming real soon now!

### Internet Material

No significant articles specifically about the Wireless Telegraphy Regulations 1923 and in the public domain have yet been identified
# History of wireless telegraphy and broadcasting in Australia/Topical/Legislation/C1919A00004
## Wireless Telegraphy Act 1919

Although wireless telephony had been the subject of experiments in Australia since the early 1900s (most notably by Henry Sutton, callsign XLM), by 1919 there was considerable public interest in wireless telephony, with demonstrations most notably by AWA. The Wireless Telegraphy Act 1905-1915 most likely extended to cover wireless telephony also, but to remove all doubt, the Act was simply and concisely amended to extend the definition of wireless telegraphy to include telephonic communication also. Thus the Australian Government asserted complete control of both wireless telegraphy and the emerging technology of wireless telephony.

### Resources

A comprehensive summary of matters pertaining to the Wireless Telegraphy Act 1919 has not yet been prepared, however the following resources have been assembled in preparation:
* Research - Wireless Telegraphy Act 1919 - Summary of research to date
* FRLI - Wireless Telegraphy Act 1919 - Transcription of the instrument from the Federal Register of Legislative Instruments
* Transcriptions and Notes - Wireless Telegraphy Act 1919 - More than 10 transcriptions and notes, primarily from the NLA's Trove
* Photos and other graphics - Wireless Telegraphy Act 1919 - Nothing uploaded as yet, no material identified as yet
* Incubator of Wikipedia Article on Wireless Telegraphy Act 1919 - Coming real soon now!

### Internet Material

No significant articles specifically about the Wireless Telegraphy Act 1919 and in the public domain have yet been identified
# History of wireless telegraphy and broadcasting in Australia/Topical/Legislation/C1920L00256

Summary: Wireless Telegraphy Regulations 1920 C1920L00256 SR 1920 No. 256, 9 December 1920 (in operation forthwith)

## Wireless Telegraphy Regulations 1920

The commencement of the Wireless Telegraphy Regulations 1920 reflected the transition of regulation of wireless from the Department of Navy to the Postmaster-General's Department and enabled a new era of amateur activity which had effectively been quashed since early in the first World War.

### Resources

A comprehensive summary of matters pertaining to the Wireless Regulations 1920 has not yet been prepared, however the following resources have been assembled in preparation:
* Research - Wireless Telegraphy Regulations 1920 - Summary of research to date
* FRLI - Wireless Telegraphy Regulations 1920 - Transcription of the instrument from the Federal Register of Legislative Instruments
* Transcriptions and Notes - Wireless Telegraphy Regulations 1920 - More than 10 transcriptions and notes, primarily from the NLA's Trove
* Photos and other graphics - Wireless Telegraphy Regulations 1920 - Nothing uploaded as yet, no material identified as yet
* Incubator of Wikipedia Article on Wireless Telegraphy Regulations 1920 - Coming real soon now!

### Internet Material

No significant articles specifically about the Wireless Telegraphy Regulations 1920 and in the public domain have yet been identified

### In-line Citations

* ↑ https://www.legislation.gov.au/Details/C1920L00256